[asterisk-bugs] [Asterisk 0018172]: Peer goes unreachable when placing a call from it.

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18172 
====================================================================== 
Reported By:                jordankirby
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18172
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
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-10-20 06:23 CDT
Last Modified:              2010-10-22 09:02 CDT
====================================================================== 
Summary:                    Peer goes unreachable when placing a call from it.
Description: 
We are using 1.8RC5, Asterisk RealTime (MySQL) and realtime caching.
Both the server and the phones are behind separate NAT (phone in office,
server in data centre).

In this example, SIP/3001 calls SIP/3002 (via a gosub). The call proceeds
fine but asterisk sees SIP/3001 as unavailable for a period of time after
the initial invite.

This looks to be because asterisk starts sending OPTIONS and NOTIFIES to
the LAN IP address of the phone rather than it's NATed IP address.

In the attached trace:
  10.50.0.47 is the server's LAN IP.
  212.62.4.230 is the server's NATed IP.
  192.168.1.231 is 3001's LAN IP.
  195.59.152.66 is 3001's NATed IP.

Asterisk output:

  == Using SIP RTP CoS mark 5
    -- Executing [3002 at DLPN_All:1] Gosub("SIP/3001-000000aa",
"internal,3002,1")
    -- Executing [3002 at internal:1] Dial("SIP/3001-000000aa", "SIP/3002")
  == Using UDPTL CoS mark 5
  == Using SIP RTP CoS mark 5
    -- Called 3002
    -- SIP/3002-000000ab is ringing
[Oct 20 12:11:05] NOTICE[24099]: chan_sip.c:24694 sip_poke_noanswer: Peer
'3001' is now UNREACHABLE!  Last qualify: 37
  == Spawn extension (internal, 3002, 1) exited non-zero on
'SIP/3001-000000aa'
    -- Registered SIP '3001' at 195.59.152.66:17261
[Oct 20 12:11:55] NOTICE[24099]: chan_sip.c:19523
handle_response_peerpoke: Peer '3001' is now Reachable. (34ms / 2000ms)

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

---------------------------------------------------------------------- 
 (0128319) jordankirby (reporter) - 2010-10-22 09:02
 https://issues.asterisk.org/view.php?id=18172#c128319 
---------------------------------------------------------------------- 
Once peers are registered and online, if I issue a reload some of them
start to show in "sip show peers" with their internal IP address:

Name/username              Host                                    Dyn
Forcerport ACL Port     Status     Realtime
3001/3001                  192.168.1.231                            D   N 
    17261    UNREACHABLE Cached RT
3002/3002                  192.168.1.230                            D   N 
    40452    UNREACHABLE Cached RT


But viewing the database at the same time shows the correct, external IP
address:

mysql> select name,ipaddr from gag1_sip;
+--------------+---------------+
| name         | ipaddr        |
+--------------+---------------+
| 3001         | 195.59.152.66 |
| 3002         | 195.59.152.66 | 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-10-22 09:02 jordankirby    Note Added: 0128319                          
======================================================================