I am currently using multiple instances of Kamailio with a common database
and using the usrloc module with db_mode=4 and server_id to filter the
contacts that get loaded at startup on each server.
The problem I seem to have is that using the RPC call ul.add, I cannot see
any parameter to send to specify the server_id. The server_id that the
contact is given is 0. If I manually go into the db and modify the
server_id everything works as expected. I think I must be missing something
somewhere as I'm sure you shouldn't need to do this.
Can anyone help please.
Thanks
Daz
Hello list,
Hope you all doing fine!
I am using version 5.0.7 and I was trying to use the set_advertised_address
with an avp variable but it does not replace with the avp value....
I then find out this thread
https://lists.kamailio.org/pipermail/sr-users/2016-March/092327.html, in
which is mentioned:
*"I expect those functions not to support pvs, but I think this issomething
to address in 5.0 and get all core functions working with pvs."*
Looks like this was actually not done.... is that correct? Is there any
plan to do it?
In my case I want to use the set_advertised_address after reading the value
from DB, so I can't use the advertised_address or listen options.... Any
idea on how I could achieve that?
Thank you,
Kind regards,
Patrick Wakano
Hello,
I have kamailio and rtpproxy running on the same server located behind a
router with NAT just like below.
UA(internet)---public ip---router(NAT)--Kamailio+RTPproxy(private
ip)--UA(private network)
There are several issues like one way audio.
I need users on the internet to communicate with each other, users on the
private network to communicate with each other, and users on the internet
and the private network to communicate with each other.
What is the best approach?
Best regards,
Clarence
Hello,
as it was discussed during our last IRC devel meeting before the summer,
the time to release a new major version should be this autumn.
With the Kamailio Developers Meeting planned for September 27-28, 2018,
I think it is better to freeze the code couple of days after that event.
So I propose the following milestones:
* on Thursday, October 4, 2018 - last development day, code for 5.2.0
will be frozen at the end of the day
* 4 to 6 weeks of testing
* release sometime in November, to be decided more precisely after the
first weeks of testing, some rough candidates being within the weeks of
Nov 5 or Nov 19
If anyone has something to add or adjust, let's discuss on sr-users
mailing list.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference -- www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com
Hello,
a matter of the schedule to be agreed in the morning and the
availability during the Kamailio Developers Meeting, we may do a new
stable release from branch 5.1.6 on Thursday, Sep 27, 2018, in the
afternoon. Given that several of us will be in the same room, the
special goal would be to try to automate the process as much as possible.
If the time doesn't allow it, then the release will be done next week, a
specific day to be decided by the end of this week.
Anyhow, this is the informal notification to report as soon as possible
any issues you are aware of and not yet in bug tracker, so they get a
chance to be fixed.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference -- www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com
Hi guys!
We have four a scripts that sends dlg.list command to kamailio through
xmlrpc. They are not executed simultaneously. Sometimes, we are getting
the following errors:
fm_search_defrag(): fm_search_defrag(0x7f212c25a000, 5273984); Free
fragment not found!2017-05-26T13:54:20.438736-03:00 drwsip02
/usr/local/sbin/kamailio[19833]: ERROR: <core> [mem/f_malloc.c:498]:
fm_malloc(): fm_malloc(0x7f212c25a000, 5273984) called from core:
tcp_main.c: tcpconn_new(957), module: core; Free fragment not
found!2017-05-26T13:54:20.439101-03:00 drwsip02
/usr/local/sbin/kamailio[19833]: ERROR: <core> [tcp_main.c:959]:
tcpconn_new(): mem. allocation failure2017-05-26T13:54:20.439344-03:00
drwsip02 /usr/local/sbin/kamailio[19833]: ERROR: <core> [tcp_main.c:3985]:
handle_new_connect(): tcpconn_new failed, closing socket
I all ready increased this two variables:
tcp_conn_wq_max=30000000
tcp_rd_buf_size=5273226
How can I see how much memory xmlrpc is using?
Any advice will be appreciated.
Thanks in advance!
Diego
Hi!
I am working successfully with Kamailio in my lab setup where Kamailio is
the SBC for Asterisk.
The network layout is looking like this:
SIP-Phone <== PUBLIC NET ==> Kamailio (SBC) <== PRIVATE NET ==> Asterisk
<== PUBLIC NET ==> Carrier
Each public network is reachable from the internet and has a local firewall
with IP whitelists.
The internal SIP transactions are UDP-only but for external phones I would
like to also listen for TCP/TLS.
For this layout to work with rtpproxy (before we move on to RTPengine), we
have to enable mhomed in Kamailio.
We also have some routing issues with packets leaving with the wrong IP via
rtpproxy (when call between carrier and external phone needs to be bridged).
Most examples show that Asterisk is deployed on the same network as the
external interface of Kamailio (-> Asterisk exposed to the public network).
In our tests, this works much better but I have great security concerns
because this Asterisk instance itself does not need to be reachable from
external.
How do other users deploy Kamailio in front of Asterisk or similar as SBC
to secure internals?
There is lot of docs for Kamailio's config but IMHO less for the setup as
DMZ (SBC) proxy.
Thank you very much.
Kind regards
Kevin
Hi all. I'm having problems with an indialog ACK request which is not being
routed correctly.
I call loose_route and print:
$du=sip:MYIP:2443;transport=ws;r2=on;lr=on;did=1d1.7702;nat=ws
$route_uri=sip:MYIP;r2=on;lr=on;did=1d1.7702;nat=ws
But when I call
check_route_param("nat=ws") I get false result.
version: kamailio 5.1.4
any hints?
cheers,
Jon
--
https://pekepbx.comhttps://www.issabel.com/multitenant
