I have to say it was a painful process…it took me about an hour of tweaking…mostly my own fault…hehe. Most of you guys have seen a Cisco phone at some point. If you’ve ever watched a show on Fox, you most likely have seen one…hehe They make great phones, and not just for CallManager. You can flash these guys from skinny to SIP. The process isn’t that bad once you get the steps down. Here’s what I did.<\/p>\n
You will first need two things:<\/p>\n
When you go to download your firmware, the zip will be named something like P0S3-8-12-00.zip. You want to make sure that the package is listed as for 3rd party SIP call control environment<\/em>. Extract these to a folder somewhere. <\/p>\n XMLDefault.cnf.xml<\/strong>*TFTP Server<\/H3>
\nI used tftpd32<\/a>. This is a great windows prog that will run a DHCP server, TFTP server, syslog server. Using this, set the files folder to that of the firmware folder we just extracted.<\/p>\n*DHCP Server<\/H3>
\nThis is optional because you can simply set all of this up statically on the phone. I chose to use it. In the DHCP server section of tftpd32, fill out the normal information and add option 66 as the IP of your TFTP server.<\/p>\n*Create Config Files<\/H3>
\nSEP001111111111.cnf.xml<\/strong>
\nGrab the MAC address off of the back of you phone and create a file by combining SEP *phones mac* .cnf.xml. The contents should resemble the info below:<\/p>\n<device>\r\n<loadInformation model="IP Phone 7960">P0S3-8-12-00<\/loadInformation>\r\n<\/device><\/code><\/pre>\n
\nThis guy will need to be tailored to whatever the firmware matrix page says. The loadInformationX section needs to correspond to your version of SIP. X = version number.<\/p>\n<Default>\r\n <callManagerGroup>\r\n <members>\r\n <member priority="0">\r\n <callManager>\r\n <ports>\r\n <ethernetPhonePort>2000<\/ethernetPhonePort>\r\n <mgcpPorts>\r\n <listen>2427<\/listen>\r\n <keepAlive>2428<\/keepAlive>\r\n <\/mgcpPorts>\r\n <\/ports>\r\n <processNodeName><\/processNodeName>\r\n <\/callManager>\r\n <\/member>\r\n <\/members>\r\n <\/callManagerGroup>\r\n <loadInformation8 model="IP Phone 7960">P0S3-8-12-00<\/loadInformation8>\r\n<authenticationURL><\/authenticationURL>\r\n <directoryURL><\/directoryURL>\r\n <idleURL><\/idleURL>\r\n <informationURL><\/informationURL>\r\n <messagesURL><\/messagesURL>\r\n <servicesURL><\/servicesURL>\r\n<\/Default><\/code><\/pre>\n*Loading Image<\/H3>
\nYou will want to watch the log tab on the TFTP server to see which files the phone is requesting. It appears that it requests the file names differently depending on what version it is currently running.<\/p>\n