Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

46XX Upgrade script command 1

Status
Not open for further replies.

Maya97

Technical User
Sep 10, 2007
110
US
Hello All,

I am at a new location and they are trying to bring up 9600 series phones on CM 3.0. I see here that they are using H.323 and the 46xx upgrade script I have in front of me is using 4600 series phones as aliases to make the 9600 phones work in this environment. However, alot of the functionality will not work on the phones and I was wondering if there are commands out there that would help me get the sleep function, directory key, and other keys or functions to be administered to the phones.

Any suggestions or documentations will be very helpful...also at bootup the phones show LLDP error and there is no call server for the phones to connect with.
 
You can only run FW 1.55 or smaller on CM3.0. You probably need to downgrade the firmware. And you can't run any 96X1 phones on CM3.0.
 
Well can you tell me how this company managed to get 9620, 9650 and 9670 working on CM 3.0. I am looking at the 46xx file and it looks like they made the phones aliases in the pbx so that they can do "get" and "if" commands...I am not understanding this at all. Its more information to the file below I just want to add more functionality to the phones.

#check bootApp version

IF $MODEL4 SEQ 4601 goto BOOTAPP4601
IF $MODEL4 SEQ 4602 goto BOOTAPP4602
IF $MODEL4 SEQ 4606 goto BOOTAPP46XX
IF $MODEL4 SEQ 4610 goto BOOTAPP4610
IF $MODEL4 SEQ 4612 goto BOOTAPP46XX
IF $MODEL4 SEQ 4620 goto BOOTAPP4620
IF $MODEL4 SEQ 4624 goto BOOTAPP46XX
IF $MODEL4 SEQ 4621 goto BOOTAPP4620
IF $MODEL4 SEQ 4622 goto BOOTAPP4620
IF $MODEL4 SEQ 4625 goto BOOTAPP4625
IF $MODEL4 SEQ 4690 goto BOOTAPP4690

goto END

# BOOTAPP4601
IF $MODEL SEQ 4601D01A goto BOOTAPP4601D
IF $MODEL SEQ 4601D01B goto BOOTAPP4601P
goto END

# BOOTAPP4601D
IF $BOOTNAME SEQ 4601dbte1_82.bin goto CONVERT01
IF $BOOTNAME SEQ cvt01_2_3.bin goto AVAYACODE01
IF $BOOTNAME SEQ b01d01b2_3.bin goto DEF46XX
IF $APPNAME SEQ a01d01b2_3.bin goto END
goto GET01_182
goto END
 
96xx series phones were not natively supported in CM 3. They had to be programmed as 46xx sets.
 
wmainc,

you are right I found that the phones were created as 4600 ip phone however; I need the commands to make certain functions work or can I use the actual 46xx file for 4600 phones to make this happen? If I can how do I go about it?
 
Well can you tell me how this company managed to get 9620, 9650 and 9670 working on CM 3.0. I am looking at the 46xx file and it looks like they made the phones aliases in the pbx so that they can do "get" and "if" commands...I am not understanding this at all. Its more information to the file below I just want to add more functionality to the phones.

I stand corrected FW2.0 and smaller must be installed (not FW1.55) on all 96XX phones to run on CM3.0. Since 9670 first release was 2.0 it should work. Upgrade any of those phones to FW3.0 or larger and your phone won't register.

This is right from the support site:

CM 3.0 and CM 3.1 < load R013x.01.2.639.1 do not support Spice 3.0 firmware. The phone will not register to those CM loads.
 
Oh so the phones will just have basic functionality, no bells and whistles.
 
The 96xx phones use a 96xxupgrade file, but still use the 46xxsettings file.

the 16xx uses the 46xxsettings file too, but still have their own upgrade script file.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top