sr-users January 2014

sr-users@lists.kamailio.org

93 participants
142 discussions

Kamailio World 2014 - First group of speakers
by Daniel-Constantin Mierla 21 Jan '14

21 Jan '14

Hello, I would like to announce that the details about first group of speakers to present at Kamailio World Conference are now published at: - http://conference.kamailio.com/k02/speakers/ There are several excellent proposals still under review, we expect to fill the schedule very soon, hurry up if you intend to submit one. So far we have a good mixture of topics with a consistent group of new speakers comparing with the past edition. A selection with the titles of the proposals is available at: - http://conference.kamailio.com/k02/schedule/ Many thanks to the sponsors that make the event happening: FhG Fokus, Asipto, Sipwise, Sipgate, ITCenter, NG Voice. If you plan to attend, consider registering as soon as possible to secure your seat - registration form is available at: - http://conference.kamailio.com/k02/registration/ Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

Non-authentication setup of Kamailio
by Carel Burger 20 Jan '14

20 Jan '14

Hi there, I have never used Kamailio before but want to investigate if if will work in my scenario before I invest time to learn it. I am the administrator of a small Wireless ISP. We do not provide SIP channels to our customers, we rather let them choose a service provider of their choice. Currently our customers are using two different providers. Since we are using ADSL with only one static IP we sometimes run into issues at the providers side with one way audio when our clients make a call to another client which is using the same service provider. I assume this is because of NAT. Since the RTP traffic actually leaves our network and then comes back to the other client the quality of the call is not as good as phoning a non client from the network. I want to know if it would be possible to setup Kamailio to keep the internal network calls traffic from leaving the network, and also allow free phone calls on our network. To do this we would require the authentication to take place on the service providers sip server and not on Kamailio. Kamailio would only do routing of the traffic and not worry about authentication. Would this be possible? Regards, Carel Burger

2 2

Development of a Mobile VOIP app connecting to Kamailio Server
by Neville D'Souza 20 Jan '14

20 Jan '14

Hi, I recently got a Kamailio v4.0.0 server up and running with Siremis v4.0.0 on a Debian Wheezy system with mysql as backend database . The Chat, file sharing ,audio and video services work flawlessly even behind nat and the same need to be incorporated in an app. I have configured rtpproxy and tls with self signed certificates. This is basically a test environment and we will install the same kamailio version with commercial certificates on a live hosted server. Server side everything is working. Problem is on the development side. Our company is venturing into VOIP apps for the first time and trying to look at how to go about it. Firstly we would like to start with an android app and then move on to Iphone, Windows, Blackberry and Symbian app. We need to know what is required on server side (any software to be installed or any configuration on kamailio or addition of modules) and client side ( which library and development environment to use) to make it work. Lastly in terms of security what things I need to take care of in the server and app. Best Regards, Neville D'Souza

2 3

kamailio crash after sqlops failures
by Uri Shacked 19 Jan '14

19 Jan '14

Daniel hi, I attached the following file: 1. "bt full" and "log" for each of the 3 servers. 2. The central MySQL slow queries log 3. The var/log/messages from one server. The servers crashed at different times but: 1. The MySQL server was very slow between 16:10:00 till 16:12:00 (approximately). 2. On each server, I am pretty sure, kamailio crashed while doing the data reload from modules like MTREE, HTABLE, DIALPLAN and CARRIERROUTE (all and all round 100,000 rows). Thanks again, Uri On Thu, Jan 16, 2014 at 2:17 AM, Daniel-Constantin Mierla <daniel(a)asipto.com > wrote: > Hello, > > the backtrace shows a crash in tm module, not sqlops. > > Can you tell which of the log files correspond to the instance that > produced the core file from where you took the back trace you attached? > > Can you give the backtraces from all cores? You say there were 3 crashes. > It is important to see if the backtrace is the same everywhere. > > Cheers, > Daniel >

2 2

Re: [SR-Users] S-CSCF configuration brings to seg fault
by Gennaro Sarnataro 17 Jan '14

17 Jan '14

Hi Carsten, I would like to try my scenarios using a kamailio nightly build but i wasn't able to checkout it. Can you indicate me where to find latest builds? 2014/1/15 Gennaro Sarnataro <gen.sarnataro(a)gmail.com> > hi Carsten, > thank for your responsivness!!! > i'm using 4.1 version installed from repository. > how do you fix it?? > > > 2014/1/15 Carsten Bock <carsten(a)ng-voice.com> > >> Salut Gennaro, >> >> what Version of Kamailio are you using? Did you install it from GIT or >> from what repository? >> Looks similar to a bug, i just fixed yesterday... >> I recommend to use at least a 4.1 nightly build. >> >> Thanks, >> Carsten >> >> 2014/1/15 Gennaro Sarnataro <gsarnataro(a)it.tiscali.com>: >> > hello everyone, >> > I'm using some kamailio configurations to perform I-CSCF and S-CSCF. >> > My configurations file let me register and unregister correctly. >> > When i try to perform an invite I've a memory leak as you can see from >> this >> > log: >> > >> >> Jan 15 11:07:50 localhost kamailio[2873]: INFO: <script>: route: >> received >> >> packet >> >> >> >> Jan 15 11:07:50 localhost kamailio[2873]: INFO: <script>: route: >> received >> >> register >> >> >> >> Jan 15 11:07:50 localhost kamailio[2873]: INFO: ims_auth >> >> [authorize.c:663]: authenticate(): uri=sip:ims.test.net >> >> nonce=173692b1aea9182c2ac712f915f0144a >> >> response=f1efa37094e4492af1e292043c3d57ea qop=auth nc=00000001 >> >> cnonce=a2f5a827ac94467a39e81584c11e8284 hbody= >> >> >> >> Jan 15 11:07:50 localhost kamailio[2873]: INFO: ims_auth >> >> [authorize.c:708]: authenticate(): UE said: >> f1efa37094e4492af1e292043c3d57ea >> >> and we expect f1efa37094e4492af1e292043c3d57ea ha1 >> >> 1c31125e2929b3fd6a609bd1a134a631 (REGISTER) >> >> >> >> Jan 15 11:07:50 localhost kamailio[2873]: INFO: ims_registrar_scscf >> >> [cxdx_sar.c:79]: create_return_code(): created AVP successfully : >> >> [saa_return_code] - [-2] >> >> >> >> Jan 15 11:07:50 localhost kamailio[2932]: INFO: ims_registrar_scscf >> >> [cxdx_avp.c:138]: cxdx_get_avp(): cxdx_get_experimental_result_code: >> Failed >> >> finding avp >> >> >> >> Jan 15 11:07:50 localhost kamailio[2932]: INFO: ims_registrar_scscf >> >> [cxdx_sar.c:79]: create_return_code(): created AVP successfully : >> >> [saa_return_code] - [1] >> >> >> >> Jan 15 11:07:50 localhost kamailio[2932]: WARNING: tm >> [t_lookup.c:1536]: >> >> t_unref(): WARNING: script writer didn't release transaction >> >> >> >> Jan 15 11:08:05 localhost kamailio[2940]: ERROR: <script>: INVITE >> >> (sip:+393922568123@ims.test.net (10.139.140.249:14437) to >> >> sip:+39666555@ims.test.net, >> >> >> 0gQAAC8WAAACBAAALxYAAM3V1YJ1oc5VxmgXA6gfuMM+33iKMHHLO4FAjeWDRORBfoRu5acqCjeTKNa2pjdRdA--(a)10.139.140.249 >> ) >> >> >> >> Jan 15 11:08:05 localhost kamailio[2940]: INFO: <script>: route: >> received >> >> packet >> >> >> >> Jan 15 11:08:05 localhost kamailio[2940]: INFO: <script>: route: Mobile >> >> Originating Side >> >> >> >> Jan 15 11:08:05 localhost kamailio[2940]: INFO: <script>: Routing >> Mobile >> >> Originating side >> >> >> >> Jan 15 11:08:05 localhost kamailio[2940]: INFO: <script>: Adding angle >> >> brackets to P-Asserted-Identity >> >> >> >> Jan 15 11:08:05 localhost kamailio[2940]: INFO: ims_isc [mod.c:236]: >> >> isc_match_filter(): Checking triggers >> >> >> >> Jan 15 11:08:05 localhost kamailio[2940]: : <core> >> [mem/q_malloc.c:454]: >> >> qm_free(): BUG: qm_free: bad pointer 0x7f3dc03597a0 (out of memory >> block!) >> >> called from <core>: parser/parse_param.c: do_free_params(629) - >> aborting >> >> >> >> Jan 15 11:08:05 localhost kamailio[2943]: : <core> [pass_fd.c:293]: >> >> receive_fd(): ERROR: receive_fd: EOF on 90 >> >> >> >> Jan 15 11:08:05 localhost kamailio[2863]: ALERT: <core> [main.c:775]: >> >> handle_sigs(): child process 2940 exited by a signal 6 >> >> >> >> Jan 15 11:08:05 localhost kamailio[2863]: ALERT: <core> [main.c:778]: >> >> handle_sigs(): core was generated >> >> >> >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: <core> [main.c:790]: >> >> handle_sigs(): INFO: terminating due to SIGCHLD >> >> >> >> Jan 15 11:08:05 localhost kamailio[2939]: INFO: <core> [main.c:841]: >> >> sig_usr(): INFO: signal 15 received >> >> >> >> Jan 15 11:08:05 localhost kamailio[2942]: INFO: <core> [main.c:841]: >> >> sig_usr(): INFO: signal 15 received >> >> >> >> >> >> ..... >> >> >> >> >> >> Jan 15 11:08:05 localhost kamailio[2942]: INFO: <core> [main.c:841]: >> >> sig_usr(): INFO: signal 15 received >> >> >> >> Jan 15 11:08:05 localhost kamailio[2876]: INFO: <core> [main.c:841]: >> >> sig_usr(): INFO: signal 15 received >> >> >> >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: cdp [mod.c:251]: >> >> cdp_exit(): CDiameterPeer child stopping ... >> >> >> >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: cdp >> [diameter_peer.c:428]: >> >> diameter_peer_destroy(): destroy_diameter_peer(): Terminating all >> >> children... >> >> >> >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: cdp >> [diameter_peer.c:435]: >> >> diameter_peer_destroy(): destroy_diameter_peer(): Waiting for child >> [2939] >> >> to terminate... >> >> >> >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: cdp >> [diameter_peer.c:435]: >> >> diameter_peer_destroy(): destroy_diameter_peer(): Waiting for child >> [2938] >> >> to terminate... >> >> >> >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: cdp >> [diameter_peer.c:435]: >> >> diameter_peer_destroy(): destroy_diameter_peer(): Waiting for child >> [2937] >> >> to terminate... >> >> >> >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: cdp >> [diameter_peer.c:435]: >> >> diameter_peer_destroy(): destroy_diameter_peer(): Waiting for child >> [2936] >> >> to terminate... >> >> >> >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: cdp >> [diameter_peer.c:435]: >> >> diameter_peer_destroy(): destroy_diameter_peer(): Waiting for child >> [2935] >> >> to terminate... >> >> >> >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: cdp >> [diameter_peer.c:435]: >> >> diameter_peer_destroy(): destroy_diameter_peer(): Waiting for child >> [2934] >> >> to terminate... >> >> >> >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: cdp >> [diameter_peer.c:435]: >> >> diameter_peer_destroy(): destroy_diameter_peer(): Waiting for child >> [2933] >> >> to terminate... >> >> >> >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: cdp >> [diameter_peer.c:435]: >> >> diameter_peer_destroy(): destroy_diameter_peer(): Waiting for child >> [2932] >> >> to terminate... >> >> >> >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: cdp >> [diameter_peer.c:447]: >> >> diameter_peer_destroy(): destroy_diameter_peer(): All processes >> terminated. >> >> Cleaning up. >> >> >> >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: cdp [worker.c:137]: >> >> worker_destroy(): Unlocking workers waiting on empty queue... >> >> >> >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: cdp [worker.c:140]: >> >> worker_destroy(): Unlocking workers waiting on full queue... >> >> >> >> Jan 15 11:08:05 localhost kamailio[2863]: CRITICAL: cdp >> >> [diameter_peer.c:487]: diameter_peer_destroy(): >> destroy_diameter_peer(): Bye >> >> Bye from C Diameter Peer test >> >> >> >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: cdp [mod.c:253]: >> >> cdp_exit(): ... CDiameterPeer child stoped >> > >> > >> > after that the S-CSCF terminate. >> > it's unuseful to attach any wireshark dump because,as I told before, the >> > Serving process terminates just after receiving the INVITE. >> > Instead I attach my configuration. >> > >> > thanks in advance!!! >> > >> > saluti >> > >> > Gennaro Sarnataro >> > >> > _______________________________________________ >> > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list >> > sr-users(a)lists.sip-router.org >> > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users >> > >> >> >> >> -- >> Carsten Bock >> CEO (Geschäftsführer) >> >> ng-voice GmbH >> Schomburgstr. 80 >> D-22767 Hamburg / Germany >> >> http://www.ng-voice.com >> mailto:carsten@ng-voice.com >> >> Office +49 40 34927219 >> Fax +49 40 34927220 >> >> Sitz der Gesellschaft: Hamburg >> Registergericht: Amtsgericht Hamburg, HRB 120189 >> Geschäftsführer: Carsten Bock >> Ust-ID: DE279344284 >> >> Hier finden Sie unsere handelsrechtlichen Pflichtangaben: >> http://www.ng-voice.com/imprint/ >> >> _______________________________________________ >> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list >> sr-users(a)lists.sip-router.org >> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users >> > > > > -- > Gennaro Sarnataro > -- Gennaro Sarnataro

2 1

Re: [SR-Users] S-CSCF configuration brings to seg fault
by Gennaro Sarnataro 17 Jan '14

17 Jan '14

hi Carsten, thank for your responsivness!!! how do you fix it?? i'm using 4.1 version installed from repository. I would like to try my scenarios using a kamailio nightly build but i wasn't able to checkout it. Can you indicate me where to find latest builds? 2014/1/15 Carsten Bock <carsten(a)ng-voice.com> > Salut Gennaro, > > what Version of Kamailio are you using? Did you install it from GIT or > from what repository? > Looks similar to a bug, i just fixed yesterday... > I recommend to use at least a 4.1 nightly build. > > Thanks, > Carsten > > 2014/1/15 Gennaro Sarnataro <gsarnataro(a)it.tiscali.com>: > > hello everyone, > > I'm using some kamailio configurations to perform I-CSCF and S-CSCF. > > My configurations file let me register and unregister correctly. > > When i try to perform an invite I've a memory leak as you can see from > this > > log: > > > >> Jan 15 11:07:50 localhost kamailio[2873]: INFO: <script>: route: > received > >> packet > >> > >> Jan 15 11:07:50 localhost kamailio[2873]: INFO: <script>: route: > received > >> register > >> > >> Jan 15 11:07:50 localhost kamailio[2873]: INFO: ims_auth > >> [authorize.c:663]: authenticate(): uri=sip:ims.test.net > >> nonce=173692b1aea9182c2ac712f915f0144a > >> response=f1efa37094e4492af1e292043c3d57ea qop=auth nc=00000001 > >> cnonce=a2f5a827ac94467a39e81584c11e8284 hbody= > >> > >> Jan 15 11:07:50 localhost kamailio[2873]: INFO: ims_auth > >> [authorize.c:708]: authenticate(): UE said: > f1efa37094e4492af1e292043c3d57ea > >> and we expect f1efa37094e4492af1e292043c3d57ea ha1 > >> 1c31125e2929b3fd6a609bd1a134a631 (REGISTER) > >> > >> Jan 15 11:07:50 localhost kamailio[2873]: INFO: ims_registrar_scscf > >> [cxdx_sar.c:79]: create_return_code(): created AVP successfully : > >> [saa_return_code] - [-2] > >> > >> Jan 15 11:07:50 localhost kamailio[2932]: INFO: ims_registrar_scscf > >> [cxdx_avp.c:138]: cxdx_get_avp(): cxdx_get_experimental_result_code: > Failed > >> finding avp > >> > >> Jan 15 11:07:50 localhost kamailio[2932]: INFO: ims_registrar_scscf > >> [cxdx_sar.c:79]: create_return_code(): created AVP successfully : > >> [saa_return_code] - [1] > >> > >> Jan 15 11:07:50 localhost kamailio[2932]: WARNING: tm [t_lookup.c:1536]: > >> t_unref(): WARNING: script writer didn't release transaction > >> > >> Jan 15 11:08:05 localhost kamailio[2940]: ERROR: <script>: INVITE > >> (sip:+393922568123@ims.test.net (10.139.140.249:14437) to > >> sip:+39666555@ims.test.net, > >> > 0gQAAC8WAAACBAAALxYAAM3V1YJ1oc5VxmgXA6gfuMM+33iKMHHLO4FAjeWDRORBfoRu5acqCjeTKNa2pjdRdA--(a)10.139.140.249 > ) > >> > >> Jan 15 11:08:05 localhost kamailio[2940]: INFO: <script>: route: > received > >> packet > >> > >> Jan 15 11:08:05 localhost kamailio[2940]: INFO: <script>: route: Mobile > >> Originating Side > >> > >> Jan 15 11:08:05 localhost kamailio[2940]: INFO: <script>: Routing Mobile > >> Originating side > >> > >> Jan 15 11:08:05 localhost kamailio[2940]: INFO: <script>: Adding angle > >> brackets to P-Asserted-Identity > >> > >> Jan 15 11:08:05 localhost kamailio[2940]: INFO: ims_isc [mod.c:236]: > >> isc_match_filter(): Checking triggers > >> > >> Jan 15 11:08:05 localhost kamailio[2940]: : <core> [mem/q_malloc.c:454]: > >> qm_free(): BUG: qm_free: bad pointer 0x7f3dc03597a0 (out of memory > block!) > >> called from <core>: parser/parse_param.c: do_free_params(629) - aborting > >> > >> Jan 15 11:08:05 localhost kamailio[2943]: : <core> [pass_fd.c:293]: > >> receive_fd(): ERROR: receive_fd: EOF on 90 > >> > >> Jan 15 11:08:05 localhost kamailio[2863]: ALERT: <core> [main.c:775]: > >> handle_sigs(): child process 2940 exited by a signal 6 > >> > >> Jan 15 11:08:05 localhost kamailio[2863]: ALERT: <core> [main.c:778]: > >> handle_sigs(): core was generated > >> > >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: <core> [main.c:790]: > >> handle_sigs(): INFO: terminating due to SIGCHLD > >> > >> Jan 15 11:08:05 localhost kamailio[2939]: INFO: <core> [main.c:841]: > >> sig_usr(): INFO: signal 15 received > >> > >> Jan 15 11:08:05 localhost kamailio[2942]: INFO: <core> [main.c:841]: > >> sig_usr(): INFO: signal 15 received > >> > >> > >> ..... > >> > >> > >> Jan 15 11:08:05 localhost kamailio[2942]: INFO: <core> [main.c:841]: > >> sig_usr(): INFO: signal 15 received > >> > >> Jan 15 11:08:05 localhost kamailio[2876]: INFO: <core> [main.c:841]: > >> sig_usr(): INFO: signal 15 received > >> > >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: cdp [mod.c:251]: > >> cdp_exit(): CDiameterPeer child stopping ... > >> > >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: cdp > [diameter_peer.c:428]: > >> diameter_peer_destroy(): destroy_diameter_peer(): Terminating all > >> children... > >> > >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: cdp > [diameter_peer.c:435]: > >> diameter_peer_destroy(): destroy_diameter_peer(): Waiting for child > [2939] > >> to terminate... > >> > >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: cdp > [diameter_peer.c:435]: > >> diameter_peer_destroy(): destroy_diameter_peer(): Waiting for child > [2938] > >> to terminate... > >> > >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: cdp > [diameter_peer.c:435]: > >> diameter_peer_destroy(): destroy_diameter_peer(): Waiting for child > [2937] > >> to terminate... > >> > >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: cdp > [diameter_peer.c:435]: > >> diameter_peer_destroy(): destroy_diameter_peer(): Waiting for child > [2936] > >> to terminate... > >> > >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: cdp > [diameter_peer.c:435]: > >> diameter_peer_destroy(): destroy_diameter_peer(): Waiting for child > [2935] > >> to terminate... > >> > >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: cdp > [diameter_peer.c:435]: > >> diameter_peer_destroy(): destroy_diameter_peer(): Waiting for child > [2934] > >> to terminate... > >> > >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: cdp > [diameter_peer.c:435]: > >> diameter_peer_destroy(): destroy_diameter_peer(): Waiting for child > [2933] > >> to terminate... > >> > >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: cdp > [diameter_peer.c:435]: > >> diameter_peer_destroy(): destroy_diameter_peer(): Waiting for child > [2932] > >> to terminate... > >> > >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: cdp > [diameter_peer.c:447]: > >> diameter_peer_destroy(): destroy_diameter_peer(): All processes > terminated. > >> Cleaning up. > >> > >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: cdp [worker.c:137]: > >> worker_destroy(): Unlocking workers waiting on empty queue... > >> > >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: cdp [worker.c:140]: > >> worker_destroy(): Unlocking workers waiting on full queue... > >> > >> Jan 15 11:08:05 localhost kamailio[2863]: CRITICAL: cdp > >> [diameter_peer.c:487]: diameter_peer_destroy(): > destroy_diameter_peer(): Bye > >> Bye from C Diameter Peer test > >> > >> Jan 15 11:08:05 localhost kamailio[2863]: INFO: cdp [mod.c:253]: > >> cdp_exit(): ... CDiameterPeer child stoped > > > > > > after that the S-CSCF terminate. > > it's unuseful to attach any wireshark dump because,as I told before, the > > Serving process terminates just after receiving the INVITE. > > Instead I attach my configuration. > > > > thanks in advance!!! > > > > saluti > > > > Gennaro Sarnataro > > > > _______________________________________________ > > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > > sr-users(a)lists.sip-router.org > > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > > > > > > -- > Carsten Bock > CEO (Geschäftsführer) > > ng-voice GmbH > Schomburgstr. 80 > D-22767 Hamburg / Germany > > http://www.ng-voice.com > mailto:carsten@ng-voice.com > > Office +49 40 34927219 > Fax +49 40 34927220 > > Sitz der Gesellschaft: Hamburg > Registergericht: Amtsgericht Hamburg, HRB 120189 > Geschäftsführer: Carsten Bock > Ust-ID: DE279344284 > > Hier finden Sie unsere handelsrechtlichen Pflichtangaben: > http://www.ng-voice.com/imprint/ > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users(a)lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users >

1 0

kamailio-4.0.2 core issue
by Surendra 17 Jan '14

17 Jan '14

Hi, We are facing a core issue in 4.0.2 version. Please find the GDB trace below #0 udp_rcv_loop () at udp_server.c:471 471 fromlen=sockaddru_len(bind_address->su); (gdb) bt #0 udp_rcv_loop () at udp_server.c:471 #1 0x0000000000475c14 in main_loop () at main.c:1851 #2 0x000000000047a98b in main (argc=<value optimized out>, argv=<value optimized out>) at main.c:2939 We have simulated this so many times in load mode. Machine details: Linux PLT-RA-RD-W167A.localdomain 2.6.18-308.el5 #1 SMP Fri Jan 27 17:17:51 EST 2012 x86_64 x86_64 x86_64 GNU/Linux Can anyone help me on this Regards Surendra

1 0

kamailio-4.1.1 avp issue within failure routes
by José Seabra 17 Jan '14

17 Jan '14

Hi there, I upgraded my kamailio server from version 4.0.1 to 4.1.1, then i noticed that all my "AVP's variavels" that are initialized on initial "INVITE", are all set as null when call goes to failure route, so kamailio is not keeping the variavel values for same call(dialog) When it happens i see the following warning "WARNING: tm [t_lookup.c:1536]: t_unref(): WARNING: script writer didn't release transaction" Thanks for your help -- Regards José Seabra

3 11

Memory Leaks with Kamailio using SEAS module
by ziad habchi 17 Jan '14

17 Jan '14

Dear Support, I am having an "out of memory" problem while using kamailio with SEAS module. After using Kamailio with the SEAS module for few hours with a high load , I am getting "out of memory" error that I believe is caused from a memory leak. I would like your help interpreting this error. The output of kamailio -v is : version: kamailio 4.0.4 (i386/linux) cabe58 flags: STATS: Off, USE_IPV6, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 4MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: cabe58 compiled on 14:23:27 Dec 2 2013 with gcc 4.1.2 kamctl ps : Process:: ID=0 PID=31191 Type=attendant Process:: ID=1 PID=31192 Type=udp receiver child=0 sock=193.100.200.18:5070 Process:: ID=2 PID=31193 Type=udp receiver child=1 sock=193.100.200.18:5070 Process:: ID=3 PID=31194 Type=udp receiver child=2 sock=193.100.200.18:5070 Process:: ID=4 PID=31195 Type=udp receiver child=3 sock=193.100.200.18:5070 Process:: ID=5 PID=31196 Type=slow timer Process:: ID=6 PID=31197 Type=timer Process:: ID=7 PID=31198 Type=ctl handler Process:: ID=8 PID=31199 Type=MI FIFO Process:: ID=9 PID=31200 Type=SEAS Process:: ID=10 PID=31201 Type=tcp receiver (generic) child=0 Process:: ID=11 PID=31202 Type=tcp receiver (generic) child=1 Process:: ID=12 PID=31203 Type=tcp receiver (generic) child=2 Process:: ID=13 PID=31204 Type=tcp receiver (generic) child=3 Process:: ID=14 PID=31205 Type=tcp main process kamcmd pkg.stats: { entry: 0 pid: 31191 rank: 0 used: 72480 free: 4091840 real_used: 102448 } { entry: 1 pid: 31192 rank: 1 used: 80624 free: 4083696 real_used: 110592 } { entry: 2 pid: 31193 rank: 2 used: 80624 free: 4083696 real_used: 110592 } { entry: 3 pid: 31194 rank: 3 used: 80624 free: 4083696 real_used: 110592 } { entry: 4 pid: 31195 rank: 4 used: 80624 free: 4083696 real_used: 110592 } { entry: 5 pid: 31196 rank: -1 used: 2276560 free: 4083744 real_used: 17770256 } { entry: 6 pid: 31197 rank: -1 used: 1787296 free: 4083744 real_used: 17280992 } { entry: 7 pid: 31198 rank: -2 used: 77760 free: 4086544 real_used: 107744 } { entry: 8 pid: 0 rank: 0 used: 89920 free: 4074352 real_used: 119936 } { entry: 9 pid: 0 rank: 0 used: 0 free: 0 real_used: 0 } { entry: 10 pid: 31201 rank: 5 used: 140240 free: 4023728 real_used: 170560 } { entry: 11 pid: 31202 rank: 6 used: 140240 free: 4023712 real_used: 170576 } { entry: 12 pid: 31203 rank: 7 used: 140240 free: 4023856 real_used: 170432 } { entry: 13 pid: 31204 rank: 8 used: 140240 free: 4023712 real_used: 170576 } { entry: 14 pid: 31205 rank: -4 used: 3877344 free: 4030176 real_used: 19269056 } As you can see above , the output of the SEAS module is not showing (pid 31200) Moreover , I can see that the real_used value in the kamcmd core.shmmem keep on increasing , and free decrease until I finally get an error "out of memory" When my SEAS client exit the output of kamcmd core.shmmem : { total: 33554432 free: 16273440 used: 1787296 real_used: 17280992 max_used: 33553520 fragments: 8098 } The traffic is a simple SIP MESSAGE from a seagull simulator, with a 200OK reply from my SEAS client. I appreciate your support, Thank you in advance, Ziad Habchi

3 10

Help required
by Gerhard De Villiers-Mohr 17 Jan '14

17 Jan '14

Good day Can you please forward me a manual of some sort or assist with setting up the kamailio serimis 4.0 to accept registration of IP PBX systems or soft phones. I am very new to this and need a step by step instructions. Also I will be getting a sip trunk to use for testing purposes before we go live and need help with setting this up and routing calls from users to the sip trunk for outbound calls. Please assist me , this is very new to me. If you prefer to do a remote login session I will gladly provide you with the teamviewer session details. Sincerely. Description: Description: Description: gerhard mohr email signature

1 0

← Newer
1
...
6
7
8
9
10
11
12
...
15
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users January 2014