Cisco Unified Messaging Gateway 1.0 CLI Administrator Guide - Appendix A: Registering Cisco Unity Express Endpoints to UMG 1.0 [Cisco Unified Messaging Gateway]

Table Of Contents

Appendix A: Cisco Unity Express Endpoint Autoregistration to Cisco Unified Messaging Gateway 1.0

Overview of the Autoregistration Process

Configuring Cisco Unity Express 3.1 and later versions Autoregistration with Cisco UMG

SUMMARY STEPS

DETAILED STEPS

Example

Manually Registering a Cisco Unity Express Endpoint

Examples

Verifying the Registration Status of a Cisco Unity Express 3.1 Endpoint

Enabling or Disabling Remote Lookup, With or Without TUI Confirmation

Viewing Cached and/or Configured Network Locations

Refreshing Locations

Setting the Expiration for Cached Locations

Overloading a NAT Device: the Consequences for Endpoints

Appendix A: Cisco Unity Express Endpoint Autoregistration to Cisco Unified Messaging Gateway 1.0

Revised: April 13, 2010

This section covers principally the new commands in Cisco Unity Express 3.1 and later versions to enable endpoints of this type to autoregister with Cisco Unified Messaging Gateway (UMG) 1.0.

Endpoints running Cisco Unity Express 3.0 or earlier versions do not support autoregistration. They must be manually configured on Cisco UMG.

An endpoint of the type Cisco Unity Express 3.1 and later versions that does not autoregister will be treated as if it were Cisco Unity Express 3.0 or earlier versions.

The section contains the following topics:

•Overview of the Autoregistration Process

•Configuring Cisco Unity Express 3.1 and later versions Autoregistration with Cisco UMG

•Manually Registering a Cisco Unity Express Endpoint

•Verifying the Registration Status of a Cisco Unity Express 3.1 Endpoint

•Enabling or Disabling Remote Lookup, With or Without TUI Confirmation

•Viewing Cached and/or Configured Network Locations

•Refreshing Locations

•Setting the Expiration for Cached Locations

•Overloading a NAT Device: the Consequences for Endpoints

Overview of the Autoregistration Process

The purpose of autoregistration is for Cisco UMG to automatically "discover" legitimate endpoints of the type Cisco Unity Express 3.1 and later versions. (

Note The only type of endpoint that can autoregister is Cisco Unity Express 3.1 and later versions. In this appendix, 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 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:

•ï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 "Configuring Endpoint Autoregistration Support" on page 28.

–The instructions for configuring this ID and password on Cisco Unity Express 3.1 and later versions are given below, in "Configuring Cisco Unity Express 3.1 and later versions Autoregistration with Cisco UMG".

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.

Note If autoregistration for the primary messaging gateway fails cue to incorrect configuration, the endpoint does not attempt to proceed with the secondary messaging gateway. However, if connectivity problems prevent the endpoint from contacting the primary messaging gateway, the endpoint does try to reach the secondary messaging gateway.

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 versions, 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 "Provisioning Endpoints Manually" on page 31. An endpoint running Cisco Unity Express 3.1 and later versions that is not enabled to autoregister will be treated the same as these other types of endpoint.

Configuring Cisco Unity Express 3.1 and later versions Autoregistration with Cisco UMG

An endpoint running Cisco Unity Express 3.1 and later versions or later can autoregister with Cisco Unified Messaging Gateway. This means that when the endpoint comes online (or when you use the messaging-gateway registration command), it seeks out its messaging gateway(s), if configured) and registers itself. The alternative is manual provisioning, which entails configuring all relevant details for each endpoint on its messaging gateway. This is the only option available to supported endpoints not running Cisco Unity Express 3.1 and later versions.

After an endpoint autoregisters, its messaging gateway exchanges directories with its peers so that the whole system becomes aware that this endpoint is now online. After the endpoint administrator enables 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, the administrator for Cisco Unity Express 3.1 and later versions must specify the primary (and optionally the secondary) messaging gateway access information. Using these commands on the endpoint causes the profile(s) for the messaging gateways to be stored in the endpoint's running-config.

Caution You must copy these configurations to the startup-config to make them persistent.

SUMMARY STEPS

1. config t

2. messaging-gateway primary location-id { umg-ip-addr | umg-hostname }

3. username user password { text | encrypted } password

4. (Optional) retry-interval integer

5. (Optional) nat { http | vpim } a.b.c.d integer

6. end

7. (Optional) messaging-gateway secondary location-id { umg-ip-addr | umg-hostname }

8. (Optional) username user password { text | encrypted } password

9. (Optional) retry-interval integer

10. (Optional) nat { http | vpim } a.b.c.d integer

11. end

12. messaging-gateway registration

13. end

14. show messaging-gateway

DETAILED STEPS

Command or Action

Purpose

Step 1

config t

Example:

se-10-0-0-0# config t

Enters configuration mode.

Step 2

messaging-gateway primary location-id { umg-ip-addr | umg-hostname }

Example:

se-10-0-0-0(config)# messaging-gateway primary 100 192.0.2.21

Enters messaging gateway configuration mode and specifies the following information for the primary messaging gateway:

•location-id--the location-id of the primary messaging gateway

•umg-ip-addr | umg-hostname--the IP address or hostname of the primary messaging gateway

Configurethe primary messaging gateway before the secondary. If you do not, you will get the error message "Primary messaging gateway needs to be configured first."

Step 3

username user password { text | encrypted } password

Example:

se-10-0-0-0(config-messaging-gateway)# username cue31 password text herein

Specifies the username and password required to autoregister with the messaging gateway. Note that the username is not necessarily the same as the endpoint's location ID, because the Cisco UMG administrator can configure a messaging gateway to expect the same username from multiple endpoints.

Step 4

retry-interval integer

Example:

se-10-0-0-0(config-messaging-gateway)# retry-interval 2

(Optional) The retry-interval is the delay in minutes before the endpoint attempts to reregister with the messaging gateway. The default is 5 minutes, range 0 - 65535.

Step 5

nat { http a.b.c.d integer | vpim a.b.c.d integer }

Example:

se-10-0-0-0(config-messaging-gateway)# nat http 192.0.2.22 80

(Optional) Configures HTTP or VPIM NAT for the specified messaging gateway. Integer is the HTTP or the VPIM port, range 1 - 65535.

Step 6

end

Example:

se-10-0-0-0(config-messaging-gateway)# end

Exits messaging gateway configuration mode and enters config mode.

Step 7

messaging-gateway secondary location-id { umg-ip-addr | umg-hostname }

Example:

se-10-0-0-0(config)# messaging-gateway secondary 101 192.0.2.21

(Optional) Enters messaging gateway configuration mode and specifies the following information for the secondary messaging gateway:

•location-id--the location-id of the secondary messaging gateway

•umg-ip-addr | umg-hostname--the IP address or hostname of the secondary messaging gateway

Configurethe primary messaging gateway before the secondary. If you do not, you will get the error message "Primary messaging gateway needs to be configured first."

Step 8

username user password { text | encrypted } password

Example:

se-10-0-0-0(config-messaging-gateway)# username cue32 password text herein

Specifies the username and password required to autoregister with the messaging gateway. Note that the username is not necessarily the same as the endpoint's location ID, because the Cisco UMG administrator can configure a messaging gateway to expect the same username from multiple endpoints.

Step 9

retry-interval integer

Example:

se-10-0-0-0(config-messaging-gateway)# retry-interval 2

(Optional) The retry-interval is the delay in minutes before the endpoint attempts to reregister with the messaging gateway. The default is 5 minutes, range 0 - 65535.

Step 10

nat { http a.b.c.d integer | vpim a.b.c.d integer }

Example:

se-10-0-0-0(config-messaging-gateway)# nat vpim 192.0.2.23 9925

(Optional) Configures HTTP or VPIM NAT for the specified messaging gateway. Integer is the HTTP or the VPIM port, range 1 - 65535.

Step 11

end

Example:

se-10-0-0-0(config-messaging-gateway)# end

Exits messaging gateway configuration mode.

Step 12

messaging-gateway registration

Example:

se-10-0-0-0(config)# messaging-gateway registration

Causes the endpoint to send a registration message to its primary and, if applicable, to its secondary messaging gateway, unless registration with the primary fails due to a configuration error.

Step 13

end

Example:

se-10-0-0-0(config)# end

Exits config mode and enters EXEC mode.

Step 14

show messaging-gateway

Example:

se-10-0-0-0# show messaging-gateway

(Optional) Displays the details associated with the registration with the messaging gateway, successful or otherwise. For more information, see the "Verifying the Registration Status of a Cisco Unity Express 3.1 Endpoint" section.

Step 15

write memory

Example:

se-10-0-0-0# write memory

Copies the running-config to the startup-config.

Example

The following commands on a Cisco Unity Express 3.1 and later versions endpoint set it up to autoregister with Cisco UMG, and then enable autoregistration and finally write the configuration to startup-config.
se-10-0-0-0# config t
se-10-0-0-0(config)# messaging-gateway primary 100 192.0.2.0
se-10-0-0-0(config-messaging-gateway)# username cue31 password text herein
se-10-0-0-0(config-messaging-gateway)# retry-interval 2
se-10-0-0-0(config-messaging-gateway)# nat http 192.0.2.22 80
se-10-0-0-0(config-messaging-gateway)# end
se-10-0-0-0(config)# messaging-gateway secondary 101 192.0.2.21
se-10-0-0-0(config-messaging-gateway)# username cue32 password text herein
se-10-0-0-0(config-messaging-gateway)# retry-interval 2
se-10-0-0-0(cconfig-messaging-gateway)# nat vpim 192.0.2.23 9925
se-10-0-0-0(config-messaging-gateway)# end
se-10-0-0-0(config)# messaging-gateway registration
se-10-0-0-0(config)# end
se-10-0-0-0> show messaging-gateway
Messaging gateways :
AutoRegister to gateway(s) : Enabled
Remote directory lookup : Enabled (without TUI prompt)
Primary messaging gateway :
        192.0.2.0
        nat http 192.0.2.22 (80)
        Status : Registered (Wed Sep 19 18:04:45 PDT 2007)
        Reg-expiration : Thu Sep 20 18:04:45 PDT 2007
        Default route : Disabled
        Location-id : 100
        Reg-id : cue31
        Reg-password : (Not displayed)
        Retry-interval : 2 minute(s)
Secondary messaging gateway :
        192.0.2.21
        nat http 10.1.3.150 (80)
        nat vpim 192.0.2.23 (9925)
        Status : Registered (Wed Sep 19 18:04:45 PDT 2007)
        Reg-expiration : Thu Sep 20 18:04:45 PDT 2007
        Default route : Disabled
        Location-id : 101
        Reg-id : cue32
        Reg-password : (Not displayed)
        Retry-interval : 2 minute(s)
se-10-0-0-0> write memory
Manually Registering a Cisco Unity Express Endpoint

If you want to add a Cisco Unity Express endpoint to your Cisco UMG system, and

•it is running Cisco Unity Express 3.0 or earlier versions, or

•you want to avoid autoregistration activity with an endpoint running Cisco Unity Express 3.1 and later versions,

you must manually provision it from Cisco UMG.

Configure the endpoint following the instructions in the Cisco Unity Express documentation. Reproduced below is the relevant section of it, "Configuring Network Locations" from the Cisco Unity Express 2.3 CLI Administrator Guide. This is for orientation only.

Note You must perform the steps only if the endpoint has never undergone initial configuration - if the endpoint is already in operation, you will already have done all this.

SUMMARY STEPS

1. config t

2. network location-id number

3. (Optional) name location-name

4. (Optional) abbreviation name

5. email domain domain-name

6. voicemail phone-prefix digit string

7. (Optional) voicemail extension-length number [min number | max number]

8. (Optional) voicemail vpim-encoding {dynamic | G711ulaw | G726}

9. (Optional) voicemail spoken-name

10. end

Repeat Steps 2 through 10 for each remote location.

11. network local location-id number

12. end

13. show network locations configured

14. show network detail location-id number

15. show network detail local

16. show network queues

DETAILED STEPS
Command or Action

Purpose

Step 1

config t
Example:

se-10-0-0-0# config t

Enters configuration mode.

Step 2

network location-id number
Example:

se-10-0-0-0(config)# network location-id 9

Enters location configuration mode to allow you to add or modify a location.

•number—A unique numeric ID assigned to the location. This number is used to identify the location and is entered when a subscriber performs addressing functions in the TUI. The maximum length of the number is 7 digits. Cisco Unity Express supports up to 500 locations on a single system.

•To delete a location, use the no form of this command.

Step 3

name location-name
Example:

se-10-0-0-0(config-location)# name "San Jose"

(Optional) Descriptive name used to identify the location. Enclose the name in double quotes if spaces are used.

•To delete a location name description, use the no form of this command.

Step 4

abbreviation name
Example:

se-10-0-0-0(config-location)# abbreviation sjcal

(Optional) Creates an alphanumeric abbreviation for the location that is spoken to a subscriber when the subscriber performs addressing functions in the TUI. You cannot enter more than 5 characters.

•To delete an abbreviation, use the no form of this command.

Step 5

email domain domain-name
Example:

se-10-0-0-0(config-location)# email domain mycompany.com

Configures the e-mail domain name or IP address for the location. The domain name is added when sending a VPIM message to the remote location (for example, "4843000@mycompany.com"). If you do not configure a domain name or IP address, the Cisco Unity Express system at this location cannot receive network messages.

•To remove the e-mail domain name or IP address and disable networking, use the no form of this command.

Caution If you remove the e-mail domain for a network location, the system automatically disables networking from the Cisco Unity Express module to that location.
If you remove the e-mail domain for the local location, then networking on that Cisco Unity Express module is disabled.
To reenable a location, assign it a valid e-mail domain.

Step 6

voicemail phone-prefix digit-string
Example:

se-10-0-0-0(config-location)# voicemail phone-prefix 484

(Optional) Configures the phone number prefix that is added to an extension to create a VPIM address for a subscriber at the location. A prefix is required only if an e-mail domain services multiple locations and extensions between the locations are not unique. Valid values: 1 to 15 digits. Default value: empty.

•To delete a phone prefix, use the no form of this command.
Step 7
voicemail extension-length {number | min number max number}
Example:

se-10-0-0-0(config-location)# voicemail extension-length 8
se-10-0-0-0(config-location)# voicemail extension-length min 5 max 9
(Optional) Configures the voice mail extension length for the location.

•number—Configures the number of digits contained in extensions at the location.

•max number—Sets the minimum number of digits for extensions. Default value: 2.

•min number—Sets the maximum number of digits for extensions. Default value: 15.

•To remove the configuration for the number of digits for extensions, use the no form of this command.
Step 8

voicemail vpim-encoding {dynamic | G711ulaw | G726}
Example:

se-10-0-0-0(config-location)# voicemail vpim-encoding G711ulaw

(Optional) Configures the encoding method used to transfer voice-mail messages to this location.

•dynamic—Cisco Unity Express negotiates with the location to determine the encoding method

•G711ulaw—Cisco Unity Express always sends messages as G711 mu-law .wav files. Set this only if the receiving system supports G711 mu-law encoding (such as Cisco Unity).

•G726—Cisco Unity Express always sends messages as G726 (32K ADPCM). Use for low-bandwidth connections or when the system to which Cisco Unity Express is connecting does not support G711 u-law.

•Default value: dynamic.

•To return to the default value for encoding, use the no or default form of this command.

Step 9

voicemail spoken-name
Example:

se-10-0-0-0(config-location)# voicemail spoken-name

(Optional) Enables sending the spoken name of the voice-mail originator as part of the message. If the spoken name is sent, it is played as the first part of the received message. Default: enabled.

•To disable sending the spoken name, use the no form of this command.

Step 10

end
Example:

se-10-0-0-0(config-location)# end

Exits location configuration mode.

Step 11

network local location-id number
Example:

se-10-0-0-0(config)# network local location-id 1

Enables networking for the local Cisco Unity Express system identified by the location-id number.

•To delete the local location, use the no form of this command.

Caution If you delete the local network location and then save your configuration, when you reload Cisco Unity Express, the local network location will remain disabled. After Cisco Unity Express restarts, reenter the network local location-id command to reenable networking at this location.

Step 12

exit
Example:

se-10-0-0-0(config)# exit

Exits configuration mode.

Step 13

show network locations configured
Example:

se-10-0-0-0# show network locations configured

(Optional) Displays the location-id, name, abbreviation, and domain name for each configured Cisco Unity Express location.

Step 14

show network detail location-id number
Example:

se-10-0-0-0# show network detail location-id 9

(Optional) Displays network information for the specified location-id, including the number of messages sent and received.

Step 15

show network detail local
Example:

se-10-0-0-0# show network detail local

(Optional) Displays network information for the local Cisco Unity Express location, including the number of messages sent and received.

Step 16

show network queues
Example:

se-10-0-0-0# show network queues

(Optional) Displays information about messages in the outgoing queue that are to be sent from this Cisco Unity Express system. The queue information contains three displays: one for urgent job queue information, one for normal job queue information, and one for running job information.
Examples

The following examples illustrate the output from the show network commands on company Mycompany's call control system in San Jose with remote voice-mail provided by six remote Cisco Unity Express sites.
se-10-0-0-0# show network locations
ID        NAME                          ABBREV  DOMAIN
101       'San Jose'                      SJC    sjc.mycompany.com
102       'Dallas/Fort Worth'             DFW    dfw.mycompany.com
201       'Los Angeles'                   LAX    lax.mycompany.com
202       'Canada'                        CAN    can.mycompany.com
301       'Chicago'                       CHI    chi.mycompany.com
302       'New York'                      NYC    nyc.mycompany.com
401       'Bangalore'                     BAN    bang.mycompany.com                              
se-10-0-0-0# show network detail location-id 102
Name:                               Dallas/Fort Worth
Abbreviation:                       DFW
Email domain:                       dfw.mycompany.com
Minimum extension length:           2
Maximum extension length:           15
Phone prefix:                           
VPIM encoding:                       G726
Send spoken name:                    enabled
Sent msg count:                      10
Received msg count:                  110
se-10-0-0-0# show network detail local
location-id:                          101
Name:                                 San Jose
Abbreviation:                         SJC
Email domain:                         sjc.mycompany.com
Minimum extension length:             2
Maximum extension length:             15
Phone prefix:                           
VPIM encoding:                        dynamic
Send spoken name:                     enabled
The following example illustrates output from the show network queues command. The output includes the following fields:

•ID—Job ID.

•Retry—Number of times that Cisco Unity Express has tried to send this job to the remote location.

•Time—Time when the job will be resent.
se-10-0-0-0# show network queues 
Running Job Queue
=================
ID    TYPE TIME       RETRY SENDER          RECIPIENT
107   VPIM 06:13:26   20    jennifer        1001@sjc.mycompany.com
106   VPIM 06:28:25   20    jennifer        1001@sjc.mycompany.com
Urgent Job Queue
=================
ID    TYPE TIME       RETRY SENDER          RECIPIENT
123   VPIM 16:33:39   1     andy            9003@lax.mycompany.com
Normal Job Queue
=================
ID    TYPE TIME       RETRY SENDER          RECIPIENT
122   VPIM 16:33:23   1     andy            9001@lax.mycompany.com
124   VPIM 16:34:28   1     andy            9003@lax.mycompany.com
125   VPIM 16:34:57   1     andy            9002@lax.mycompany.com
126   VPIM 16:35:43   1     andy            9004@lax.mycompany.com
Verifying the Registration Status of a Cisco Unity Express 3.1 Endpoint

You can verify whether the current Cisco Unity Express 3.1 and later versions endpoint is registered with a messaging gateway, and check all the details associated with the registration - successful or otherwise - by using the show messaging-gateway command in Cisco Unity Express EXEC mode.

You can see which Cisco UMGs you have configured as its primary and secondary messaging gateways, with their respective port numbers. Indications in the status column show whether or not the endpoint has registered with the messaging gateway successfully.

Table 14 show messaging-gateway Output

AutoRegister to messaging gateway(s)

Enabled / disabled

Remote directory lookup

Enabled / disabled

with / without TUI prompt

Primary/secondary messaging gateway

IP address (port number)

Status

Registered / Not Registered

If registered, timestamp of initial registration confirmation; if not registered, reason is given as a code (see Table 15)

Default route

Enabled/ disabled

Location-id

location-id of the messaging gateway

Reg-id

Registration username the Cisco UMG expects from endpoint

Reg-password

(Not displayed)

Registration password the Cisco UMG expects from endpoint. It is never displayed.

Retry-interval

Delay in minutes before the endpoint attempts to register again. Default is 5 minutes.

Not displayed if not set.

If the endpoint has registered successfully, you will see the date and time of the initial registration in the status column. You can also check the configuration for a default routing destination for a message to a voicemail address that can be resolved by neither Cisco Unity Express nor Cisco UMG. To illustrate: if you give a phone number that cannot be found in a Cisco Unity Express local search or in a Cisco UMG remote lookup, the message will be forwarded to that default route destination.

If the endpoint has not registered successful, the reason for the failure will be displayed in the status column.

ï

Table 15 show messaging-gateway: Status Codes

Code

Meaning

Registered

Not registered

Autoregistration is not enabled

Not configured

Not registered (general error)

Autoregistration failed due to an error other than those specified in this table.

Not registered (connection timeout)

Connection timed out

Not registered (authentication failed)

Authentication failed

Not registered (link is down)

Link is down

Not registered (location is forbidden)

The Cisco Unity Express endpoint with that location-id has been blocked by Cisco UMG and is thus is not allowed to register (for instructions on how to prevent an endpoint from registering, see "Configuring Endpoint Autoregistration Support" on page 28).

Not Registered (duplicated location)

The Cisco Unity Express location ID is not globally unique: there is another entity in the system with the same location-id.

Not Registered (invalid configuration)

General configuration error such as the secondary messaging gateway location ID not being configured on the primary messaging gateway.

Not Registered (manually de-registered)

An intermediate state to indicate manually triggered re-registration, for example, the messaging gateway's access information being updated.

Enabling or Disabling Remote Lookup, With or Without TUI Confirmation

Enabling Remote Directory Lookup Without TUI Prompt

When you enable autoregistration by issuing the messaging-gateway registration command on a Cisco Unity Express 3.1 and later versions endpoint, you also enable the endpoint to do remote lookup automatically. This includes a short prompt informing subscribers that the lookup may take some time.

Enabling Remote Directory Lookup With TUI Prompt

Enabling the remote directory lookup feature does not also enable the directory lookup confirmation in the TUI flow feature, in which Cisco Unity Express 3.1 and later versions gives subscribers the option to do remote lookup if there is no local match. To enable TUI directory lookup confirmation, use the config-mode command messaging-gateway directory lookup tui-prompt.

Disabling Remote Directory Lookup

To have no remote lookup at all, disable it by issuing the no messaging-gateway directory lookup command.

Note Disabling the remote directory lookup feature also disables directory lookup confirmation in the TUI flow, and conversely, enabling directory lookup confirmation in the TUI flow will also enable remote directory lookup.

Viewing Status

To view the status of these features, use the show messaging-gateway command, which displays the following output:

Remote directory lookup status:

•No--remote directory lookup is disabled

•Yes--remote directory lookup is enabled

–Enabled with TUI-prompt--TUI confirmation prompt is enabled

–Enabled without TUI-prompt--TUI confirmation prompt is disabled.

Viewing Cached and/or Configured Network Locations

To view a list of all cached remote location entries on Cisco Unity Express 3.1 and later versions, use the EXEC-mode show network locations cached command.

To list all configured remote location entries on Cisco Unity Express 3.1 and later versions, use the EXEC-mode show network locations configured command. This command replaces the old show network locations command.

Refreshing Locations

To manually refresh a cached location entry on Cisco Unity Express 3.1 and later versions, use the network location cache refresh id command in EXEC-mode. This command will not generate any response if it is performed successfully. Otherwise, an error message appears.

Setting the Expiration for Cached Locations

To set the expiration time for a cached location on Cisco Unity Express 3.1 and later versions, use the network location cache expiry int command in config-mode. The int value stands for number of days. By default, this value is set to 4. The no command will set the value back to its default value. The value is persisted by means of the nvgen method. It is not stored in the database.

Overloading a NAT Device: the Consequences for Endpoints

One endpoint can be configured to get to its primary messaging gateway with complete connectivity if:

•Two Cisco Unity Express endpoints are behind a NAT device that has only one IP address to assign --an overload situation--

•Those endpoints have two different messaging gateways configured as primary messaging gateways,

Note The other endpoint can only do HTTP-related activities (assuming proper configuration) and not the SMTP activities.