Bogdan I used local cache to store the Request URI and then changed the contact Header of 200 OK at Proxy by replacing the contact from RURI. It worked for me. But you can see in 200 OK UAS-Proxy that UAS is changing the Contact with proxy IP. Bob-Proxy SIP/2.0 200 OKVia: SIP/2.0/UDP proxy.com:7000;branch=z9hG4bK9347.84c78b97.0Via: SIP/2.0/UDP sipuas.com:7000;branch=z9hG4bK9347.4f022b62.0Via: SIP/2.0/UDP proxy.com:7000;branch=z9hG4bK9347.74c78b97.0Via: SIP/2.0/UDP 172.16.37.66:5065;received=203.215.176.22;rport=33611;branch=z9hG4bK266489159Record-Route: <sip:proxy.com:7000;lr;ftag=1397829413>Record-Route: <sip:923071000...@sipuas.com:7000;lr;ftag=1397829413;did=bbf.3846c9b2>Record-Route: <sip:proxy.com:7000;lr;ftag=1397829413;EdgeProxy=true>Contact: <sip:923071000202@139.190.68.251:34580;transport=UDP>To: <sip:923071000...@sip.realm.com:7000>;tag=ab9efd6aFrom: "+923071000201" <sip:+923071000...@sip.realm.com>;tag=1397829413Call-ID: 146889629CSeq: 21 INVITEAllow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBEContent-Type: application/sdpSupported: replaces, norefersub, extended-refer, timer, outbound, path, X-cisco-serviceuriUser-Agent: Zoiper r30645Allow-Events: presence, kpmlContent-Length: 243 proxy-UAS SIP/2.0 200 OKVia: SIP/2.0/UDP sipuas.com:7000;branch=z9hG4bK9347.4f022b62.0Via: SIP/2.0/UDP proxy.com:7000;branch=z9hG4bK9347.74c78b97.0Via: SIP/2.0/UDP 172.16.37.66:5065;received=203.215.176.22;rport=33611;branch=z9hG4bK266489159Record-Route: <sip:proxy.com:7000;lr;ftag=1397829413>Record-Route: <sip:923071000...@sipuas.com:7000;lr;ftag=1397829413;did=bbf.3846c9b2>Record-Route: <sip:proxy.com:7000;lr;ftag=1397829413;EdgeProxy=true>Contact: <sip:923071000202@139.190.68.251:34580;transport=UDP>To: <sip:923071000...@sip.realm.com:7000>;tag=ab9efd6aFrom: "+923071000201" <sip:+923071000...@sip.realm.com>;tag=1397829413Call-ID: 146889629CSeq: 21 INVITEAllow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBEContent-Type: application/sdpSupported: replaces, norefersub, extended-refer, timer, outbound, path, X-cisco-serviceuriUser-Agent: Zoiper r30645Allow-Events: presence, kpmlContent-Length: 243 UAS-Proxy SIP/2.0 200 OKVia: SIP/2.0/UDP proxy.com:7000;branch=z9hG4bK9347.74c78b97.0Via: SIP/2.0/UDP 172.16.37.66:5065;received=203.215.176.22;rport=33611;branch=z9hG4bK266489159Record-Route: <sip:proxy.com:7000;lr;ftag=1397829413>Record-Route: <sip:923071000...@sipuas.com:7000;lr;ftag=1397829413;did=bbf.3846c9b2>Record-Route: <sip:proxy.com:7000;lr;ftag=1397829413;EdgeProxy=true>Contact: <sip:923071000...@proxy.com:7000;transport=UDP>To: <sip:923071000...@sip.realm.com:7000>;tag=ab9efd6aFrom: <sip:923071000...@sip.realm.com:7000>;tag=1397829413Call-ID: 146889629CSeq: 21 INVITEAllow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBEContent-Type: application/sdpSupported: replaces, norefersub, extended-refer, timer, outbound, path, X-cisco-serviceuriUser-Agent: Zoiper r30645Allow-Events: presence, kpmlContent-Length: 257 Proxy-Alice # remove_hf("Contact"); append_hf("Contact: <$var(uri)>;transport=UDP>/r/n"); SIP/2.0 200 OKVia: SIP/2.0/UDP 172.16.37.66:5065;received=203.215.176.22;rport=33611;branch=z9hG4bK266489159Record-Route: <sip:proxy.com:7000;lr;ftag=1397829413>Record-Route: <sip:923071000...@sipuas.com:7000;lr;ftag=1397829413;did=bbf.3846c9b2>Record-Route: <sip:proxy.com:7000;lr;ftag=1397829413;EdgeProxy=true>To: <sip:923071000...@sip.realm.com:7000>;tag=ab9efd6aFrom: <sip:923071000...@sip.realm.com:7000>;tag=1397829413Call-ID: 146889629CSeq: 21 INVITEAllow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBEContent-Type: application/sdpSupported: replaces, norefersub, extended-refer, timer, outbound, path, X-cisco-serviceuriUser-Agent: Zoiper r30645Allow-Events: presence, kpmlContent-Length: 257Contact: <sip:923071000202@139.190.68.251:34580;transport=UDP>
RegardsHamid R. Hashmi Date: Wed, 9 Sep 2015 12:58:36 +0300 From: bog...@opensips.org To: hamid2kv...@hotmail.com; users@lists.opensips.org Subject: Re: [OpenSIPS-Users] ACK did not Receive on Proxy and get in loop Hi Hamid, If you use PATH support on the proxy, this should translate into UAS adding an extra Route header when routing calls back the UAS. Nevertheless, the PATH does not interfere and change anything when comes to the sequential requests. Could you post the 200 OK between UAS-proxy and proxy-UAC ? Best regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 07.09.2015 14:23, Hamid Hashmi wrote: Bogdan, I am using path module on Both servers (Proxy - add_path_receive() and UAS - use_received 1 ). UAS change the Contact header of 200 OK with the IP given in field 'path' in table 'location'. But when I make a call by bypassing proxy, UAS did not change the contact header. What am I doing wrong in using module Path ? Regards Hamid R. Hashmi Date: Mon, 7 Sep 2015 13:16:35 +0300 From: bog...@opensips.org To: users@lists.opensips.org; hamid2kv...@hotmail.com Subject: Re: [OpenSIPS-Users] ACK did not Receive on Proxy and get in loop Hi Hamid, There is something wrong with the contact in the 200 OK - as you see, the 200 OK reply from proxy to Alice contains in the Contact header the IP of the the proxy, while it should contain the IP address of BOB (the issuer of that reply). Because of that bogus Contact header, the whole in-dialog routing (for the ACK) gets broken. Best Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 03.09.2015 09:29, Hamid Hashmi wrote: Dear Bogdan and Sammy 200 OK received to Alice is as follows SIP/2.0 200 Ok Via: SIP/2.0/UDP 203.215.176.22:43912;received=203.215.176.22;branch=z9hG4bK-d87543-769673078-1--d87543-;rport=48008 From: 923071000201<sip:923071000...@sip.realm.com>;tag=450fb754 To: <sip:00923071000...@sip.realm.com>;tag=b1UXiUx Call-ID: ac263a229e15d211 CSeq: 3 INVITE User-Agent: LinphoneAndroid/2.5.0 (belle-sip/1.4.1) Supported: outbound Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO, UPDATE Contact: <sip:923071000...@proxy.com:1234>;+sip.instance="<urn:uuid:05d62157-0f77-46f8-9dee-5c37a646cbc6>" Content-Type: application/sdp Content-Length: 181 Record-route: <sip:proxy.com:1234;lr> Record-route: <sip:00923071000...@sipuas.com:1234;lr;ftag=450fb754;did=1cd.ad2b02c7> While Alice send ACK as Follows ACK sip:923071000...@proxy.com:1234 SIP/2.0 To: <sip:00923071000...@sip.realm.com>;tag=b1UXiUx From: 923071000201<sip:923071000...@sip.realm.com>;tag=450fb754 Via: SIP/2.0/UDP 203.215.176.22:43912;branch=z9hG4bK-d87543-546180712-1--d87543-;rport Call-ID: ac263a229e15d211 CSeq: 3 ACK Route: <sip:00923071000...@sipuas.com:1234;lr;ftag=450fb754;did=1cd.ad2b02c7> Route: <sip:proxy.com:1234;lr> Contact: <sip:923071000201@203.215.176.22:50056> Max-Forwards: 70 Proxy-Authorization: Digest username="923071000201",realm="sip.realm.com",nonce="55e6f4533b45a508ef98ccd396274bf65ba99882",uri="sip:00923071000...@sip.realm.com:1234",response="5eea832060c8218b4229a8623d26bf1d",cnonce="825a886fc914ef2a",nc=00000001,qop=auth,algorithm=MD5 User-Agent: eyeBeam release 3007n stamp 17816 Content-Length: 0 ACK must be sent to TOP most Record-route first but its going to sceond Record-route first. Is it a correct behavior ? Regards Hamid R. Hashmi Date: Wed, 2 Sep 2015 11:11:28 -0400 From: govoi...@gmail.com To: users@lists.opensips.org Subject: Re: [OpenSIPS-Users] ACK did not Receive on Proxy and get in loop I beleive you have to engage NAT corrections in reply route for 200OK. I havent seen your SIP trace but if im Comtaact header the IP is of UAS and it goes to the caller side ACK will get directly to that IP. Just my guess. Need more info from you. Regards, Sammy On Sep 2, 2015 10:24 AM, "Hamid Hashmi" <hamid2kv...@hotmail.com> wrote: ACK is not receiving on Proxy, It directly goes to UAS and get in loop at Proxy before relayed to bob. Can you explain why ACK is going directly to UAS while all other responses going to proxy? Alice Proxy UAS Bob | | | | | INVITE | | | |--------------->| INVITE | | | 100 |--------------->| | |<---------------| INVITE | | | |<---------------| | | | | | | | INVITE | | |-------------------------------->| | | | | | | 180 | | |<--------------------------------| | | | | | | 180 | | | |--------------->| | | | | | | | 180 | | | 180 |<---------------| | |<---------------| | | | | 200 | | |<--------------------------------| | | | | | | 200 | | | |--------------->| | | | | | | | 200 | | | |<---------------| | | 200 | | | |<---------------| | | | | | | | ACK | | |-------------------------------->| | | | ACK | | | |<---------------| | | | | | | ACK | | | | | | | ACK | | | | | | | ACK | | . . . . . . . . . . . . Regards Hamid R. Hashmi _______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users