Specifications

CHAPTER
22-1
Cisco Unity Express Voice-Mail and Auto-Attendant CLI Administrator Guide for 3.0 and Later Versions
OL-14010-09
22
Registering Cisco Unity Express Endpoints to
Cisco Unified Messaging Gateway
This section describes Cisco Unity Express endpoints, covering principally the new commands in Cisco
Unity Express 3.1 to enable endpoints of this type to autoregister with Cisco Unified Messaging Gateway
(UMG).
Endpoints running Cisco Unity Express 3.0 or earlier do not support autoregistration. They must be
manually configured on Cisco UMG.
The section contains the following topics:
• Overview of the Autoregistration Process, page 1
• Configuring Autoregistration with Cisco UMG, page 2
• Manually Registering a Cisco Unity Express Endpoint, page 6
• Verifying the Registration Status of a Cisco Unity Express Endpoint, page 12
• Enabling or Disabling Remote Lookup, With or Without TUI Confirmation, page 14
• Viewing Cached and/or Configured Network Locations, page 14
• Refreshing Locations, page 15
• Setting the Expiration for Cached Locations, page 15
• Overloading a NAT Device: the Consequences for Endpoints, page 15
Overview of the Autoregistration Process
The purpose of autoregistration is for Cisco UMG to automatically “discover” a legitimate Cisco Unity
Express 3.1 endpoint.
Note Currently, the only type of endpoint that can autoregister is Cisco Unity Express 3.1. In the current
section, the term ‘endpoint’ refers exclusively to that type of endpoint, unless otherwise specified.
A messaging gateway discovers whether an endpoint is legitimate by attempting to validate the shared
secret information in the autoregistration message sent by the endpoint. Successful validation ensures
that VPIM messages can only be exchanged between trusted peers.
The autoregistration process starts after the endpoint boots up. An appropriately configured endpoint is
enabled to autoregister and it has the following information: