I'm trying to setup a simple proxy with NAT/RTPproxy. I have started with the basic cfg file and added nat and forced rtpproxy.
The proxy is to reside in between endpoints and multiple SIP servers. Currently calls from endpoints are working great but my issue is calls from the server to the endpoint. The SIP messages are good until the 200 OK sent from the phone back, Kamailio is not fixing the contact so it's sending the private IP of the phone back to the server so all subsequent traffic is attempting to route to the private IP. I have tried using the fix_nated_contact everywhere I could think but still no difference.
Attached is sip capture and the kamailio.cfg i'm currently using.
Thank you,
Brian
Hi,
Can anyone give a quick answer regarding RtpEngine and support for iLBC
codec?
I have followed the instructions how to build and enable codecs according
to the GitHub manual. But iLBC codec is missing when performing "rtpengine
--codecs".
I have tried to google around for iLBC references, but the only thing that
I have found so far is libilbc, which is a lib for ffmpeg, and it looks
like ffmpeg needs to be recompiled.
What is the correct/fastest way forward for getting iLBC support on
RtpEngine on debian 9?
The purpose it to test a-law to iLBC transcoding.
Best Regards,
Lars
Greetings,
I found an odd behaviour in Kamailio and i would like to know if it's
intentional.
I've made this snippet for showing :
$var(teste) = $null;
if($var(teste) == "Test")
{
xerr("TEST : If returned true");
}
The "if" returns true if the $var is $null or 0.
I'm using the "cmp_str()" now in order to avoid this issue.
Best Regards,
Duarte Rocha
Hi,
I am using this command for starting RTPengine -
/usr/sbin/rtpengine --table=0 --interface=192.168.1.x\!182.75.xx.yy
--listen-ng=127.0.0.1:22222 --pidfile=/var/run/rtpengine.pid --log-level=6
--log-facility=local1
in kamailio.cfg --> listen=MY_SIP_ADDR advertise 182.75.xx.yy:5060
But still there is no RTP from outside network.
Still not able to sort out what is the issue.If pfsense is blocking rtp
packets or any other.
but i have very config on pfsense.
Thanks & Regards,
Arish Haque
Hello,
No, both server have the same script, the only difference is that they are connected to different DB.
We increase the max TLS connections because we plan to move some customer on this proxy and we want to be ready to accept more than 2K TLS connection .
Laurent
-----Message d'origine-----
De : Henning Westerholt <hw(a)kamailio.org>
Envoyé : mercredi, 24 octobre 2018 22:46
À : sr-users(a)lists.kamailio.org
Cc : Laurent Schweizer <laurent.schweizer(a)peoplefone.com>
Objet : [JUNK-SPAM] Re: [SR-Users] : hight shared memory usage
Am Mittwoch, 24. Oktober 2018, 15:24:05 CEST schrieb Laurent Schweizer:
> I have 2 proxy running and we have a very big difference of memory
> usage between them, moreover we have more connected users on the proxy
> with less memory usage.
>
> We have this issue on the first proxy, today we have to increase the
> shared memory as it was no more possible to setup new TCP connection.
>
> We use the same version of the proxy, script is quite the same, one
> difference, on the proxy with the issue we increase the number of max
> TLS connection to 20K
>
> Any idea ?
> is TLS consuming more memory than TCP or UDP ?
Hello Laurent,
TLS is using more memory than TCP and than UDP, due to the higher workload and overhead for crypto/connection tracking.
But looking to your registered user count this should not make a big difference in the end.
Do you have maybe a different usage pattern on the first proxy comparing to the second one? So that different parts of the cfg or the code are executed?
Why do you increased the number of max TLS connections on the first proxy, you had also some issues here?
> First proxy (with high memory usage):
>
>
> [cycle #: 3; if constant make sure server lives] Kamailio Runtime
> Details:
> kamailio 5.0.6 (x86_64/linux)
> now: Wed Oct 24 15:18:55 2018
> up_since: Wed Oct 24 13:21:12 2018
> uptime: 7063
>
> Transaction Statistics:
> tmx:UAS_transactions = 56240 tmx:active_transactions = 4
> tmx:UAC_transactions = 0 tmx:inuse_transactions = 18
>
> Stateless Server Statistics:
> sl:sent_replies = 134317 sl:sent_err_replies = 0
>
> UsrLoc Statistics:
> usrloc:location_ch-contacts = 1463 usrloc:location_ch-users = 1181
> usrloc:location_ch-expires = 1076 usrloc:registered_users = 1181
>
> Core Statistics:
> core:rcv_requests = 214220 core:rcv_replies = 179145
> core:fwd_requests = 5495 core:fwd_replies = 73
>
> Shared Memory Statistics:
> shmem:fragments = 529 shmem:real_used_size =
> 15862690496 shmem:free_size = 36566109504 shmem:total_size =
> 52428800000 shmem:max_used_size = 16198927224 shmem:used_size =
> 15854961104
>
>
>
> cat /proc/net/netstat | cut -d" " -f12-17 ; cat /proc/net/sockstat TW
> TWRecycled TWKilled PAWSPassive PAWSActive PAWSEstab
> 339118 0 684 3195 0 4648
> InBcastOctets OutBcastOctets InCsumErrors InNoECTPkts InECT1Pkts
> InECT0Pkts
> 14620680 0 0 19142166496 9683 133135
> sockets: used 1951
> TCP: inuse 1029 orphan 0 tw 2 alloc 1036 mem 15
> UDP: inuse 540 mem 446
> UDPLITE: inuse 0
> RAW: inuse 0
> FRAG: inuse 0 memory 0
>
>
>
> -------------------------------------------
>
>
> Second proxy (memory is OK) :
>
> [cycle #: 2; if constant make sure server lives] Kamailio Runtime
> Details:
> kamailio 5.0.6 (x86_64/linux)
> now: Wed Oct 24 15:19:39 2018
> up_since: Mon Jul 2 00:31:48 2018
> uptime: 9902871
>
> Transaction Statistics:
> tmx:UAS_transactions = 86712048 tmx:active_transactions = 92
> tmx:UAC_transactions = 0 tmx:inuse_transactions = 178
>
> Stateless Server Statistics:
> sl:sent_replies = 641635175 sl:sent_err_replies = 0
>
> UsrLoc Statistics:
> usrloc:location-contacts = 3971 usrloc:location-users = 3845
> usrloc:location-expires = 286685 usrloc:registered_users = 3845
>
> Core Statistics:
> core:rcv_requests = 752644955 core:rcv_replies = 1181197213
> core:fwd_requests = 14482059 core:fwd_replies = 206909
>
> Shared Memory Statistics:
> shmem:fragments = 28437 shmem:real_used_size = 56447456
> shmem:free_size = 2091036192 shmem:total_size = 2147483648
> shmem:max_used_size = 82099768 shmem:used_size = 43354160
>
>
> cat /proc/net/netstat | cut -d" " -f12-17 ; cat /proc/net/sockstat TW
> TWRecycled TWKilled PAWSPassive PAWSActive PAWSEstab
> 273625 0 0 0 0 3524
> InBcastOctets OutBcastOctets InCsumErrors InNoECTPkts InECT1Pkts
> InECT0Pkts
> 2010 0 1 179031265416 81564 21432766
> sockets: used 4964
> TCP: inuse 576 orphan 0 tw 3 alloc 681 mem 105
> UDP: inuse 3908 mem 3117
> UDPLITE: inuse 0
> RAW: inuse 0
> FRAG: inuse 0 memory 0
Best regards,
Henning
--
Henning Westerholt - https://skalatan.de/blog/ Kamailio security assessment - https://skalatan.de/de/assessment
Hi List!
I currently have 3 Kamailio's (Version 5.1) in an ACTIVE-ACTIVE-ACTIVE
scenario behind a load balancer all 3 nodes are listening and advertising
the same virtual ip of the load balancer. Im using dmq module together with
dialogue module to sync the state of the dialog to all 3 nodes. Is there a
way or module that i can use to also sync every transaction?
Problem that im facing right now is that an INVITE will come to Kamailio1
and the 100 TRYING or 183 RINGING or 200OK will go to Kamailio2 and since
Kamailio1 hasn't received a response will retransmit the INVITE. Or is
there a way with dmq to also update the other nodes for responses like 100
,183 or 200 OK so that Kamailio1 knows not to retransmit?
Maybe im going down the wrong path? :)
Any assistance would be greatly appreciated
My config for dmq and dialog:
#=====================DIALOG====================================
modparam("dialog", "enable_dmq", 1)
#=====================DMQ=======================================
modparam("dmq", "server_address", "sip:x.x.x.x:5080")
modparam("dmq", "notification_address", "sip:y.y.y.y:5080")
modparam("dmq", "multi_notify", 1)
modparam("dmq", "num_workers", 4)
modparam("dmq", "ping_interval", 30)
request_route {
# MANAGE ALL DIALOGS
dlg_manage();
if(is_method("KDMQ"))
{
dmq_handle_message();
}
Thanks!
Phillip
I got two tablets registering with the same username, this used to work
but now I got a bug report that only one of them gets a call.
I found out that the problem is in the ruid column as they both end up
with this ruid value uloc-1-5bd0abe9-83c-e4
How is that ruid value calculated, and how can I change this?
--
-------------------- 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
---------- Mensaje reenviado ---------
De: Diego Nadares <dnadares(a)gmail.com>
Fecha: El vie, 5 oct. 2018 a las 15:46
Asunto: Re: [SR-Users] tcp Free fragment not found
Para: Daniel-Constantin Mierla <miconda(a)gmail.com>
Hi Daniel,
Sorry for the delay.
-M 32 -m 128
Should I increase any/both of these params?
Thanks again!
Diego
El jue., 4 oct. 2018 a las 3:31, Daniel-Constantin Mierla (<
miconda(a)gmail.com>) escribió:
> Hello,
>
> what are the values for -m and -M command line parameters?
>
> Cheers,
> Daniel
>
> On 03.10.18 16:37, Diego Nadares wrote:
>
> Hi guys! I hope you are doing well.
>
> Any hint on this? I changed to json but sometimes i get the same error.
>
> 2018-10-03T10:12:11.066539-03:00 drwsip11 /usr/local/sbin/kamailio[28173]:
> ERROR: <core> [mem/f_malloc.c:415]: fm_search_defrag(): fm_search_defrag(0
> x7f575c4ad000, 5352056); Free fragment not found!
> 2018-10-03T10:12:11.067552-03:00 drwsip11 /usr/local/sbin/kamailio[28173]:
> ERROR: <core> [mem/f_malloc.c:498]: fm_malloc(): fm_malloc(0x7f575c4ad000,
> 5352056) called from core: tcp_main.c: _wbufq_add(636), module: core;
> Free fragment not found!
> 2018-10-03T10:12:11.068128-03:00 drwsip11 /usr/local/sbin/kamailio[28182]:
> ERROR: <core> [tcp_main.c:3496]: handle_ser_child(): received CON_ERROR for
> 0x7f575f6a6918 (id 12638), refcnt 3, flags 0x4018
> 2018-10-03T10:12:11.068397-03:00 drwsip11 /usr/local/sbin/kamailio[28173]:
> ERROR: sl [../../forward.h:220]: msg_send_buffer(): tcp_send failed
> 2018-10-03T10:12:11.068929-03:00 drwsip11 /usr/local/sbin/kamailio[28173]:
> ERROR: xmlrpc [xmlrpc.c:795]: send_reply(): Error while sending reply
> 2018-10-03T10:12:11.092080-03:00 drwsip11 /usr/local/sbin/kamailio[28173]:
> WARNING: <core> [tcp_read.c:1666]: handle_io(): F_TCPCONN connection marked
> as bad: 0x7f575f6a6918 id 12638 refcnt 1
>
> Is there any stat to see? Or any additional configuration to make?
>
> Here is my tcp related config
>
> tcp_connection_lifetime=3605
> tcp_conn_wq_max=30000000
> tcp_rd_buf_size=5273226
>
> We are running kamilio 4.4.5
>
> Thanks in advance!
>
> Diego
>
>
>
>
> El vie., 26 may. 2017 a las 16:12, Diego Nadares (<dnadares(a)gmail.com>)
> escribió:
>
>> 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
>>
>>
>
> _______________________________________________
> Kamailio (SER) - Users Mailing Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
>
> --
> 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 all,
I noticed double Session Description Protocol Version (v) 0 data in the SDP section when using rtpengine with Kamailio. Has any else noticed this? Is there a way for Kamailio to remove one of them?
Thank you,
-Steve
