Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 

Fast track support for SIP phones

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 :

FamilyKpml-supportDND-updateConfig-dnld-resetFeature-keys-suportDefault-passwdSSH-support
TNPYesYesNoYesNoneNo
RTLNoNoYesYesNoneYes
URTLNoNoYesYesCiscoYes
GumboNoNoYesYesNoneNo
RTYesYesYesNoNoneYes
OEMNoNoYesYesNoneNo


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

 

Version history
Revision #:
1 of 1
Last update:
‎05-21-2014 05:49 AM
Updated by:
 
Labels (1)
Comments
Cisco Employee

   

New Member

Great article!

I have these questions..

With this enhancement can Cisco SIP phone do up to 10 multiparty voice conferencing with CME?

How many lines does 8831 support?

How will 8831 handle conferencing when two simultaneous call came in within the scope of this enhancement.

Thanks,

New Member

Hi, 

This sounds great...

thanks.

-Shakir

Thanks!! Great documentation!

Do you know if the 88XX phones are supported with this now? Specifically the 8841?

Cisco Employee

Hi Jonathan , CME 10.5 supports 8841 in fast track mode.

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucme/requirements/guide/cme105spc.html

Cheers!

Aravindh

Finally registered 8831 to CME 10.5. 4 days and 14 hours each day. I am posting my config

Router IOS: "flash0:c2900-universalk9-mz.SPA.154-3.M2.bin"

Config :

voice service voip
no ip address trusted authenticate
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
no supplementary-service sip moved-temporarily
no supplementary-service sip refer
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none
h323
call start slow
sip
bind control source-interface Loopback0
bind media source-interface Loopback0
registrar server
no silent-discard untrusted
!
voice class codec 1
codec preference 1 g711ulaw
codec preference 2 g711alaw
codec preference 3 g729r8
codec preference 4 g729br8
!
!
!
!
voice register pool-type 8831
xml-config maxNumCalls 2
xml-config busyTrigger 1
xml-config custom sshAccess 0
phoneload-support
num-lines 2
description Cisco SIP Phone 8831
reference-pooltype 6921
!
voice register global
mode cme
source-address 10.195.1.3 port 5060
max-dn 2
max-pool 4
load 8831 sip8831.9-3-3-5
timezone 42
tftp-path flash:
file text
create profile sync 0264103030741005
!
voice register dn 1
number 611050
name Conference Phone
!
voice register dialplan 1
type 7940-7960-others
pattern 1 611...
pattern 2 57....
!
voice register pool 1
busy-trigger-per-button 1
id mac AC44.F212.B9FE
type 8831
number 1 dn 1
dialplan 1
dtmf-relay sip-kpml
voice-class codec 1
username admin password cisco
no vad

and finally got it registered:

#sh voice register pool 1 brief
Pool ID              IP Address      Ln DN  Number               State
==== =============== =============== == === ==================== ============
1    AC44.F212.B9FE  10.195.92.15    1  1   611050$              REGISTERED

It took four days but learned so many things

Use the correct 8831 firmware

You might nor get US language .jar for 9-3-3-5 in Locale . Hence download from other firmware versions

I am running all phones (42) on SCCP and one 8831 on SIP on same CME and it is working for me.

I can not comment upon that conferencing and all are working fine or not as the Phone is in Shanghai and I was working on it from India office.

However I will get updates from colleagues and will post.

Thanks.!

New Member

Hi Harshdeep,

I have three CP-8831 and IOS Version 15.4(3)M3, RELEASE SOFTWARE (fc2) and System Bootstrap, Version 15.0(1r)M16, RELEASE SOFTWARE (fc1).

The phones do not boot beyond the Cisco logo. What could be the problem ?

Please see attached configs.

New Member

Guys, could you please tell me what is the nearest reference phone to the CP-8851? I got confused and I don't know what to choose. I believe it's one of the TNP family phones but which one?

Your help is much appreciated.

Thank you

Bassam

New Member

Hello Gauravdeep

I'm an end user here trying to find anyone who can get my 8845 and 8865 phones to work on a 2911 router via Fast-Track as you have spec'd above. Do you have any advice based on your experience, or might you yourself, or possibly someone you know be able to work on this for me? Tried everything to no avail.

Looking forward to your response.

Thank you!