Hi Aqs,

the 'loose_routing' mechanism was not changed it terms of behavior - if a local IP/domain is found in RURI, it considers that the previous hop was a strict router. So, either 45.77.69.46 it should not be listed as local IP, either the routing is broken making 45.77.69.46 IP to get into RURI.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
OpenSIPS Bootcamp 2018
  http://opensips.org/training/OpenSIPS_Bootcamp_2018/

On 09/23/2018 07:25 PM, Aqs Younas wrote:
ok, digging more i see this used to happen when RURI contains the address added into opensips as domain. I remember this used to work fine before. As i am routing dispatching request to multiple media servers based upon domain.

Any pointer on this?

Br, Aqs.

On Sun, 23 Sep 2018 at 00:08, Aqs Younas <[email protected] <mailto:[email protected]>> wrote:

    Greetings list,

    I am using opensips to bridge between two different networks. But
    I see my in-dialog requests being messed up inside the opensips.
    Looks like opensips is performing strict routing at loose_route()
    function resulting in-dialog requests to never reach destination.

    Bye Coming to opensips.

    2018/09/22 18:34:48.230224 39.38.137.105:5060
    <http://39.38.137.105:5060> -> 167.99.37.41:5080
    <http://167.99.37.41:5080>
    BYE sip:[email protected]:5060;transport=udp SIP/2.0
    CSeq: 3 BYE
    From: "1010" <sip:[email protected]
    <mailto:sip%[email protected]>>;tag=54afd375
    To: <sip:[email protected]
    <mailto:sip%[email protected]>>;tag=B6DU3jrK9mjBc
    Call-ID: 0c42f165809a65019216a92969e38cb6@0:0:0:0:0:0:0:0
    Max-Forwards: 70
    Route:
    
<sip:167.99.37.41:5080;r2=on;lr;ftag=54afd375;nat=yes>,<sip:167.99.37.41:6060;r2=on;lr;ftag=54afd375;nat=yes>
    Via: SIP/2.0/UDP
    192.168.10.3:5060;branch=z9hG4bK-323230-ef1af21aa6eeac828830f4063d89d607
    Contact: "1010"
    <sip:[email protected]:5060;transport=udp;registering_acc=45_77_69_46>
    Proxy-Authorization: Digest
    
username="1010",realm="45.77.69.46",nonce="2874ff58-bf0e-4ede-aecf-74ddd539ac62",uri="sip:[email protected]
    
<mailto:sip%[email protected]>",response="a931d609c29b569494ffa7e11c7c6c9b",algorithm
    D5,qop=auth,cnonce="xyz",nc=00000001
    User-Agent: Jitsi2.10.5550Windows 10
    Content-Length: 0

    Bye leaving opensips.

    2018/09/22 18:34:48.234429 167.99.37.41:5080
    <http://167.99.37.41:5080> -> 167.99.37.41:6060
    <http://167.99.37.41:6060>
    *BYE sip:167.99.37.41:6060;r2=on;lr;ftag=54afd375;nat=yes SIP/2.0*
    CSeq: 3 BYE
    From: "1010" <sip:[email protected]
    <mailto:sip%[email protected]>>;tag=54afd375
    To: <sip:[email protected]
    <mailto:sip%[email protected]>>;tag=B6DU3jrK9mjBc
    Call-ID: 0c42f165809a65019216a92969e38cb6@0:0:0:0:0:0:0:0
    Max-Forwards: 69
    Via: SIP/2.0/UDP 167.99.37.41:5080;branch=z9hG4bK0993.18510595.0
    Via: SIP/2.0/UDP
    
192.168.10.3:5060;rport=5060;received=39.38.137.105;branch=z9hG4bK-323230-ef1af21aa6eeac828830f4063d89d607
    Contact: "1010"
    <sip:[email protected]:5060;transport=udp;registering_acc=45_77_69_46>
    Proxy-Authorization: Digest
    
username="1010",realm="45.77.69.46",nonce="2874ff58-bf0e-4ede-aecf-74ddd539ac62",uri="sip:[email protected]
    
<mailto:sip%[email protected]>",response="a931d609c29b569494ffa7e11c7c6c9b",algorithm
    D5,qop=auth,cnonce="xyz",nc=00000001
    User-Agent: Jitsi2.10.5550Windows 10
    Content-Length: 0

    Could someone give me some pointers on this?

    Any help is much appreciated.

    Br, Aqs.



_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to