9133i works but every morning says "No service"

xinsight

Posts: 18
Member Since:
2008-01-17

Submitted by xinsight on Thu, 01/17/2008 - 5:04pm.

I've been impressed with the 9133i so far. Everything works great, but for some reason, after a period of time (usually during the night) the message indicator light goes on and the display says "No Service".

After unplugging/replugging the power adapter for the phone, it reboots, and everything works fine.

One bizarre detail, is that when the phone says "No Service" - pushing the arrow keys shows the IP address 192.168.10.9. The phone actually has the address 192.168.10.20, and the .9 address is not used, AFAIK.

There is a router between the phone and the asterisk server. (192.168.10.1)

I've tried logging debug info to a syslogd, but the messages are jibberish to me. I may have to put a laptop on the network just to sniff packets for a while.

Anyone have any other ideas what could be wrong? (or how to debug the problem?)

Thanks!

-jay

Build your own PBX
pbxer.com

&nbsp

aastra2

Posts: 324
Member Since:
2006-10-05

"No Service" means that the

Sat, 01/19/2008 - 7:13am

"No Service" means that the phone has lost it's registration with the asterisk box. This should be easy to confirm by looking at the Asterisk status on Trixbox.

As to why this is happening it's hard to say. Are the phones and Trixbox on either side of a NAT box (the IP addresses you mention are private)? Some statefull firewalls have awful implementations for SIP and have tendency to break things.

----
Gareth

Firmware 2.5.1 available.
Download it from www.aastratelecom.com

&nbsp

xinsight

Posts: 18
Member Since:
2008-01-17

Yes, I think you're right

Mon, 01/21/2008 - 7:58am

Yes, I think you're right that it might have something to do with the NAT firewall traversal.

What is strange is that the phone sometimes says "No service" but the red message indicator light doesn't go on. This usually means that I can still make calls. (not sure about receiving) Once the red light goes on - the phone seems to have given up trying to reconnect/reregister and requires a reboot.

Do you know what the red light indicates? Any idea why the mysterious IP address shows up on the phone when the 'no service' and red light is on? (There may be a firewall issue, but the phone is displaying his IP address all on it's own.) Is there a way to reboot the phone - or ask it to reregister w/out unplugging the power?

I've got "sip debug peer aastra1" in the asterisk console. Will that catch any relevant info?

thanks!

Build your own PBX
pbxer.com

&nbsp

xinsight

Posts: 18
Member Since:
2008-01-17

followup

Thu, 01/24/2008 - 8:13am

I believe the "no service" problem has been resolved.

I recently installed WPA on my router and the phone has not shown the message since. The phone is of course, not wireless, but I wonder if some neighbour's computer (the mysterious 192.168.10.9) was sending nasty UDP packets or trying to hack the phone... or maybe someone had a TFTP server and it was trying to download a config?)

Yeah, that does sound a bit crazy, now that I type it all out. But for whatever reason encrypting the wifi seemed to eliminate to No Service errors.

(i'd still like to know why the phone shows an IP address that is different from the address of the phone. Any aastra engineers out there...?)

Build your own PBX
pbxer.com

&nbsp

xinsight

Posts: 18
Member Since:
2008-01-17

problem persists

Sat, 03/15/2008 - 12:47pm

This "no service" problem is continuing to drive me crazy.

Seems that others have this problem as well, and it was explicitly mentioned in the 2.2.0 firmware bug fixes.

"Fixed crash after the phone looses connectivity to the server and goes into the "No Service" state."
http://www.trixbox.org/forums/vendor-moderated-forums/aastra-endp...

I would LOVE to know if this is fixed or planning to be fixed in the firmware for the 9133i. Anyone know?

Build your own PBX
pbxer.com

&nbsp

aastra2

Posts: 324
Member Since:
2006-10-05

The "No Service" crash was

Sat, 03/15/2008 - 1:17pm

The "No Service" crash was specific to the 5i phones and did not affect the 9133i

----
Gareth

Firmware 2.5.1 available.
Download it from www.aastratelecom.com

&nbsp

xinsight

Posts: 18
Member Since:
2008-01-17

next steps...

Sat, 03/15/2008 - 2:16pm

ah, well, "no service crash" seemed to summarize my problem as well. It certainly appears that the phone gets into some sort of state and cannot recover without a reboot.

I'd like to get this problem fixed. Any tips on how to isolate the problem? Here's what I'm doing currently:

* logging all debug messages to a server running syslogd

* saved the stack after a "no service crash"

* submitted a support ticket at the aastra website:

http://www.aastratelecom.com/cps/rde/xchg/SID-3D8CCB6A-15B4EFB9/0...

Is there anything else?

Build your own PBX
pbxer.com

&nbsp

jahyde

Posts: 2002
Member Since:
2006-06-02

reboot the phone

Sat, 03/15/2008 - 10:19pm

reboot the phone everynight

theres a script on voip-info.org I think its in the aastra 480i area - just put it in cron with your ips.

--my PBX is run on 2 V8's

&nbsp

PBXMatt

Posts: 13
Member Since:
2006-06-06

I have the same problem

Sat, 03/15/2008 - 10:51pm

I have three SIP Aastra phones, a 9133, 480iCT and a 57i, and am using a SIP trunk by Axvoice. I am having the same problem with my Aastra phones. I solved the problem by removing my SIP trunk (Axvoice). Without the SIP trunk, my system works fine. I have added an IAX2 trunks from Viopstreet and the system still works fine without and dropouts. I still don't know why my SIP trunk makes my SIP Astra extensions act wierd. I have Trixbox 2.6.0.2 as a recent clean install.

My older Trixbox ver 1.2.3 worked for a long time without any problems. I don't know if it was the Aastra firmware upgrade or the Trixbox upgrade that caused the problem, because I upgraded the phones and Trixbox at the same time.

I hope someone has an answer.

Thanks,

Matt

&nbsp

xinsight

Posts: 18
Member Since:
2008-01-17

possible workaround

Wed, 03/19/2008 - 5:46pm

It seems to be due to dns lookup code. I replaced all the server names (voip.example.com) with their IP addresses. It's been running for over 24 hour without the "No Service" problem.

This was identified when looking at the stack trace once the phone is in it's "No Service" state. There is a thread called "tDnsResolv" on the phone. If it is in "PEND" then it's working fine. If it's in "SUSPEND" then there are problems.

It would be nice to get this properly fixed in the firmware, since using IP addresses in the config is messy and not a long-term solution.

I've opened a ticket with tech support. I suggest anyone else with this problem do the same. The normal reaction for tech-support and engineering is that they can't replicate the problem, and no one else is complaining, so it must be something the customer is doing. The more people complaining, the more priority and resources get allocated to the problem.

Build your own PBX
pbxer.com

&nbsp

lmuller

Posts: 3
Member Since:
2008-05-01

Voice Mail stuck in gue to email

Fri, 05/02/2008 - 11:29am

We have had this problem for the past week affecting many of our Aastra 933i and 57i and 55i phones. We found that periodically the server CPU was spiking out which led us to find that 1gb voice mails were stuck in the queue trying to be delivered. Every time the queue tried to deliver the CPU would spike and phones trying to register with the server would drop out and show now service.

We are resetting the duration for voice mails to hopefully resolve this problem.

&nbsp

xinsight

Posts: 18
Member Since:
2008-01-17

update

Wed, 09/17/2008 - 1:19pm

Just in case anyone else is following along, here is a short update.

In July I installed a special firmware (1.4.2.4002) from Aastra to give them a stack trace on the suspended DNS thread. I sent the stack trace info to them.

In August they sent me a beta version of new firmware (1.4.3 beta1) which was supposed to address this DNS crashing/no service problem. It didn't. I sent them the stack trace and haven't heard from them since.

I find it surprising that they have trouble replicating the problem, but I was impressed that they followed up with me. Anyways, using IP addresses makes the phones rock solid reliable, so it's a reasonable workaround.

Build your own PBX
pbxer.com

&nbsp

IcelandDreams

Posts: 415
Member Since:
2007-09-11

You might also explain more

Wed, 09/17/2008 - 2:09pm

You might also explain more about the network layout unless all is now well. you mention WPA on the router, is that the same router that the phone has to cross to find the PBX? Is there a wireless link between nets? You were running an open wireless? I hope you have all the networking issues correct. The DNS issue mentioned elsewhere is one thing but your problem might be something else.

Of course I don't say that wireless links are a problem since I do it all the time just for fun and it does work given a proper setup and is a good test of the limits of SIP.

&nbsp

xinsight

Posts: 18
Member Since:
2008-01-17

The wireless/WPA turned out

Wed, 09/17/2008 - 3:43pm

The wireless/WPA turned out to be a non-issue. The problem was hard to isolate since it happened seemingly at a random interval every couple of days. The suspended DNS thread convinced me that the DNS code was the source of the problem:

The network setup is quite basic (and I presume common): The phone has a private IP address, is connected to a standard residential router and uses a cable internet connection to connect to the internet and the asterisk PBX (which has a public IP address).

This image summarizes the network architecture:

http://www.pbxer.com/wp-content/uploads/2008/08/pbxer-voip-overvi...

Build your own PBX
pbxer.com

&nbsp

keystoneit

Posts: 27
Member Since:
2006-09-04

9112i and 9133i - "No Service" message.

Thu, 09/18/2008 - 12:55pm

We've seen variations of this problem across several servers and different types of networks. Basically if there is any problem with the registration, even for a few seconds, it will say "No Service" on the display until the the handset is picked up again. If the red light stays on solid, then it currently has no registration with the server. I summarized my troubleshooting here: http://tinyurl.com/4rxq8g

At the end of the day, we quit even trying to sell the 9112i and 9133i since the misleading "No Service" message was causing unnecessary customer concern and support calls.

Pat McKay
FtOCC

http://www.keystoneit.com
http://www.linkedin.com/in/keystoneit

&nbsp

9133i works but every morning says "No service"

Comment viewing options

Search

Main

User login

Who's online