[asterisk-dev] SUBSCRIPTION for MWI support for multiple boxes

Norman Brandinger norm at goes.com
Wed Sep 19 16:31:11 CDT 2007


Norman Brandinger wrote:
> In reference to this thread:
>
> http://lists.digium.com/pipermail/asterisk-dev/2006-October/023925.html
>
> Was this idea tabled or was it implemented ?  I would be willing to put
> some development efforts into helping to make this work (so that we can
> remove, or at least not wholly depend on externnotify).
>
> In a nutshell, would appear to require multiple NOTIFYs being sent from
> Asterisk to the peer, one for each "mailbox=" entry.
>
> We are trying to implement a SPA9000 solution without depending on the
> SPA400 voicemail server (which, by the way, is based on Asterisk).

Just from memory, this is how I would expect things to work in Asterisk
right now.

In 1.4, you can have multiple mailboxes specified - mailbox=1234,5678 at
foo.
Asterisk will not send separate NOTIFY messages for each mailbox.  It will
determine a combined mailbox state and send that.

In trunk, it will actually send the state of each mailbox in a separate
NOTIFY
message.  Also, FWIW, the code to do this is actually very invasive and
would
not be easily backported.

-- 
Russell Bryant
Software Engineer
Digium, Inc.




I'm running SVN-trunk-r82835 over here in a test environment and only a
single NOTIFY is generated, even with multiple mailbox entries.  The
single NOTIFY does not appear to use the mailbox name (54321 and/or
654321) in any part of the message.

Note the invalid To header in the NOTIFY.  I've opened
http://bugs.digium.com/view.php?id=10756 against it.  Perhaps this error
is causing the rest of the NOTIFY to peer processing to fail.

Regards,
Norm


[2125551212]
context=SPA9000
canreinvite=no
subscribecontext=SPA9000
type=peer
host=test.example.com
disallow=all
allow=ulaw
call-limit = 4
subscribemwi=yes
mailbox=54321 at 2125551212, 654321 at 1215551212
vmexten=2125551212


Reliably Transmitting (NAT) to 111.222.333.28:5060:
NOTIFY sip:2125551212 at 192.168.1.190:5060 SIP/2.0
Via: SIP/2.0/UDP 111.222.333.28:5060;branch=z9hG4bK4e8135c0;rport
Max-Forwards: 70
From: "asterisk" <sip:asterisk at test.example.com>;tag=as6c76fb49
To: <sip:sip:2125551212 at 192.168.1.190:5060>;tag=e243619ea6bfe323
Contact: <sip:asterisk at 111.222.333.28:5060>
Call-ID: 2b91837a-83d6caf7 at 192.168.1.190
CSeq: 102 NOTIFY
User-Agent: Asterisk PBX
Event: message-summary
Content-Type: application/simple-message-summary
Subscription-State: active
Content-Length: 99

Messages-Waiting: no
Message-Account: sip:2125551212 at test.example.com
Voice-Message: 0/0 (0/0)





More information about the asterisk-dev mailing list