Iñaki,
Iñaki Baz Castillo wrote:
> 2010/4/20 Brett Tate <br...@broadsoft.com>:
>> section 5.1.1.1:
>> " If all the Contact header fields in a REGISTER request are SIPS, the
>> UAC MUST use SIPS AORs in the From and To header fields in the
>> REGISTER request. If at least one of the Contact header fields is
>> not SIPS (e.g., sip, mailto, tel, http, https), the UAC MUST use SIP
>> AORs in the From and To header fields in the REGISTER request.
>> "
>
> Is it a joke? or another hyper-exotic and unfeasible feature born in
> IETF? how is supposed that a Contact field in a REGISTER can be a
> "mailto" or "http"???
It is not a joke, though I have never heard of it being used yet.
Obviously such a contact cannot be used for transporting sip traffic.
However it can potentially be used as an alternative means of reaching
the AOR.
For instance, if a mailto: url were among the registered contacts, and
none of the sip contacts was reachable, the proxy for the AOR could
return a 3xx with the mailto contact. Then the caller could send an
email with a message. This is potentially a voicemail mechanism that
doesn't require a voicemail server.
Another possibility is a tel: URL.
Rather that considering it "hyper-exotic and unfeasible", you could just
consider it "forward looking".
Thanks,
Paul
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
