Rajesh Khandewale wrote:
Rohan,
Thanks so much for your quick and detailed response!
Voice mail sessions are generally short lived and transient, so I would like to know what is the use for registering per user in case of voice mail
Most *calls* are generally short and transient.
scenarios. Is this more for a scenario where the user registers with the main proxy (e.g. web client) and then all entities (e.g. messaging notifier) can register for that user with callee capabilities.
The VM would register for the same reason that any UA does - so the proxy responsible for the Address of Record will know it is one of the candidate locations that calls might be routed.
As Rohan explained, you might do this if your proxy doesn't implicitly provide a VM server.
Paul
Rajesh.
-----Original Message----- From: Rohan Mahy [mailto:[EMAIL PROTECTED]
Hi,
The example shows how a messaging notifier (typically a voicemail server) can register its *capabilities* with a registrar. By definition any process that involves a REGISTER request is only for the resource specified in the To header (per user).
In practice its very unlikely that a voicemail/messaging server would make itself know to a proxy in the same domain. It is much more likely that the relationship between a sip proxy and a messaging server is administratively configured. However, if I have a voicemail server in a different domain, I could do a third party registration like this:
REGISTER sip:iptel.org SIP/2.0 To: <sip:[EMAIL PROTECTED]> From: <sip:[EMAIL PROTECTED]>;tag=08934471 Contact: <sip:[EMAIL PROTECTED]> ;actor="msg-taker";methods="SUBSCRIBE" ;automata;events="message-summary" etc...
This causes iptel.org (assuming iptel.org supported callee capabilities) to store the actor, methods, automata, and events capabilities along with my Contact at mailboxes.com.
Going back to the administratively configured case, if the result of that configuration is that the some entity populates a Contact with callee capabilities into the data store used for SIP registrations, then the caller preferences routing described in RFC 3842 can work appropriately.
Hope this helps.
thanks, -rohan
On Mar 25, 2005, at 7:59, Rajesh Khandewale wrote:
Section 4.2. of RFC3842, gives an example on how a messaging notifier can register the callee preferences with the registrar. I am a little unclear on whether this is per user or for the messaging notifier UA? If it's for UA then how are the From, To and Contact headers specified. Has anyone done this before?
Rajesh.
_______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
