|
Cisco Unity Express Module Configuration
Mentioned in Part-1 of our Cisco Unity Express installation article, the Cisco Unity Express setup procedure is identical for ISM-SRE-300-K9 and SM-SRE-700-K9 modules. We will be using the smaller ISM-SRE-300-K9 for this article. The only notable difference in the CallManager Express configuration will be the module’s interface that connects to CallManager Express.
For the SRE-300, the module’s interface name is interface ISM0/0, whereas for the SM-SRE-700 it is service-module sm2/0. Both interfaces are GigabitEthernet, connected via each router’s internal bus.
The ISM-SRE-300-K9 module is configured with its own IP address and acts as a separate machine inside the router. Before we can begin configuring Unity Express, preinstalled by Cisco, we must configure IP connectivity with the router so we can then access the ISM-SRE-300-K9 module and initialize the Unity Express setup.
When physically installing an SRE module, CCME will automatically make two additional interfaces available in its configuration. For the ISM-SRE-300-K9, they are interface ISM0/0 and interface ISM0/1, whereas for the SM-SRE-700 they are interface SM2/0 and interface SM2/1.
First step is to configure IP connectivity between the router (CCME) and Unity Express. This is achieved by configuring interface ISM0/0 with an IP address (ISM-SRE-300-K9) or interface SM2/0 for the SM-SRE-700.
Our CCME router has two IP addresses, 192.168.9.5/24 (Data VLAN) and 192.168.10.5/24 (Voice VLAN). When configuring an IP address on Unity Express, there is the choice of assigning one part of the existing network(s) (192.168.9.0 or 192.168.10.0) or one that is on a completely different network.
It is a common practice to configure Unity Express with an IP address that is part of the Voice VLAN, that is, 192.168.10.0/24 in our example:
interface ISM0/0
description Unity-Express-Module
ip unnumbered GigabitEthernet0/0.2
ip virtual-reassembly in
service-module ip address 192.168.10.10 255.255.255.0
!Application: CUE Running on ISM
service-module ip default-gateway 192.168.10.5
In the above configuration commands, we’ve configured our Unity Express module with IP address 192.168.10.10 and a default-gateway of 192.168.10.5 (CCME’s Voice VLAN IP address), this is because the Unity Express module is physically connected to our router’s internal interfaces (ISM) and therefore must use one of the router’s IP interfaces as a default-gateway.
The ip unnumbered <interface> command allows the Cisco Unity Express module to use a network subnet IP address associated with a specific router egress port such as GigabitEthernet0/0.2. This configuration method requires a static route to the service-engine interface. The router interface associated with the Cisco Unity Express interface (GigabitEthernet 0/0.2) must be in an "up" state at all times for communication between the router and module.
At this point we should note that GigabitEthernet0/0 is configured as a trunk link with our switch. This configuration method is known as ‘Router on a Stick’ and allows all configured VLANs to pass through a single interface. For more information on this configuration method, please refer to our Router-on-a-Stick article.
Following is the configuration of our GigabitEthernet 0/0 interface:
!
interface GigabitEthernet0/0
no ip address
duplex auto
speed auto
!
interface GigabitEthernet0/0.1
description Data-VLAN
encapsulation dot1Q 1 native
ip address 192.168.9.5 255.255.255.0
!
interface GigabitEthernet0/0.2
description Voice-VLAN
encapsulation dot1Q 2
ip address 192.168.10.5 255.255.255.0
!
Next step is to create a static route to Unity Express’s IP address via the internal service module (ISM0/0):
2911-CCME (config)# ip route 192.168.10.10 255.255.255.255 ISM0/0
At this point, we should be able to ping Unity Express’s IP address:
2911-CCME# ping 192.168.10.10
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.10.10, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
CallManager Express - Telephony-Service Configuration
Next step is to configure our CallManager Express web-based administrator user (if not already configured), voicemail extension on CallManager Express, voicemail dial-peer and Message Waiting Indicator (MWI) extensions used to enable/disable the red light (message waiting indicator) on the IP phone when there is a message waiting in the user’s voice mailbox:
2911-CCME(config)# telephony-service
2911-CCME(config-telephony)# web admin system name administrator password firewallcx
2911-CCME(config-telephony)# voicemail 810
2911-CCME(config-telephony)# create cnf
Creating CNF files
2911-CCME(config-telephony)# exit
2911-CCME(config)#
2911-CCME(config)# dial-peer voice 101 voip
2911-CCME(config-dial-peer)# description Unity Express - VoiceMail
2911-CCME(config-dial-peer)# destination-pattern 810
2911-CCME(config-dial-peer)# session protocol sipv2
2911-CCME(config-dial-peer)# session target ipv4:192.168.10.10
2911-CCME(config-dial-peer)# dtmf-relay rtp-nte
2911-CCME(config-dial-peer)# codec g711ulaw
2911-CCME(config-dial-peer)# no vad
2911-CCME(config-dial-peer)# exit
2911-CCME(config)#
2911-CCME(config)# ephone-dn 1
2911-CCME(config-ephone-dn)# number 800... no-reg both
2911-CCME(config-ephone-dn)# mwi on
2911-CCME(config-ephone-dn)# exit
2911-CCME(config)#ephone-dn 2
2911-CCME(config-ephone-dn)# number 801... no-reg both
2911-CCME(config-ephone-dn)# mwi off
2911-CCME(config-ephone-dn)#exit
2911-CCME(config)#
|