Hi ALL
I need to configure dispatcher call to the server asterisk i have a 21
server and i need to dispatcher call to all the server
AGENT----> kamailio --->asterisk1
---> asteisk2
---> -
---> -
---> -
---> asterisk21
please i need your help
THANK YOU
hello ,
im using kamailio and rtpengine.
i use rtpengine with rtp timeout as follows
rtpengine --timeout=240 --silent-timeout=600 -b2b-url=http://kamailioip:5060/RPC --xmlrpc-format=2
and in kamailio
modparam("jsonrpcs", "pretty_format", 1)
modparam("jsonrpcs", "transport", 7)
event_route[xhttp:request] {
if ($hu =~ "^/RPC") {
jsonrpc_dispatch();
xhttp_reply("200", "OK", "text/xml", "<methodResponse><params><param><value><string>OK</string></value></param></params></methodResponse>");
exit;
}
}
rtpengine successfully reaches the rpc endpoint but i have an error on the jsonrpcs module
43(50) ERROR: jsonrpcs [jsonrpcs_mod.c:1275]: ki_jsonrpcs_dispatch(): invalid json doc [[<?xml version="1.0" encoding="UTF-8"?>
<methodCall>
<methodName>dlg.terminate_dlg</methodName>
<params>
<param><value><string>1-10(a)172.22.244.139</string></value></param>
<param><value><string>10SIPpTag091</string></value></param>
<param><value><string>8U173ymKpc1pp</string></value></param>
</params>
</methodCall>
]]
and so the dialog module can not ends the call
Kamailio 5.5.2 on debian bullseye
rtpengine 10.0.1.8 on debian bullseye
Thanks.
hello,
do we have something like xavp in htable or a module that implements having multiple values in stack like xavp but not tied to transaction.
i want data be seen by all processes but with the functionnality of xavp.
Thanks.
Hello,
The Asterisk conference (Astricon 2021) happened last week, I had a session
about extending Asterisk with the LRKProxy module in Kamailio in terms of
RTP sessions.
cheers,
--
--Mojtaba Esfandiari.S
Hi All,
Is there an equivalent to corex's send_tcp (https://kamailio.org/docs/modules/5.2.x/modules/corex.html#corex.f.send_tcp <https://kamailio.org/docs/modules/5.2.x/modules/corex.html#corex.f.send_tcp>) for TLS?
I have a bit of an odd edge case where I can't add Via headers etc, and send_udp and send_tcp allow me to achieve what I want, but it doesn't seem to have a means of doing the same with TLS?
Essentially I want to transparently proxy what is received by Kamailio on one interface to a TLS connection e.g.
A = (TCP) => Kamailio = (TLS) => Remote Host
(A) in this instance is already setting a Via header of the Kamailio's external IP and transport tis. I appreciate this is a non-standard way of doing it, but (A) is a black box that I can't change, what I'm essentially trying to do is have Kamailio handle the TLS but essentially (A) thinks it's at the edge.
I can make it work with send_tcp for a standard TCP connection, but if I use t_relay or even forward() to send onwards by TLS then Kamailio obviously adds its own headers as you'd expect.
Ross
Hello!
In our architecture, Kamailio uses 2 local Redis servers to get routing
information.
We noticed that if at the start of Kamailio the first in the modparam list
is a running Redis server (name=real), and the second in the list is not
running (name=fake), then Kamailio will not even try to connect to the
running one.
# ----- redis server params -----
modparam("ndb_redis", "init_without_redis", 1)
modparam("ndb_redis", "server", "name=real;addr=127.0.0.1;port=6379;db=1")
modparam("ndb_redis", "server", "name=fake;addr=127.0.0.1;port=6479;db=2")
But if the servers in the list above are reversed, then everything will
work as it should.
Looks the initialization order affects behavior.
Syslog output:
Nov 11 18:00:45 kamailio /usr/sbin/kamailio[11445]: ERROR: ndb_redis
[redis_client.c:224]: redisc_init(): Failed to create REDIS returned an
error: Connection refused
Nov 11 18:00:45 kamailio /usr/sbin/kamailio[11445]: ERROR: ndb_redis
[redis_client.c:259]: redisc_init(): error communicating with redis server
[fake] (127.0.0.1:6479/2): Connection refused
Nov 11 18:00:45 kamailio /usr/sbin/kamailio[11445]: WARNING: ndb_redis
[redis_client.c:264]: redisc_init(): failed to initialize redis
connections, but initializing module anyway.
There is no established connection to the real server after Kamailio starts
both through redis-cli and through ss.
[root@kamailio ~]# ss -anp | grep 6379
tcp LISTEN 0 128 127.0.0.1:6379 *:*
users:(("redis-server",pid=10376,fd=6))
[root@kamailio ~]# kamailio -v
version: kamailio 5.6.0-dev2 (x86_64/linux) 378a2d
compiled on 04:12:43 Nov 11 2021 with gcc 4.8.5
[root@kamailio ~]# cat /etc/redhat-release
CentOS Linux release 7.9.2009 (Core)
g
--
BR,
Denys Pozniak
Hi All,
Try as I may I cannot force an outbound TCP request to use a non-ephemeral source port.
Looking at the documentation it seems that as long as I have a line like
listen=tcp:10.30.0.55:3339
I should be able to force an outbound connection to originate from that host and port, i.e. to establish a persistent connection from a specific socket to a remote host, but having tried to set it via $fs and set_send_socket() it always uses an ephemeral port.
Ideally I would like kamailio to use a specific source port for contacting a specific remote host and keep the TCP socket established, and it seems like it should be simple enough to do but it's not working as expected.
Best,
Ross
Hopefully the collective hive mind can help with this one, as I have little experience of using TCP in this manner and neither does a friendly Kamailio expert I know personally.
I'm replacing a closed box thing that accepts connections from various nodes over TCP. They send INVITEs and REGISTERs over that TCP socket and expect to receive inbound calls over the same established TCP socket.
Struggling to make Kamailio behave the same way, but it should be possible.
The first time it receives a message, I add the sender to the dispatcher as follows;
jsonrpc_exec('{"jsonrpc": "2.0", "method": "dispatcher.add", "params": [5, "sip:$si:$sp;transport=tcp", 0, "socket=tcp:127.0.0.1:5776"], "id": 1}');
This works great, but despite setting the socket to use there, when a call later comes in and it's routed to one of the dispatcher nodes that's been added in this way it fails because Kamailio attempts to open a new connection to the IP / PORT rather than having kept the socket open from the earlier message and reusing the same connection/.
Any ideas? I get the feeling I'm missing something obvious!
Ross
Yup, this is works!
Thanks!
Not reflected in docs, though...
ср, 10 нояб. 2021 г. в 16:13, Fred Posner <fred(a)palner.com>:
>
> On 11/10/21 11:10 AM, Igor Olhovskiy wrote:
> > Hello,
> > I'm getting issues with *htable.get* rpc command
> > Running
> > kamctl rpc htable.get client_to_re 65825
>
> What happens when you try:
>
> s:65825 vs 65825
>
>
>
> Fred Posner | palner.com
> Matrix: @fred:matrix.lod.com
> o: +1 (212) 937-7844
>
--
Best regards,
Igor
