From michael@kapsulate.com Wed Nov 20 13:55:16 2019
From: Michael Iedema <michael@kapsulate.com>
To: sr-users@lists.kamailio.org
Subject: Re: [SR-Users] Beginner Help: Relay vs Forward
Date: Wed, 20 Nov 2019 13:55:12 +0100
Message-ID: <FB86B00E-0991-471E-8969-4132B2F16307@kapsulate.com>
In-Reply-To: <A3F58424-740A-4E92-A15C-B5BD7A161221@kapsulate.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0017802943=="

--===============0017802943==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

I=E2=80=99ve switched from a Dockerized Kamailio instance to a native install=
ation. Here is my most recent trace when trying to forward traffic:

 0(70677) INFO: <script>: ORIGINATOR -> REGISTER: Destination URI is now sip:=
192.168.86.110:5061
 0(70677) ERROR: *** cfgtrace:request_route=3D[DEFAULT_ROUTE] c=3D[/etc/kamai=
lio/kamailio-proxy.cfg] l=3D155 a=3D24 n=3Dt_relay
 0(70677) ERROR: <core> [core/forward.c:181]: get_out_socket(): no socket fou=
nd
 0(70677) ERROR: <core> [core/forward.c:183]: get_out_socket(): no correspond=
ing socket found for(udp:192.168.86.110:5061)
 0(70677) ERROR: tm [./ut.h:318]: uri2dst2(): no corresponding socket found f=
or "192.168.86.110" af 2 (udp:192.168.86.110:5061)
 0(70677) ERROR: tm [t_fwd.c:467]: prepare_new_uac(): can't fwd to af 2, prot=
o 1  (no corresponding listening socket)
 0(70677) ERROR: tm [t_fwd.c:1724]: t_forward_nonack(): failure to add branch=
es
 0(70677) ERROR: *** cfgtrace:request_route=3D[DEFAULT_ROUTE] c=3D[/etc/kamai=
lio/kamailio-proxy.cfg] l=3D156 a=3D2 n=3Dexit


My Kamailio instance is running on 192.168.86.107:6060. The originating servi=
ce is on 192.168.86.110:5060. The REGISTER service is on 192.168.86.110:5061.

The refactor in my architecture I=E2=80=99m trying to make is:
 - previously: Originator Service -> Register Service
 - now: Originator -> Kamailio -> Register Service

I=E2=80=99m trying to get traffic from 192.168.86.110:5060 to route to 192.16=
8.86.110:5061 but keep seeing this =E2=80=9Cno socket found=E2=80=9D error. I=
 didn=E2=80=99t think I was trying to bind that address, just rewriting the $=
du to point to the different host and port...


 # ORIGINATOR sent us something
 if ( $(ct{nameaddr.uri}{uri.port}) =3D=3D PORT_ORIGINATOR ) {

   xlog("L_INFO", "ORIGINATOR: sent $rm\n=E2=80=9D);

   if (is_method("REGISTER")) {
     $du =3D "sip: HOST_REGISTER:PORT_REGISTER";
     xlog("L_INFO", "ORIGINATOR -> REGISTER: Destination URI is now $du\n");
     t_relay();
     exit;
   }
  ...
 }

## END SNIPPET ##



Apologies if I=E2=80=99m missing something obvious! Thanks as always for your=
 time.

-Michael



> On Nov 19, 2019, at 10:24, Michael Iedema <michael(a)kapsulate.com> wrote:
>=20
> Hi all,
>=20
> I am trying to place Kamailio between several SIP services which are differ=
entiated by port and by the type of message they handle. To be concrete, here=
 are the services:
>=20
> Originator:
> - reachable on port 5060
> - originates all traffic to the services
>=20
> Service A:
> - reachable on port 5061
> - handles REGISTER
>=20
> Service B:
> - reachable on port 5062
> - handles INVITE
>=20
> Service C:
> - reachable on port 5063
> - handles MESSAGE
>=20
> The services, originator and Kamailio instance may all be run on the same I=
P or may be split onto different addresses. Previously, the originator needed=
 to know the address and port of each service. Now I want to make Kamailio re=
sponsible for that task so it can be done more intelligently.
>=20
> To start though I simply want to get traffic flowing between the services a=
nd this is where I=E2=80=99m struggling to climb the learning curve. In my te=
st setup the originator and all services are on the same IP with only Kamaili=
o running on a different IP.
>=20
> Address 1            Address 2
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Originator  <-->  Kamailio:6060
>                               |
>                               |
> Service A  <-------> |
> Service B  <-------> |
> Service C  <-------> |
>=20
>=20
> My first attempt at the logic looks like this:
>=20
> # HOST DEFINITIONS
> #!substdef "/HOST_ORIGINATOR/192.168.86.110/"
> #!substdef "/HOST_REGISTER/192.168.86.110/=E2=80=9C
> #!substdef "/HOST_INVITE/192.168.86.110/"
> #!substdef "/HOST_MESSAGE/192.168.86.110/"
>=20
> # PORT DEFINITIONS
> #!substdef =E2=80=9C/PORT_ORIGINATOR/5060/"
> #!substdef "/PORT_REGISTER/5061/=E2=80=9C
> #!substdef "/PORT_INVITE/5062/"
> #!substdef "/PORT_MESSAGE/5063/"
>=20
> # ROUTE LOGIC
> route {
>=20
>  # ORIGINATOR sent us something
>  if ( $(ct{nameaddr.uri}{uri.port}) =3D=3D HOST_ORIGINATOR ) {
>=20
>    xlog("L_INFO", "ORIGINATOR: sent $rm\n=E2=80=9D);
>=20
>    if (is_method("REGISTER")) {
>      $du =3D "sip: HOST_REGISTER:PORT_REGISTER";
>      xlog("L_INFO", "ORIGINATOR -> REGISTER: Destination URI is now $du\n");
>      t_relay();
>      exit;
>    }
>  }
> =E2=80=A6
>=20
> #### END SNIPPET ####
>=20
>=20
> My very newbie questions are:
> - Am I even on the right track here? I understand that t_relay() establishe=
s a stateful dialog handler between the originator and register services.
> - Can I accomplish this bi-directional path statelessly with forward()?
> - Do I need to add logic to handle the messages from the REGISTER service b=
ack to ORIGINATOR?
>=20
> This config currently fails because of "no corresponding socket found=E2=80=
=9D when the relay triggers. I believe this is because I=E2=80=99m running th=
e Kamailio instance in a Docker container so my first step today is to set up=
 a native install.
>=20
> I also looked at the dispatcher module which seems very close to what I wan=
t to do. Maybe that=E2=80=99s a more natural way to go?
>=20
>=20
>=20
> Anyway, apologies for the lengthy explanation. I hope it is at least clear =
what I intend to do. I will gladly research and do trial and error to solve t=
his but need to know I=E2=80=99m going down roughly the right path. I=E2=80=
=99m not sure what I should even be googling even of the time :-)
>=20
>=20
> Thanks as always for your time and the great software!
>=20
> Regards,
> -Michael
>=20
>=20
>=20



--===============0017802943==--