CCIE Voice Lab Preparation Notes #2

SRST
There are four SRST scenarios:

• SRST configuration for MGCP gateways
• SRST for H.323 gateways
• SRST for SIP gateways
• SRST on CME

1. MGCP Gateway

• Enables fallback for MGCP gateway
  router(config)#ccm-manager fallback-mgcp
• Enters SRST configuration mode
  router(config)#call-manager-fallback
• Configure Basic SRST settings
  router(config-cm-fallback)#max-dn value [dual-line] [preference preference-order]
  router(config-cm-fallback)#max-ephone value
  router(config-cm-fallback)#ip source-address ip-address
  router(config-cm-fallback)#system message primary message
  router(config-cm-fallback)#user-local country-code
  router(config-cm-fallback)#time-format [12|24]
  router(config-cm-fallback)#date-format format
  router(config-cm-fallback)#moh filename
  router(config-cm-fallback)#max-conferences value
  router(config-cm-fallback)#call-forward reason number
  router(config-cm-fallback)#voicemail number
  router(config-cm-fallback)#secondary-dialtone digit-string
• Configure the MGCP gateway as SRST reference in CUCM.
• Assign the SRST reference to IP phones by configuring corresponding device pool.
• The last step is to configure H.323 incoming and outgoing dial peers for SRST.
  

Additionally, you can use the router to provide multicast MOH to IP phones.

router(config)#ccm-manager music-on-hold

router(config)#call-manager-fallback

router(config-cm-fallback)#moh filename

router(config-cm-fallback)#multicast moh multicast-address route address-to-send-packets-to

2. SRST for H.323

On H.323 gateways, when the WAN link fails, active calls from Cisco Unified IP phones to PSTN are not maintained by default. Call preservation may work with 'no h225 timeout keepalive' command under 'voice service voip' 'h323' configuration mode.

3. SRST for SIP Gateway

SIP SRST feature is using Back-to-Back User Agent Mode.

By default, when configuring 'voice register global', it is SRST mode.

4. SRST on CME

router(config)#telephony-service

router(config-telephony)#srst mode auto-provision {all|dn|none}

Use none when configuring SRST with CUCM.

CCIE Voice Lab Preparation Notes #1

Understanding COR on Cisco IOS Gateways

• Calling privileges on IOS gateways are implemented using class of restriction (COR).
• COR lists contain CORs and are used to control call routing.
• COR lists are assigned to dial peers (Incoming COR List & Outgoing COR List).
• For each call, the incoming COR list is matched against the outgoing COR list. If the outgoing COR list is a subset of the incoming COR list, or no incoming COR list is configured, call is routed.

A COR is the building block of calling privileges. A COR list contains multiple CORs and is bound to dial peers. For CallManager Express, COR is applied to ephone-dns. For SRST, COR is applied to number range.

COR only takes in place when both incoming COR list and outgoing COR list are applied.

Normally, when configuring Outgoing COR list, we assign one COR to one Outgoing COR list, and the Outgoing COR list is analogous to the concept of Partition in CUCM, and the Incoming COR list is analogous to Calling Search Space.

Configuration Commands:

First, you need to define COR:

router(config)#dial-peer cor custom

router(config-dp-cor)#name COR-name

Then, you need to configure COR lists:

router(config)#dial-peer cor list list-name

router(config-dp-corlist)#member name

Lastly, you need to apply COR lists to incoming or outgoing dial-peers or ephone-dns.

router(config-dial-peer)#corlist incoming | outgoing list-name

router(config-ephone-dn)#corlist incoming | outgoing list-name

To apply COR lists to SRST ephones:

router(config-cm-fallback)#cor {incoming | outgoing} cor-list-name {cor-list-tag starting-number - ending-number | default}

CME Conference Resource

1. Configure DSP as SCCP device and register to CME.
voice-card 0
no dspfarm
dsp service dspfarm

sccp local voice-interface
sccp ccm cme-address identifier 1 version 7.0+
sccp
sccp ccm group 1
associate ccm 1 priority 1
associate profile 1 register CONF

dspfarm profile 1
associate application sccp
maximum session 2
no shut

telephony-service
sdspfarm unit 2
sdspfarm tag 1 CONF
conference hardware

2. Configure ephone-dn for Ad-hoc and Meet-me conference
ephone-dn 200 octo-line
number 6666
conference ad-hoc

ephone-dn 201 octo-line
number 7777
conference meetme

3. Change ephone-template to include conf button for connected status.

CME Night Service

The instructions from CME system admin guide is not complete when configuring Night Service. Below is a brief guide on how to enable the feature on CME.

1. The first step is to define night service hours under telephony-service configuration mode.
telephony-service
night-service day Sun 18:00 23:59
night-service day ...

2. The second step is to utilize night service.
ephone-dn 1
call-forward night-service ....

CUE Licensing

CUE has two types of licensing, the license for core application, and the license for IVR.

For core application license, you can choose between CME and CM. You can have either CME or CM, but not both.

Difference between H245 Signal and H245 Alphanumaric

H245 Signal and H245 Alphanumaric are two DTMF relay methods for h.323 dial peers. They are both out of band DTMF relay methods.

H245 Signal transmits two events, the start and the stop when holding the key and releasing the key. In another word, it records the duration. It is useful in calling card scenario.

H245 Alphanumaric only sends one event, and it has the default during period for 200ms.

The Cisco recommended DTMF relay method is H245 Alphanumaric.

CUE Upgrade from Version 1 to Version 7.0.3

I just bought a Cisco Unity Express module from ebay (NM-CUE), and it arrived this morning. I never touched it before. I connected it to a Cisco 3845 ISR.

After loading the IOS, I issued 'show version', and there is a service engine found. Using 'show ip interface brief' displays the new service engine interface.

So I configured an IP address on the service engine interface, and then under service engine interface configuration mode, I configured another ip address within same subnet of the service engine interface, pointing the default gateway address as the service engine interface address, and then enabled the interface.

Then I issued 'service-module service-engine slot/port session' command to switch the console to NM-CUE. Using 'show software version', I found out the version of CUE is 1.0.7. The version required on CCIE Voice blueprint is version 7.

Further investigations show that there are several ways for the upgrade, but after some testing, I realize that to upgrade from version 1 to version 7, the only way is to upgrade through boot helper.

Before doing the upgrade, some preparation work needs to be done. First is to download the related installation pack, language files and licenses for version 7 (I downloaded version 7.0.3).

FTP server and TFTP server need to be setup. TFTP is used to upgrade the boot helper, and FTP server is used to upgrade the software, language files and licenses. I simply put all files under one directory and point both ftp and tftp path to this directory.

Reload the CUE and type '***' to get into boot helper when it is prompted to do so.

Input 'config', and configure the related information, like ip address, subnet mask, default gateway, tftp server address and boot helper file name. When config is finished, type 'boot helper', and the boot helper upgrade is started. When finished, choose '1' to install software, and type the related package name, ftp server address, username and password. When prompted, select the language file to install.

When it is done, you can have some basic initialization configurations.

Using 'software install clean url' command to install the license files.

:-D I now have version 7.0.3 installed on Unity Express.