Feature overview:         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 . 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 avail generic SIP line features like Call Hold, Call Resume etc. 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.   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: CME10.0(config)#voice register pool-type <> CME10.0(config-register-pooltype)#device-reference  <one of the supported phone-type> CME10.0(config-register-pooltype)#addons [max-addons] CME10.0(config-register-pooltype)#device-name <name> CME10.0(config-register-pooltype)#num-lines <max-lines> CME10.0(config-register-pooltype)#transport-type <udp | tcp> CME10.0(config-register-pooltype)#GSM-Handoff CME10.0(config-register-pooltype)#telnet CME10.0(config-register-pooltype)#phoneload CME10.0(config-register-pooltype)#xml-config <name>  <value> Explanation: voice register pool-type <>                  This new phone type would be listed along with the supported device types for “type <phone-type>” CLI at voice register pool. This is a mandatory field and it is used as part of ‘voice register pool-type’ as explained in the examples in subsequent sections. device-reference  <one of the supported phone-type>               Define the nearest supported phone to inherit the properties from that phone. addons [max-addons]              Define the maximum number of addon modules supported by phone. Maximum allowed value is 3. Currently the configuration for a addon module is supported in the below format under 'voice register pool’. type <phone-type> addon <module-number> <module-type> [<module-number> <module-type>]         9971 sip phone supports a maximum of 3 addon modules, 9951 sip phone supports a maximum of 2 addon modules and 8961 sip phone supports 1 addon module.  The same format would be applicable to the new sip phone types that are added using the ‘voice register pool-type” CLI with the addons keyword mentioning the maximum number of addon modules supported by the new phone device. This is not applicable for supporting a new addon for an existing phone. device-name <name>                  Define the description string for this phone device. This description string would be displayed as a help string when this new phone type is listed along with the supported device types for “type <phone-type>” CLI at voice register pool.   Num-lines <max-lines>                  Define the maximum number of lines supported by phone. Transport-type <udp | tcp>                 Define the default transport type supported by phone. Currently majority of  the SIP phones uses UDP as the default transport type and it can be changed using the ‘session-transport {udp | tcp}’ CLI. The new Sip phones CiscoMobile-iOS and Jabber-Android uses TCP as default transport type and it can be overwritten. GSM-Handoff                 Define the Phone Support for GSM handoff. Currently, Sip phones Jabber-Android and CiscoMobile-iOS supports GSM handoff.  This value would be used in XML file with the below format and it has  dependency on the associated SNR configuration - "<cucmGSMHandoffPreference>%s</cucmGSMHandoffPreference>\n" Telnet                Define the Phone Support for Telnet access. Currently, Sip phones 7905, 7912, 7960, 7940, 3951 and 3911 supports Telnet  access.  This value would be used in XML file with the below format: "<telnetAccess>%d</telnetAccess>\n" Phoneload               Define the support for phone load.“load” CLI at “voice register global” can be used to configure the corresponding phoneload for the new phone type if it supports phoneload. Xml-config <name>  <value>               Define the phone specific XML tags to be used in configuration file.                  Examples:   xml-config  maxNumCalls  3                                      xml-config  busyTrigger     3                             where 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.  This information would be used while generating XML file. Choosing the device-reference:          When a reference phone model is configured, new phone type inherits all properties of reference phone .With reference phone model being configured, specfic phone properties can be still set to default values by having no form of the particular CLIs.Explicit configuration overrides the default value or the value inherited from reference phone           Most of the new phone models would be either a new member for RT family or a cost-reduction phone model with a reference to the parent phone. This option allows the new phone to inherit all the properties of the nearest phone based on either the phone family or the parent phone without explicit configuration of those parameters.           Some of these parameters can be overwritten using the configuration options. When device-reference is not configured and phone properties are also not configured explicitly, then default value would be used which would be the corresponding phone property of 7965 phone model. i.e. 7965 phone model would be used as a default phone reference. Here is the list of supported phones which can be entered as device-reference : TNP Family   : 7906 7911 7941 7941GE 7942 7945 7961 7961GE 7962 7965 7970 7971 7975 CiscoMobile-iOS Jabber-Android 3905 OEM Family   : 3911 3951 RTL Family   : 6961 6945 6941 6921 URTL Family  : 6911 6901 GUMBO Family : 8941 8945 RT Family    : 9971 9951 8961 CUCIConnect                Generic phone parameters that are common for a phone family:   Phone Supports KPML :     Define the capability of the phone for kpml support. This would be TRUE for all TNP and RT phones. Dnd-update :     Define the phone capability for handling DND updates. When the CLI ‘[no] dnd’ is modified then a DND update would be sent to the corresponding phone using a REFER request if it belongs to TNP or  RT family. apply-config-reset :     Phone supports config dnld w/o reset. Define the capability of the phone to apply configuration without phone reset. This would be  TRUE for all RT phones. Feature-key-allowed :     supported feature buttons .Define the support for various feature keys. For RT phones, feature key buttons HOLD, XFER, FWDALL, CONFRN, NEWCALL, ENDCALL and CONFLIST are ignored during ‘show pool tag layout’. Password :     Define the default password used by phone for authentication.  For phones of URTL family the default password is “Cisco”.   SSH :     Define the support for SSH with username and password.This support is available for the phones of RT, RTL and URTL family. Table of generic properties of each phone family : Family Kpml-support DND-update Config-dnld-reset Feature-keys-suport Default-passwd SSH-support TNP Yes Yes No Yes None No RTL No No Yes Yes None Yes URTL No No Yes Yes Cisco Yes Gumbo No No Yes Yes None No RT Yes Yes Yes No None Yes OEM No No Yes Yes None No Default values for all the properties of a new phone (when no reference is defined):      num-lines  1      addons  0          description NONE      gsm-support NO      phoneload-support NO      telnet-support   NO      reference-pooltype  NONE      transport UDP      xml-config  maxNumCalls 0      xml-config  busyTrigger   0      xml-config  custom  NONE   Additional Information regarding 78XX and 8831 phones: The defect CSCun99347 was filed for the 7800 and 8831 Phones. The IOS and Firmaware information is updated in the link - http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucme/requirements/guide/cme10spc.html for 78XX phones , the closest model is the 69XX phones for 8831, we can use 6941 as a reference type. Configuration example: voice register pool-type  8831             phoneload-support     telnet-support     num-lines 6     description 8831 Phone     reference-pooltype 6941      Debugging: debug tftp events debug tftp packets (Enable only for Registration issues) debug voice register errors debug voice register events debug ccsip all   ... View more