[Home]

Summary:ASTERISK-21135: Asterisk 1.8 no longer sends unsolicited message-summary (NOTIFY) after realtime SIP peer registers
Reporter:Scott Cechovic (sacechovic)Labels:
Date Opened:2013-02-18 16:19:34.000-0600Date Closed:2013-03-11 20:41:37
Priority:MinorRegression?
Status:Closed/CompleteComponents:PBX/pbx_realtime Resources/res_odbc
Versions:1.8.11.1 Frequency of
Occurrence		Constant
Related
Issues:
Environment:CentOS 5.8 kernel 2.6.18-308.13.1.el5Attachments:
Description:Adtran IP7XX SIP phones do not do MWI subscribe and relied on the unsolicited message-summary event when rebooting to properly set the message waiting indicator.  Asterisk 1.8 cert 5 and cert 8 appear to no longer send the unsolicited message-summary event.  Since all peers are realtime peers, it doesn't appear that subscribemwi=no is supported in realtime.  Is there a way to cause the unsolicited message-summary event for realtime peers?  This can be reproduced by just rebooting a phone with unread messages.  If a new message comes in or a sip prune realtime <peer> is done, the MWI light is set correctly.
Comments:By: Rusty Newton (rnewton) 2013-02-21 16:24:54.215-0600

Hi Scott!

First off, pbx_realtime is an extended support feature and therefore supported by the community, so response times will reflect that. https://wiki.asterisk.org/wiki/display/AST/Asterisk+Module+Support+States

I'm not positive that this is the same issue you are having, but here is how one community member solved a possibly similar problem: http://lists.digium.com/pipermail/asterisk-users/2011-November/268046.html

Your question is a little confusing. To clarify and help any others who make look at this issue, I'll ask some further questions:

It sounds like you are saying Asterisk never sends out the unsolicited message-summary event (as SIP NOTIFY), But you say "If a new message comes in or a sip prune realtime <peer> is done, the MWI light is set correctly.".

1. Does Asterisk ever send out the unsolicited message-summary events to your realtime peers?

2.
{quote}
This can be reproduced by just rebooting a phone with unread messages
{quote}

Are the phones registering on boot? Verify if the phone is re-registering upon boot up. If it does register with Asterisk, then it should be receiving the unsolicited message-summary events.

3.
{quote}
Asterisk 1.8 cert 5 and cert 8 appear to no longer send the unsolicited message-summary event.
{quote}

Did this work in a previous version? What was the last version that this behaved appropriately in?



I don't know realtime very well, and I'm primarily doing triage, not debugging so I may not be able to help much further. However the additional info may help a community dev look into the issue. It does sound buggy, but this may just be a quirk of realtime.
By: Scott Cechovic (sacechovic) 2013-02-25 10:38:14.879-0600

Rusty,

Thanks for the response, I will look at the links you sent.  In the meantime, here are the answers to your questions:

1) Yes, certified 1.8 never sends the unsolicited message-summary when the Adtran phone registers (it did in 1.4).  So when the phone registers, since it does not request messages, it never sets the light.  However, from the phone, if I login in to voicemail to check for messages (or execute a sip prune realtime <SIP user>, Asterisk sends the summary (below)

Reliably Transmitting (no NAT) to 172.24.0.53:5060:
NOTIFY sip:5247@172.24.0.53:5060 SIP/2.0
Via: SIP/2.0/UDP 172.24.7.200:5060;branch=z9hG4bK0f53e70b
Max-Forwards: 70
From: "asterisk" <sip:asterisk@172.24.7.200>;tag=as0ba4fc20
To: <sip:5247@172.24.0.53:5060>
Contact: <sip:asterisk@172.24.7.200:5060>
Call-ID: 49ad3c47194cf5ac55cf2d1b4edc4da2@172.24.7.200:5060
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX 1.8.11-cert5
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 93

Messages-Waiting: yes
Message-Account: sip:asterisk@172.24.7.200
Voice-Message: 2/0 (0/0)

And, if the SIP user registered to the phone receives a new message, Asterisk sends the summary (below)

Reliably Transmitting (no NAT) to 172.24.0.53:5060:
NOTIFY sip:5247@172.24.0.53:5060 SIP/2.0
Via: SIP/2.0/UDP 172.24.7.200:5060;branch=z9hG4bK6864e39b
Max-Forwards: 70
From: "asterisk" <sip:asterisk@172.24.7.200>;tag=as2641da3f
To: <sip:5247@172.24.0.53:5060>
Contact: <sip:asterisk@172.24.7.200:5060>
Call-ID: 539f9ae46385f7ad467193e5186afc7e@172.24.7.200:5060
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX 1.8.11-cert5
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 93

Messages-Waiting: yes
Message-Account: sip:asterisk@172.24.7.200
Voice-Message: 3/0 (0/0)

2) Yes, the phone always registers on a reboot and works fine other then the MWI light (unless one of the conditions above is met).

3) Yes, the unsolicited message-summary event worked in all of the 1.4 releases.

I understand that pbx_realtime is extended support but we use it exclusively and have based our interface around it.  The problem, good or bad, is we have a bunch of these Adtran phones that do not request message info but we are wanting to upgrade all these locations to 1.8 so these customers can start phasing in Digium phones.  However, the MWI light could be a show stopper and prevent the sale of Digium phones into these customers (Worthington Federal is the customer that brought this issue to light and they have about 100 Adtran phones).  It would be nice if 1.8 could be configured to send the unsolicited message-summary to phones at registration for phones that do not solicit the message-summary info for backward compatibility.  Maybe in the [general] section of sip.conf or have the phone read subscribemwi (which currently doesn't exist) from realtime.

Thanks for your consideration and help,
Scott
By: Rusty Newton (rnewton) 2013-02-26 14:56:53.366-0600

{quote}
Yes, the unsolicited message-summary event worked in all of the 1.4 releases.
{quote}

Unfortunately a lot of things are different between 1.4 and 1.8... years of code.. It'd be more helpful if you found a previous 1.8 version where it worked. That would narrow things down a lot.

{quote}
I understand that pbx_realtime is extended support but we use it exclusively and have based our interface around it. The problem, good or bad, is we have a bunch of these Adtran phones that do not request message info but we are wanting to upgrade all these locations to 1.8 so these customers can start phasing in Digium phones. However, the MWI light could be a show stopper and prevent the sale of Digium phones into these customers (Worthington Federal is the customer that brought this issue to light and they have about 100 Adtran phones).
{quote}

If you are asking for commercial support or consulting from Digium you should contact Digium through the appropriate channels for that support. As a reseller or partner, that would be your official contacts within Digium.  

{quote}It would be nice if 1.8 could be configured to send the unsolicited message-summary to phones at registration for phones that do not solicit the message-summary info for backward compatibility. Maybe in the [general] section of sip.conf or have the phone read subscribemwi (which currently doesn't exist) from realtime.{quote}

I believe Asterisk should be sending out the unsolicited message-summary upon registration of the endpoint regardless of realtime being used or not.

Can you attempt reproduction with one of your Adtran phones and the latest Asterisk 1.8 without realtime ? If you can, please provide a packet capture of the SIP dialog and include a VERBOSE and DEBUG log from Asterisk capture during the time of the registration. We'll also need to see the configs used (sip.conf, voicemail.conf) in order to reproduce.

If you can reproduce this behavior without realtime involved, that would definitely make it a core issue and probably the fix would apply in both scenarios.




By: Scott Cechovic (sacechovic) 2013-03-11 15:38:28.266-0500

Issue resolved.  Upgraded to 1.8.15 cert1 and notifies are sent after device registers.  Works with realtime as well.