I’ve been fiddling with an Avaya 4621SW IP phone recently, and I wondered if it would be more appropriate to pass settings to it via DHCP options, rather than editing the 46xxsettings.txt file that it always downloads via TFTP.
Previously I had the following in my 46xxsettings.txt file
SET SIPDOMAIN glasgownet.com
SET SIPPROXYSRVR voip.vpn.glasgownet.com
SET SNTPSRVR pool.ntp.org
In an effort to transition this to DHCP, after a few minutes of experimenting this was the final outcome that went in to the top of my Debian dhcpd.conf file. It handles the Option 176 that Avaya phones use to get parameters passed to them.
option space Avaya;
option Avaya.custom code 176 = string;
option Avaya.custom “SNTPSRVR=pool.ntp.org,SIPPROXYSRVR=voip.vpn.glasgownet.com,SIPDOMAIN=glasgownet.com”;
The last line there contains my SIP server settings as I’m using the SIP software stack on the phone. Equally, I’ve tested the following with the H323 firmware, and it works too
option Avaya.custom “MCIPADD=18.104.22.168,MCPORT=1719,TFTPSRVR=172.24.32.1,L2Q=1,L2QVLAN=10”;
Now, http://www.voip-info.org/wiki/view/Avaya+4602+configuration states that the 4602s can be configured independently by manipulating sip_
OK, so I got to borrow an Avaya 4610SW from work, as it would be faster to play with firmware via TFTP on my home network than it would be when using the business network. These are some notes…
Turn off 802.1q – my network doesn’t do tagging.
Grab the latest firmware from ftp://ftp.avaya.com/incoming/Up1cku9/tsoweb/ip_telephone/071008/ – in this case it was plain old 46xxH323_071008.zip, and extract into TFTP root, or provide symlinks with something like cd /srv/tftp/ ; ln -s Avaya/021612/* .
Turn on the phone, and it collects the following from TFTP…
MarÂ 6 23:01:59 senior in.tftpd: RRQ from 172.24.32.29 filename 46xxupgrade.scr
MarÂ 6 23:01:59 senior in.tftpd: RRQ from 172.24.32.29 filename 46xxsettings.txt
MarÂ 6 23:02:05 senior in.tftpd: RRQ from 172.24.32.29 filename b10d01b2_9.bin
That’ll be the bootloader getting downloaded (or Bootapp, as Avaya like to call it), then saved to flash. It then rebooted, updated with BIG SCARY WARNINGS, rebooted again, and then it picked up these…
MarÂ 6 23:05:02 senior in.tftpd: RRQ from 172.24.32.29 filename 46xxupgrade.scr
MarÂ 6 23:05:03 senior in.tftpd: RRQ from 172.24.32.29 filename 46xxsettings.txt
MarÂ 6 23:05:06 senior in.tftpd: RRQ from 172.24.32.29 filename a10d01b2_9.bin
which were saved to flash again, rebooted, Updated, rebooted, and then off it went.
So, upgrades went smoothly, whilst staying on the H323 featureset. Point proven for the boss, and should be easy to deploy the new firmware after some more testing. I now want to play with SIP…
The above file includes SIP in the downloaded zip file, but APPARENTLY… the SIP firmware is chosen based on the SIG parameter in 46xxsettings.txt. So, essentially, to enable SIP, you just have to enter SET SIG 2 into 46xxsettings.txt and let 46xxupgrade.scr work the magic. However, in my experience, this failed miserably. The phone just carried on blindly using the currently loaded firmware. To manually change the phone into SIP mode, you have to hit Mute, then dial SIG (744), and then hit #. It will then prompt you to change the SIG value. Press * to toggle between H323 and SIP. When ready, press #, and # again to save the setting. After is saves, you get the option to restart the phone. Do so, and it will pick up the new firmware from the TFTP server.
After a short delay whilst it loads s10d01b2_2_2.bin, it’s off and running. As long as you’ve provided some basic SIP details in 46xxsettings.txt, it will prompt for a SIP username and password after a short delay. I believe this can also be automated based on MAC address, according to some conjecture and hearsay on the internet…
The other evening I busied myself with tweaking Asterisk to do some more geeky things. One such item was where I configured it to send a message to my Jabber account every time there was a call to a particular extension. Great for call logging, integration, and general user friendliness. If I was so inclined, it could message a Yahoo, MSN, ICQ, or AOL account through the Jabber platform to inform me of a new call. How rather flexible.
Last week I ‘accidentally’ bought a Cisco 7911 phone on Ebay. My bid was low, the device was missing a few bits, but I still thought I wouldn’t get it.
Suffice to say… I’ve just written this piece on how to load the SIP firmware onto a Cisco 7911 phone. The procedures are covered elsewhere, but I thought I could compress it into a format that’s slightly easier to understand. Hope it makes sense. 🙂
Whilst I’m at it, if anyone can email me a working SIP based cnf.xml file, it would be greatly appreciated. Getting the firmware onto the phone is easy… configuring it for Asterisk seems to be a completely different ballgame.
It’s time, and Ofcom are beginning to enforce the latest revision to General Condition 4, whereupon VoIP providers must, where technically feasible, provide location information for their VoIP users. In order to aid emergency services, they will transmit details of your fixed line location to the recipient when you make an emergency call.
Obviously this is quite an important thing, and not something you want to get wrong. So take a few moments now to ensure that the details held by your VoIP provider are the correct details.