Hi Daniel

I was actually using

kamailio:5069 lookup() => 12345678@kamailio:5070 forward() => kamailio:5071 t_relay()
                                u1
@kamailio:5070 (404)

I thus tried to change forward() to t_relay(), but then I found that the call was cancelled. Removing all 404 reply generations in the system, made my call get through.

It seems that lookup() branched the call, and the "u1" branch in kamailio:5070 generated a 404 back to kamailio:5069, but also a cancel to kamailio:5071. The cancel to kamailio:5071 was however for the u1 branch and not the 12345678 branch. But the callid was the same!


-------------------- Med Liberalistiske Hilsner ----------------------
   Civilingeniør, Kjeld Flarup - Mit sind er mere åbent end min tegnebog
   Sofienlundvej 6B, 7560 Hjerm, Tlf: 40 29 41 49
   Den ikke akademiske hjemmeside for liberalismen - www.liberalismen.dk

On 04/10/2018 10:49 AM, Daniel-Constantin Mierla wrote:

Looks like the socket used for sending out is the loopback address and thus cannot send to 192.168.2.101.

Do you use t_relay() for forwarding the request?

Cheers,
Daniel


On 10.04.18 10:08, Kjeld Flarup wrote:
Listening is configured like this:
#!define LOCALIP 192.168.2.9
#!subst "/LOCALIP/192.168.2.9/g"
listen=LOCALIP:5069

Kjeld

2018-04-10 9:43 GMT+02:00 Daniel-Constantin Mierla <miconda@gmail.com>:

Hello,

is the instance throwing the error listening only on 127.0.0.1 address?

Cheers,
Daniel


On 09.04.18 23:54, Kjeld Flarup wrote:

Hi

I have a setup with three kamailio's in the same host but on different ports. client ->5069 -> 5070 -> 5071 -> SIP provider

Now I get this error from the 5069 Kamailio when it is routing a 200 Ok to the client:

Apr  9 21:54:10 kfcpbx /usr/sbin/kamailio[9688]: ERROR: <core> [forward.c:181]: get_out_socket(): no socket found
Apr  9 21:54:10 kfcpbx /usr/sbin/kamailio[9688]: ERROR: <core> [forward.c:183]: get_out_socket(): no corresponding socket found for(udp:192.168.2.101:10120)
Apr  9 21:54:10 kfcpbx /usr/sbin/kamailio[9688]: ERROR: <core> [forward.c:808]: do_forward_reply(): cannot forward reply

By manipulating the database I can skip the 5070 Kamailio, and then it works.

I captured these two 200 Ok packets to the 5069 kamailio

Failing:

No.     Time               Source                Destination           Protocol Length Info
   4713 21:54:12.814245    127.0.0.1             127.0.0.1             SIP/SDP  2297   Status: 200 OK |

Frame 4713: 2297 bytes on wire (18376 bits), 2297 bytes captured (18376 bits)
Linux cooked capture
Internet Protocol Version 4, Src: 127.0.0.1, Dst: 127.0.0.1
User Datagram Protocol, Src Port: 5070, Dst Port: 5069
Session Initiation Protocol (200)
    Status-Line: SIP/2.0 200 OK
    Message Header
        Via: SIP/2.0/UDP 127.0.0.1:5069;rport=5069;branch=z9hG4bK6ef1.0c009dcf5b4965c5d1a13d508e0b31c5.0
        Via: SIP/2.0/UDP 192.168.2.101:10120;received=192.168.2.101;rport=10120;branch=z9hG4bKPjIq.uY6jYbHkIqCo03bYLsTzccb7oy9jw
        Record-Route: <sip:127.0.0.8;line=sr-z-yMngm271wI73zx7gmx0CmHdDZWd-w*>
        Record-Route: <sip:127.0.0.8;line=sr-z-yMngm271wI73zx7gmx0Cq.7Cc-039Sz4Rxz5kezbQWOtUMn-9yTjcWODXoTC9BzK**>
        Record-Route: <sip:127.0.0.8;line=sr-z-yMngmS0-R4LCz2LtZ-Lg02L-JoLNQGn3057t0SntZ5LNL2QD7Vz12-sjkSTtMxTiB.7Cc-0399LtUqzgSGnCQx0gQ56gLG6g0wn5UILt2NziWIO3ooTDcHdDZ*>
        Record-Route: <sip:127.0.0.8;line=sr-z-yMngm271wI73zx7gmx0Nm.7Cc5039Sz4Rxz5kezbQWOtUMn-9yTjcWODXoTC9BzK**>
        Record-Route: <sip:127.0.0.8;line=sr-z-yMngm271wI7CJx0gZx73Q.7Cc50C9I0goedg9Bzgoedg94OiRbvEynTR7EFm0wFSOZQCOsOiGQs3EIzyUMTi7jnD7qzmWjn-UVT3SwTiJx7NLo0Q**>
        Record-Route: <sip:127.0.0.1:5071;r2=on;lr=on;ftag=YNdSUHC8KGHA7ZtlPh5rrTpdcW8sdpOW;did=8de.7651>
        Record-Route: <sip:127.0.0.1:5070;lr=on;ftag=YNdSUHC8KGHA7ZtlPh5rrTpdcW8sdpOW;did=8de.01b2>
        Record-Route: <sip:127.0.0.1:5069;r2=on;lr=on;ftag=YNdSUHC8KGHA7ZtlPh5rrTpdcW8sdpOW;vsf=AAAAAAABAAAAAAAAAAAAAAAIMDE-;did=8de.d821>
        Record-Route: <sip:192.168.2.9:5069;r2=on;lr=on;ftag=YNdSUHC8KGHA7ZtlPh5rrTpdcW8sdpOW;vsf=AAAAAAABAAAAAAAAAAAAAAAIMDE-;did=8de.d821>
        From: "Door" <sip:u1@192.168.2.101>;tag=YNdSUHC8KGHA7ZtlPh5rrTpdcW8sdpOW
        To: <sip:004540294149@scantron.viptel.dk:5070>;tag=1865008112
        Call-ID: ou8V0cLHn.P7Oca-pgsnMmrWO43kIQX8
        CSeq: 5778 INVITE
        Contact: <sip:127.0.0.8;line=sr-z-yMnrBS7CQM0gqS0CQ2Q3m27FwI73qx0CQo6gJSngJM7gcHODXPdb7Md5XSvjEqzc**>
        Allow: INVITE,ACK,PRACK,SUBSCRIBE,BYE,CANCEL,NOTIFY,INFO,REFER,UPDATE
        P-AS-Response: 40294149
        Content-Type: application/sdp
        Content-Length: 499
    Message Body

OK (Without 5070)

No.     Time               Source                Destination           Protocol Length Info
    373 21:44:42.955075    127.0.0.1             127.0.0.1             SIP/SDP  2199   Status: 200 OK |

Frame 373: 2199 bytes on wire (17592 bits), 2199 bytes captured (17592 bits)
Linux cooked capture
Internet Protocol Version 4, Src: 127.0.0.1, Dst: 127.0.0.1
User Datagram Protocol, Src Port: 5071, Dst Port: 5069
Session Initiation Protocol (200)
    Status-Line: SIP/2.0 200 OK
    Message Header
        Via: SIP/2.0/UDP 127.0.0.1:5069;rport=5069;branch=z9hG4bKeea.431611add9dee6ae89135983a85d3021.0
        Via: SIP/2.0/UDP 192.168.2.101:10120;received=192.168.2.101;rport=10120;branch=z9hG4bKPjXjzYAzDU-AJ9ug6mWhSQVI4gwRomuejk
        Record-Route: <sip:127.0.0.8;line=sr-z-yMngm271wI73zx7gmx0CmHdDZWd-w*>
        Record-Route: <sip:127.0.0.8;line=sr-z-yMngm271wI73zx7gmx0Cq.7Cc-039Sz4Rxz5kezbQWOtUMn-9yTjcWODXoTC9BzK**>
        Record-Route: <sip:127.0.0.8;line=sr-z-yMn4LSntRr0NzI7NQ574XqnC0M7gQ50NJNL4EgTCQ-7imIQD7Vz12-sjkSTtMxTiB.7Cc-0399LtUqzgSGnCQx0gQ56gLG6g0wn5UILt2NziWIO3ooTDcHdDZ*>
        Record-Route: <sip:127.0.0.8;line=sr-z-yMngm271wI73zx7gmx0Nm.7Cc5039Sz4Rxz5kezbQWOtUMn-9yTjcWODXoTC9BzK**>
        Record-Route: <sip:127.0.0.8;line=sr-z-yMngm271wI7CJx0gZx73Q.7Cc50C9I0goedg9Bzgoedg94OiRbvj7pJJTBsJyFttWTd-XVsSuS75k3EqOEsCOZF3k6YiyQn-UVT3oyLCQx73Z->
        Record-Route: <sip:127.0.0.1:5071;r2=on;lr=on;ftag=sJQFliIRYoYobikO47pCVGUi7HH0KxiP;did=ea4.426>
        Record-Route: <sip:127.0.0.1:5069;r2=on;lr=on;ftag=sJQFliIRYoYobikO47pCVGUi7HH0KxiP;vsf=AAAAAAABAAAAAAAAAAAAAAAIMDE-;did=ea4.7dd2>
        Record-Route: <sip:192.168.2.9:5069;r2=on;lr=on;ftag=sJQFliIRYoYobikO47pCVGUi7HH0KxiP;vsf=AAAAAAABAAAAAAAAAAAAAAAIMDE-;did=ea4.7dd2>
        From: "Door" <sip:u1@192.168.2.101>;tag=sJQFliIRYoYobikO47pCVGUi7HH0KxiP
        To: <sip:004540294149@scantron.viptel.dk:5070>;tag=1402236088
        Call-ID: 31a27HAVA7aFhLaX9uZkBxHu31OEZqOz
        CSeq: 9542 INVITE
        Contact: <sip:127.0.0.8;line=sr-z-yMnrBS7CQM0gqS0CQ2Q3m27FwI73qx0CQo6gJSngJM7gcHODXPdb7Md5XSvjEqzc**>
        Allow: INVITE,ACK,PRACK,SUBSCRIBE,BYE,CANCEL,NOTIFY,INFO,REFER,UPDATE
        P-AS-Response: 40294149
        Content-Type: application/sdp
        Content-Length: 500
    Message Body

Somehow it must be the contents in the 200 Ok package, but I really cant se any significant difference.

Anybody knows what that message is caused by?

-- 
-------------------- Med Liberalistiske Hilsner ----------------------
   Civilingeniør, Kjeld Flarup - Mit sind er mere åbent end min tegnebog
   Sofienlundvej 6B, 7560 Hjerm, Tlf: 40 29 41 49
   Den ikke akademiske hjemmeside for liberalismen - www.liberalismen.dk



_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - April 16-18, 2018, Berlin - www.asipto.com
Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com



_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - April 16-18, 2018, Berlin - www.asipto.com
Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com