[asterisk-bugs] [Asterisk 0017299]: chan_sip.c: Peer 'XXX' is now UNREACHABLE

Asterisk Bug Tracker noreply at bugs.digium.com
Thu May 6 13:21:52 CDT 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17299 
====================================================================== 
Reported By:                invitu
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17299
Category:                   Channels/chan_sip/Registration
Reproducibility:            sometimes
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.1.18 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-05-06 12:53 CDT
Last Modified:              2010-05-06 13:21 CDT
====================================================================== 
Summary:                    chan_sip.c: Peer 'XXX' is now UNREACHABLE
Description: 
Hello,

I work with asterisk 1.6.1.18 (from fedora packages) behind a nat and
hardphones (linksys SPA922-942 and siemens C470IP) which are behind
different nats too. For testing, I also have a SPA942 on my LAN. Moreover,
public IP are dynamic (because our unique ISP does not provide fixed IP
addresses) but this is not the purpose for that issue because all worked
very well for months.

Since several days, I have "unreachable" messages on the CLI that should
not be due to NAT timeouts because I also have them with my LAN peer.
Nothing has changed on my server and the problem appeared suddenly. For
information, the problem occured twice this year with earlier asterisk
versions and I don't know what resolved it.

Of course, during the time the peer is unreachable, it cannot be called
which is a problem.

This time, I have debug information. Here are my confs & logs.

Regards

====================================================================== 

---------------------------------------------------------------------- 
 (0121489) pabelanger (manager) - 2010-05-06 13:21
 https://issues.asterisk.org/view.php?id=17299#c121489 
---------------------------------------------------------------------- 
Thanks for your comments. This does not appear to be a bug report and we
are closing it. We appreciate the difficulties you are facing, but it would
make more sense to raise your question in the support tracker,
http://www.asterisk.org/support 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-05-06 13:21 pabelanger     Note Added: 0121489                          
======================================================================




More information about the asterisk-bugs mailing list