Hello,
is the proxy listening on 10080?
I haven't looked yet at the chance to return 2, but when I did the work
for gruu, some changes were done to rr module not to detect as strict
routing and everything seemed fine for this case.
Can you test with a version before the return 2 addition just to see if
the $du is set?
Cheers,
Daniel
On 4/18/13 5:15 PM, Juha Heinanen wrote:
my proxy (master version) receives this kind of ack to
invite:
ACK sip:jh@test.fi;gr=urn:uuid:eea2f222-60b6-4ba1-a764-99cc0eb3ba9f SIP/2.0
Route: <sip:Wvip1a55myyd/QXAYmYKJ2DAYmYK5U8=@192.98.102.10:10080;transport=ws;lr>
Via: SIP/2.0/WS gammj1mb37kg.invalid;branch=z9hG4bK6981394
Max-Forwards: 69
To: <sip:jh@test.fi>;tag=hosudd4jlh
From: "Test" <sip:test@test.fi>;tag=k808o8t8np
Call-ID: edbrqn9t6jbvf749ajil
CSeq: 2850 ACK
Supported: path, outbound, gruu
User-Agent: JsSIP 0.3.0
Content-Length: 0
i call loose_route() on it, which returns 2 (route calculation based on
flow-token has been successful) and after that $ru/$du are
Apr 18 17:56:44 siika /usr/sbin/sip-proxy[14517]: INFO: ru/du =
<sip:jh@test.fi;gr=urn:uuid:eea2f222-60b6-4ba1-a764-99cc0eb3ba9f>/<sip:T4Ah7mN1nrM0HgXAYmYKJ2DAYmYK5bA=@192.98.102.10:10080;transport=ws;lr>
why is $du set when there is only one route header denoting the proxy
itself?
how can i now test that routing should be based on r-uri, when $du gets
set for no reason?
-- juha
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
Daniel-Constantin Mierla -
http://www.asipto.com
http://twitter.com/#!/miconda -
http://www.linkedin.com/in/miconda