Aastra 57i/57iCT's Not registering

[rushter]

I have a trouble ticket in with Aastra right now and they have copies of our log files to see what is going on but this problem is odd.
We have three 57i's and one 57iCT and they are not staying registered with Asterisk.
Anyone ever had this issue? Anyone know of a fix? Hoping Mr. WM might have some say in this.
I also have four Grandstream GXP2000's on the system and they are working like a charm.

Edit: We purchased the Dell SC440 and were going to do the Orgasmatron ][ install and after two failed attempts with it started everything up with PiaF and things are going smoothly. Sorry Ward, we were having issues with IPConnect on the O2.
Got the pbx setup done, got the phones connected with the configs all set up with no major issues and then we had the above happen. I am going to go ahead and attach the log file for one of our Aastra's to see if anyone can crack the issue.
Asterisk registration time is set to 120 and on the phones, it was originally 0, we tried 60, 120 and 300 and still have the 'No Service' on the display of the 57i's randomly.

 

[rushter]

I thought for sure that I might be able to get some help on this. I am awaiting a call back from Aastra tech support to see what they have to say. So many people have mentioned this before and I have yet to see any solutions. Grrr....

 

[Phone_User]

Do you have the latest Firmware for the 57i/57iCT? If not download that first and install.

Then run setup aastra-xml-script. Then go to your TFTPboot dir on your server and delete all the .cfg files. Then go to /var/cache/aastra and delete all the .session files.

Then in /var/cache/aastra delete all the entries in the startup_asterisk.cfg file.

Reboot the phones and see if that helps.

I had the same problem, did the above and all was good again.

Rob

 

[gregc]

What kind of trunks? ZAP, IAX, SIP?

Who is the service provider?

 

[jmullinix]

He has all 3. The Aastra phones will not stay registered with the PIAF server. Grandstream phones on the same server and on the same lan are working perfectly.

 

[gregc]

Try disabling the SIP trunks and see if they stay registered.

If they do, search the help forum here for similar problems. There have been a few fixes that have worked for a few people. My only fix was to dump my SIP trunks. Our primary is a PRI, so no big deal. Back up is IAX through PIAF. Haven't had the problem since.

 

[jmullinix]

Greg,

I had him register one of the troublesome phones to my server here in GA. It appears to stay registered just fine. I have a bunch of SIP trunks on this box. I am starting to smell a bad PIAF/Asterisk load or 1.4.21.2 has an undiscovered bug. I am running 1.4.20 here.

 

[gregc]

I would still try to disable his SIP trunks to check and see. I'd bet his problem gets resolved. It is likely his server has some settings that are set that causes the problem whereas your server doesn't.

Check the posts here about this issue. It may just be a DNS issue on his box. I believe this post is related to his problem.

 

[cjkeeme]

I had this problem too. I have an office full of Aastra phone (40). I have a mix of 9112i, 51i, 53i, 57i, and 57i CTs in this environment.

I was always receiving no service announcements. To remedy the problem I set the qualify much higher.

I set the qualify to

10000|yes

and have not seen a 'no service' error again.

One thing I did notice when the 'no service' was appearing was that I did in fact have service. Calls came in and out just fine. Is this true in your circumstance?

 

[rushter]

Fixed? - For now...testing to see.

After sending our syslog to Aastra and getting them to see what they could find out we received a reply that basically said that they could not really determine the cause from the logs. They explained it to me and I did my best to understand it - not that I really understand it yet but anyways...
The fix that has been working for us for almost 24 hours now is that in the Advanced Settings section under Global SIP for the phone there is a setting called Transaction Timer that is set to 4000 by default. Aastra suggested that we set that to a higher number (they do not want me to say the number as it is only to test right now) as a possible workaround. Well, it has been working. They only issue that they said that we should worry about is that it would cause a lot more un-needed traffic on the server and it might affect server load. Not sure that it will be much of an issue here as we are a small business and seriously doubt if we will ever have more than 3 or 4 phones going at the same time.
I do want to thank John Mullinix from Cohutta.com - great mentor for anyone out there needing some guidance on all of this.
I want to also apologize to everyone who responded here with possible fixes as I did not try any of what was suggested only because I really needed to hear it from Aastra first and if they could not do anything I would go the other routes.

One thing I did notice when the 'no service' was appearing was that I did in fact have service. Calls came in and out just fine. Is this true in your circumstance?

This was happening before - service was still actually there when any one of the extensions was picked up. We even monitored it dropping the registration in the midst of a call. But the call itself was not dropped.

 

[cjkeeme]

What was the Transaction Timer value you set to? I would like to try this fix. Thanks.