Hello list,
Hope you are all doing well!
I am trying to figure out a way to retrieve the local socket the t_relay()
has decided to use in a mhomed=1 env. Is there a way to do that? I couldn't
find any variable other than the $snd ones that maybe have this info, but I
am not using onsend_route anyw
Hello,
I added to the config file:
tcp_no_connect=yes
And with that param, the same test results in a different behavior, but
still not working:
"message":" DEBUG: {1 12583750 BYE RVXZVMHKop}
[core\/msg_translator.c:161]: check_via_address(): (198.1.54.228,
198.1.54.228, 0)"}
"message":" ERROR
Bumping this thread up!
I did some more tests trying to narrow down the problem and this is what I
found...:
On the INVITE, I add the TCP connection information I want to save (for
later reuse). Snippets:
...(found this in the misc/examples/pkg/sip-router-oob.cfg, but I haven't
noticed any chang
Hello,
adding few notes ...
Like Alex said in another response, the get_out_socket() error is when
Kamailio doesn't find a IP routing path between its listen socket and
target address (sip:192.168.86.110:5061).
Then, to your initial message: t_relay() does not create/track dialogs,
only SIP tran
Hi Michael,
First, the "no corresponding socket" issue is the result of a
determination by Kamailio that it has no outgoing listener (the
combination of transport protocol, IP address and port) interface that
can reach the destination network of the next hop.
The way that Kamailio makes this dete
Hi Michael,
the mostly used model AFAIK is dispatcher cos you can define groups (also
with only one member). That's more flexible if you scale up the backend
services.
Also an docker newbie the macvlan driver gives you native ip access within
the container.
The socket error message shows up an
I’ve switched from a Dockerized Kamailio instance to a native installation.
Here is my most recent trace when trying to forward traffic:
0(70677) INFO:
hi
thank you so much for this information
my issue is resolved
On Wed, Nov 20, 2019 at 3:51 PM Markus Bönke wrote:
> … and it’s now an xavp, to log contents you can use something like:
>
> xlog("L_INFO","Socket: {$xavp(AVP_SOCK)}\n");
> xlog("L_INFO","Destination: {$xavp(AVP_DST)=>sock}\n");
> x
Hi Igor,
I would then more test dmq and dmq_usrloc modules. Therefore you can hold
the register state on multiple Kamailio at the same time.
https://kamailio.org/docs/modules/devel/modules/dmq_usrloc.html
Cheers
Karsten
Igor Olhovskiy schrieb am Di., 19. Nov. 2019,
15:34:
> Actually same as d
… and it’s now an xavp, to log contents you can use something like:
xlog("L_INFO","Socket: {$xavp(AVP_SOCK)}\n");
xlog("L_INFO","Destination: {$xavp(AVP_DST)=>sock}\n");
xlog("L_INFO","Number of destinations: {$avp(AVP_CNT)}\n");
xlog("L_INFO","All destinations: {$(avp(AVP_DST)[*])}\n"
If you are using version 5.2+ you need to put the name of the avp, not $avp...
like
...
modparam("dispatcher", "xavp_dst", "AVP_DST")
modparam("dispatcher", "xavp_dst_mode", 0)
modparam("dispatcher", "xavp_ctx", "AVP_CTX")
…
Best regards,
Markus
> Am 20.11.2019 um 11:04 schrieb Karsten Horsma
hi Johansson
thank you for reply
i got this in logs kamailio-c
...
0(26418) ERROR: [core/modparam.c:140]: set_mod_param_regex():
parameter of type <1> not found in module
0(26418) CRITICAL: [core/cfg.y:3510]: yyerror_at(): parse error in
config file /etc/ka
Hi Gaurav,
check your config file Syntax with kamailio -DD -c -f
/etc/kamailio/kamailio.cfg
That should show you what's wrong.
And your Kamailio version is needed for help.
The dispatcher avps changed during some 5.x versions. Take a look at the
dispatcher module documentation for your specific
> On 20 Nov 2019, at 10:55, Gaurav Bmotra wrote:
>
> ERROR: bad config file (4 errors)
Check the syslog for details on these four errors or start kamailio in the
foreground with "kamailio -c” to see them.
/O___
Kamailio (SER) - Users Mailing List
s
hi
i want to use dispatcher Module and following is the config..
---
loadmodule "dispatcher.so"
--
modparam("dispatcher", "db_url", "mysql://kamailio:kamailiorw@localhost
/kamailio")
modparam("dispatcher", "table_name", "dispatcher")
modparam("dispat
15 matches
Mail list logo
