RE: [Sip] INFO: A recap, sense of consensus and a proposal for direction.

[Hadriel Kaplan <HKaplan at acmepacket.com>]

> -----Original Message-----
> From: Francois Audet [mailto:audet at nortel.com]
>
> > Or a package
> > for sending vcard info to the caller/called.  Or a package
> > for giving out a jpeg for photo-id, or for call screen
> > display.
>
> Isn't that what the Call-info header is exactly for (RFC 3261/20.9)?

It was my understanding the Call-Info header was to give a URI to go fetch stuff from, usually an HTTP URI (if one could use the term "usually" for the Call-Info header ;).  That is highly unlikely I think, since it is highly unlikely a SIP UA has a web-server to provide such, or one globally reachable (like, good luck if it's behind a NAT/FW).  I guess you could put in a SIP URI and tell it to Subscribe for a jpeg photo-id package, and stick some cookie in the uri so the serving UA can correlate the subscribe request to the call (i.e., which call is asking for this info?).  <sarcasm>Yeah that's a lot more reasonable than just using the Invite dialog to send it in an INFO.</sarcasm>

-hadriel



_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip