IMHO you just need to add Record-Route header field at proxy to every
request. I think the applicable section of RFC3261 would be page 17:
" (...) In some cases, it may be useful for proxies in the SIP
signaling path to see all the messaging between the endpoints for the
duration of
the session. For example, if the
biloxi.com proxy server wished to
remain in the SIP messaging path beyond the initial INVITE, it would
add to the INVITE a required routing header field known as Record-
Route that contained a URI resolving to the hostname or IP address of
the proxy. This information would be received by both Bob's SIP
phone and (due to the Record-Route header field being passed back in
the 200 (OK)) Alice's softphone and stored for the duration of the
dialog. The
biloxi.com proxy server would then receive and proxy the
ACK, BYE, and 200 (OK) to the BYE. Each proxy can independently
decide to receive subsequent messages, and those messages will pass
through all proxies that elect to receive it. This capability is
frequently used for proxies that are providing mid-call features.
(...)"
--
Regards,
Arek Bekiersz
Ladislav Andel wrote:
fang tian wrote:
> Hi ,
> I am a new user of iptel ser,I want to make this configuration
>
> UE1,2,3,4<---------->IPtel ser
> <---------------------------------->application server ,
> the UEs send out invite request to iptel ser first ,I want to make
> iptel ser forward this request to application server with two route
> header added:
> route:application server :5060
> route:iptel ser :5060
> so the application server can send this request back to iptel ser.
> your kindly help is appreciated ,thanks
>
> RGS
> tian.