This directory has been setup for beta customers using the SIP IP Phone. Provided in this directory is the latest image and the release notes associated with the image. The ipphone-beta@cisco.com alias is setup with engineering and marketing folks for any questions, comments, or concerns that you may have regarding the phone. Phase 2 - April, 2000 --------------------- Phase 2 beta images are named P003Zxxx.bin where xxx is a number. The release notes and Administrator's Guide are Acrobat Reader (*.pdf) files. Phase 3 - June, 2000 -------------------- Phase 3 beta images are named P0S3Z3xx.bin where 3xx is a number. The Administrator's Guide is an Acrobat Reader (*.pdf file). Phase 3 / Release 1.0 - Generally Available - August, 2000 ---------------------------------------------------------- Release 1.0 has been officially released. The documentation can be found at: http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/sip7960/index.htm The software is P0S30100.bin and is located in the directory. The software can also be found in the software center link on CCO. Phase 4 - October, 2000 ----------------------- Phase 4 beta images are named P0S3Z4xx.bin where 4xx is a number. The Administrator's Guide is an Acrobat Reader (*.pdf file). Phase 4 / Release 2.0 - Generally Available - January, 2001 ----------------------------------------------------------- Release 2.0 has been officially released. The documentation can be found at: http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/sip7960/index.htm The software is P0S30200.bin and is located in the directory. The software can also be found in the software center link on CCO. Phase 4+ (3-way call) - April, 2001 ----------------------------------- Phase 4+ beta images are named P0S3Z4xx.bin where 4xx is a number. The Administrator's Guide is located: http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/sip7960/sipadm2/index.htm Phase 4+ / Release 2.1 - Generally Available - June, 2001 ----------------------------------------------------------- Release 2.1 has been officially released. The documentation can be found at: http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/sip7960/index.htm The software is P0S30201.bin and is located in the directory. The software can also be found in the software center link on CCO. Release 2.2 Beta - October, 2001 ---------------------------------- Release 2.2 Beta images are named P0S3Z5xx.bin where XX is a number. The Release 2.1 Administrator's Guide should be used for documentation with the additions/changes noted below. The Release 2.1 Admin Guide is located at: http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/sip7960/sipadm21/index.htm Release 2.2 - Generally Available - October, 2001 ------------------------------------------------- Release 2.2 has been officially released. The documentation can be found at: http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/sip7960/index.htm The software is P0S30202.bin and is located in the directory. The software can also be found in the software center link on CCO. Release 3.0 Beta - December, 2001 --------------------------------- Release 3.0 Beta images are named P0S3-02-7-XX.bin where XX is a number. The Release 3.0 Beta Administrator's Guide should be used for documentation with the additions/changes noted below. Release 3.0 - Generally Available - January, 2002 ------------------------------------------------- Release 3.0 has been officially released. The documentation can be found at: http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/sip7960/index.htm The software is P0S3-03-0-00.bin and is located in the directory. The software can also be found in the software center link on CCO. Release 3.1 - Generally Available - March, 2002 ----------------------------------------------- Release 3.1 has been officially released. The documentation can be found at: http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/sip7960/index.htm The software is P0S3-03-1-00.bin and is located in the directory. The software can also be found in the software center link on CCO. Release 3.2 - Generally Available - June, 2002 ---------------------------------------------- Release 3.2 has been officially released. The documentation can be found at: http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/sip7960/index.htm The software is P0S3-03-3-00.bin and is located in the directory. The software can also be found in the software center link on CCO. Release 4.0 - Generally Available - August, 2002 ------------------------------------------------ Release 4.0 has been officially released. The documentation can be found at: http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/sip7960/index.htm The software is P0S3-04-0-00.bin and is located in the directory. The software can also be found in the software center link on CCO. Release 4.1 - Generally Available - September, 2002 --------------------------------------------------- Release 4.1 has been officially released. The documentation can be found at: http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/sip7960/index.htm The software is P0S3-04-1-00.bin and is located in the directory. The software can also be found in the software center link on CCO. Release 4.2 - Generally Available - January, 2003 ------------------------------------------------- Release 4.2 has been officially released. The documentation can be found at: http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/sip7960/index.htm The software is P0S3-04-2-00.bin and is located in the directory. The software can also be found in the software center link on CCO. Release 4.3 - Generally Available - February, 2003 -------------------------------------------------- Release 4.3 has been officially released. The documentation can be found at: http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/sip7960/index.htm The software is P0S3-04-3-00.bin and is located in the directory. The software can also be found in the software center link on CCO. PHASE 2 RELEASE NOTE ADDITIONS ****************************** 5/23/00 ------- Recent testing with Phase 2 has uncovered that the SIP IP Phone sometimes gets into a state of 'Phone not registered' after a period of 24-72 hours. The problem has been identified and will be resolved as part of the Phase 3 delivery. Presently, if you encounter this issue the workaround is to cycle power on the phone. PHASE 2 to PHASE 3 UPGRADE ************************** 6/26/00 ------- There are a few steps that will need to be taken to ensure successful upgrade from Phase 2 (P003Z210) to Phase 3 (P0S3Z324). The reason for some of the changes are due to multiple line support of the phone and consistent image naming convention. The following steps should be taken to ensure successful upgrade: 1. Download the latest 'Cisco SIP IP Phone Administrator Guide' from the ftpeng server - filename phase3_adminguide.pdf (Acrobat Reader format). 2. Download the configuration file conversion utility and convert Phase2 configuration files to Phase 3: cnfupgrade (Solaris Platform) cnfupgrade_pc.exe (PC Platform) This utility allows for an easy conversion of existing Phase 2 configuration files (SIP.cnf) to Phase 3 configuration files with the changed parameters. The script is run from the command line with one file or multiple files: Solaris: cnfupgrade SIP003094C25C70.cnf SIP003094C2613D.cnf or PC: cnfupgrade_pc SIP003094C25C70.cnf SIP003094C2613D.cnf The script results in two files - SIP003094C25C70.cnf (Phase 3) SIP003094C25C70.bak (Old Phase 2) 3. Download the Phase 3 Phone image (P0S3Z324.bin) to the root tftp directory. 4. Download SIP_Default_generic.cnf and SIP_Config_generic.cnf - These are generic Phase 3 Config files. Refer to the Administrator's Guide for use of the SIPDefault.cnf configuration file, which allows for global control of parameters. 5. Change the image_version in SIP003094C25C70.cnf to reflect the new image. After the upgrade is complete, then image_version can be used in SIPDefault.cnf Note: If using SIPDefault.cnf for image_version, the SIP.cnf should NOT have this parameter; otherwise, the value in the SIP.cnf is what will be used. 6. Power Cycle the phone. The phone will upgrade from Phase 2 to Phase 3. CONFIGURATION FILE PARAMETER CHANGES FROM PHASE 2 TO PHASE 3 ************************************************************ To be more consistent with multiple DN support and timer support there was a need to change a few configuration file parameters. These changes are from Phase 2 to Phase 3 only. There should not be any changes from Phase 3 forward. Phase 2 Phase 3 ------- ------- user_name line1_name proxy_1 proxy1_address logical_name line1_authname logical_password line1_password register_timeout timer_register_expires PHASE 3 FILES REQUIRED FROM TFTP ******************************** The OS79XX.TXT file is strictly for determining which VoIP environment your phone will need to run in. Since we are running in a SIP environment you technically do not need to have this file, but for completeness the file consists of one line: P0S30100 The name of the file is case sensitive: OS79XX.TXT The RINGLIST.DAT file is a file that contains any customized ringers. The phone by default has Chirp1 and Chirp2. The RINGLIST.DAT file allows for the sysadmin to specify a list of ringers that can be downloaded via TFTP. The format of the file looks like: Old Style ringer1.pcm Synth Low ringer2.pcm where ringer1.pcm and ringer2.pcm are the ring files located in the root TFTP directory, and Old Style and Synth Low show up on the Ring Type menu as options 3 and 4. When you select one of the ringers (that are not Chirp1 or Chirp2) the ringer is loaded via TFTP if played and loaded via TFTP and stored in flash if selectedand saved. CONFIGURATION FILE PARAMETER CHANGES FROM PHASE 3 TO PHASE 4 ************************************************************ There was a need to change user configuration file parameters to clear some confusion. There are NO user parameters beyond Phase 3. Any config files that contain user parameters will show up as parse errors in Settings --> Status --> Status Messages Phase 3 Phase 4 ------- ------- userN_name REMOVED userN_authname REMOVED userN_password REMOVED RECOMMENDED STEPS TO DO PRIOR TO UPGRADE FROM PHASE 3 TO PHASE 4 **************************************************************** 1. Download the latest 'Cisco SIP IP Phone Administrator Guide' from the ftpeng server - filename phase4_adminguide.pdf (Acrobat Reader format). 2. Download the Phase 4 Phone image (P0S3Z431.bin) to the root tftp directory. 3. Add the new Phase 4 paramters from SIP_Default_generic.cnf to SIPDefault.cnf, as well as from SIP_Config_generic.cnf to SIP.cnf 4. At a minimum, specify a SNTP Server and timezone. This will display time in the upper left corner of the phone display. Without these provisioned the phone will not display the correct time or will display 'No time server'. 5. The dialplan.xml file is an example dialplan configuration. Edit the dialplan.xml file to reflect the correct corporate dial configuration for your location. The dialplan.xml file should be copied into the root TFTP directory, but can be moved to a different location based on the dial_template parameter. 6. Edit the tftp_cfg_dir parameter in SIPDefault.cnf to reflect a directory, relative to root TFTP directory, where all Phone specific configuration files are stored. If it is left as "" the Phone specific files can be left in the root TFTP directory. *************************************** ADDITIONAL PHASE 4 FEATURE DESCRIPTIONS *************************************** CC-Diversion ------------ Support for the CC-Diversion header has been implemented per the IETF draft: draft-levy-sip-diversion-00.txt MWI via unsolicit NOTIFY ------------------------ Support for Message Waiting Indication has been implemented using unsolicit NOTIFY *only* following the 'classic' format outlined in the IETF draft: draft-mahy-sip-message-waiting-00.txt Example: --- A6: Notifier -> Subscriber This is a notification using "classic", boolean message waiting. NOTIFY sip:rohan@dhcp78-193.cisco.com SIP/2.0 To: From: Date: Mon, 10 Jul 2000 16:28:53 -0700 Contact: Call-ID: 1349882@dhcp78-193.cisco.com CSeq: 8938 NOTIFY Event: message-summary Content-Type: text/plain Content-Length: 22 Message-Waiting: yes --- Message-Waiting: yes lights the LED on the Handset Message-Waiting: no turns off the LED on the Handset NOTE: Since only unsolicit NOTIFY is being used and not the complete Subscribe/Notify, the indication will not be maintained through an upgrade or power cycle. Remote Reboot ------------- This feature allows a System Administrator to maintain control of the phone up to and including an upgrade. The following is a list of steps involved to use the remote reboot feature, as well as an explaination as to how it works. The starting point is that a network exists that includes SIP Phones, a SIP Proxy Server, and the TFTP server for images and phone configs. For purposes of an example assume the phone is running the P0S3Z438 image. There exists a file, syncinfo.xml, that controls the image version and associated sync value. This syncinfo.xml file exists in the root TFTP directory just as the SIPDefault.cnf and RINGLIST.DAT files. The xml file will have the format: where 'IMAGE VERSION' represents the image versions of the phone and 'SYNC' represents the sync level of the phone. The default sync level for the phone is 1. The 'sync' parameter default can also be specified via the config files. The sync parameter can be up to 32 characters in length indicating for instance a date or time. There are a few steps needed prior to the reboot process on the phone: 1. Edit the image_version paramter in SIPDefault.cnf to the correct image (ie. image_version: P0S3Z439) 2. Edit the syncinfo.xml file to reflect a new sync value for the *current* image, and enter the new image with the this same sync value. 3. Send NOTIFY to phone with a check-sync Event header. The reboot process on the phone is initiated when a NOTIFY is received with an Event header equal to 'check-sync'. The issue of how the phone receives the NOTIFY or what application generates the NOTIFY will not be address because it has no effect on the phone behavior. Once the phone receives the NOTIFY with check-sync Event header the process is started. An example NOTIFY, where 12345 is one of the lineN_name parameters configured and 1.2.3.4 is the proxyN_address for line N, is as follows: ----------- NOTIFY sip:12345@1.2.3.4:5060 SIP/2.0 Via: SIP/2.0/UDP 1.2.3.4:5060;branch=1 Via: SIP/2.0/UDP 1.1.1.2 From: To: Event: check-sync Date: Mon, 10 Jul 2000 16:28:53 -0700 Call-ID: 1349882@1.1.1.2 CSeq: 1300 NOTIFY Contact: Content-Length: 0 ----------- Steps for reboot once the Notify is received: 1. Is the phone in an idle state? Yes - wait 20 seconds No - wait until idle state, then wait 20 seconds 2. After the 20 seconds, TFTP for the syncinfo.xml file 3. Is the current image (P0S3Z438) listed in the syncinfo.xml file? Yes - Goto Step 5 No - Goto Step 4 4. Is there a wildcard entry for the IMAGE VERSION variable in syncinfo.xml? Yes - Goto Step 5 No - Goto Step 6 5. Is the SYNC value different than what is stored on the phone? Yes - Goto Step 7 No - Goto Step 6 6. Do Nothing 7. Store new sync value in flash and Reboot The phone then goes through the normal boot process, sees the new image, and upgrades to the P0S3Z439 image with a sync value of 2. By adding the new line in the syncinfo.xml file erroneous reboots are prevented. NOTIFY meesages with check-sync headers can be sent to the phone but since the sync value for the P0S3Z439 image is the same as what is stored on the phone the phone does not reboot. 12 Hr/24 Hr Time Display ------------------------ This feature is controlled by the user via the services menu. The default is 24 hour diplay. There is also a parameter in the config file - time_format_24hr (0 - 12 Hour, 1 - 24 Hour). ***************************** PHASE 4+ FEATURE DESCRIPTIONS ***************************** 3-way conferencing ------------------ Three-way call, or conferencing, is a feature to support conferencing with two other phones by providing mixing on the initiating phone. To set up a 3-way conference: http://www.cisco.com/univercd/cc/td/doc/product/voice/c_ipphon/ip_7960/ getstart/ipp60get.htm#51304 Caveats: - 3-way conferencing can only be done with g711ulaw or g711alaw. - Inband DTMF tones on the conferencing node are disabled during a 3-way conference call. - Call waiting calls cannot be conferenced in, the conferencing node must establish both legs of the 3-way conference. Distinctive Alerting -------------------- Dinstinctive ringing is now invoked if the INVITE contains an Alert-Info header. The header takes the form of Alert-info: x and is only received by the phone, where x is any number. The phone will not generate this header. Dinstinctive ringing is supported both when the phone is idle or during a call. In the idle mode, the phone will ring with a different cadence. The selected ringing type will be played twice with a short pause in between. In call-waiting mode, two short beeps will be generated instead of one long beep. **************************************** ADDITIONAL PHASE 4+ FEATURE DESCRIPTIONS **************************************** DNS SRV ------- DNS SRV support has been implemented in accordance with RFC2782, as well as draft-ietf-sip-srv-01.txt. Support for Backup Proxy ------------------------ When the configured proxyN_address does not respond to the INVITE message sent by the Cisco SIP Phone, the phone will send the INVITE to the backup proxy (proxy_backup parameter in the config file). The determination as to when to use the backup proxy is as follows: The phone does not REGISTER with the backup proxy, and all interactions such as authentication are treated the same as would be with the primary proxy. Initial INVITE has no response, after 7 retries display a message 'Network Delay, trying backup' and send the INVITE to the configured backup proxy. The backup proxy is used for the duration of the call and is used for INVITE methods only. The next attempt to use the primary proxy will switch to the backup proxy after 3 retries, while display the message 'Network Delay, trying backup'. The switch to backup will remain at 3 retries until 12 successful 1xx, 2xx, 3xx, 4xx, 5xx, or 6xx messages are received from the primary proxy without having to use the backup proxy. The new parameters for the config file are: proxy_backup: 1.2.3.4 (restricted to dotted ip only) proxy_backup_port: 5060 (default is 5060) Support for Emergency Proxy --------------------------- When an Emergency Proxy is configured and the dialed number matches a TEMPLATE in the dialplan that has the route=emergency attribute, the phone will generate an INVITE to the address specified in proxy_emergency. The Emergency Proxy will be used for the duration of the call. See below for dialplan TEMPLATE changes. Furthermore, the backup proxy logic also applies if the emergency proxy is not available. The new parameters for the config file are: proxy_emergency: 1.2.3.4 (restricted to dotted ip only) proxy_emergency_port: 5060 (default is 5060) Dialplan TEMPLATE change ------------------------ The updated description for the