[asterisk-bugs] [Asterisk 0018302]: Asterisk 1.6.2.14 w/ Realtime SIP Peers: MWI gets stuck in a loop sending 1000's of SIP NOTIFY messages when rtcachefriends = no
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Dec 6 15:00:57 CST 2010
The following issue has been UPDATED.
======================================================================
https://issues.asterisk.org/view.php?id=18302
======================================================================
Reported By: BrettW
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18302
Category: Channels/chan_sip/Subscriptions
Reproducibility: always
Severity: minor
Priority: normal
Status: acknowledged
Asterisk Version: 1.6.2.14
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-11-13 04:27 CST
Last Modified: 2010-12-06 15:00 CST
======================================================================
Summary: Asterisk 1.6.2.14 w/ Realtime SIP Peers: MWI gets
stuck in a loop sending 1000's of SIP NOTIFY messages when rtcachefriends = no
Description:
I am running Asterisk 1.6.2.14 on Linux CentOS 5.5 x64.
I am using the ODBC backend (to MySQL) for voicemail storage, voicemail
box configuration, and sip user/peer configuration. Whenever a phone is
actively subscribed to a voicemail box, Asterisk gets stuck in a loop
sending 1000's of SIP NOTIFY packets to the phones if there is a new
message in the voicemail box. Moving the message to an Inbox that has no
active subscriptions makes Asterisk settle down (and not send 1000's of
these packets).
This only occurs when rtcachefriends = no in sip.conf. Changing
rtcachefriends to yes resolves this. Unfortunately I'm looking to go with
the Realtime engine without having to "prune" or "flush" the SIP peers to
update them.
Also, disabling the ODBC backend for sip users/peers and configuring peers
statically in sip.conf also resolves this.
The SIP NOTIFY messages that are sent to the phones are all the same, with
the exception that the Call-ID and tags are all unique. A copy of the
NOTIFY messages is below.
I'm currently running this on a development server. As such, I am willing
to let a developer into the system to watch what is happening. I can
reproduce this very easily. Just ask! ;-)
Thanks!
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2010-12-06 15:00 lmadsen Description Updated
2010-12-06 15:00 lmadsen Additional Information Updated
======================================================================
More information about the asterisk-bugs
mailing list