[AusNOG] Cisco 9951 phones w/ SIP firmware

[Alistair Weddell]

Hi Tim,

Just a note that these phones run a Java based OS and as such will require a different set of firmware to your standard 7940/60's.  They also take a different format config file, XML based; similar to the Java powered 7912 or the 79x1 devices as mentioned by Chris, you might have more luck looking at the config file examples for these more popular devices to gain an understanding of this format as it varies vastly to the 79x0 devices mentioned in most Asterisk blogs.

Best of luck!

Al

Alistair Weddell | Network and Security Engineer
Lonely Planet
90 Maribyrnong St
Footscray, VIC 3011 Australia
tel. +61 (0) 3 8379 8000

--


From: ausnog-bounces at lists.ausnog.net [mailto:ausnog-bounces at lists.ausnog.net] On Behalf Of Christopher Pollock
Sent: Wednesday, 14 December 2011 2:08 PM
To: ausnog at ausnog.net
Subject: Re: [AusNOG] Cisco 9951 phones w/ SIP firmware

Hi Tim,

Not those phones specifically, but I did spent a lot of time getting familiar with the 7940 and 7941 in an Asterisk environment a few years back.  From what I remember, Cisco will sell you a support contract for the phone that is pretty cheap, so you can just download everything you need.

Until these things boot, the biggest debugging tool you have is what files it requests from TFTP.  If you can hack up a custom console cable, some of their phones have a console or aux port you can cable into and get some debug info out of.  If it actually boots, you can do some tricks with authorized_keys files and/or the web interface to get debug stuff, detailed in a blog post I made about my fun: http://resolvehax.blogspot.com/2009/04/how-to-set-your-cisco-7940-and-7941-ip.html

My experiences with the 7941 are probably the closest to your 9951 as I believe the configuration file formats etc are the same.

Unfortunately there's a lot of trial and error, and usually if the configuration file itself has loaded and parsed successfully, then it's actually a problem with the configuration, which is much harder to identify.  For example some older versions of the firmware would accept true, TRUE or 1, false FALSE or 0 in any boolean field, whereas later they're more strict, etc.

The bright side is, once you get them configured just right, they tend to work forever.  The down-side is, you're in for more haxing next time you need to reconfigure it.

Cheers,
--
Christopher Pollock,
io Networks Pty Ltd.
e. chris at ionetworks.com.au
p. 1300 1 2 4 8 16
m. 0410 747 765
skype: christopherpollock
http://www.ionetworks.com.au
In-house, Outsourced.


On Wed, Dec 14, 2011 at 9:46 AM, Tim G <tim at digitalpacific.com.au> wrote:

Hi Guys,

I am just wondering if anyone here has had any experience in getting Cisco 9951's working with anything that is not Cisco Call Manager?

I have managed to get the Cisco phone upgraded to the latest SIP firmware, cmterm-9951.9-2-2SR1-9.

The phone boots and pulls config files provided on my TFTP server.

However, the whole process fails miserably when the phone requests two files off the TFTP server, which do not exist. English_United_States/lk-sip.jar and United_States/g4-tones.xml.

I managed to get most of the files that the phone seemed to be requesting from CME_8.8_Locale.rar, however it appears that not all the files are actually there.

Infact, in this file, there is no lk-sip.tar, and the only file similar to g4-tones.xml is actually g3-tones.xml.

On the Cisco download page, there is the option to download a language pack for CME, po-locale-en_GB-9.2.2.1000-1.cop.sgn, however this file can not be extracted, and seems like it will only work on a CME box.

Has anyone had any luck getting these phones to work inside a non-cisco environment?

Any help or pointers in the correct location would be greatly appreciated.

Regards,
Tim

_______________________________________________
AusNOG mailing list
AusNOG at lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog


________________________________

This email, including attachments, is intended only for the addressee and may be confidential, privileged and subject to copyright. If you have received this email in error, please advise the sender and delete it. If you are not the intended recipient of this email, you must not communicate to others content that is confidential or subject to copyright, unless you have the consent of the content owner.