Voice Mail: MWI Problem / Pjsip (13.24.0)

Home » Asterisk Users » Voice Mail: MWI Problem / Pjsip (13.24.0)
Asterisk Users 6 Comments

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:
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:
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:
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@default

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

Thanks, kind regards, Michael

—

6 thoughts on - Voice Mail: MWI Problem / Pjsip (13.24.0)

  • 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@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@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” ;tag=cdf1842f-6845-4419-9bba-b5aa648c1e1a To: “Home” ;tag=494263154
    Contact:
    Call-ID: 2516407290@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

    —

  • Before I’m opening an issue, I would like to prove my expectations – maybe it isn’t a problem at all or it’s a problem of the phone.

    That’s how it works at the moment:

    – MWI Mode: unsolicited
    – MWI Aggregation: on
    – Call arrives and is received as voice mail

    – after next REGISTER, the first NOTIFY is sent to phone
    – Phone message indicator is blinking and display says: 1 VM
    – after next REGISTER, same NOTIFY is sent again
    – Phone message indicator stops blinking. Display still says 1 VM
    – …

    => The phone switches of blinking indicator if NOTIFYs repeatedly send the very same information. If there is meanwhile
    one more VM signaled, the indicator is blinking again until this new NOTIFY is sent repeatedly.

    My questions:
    – Is MWI exactly expected to repeatedly send the same information?

    – Is it expected, that unsolicited MWIs are sent only after a REGISTER and not at the moment the VM has been finalized?

    Thanks, Michael

    —

  • Michael,

    Just a side note. I’ve had reports of MWI not turning off after a message has been listened to under both 13.24.0 and 13.24.1. It will typically turn off after a few minutes. We’re just using chan_sip. I haven’t had any reports when we were under 13.23.1

    Doug

    —

  • Turning off isn’t a problem here: Any time I’m requesting VMs on the phone, the blinking MWI is turned off and no voice mails are shown on the display any more (I think it’s done by the phone itself) – until next REGISTER / NOTIFY is retrieved: if there is any unrequested / new voice mail left, it will be signaled again by blinking MWI and on the display.

    Regards, Michael

    —