|Summary:||ASTERISK-21913: Successive NOTIFY for MWI subscriptions isn't sent|
|Reporter:||Malcolm Davenport (mdavenport)||Labels:|
|Date Opened:||2013-06-14 16:15:14||Date Closed:||2013-06-14 18:27:04|
|Environment:||Asterisk SVN-trunk-r391828||Attachments:||( 0) debug1.txt|
( 1) debug2.txt
|Description:||Here's an Endpoint:
callerid="Malcolm Davenport" <101>
It starts up and it subscribes for MWI and it gets notice of it:
If I then log in and check my voicemail, and delete the voicemail that's waiting, Asterisk never sends a NOTIFY to the endpoint (the phone) that there are no more waiting messages.
It happens if I've got a message that I playback to remove, where the indicator should turn off due to NOTIFY, as well as if I leave a message that I expect to turn on the indicator due to NOTIFY.
|Comments:||By: Mark Michelson (mmichelson) 2013-06-14 17:11:29.799-0500|
I've reproduced this issue myself. Adding debugging messages, I can see that res_sip_mwi is subscribing to MWI stasis messages, and I can see that app_voicemail publishes an MWI event for the mailbox. However, I never see my stasis callback called in res_mwi_stasis. So something is happening in the stasis core that is resulting in res_sip_mwi never being told that mailbox state has changed.
I double-checked by switching from using res_sip and its ilk to using chan_sip, and I saw the same issue occur there as well. No NOTIFY was sent because the stasis callback was not called when the mailbox state changed.
By: Rusty Newton (rnewton) 2013-06-14 17:19:25.240-0500
attaching debug removed from inline.
By: Malcolm Davenport (mdavenport) 2013-06-17 07:58:56.581-0500
Works for me.