Based on RFC 3261, a target refresh request is used by one UA to tell the other UA a new target URI to send future requests to (see section 12.2). The target URI is placed in the Contact header of the request. The route set (the set of URIs to include in the Route header of the request) is established by the original INVITE transaction that established the dialog. You are not suppose to change the route set. Thus a target refresh request does not change the route set.
The Request-URI of the target refresh request will be the target URI of the other UA learned from the Contact header of the original INVITE transaction or the latest target refresh request from that other UA. The Route header values in the target refresh request will cause the request to visit the same proxies that the original INVITE transaction passed thru. They are allowed to Record-Route the request, but you would end up with the same set of Record-Route headers as the original request. cheers, (-:bob Robert F. Penfield Chief Software Architect Acme Packet, Inc. 130 New Boston Street Woburn, MA 01801 [EMAIL PROTECTED] ----- Original Message ----- From: "Kool Guy" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, October 18, 2002 10:35 AM Subject: Fwd: [Sip-implementors] Question on target refresh > A while back I had asked few questions about SIP Proxy target refresh. > > Does anyone have answers? > > Thanks > ------------------------------------------------------------- > Could someone give an example of a target refresh call flow. > > How does the RequestURI and the route header in the two > requests work out. > > Is it possible to do a target refresh with the older record route > or with the loose routing mechanism. > > When a target refresh comes to the SIP Proxy, is the new route header > based on the new request URI or the existing recordRoute? > > _________________________________________________________________ > Get faster connections -- switch to MSN Internet Access! > http://resourcecenter.msn.com/access/plans/default.asp > > _______________________________________________ > 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
