SUBSCRIPTION for MWI support for multiple boxes

In reference to this thread:

http://lists.digium.com/pipermail/asteris
k-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).

Regards,
Norm

p.s. I'll be really embarrassed if this already works and I
couldn't
figure out how to configure it (even after RTFM/RTFT).

Below is the relevant section of the Linksys SPA9000 Admin
Guide:

The SPA9000 sends a one-time SUBSCRIBE for the
message-summary event
package for each line with a valid <Mailbox Subscribe
URL>. The
SUBSCRIBE implies subscription for the status of all the
mailboxes
associated with the voicemail account used-ID; it does not
include any
mailbox ID in the request. Following is an example:

SUBSCRIBE sip:mailbox-subscribe-url SIP/2.0
Via: SIP/2.0/UDP 172.16.22.23:5062;branch=z9hG4bK-44f9d0f0
From: Line 3 <sip:14089991003sip.myitsp.com>;tag=ac6013983cce7526
To: <sip:mailbox-subscribe-url>
Call-ID: ace86200-bbe839de172.16.22.23
CSeq: 63017
SUBSCRIBE Max-Forwards: 70
Contact: <sip:14089991003172.16.22.23:5062>
Expires: 2147483647
Event: message-summary
User-Agent: Sipura/SPA9000-3.2.2
Content-Length: 0

Note that the Expires value is purposely set to a very large
number so
the subscription does not expire and there is no need to
renew the
subscription. The voicemail server is expected to send a
NOTIFY
immediately upon receiving this SUBSCRIBE message for each
mailbox on
this account. The Request-URI of the NOTIFY should reference
the CONTACT
header of the corresponding SUBSCRIBE, but the user-ID in
the To header
should be the mailbox ID. The following example shows a
NOTIFY for the
mailbox ID 5031 on the account 14089991003:

NOTIFY sip:14089991003172.16.22.23:5062 SIP/2.0
Via: SIP/2.0/UDP 178.178.221.230;branch=z9hG4bK-44f9d0f0
From: <sip:voicemailsip.myitsp.com>;tag=ab789
To: <sip:5031172.16.22.23:5062>;tag=ac6013983cce7526
Call-ID: ace86200-bbe839de178.178.221.230
CSeq: 537
NOTIFY Expires: 2147483647
Event: message-summary User-Agent: ITSP/Voicemail-Server
Content-Length: 0

_______________________________________________

Sign up now for AstriCon 2007!  September 25-28th.  http://www.astricon.net/


--Bandwidth and Colocation Provided by http://www.api-digital.c
om--

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

Norman Brandinger wrote:
> In reference to this thread:
> 
> http://lists.digium.com/pipermail/asteris
k-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,5678foo.
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.

_______________________________________________

Sign up now for AstriCon 2007!  September 25-28th.  http://www.astricon.net/


--Bandwidth and Colocation Provided by http://www.api-digital.c
om--

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

Norman Brandinger wrote:
> In reference to this thread:
>
> http://lists.digium.com/pipermail/asteris
k-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=543212125551212, 6543211215551212
vmexten=2125551212


Reliably Transmitting (NAT) to 111.222.333.28:5060:
NOTIFY sip:2125551212192.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:asterisktest.example.com>;tag=as6c76fb49
To: <sip:sip:2125551212192.168.1.190:5060>;tag=e243619ea6bfe323
Contact: <sip:asterisk111.222.333.28:5060>
Call-ID: 2b91837a-83d6caf7192.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:2125551212test.example.com
Voice-Message: 0/0 (0/0)



_______________________________________________

Sign up now for AstriCon 2007!  September 25-28th.  http://www.astricon.net/


--Bandwidth and Colocation Provided by http://www.api-digital.c
om--

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev