Are amongst the most popular desktop IP phones out there. By default, Cisco ship their phones from the factory pre-loaded with their proprietary SCCP protocol firmware (also commonly referred to as “skinny”).
If you are running Asterisk, Trixbox, Switchvox or any other standards-based SIP platform or hosted service, you’ll need to migrate your Cisco phone(s) from their native SCCP (skinny) load to SIP in order to use them. While this is not a particularly difficult procedure, it can be frustrating for those who have never attempted the process. For the purposes of this exercise, we’re using a Cisco CP-7960G. The process may be slightly different depending upon the specific model of Cisco IP phone you are working with. Can support either the Skinny Call Control Protocol (SCCP), Session Initiation Protocol (SIP), or the Media Gateway Control Protocol (MGCP), but not more than one simultaneously.
This is possible because they load different firmware versions on bootup. This functionality is transparent to the end user, and you enable it through changes to the basic text−based configuration files that the phones download from a Trivial File Transfer Protocol (TFTP) server. First, a few prerequisites: A – You’ll need a CCO login for Cisco.com in order to obtain the latest SIP firmware. The easiest way to obtain a CCO login is to purchase a Smartnet maintenance contract for your Cisco IP phone from an authorized Cisco reseller. Once you have a registered Smartnet, you can obtain CCO login credentials and access the section of Cisco’s website. Expect to pay $8-$15 for a Smartnet contract. B – You should have a comfort level with basic networking concepts and TFTP setup/administration.
Follow these steps to enable SIP functionality: Step #1 Download these files from Cisco SIP IP Phone Software ( registered customers only) and place them in the root directory of your TFTP server (tftpboot on a UNIX machine): • P0S30100.bin This is the SIP image. You’ll want to download the file in binary format, to ensure that it is not corrupted. Note: There are many different variations of this file, depending on the version of software that you are loading.These are some examples: • SIP Release 2.3 or earlier: P0S3xxyy.bin The xx variable is the version number, and yy is the sub−version number. • SIP Release 3.0 and later: P0S3−xx−y−zz.bin The xx variable is the major version number, y is the minor version number, and zz is the sub−version number. • SIP Release 5.0 and later: After this version has been installed, you will not be able to revert back to versions earlier than 5.0. You may still change from SCCP images to SIP images, but they both must be version 5.0 or later.
For more information on this, refer to Release Notes for Cisco SIP IP Phone 7940/7960 Release 5.0. Cara membuat software silent installer software free. • This table describes the meanings of the first 4 characters in the binary files names. Note: To verify which image the phone is using, choose Settings > Status > Firmware Versions.
Table 2 lists Severity 1, 2 and 3 defects that are open for the Cisco Unified IP Phone 7975G, 7965G, 7945G, 7962G and 7942G using the SCCP and SIP versions of firmware release 8.3(2)SR1. For more information about an individual defect, you can access the online record for the defect by clicking the Identifier or going to the URL shown. Feb 16, 2011 - How to load SIP or SCCP on a Cisco 7940 7960 7941 7961 Ip Phone. 7942, 7962, 7945, 7965 IP phone to any firmware you want from the Cisco. If you are downloading an older version of the SIP/SCCP firmware and it.
Different phone models use different processors. This fourth digit can help determine the model of phone for which the file is used. • OS79XX.TXT—This file tells the Cisco 7940/7960 which binary to download from the TFTP server. This file is case sensitive and must only contain the name of the file that you want to load, without the.bin extension. For example, if you attempt to load the SIP version 2.3 software, it must contain only the line P0S30203. If you try to load versions 3.0 and later, the file name must be in the format P0S3-xx-y-zz. For example, if you attempt to load the SIP version 7.1 software, OS79XX.TXT must contain the line P0S3-07-1-00.