Table Of Contents

Entering and Exiting the Command Environment

EXEC and Configuration Modes

Entering the Command Environment

Prerequisites

Exiting the Command Environment

Entering and Exiting the Command Environment

---

Last updated: April 13, 2010

This chapter describes the procedures for entering and exiting the Cisco Unified Messaging Gateway command environment, where Cisco UMG configuration commands are executed. The following sections describe these procedures:

•EXEC and Configuration Modes

•Entering the Command Environment

•Exiting the Command Environment

•Exiting the Command Environment

EXEC and Configuration Modes

Cisco UMG uses the network module's CLI, which you access through the host-router console. The network module CLI is similar to the router CLI:

Similarities

Standard Cisco IOS navigation and command-completion conventions apply (for example, ? lists options, TAB completes a command, and | directs show command output).

Differences

Standard command names and options do not necessarily apply. A notable example is the command for accessing global configuration mode: the Cisco IOS command is configure terminal; the network module command is config terminal or config t.

Cisco UMG employs a last-one-wins rule. For example, if George and Frank both try to set the IP address for the same entity at the same time, the system starts and completes one operation before it starts the next. The last IP address set is the final result.

The Cisco UMG command modes, privileged EXEC, configuration, registration configuration, list configuration, endpoint configuration, and NAT configuration operate similarly to the EXEC and configuration modes in the Cisco IOS CLI.

After you enter configuration mode, all the CLI commands can be used in the no form, for example, no network messaging gateway location-id { hostname | ip-address }. This command deletes the specified peer messaging gateway.

Entering the Command Environment

After the Cisco UMG network module is installed, IP connectivity with it established, and the software active, use this procedure to enter the command environment.

Prerequisites

The following information is required to enter the Cisco UMG command environment:

•IP address of the router that contains the Cisco UMG module

•Username and password to log in to the router

•Slot in the router where the Cisco UMG network module resides

•Port through which the router communicates with Cisco UMG

SUMMARY STEPS

1. Open a telnet session.

2. telnet ip-address

3. Enter the username and password of the router.

4. service-module integrated-Service-Engine slot/port session

5. (Optional) enable

DETAILED STEPS

	Command or Action	Explanation
Step 1	Open a telnet session.	Use a DOS window, a secure shell, or a software emulation tool such as Reflection.
Step 2	telnet ip-address Example: C:\>telnet 192.0.2.22	Specifies the IP address of Cisco UMG's host router.
Step 3	Username: Password:	Enter your username and password for the router.
Step 4	service-module integrated-Service-Engine slot/port session Example: Router# service-module integrated-Service-Engine 1/0 session	Enters the Cisco UMG command environment using the module located in slot and port. The first time you do this, the prompt changes to "se" with the IP address of the Cisco UMG module. After that, the prompt is the hostname you give to the module. If entering ip-address slot/port elicits the response "Connection refused by remote host" enter the command service-module integrated Service-Engine slot/port session clear and retry this step.
Step 5	enable Example: se-10-0-0-0# enable	Enters Cisco UMG EXEC mode. You are ready to begin configuration.

Exiting the Command Environment

To leave the Cisco UMG command environment and return to the router command environment, in Cisco UMG EXEC mode enter the exit command once to exit EXEC mode, and again to exit the application.

The following example illustrates the exit procedure:

se-10-0-0-0# exit

se-10-0-0-0# exit

router-prompt#