[Devel] Voicemail handling (message waiting indicator)

[Dimo]

HI guys,
Sorry, i was not near a computer to answer your questions.

Firstly - the silo module looks fine to mee too. I was thinking on
using it and it may be a great functionality if it can be expanded to
support the call-id from the subscribe. The only problem I see, (not
sure if i am correct) is that if a user has 3-4 phones, at the moment
the first phone registers, the silo will dump everything, and the
second phone will not know that there is a message waiting in VM.

About the unsolicited MWI, with random call-id - strangely some
versions of eyebeam do not accept the random call-id but demand the
one from registration, others act funny  - it is not the case in the
current version though, where unsolicited mwi works.
Other equipment I noticed requiring the call-id from Register is Linksys PAP 2T
So I think vendors are starting to adopt this strategy.

On a side note, i think it is better for equipment to require call-id
from register to avoid fakes, although MWI is not something so
critical, it still will result in people checking their VM when they
do not have messages wasting time similarly to spam, and even
complaining to their sip provider for false MWI.

What is your oppinion of making openser handling the SUBSCRIBE
messages? Something like a subscribe module which will use the info
from VM server and answer to subscriptions, with fallback to
registration call-id from register, if there is no subscribe.

Thank you for the active participation!
Dimo

On 1/27/07, Christian Schlatter <cs at unc.edu> wrote:
> Olle E Johansson wrote:
> >
> > 26 jan 2007 kl. 16.36 skrev Christian Schlatter:
> >
> >> Dimo,
> >>
> >> Could you list some example SIP UA products that do only accept MWI
> >> NOTIFYs with the caller-id from the initial registration?
> >>
> >> The endpoints I've seen so far do all accept so called unsolicited MWI
> >> NOTIFYs, so they don't care about the caller-id at all. Examples are
> >> Polycom, Snom, Cisco, or Linksys SIP phones.
> >>
> >
> > Either that or the callID from the SUBSCRIBE, but not the REGISTER.
> > Asterisk supports both ways.
> >
> > /O
> >
>
> With the caveat that Asterisk only supports SUBSCRIBE MWI for endpoints
> registered at the Asterisk box. Since we use OpenSER as registrar and
> Asterisk for VM this limits us to using the non-standard unsolicited MWI
> solution. That works well so far, but, rather paradoxically, I just hope
> that the SIP phone vendors keep supporting this non-standard behavior.
>
>
> Christian
>
> _______________________________________________
> Devel mailing list
> Devel at openser.org
> http://openser.org/cgi-bin/mailman/listinfo/devel
>