Cisco Unity Connection Integrating with CM Express Using SCCP.

Posted: Saturday, December 21, 2013 by Mahmoud Ramadan Ali in Labels:
0

-You can integrate Cisco Unified Communications Manager Express (CME) to Cisco Unity Connection using SCCP or SIP. In the following pages, the SCCP integration is explored from the perspective of CME; although, an overview of the Cisco Unity Connection integration is discussed. 

-I'm using the demo version of CUC which is limited to only two voice mail ports but sure you can increase the number of ports depending on your CUC license.  
  
Cisco Unified CME Integration Configuration:
CME Baisc configuration.
-The IOS Configuration in CME begins with ensuring that the IP phones are configured and registered. Cisco Unified CM uses the telephony-service to perform the global configurations for CME.
-The voicemail 2000 command defines the configuration of the Messages button on the registered phones. In this case, the pilot number of 2000 is configured; therefore, the phone attempts to dial 2000 when the Messages button is selected. 
CME(config)#telephony-service
CME(config-telephony)# max-ephones 10
CME(config-telephony)# max-dn 10
CME(config-telephony)# ip source-address 192.168.1.200 port 2000
CME(config-telephony)# voicemail 2000 
CME Dial Peer Configuration.
-Even though a user presses the Message button and the attempt is made to dial 2000 automatically, there must still be a configured dial plan on CME. You accomplish this by using the dial-peer configuration command.
-Dual tone multifrequency (DTMF) relay is configured to provide out-of-band relay of tones using the H.245 signaling channel, as opposed to the audio channel. In this way, the correct tones are transmitted end-to-end.
CME(config)#dial-peer voice 1 voip
CME(config-dial-peer)# destination-pattern 2000
CME(config-dial-peer)#session target ipv4:192.168.1.50
CME(config-dial-peer)#dtmf-relay h245-alphanumeric
Configure the Voice Messaging Port Extensions.
-The ephone-dn command configures specific directory numbers.In our example i'm using only the first channel of each DN for  voice messaging.
-The "huntstop channel" reserve the second ephone-dn channel for supervised transfers.
-The " preference " command sets the dial-peer preference for the extension to hunt trough the port group if the target port is busy.
-The "huntstop" disables hunting on my last messaging port since it's considered to be the last resort and if it's the user will hear a busy signal when accessing his voice mail.
CME(config)#ephone-dn 3 dual-line
CME(config-ephone-dn)#number 2000
CME(config-ephone-dn)#name VOICE-MSG-SYS
CME(config-ephone-dn)#huntstop channel
CME(config-ephone-dn)#no huntstop
CME(config-ephone-dn)#preference 0
CME(config-ephone-dn)#exit
CME(config)#ephone-dn 4 dual-line
CME(config-ephone-dn)#number 2000
CME(config-ephone-dn)#name VOICE-MSG-SYS 
CME(config-ephone-dn)#huntstop channel
CME(config-ephone-dn)#preference 1
CME(config-ephone-dn)#huntstop 
Associate the Voice Messaging Ports to the phone number.
-The ephone 3 and ephone 4 configurations associate two voicemail ports to the directory number used for the voice-messaging integration. In this case, the vm-device-id, CME-VI1 is associated with ephone 3, whereas CMEVI2 is associated with ephone 4 through the configuration of the button 1:3 command. Both ephone-dn 3 and ephone-dn4 are configured with the voicemail pilot of 2000. 
-The "CME-VI" prefix will be configured in CUC as the device name prefix.
CME(config)#ephone 2
CME(config-ephone)#vm-device-id CME-VI1
CME(config-ephone)#button 1:3
CME(config-ephone)#exit
CME(config)#ephone 3
CME(config-ephone)# vm-device-id CME-VI2
CME(config-ephone)# button 1:4
Configure a Directory Number For MWI Notification.
-The ephone-dn 5 and ephone-dn 6 configurations designate the MWI On and MWI Off respectively using the number command. This configuration must match the MWI configured under the port group in Cisco Unity Connection Administration.
CME(config)#ephone-dn 5
CME(config-ephone-dn)#number 5000
CME(config-ephone-dn)#mwi on
CME(config-ephone-dn)#exit
CME(config)#ephone-dn 6
CME(config-ephone-dn)#number 6000
CME(config-ephone-dn)#mwi off
Tip:The WMI DNs are NOT counted as messaging ports.

Cisco Unity Connection Integration Configuration.
Configure a New Phone System.
-Configure a new phone system in Cisco Unity Connection Administration for Cisco Unified CME.

Configure a New Port Group.
-In the "Related Links"click "Add Port Group" and choose the "Phone System" you have configured before also the "Port Group Type" is "SCCP".
-Choose a descroptive name for the "Port Group" and configure the "Device Name Prefix" the same as the prefix used in CME also configure the WMI On/Off port numbers respectively to match your CME configuration.
-The "IP Address" will be your CME SCCP listing IP,do NOT use the "Host Name" just to avoid any DNS resolution issues.

Configure a New Ports.
-Set the "Number of Ports" to two and choose you "Phone System" and "Port Group" configuration.
-The "Port Behavior" settings will be vary depending on your configuration but i recommend you to check all of them.
 Reset the Port Group and Verify Your Configuration.
-In the "Port Group" configuration page click the "Reset" Button even if it says that the reset is NOT required to register the voice ports with CME.
-Use the "show ephone registered" command to veritfy the voice messaging ports registration proess.
CME#show ephone registered
ephone-2 Device:CME-VI1 TCP socket:[2] activeLine:0 REGISTERED in SCCP ver 18 and Server in ver 5
mediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0
IP:192.168.1.50 36807 Unity Voice Port  keepalive 43 max_line 1
button 1: dn 3  number 2000 CH1   IDLE         CH2   IDLE
ephone-3 Device:CME-VI2 TCP socket:[4] activeLine:0 REGISTERED in SCCP ver 18 and Server in ver 5
mediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0
IP:192.168.1.50 36808 Unity Voice Port  keepalive 43 max_line 1
button 1: dn 4  number 2000 CH1   IDLE         CH2   IDLE
Summary:NOT bad isn't it?!...CME and CUC integration could be achieved using SCCP or SIP....SCCP requires much configuration steps more than SIP but in both cases your next step will be creating the CUC users whether manully or from LDAP...i hope you enjoyed the post i personally enjoyed it!.