Subscribing for presence and message-summary are two completely different
things, just because one works doesn’t mean the other will.
Agreed, however I simply wanted to make it clear that this client is
completely capable of authenticating to the server, in order to avoid anyone
suggesting that that was the problem, causing the 404 Not Found.
For subscribing to MWI the mailbox(es) have to be configured on the AOR[1].
That’s potentially useful information I can feed back to the provider.
The endpoint also has to subscribe to the mailbox itself,
I presume that by “endpoint” you’re referring to my SIP client?
so if the mailbox is 6000 then it needs to subscribe to 6000.
Pardon my ignorance, but what else would it subscribe to? My extension on
this system is 941, and the mailbox is 941, so my SUBSCRIBE request is
specifying 941. I don’t really see what the alternative would be?
There is also an option[2] that can be used to do unsolicited until a
subscription occurs.
The PBX system is sending unsolicited NOTIFYs containing the message-summary
data, however this SIP client ignores that unless / until it has successfully
SUBSCRIBEd and received a 200 OK response.
[1]
https://github.com/asterisk/asterisk/blob/master/configs/samples/
pjsip.conf.sample#L1133
So, in your example above, this should be mailboxes=6000?
[2]
https://github.com/asterisk/asterisk/blob/master/configs/samples/
pjsip.conf.sample#L674
So, if mwi_subscribe_replaces_unsolicited=no does that mean that a SIP client
can SUBSCRIBE, but that the server will also continue sending unsolicited
NOTIFYs (for other clients which aren’t so fussy)?
Thanks,
Antony.