asterisk users - Dec 2018 - Voice mail: MWI problem / pjsip (13.24.0)

Hello!

I'm facing a problem concerning MWI. The problem is:

The phone switches off the MWI exactly at the moment the second NOTIFY package
for one voice mail
arrives.

The phone switches off MWI independently if the voice mail has been acknowledged
or not before.


The behavior in detail:

- Once each hour, phone sends SUBSCRIBE
- Asterisk receives incoming voice mail for Device 200.
- some time later: Phone executes a REGISTER
- Directly after succeeded REGISTER, asterisk sends Notify
- Notify is acked by phone



The content of the packages

----------------------------------------------------------------------
SUBSCRIBE

Contact: <sip:1234 at 192.168.16.73:7594>
User-Agent: C610 IP/42.231.00.000.000
Event: message-summary
Expires: 3600
Allow: NOTIFY
Accept: application/simple-message-summary
Content-Length: 0


SIP/2.0 200 OK
Expires: 3600
Contact: <sip:192.168.16.70:5060>
Allow: OPTIONS, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE,
PRACK, REGISTER,
REFER, MESSAGE
Supported: 100rel, timer, replaces, norefersub
Server: FPBX-13.0.195.19(13.24.0)
Content-Length:  0
----------------------------------------------------------------------



After REGISTER:

----------------------------------------------------------------------
NOTIFY

Contact: <sip:1234 at 192.168.16.70:5060>
Call-ID: 7a5ee160-47a1-4efa-b190-66843d644243
CSeq: 9921 NOTIFY
Subscription-State: terminated
Event: message-summary
Allow-Events: message-summary, presence, dialog, refer
Max-Forwards: 70
User-Agent: FPBX-13.0.195.19(13.24.0)
Content-Type: application/simple-message-summary
Content-Length:    49

Messages-Waiting: yes
Voice-Message: 1/1 (0/0


SIP/2.0 200 OK
Call-ID: 7a5ee160-47a1-4efa-b190-66843d644243
CSeq: 9921 NOTIFY
User-Agent: C610 IP/42.231.00.000.000
Content-Length: 0
-----------------------------------------------------------------------

=> MWI on!

-> That was expected!



Now happens next REGISTER and after this, the next NOTIFY (the same as shown
above) is sent to the
phone

=> MWI is switched off!



If there coincidentally is a NOTIFY sequence in between ending with

Messages-Waiting: no
Voice-Message: 0/0 (0/0)
------------------------
Messages-Waiting: yes
Voice-Message: 1/1 (0/0

the MWI will be active again (this may be achieved if mwi aggregation is turned
off and the order is
exactly as shown above - but that's chance).




I'm wondering now: what's the generally expected behavior? Should the
phone handle repeatedly sent
NOTIFY packages for same voice mail as if they had been sent once or should
asterisk signal the same
voice mail only once and not repeatedly?


Configuration:

pjsip.aor.conf:
[1234]
mailboxes=1234 at default

pjsip.endpoint.conf
[1234]
aggregate_mwi=yes or no



Thanks,
kind regards,
Michael

On 26.12.18 at 14:48 Michael Maier wrote:
> Hello!
> 
> I'm facing a problem concerning MWI. The problem is:
> 
> The phone switches off the MWI exactly at the moment the second NOTIFY
package for one voice mail
> arrives.
> 
> The phone switches off MWI independently if the voice mail has been
acknowledged or not before.
> 
> 
> The behavior in detail:
> 
> - Once each hour, phone sends SUBSCRIBE
> - Asterisk receives incoming voice mail for Device 200.
> - some time later: Phone executes a REGISTER
> - Directly after succeeded REGISTER, asterisk sends Notify
> - Notify is acked by phone
After enabling debugging, I detected one more strange thing:

After the voice mail call has been ended w/ BYE, asterisk directly sends a
NOTIFY message - which
*never* reached the network stack!


[2018-12-26 16:51:46] DEBUG[4218]: res_mwi_devstate.c:50 mwi_update_cb: Sending
inuse devstate change for MWI:1234 at device
[2018-12-26 16:51:46] DEBUG[10322]: res_pjsip/pjsip_message_filter.c:288
filter_on_tx_message: Re-wrote Contact URI host/port to 192.168.16.70:5060 (this
may be re-written again later)
<--- Transmitting SIP request (660 bytes) to UDP:192.168.16.73:7594 --->
NOTIFY sip:1234 at 192.168.16.73:7594 SIP/2.0
Via: SIP/2.0/UDP
192.168.16.70:5060;rport;branch=z9hG4bKPjc8294b4c-0d0a-43b6-aaa3-3cd361fd44b2
From: "Home" <sip:1234 at
192.168.16.70>;tag=cdf1842f-6845-4419-9bba-b5aa648c1e1a
To: "Home" <sip:1234 at 192.168.16.70>;tag=494263154
Contact: <sip:192.168.16.70:5060>
Call-ID: 2516407290 at 192_168_16_73
CSeq: 18170 NOTIFY
Event: message-summary
Subscription-State: active;expires=1086
Allow-Events: message-summary, presence, dialog, refer
Max-Forwards: 70
User-Agent: FPBX-13.0.195.19(13.24.0)
Content-Type: application/simple-message-summary
Content-Length:    49

Messages-Waiting: yes
Voice-Message: 3/1 (0/0)


Compared to the NOTIFY-packages after REGISTER, there is a difference in
Subscription-State:

The NOTIFY tried to be sent after the end of the voice mail call has an active
state:

	Subscription-State: active;expires=1086

compared to the NOTIFY state after INVITE (which reach the network stack):

	Subscription-State: terminated


Thanks,
regards,
Michael

Hi!

I just want to say, that 13.24.1 doesn't fix the problem described in the
posts above.


Regards,
Michael