h1

Reestablishing a Broken CallManager Cluster SQL Subscription with Cisco CallManager (Link)

October 30, 2007

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00801d11a6.shtml

h1

Cisco Unified CallManager 4.1 TCP and UDP Port Usage (Link)

October 30, 2007

Cisco Unified CallManager 4.1 TCP and UDP Port Usage (Revised 8/28/2006)

h1

CCM and Unity Passwords

October 29, 2007

CallManager:
To access the CCM Password Changer tool, open a DOS window (Start > Run > type cmd), enter CCMPwdChanger, and press Enter.

Unity:
To gain appropriate rights to access the SA page, you must run the GrantUnityAccess utility. This tool is located at C:\commserver\grantunityaccess.exe.

h1

CME and CUE Intergration using a 2811 with PVDM2

October 26, 2007

Cisco Unity Express only supports G711 codec which means calls placed from a remote site using another codec (i.e. G729) will need to be transcoded on the CME router. The example below is using a 2811 (IOS 12.4T) with a PVDM2-32 installed. Note that in the real CCIE lab a NM-HDV will be used which is configured differently than below.

R2#show version | include IOS
Cisco IOS Software, 2800 Software (C2800NM-ADVENTERPRISEK9_IVS-M), Version 12.4(11)T2, RELEASE SOFTWARE (fc4)
R2#show inventory | include PVDM
NAME: “PVDMII DSP SIMM with Two DSPs on Slot 0 SubSlot 4”, DESCR: “PVDMII DSP SIMM with Two DSPs”
PID: PVDM2-32 , VID: NA , SN: FOC09312XE2
R2#

! Enable the DSP Farm Services
voice-card 0
no dspfarm
dsp services dspfarm
!
! Permit h323 to SIP as the communication from CME to CUE is SIP
voice service voip
allow-connections h323 to sip
!
! Enable SCCP and determine the interface used to register
sccp local FastEthernet0/0.120
sccp ccm 177.1.120.254 identifier 1
sccp
!
! Defines the CCM group and enters SCCP configuration mode
sccp ccm group 1
associate ccm 1 priority 1
associate profile 1 register mta001a2f7e9300 <- MTA + MAC Address of Fa0/0.120
!
! Define the DSPFarm profile and specify transcoding
! Next specify the codecs that will be transcoded along with the maximum sessions
! Now associate it with the SCCP application
dspfarm profile 1 transcode
codec g711ulaw
codec g729ar8
maximum sessions 5
associate application SCCP
!
!
dial-peer voice 2999 voip
destination-pattern 2999
session protocol sipv2
session target ipv4:177.1.120.2
dtmf-relay sip-notify
codec g711ulaw
no vad
!
! Finally specify the number of units and transcoding sessions along with binding the session to CME
telephony-service
max-ephones 10
max-dn 100
ip source-address 177.1.120.254 port 2000
sdspfarm units 5
sdspfarm transcode sessions 5
sdspfarm tag 1 mta001a2f7e9300
cnf-file location flash:
voicemail 2999
!
!
ephone-dn 1 dual-line
number 2001
call-forward busy 2999
call-forward noan 2999 timeout 4
!
!
ephone-dn 99
number 8000….
mwi on
!
ephone-dn 100
number 8001….
mwi off
!
!
ephone 1
device-security-mode none
description R2 Phone 1
mac-address 0014.A8AC.D73F
fastdial 1 2002 name Phone 2
speed-dial 1 2002 label “R2 Phone 2”
type 7960
button 1:1 2:11

R2#show sccp
SCCP Admin State: UP
Gateway IP Address: 177.1.120.254, Port Number: 2000
IP Precedence: 5
User Masked Codec list: None
Call Manager: 177.1.120.254, Port Number: 2000
Priority: N/A, Version: 3.1, Identifier: 1

Transcoding Oper State: ACTIVE – Cause Code: NONE
Active Call Manager: 177.1.120.254, Port Number: 2000
TCP Link Status: CONNECTED, Profile Identifier: 1
Reported Max Streams: 10, Reported Max OOS Streams: 0
Supported Codec: g729ar8, Maximum Packetization Period: 60
Supported Codec: g711ulaw, Maximum Packetization Period: 30
Supported Codec: rfc2833 dtmf, Maximum Packetization Period: 30
Supported Codec: rfc2833 pass-thru, Maximum Packetization Period: 30
Supported Codec: inband-dtmf to rfc2833 conversion, Maximum Packetization Period: 30

R2#show sdspfarm units

mtp-1 Device:mta001a2f7e9300 TCP socket:[1] REGISTERED
actual_stream:4 max_stream 10 IP:177.1.120.254 19843 MTP YOKO keepalive 39
Supported codec: G711Ulaw
G729a

max-mtps:5, max-streams:10, alloc-streams:10, act-streams:6
R2#

Call is placed from remote site and forwarded to CUE VM

R2#show voip rtp connections
VoIP RTP active connections :
No. CallId dstCallId LocalRTP RmtRTP LocalIP RemoteIP
1 517 519 18058 31918 177.1.0.2 177.1.30.100
2 519 517 18566 16908 177.1.120.254 177.1.120.2
3 521 522 18562 2000 177.1.120.254 177.1.120.254
4 523 522 19370 2000 177.1.120.254 177.1.120.254
Found 4 active RTP connections

R2#show sdspfarm sessions callID 519
Stream-ID:4, srcCall-ID:519, codec:G711Ulaw64k , dur:20ms, vad:0, dstCall-ID:517, confID:3, mtp:2
Peer Stream-ID: 3, srcCall-ID:517, codec:G729 , dur:20ms, vad:0, dstCall-ID:519, confID:3, mtp:2
R2#

h1

CallManager Regions

October 26, 2007

Regions define the codec used within the region and to other regions on a per region basis.  The two most common codecs used are G711 (80kbps) and G729 (24kbps).

Regions are assigned to devices through the use of device pools.

Regions are used in conjunction with locations for Call Admission Control.

h1

CallManager Locations

October 26, 2007

Locations are using to limit the amount of bandwidth to and from a particular location.  G711 calls consume 80kbps of bandwidth per call and G729 consume 24kbps per call. Bandwidth within a location is assumed to be unlimited.

When the location bandwidth is exceeded additional calls to or from the location with receive a reorder tone and a “Not Enough Bandwidth” message will be displayed on the phone attempting to make the call.  The text of this message can be changed by altering the “Out-of-Bandwidth Text” in the Service Parameters Configuration for CallManager.

Note that locations are applied at the device level.  This can make CAC tedious to implement on a large scale unless BAT is used to apply locations to the devices.  In the Voice CCIE lab BAT can be a real big time saver.

Locations are used in conjunction with regions for Call Admission Control (CAC).  The region will determine the codec settings for calls within a region and to other regions.

h1

Enabling Dependency Records in CallManager 4.1(3)

October 26, 2007

It is recommend for those who aren’t very familiar with CCM or are just really learning CCM to enable dependency records to help understand the relationships between components within CCM.  In CCM 3.3(3) dependency records were enabled by default but due to the additional CPU resources taken by the dependency records feature they are disabled by default in CCM 4.1(3).

To enable them go to System -> Enterprise Parameters  -> CCMAdmin Parameters -> Enable Dependency Records = True

From CCM:

Enable Dependency Records : This parameter determines whether to display dependency records in Cisco CallManager Administration. Valid values specify True (display dependency records) or False (do not display dependency records).
This is a required field.
Default: false.
Displaying dependency records leads to high CPU usage and takes some time because it executes in a low-priority thread. If you monitor CPU usage, you might see high CPU usage alarms. To avoid possible performance issues, display dependency records only during off-peak hours or during the next maintenance window. Close and reopen the web browser for the parameter change to take effect.

h1

Important Note Regarding CME MOH Testing

October 24, 2007

* IP phones do not support multicast at 224.x.x.x addresses.

* Cisco Unified CME 3.3 and earlier versions do not support MOH for local Cisco Unified CME phones that are on hold with other Cisco Unified CME phones; these parties hear a periodic repeating tone instead.

h1

Troubleshooting the CUE MWI

October 24, 2007

Troubleshooting something as simple as a MWI not working properly can take up a lot of time in the real lab.  Running into small problems like this during your preparation and successfully troubleshooting them can definitely save time in the real lab.

http://www.cisco.com/en/US/products/sw/voicesw/ps5520/products_tech_note09186a008027fa9f.shtml#mwi_exp

h1

CCIE Voice Lab Cataylst 6500 Configuration

October 22, 2007

Below is a link to the CatOS needed for the current CCIE Voice Lab.

Catalyst 6500 Series Software Configuration Guide, 7.6

http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/catos/7.x/configuration/guide/confg_gd.html