Specifications

22-2
Cisco Unity Express Voice-Mail and Auto-Attendant CLI Administrator Guide for 3.0 and Later Versions
OL-14010-09
Chapter 22 Registering Cisco Unity Express Endpoints to Cisco Unified Messaging Gateway
Configuring Autoregistration with Cisco UMG
• The location-id and IP address or domain name of its primary (and where applicable, its secondary)
messaging gateway
• Registration ID and password that the messaging gateways will be expecting.
– The instructions for configuring this ID and password on Cisco UMG are given in the
Cisco UMG 1.0 CLI Administrator Guide.
– The instructions for configuring this ID and password on Cisco Unity Express 3.1 are given
below, in
“Configuring Autoregistration with Cisco UMG” on page 2.
Beginning the process, the endpoint sends registration requests to both the primary Cisco UMG and the
secondary messaging gateway in that order, if a secondary is configured. In the registration message is
information about itself, such as its own location ID, broadcast ID, and so on. If the primary messaging
gateway encounters configuration problems during registration (for example, a missing location-id), the
process will fail, and the endpoint will not try to register with the secondary messaging gateway. If the
problems are of a different nature (for example, connectivity problems) the endpoint will go ahead and
try to register with the secondary messaging gateway.
When the endpoint autoregisters, the messaging gateway adds the endpoint to a trusted endpoints table
and the endpoint is then allowed to send and receive VPIM messages to and from the messaging gateway
with which it has registered, as well as to retrieve remote user information.
Automatic directory information exchange takes place a couple of minutes after registration, thereby
enabling the messaging gateway to learn about the endpoint’s properties.
Endpoints of the types Cisco Unity Express 3.0 or earlier, Cisco Unity, and Avaya Interchange do not
support autoregistration, so they must be individually provisioned from messaging gateways.
Instructions for doing this are given in the Cisco UMG 1.0 CLI Adminstrator Guide. An endpoint
running Cisco Unity Express 3.1 that is not enabled to autoregister will be treated the same as these other
types of endpoint.
Configuring Autoregistration with Cisco UMG
An endpoint running Cisco Unity Express 3.1 or later can autoregister with Cisco Unified Messaging
Gateway. This means that when the endpoint comes online, it seeks out its messaging gateways (both
primary and secondary, if configured) and registers itself. The alternative - manual provisioning (as
opposed to autoregistration) - entails configuring all relevant details of each endpoint on its messaging
gateway. This is the only option available to endpoints not running Cisco Unity Express 3.1.
After the messaging gateway authorizes the endpoint, it exchanges directories with its peers so that the
whole system becomes aware that this endpoint is now online. Once you have enabled autoregistration,
any time either the endpoint or the messaging gateway goes offline, the endpoint will re-register
automatically as soon as both come back online.
Before enabling autoregistration, you must first specify the primary and then the secondary messaging
gateway access information. Only after this do you enable autoregistration. Issuing these commands
causes the profile(s) for the messaging gateways to be stored in the running configuration on Cisco Unity
Express 3.1.
Note The endpoint cannot autoregister until you issue the messaging-gateway registration
command.
Caution You must copy the configurations to the startup-config to make them persistent.