[eric]

Linksys just released firmware version 5.1.10 for the SPA922 and SPA942 phones.

The new firmware release includes new features and bug fixes.

New features include:

• converting character encoding to unicode;
• displaying the proxy name under the phone status GUI;
• saving and displaying the last call RTP information on the status menu;
• adding DHCP option 60 Vendor Class ID information to the DHCP request;
• editing 9th cadence option;
• ordering three prefered codecs for each extension;
• incoming page audio mixes with current call audio.

Bug fixes include:

• muting spa942 speakerphone in three-way conference call does not block audio between the other two parties;
• displaying off hookchoose softkey *code correctly, *69 instead of *6;
• escaping occurrences of # in the outbound INVITE dial string;
• preventing string overrun during translation
• removing excess syslog error messages when the dictionary is not loaded during bootup;
• displaying characters g, j, p, q, & y correctly on the LCD display;
• changing network mask setting from the display does not work with foreign language settings;
• including annexb=yes/no in SDP INVITE response;
• reporting incorrect full/half duplex value in CDP packets;
• configuring the SCA Barge In Enable parameter.

Linksys SPA922 Firmware

Linksys SPA942 Firmware

[humba3]

Actually, there's but one firmware

[Bheavner]

Sorry - duplicate post - but I wanted it to be on the phone firmware page as well for other searches.

I'm in the midst of configuring a new system (SPA400, SPA9000, SPA922 & 942 phones) and I upgraded the SPA9000 to v5.1.8 and the phones to the also newly released 5.1.10. When I tried to use the spa9000 setup wizard 1.1.0.6 to continue my configuration, it would no longer work properly. I didn't make specific note of the errors, but it would not connect with the phones to configure, and seemed to just be flaky. I downgraded the SPA9000 to 5.1.7 and the phones to 5.1.7, and I was able to keep working.

I'm ok with this configuration, but does anybody know if there is an updated setup wizard available (or coming soon) that will work with the new firmware? Or am I just doing something wrong?

[humba3]

escaping occurrences of # in the outbound INVITE dial string;

That "fix" just broken my trunk seizure prefixes.. I can't help but think that

INVITE sip:%23123@192.168.1.4:6060 SIP/2.0

is incorrect and

INVITE sip:#1123@192.168.1.4:6060 SIP/2.0

would be correct. After all, # is both part of 7 bit ASCII (and SIP is UTF8) and # has been a part of telephony for way longer than SIP.
Time to study the RFC once more to see if the %23 is really what it ought to be