[Home]

Summary:ASTERISK-12528: Stops replying to some registration requests after restarting the process or rebooting server
Reporter:gblithium (gblithium)Labels:
Date Opened:2008-08-06 00:44:55Date Closed:2009-01-19 14:37:51.000-0600
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Channels/chan_sip/Registration
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Whenever I stop asterisk for more then a few minutes or if the box gets rebooted, many of the hardphone we use can't not register anymore. We're using Aastra 55i phones w/ the latest firmware 2.2.1.25. I can sniff the asterisk box's dedicated voip eth1 interface and see the request from the hardphone. There is never a SIP response back from asterisk. Phone claims 408.

I increase the debug to 9, verbose to 4 and "sip debug" but nothing shows up in the logs (full => notice,warning,error,debug,verbose).

Rebooting the phones do not fix this problem.

Only fix so far is to give the phone a new IP address that hasn't had the same problem before.

****** ADDITIONAL INFORMATION ******

Here is what the aastra is sending to asterisk:
U 2008/08/05 22:45:18.321508 10.10.180.171:5060 -> 10.10.180.2:5060
REGISTER sip:10.10.180.2:5060 SIP/2.0.
Via: SIP/2.0/UDP 10.10.180.171:5060;branch=z9hG4bK34ad52c8a01af55f8.
Max-Forwards: 70.
From: <sip:312@10.10.180.2:5060>;tag=484216173b.
To: <sip:312@10.10.180.2:5060>.
Call-ID: 86a41e3f3d722f3b.
CSeq: 842 REGISTER.
Allow:  INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, UPDATE, PRACK, SUBSCRIBE, INFO.
Allow-Events: talk, hold, conference.
Contact: 312 <sip:312@10.10.180.171:5060;transport=udp>;expires=120.
User-Agent: Aastra 55i/2.2.1.25.
Content-Length: 0.


16 of the 40 phones are currently in this state.
Comments:By: gblithium (gblithium) 2008-08-06 13:44:07

The asterisk box is also multihomed.

eth0 = 10.10.100.2
eth1 = 10.10.180.2 (dedicated to voice traffic and the same network as the hardphones)


If change the hardphones registration server to 10.10.100.2 it will work fine. But is still is unable to if set to 10.10.180.2

In both cases Outbound proxy is set to 10.10.180.2.

I ran a tcpdump to make sure the traffic wasn't going out the wrong interface and it wasn't. I still don't see anything in the logs w/ debug/verbose=4 + "sip debug" + recordhistory/dumphistory = yes.
By: Leif Madsen (lmadsen) 2008-12-05 10:35:03.000-0600

As per oej on IRC today, outboundproxy is not a route, which I take to mean that by setting outboundproxy, that does not tell Asterisk which interface to send the packets out of.

We will need to see if Asterisk is actually getting the REGISTRATION packet, and the only way to know that is with a 'sip debug' from the Asterisk CLI.

Can you please attach that? Thanks
By: gblithium (gblithium) 2008-12-08 15:08:21.000-0600

We've since changed hardware/OS that asterisk runs on. We haven't seen the problem. I'll shutdown asterisk a few time today and see if we still have the same problem.
By: James Golovich (jamesgolovich) 2009-01-19 14:25:27.000-0600

It's been over a month.  Is everything ok now so this can get closed out?
By: Leif Madsen (lmadsen) 2009-01-19 14:37:51.000-0600

Closing this issue as it appears changing hardware resolved the issue. Thanks!