[asterisk-bugs] [Asterisk 0011210]: SIP reload for large config halts SIP Processing
noreply at bugs.digium.com
noreply at bugs.digium.com
Mon Nov 12 11:58:32 CST 2007
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=11210
======================================================================
Reported By: dtyoo
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 11210
Category: Channels/chan_sip/General
Reproducibility: always
Severity: major
Priority: normal
Status: new
Asterisk Version: 1.4.13
SVN Branch (only for SVN checkouts, not tarball releases): 1.4
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 11-09-2007 16:06 CST
Last Modified: 11-12-2007 11:58 CST
======================================================================
Summary: SIP reload for large config halts SIP Processing
Description:
It seems that asterisk stops processing sip for some amount of time during
reloads. This causes weird dialing behavior for our end users trying to
make / recieve calls during the reloads, and some of our sip endpoints
start re-registering to other, backup servers when the reloads occur. Do
you have any suggestions / thoughts on this? I was going to start looking
at realtime as a possible solution, but given the size and complexity of
our dialplan, and integration with our existing backend systems this is
probably not going to be a quick fix.
======================================================================
----------------------------------------------------------------------
twilson - 11-12-07 11:58
----------------------------------------------------------------------
I know I ran into this issue about 2 years ago and switched to realtime to
avoid it (which works great btw). When you do a sip reload, asterisk sends
qualify packets to all peers (if you have qualify set to something)--which
I think are now spaced 100ms apart to avoid this issue, and I think it will
also cause mwi to be sent to all peers as well. This is a lot of messages
to send (and I've taken down a SER box with them before).
I would suggest, for testing purposes, turning off qualify and trying a
reload to see if there is any interruption after reload. Then if it is the
same, temporarily take out the malibox setting for the peers and do a
reload and see if that is what is causing the problem and then we can go
from there. Although, when I had to fix the problem I had to use realtime
without caching, and handle MWI externally (we had many asterisk boxes
sharing a config, so *each* would blast mwi messages when it did a reload).
Issue History
Date Modified Username Field Change
======================================================================
11-12-07 11:58 twilson Note Added: 0073528
======================================================================
More information about the asterisk-bugs
mailing list