On Fri, 2007-09-07 at 08:44 -0400, Paul Kyzivat wrote: > You didn't say, but what I presume you are considering is embedding an > Expires parameter in the Refer-To URI: > > Refer-To: sip:[EMAIL PROTECTED]:60 > > This would then turn into an INVITE w/Expires. For this usage it doesn't > really matter whether it is done by the inviter or by the invitee, as > long as it is done. > > So I think this is a good usage, except that you must be concerned if > the referee will honor the embedded Expires header and put it into the > INVITE, and whether at least one of the referee and invitee act on it to > terminate the INVITE. These aren't sure things.
That's similar to how we do find-follow forwarding for users in sipXecs. The location service returns Contacts that have q value field parameters to control the order, and expires header parameters to control how long each is to be pursued. In a sipXecs system, the redirect is processed by our own forking proxy, so we don't need to worry about them being understood. -- Scott Lawrence tel:+1.781.229.0533;ext=162 or sip:[EMAIL PROTECTED] sipXecs project coordinator - SIPfoundry http://www.sipfoundry.org/sipXecs CTO, Voice Solutions - Bluesocket Inc. http://www.bluesocket.com/ http://www.pingtel.com/ _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
