[Asterisk-Dev] Routing NOTIFY Messages?

[John J. Sawa]

I'm going out on a limb here so please excuse my ignorance as I am just 
getting familiar with the architecture of *. Would it not be possible to 
allow a definition in the [peers] section of sip.conf for example, 
allownotify=yes which would then allow the routing of NOTIFY messages to 
that peer and in this case just an extension?

I also am taking your advice on pursing another SIP proxy to implement 
this. -John

Olle E. Johansson wrote:

> John J. Sawa wrote:
>
>> Is it possible to route SIP NOTIFY messages through * ?
>>
>> Basically, I have an external VoiceMail application that needs the 
>> ability to send SIP NOTIFY messages to * users, in order to do MWI to 
>> the SIP phones. I realize the asterisk voicemail application does 
>> this, but does * have the ability to accept these SIP messages from 
>> another application. If so, will my application have to REGISTER then 
>> INVITE the phone then send the NOTIFY message?
>>
>> Currently, my application can send NOTIFY messages directly to the 
>> phones in order to turn on and off MWI, but I would really like to be 
>> able to send these messages to * and have it handle the routing to 
>> the endpoints as * knows all the endpoints due to registration and 
>> proxy capabilities. Any input on if and how this can be done would be 
>> appreciated.
>
> Incoming NOTIFYs are not handled by Asterisk at all. Asterisk
> sends outbound NOTIFY messages for MWI to SIP peers with
> mailbox= definition in [peer] section of sip.conf.
>
> The problem with routing incoming NOTIFY is how to handle them, as with
> many other SIP non-call things in Asterisk,  Is the user part of
> the URI an extension or a SIP peer? It's not obvious.
> We can't easily have two name spaces, so today the default handling is
> sending a NOTIFY to an extension. SUBSCRIBEs have more or less
> the same problem, the implementation today allows SUBSCRIBE to
> an Asterisk extension. Many Asterisk admins want to subscribe to
> a SIP peer, which breaks the architecture somewhat.
>
> The best solution today is to use a SIP proxy for doing this kind
> of stuff.
>
> /Olle
> _______________________________________________
> Asterisk-Dev mailing list
> Asterisk-Dev at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-dev
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-dev