Lates firmware of Aastra 5xi phones

[Christoph]

We are using 3cx V6 with Aastra 57i and 53i. Everything works fine so far. We tried to upgrade (do backup of config, removed 6.x and did a fresh install of v7 with IIS, restore of config) to V7.

After upgrade and adapting the config urls send via dhcp to reflect changes in IIS, the following happend: The Aastra phones registered successfully on 3cx, but dropped out about 60 seconds later and started to reboot and reregistered again. This repeats all day long.

We were unable to figure out the problem. The config url and proxy seems to be correct and as the server log shows the phones are registering on 3cx but drop out shortly after. The aastra have the latest firmware on - and it's the same config as in V6 - which still works well?

Any ideas what could be the issue?

Thanks
Christoph

 

[NWTech]

Re: 3cx install of 7.x doesn't work with Aastra 5xi phones

This is a known issue with Aastra as of 2 days ago. It is a problem in the 2.3 and 2.4 firmware. It does not happen with 2.2.0.116. I have confirmed this for a couple days. When the phone registers the PBX sends back a no answer and the phone reboots. I have trouble tickets into both 3cx and aastra to resolve the issue. If you are not dependent on webapps you can just role back to 2.2.0.116 and roll forward the repair is released.

 

[Christoph]

Re: 3cx install of 7.x doesn't work with Aastra 5xi phones

ok, thanks - I didn't find your original post. So let's see who moves first, Aastra or 3cx...

cheers,
Christoph

 

[nb]

We cannot reproduce this issue here in our test labs. We have all sorts of aastras.

Can you specify the exact model and firmware you are using please?

For example - one of our aastras is 57i version 2.4.0.96

Also the exact description how this crashes. Normally when it crashes it is a bug in the firmware. I had crashes in the past with aastra and they were always resolved with a firmware upgrade.

 

[Christoph]

57i Revision 0
Firmware Version 2.3.1.26
Firmware-Release-Code SIP
Boot-Version 2.0.1.1055
Datum/Zeit Aug 26 2008 23:13:58


This is how the log looks like, as mentioned the phone registers with 3cx but drops shortly after to reboot...

SipEngine crashed on 10/12/2008 at 8:29:50
SipEngine crashed on 10/12/2008 at 8:27:29
SipEngine crashed on 10/12/2008 at 8:25:47
SipEngine crashed on 10/12/2008 at 8:23:57
SipEngine crashed on 10/12/2008 at 7:57:14
SipEngine crashed on 10/12/2008 at 7:55:34
SipEngine crashed on 10/12/2008 at 7:53:59
SipEngine crashed on 10/12/2008 at 7:52:19
SipEngine crashed on 10/12/2008 at 7:50:40
SipEngine crashed on 10/12/2008 at 7:45:47
SipEngine crashed on 10/12/2008 at 7:43:37
SipEngine crashed on 10/12/2008 at 7:41:26
SipEngine crashed on 10/12/2008 at 7:39:16
SipEngine crashed on 10/12/2008 at 7:37:6
SipEngine crashed on 10/12/2008 at 0:2:32
SipEngine crashed on 10/12/2008 at 0:0:28
SipEngine crashed on 9/12/2008 at 23:58:23
SipEngine crashed on 9/12/2008 at 23:56:17
SipEngine crashed on 9/12/2008 at 23:54:7
SipEngine crashed on 9/12/2008 at 23:52:2
SipEngine crashed on 9/12/2008 at 23:50:1
SipEngine crashed on 9/12/2008 at 23:48:0
SipEngine crashed on 9/12/2008 at 23:45:50
SipEngine crashed on 9/12/2008 at 23:43:40
SipEngine crashed on 9/12/2008 at 23:41:30
SipEngine crashed on 9/12/2008 at 23:39:19
SipEngine crashed on 9/12/2008 at 23:37:9
SipEngine crashed on 9/12/2008 at 23:35:6
SipEngine crashed on 9/12/2008 at 23:33:3
SipEngine crashed on 9/12/2008 at 23:31:0
SipEngine crashed on 9/12/2008 at 23:28:55

 

[nb]

Yes

But what happens exactly? The phone is idle and it happens? Do you do a blind transfer, answer a call? You have to be more specific and give me more details because I repeat - I cannot replicate this here.

I can get no information from a repeated log entry: SipEngine crashed on 10/12/2008 at 7:55:34
I know its crashing because you are telling me so.
Hence we need more verbose logs.
Syslog the aastra and add a a higher debug level.
First modify the following to 63 instead of 1

LINEMGR 63
SIP 63
DIS 63

And send the traces again

But before this upgrade to 2.4 firmware. I cannot help you on this firmware you have at the moment

Nicky

 

[Christoph]

will try firmware upgrade first, sorry didn't get that there is a new 2.4 release already..but as it is our production system it will take a while to get it back up on 7.x to reproduce. will also do the syslog.

 

[NWTech]

Our restart happens when the phone is idle sitting on the bench. We have 1 - 57i, 1 -57iCT and 2 - 55i that all started restarting after upgrading to 7.0. Here is Aastra repsonse after looking at all of the logs that you have asked for and they where able to duplicated it in the lab....

Hi Ryan,
We could finally identify the main cause of the restarts. The source of the problem is because of RFC violation by your server.
Based on RFC3262 page 65 we have:
The registrar returns a 200 (OK) response. The response MUST
contain Contact header field values enumerating all current
bindings. Each Contact value MUST feature an "expires"
parameter indicating its expiration interval chosen by the
registrar.
As per the RFC the “200 OK” response for registration MUST contain “Contact” header which was missed in the SIP message came from your server. Please communicate this with your service provider to have a fix.
For your convenience I’ll close this ticket within 48 hours if I don’t hear back from you on this, while we will look into implementing a better way to handle this on our side rather than the phone being restarted.
Regards,
Bram Biria
Tier 2/3 VoIP Support Engineer
Aastra Telecom Inc.

I hope this helps 3cx maybe fix the repsonse from the 3cx server.

 

[Christoph]

same here, the phone reboot in idle state...

tnx
Christoph

 

[William400]

Hi

We are working on this with Aastra.

We shall post an update as soon as this is at hand.

 

[mcallen]

anyone have an update on this? These phones have some buggy little annoyances that I suspect have been fixed in newer firmware but we have to run the 2.2.x because of the v7 reboot issues with these Aastra phones. Thanks for any info or update!

 

[NWTech]

That is a great question. Are we going to see a repsonse on this issue?

 

[STCJeff]

I know I'll jinx myself by saying this, but we have 8 57i phones here running 2.4.0.96 on v7 with no restart issue (they've been running great for about 2 months now). Maybe there is a specific feature you're using on the phones that is not working correctly with 3CX? Ours are set up pretty basic, but seem to work fine.

 

[nb]

Hi Guys

We are working on this.
We managed to reproduce it with the very latest aastra firmware 2.4.1.37 on 51i and 55i. We are checking out what the problem is.

In the meantime it would be better to roll back to a previous firmware - the earlier 2.4.0 firmware would be enough. the problem does not exist in that firmware.

 

[worksighted]

Im pretty sure you need to go back to at 2.3.x. We were having the issue with the earlier 2.4 release as well.

Mike

 

[nb]

Hi - We have an update on this.

We are planning to release a new update of the 3cx phone system which will have a fix for this. Sometime this week for sure we will upload.

Thanks for your patience and contribution guys to fix this issue.

 

[goodwija]

I've now tested the new build with Aastra phones and it is all looking good so far - no more rebooting. Greeat news! Thanks 3CX