cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Community Helping Community

875
Views
0
Helpful
4
Replies
Highlighted
Contributor

cisco 7940 upon powering on

Hi everybody

I just want to confirm few things:

1) Does cisco ip phone  7940 with sccp firmware look for file OS79XX.TXT on tftp when first powers up?

2)  Does cisco ip phone 7940 with sccp firware version upon resetting, look for SEPMac file for example

SEP003094C25D2E.cnf.xml  where 94c25D2E is the mac address of the phone?

thanks

Everyone's tags (3)
3 ACCEPTED SOLUTIONS

Accepted Solutions
Hall of Fame Master

cisco 7940 upon powering on

1. only with old frimware version when phone is factory reset.

2. yes.

View solution in original post

Hall of Fame Community Legend

cisco 7940 upon powering on

Hi there,

Just a reference to the great tips from my friend Paolo (+5 "P" )

Original Boot Mechanism for Firmware Image Selection

A protocol boot mechanism is used to select the firmware image. During  the phone bootup, regardless of protocol, the first file requested is  the OS79XX.TXT file. The OS79XX.TXT file includes a line that contains  the image name of the protocol that you select to run. For example, the  image should read P003xxyyzzww for SCCP, P0S3-xx-y-zz for SIP, or  P0M3-xx-y-zz for MGCP.

The phone uses the first four characters in the image name of the  OS79XX.TXT file to determine how to load the image. If the first four  characters match, the universal boot mechanism is bypassed and the phone  continues with its current protocol boot sequence. However, if the  first four characters do not match (namely the third digit, which  represents the protocol), the universal boot mechanism will attempt to  load the new protocol image that has been defined in the OS79XX.TXT  file.

Universal Application Loader

The universal application loader allows for additional phone features to  be added across all protocols. This feature also eliminates the need  for a separate OS79XX.TXT file, which used to be required for booting  between protocols.

The universal application loader operates in a manner very similar to  the older SCCP, SIP, and MGCP systems. It relies on a TFTP server to  supply information in text files known as "configuration files." The  information in these files points to a new loads file, which contains  the names of the desired application image and universal application  loader. This system allows the universal application loader to know  which image revision is desired in the phone. Once this information is  known, the phone has the ability to upgrade itself and the application  image as needed.

The universal application loader allows the system administrator to use  SCCP, SIP, and MGCP, on the same network. To do this, a hunt algorithm  is employed that searches for multiple configuration files. Depending on  which configuration file is found first, the phone will automatically  select that protocol. The hunt algorithm ensures that the administrator  can assign a specific protocol to a specific phone. The hunt algorithm  searches for files in the following order:

1. CTLSEP MAC File—For example, CTLSEP003094C25D2E.tlv. See the "Secure and Nonsecure Configuration" section.

2. SEP MAC File—For example, SEP003094C25D2E.cnf.xml.

3. SIP MAC File—For example, SIP003094C25D2E.cnf.

4. MGCP MAC File—For example, MGC003094C25D2E.cnf.

5. XML Default File—For example, XMLDefault.cnf.xml.

6. SIP Default File—For example, SIPDefault.cnf.

7. MGCP Default File—For example, MGCDefault.cnf.

The universal application loader is also capable of searching multiple  servers to find the configuration files, using DHCP, manual settings,  and Domain Name System (DNS). The configuration file can also contain a  dynamic_tftp address, which will force the phone to use a different  server.

If the universal application loader exhausts all possible servers and  still cannot find any configuration files, it will assume that the  application image in flash memory is correct and will launch it. If it  cannot find an application image in flash memory, it will stop and  display "No Load Specified" on the screen.

The loads file contains the universal application loader and the  application image, as well as an LA_VERSION command (used to determine  if the universal application loader needs to be upgraded).   The  universal application loader is identified by its extension (.sbn),  which indicates that it is signed. The signed application image is  identified by a .sb2 extension. The loads file itself is also signed and  has a .loads extension.

http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/7960g_7940g/mgcp/firmware/matrix/frmwrup.html#wp1046451

Cheers!

Rob

"Every fool's got a reason to feelin' sorry for himself" - Springsteen

View solution in original post

Hall of Fame Master

cisco 7940 upon powering on

No, as mentioned above, it will not look for tha file, that is now obsolete.

Thank you for the nice rating and good luck!

View solution in original post

4 REPLIES 4
Hall of Fame Master

cisco 7940 upon powering on

1. only with old frimware version when phone is factory reset.

2. yes.

View solution in original post

Hall of Fame Community Legend

cisco 7940 upon powering on

Hi there,

Just a reference to the great tips from my friend Paolo (+5 "P" )

Original Boot Mechanism for Firmware Image Selection

A protocol boot mechanism is used to select the firmware image. During  the phone bootup, regardless of protocol, the first file requested is  the OS79XX.TXT file. The OS79XX.TXT file includes a line that contains  the image name of the protocol that you select to run. For example, the  image should read P003xxyyzzww for SCCP, P0S3-xx-y-zz for SIP, or  P0M3-xx-y-zz for MGCP.

The phone uses the first four characters in the image name of the  OS79XX.TXT file to determine how to load the image. If the first four  characters match, the universal boot mechanism is bypassed and the phone  continues with its current protocol boot sequence. However, if the  first four characters do not match (namely the third digit, which  represents the protocol), the universal boot mechanism will attempt to  load the new protocol image that has been defined in the OS79XX.TXT  file.

Universal Application Loader

The universal application loader allows for additional phone features to  be added across all protocols. This feature also eliminates the need  for a separate OS79XX.TXT file, which used to be required for booting  between protocols.

The universal application loader operates in a manner very similar to  the older SCCP, SIP, and MGCP systems. It relies on a TFTP server to  supply information in text files known as "configuration files." The  information in these files points to a new loads file, which contains  the names of the desired application image and universal application  loader. This system allows the universal application loader to know  which image revision is desired in the phone. Once this information is  known, the phone has the ability to upgrade itself and the application  image as needed.

The universal application loader allows the system administrator to use  SCCP, SIP, and MGCP, on the same network. To do this, a hunt algorithm  is employed that searches for multiple configuration files. Depending on  which configuration file is found first, the phone will automatically  select that protocol. The hunt algorithm ensures that the administrator  can assign a specific protocol to a specific phone. The hunt algorithm  searches for files in the following order:

1. CTLSEP MAC File—For example, CTLSEP003094C25D2E.tlv. See the "Secure and Nonsecure Configuration" section.

2. SEP MAC File—For example, SEP003094C25D2E.cnf.xml.

3. SIP MAC File—For example, SIP003094C25D2E.cnf.

4. MGCP MAC File—For example, MGC003094C25D2E.cnf.

5. XML Default File—For example, XMLDefault.cnf.xml.

6. SIP Default File—For example, SIPDefault.cnf.

7. MGCP Default File—For example, MGCDefault.cnf.

The universal application loader is also capable of searching multiple  servers to find the configuration files, using DHCP, manual settings,  and Domain Name System (DNS). The configuration file can also contain a  dynamic_tftp address, which will force the phone to use a different  server.

If the universal application loader exhausts all possible servers and  still cannot find any configuration files, it will assume that the  application image in flash memory is correct and will launch it. If it  cannot find an application image in flash memory, it will stop and  display "No Load Specified" on the screen.

The loads file contains the universal application loader and the  application image, as well as an LA_VERSION command (used to determine  if the universal application loader needs to be upgraded).   The  universal application loader is identified by its extension (.sbn),  which indicates that it is signed. The signed application image is  identified by a .sb2 extension. The loads file itself is also signed and  has a .loads extension.

http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/7960g_7940g/mgcp/firmware/matrix/frmwrup.html#wp1046451

Cheers!

Rob

"Every fool's got a reason to feelin' sorry for himself" - Springsteen

View solution in original post

Contributor

cisco 7940 upon powering on

Thanks Rob and Paolo

So what do kind of behavior we expect from modern cisco ip phone upon powering on?  Will they look for OS79XX.txt file on tftp server? I understand that when we reset the phone, the phone will look for specific file on tftp server for example  SEP mac file if the loaded firware is sscp. But that is only when we reset the phone. What if we not reset the phone and simply power it up , will it look for OS79XX.txt file?( Considering only cisco ip phone with latest firware)

thanks

Hall of Fame Master

cisco 7940 upon powering on

No, as mentioned above, it will not look for tha file, that is now obsolete.

Thank you for the nice rating and good luck!

View solution in original post

CreatePlease to create content
Content for Community-Ad
FusionCharts will render here