[asterisk-bugs] [Asterisk 0013316]: Realtime registrations don't work after a sip reload
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Aug 28 21:14:06 CDT 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=13316
======================================================================
Reported By: bcramer
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 13316
Category: Channels/chan_sip/DatabaseSupport
Reproducibility: always
Severity: major
Priority: normal
Status: feedback
Asterisk Version: SVN
SVN Branch (only for SVN checkouts, not tarball releases): 1.4
SVN Revision (number only!): 138258
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 2008-08-15 22:00 CDT
Last Modified: 2008-08-28 21:14 CDT
======================================================================
Summary: Realtime registrations don't work after a sip reload
Description:
Sip registrations get mixed up as the Nat'ed IP's get populated in the sip
status, then the status becomes UNKNOWN. Shortly after the sip
registration completely disappears/expires:
sbc02*CLI> sip show peers
Name/username Host Dyn Nat ACL Port Status
Realtime
6046309553 24.207.127.215 D N 5060 OK (10 ms) Cached RT
blah 10.10.200.10 D N 5060 OK (1 ms)
2 sip peers [Monitored: 2 online, 0 offline Unmonitored: 0 online, 0
offline]
sbc02*CLI> sip reload
Reloading SIP
== Parsing '/etc/asterisk/sip.conf': Found
sbc02*CLI> sip show peers
Name/username Host Dyn Nat ACL Port Status
Realtime
6046309553/6046309553 192.168.1.100 D N 5060 UNKNOWN
Cached RT
blah 10.10.200.10 D N 5060 OK (1 ms)
2 sip peers [Monitored: 1 online, 1 offline Unmonitored: 0 online, 0
offline]
<couple minutes later>
sbc02*CLI> sip show peers
Name/username Host Dyn Nat ACL Port Status
Realtime
vr01mcitosbc02mci/vr01mci 10.10.200.10 D N 5060 OK (1 ms)
1 sip peers [Monitored: 1 online, 0 offline Unmonitored: 0 online, 0
offline]
======================================================================
----------------------------------------------------------------------
(0091882) callguy (reporter) - 2008-08-28 21:14
http://bugs.digium.com/view.php?id=13316#c91882
----------------------------------------------------------------------
Corydon76: I think there's something more subtle going on here. While I
agree that the patches you committed stop the functional issue (phones
appear to be able to make/receive calls even when in "UKNOWN" state) there
is still a display issue, but it isn't deterministic. What appears to have
happened is that something has changed in the NAT code. If I do a reload
and take a sample of 100 peers that were online before, about 37 of them
were still showing as "OK (xx ms)" after re-registering.
However, if I go into the Cisco router that the majority of them are
behind, and execute "clear ip nat translations *" that will clear the local
NAT table and all of the phones will change to the "OK" status after
re-registration.
This wasn't the behavior in past versions (we don't have any issue with
1.4.20), so something has changed in the interim that seems to be confusing
the nat handling in asterisk (I can confirm that nothing has changed on the
firewall).
I'm not really sure what the right tactic is to help debug this, please
let me know what we can do to help.
Issue History
Date Modified Username Field Change
======================================================================
2008-08-28 21:14 callguy Note Added: 0091882
======================================================================
More information about the asterisk-bugs
mailing list