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

Asterisk Bug Tracker noreply at bugs.digium.com
Mon May 24 14:56:57 CDT 2010


The following issue has been UPDATED. 
====================================================================== 
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:                     closed
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:              
Resolution:                 won't fix
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-05-06 12:53 CDT
Last Modified:              2010-05-24 14:56 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

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

---------------------------------------------------------------------- 
 (0122331) pabelanger (manager) - 2010-05-24 14:56
 https://issues.asterisk.org/view.php?id=17299#c122331 
---------------------------------------------------------------------- 
This appears to be support related, not a bug. You will find more
information about gaining support at http://www.asterisk.org/support

Also not 1.6.0 / 1.6.1 is only for security fixes only, I would suggest
using 1.6.2 branch. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-05-24 14:56 pabelanger     Note Added: 0122331                          
2010-05-24 14:56 pabelanger     Status                   new => closed       
2010-05-24 14:56 pabelanger     Resolution               reopened => won't fix
======================================================================




More information about the asterisk-bugs mailing list