Wednesday, December 10, 2014

Cisco CME Fast Track Feature


This feature is introduced in CME 10.0 - 15.3(3)M. It provides support for new SIP phone device without changing the IOS version .

Before

In the subsequent CME releases, these new phones would be added into the list of supported phones for CME with the necessary code changes. Currently all the new SIP phone devices which are not yet supported on CME can register to CME as 3rd party SIP phones and get generic SIP line features like Call Hold, Call Resume etc.

After

Fast track support would provide a new configuration utility to provide the phone characteristics of a new SIP phone device. As part of this feature, CME  code would be enhanced to retrieve the phone characteristics of a new SIP phone device and allow the registration of these new SIP phone devices. With this new configuration utility, existing SIP features on CME  would be made available to the new SIP phone devices.

Some new phones do not add new features, but just change the display, change the button layout, etc. Some new phones are created due to cost cutting to provide fewer features or provide the same features with different hardware. These kinds of new phone support which do not change software protocols, do not need CME new feature support are the targets of this feature. To take advantage of the IOS rich parser capability, the configuration will be done using CLI commands.

Forward Compatibility
New SIP phone model is configured using the Fast-Track configuration approach . When CME is upgraded to a later version which has the built-in support for this new SIP phone model , the Fast-Track configuration for the SIP phone model gets removed automatically

If the CME is downgraded to version which does not have the built-in support then the Fast-Track configuration should be applied again manually.

Restrictions:
  •  Provisioning of new SIP Phones is supported using IOS CLI commands only, No GUI and SNMP support.
  •  Only XML format of phone configuration file will be supported. Text format will not be supported by this feature.
  •  Cisco Legend phones ATA,7905,7912 supports only TEXT, such new phone types are not supported.
  •  Only built in supported phones can be used as reference phone while configuring a new SIP phone model
  •  New phones having a "new call flow" , "new message flow" or "new configuration file format" that are not supported in CME will not be supported by this feature as it needs code changes at CME.

Configuration

configure terminal
voice register pool-type pool-type
 addons max-addon count
 description string
 gsm-support
 num-lines number
 phoneload-support
 reference-pooltype pool-type
 telnet-support
 transport transport-type
 xml-config xml-tag value
exit


Command or Action
Purpose
Step 1
enable
 
Router> enable
Enables the privileged EXEC mode. Enter your password if prompted.
Step 2
configure terminal
 
Router# configure terminal
Enters the global configuration mode.
Step 3
voice register pool-type
 
Router(config)# voice register pool-type 9900

Enters the voice register pool configuration mode and creates a pool configuration for a Cisco Unified SIP IP phone in Cisco Unified CME.
If the new phone type is an existing phone that is supported on Cisco Unified CME release, you get the following error message:
ERROR: 8945 is built-in phonemodel, cannot be changed
Step 4
addons max-addons
 
Router(config-register-pooltype)# addons 3
Defines the maximum number of add-on modules supported in Cisco Unified SIP IP phones.
  • max-addons —The maximum allowed value is 3. The configured add-on modules can be used while defining the pool for the new SIP phone model using the existing type command as shown below:
type [addon 1 module-type [2 module-type]]
Step 5
description string
 
Router(config-register-pooltype)# description TEST PHON
Defines the description string for the new phone type.
Step 6
gsm-support
 
Router(config-register-pooltype)# gsm-support
Defines phone support for Global System for Mobile Communications (GSM) support.
Step 7
num-lines max-lines
 
Router(config-register-pooltype)# num-lines 12
Defines the maximum number of lines supported by the new phone.
  • max-lines —If this parameter is not configured, the default value 1 is used.
Step 8
Phoneload-support
 
Router(config-register-pooltype)# Phoneload-support
Defines phone support for firmware download from Cisco Unified CME. You can use the load command in the voice register global mode to configure the corresponding phone load for the new phone type if it supports phone load.
Step 9
telnet-support
 
Router(config-register-pooltype)# telnet-support
Defines phone support for Telnet access.
Step 10
transport { udp | TCP }
 
Router(config-register-pooltype)# transport TCp
Defines the default transport type supported by the new phone.
If this parameter is not configured, UDP is used as the default value. The session-transport command configured at the voice register pool takes priority over this configuration.
Step 11
Xml-config {maxNumCalls | busyTrigger | custom}
 
Router(config-register-pooltype)#xml-config busyTrigger 2
Router(config-register-pooltype)#xml-config maxNumCalls 4
Router(config-register-pooltype)#xml-config custom 1
Defines the phone-specific XML tags to be used in the configuration file.
  • maxNumCalls— Defines the maximum number of calls allowed per line.
  • busyTrigger— Defines the number of calls that triggers Call Forward Busy per line on the SIP phone.
  • custom—Defines custom XML tags which can be appended at the end of the phone specific CNF file.
These parameters are used while generating the configuration profile file. CUCME does not use these configuration values for any other purpose.
Step 12
exit
 
Router(config-register-pooltype)# exit
Exits the voice register-pooltype configuration mode.
Step 13
end
 
Router(config)# end


Cisco Approved Configuration for 7800 Series Phones

New Cisco Unified SIP Phone model
Recommended Fast-track configuration
Cisco Unified CME
Versions supported
Comments
7821
voice register pool-type 7821
description Cisco IP Phone 7821
reference-pooltype 6921
CUCME 10.0 (15.3(3)M) to CUCME 10.5 (15.4(3)M)
7821 phone is a hardware revision of the earlier 6921 phone.
7841
voice register pool-type 7841
description Cisco IP Phone 7841
reference-pooltype 6941
CUCME 10.0 (15.3(3)M) to CUCME 10.5 (15.4(3)M)
7841 phone is a hardware revision of the earlier 6941 phone
7861
voice register pool-type 7861
description Cisco IP Phone 7861
reference-pooltype 6961
num-lines 16
CUCME 10.0 (15.3(3)M) to CUCME 10.5 (15.4(3)M)
7861 phone is a hardware revision of the earlier 6961 phone. This phone has 16 lines whereas 6961 has 12 lines.
8831
voice register pool-type 8831
description Cisco IP Phone 8831
reference-pooltype 6921
CUCME 10.0 (15.3(3)M) until built in phone support is added at CUCME
8831 is a IP Conference Phone.

Example

voice register pool-type  7841
 xml-config maxNumCalls 4
 xml-config busyTrigger 2
 telnet-support
 gsm-support
 transport tcp
 num-lines 4
 addons 2
 description Cisco IP Phone 7841
 reference-pooltype 6941
!
voice register pool  1
 busy-trigger-per-button 1
 id mac 0008.2F1B.747B
 type 7841
 number 1 dn 1
 template 1
 dtmf-relay rtp-nte
 description OIM PHONE

7 comments:

  1. Maaz Ahmed Shariff12:22 PM, August 29, 2016

    Hi Mohammed, Have one small doubt. Could you help me clear that ?

    ReplyDelete
  2. Could you tell the procedure in order to register the 7821 phones properly on CM Express?

    ReplyDelete
  3. Could you show the CNF files created by 7800 phones on tftp server CM Express?

    ReplyDelete

DNS Performance Troubleshooting

When you are troubleshooting internet performance, there are different parts of the connection should be verified:   ·         DNS Pe...