IMO "pres" uri is meant for presentity/watchers participants for "presence" and related event packages. "sip" scheme is more generic and may include "sip protocol" participants including call and "presence". All these schemes are meant for IP domain. TEL scheme is defined to accommodate E.164 numbers from non-IP domain and SUBSCRIBE/NOTIFY framework is not defined for these entities unless you have some ENUM mapping available I am not sure whether this is convincing enough.
On Fri, Oct 24, 2008 at 3:23 PM, Iñaki Baz Castillo <[EMAIL PROTECTED]> wrote: > 2008/10/22 Iñaki Baz Castillo <[EMAIL PROTECTED]>: >> Hi, SIP Presence Event Package RFC( 3856 ) says that From and To of a >> SUBSCRIBE cannot be a TEL URI: >> >> Section 5. >> >> SUBSCRIBE messages also contain logical identifiers that define the >> originator and recipient of the subscription (the To and From header >> fields). These headers can take either a pres or SIP URI. >> >> >> Why? Why is valid a PRES URI but not a TEL? > > Any explanation please? > > -- > Iñaki Baz Castillo > <[EMAIL PROTECTED]> > > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
