Aastra Releases Firmware Version 2.2.0
Submitted by aastra2 on Fri, 03/14/2008 - 12:33pm.
As someone has already spotted, Aastra has released an firmware upgrade for the 5i phones. The new firmware is available for download from the Aastra website , and a trixbox RPM will follow shortly.
Full details of the changes are in the release notes. But some of the highlights for trixbox users are:
- One button transfer using BLF or Speed dial
- Ability to stop the phone switching to the ringing line (so Xfer and Conf soft keys don't disappear)
- Registration status now shown in the WebUI to aid troubleshooting
- Secondary dial tone support via phone's dial plan
- Numerous XML improvements
Important bug fixes include:
- "Unknown Name" is no longer displayed for outgoing calls to numbers not in the directory.
- CT cordless handset MWI indication is now working again
- Corrected problems with some display names (ones containing non-alpha numeric characters) causing calls to fail
- Fixed resource leak when phone receives a lot of SIP message retransmissions
- Fixed various memory leaks in XML parsing
- Fixed crash after the phone looses connectivity to the server and goes into the "No Service" state.
Calls drops after transfer
Fri, 03/14/2008 - 1:34pm
Hi everyone
My client have some trouble with transfer (3 way call).
All the calls comes from ZAP/trunk (Digium 4FXO) the receptionist (she's in a ring group 600) she have the 226 and 230 ext and use 1 Aastra 9133i. She takes the call and use the Xfer button and got a dial tone then she dial the ext to transfer (let say the ext 225) and whe she reach the voicemail (the person at ext 225...) she decide to return to the customer (Zap Channel) by touch the line button and the call drop. Every time.
Here some info from un droped call... What do you thing
Executing [vmx@macro-vm:5] NoOp("SIP/226-b7702728", "Checking if ext 225 is enabled: ") in new stack
-- Executing [vmx@macro-vm:6] GotoIf("SIP/226-b7702728", "1?s-NOANSWER|1") in new stack
-- Goto (macro-vm,s-NOANSWER,1)
-- Executing [s-NOANSWER@macro-vm:1] Macro("SIP/226-b7702728", "get-vmcontext|225") in new stack
-- Executing [s@macro-get-vmcontext:1] Set("SIP/226-b7702728", "VMCONTEXT=default") in new stack
-- Executing [s@macro-get-vmcontext:2] GotoIf("SIP/226-b7702728", "0?200:300") in new stack
-- Goto (macro-get-vmcontext,s,300)
-- Executing [s@macro-get-vmcontext:300] NoOp("SIP/226-b7702728", "") in new stack
-- Executing [s-NOANSWER@macro-vm:2] VoiceMail("SIP/226-b7702728", "225@default|su") in new stack
--
-- Stopped music on hold on Zap/1-1
--
-- Recording the message
-- x=0, open writing: /var/spool/asterisk/voicemail/default/225/tmp/pjerf9 format: wav49, 0x8c0eef0
-- x=1, open writing: /var/spool/asterisk/voicemail/default/225/tmp/pjerf9 format: wav, 0x8c0aa78
== Connect attempt from '127.0.0.1' unable to authenticate
== Spawn extension (macro-dial, s, 7) exited non-zero on 'SIP/226-b7702728
== Spawn extension (macro-dial, s, 7) exited non-zero on 'SIP/226-b7702728
-- Executing [h@macro-dial:1] Macro("SIP/226-b7702728
-- Executing [s@macro-hangupcall:1] ResetCDR("SIP/226-b7702728
-- Executing [s@macro-hangupcall:2] NoCDR("SIP/226-b7702728
-- Executing [s@macro-hangupcall:3] GotoIf("SIP/226-b7702728
-- Goto (macro-hangupcall,s,6)
-- Executing [s@macro-hangupcall:6] GotoIf("SIP/226-b7702728
-- Goto (macro-hangupcall,s,9)
-- Executing [s@macro-hangupcall:9] GotoIf("SIP/226-b7702728
-- Goto (macro-hangupcall,s,11)
-- Executing [s@macro-hangupcall:11] Hangup("SIP/226-b7702728
== Spawn extension (macro-hangupcall, s, 11) exited non-zero on 'SIP/226-b7702728
== Spawn extension (macro-hangupcall, s, 11) exited non-zero on 'SIP/226-b7702728
== Connect attempt from '127.0.0.1' unable to authenticate
== Connect attempt from '127.0.0.1' unable to authenticate
-- User hung up
== Spawn extension (macro-vm, s-NOANSWER, 2) exited non-zero on 'Zap/1-1' in macro 'vm'
== Spawn extension (macro-vm, s-NOANSWER, 2) exited non-zero on 'Zap/1-1' in macro 'exten-vm'
== Spawn extension (macro-vm, s-NOANSWER, 2) exited non-zero on 'Zap/1-1'
-- Hungup 'Zap/1-1'
TB2.4 - TDM04B
Gareth
I just download the
Sat, 03/15/2008 - 11:15pm
Gareth
I just download the newest firmware and wanted to give a big thanks for getting the disappearing transfer button issue fixed. Also I love the new 1 touch BLF/transfer BLF works great. My only question is with all the memory leak fixes and such will the 5i phones now support over 50 BLF with the 536/560. We have been using SNOM 370 with there expansion module for most receptionist and would love to get back to Aastra but most of our applications require more than 50 BLF's
I like the new BLF/XFER
Mon, 03/17/2008 - 2:39am
I like the new BLF/XFER feature and the paging but the docs are lacking in places. The release notes illustrate the CF options on the phone but no-where does it mention the config options
sip line1forward all state:
sip line1 forward all number:
sip line1forward busy state:
sip line1 forward busy number:
sip line1forward no answer state:
sip line1 forward no answer number:
sip line1 ring number:
Also shouldn't the commands follow the same basic layout? E.g. line1forward vs line1 forward?
50 BLF limitations
Tue, 03/18/2008 - 5:00am
Hi, Gareth,
I got the following reply from Aastra's Support service:
Unfortunately the new firmware still won't give you access to program more than 50 BLF keys. The phones simply could not handle that much traffic all at one time. I realize this may seem to make the addition of a third side card almost obsolete but the physical limitations of the phone dictate the use of the side cards so only 50 of the keys can be programmed as BLFs.
-------------
Well, most of my applications require 55i with > 50 BLF, but anything I can do, except migrate to SNOM? upgrade to 57i, 560M, or any memory upgrade of my existing 55i.
Most of my customer wants 5i series with 2-3 sider, but the limtations of 50 BLF really give us a lot of trouble NOW.
I'm not currently aware of
Tue, 03/18/2008 - 8:24am
I'm not currently aware of any plans to increase the number of supported BLFs past the 50 mark. The changes that went into 2.2.0 were more for stability improvements than trying to up the number of BLFs we can support.
However all our future changes are driven from customer requirements. So if you want us to support more than 50 BLFs then you should get the support team to raise a feature request on your behalf or talk to your sales rep about it.
Out of curiosity, how many BLFs do you need? What's your typical and maximum numbers?
When will we see a new f/w
Tue, 03/18/2008 - 8:50am
When will we see a new f/w release for the 9133i? The last one was in June and I know there are a few outstanding issues. Specifically of concern for me are:
- improved echo cancellation
- addition of XML functions that allow for the control of the light states based on events/etc.
BLF limitations with Aastra 5i series
Tue, 03/18/2008 - 9:51am
Gareth,
I realised it could be some memory overflow issues.
I tried 2.0.1 and 2.0.2 today, all BLF works but it locks up the phone very frequently.
I will try 2.1.0 (if all BLF works) and do a regular reboot script everynight.
Not really sure when this limtation started 2.1 or 2.1.1, no idea!
We choose 5i series and 536/ 560M series, because we are very happy 9133i, 480i performance in last 2-3 years. I have an experience with 55i + 1x536M about 6months ago. (Firmware 2.0.1-2000) and eveything seem fine. Thats why we are more confident with more 536M + more BLF deployed this time.
Besides, AASTRA is the only available product could provide more than 100+ prog. key.
It's best for receptionist phone I seen so far. SNOM, Linksys, and Thomson only provides around 32-64 keys.
GXP-2000 provides 108 (2x56) keys. - but GXP series were not stable enough to a enterprise application. Their sound, outlook, security and User Interface were horrible.
Most of my clients are looking for solution to migrate to VoIP from keyline/ traditional PBX.
I am expecting at least 72 (2x36) exp. prog. keys with AASTRA, norm installations. 100-120 keys., sometimes, upto 150.
If you are just looking for
Tue, 03/18/2008 - 7:47pm
If you are just looking for the new firmware
http://www.aastratelecom.com/cps/rde/xchg/SID-3D8CCB6A-F9178B6F/0...
I installed the new firmware
Wed, 03/26/2008 - 10:18am
I installed the new firmware last week but it doesn't seem to have resolved the problems with BLFs that I am having. When a good number of BLFs are active (a call group ringing for example) the phone sometimes loses track and leaves the lights lit. This cause problems for the receptionist as she cannot use the extension button to transfer a call (it tries directed pickup instead)
This problem is causing me severe cash flow problems :(
The new Admin Guide yet
Fri, 03/28/2008 - 10:42am
seondary dial tone
Mon, 03/31/2008 - 7:06am
I manage to do the dial plan with secondary dial tone, it's something like e.g.
tone set: UK
4xx|5xx|9;xxxxxxxx|x+#
the primary and secondary dial tone are the same by default.
I read through both ther Admin Gudie and release notes earlier,
I can't find anything about secondary dial tone in Web UI and the config. files.
I wish to have something like:
Europe dial tone; and UK secondary dial tone.
Firmware Version Confusion
Wed, 08/13/2008 - 1:20pm
The Yum trixbox RPM page for 2.3.0 of Aastra firmware says:
>Summary
>Aastra Telecom Firmware for the 5i series of VoIP phones, the 9480i, 9480iCT and 9143i >VoIP phones and the 480i, 480iCT, 9133i, and 9112i VoIP phones
However, from the threads I've red, it sounds like 1.4.2.3 is the latest for the 9112i and the 9133i.
Am I wrong in assuming that 2.3.0 is currently only for the 5i series IP Phones, 9480i, 9480iCT and 9143i phones:?
I'm thinking that eventually this firmware will work on all but currently only on the newer/better phones.
Anyone with firsthand knowledge regarding this--please enlighten us that do not know.
Ahh, the changelog on the
Fri, 08/15/2008 - 12:13pm
Ahh, the changelog on the yum server only shows the last 3 updates to the package...
the next one down says
Tue Nov 27 14:00:00 2007 Aastra Support
- Release 1.4.2.3000 for 480i, 480iCT, 9133i, and 9112i.
- Release 2.1.1 for 5i series IP Phones.
- See www.aastratelecom.com for release notes
so the 2.3.0 rpm package contain 2.3.0 for the 5i series of phones and the 9480i(CT) 9143 and 1.4.2.3000 for the classic phones.
The RPM release number usually corresponds to the 5i series lastest firmware. but not always. eg. in the near future we will be releasing 1.4.3 and the rpm release number may be updated to 2.3.1 even though the 5i firmware hasn't changed... have to think thi s thorugh though :)
To answer you question, the 480i(CT),9133i, and 9112i will never use the 2.x software. They are not capable.
Cheers
Kieran
Member Since:
2006-10-05