Home » Forums » Vendor Forums - Certified » Aastra endpoints

Phones Constantly Going Offline

andrewvanh
Posts: 16
 Member Since:
2009-01-21
Submitted by andrewvanh on Thu, 04/29/2010 - 7:38am.

I have about 30 9480i and 9143i phones on a dual core system that is very under-utilized. The phones are all on a DHCP network with a 60 minute lease time. It seems like every so often some of the phones will show no service on the display for about 30seconds to a couple minutes. What is strange is the phones can still place or receive phone calls during this time. I have even been on the phone when I have noticed the light on the phone shows solid like it has no service.

The FOP is trixbox also shows that the phone is dicsonnected.

I don't know if this has anything to do with the phone not getting a response from the DHCP server or the trixbox server. Is there any suggestions of what to try?

I have run TOP on the server and watched it for a while when this problem was occuring. I never see the values spike past 0.35. Normally they are in the 0.02 range for all three. As I said, the server is very powerful and under-utilized. Trixbox version is 2.6.2.3. All phones have the newest firmware.

‹ New Aastra XML scripts for Trixbox CE Aastra 57i stuck booting ›


Chris1.berry
Posts: 33
 Member Since:
2008-03-19
60 minutes is a really short
Thu, 04/29/2010 - 3:53pm

60 minutes is a really short lease time. Could try setting that up past 24 hours, the default lease time on a microsoft server for a wired network is 8 days.



andrewvanh
Posts: 16
 Member Since:
2009-01-21
Yes it is really short. I
Fri, 04/30/2010 - 8:54am

Yes it is really short. I am doing some work on the DHCP and want settings propogated quickly. I am going to increase this, but still am concerned about the issue. I don't know if it is anything to do with DHCP. I do notice that they obtain a new lease about the same time they go offline.



andrewvanh
Posts: 16
 Member Since:
2009-01-21
Still no dice. I set some
Thu, 05/06/2010 - 10:12am

Still no dice. I set some to static IP. I am having issues with both DHCP and static. The error on the phone is a 408 under status. I did find out that it has nothing to do with DHCP leases. Normally my ping times to the phones are around 25ms. When I see a phone go offline I see it go to 150ms for that small amount of time. Below are the settings from the phone.

Registration Failed Retry Timer 1800
Registration Timeout Retry Timer 120
Registration Renewal Timer 15
BLF Subscription Period 600
ACD Subscription Period 3600
BLA Subscription Period 300
Blacklist Duration 300



PBXMatt
Posts: 13
 Member Since:
2006-06-06
I have the same problem on two systems
Fri, 05/07/2010 - 1:14pm

I have 1 Trixbox 2.6.2.3 system that has been in service for four years. It has 1 Aastra 57i, 2-9133i, 1-480iCT, 1-Linksys SPA-2102, 1-SPA-3102 on the local net, and 1-480iCT, 1-9133i at a remote site. I also have 2-Linksys SPA-2102 at two remote locations across the US. All the Aastra phones on the local net that were configered by the endpoint manager work fine. The local and remote Linksys ATA's work with no problem. The two remote Aastra phones (at one location) that I could not use the endpoint manager, have the problem of going in and out of service all the time. I can still use the phone to make calls out even if the red light shows no service, but if the red light is on (no service), I can't receive calls. If I bring the remote Aastra phones to the local network and program them with the endpoint manager, I have no problems. At first I thought it was a problem with the remote site untill I installed a new Trixbox system 3 months ago.

I installed a new Trixbox 2.8.0.4 system with 1-Aastra 6757i, 1-6730i, and one Linksys SPA-3102 on the local network. I have one SPA-3102 at a remote site. I was not able to program the Aastra phones with the endpoint manager, but with the default settings and some local programing for entension number, time and password, the two Aastra phones go in and out of service all the time. I am using the same registration timeout and retry as andrewvanh above. I have changed the registration timers to different times with no results. The Linksys systems work with no problems. I think when you use the endpoint manager, it makes changes to the phone that you don't see using a web page to program the phone. I would like to know what settings this is.

andrewvanh, did you use the endpoint manager?

Thanks,

Matt



busster8
Posts: 388
 Member Since:
2006-06-25
Aastra Phones
Fri, 05/07/2010 - 1:26pm

Had the same problem. Ended up installing older software and the problem went away.



PBXMatt
Posts: 13
 Member Since:
2006-06-06
What firmware or software version are you using?
Fri, 05/07/2010 - 3:34pm

I am using firmware 2.5.0.82 on the Aastra 57i which works fine on the local network. I use 1.4.3.23 firmware on the 480iCT and 9133i at the remote location which are my problem phones. I also have a 480iCT and 9133i with the same firmware as the remote location on the local network and I have no problems with the local phones.

My second system uses firmware 2.5.1.41 for the Aastra 6757i and 6730i and the two phones are my problem phones for the second system.

busster8, what phone do you have and what firmware version did you use to solve the problem?
Did you use the endpoint manager to program the phones?

I think using the endpoint manager solved the problem with my Aastra local phones. I also think that the default settings are different in the different firmware versions. I always start with the default firmware and change only the settings that need to be changed. But if the new firmware version has changed a default setting from the old, this could be causing my problem.

What do you think/



andrewvanh
Posts: 16
 Member Since:
2009-01-21
Firmware and Model
Tue, 05/11/2010 - 12:50pm

I have the 9480i and 9143i. Version 2.5.3.2002. This was the newest version off the Aastra website. They are also programmed using the xml script to generate the config file. I would love to hear one of the Aastra guys chime in on this.

The only other thing that has changed on my network is I did update the phones from a firmware that was about 1-2 years old.



SkykingOH
Posts: 9541
 Member Since:
2007-12-17
I just helped a client with
Tue, 05/11/2010 - 3:36pm

I just helped a client with this issue. Turned out to be a DNS problem on the server.

--

Scott

aka "Skyking"



PowerOn
Posts: 52
 Member Since:
2007-10-17
Did you try reset to factory
Tue, 05/11/2010 - 4:53pm

Did you try reset to factory defaults and removing local config after the firmware update?

--

Rent an Asterisk Virtual Private Server.
http://vps.powerpbx.org



PBXMatt
Posts: 13
 Member Since:
2006-06-06
New Firmware
Wed, 05/12/2010 - 1:21pm

I was on the Aastra website and downloded the new firmware for the 6757i and the 6730i.
The new firmware is ver. 2.6.0.66. I am on my way to the PBX with the phone problems to install the new firmware. I will report back later today or tomorrow morning if this firmware solves the problem.

Matt



PBXMatt
Posts: 13
 Member Since:
2006-06-06
Still not working
Wed, 05/12/2010 - 9:50pm

I just compleated upgrading the firmware to my Aastra 9757i and 6730i phones with ver. 2.6.0.66.
Remove Local Configuration Settings.
Reset the phones to factory defaults.
Used the endpoint manager with the XML 2.2.1 to install the phones.
I still have the problem of the phones going in and out of service.

My next step is to look at the router. It is a Linksys WRT54GS hooked to a cable modem. Anybody have info on this router?



euser4life
Posts: 180
 Member Since:
2006-07-16
You need to install a DNS server on the PBX
Thu, 05/13/2010 - 6:40am

You should do the following on your PBX.

yum -y install caching-nameserver
chkconfig --level 345 named on
nano /etc/resolv.conf
> Prepend: "nameserver 127.0.0.1"

Also you should not use the endpoint manager to deploy the phones. You should use the Aastra XML scripts. Read up on them as they will make your life easier and harness the ability of these amazing headsets.

Also on your aastra.cfg file you probably should add the DNS parameter with the IP address of your PBX.



mammoth
Posts: 449
 Member Since:
2006-06-14
my suggestions for what they're worth
Thu, 05/13/2010 - 8:26am

We had the same issue occurring on our phones connecting over our IPSEC vpn back to the main office where the trixbox pbx is located. Phones would randomly go into NO Service state and would not receive new calls, but would hold a call if already in progress.

So, looking at the asterisk logs of a No Service state phone, we saw the Sip session was having trouble determining which codec to use. So, in the phone, under Global Sip Settings, we changed Codec1 from "All" to "G711.u 8k." We also changed our Registration Period to 3600 as recommended in another post on this issue (default value is 0). Obviously, if you are using a different codec, you should choose accordingly.

The problem has gone away entirely. It's been six months, and we have not seen the issue recur on any phone after implementing this two pronged solution.

Our phones all use DHCP with default gateway and DNS servers, DNS is handled at both main office and remote locations by Monowall or Pfsense boxes, and there is no dns installed on trixbox server. Registration is by IP address to the pbx at main office, using its local subnet IP.

I hope this helps.

jason



PBXMatt
Posts: 13
 Member Since:
2006-06-06
I have tried the above with
Fri, 05/14/2010 - 11:11am

I have tried the above with no results. The G711.u codec does not seem to be the problem. There is nothing in the log that shows the sip session having troble determining which codex to use. When the phone is in the idle state, are the codec involved? Here is the asterisk log. Not sure what the "FONALITY: This thread has already held the conlock, skip locking" means, but it is throughout the log.

[May 14 10:14:47] VERBOSE[17533] logger.c: == Manager 'admin' logged off from 127.0.0.1
[May 14 10:15:07] NOTICE[2528] chan_sip.c: Peer '505' is now UNREACHABLE! Last qualify: 14
[May 14 10:15:07] DEBUG[2384] pbx.c: FONALITY: This thread has already held the conlock, skip locking
[May 14 10:15:17] NOTICE[2528] chan_sip.c: Peer '505' is now Reachable. (13ms / 2000ms)
[May 14 10:15:17] DEBUG[2384] pbx.c: FONALITY: This thread has already held the conlock, skip locking
[May 14 10:19:17] NOTICE[2528] chan_sip.c: Peer '505' is now UNREACHABLE! Last qualify: 14
[May 14 10:19:17] DEBUG[2384] pbx.c: FONALITY: This thread has already held the conlock, skip locking
[May 14 10:19:27] NOTICE[2528] chan_sip.c: Peer '505' is now Reachable. (11ms / 2000ms)
[May 14 10:19:27] DEBUG[2384] pbx.c: FONALITY: This thread has already held the conlock, skip locking
[May 14 10:23:27] NOTICE[2528] chan_sip.c: Peer '505' is now Lagged. (3995ms / 2000ms)
[May 14 10:23:27] DEBUG[2384] pbx.c: FONALITY: This thread has already held the conlock, skip locking
[May 14 10:23:37] NOTICE[2528] chan_sip.c: Peer '505' is now Reachable. (11ms / 2000ms)
[May 14 10:23:37] DEBUG[2384] pbx.c: FONALITY: This thread has already held the conlock, skip locking
[May 14 10:25:38] DEBUG[2384] pbx.c: FONALITY: This thread has already held the conlock, skip locking
[May 14 10:27:37] NOTICE[2528] chan_sip.c: Peer '505' is now Lagged. (3992ms / 2000ms)
[May 14 10:27:37] DEBUG[2384] pbx.c: FONALITY: This thread has already held the conlock, skip locking
[May 14 10:27:43] VERBOSE[17583] logger.c: == Manager 'admin' logged on from 127.0.0.1
[May 14 10:27:43] VERBOSE[17583] logger.c: == Manager 'admin' logged off from 127.0.0.1

Matt



euser4life
Posts: 180
 Member Since:
2006-07-16
Matt it looks like you have
Fri, 05/21/2010 - 5:40am

Matt it looks like you have a poor network somewhere between the sites.

Take a look at the following that you pasted from your logs:

[May 14 10:27:37] NOTICE[2528] chan_sip.c: Peer '505' is now Lagged. (3992ms / 2000ms)

Your register times exceed 2 seconds from your remote endpoint. As soon as you hit this threshold the phones will go into no service and not register. You need to look at your network between the sites. Try collecting some data from tools such as "Pingplotter" and "MTR". Perhaps a VPN problem or an issue with one of the hops you go through is dropping packets. Also check the physical connections with a fluke.

Your issue is definitely network based.



kerryg
Posts: 6790
 Member Since:
2006-05-31
I had this same exact issue
Fri, 05/21/2010 - 1:05pm

I had this same exact issue a while back and figured out another machine on the network had been statically set with the same IP address as the trixbox CE system. Every once in a while some of the phones would drop off. I soon figured out it was happening on a very regular time interval. I finally unplugged everything from the network and problem went away. As I plugged systems back in one at a time I eventually found the culprit.

--

Kerry Garrison
http://www.VoipStore.com - http://3cxbook.com
(888) VOIPSTORE - (888) 864-7786



SkykingOH
Posts: 9541
 Member Since:
2007-12-17
You can see this in your
Fri, 05/21/2010 - 2:19pm

You can see this in your switch if you have an ARP problem. The MAC address will change.

--

Scott

aka "Skyking"



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.