Comments on: Configure Cisco IP Phones with Asterisk

By: Tyler Winfield

Tyler Winfield — Tue, 24 Aug 2010 21:20:01 +0000

@Richard, Thanks for the tip, you are correct that there is an "error" in the XMLDefault.cnf.xml file but it seems to be an encoding error and not so much a syntax error. in the tag, the quotes around model="7960" aren't always encoded as quotes, seems like some character encodings don't like it. Try re-typing the line and saving the file again it should re-encode the text into a more friendly version for whatever OS you are on.

By: Mc GRATH Richard

Mc GRATH Richard — Tue, 24 Aug 2010 20:43:19 +0000

Before test onto Trixbox, I have found a mistake on XMLDefault.cnf.xml on line column 21 specifically on loadInformation436.
I don’t know if these will cause error during installation, configuration or operation.

By: Tyler Winfield

Tyler Winfield — Tue, 24 Aug 2010 03:05:54 +0000

@wzence
Try not using an SEP.cnf.xml file at all. It isn’t actually required for the 7940/7960 models and may get you further.
Tyler

By: wzence

wzence — Tue, 24 Aug 2010 01:47:27 +0000

Hi Tyler Winfield

I’m trying to upgrade Cisco 7940 from SCCP firmware P00307010200 to SIP P0S3-8-12-00 using the configuration files provided.

It keeps getting stuck after reading the SEP.cnf.xml file.

The TFTP error log that keeps repeating is

TFTPServer.Service.ConnectionPool – In connection pool there are 7 free connections and 0 occupied connection

Do you have any idea whats happening? By the way, do you know if Cisco 7940 SCCP firmware P00307010200 is upgradable to SIP?

2010-08-24 09:38:42,618 [3] INFO TFTPServer.Service.PacketParser.RequestPacket – Received request packet, file name: SEP00192F5ED307.cnf.xml, transfer mode: binary, block size: , tsize: , timeout:
2010-08-24 09:38:42,618 [8] INFO TFTPServer.Service.ConnectionPool – Beginning processing GET request from 192.168.10.35:49848, file name: SEP00192F5ED307.cnf.xml, transfer mode: binary,
2010-08-24 09:38:43,446 [8] INFO TFTPServer.Service.ConnectionPool – In connection pool there are 7 free connections and 0 occupied connection
2010-08-24 09:38:44,446 [8] INFO TFTPServer.Service.ConnectionPool – In connection pool there are 7 free connections and 0 occupied connection

By: Tyler Winfield

Tyler Winfield — Wed, 18 Aug 2010 20:25:34 +0000

@Stone
If you don’t get anywhere with that suggestion, I can give you a hand with some investigation to figure out the configuration files.

It appears the 3911 shares a codebase with the Cisco 7912. This should mean it follows similar boot / startup processes. I’ve never seen or used a 3911 but if its similar to a 79XX model, I’m sure we can find something to either make it work on confirm that it cannot work with asterisk.

By: Stone

Stone — Wed, 18 Aug 2010 08:47:11 +0000

To Tyler Winfield

Thanks, I’ll try today. Later I will write that in the end succeeded.

By: Tyler Winfield

Tyler Winfield — Tue, 17 Aug 2010 18:49:19 +0000

I’ve heard these do work with Asterisk just fine. From what I can find, it looks like it references SIPDefault.cnf. May want to try using the 7940 configuration file (somethings will need modification i expect; the firmware image for example) as the starting point. If you do get it to work, I would very much like to hear the steps necessary and add them to this document (with permission of course). If I find anything further thats more definitive I will post it as well.

By: Stone

Stone — Tue, 17 Aug 2010 17:09:15 +0000

Is anybody know how to connect Cisco 3911 to Asterisk (config files, ets.)?

By: Sascha Ferley

Sascha Ferley — Fri, 30 Jul 2010 22:44:00 +0000

@Sean Simpson
Been also trying right now to get the Cisco9971 to play nice.. I managed to get the g-sip.jar and the tones.xml file in case you need, but those files have zero impact on registration it seems.
I have access to a Callmanager (CUCM 8.x) and been pulling files from there, but nothing.. won’t register.. i wonder if there is something about the: field that needs to be made to work.

By: Tyler Winfield

Tyler Winfield — Tue, 13 Jul 2010 15:29:59 +0000

@Monideth
You are quite right. this 12 character maximum is true for all of the XML configured models that I’ve tested so far. It also seems that the IP Communicator cannot handle spaces at all in the phoneLabel. I haven’t confirmed this on the 7970 but expect this is true there as well as it uses the same firmware. (didn’t think to test this at the time and don’t have a 7970 available at the moment)

Thanks for the note. I’ll add that in somewhere as well permanently, that could probably be easy to miss for many people.