[SR-Users] no corresponding socket found error

[David Escartín via sr-users]

Hello all

we are seeing these kind of logs in a Debian GNU/Linux 11 using kamailio
5.5.6

Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155702]:
ERROR:  [core/forward.c:183]: get_out_socket(): no corresponding
socket found for(udp:164.152.22.248:5060)
Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155698]:
ERROR:  [core/forward.c:183]: get_out_socket(): no corresponding
socket found for(udp:208.74.138.184:5060)
Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155695]:
ERROR:  [core/forward.c:183]: get_out_socket(): no corresponding
socket found for(udp:208.74.138.181:5060)
Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155693]:
ERROR:  [core/forward.c:183]: get_out_socket(): no corresponding
socket found for(udp:38.102.250.60:5060)
Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155707]:
ERROR:  [core/forward.c:183]: get_out_socket(): no corresponding
socket found for(udp:87.1.1.27:5060)
Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155707]:
ERROR: tm [ut.h:302]: uri2dst2(): no corresponding socket for "87.1.1.27"
af 2
Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155707]:
ERROR: tm [t_fwd.c:470]: prepare_new_uac(): can't fwd to af 2, proto 1  (no
corresponding listening socket)
Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155697]:
ERROR:  [core/forward.c:183]: get_out_socket(): no corresponding
socket found for(udp:208.74.138.184:5060)
Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155694]:
ERROR:  [core/forward.c:183]: get_out_socket(): no corresponding
socket found for(udp:192.40.216.97:5060)
Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155694]:
ERROR:  [core/forward.c:183]: get_out_socket(): no corresponding
socket found for(udp:208.74.138.180:5060)
Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155714]:
ERROR:  [core/forward.c:183]: get_out_socket(): no corresponding
socket found for(udp:87.1.1.27:5060)

The kamailio instance we are using is receiving around 1500 calls per
second in average when we do start seeing these errors more frequently
In this instance we are using multihomed
the listen address list is

children=14
socket_workers=1
listen=udp:192.168.99.70:5081
listen=udp:192.168.99.81:5060
listen=udp:87.1.1.27:5060
listen=tcp:192.168.96.105:8095
listen=tcp:87.1.1.27:5060
tcp_children=6
port=5060

We use the first worker only to perform the OPTIONS requests from the
dispatcher module.
The sockets
listen=udp:192.168.99.81:5060
listen=udp:87.1.1.27:5060
are used to communicate both A and B legs

so when a message is received at 192.168.99.81:5060 we send it to
87.1.1.27:5060 and viceversa
We were using $fs variable before doing the t_relay() function.
This way is working, but when load increases, seems sometimes kamailio
doesn't get the proper socket to forward the reply.
I think the errors mainly are related to responses which are being
forwarded, like if the function get_sock_info_list was not able to retrieve
the listen interfaces

we have tried to set in the onreply routes the commands
set_recv_socket("udp:192.168.99.81:5060");
set_send_socket("udp:87.1.1.27:5060"); (when reply goes from private to
public domain)

and it seems it reduces the number of
Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155702]:
ERROR:  [core/forward.c:183]: get_out_socket(): no corresponding
socket found for(udp:164.152.22.248:5060)
Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155698]:
ERROR:  [core/forward.c:183]: get_out_socket(): no corresponding
socket found for(udp:208.74.138.184:5060)
Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155695]:
ERROR:  [core/forward.c:183]: get_out_socket(): no corresponding
socket found for(udp:208.74.138.181:5060)
Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155693]:
ERROR:  [core/forward.c:183]: get_out_socket(): no corresponding
socket found for(udp:38.102.250.60:5060)
errors

But i honestly don't know why the
Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155707]:
ERROR: tm [ut.h:302]: uri2dst2(): no corresponding socket for "87.1.1.27"
af 2
Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155707]:
ERROR: tm [t_fwd.c:470]: prepare_new_uac(): can't fwd to af 2, proto 1  (no
corresponding listening socket)
appear

We aldso tried to increase the kernel buffers rmem and wmem from 208KB (as
we had by default) to 4MB

Do you know a reason which could cause these logs to appear?
Any setup that could mitigate them?

thanks a lot and regards
david escartin
-- 

David Escartín
NOC engineer
www.sonoc.io
[image: LinkedIn] 
[image: Twitter] 
[image: Instagram] 
This e-mail is for the exclusive use of its recipients and may contain
business secrets or other confidential or privileged 

[SR-Users] "no corresponding socket found" logs

[David Escartín via sr-users]

Hello all

we are seeing these kind of logs in a Debian GNU/Linux 11 using kamailio
5.5.6

Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155702]:
ERROR:  [core/forward.c:183]: get_out_socket(): no corresponding
socket found for(udp:164.152.22.248:5060)
Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155698]:
ERROR:  [core/forward.c:183]: get_out_socket(): no corresponding
socket found for(udp:208.74.138.184:5060)
Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155695]:
ERROR:  [core/forward.c:183]: get_out_socket(): no corresponding
socket found for(udp:208.74.138.181:5060)
Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155693]:
ERROR:  [core/forward.c:183]: get_out_socket(): no corresponding
socket found for(udp:38.102.250.60:5060)
Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155707]:
ERROR:  [core/forward.c:183]: get_out_socket(): no corresponding
socket found for(udp:87.1.1.27:5060)
Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155707]:
ERROR: tm [ut.h:302]: uri2dst2(): no corresponding socket for "87.1.1.27"
af 2
Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155707]:
ERROR: tm [t_fwd.c:470]: prepare_new_uac(): can't fwd to af 2, proto 1  (no
corresponding listening socket)
Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155697]:
ERROR:  [core/forward.c:183]: get_out_socket(): no corresponding
socket found for(udp:208.74.138.184:5060)
Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155694]:
ERROR:  [core/forward.c:183]: get_out_socket(): no corresponding
socket found for(udp:192.40.216.97:5060)
Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155694]:
ERROR:  [core/forward.c:183]: get_out_socket(): no corresponding
socket found for(udp:208.74.138.180:5060)
Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155714]:
ERROR:  [core/forward.c:183]: get_out_socket(): no corresponding
socket found for(udp:87.1.1.27:5060)

The kamailio instance we are using is receiving around 1500 calls per
second in average when we do start seeing these errors more frequently
In this instance we are using multihomed
the listen address list is

children=14
socket_workers=1
listen=udp:192.168.99.70:5081
listen=udp:192.168.99.81:5060
listen=udp:87.1.1.27:5060
listen=tcp:192.168.96.105:8095
listen=tcp:87.1.1.27:5060
tcp_children=6
port=5060

We use the first worker only to perform the OPTIONS requests from the
dispatcher module.
The sockets
listen=udp:192.168.99.81:5060
listen=udp:87.1.1.27:5060
are used to communicate both A and B legs

so when a message is received at 192.168.99.81:5060 we send it to
87.1.1.27:5060 and viceversa
We were using $fs variable before doing the t_relay() function.
This way is working, but when load increases, seems sometimes kamailio
doesn't get the proper socket to forward the reply.
I think the errors mainly are related to responses which are being
forwarded, like if the function get_sock_info_list was not able to retrieve
the listen interfaces

we have tried to set in the onreply routes the commands
set_recv_socket("udp:192.168.99.81:5060");
set_send_socket("udp:87.1.1.27:5060"); (when reply goes from private to
public domain)

and it seems it reduces the number of
Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155702]:
ERROR:  [core/forward.c:183]: get_out_socket(): no corresponding
socket found for(udp:164.152.22.248:5060)
Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155698]:
ERROR:  [core/forward.c:183]: get_out_socket(): no corresponding
socket found for(udp:208.74.138.184:5060)
Sep 21 17:41:13 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155695]:
ERROR:  [core/forward.c:183]: get_out_socket(): no corresponding
socket found for(udp:208.74.138.181:5060)
Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155693]:
ERROR:  [core/forward.c:183]: get_out_socket(): no corresponding
socket found for(udp:38.102.250.60:5060)
errors

But i honestly don't know why the
Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155707]:
ERROR: tm [ut.h:302]: uri2dst2(): no corresponding socket for "87.1.1.27"
af 2
Sep 21 17:41:14 lax-dedge-1 /usr/local/kamailio/sbin/kamailio[3155707]:
ERROR: tm [t_fwd.c:470]: prepare_new_uac(): can't fwd to af 2, proto 1  (no
corresponding listening socket)
appear

We aldso tried to increase the kernel buffers rmem and wmem from 208KB (as
we had by default) to 4MB

Do you know a reason which could cause these logs to appear?
Any setup that could mitigate them?

thanks a lot and regards
david escartin


-- 

David Escartín
NOC engineer
www.sonoc.io
[image: LinkedIn] 
[image: Twitter] 
[image: Instagram] 
This e-mail is for the exclusive use of its recipients and may contain
business secrets or other confidential or privileged 

Re: [SR-Users] no corresponding socket found for

[Kjeld Flarup]

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=127.0.0.1:5069 
listen=LOCALIP:5069


Kjeld

2018-04-10 9:43 GMT+02:00 Daniel-Constantin Mierla >:


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: 
[forward.c:181]: get_out_socket(): no socket found
Apr  9 21:54:10 kfcpbx /usr/sbin/kamailio[9688]: ERROR: 
[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: 
[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:

    Record-Route:


    Record-Route:


    Record-Route:


    Record-Route:


    Record-Route:


    Record-Route:


    Record-Route:


    Record-Route:


    From: "Door" 
;tag=YNdSUHC8KGHA7ZtlPh5rrTpdcW8sdpOW
    To: 
;tag=1865008112
    Call-ID: ou8V0cLHn.P7Oca-pgsnMmrWO43kIQX8
    CSeq: 5778 INVITE
    Contact:


    Allow:
INVITE,ACK,PRACK,SUBSCRIBE,BYE,CANCEL,NOTIFY,INFO,REFER,UPDATE
    

Re: [SR-Users] no corresponding socket found for

[Daniel-Constantin Mierla]

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=127.0.0.1:5069  
> listen=LOCALIP:5069
>
>
> Kjeld
>
> 2018-04-10 9:43 GMT+02:00 Daniel-Constantin Mierla  >:
>
> 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: 
>> [forward.c:181]: get_out_socket(): no socket found
>> Apr  9 21:54:10 kfcpbx /usr/sbin/kamailio[9688]: ERROR: 
>> [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: 
>> [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:
>> 
>>     Record-Route:
>> 
>> 
>>     Record-Route:
>> 
>> 
>>     Record-Route:
>> 
>> 
>>     Record-Route:
>> 
>> 
>>     Record-Route:
>> 
>> 
>>     Record-Route:
>> 
>> 
>>     Record-Route:
>> 
>> 
>>     Record-Route:
>> 
>> 
>>     From: "Door" 
>> ;tag=YNdSUHC8KGHA7ZtlPh5rrTpdcW8sdpOW
>>     To: 
>> ;tag=1865008112
>>     Call-ID: ou8V0cLHn.P7Oca-pgsnMmrWO43kIQX8
>>     CSeq: 5778 INVITE
>>     Contact:
>> 
>> 
>>     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 

Re: [SR-Users] no corresponding socket found for

[Kjeld Flarup]

Listening is configured like this:

#!define LOCALIP 192.168.2.9
#!subst "/LOCALIP/192.168.2.9/g"
listen=127.0.0.1:5069
listen=LOCALIP:5069


Kjeld

2018-04-10 9:43 GMT+02:00 Daniel-Constantin Mierla :

> 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: 
> [forward.c:181]: get_out_socket(): no socket found
> Apr  9 21:54:10 kfcpbx /usr/sbin/kamailio[9688]: ERROR: 
> [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: 
> [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   SourceDestination
> Protocol Length Info
>4713 21:54:12.814245127.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:  yMngm271wI73zx7gmx0CmHdDZWd-w*>
> Record-Route:  039Sz4Rxz5kezbQWOtUMn-9yTjcWODXoTC9BzK**>
> Record-Route:  JoLNQGn3057t0SntZ5LNL2QD7Vz12-sjkSTtMxTiB.7Cc-
> 0399LtUqzgSGnCQx0gQ56gLG6g0wn5UILt2NziWIO3ooTDcHdDZ*>
> Record-Route:  7Cc5039Sz4Rxz5kezbQWOtUMn-9yTjcWODXoTC9BzK**>
> Record-Route:  7Cc50C9I0goedg9Bzgoedg94OiRbvEynTR7EFm0wFSOZQCOsOiGQs3EIzyUMTi7jnD7qzmWjn-
> UVT3SwTiJx7NLo0Q**>
> Record-Route:  YNdSUHC8KGHA7ZtlPh5rrTpdcW8sdpOW;did=8de.7651>
> Record-Route:  YNdSUHC8KGHA7ZtlPh5rrTpdcW8sdpOW;did=8de.01b2>
> Record-Route:  YNdSUHC8KGHA7ZtlPh5rrTpdcW8sdpOW;vsf=AAABAAAIMDE-;
> did=8de.d821>
> Record-Route:  YNdSUHC8KGHA7ZtlPh5rrTpdcW8sdpOW;vsf=AAABAAAIMDE-;
> did=8de.d821>
> From: "Door"  ;tag=
> YNdSUHC8KGHA7ZtlPh5rrTpdcW8sdpOW
> To: 
> ;tag=1865008112
> Call-ID: ou8V0cLHn.P7Oca-pgsnMmrWO43kIQX8
> CSeq: 5778 INVITE
> Contact:  0CQo6gJSngJM7gcHODXPdb7Md5XSvjEqzc**>
> 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   SourceDestination
> Protocol Length Info
> 373 21:44:42.955075127.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:  yMngm271wI73zx7gmx0CmHdDZWd-w*>
> Record-Route:  039Sz4Rxz5kezbQWOtUMn-9yTjcWODXoTC9BzK**>
> Record-Route:  yMn4LSntRr0NzI7NQ574XqnC0M7gQ50NJNL4EgTCQ-7imIQD7Vz12-sjkSTtMxTiB.7Cc-
> 0399LtUqzgSGnCQx0gQ56gLG6g0wn5UILt2NziWIO3ooTDcHdDZ*>
> Record-Route:  7Cc5039Sz4Rxz5kezbQWOtUMn-9yTjcWODXoTC9BzK**>
> 

Re: [SR-Users] no corresponding socket found for

[Daniel-Constantin Mierla]

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: 
> [forward.c:181]: get_out_socket(): no socket found
> Apr  9 21:54:10 kfcpbx /usr/sbin/kamailio[9688]: ERROR: 
> [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: 
> [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:
> 
>     Record-Route:
> 
>     Record-Route:
> 
>     Record-Route:
> 
>     Record-Route:
> 
>     Record-Route:
> 
>     Record-Route:
> 
>     Record-Route:
> 
>     Record-Route:
> 
>     From: "Door"
> ;tag=YNdSUHC8KGHA7ZtlPh5rrTpdcW8sdpOW
>     To: ;tag=1865008112
>     Call-ID: ou8V0cLHn.P7Oca-pgsnMmrWO43kIQX8
>     CSeq: 5778 INVITE
>     Contact:
> 
>     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:
> 
>     Record-Route:
> 
>     Record-Route:
> 
>     Record-Route:
> 
>     Record-Route:
> 
>     Record-Route:
> 
>     Record-Route:
> 

[SR-Users] no corresponding socket found for

[Kjeld Flarup]

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:  
[forward.c:181]: get_out_socket(): no socket found
Apr  9 21:54:10 kfcpbx /usr/sbin/kamailio[9688]: ERROR:  
[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:  
[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: 

    Record-Route: 

    Record-Route: 

    Record-Route: 

    Record-Route: 

    Record-Route: 

    Record-Route: 

    Record-Route: 

    Record-Route: 

    From: "Door" 
;tag=YNdSUHC8KGHA7ZtlPh5rrTpdcW8sdpOW

    To: ;tag=1865008112
    Call-ID: ou8V0cLHn.P7Oca-pgsnMmrWO43kIQX8
    CSeq: 5778 INVITE
    Contact: 

    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: 

    Record-Route: 

    Record-Route: 

    Record-Route: 

    Record-Route: 

    Record-Route: 

    Record-Route: 

    Record-Route: 

    From: "Door" 
;tag=sJQFliIRYoYobikO47pCVGUi7HH0KxiP

    To: