Summary: | ASTERISK-16953: 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 | ||
Reporter: | Brett Woollum (brettw) | Labels: | |
Date Opened: | 2010-11-13 04:27:10.000-0600 | Date Closed: | |
Priority: | Minor | Regression? | No |
Status: | Open/New | Components: | Channels/chan_sip/Subscriptions |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
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! ****** ADDITIONAL INFORMATION ****** SIP NOTIFY Packet: NOTIFY sip:412@10.20.1.225:5064 SIP/2.0 Via: SIP/2.0/UDP 1.2.3.4:5060;branch=z9hG4bK616ee12f;rport Max-Forwards: 70 From: "asterisk" <sip:asterisk@1.2.3.4>;tag=as7242329e To: <sip:412@10.20.1.225:5064> Contact: <sip:asterisk@1.2.3.4> Call-ID: 178bd59132b75d17790873e86f4172ac@1.2.3.4 CSeq: 102 NOTIFY User-Agent: Asterisk PBX 1.6.2.14 Event: message-summary Content-Type: application/simple-message-summary Content-Length: 95 Messages-Waiting: no Message-Account: sip:asterisk@1.2.3.4 Voice-Message: 0/0 (0/0) sip.conf: [general] externip=1.2.3.4 context=incoming port=5060 nat=yes bindaddr=0.0.0.0 disallow=all allow=g722 allow=ulaw dtmfmode=rfc2833 srvlookup=yes progressinband=yes notifyringing=yes allowsubscribe=yes subscribecontext=blf_subscriptions notifyhold=yes limitonpeers=no qualify=yes rtcachefriends=no extconfig.conf: sippeers => odbc,asterisk,sip_users voicemail => odbc,asterisk,voicemail_boxes meetme => odbc,asterisk,meetme extensions => odbc,asterisk,extensions | ||
Comments: | By: Brett Woollum (brettw) 2010-11-13 04:30:50.000-0600 A mailing-list discussion about this problem can be seen here: http://lists.digium.com/pipermail/asterisk-users/2010-November/256045.html |