[SIPForum-discussion] Help needed with SIP routing decision

Yevgen Krapiva ykrapiva at gmail.com
Wed Apr 15 08:14:53 UTC 2009


I'm writing statefull proxy. Statefull proxy behavior section in RFC
doesn't pay attention to special requests like ACK and BYE.

Here is a ACK I receive in proxy server:

ACK sip: SIP/2.0
Route: <sip:user1 at>
CSeq: 1 ACK
Via: SIP/2.0/UDP;branch=z9hG4bK0cb70b0f-1028-de11-9edf-dfde3e6514eb;rport=5070;received=
From: "Phone B"
<sip:user2 at kv-po-ykrapivanb.umc.com.ua>;tag=4647660d-1028-de11-9edf-dfde3e6514eb
Call-ID: 3e40660d-1028-de11-9edf-dfde3e6514eb at kv-po-krapiva2.umc.com.ua
To: <sip:user1 at kv-po-ykrapivanb.umc.com.ua>;tag=c066ed41
Contact: <sip:user2 at;transport=udp>
Max-Forwards: 70
Content-Length: 0

Here is proxy's IP, is another peer's IP.

So, this request is for the proxy, and RFC says I should use Location
Service to determine the next target. Yes, that works, but this ACK
request also has Route header that points to the same IP as it were
retrieved from Location Service.

So the question is: Should I check Route header presence before
contacting Location Service or not ?

I didn't find the statement regarding this issue in RFC. If I've
missed something, please point.


More information about the discussion mailing list