- sr-users - kamailio.org

Difference between HTTP clients (utils.so vs http_client.so)
by Joel Serrano | VOZELIA 12 Jan '17

12 Jan '17

Hi all, Currently I see there are 2 http clients: utils.so --> http_query() http_client.so --> http_client_query() Any advice on which to use? Any pros/cons of using one over the other? Thanks, Joel. Este mensaje y, en su caso, los ficheros anexos son confidenciales, especialmente en lo que respecta a los datos personales, y se dirigen exclusivamente al destinatario referenciado.Les informamos que los datos contenidos en el presente mail, han sido facilitados por usted o recogidos de Fuentes Accesibles al Público. Dicha información personal, será incluida en un fichero bajo la responsabilidad de VOZELIA TELECOM S.L.Todos los ficheros que trata nuestra empresa se encuentran debidamente inscritos ante la Agencia Española de Protección de Datos.Vd. Como propio interesado podrá ejercitar sus derechos de Acceso, Cancelación, Rectificación u Oposición, en el mail: administracion(a)vozelia.com o en la dirección Avenida de Manoteras 8 escalera 3 2ºB, 28050 Madrid.Tal y como establece la Ley Orgánica de Protección de Datos 15/1999 de 13 de Diciembre.Para ejercer sus derechos desde Panama podrá hacerlo en la dirección Vía Argentina, Edificio Mediteranean Loft. Panama.En caso de no ser el destinatario y haya recibido este mensaje por error, agradeceremos que nos lo comunique inmediatamente al remitente sin difundir, almacenar o copiar su contenido.La divulgación o el suministro, en todo o en parte, a cualquier tercero, no podrá ser realizada sin el previo, expreso y escrito consentimiento de VOZELIA TELECOM S.L. .

3 4

RPC exact command to change voicemail IP or Port
by Annus Fictus 12 Jan '17

12 Jan '17

Hello list, I can't find the exact RPC command to change IP or port of voicemail server (module CFG_RPC): the default Kamailio configuration is: */#!ifdef WITH_VOICEMAIL/**/ /**/# VoiceMail Routing on offline, busy or no answer/**/ /**/#/**/ /**/# - by default Voicemail server IP is empty to avoid misrouting/**/ /**/voicemail.srv_ip = "" desc "VoiceMail IP Address"/**/ /**/voicemail.srv_port = "5060" desc "VoiceMail Port"/**/ /**/#!endif/* Thank you Regards

2 8

how to immediately close a tls connection
by Andy 12 Jan '17

12 Jan '17

Hi, trying to close a tls connection immediately, have ref to the connection (tcpconn) pointer please suggest, thanks! -- View this message in context: http://sip-router.1086192.n5.nabble.com/how-to-immediately-close-a-tls-conn… Sent from the Users mailing list archive at Nabble.com.

2 3

Kamailio and default paramenters to a specific gatewy
by Laura 11 Jan '17

11 Jan '17

Dear all, I'm using kamailio 4.3.6 and LCR modules.. i was wondering if it was possibile to add some special paramenter to all call sent to a specific gateway. I was try to use the " params" field on lcr_gw table but it's not working like i was think.. The issue is simple.. i want to add to field "Privacy: id" to any call i send over a specific gateway.. What is the best and easy way to do that ? Any idea is appreciate. Regards Laura

3 9

Diameter AVP handling from kamaiio.cfg
by Zoltán Miricz 10 Jan '17

10 Jan '17

Dear All, I'm wondering is it possible to catch Diameter Messages and their AVP values from kamailio.cfg just like for SIP messages? (Using pseudo variables) I looked into this function from the attached S-CSCF example. route[REG_MAR_REPLY] { #this is async so to know status we have to check the reply avp xlog("L_DBG","maa_return code is *$avp(s:maa_return_code)*\n"); Sadly it gives back only 1, -1, -2. (which is based on cxdx_mar.c the rc) What I mainly looking for is the EXPERIMENTAL_RESULT (experimental_rc) and some different AVP values besides. Thank you very much in advance! *Cheers,* *Zoltan*

2 5

Kamailio on Cluecon Weekly – Jan 11, 2017
by Daniel-Constantin Mierla 10 Jan '17

10 Jan '17

Hello, for those interested in participating to a (video) chat tomorrow, Wed, Jan 11, I will be joining the ClueCon Weekly at 12:00CT (USA) to discuss about latest Kamailio, what's new and the plans for the near future. Integration with FreeSwitch is going to be among the topics. You can join the video conference call with a webrtc capable browser. You can also join only for audio using a SIP phone or dialing from PSTN or mobile networks. More specific details are available at: - https://www.kamailio.org/w/2017/01/kamailio-on-cluecon-weekly-jan-11-2017/ Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com

1 0

Re: [SR-Users] BYE issue kamailio + rtpproxy "481 call leg transaction doesn't exists".
by Daniel-Constantin Mierla 10 Jan '17

10 Jan '17

Hello, are you using topoh module? A pcap with all sip messages part of the dialog, from the initial INVITE to the last BYE transaction would be important to have in order to investigate how the headers are changed. Cheers, Daniel On 28/12/2016 13:11, Nihar Ranjan Deb wrote: > > Hi All, > > > > I am a new user of kamailio. We have setup a kamilio server with RTP > proxy. Most of the features are working fine except BYE. > > > > > > Say User A and B are registered in kamailio server. A (caller) > connected to B(called), call established. > > > > 1. If Caller (A) disconnects the call, everything goes fine. B gets > disconnected and call releases. > > > > 2. But if Called party (B) disconnects the call, A never gets > disconnected. I checked trace as well, in this case caller (A) gets a > BYE with B's callid. So A rejects call with "481 call leg transaction > doesn't exists". > > Basically A party and B party has separate dialog established with > Kamilio. So they have two separate callids . All messages are > exchanged correctly. Only when B party disconnects call, kamailio > sends BYE to A party with B party callid. > > > > Please help me to resolve this issue. Do let me know if any more > information required. > > > > > > ------ INVITE-------------------------- > > > > INVITE sip:966268@*** SIP/2.0 > > Via: SIP/2.0/UDP > 192.168.1.36:63238;branch=z9hG4bK-524287-1---e64d171ec3b0b54e;rport > > Max-Forwards: 70 > > Contact: <sip:334031@***:8906;rinstance=ea9b5f48eb342a98> > > To: <sip:966268@***> > > From: "334031"<sip:334031@****>;tag=4406552c > > Call-ID: *82158NzljY2NiYTA5YmI3M2U1MzQyODgwMWYwYTI3ZWJjNzc* > > CSeq: 2 INVITE > > Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO, > OPTIONS, MESSAGE > > Content-Type: application/sdp > > Proxy-Authorization: Digest > username="334031",realm="*****",nonce="****",uri="sip:966268@***",response="***",algorithm=MD5 > > Supported: replaces > > User-Agent: X-Lite release 4.9.6 stamp 82158 > > Content-Length: 334 > > > > v=0 > > o=- 13127393523589215 1 IN IP4 192.168.1.36 > > s=X-Lite release 4.9.6 stamp 82158 > > c=IN IP4 192.168.1.36 > > t=0 0 > > m=audio 57116 RTP/AVP 9 8 120 0 84 101 > > a=rtpmap:120 opus/48000/2 > > a=fmtp:120 useinbandfec=1; usedtx=1; maxaveragebitrate=64000 > > a=rtpmap:84 speex/16000 > > a=rtpmap:101 telephone-event/8000 > > a=fmtp:101 0-15 > > a=sendrecv > > > > > > > > -------------------------BYE-------------------------------- > > > > > > BYE sip:334031@192.168.1.36:63238;rinstance=ea9b5f48eb342a98 SIP/2.0 > > Via: SIP/2.0/UDP > ***:5060;branch=z9hG4bKa28b.a2ac8c26802cdcc8c619784643f82000.0 > > Via: SIP/2.0/UDP > 10.0.0.1;branch=z9hG4bKsr-HqsDUwx8-phRByVr-9VwUlbcUlPcIpKo-0noY0rjI95gmMhg10qgY9mc-w5He0EJbTbkb3AZt2Yna6n4uPmqbJWEYwVKYlDTYlH* > > From: <sip:966268@***>;tag=1665200125 > > To: "334031" <sip:334031@***>;tag=4406552c > > Call-ID: > *!!:xePve9XKtEJ4NJJT-2hM9lsXe6RemqZPIRAa1PZf1wJ4DRx5ePRce0OwbHAY-RD4Hlya-HRweMH4N6RemHYMI9Y0tV*** > > CSeq: 3 BYE > > Contact: <sip:10.0.0.1;line=sr-mcsjIlJcYlxcIPVo-0-8Ylb8-9bKUlPjIlxEYwbw> > > Max-Forwards: 69 > > User-Agent: Yealink SIP-T20P 9.72.0.80 > > Content-Length: 0 > > > > > > -------------------------- 481--------------------- > > > > SIP/2.0 481 Call/Transaction Does Not Exist > > Via: SIP/2.0/UDP > ***:5060;branch=z9hG4bKa28b.a2ac8c26802cdcc8c619784643f82000.0;received=35.164.228.12 > > Via: SIP/2.0/UDP > 10.0.0.1;branch=z9hG4bKsr-HqsDUwx8-phRByVr-9VwUlbcUlPcIpKo-0noY0rjI95gmMhg10qgY9mc-w5He0EJbTbkb3AZt2Yna6n4uPmqbJWEYwVKYlDTYlH* > > To: "334031" <sip:334031@***>;tag=4406552c > > From: <sip:966268@***>;tag=1665200125 > > Call-ID: > !!:xePve9XKtEJ4NJJT-2hM9lsXe6RemqZPIRAa1PZf1wJ4DRx5ePRce0OwbHAY-RD4Hlya-HRweMH4N6RemHYMI9Y0tV** > > CSeq: 3 BYE > > Accept-Language: en > > Content-Length: 0 > > > > > > > > > > Regards, > > Nihar > > > > _______________________________________________ > 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 -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com

1 0

[Error] Install Kamailio 4.4 in Mac 10.12
by Luis De Marchi 10 Jan '17

10 Jan '17

Hi, Sorry, my english, I'm using the translator. I'm having trouble installing Kamailio for Mac 10.12 Terminal: Luis:kamailio luisdemarchi$ sudo make all CC (gcc) [M db_mysql.so] km_db_mysql.o km_db_mysql.c:41:10: fatal error: 'mysql.h' file not found #include <mysql.h> ^ 1 error generated. make[1]: *** [km_db_mysql.o] Error 1 make: *** [modules] Error 1 Luís De Marchi Diretor Administrativo +55 (41) 99815-6800 +55 (41) 3027-7669 www.snowmanlabs.com <http://www.snowmanlabs.com/>

4 4

t_precheck_trans
by Annus Fictus 10 Jan '17

10 Jan '17

Hi, where can I find documentation for this function present on the default script? In TM module not exist (Kamailio 4.4.4) Thank you Regards

3 3

use case
by Thufir Hawat 09 Jan '17

09 Jan '17

I'm ok with Linux and am dipping my toe into Asterisk by running an AWS EC2 instance. What is the most frequent usage for kamailio? Would it mainly be for SIP to SIP? So that the URI would be for a specific domain? thanks, Thufir

3 2

using kamailio to forward ipv6 to ipv4
by anfecora 09 Jan '17

09 Jan '17

Hi guys hope you have a great new year. I would appreciate if anyone can point me in to the right direction . I need to build a proxy to translate from ipv6 to ipv4, but kamailio should not process the registers or invites, only translate from ipv6 to ipv4 and forward all registrations over. is that possible? thanks.

4 5

why a register error?
by Olvera, Victor 09 Jan '17

09 Jan '17

As I attempt to use X-lite I get a 504 error. On the CSCFs I get the following: pcscf 0(2066) INFO: <script>: [REGISTER] from [sip:bob@epc.mnc001.mcc001.3gppnetwork.org] to [sip:bob@epc.mnc001.mcc001.3gppnetwork.org] 0(2066) ERROR: <script>: REGISTER (sip:bob@epc.mnc001.mcc001.3gppnetwork.org (192.168.56.1:55880) to sip:bob@epc.mnc001.mcc001.3gppnetwork.org, 81563ZDg1Y2MwZDExYWJiYWJjNDZmNzY0ZWEwYjE1ODNkYmM) icscf 11(2150) INFO: cdp [receiver.c:932]: peer_connect(): peer_connect(): Peer hss.epc.mnc001.mcc001.3gppnetwork.org<http://mcc001.3gppnetwork.org>:3868 connected 0(2138) INFO: <script>: [REGISTER] from [sip:bob@epc.mnc001.mcc001.3gppnetwork.org] to [sip:bob@epc.mnc001.mcc001.3gppnetwork.org] 0(2138) ERROR: <script>: REGISTER (sip:bob@epc.mnc001.mcc001.3gppnetwork.org (192.168.56.76:4060) to sip:bob@epc.mnc001.mcc001.3gppnetwork.org, 81563ZDg1Y2MwZDExYWJiYWJjNDZmNzY0ZWEwYjE1ODNkYmM) 0(2138) INFO: ims_icscf [cxdx_uar.c:71]: create_uaa_return_code(): created AVP successfully : [uaa_return_code] 6(2145) INFO: ims_icscf [cxdx_avp.c:137]: cxdx_get_avp(): cxdx_get_server_name: Failed finding avp 6(2145) INFO: ims_icscf [cxdx_avp.c:137]: cxdx_get_avp(): cxdx_get_result_code: Failed finding avp 6(2145) INFO: ims_icscf [cxdx_uar.c:71]: create_uaa_return_code(): created AVP successfully : [uaa_return_code] 0 scscf 11(2047) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 192.168.56.78 port 3868 11(2047) INFO: cdp [receiver.c:932]: peer_connect(): peer_connect(): Peer hss.epc.mnc001.mcc001.3gppnetwork.org<http://mcc001.3gppnetwork.org>:3868 connected 9(2045) ERROR: cdp [peerstatemachine.c:635]: I_Snd_CER(): I_Snd_CER(): Error on finding local host address > Socket operation on non-socket Great regards, Victor Olvera victor.olvera(a)verizonwireless.com<mailto:victor.olvera@verizonwireless.com> mobile # 001-214-923-9405

2 1

Re: [SR-Users] BYE issue kamailio + rtpproxy "481 call leg transaction doesn't exists".
by Nihar Ranjan Deb 09 Jan '17

09 Jan '17

Anyone any help on this. Regards, Nihar From: Nihar Ranjan Deb [mailto:nihar.ranjan@microtalkgroup.com] Sent: Wednesday, December 28, 2016 5:42 PM To: 'sr-users(a)lists.sip-router.org' Subject: BYE issue kamailio + rtpproxy "481 call leg transaction doesn't exists". Hi All, I am a new user of kamailio. We have setup a kamilio server with RTP proxy. Most of the features are working fine except BYE. Say User A and B are registered in kamailio server. A (caller) connected to B(called), call established. 1. If Caller (A) disconnects the call, everything goes fine. B gets disconnected and call releases. 2. But if Called party (B) disconnects the call, A never gets disconnected. I checked trace as well, in this case caller (A) gets a BYE with B's callid. So A rejects call with "481 call leg transaction doesn't exists". Basically A party and B party has separate dialog established with Kamilio. So they have two separate callids . All messages are exchanged correctly. Only when B party disconnects call, kamailio sends BYE to A party with B party callid. Please help me to resolve this issue. Do let me know if any more information required. ------ INVITE-------------------------- INVITE sip:966268@*** SIP/2.0 Via: SIP/2.0/UDP 192.168.1.36:63238;branch=z9hG4bK-524287-1---e64d171ec3b0b54e;rport Max-Forwards: 70 Contact: <sip:334031@***:8906;rinstance=ea9b5f48eb342a98> To: <sip:966268@***> From: "334031"<sip:334031@****>;tag=4406552c Call-ID: 82158NzljY2NiYTA5YmI3M2U1MzQyODgwMWYwYTI3ZWJjNzc CSeq: 2 INVITE Allow: SUBSCRIBE, NOTIFY, INVITE, ACK, CANCEL, BYE, REFER, INFO, OPTIONS, MESSAGE Content-Type: application/sdp Proxy-Authorization: Digest username="334031",realm="*****",nonce="****",uri="sip:966268@***",response=" ***",algorithm=MD5 Supported: replaces User-Agent: X-Lite release 4.9.6 stamp 82158 Content-Length: 334 v=0 o=- 13127393523589215 1 IN IP4 192.168.1.36 s=X-Lite release 4.9.6 stamp 82158 c=IN IP4 192.168.1.36 t=0 0 m=audio 57116 RTP/AVP 9 8 120 0 84 101 a=rtpmap:120 opus/48000/2 a=fmtp:120 useinbandfec=1; usedtx=1; maxaveragebitrate=64000 a=rtpmap:84 speex/16000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv -------------------------BYE-------------------------------- BYE sip:334031@192.168.1.36:63238;rinstance=ea9b5f48eb342a98 SIP/2.0 Via: SIP/2.0/UDP ***:5060;branch=z9hG4bKa28b.a2ac8c26802cdcc8c619784643f82000.0 Via: SIP/2.0/UDP 10.0.0.1;branch=z9hG4bKsr-HqsDUwx8-phRByVr-9VwUlbcUlPcIpKo-0noY0rjI95gmMhg10 qgY9mc-w5He0EJbTbkb3AZt2Yna6n4uPmqbJWEYwVKYlDTYlH* From: <sip:966268@***>;tag=1665200125 To: "334031" <sip:334031@***>;tag=4406552c Call-ID: !!:xePve9XKtEJ4NJJT-2hM9lsXe6RemqZPIRAa1PZf1wJ4DRx5ePRce0OwbHAY-RD4Hlya-HRwe MH4N6RemHYMI9Y0tV** CSeq: 3 BYE Contact: <sip:10.0.0.1;line=sr-mcsjIlJcYlxcIPVo-0-8Ylb8-9bKUlPjIlxEYwbw> Max-Forwards: 69 User-Agent: Yealink SIP-T20P 9.72.0.80 Content-Length: 0 -------------------------- 481--------------------- SIP/2.0 481 Call/Transaction Does Not Exist Via: SIP/2.0/UDP ***:5060;branch=z9hG4bKa28b.a2ac8c26802cdcc8c619784643f82000.0;received=35.1 64.228.12 Via: SIP/2.0/UDP 10.0.0.1;branch=z9hG4bKsr-HqsDUwx8-phRByVr-9VwUlbcUlPcIpKo-0noY0rjI95gmMhg10 qgY9mc-w5He0EJbTbkb3AZt2Yna6n4uPmqbJWEYwVKYlDTYlH* To: "334031" <sip:334031@***>;tag=4406552c From: <sip:966268@***>;tag=1665200125 Call-ID: !!:xePve9XKtEJ4NJJT-2hM9lsXe6RemqZPIRAa1PZf1wJ4DRx5ePRce0OwbHAY-RD4Hlya-HRwe MH4N6RemHYMI9Y0tV** CSeq: 3 BYE Accept-Language: en Content-Length: 0 Regards, Nihar

1 0

VERY IMPORTANT: deciding when to remove the MI code
by Daniel-Constantin Mierla 06 Jan '17

06 Jan '17

Hello, we started discussing about removing MI (so called management interface) for very long time, more or less since 2008. The RPC should remain the control interface, given its better structure for commands, parameters, etc ... MI is custom protocol using a line-oriented communication via fifo or socket file with kamailio (e.g., implemented mi_fifo and mi_datagram modules). RPC is the alternative, a more standardized concept, with better structured format. I think it's time to set a clear roadmap for doing the removal. Overall, it will be easier to maintain the code, right now being duplicated code for doing the same operation over MI or RPC, and MI shows its limitations (or complexity to deal with) for advanced needs (see the discussions about how to provide multi-line value parameters over MI). So, I want to know if there are many relying on MI directly and they still want to keep it, what would be the expected duration they need for upgrading their tools to work with RPC interface, other relevant aspects people have in favour of mi vs rpc. I am even willing to do the removal in time befire freezing the 5.0 branch. We will ensure a clean start of 5.x series. The main concern from my point of view is kamctl -- but I think we can preserve the compatibility for kamctl commands and parameters (so command line execution of kamctl will be the same), but the output might be different. That's because it should be easy to updated it to communicate with jsonrpc-s module, but then it will get json-formatted results. To summarize, two big questions to answer: a) Are you ok to remove the MI code/commands? b) If yes to a), are you ok to be done for v5.0? Not providing feedback will be considered as 'yes' for both questions, so **speak up if you want MI to be kept or delay it removal**. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com

6 30

presentity tabla, faster update when drop TCP/TLS connection
by João Resende 05 Jan '17

05 Jan '17

I'm testing kamailio with a SIP client with presence support, when I get a connection drop from a client (i.e when the client lost the access to the Internet connection) I do not receive the change in the status to offline immediately, I just received when the timeout from the presentity database finishes. Exists a way to define this? or it is a bug? or should be a new feature? I know that I'm able to change the expiry parameter from the presentity table, but that increases my battery consumption and the data exchange, the same happens if I reduce the publish interval on the client side.

3 9

Re: [SR-Users] using kamailio to forward ipv6 to ipv4
by anfecora 05 Jan '17

05 Jan '17

Yes i am planning on proxing media. The case is that client will only talk ipv6 but the registrar only have ipv4 connectivity. Therefore need to create a proxy to translate this dialogs. Thi thnking on using kamailio to receive the registration modify the pckets and forward registrations in ipv4. I was thinking in using the asterisk kamailio example but instead of asterisk behind will be an sbc. Therefore kamailio will listen in ipv6 and translate over to ipv4 including media of course via rtpproxy. On Jan 5, 2017 9:43 AM, "Frank Carmickle" <frank(a)carmickle.com> wrote: > On Jan 5, 2017, at 12:24 PM, anfecora <anfecora(a)gmail.com> wrote: > > Hi guys hope you have a great new year. > I would appreciate if anyone can point me in to the right direction . > > I need to build a proxy to translate from ipv6 to ipv4, but kamailio should not process the registers or invites, only translate from ipv6 to ipv4 and forward all registrations over. A bit more information about the situation would be helpful. What exactly are you trying to do? > is that possible? 6 to 4 translation is possible, but until we understand the situation I’m not sure we can be that helpful. Are these phones? If so are they dual stack? Is the underlying network dual stack? There’s a lot of work to do to get this right in a Kamailio config. You’ll need to run rtpengine to proxy the media if the endpoints are not dual stack. Who keeps the mapping of the v6 to v4 and v4 to v6 translations? How is that mapping determined? I’d recommend ds-lite if you are in a position to alter the network and the phones/systems allow for it. HTH —FC > thanks. > > > _______________________________________________ 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

CDR - acc_cdrs
by Annus Fictus 05 Jan '17

05 Jan '17

Hello, I'm trying to save Kamailio CDR on acc_cdrs table without success. My relevant configuration look like: ----- #!define FLT_ACC 1 #!define FLT_ACCMISSED 2 #!define FLT_ACCFAILED 3 ----- #!define WITH_ACCDB ---- loadmodule "dialog.so" loadmodule "acc.so" modparam("dialog", "dlg_flag", 0) ---- # ----- acc params ----- modparam("acc", "early_media", 0) modparam("acc", "report_ack", 0) modparam("acc", "report_cancels", 0) modparam("acc", "detect_direction", 0) modparam("acc", "log_flag", FLT_ACC) modparam("acc", "log_missed_flag", FLT_ACCMISSED) modparam("acc", "log_extra", "src_user=$fU;src_domain=$fd;src_ip=$si;" "dst_ouser=$tU;dst_user=$rU;dst_domain=$rd") modparam("acc", "failed_transaction_flag", FLT_ACCFAILED) #!ifdef WITH_ACCDB modparam("acc", "db_flag", FLT_ACC) modparam("acc", "db_missed_flag", FLT_ACCMISSED) modparam("acc", "db_url", DBURL) modparam("acc", "cdr_enable", 1) modparam("acc", "cdr_log_enable", 1) modparam("acc", "cdr_on_failed", 1) modparam("acc", "cdrs_table", "acc_cdrs") modparam("acc", "cdr_start_on_confirmed", 1) modparam("acc", "db_extra", "src_user=$fU;src_domain=$fd;src_ip=$si;" "dst_ouser=$tU;dst_user=$rU;dst_domain=$td") #!endif Any hint is really appreciate. Regards

2 4

unexpected char - status 6
by AL S 05 Jan '17

05 Jan '17

Hi, Kamailio is throwing error message from "parse_to.c" with status=6. The source code shows status 6 as URI_ENCLOSED. However, tcpdump of the call does not show any enclosed angle bracket is missing. (tcpdump pcap file is attached.) Kamailio log Jan 4 10:18:21 orl-ar-openser01 /usr/sbin/kamailio[2374]: ERROR: <core> [parser/parse_to.c:626]: ERROR: parse_to : unexpected char [#015] in status 6: <<<sip:2057030997@72.31.12.161;tag=gK04001cd3>> . FROM and TO in INVITE received by Kamailio From: <sip:7272697443@71.44.15.84>;tag=gK00d6c4e0 To: <sip:2057030997@72.31.12.161>;tag=gK04001cd3 FROM and TO in INVITE forward by Kamailio for the same call From: <sip:7272697443@71.44.15.84>;tag=gK00d6c4e0 To: <sip:2057030997@72.31.12.161\000\000>;tag=gK04001cd3 PS: this error message is happening on all 4 kamailio servers (3.3.0) PS: call failure only happens in re INVITE (call stays active longer than 15 min) Your help would be appreciated. Thanks, AS

2 2

RTPProxy with VPN
by Rodrigo Moreira 05 Jan '17

05 Jan '17

Hello, I am having problems with RTPPROXY. I need it to work as a bridge. On one side will have a VPN tunnel called a tun0, on the other an eth0 interface. Is it possible for RTPPROXY to run correctly in this scenario? How can I test if RTPPROXY is running correctly? Is there any command? What would the configuration look like inside /etc/default/rtpproxy Please help me. Best regards -- Rodrigo M. (37) 9132-4539 (34) 9889-3069 rodrigo.moreira2007

2 1

Re: [SR-Users] Regarding usage of Redis Module in Kamailio core
by Vicente Hernando 05 Jan '17

05 Jan '17

Hello Hemanth, this minimal kamailio cfg file works for me to test ndb_redis module. #!KAMAILIO debug=4 log_stderror=yes children=4 fork=yes #disable_tcp=yes mpath="modules/" loadmodule "ndb_redis.so" # An already configured redis server is needed here modparam("ndb_redis", "server", "name=srv1;addr=127.0.0.1;port=6379;db=0") request_route { redis_cmd("srv1", "SET foo bar", "r"); exit; } Changing the parameters to suit your configuration, you can use it to debug your system. Regards, Vicente. On 01/05/2017 07:55 AM, hemanth(a)advaitamtech.com wrote: > > Hello Vicente, > > Thanks for your response, > > In response to your query, > > Yes i have Built ndb_redis module and i can see ndb_redis.so in /usr/local/lib64/kamailio/modules folder, I have installed hiredis depenency also, > > I have also modified the kamailio.cfg file loadmodule and modparam list, > > I feel like the way i am using the redis_cmd is wrong, I think i need to add it in route section of kamailio.cfg file, Can you please guide me regarding how to use redis db in order to update user information to DB on registration of each user. > > Thanks & Regards > Hemanth > > > Message: 8 > Date: Wed, 4 Jan 2017 14:41:42 +0530 (IST) > From: "hemanth(a)advaitamtech.com" <hemanth(a)advaitamtech.com> > To: sr-users(a)lists.sip-router.org > Subject: [SR-Users] Regarding usage of Redis Module in Kamailio core > Message-ID: <1483521102.18025940(a)apps.rackspace.com> > Content-Type: text/plain;charset=UTF-8 > > Hello, > > I am using Kamailio as a SIP proxy, > > I want to store Registered user information in Redis DB, > > I am able to configure REDIS DB, But i am not able to run the redis command from > > Kamailio core using the function > > "redis_cmd("srvN","SET key 1", "r")" > > I am getting undefined reference error as below > > "/usr/local/src/kamailio-4.4/kamailio/receive.c:208: undefined reference to `redis_cmd'" > > can anyone please help me to fix this issue > > Thanks & Regards > Hemanth > > > > > ------------------------------ > > Message: 9 > Date: Wed, 4 Jan 2017 10:50:05 +0100 > From: Vicente Hernando <vhernando(a)systemonenoc.com> > To: sr-users(a)lists.sip-router.org > Subject: Re: [SR-Users] Regarding usage of Redis Module in Kamailio > core > Message-ID: <b003d2aa-ddd0-574d-b9e3-9b91e44976f1(a)systemonenoc.com> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hello Hemanth, > > just a quick response, I would check if you compiled ndb_redis module > correctly (also if you have hiredis library dependency). > > Also I would check if you loaded ndb_redis module in your configuration > file. > > > Regards, > Vicente. > > On 01/04/2017 10:11 AM, hemanth(a)advaitamtech.com wrote: >> Hello, >> >> I am using Kamailio as a SIP proxy, >> >> I want to store Registered user information in Redis DB, >> >> I am able to configure REDIS DB, But i am not able to run the redis command from >> >> Kamailio core using the function >> >> "redis_cmd("srvN","SET key 1", "r")" >> >> I am getting undefined reference error as below >> >> "/usr/local/src/kamailio-4.4/kamailio/receive.c:208: undefined reference to `redis_cmd'" >> >> can anyone please help me to fix this issue >> >> Thanks & Regards >> Hemanth >> >> >> _______________________________________________ >> 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 > > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > sr-users mailing list > sr-users(a)lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > > > ------------------------------ > > End of sr-users Digest, Vol 140, Issue 3 > **************************************** > > > >

1 0

Kamailio cancel branch only after receiving replies
by Aqs Younas 05 Jan '17

05 Jan '17

Greetings list, I am forking a call to multiple destinations and want to keep the only branch which sends quicker first 180/183 reply and cancel the remaining branches. Below is my related cfg snippet. modparam("tm", "failure_reply_mode", 3) modparam("tm", "fr_timer", 30000) modparam("tm", "fr_inv_timer", 120000) modparam("tm", "cancel_b_method", 2) ... route[SIPOUT] { if (uri==myself) return; append_hf("P-hint: outbound\r\n"); append_branch(); append_branch(); route(RELAY); exit; } onreply_route[MANAGE_REPLY] { xdbg("incoming reply\n"); if(status=~"[12][0-9][0-9]") { xlog("L_INFO","Received $rs (IP:$si:$sp)\n"); if(status=~"18[03]"){ t_cancel_branches("others"); xlog("L_INFO","cancelled all other branches\n"); } route(NATMANAGE); } } ... But I see kamailio does not instantly send CANCEL to other branches after it has received 180/180 from any branch. Kamailio is sending CANCEL to other branches after they start sending 180/183 one by one. How can I cancel all other branches instantly? I am sure there is something wrongly configured in my configuration. Any suggestion is much appreciated. Best Regards.

3 3

location
by Slava Bendersky 05 Jan '17

05 Jan '17

Hello Everyone, Why save location will ignore on pv var when trying save on reply 200 OK. if(is_method("REGISTER") && fnmatch("$rs", "200")) { xlog("L_INFO", "OnReply: Registration is $rs OK saving --> $avp(rcvcontact) in db\n"); $var(oar) = "sip:" + $tU + "@" + $(avp(rcvcontact){uri.host}) + ":" + $(avp(rcvcontact){uri.port}); if(!save("location", "0x04", "$var(oar)")) { xlog("L_INFO", "Error saving the location\n"); } Dec 26 11:43:20 cavprx00 kamailio: 4(5546) ERROR: *** cfgtrace:onreply_route=[LOCATION_REPLY] c=[/etc/kamailio/kamailio-prod.cfg] l=619 a=26 n=xlog Dec 26 11:43:20 cavprx00 kamailio: 4(5546) INFO: <script>: OnReply: Registration is 200 OK saving --> sip:4300@client_pub_ip:31376;transport=tls in db Dec 26 11:43:20 cavprx00 kamailio: 4(5546) ERROR: *** cfgtrace:onreply_route=[LOCATION_REPLY] c=[/etc/kamailio/kamailio-prod.cfg] l=620 a=63 n=assign Dec 26 11:43:20 cavprx00 kamailio: 4(5546) ERROR: *** cfgtrace:onreply_route=[LOCATION_REPLY] c=[/etc/kamailio/kamailio-prod.cfg] l=624 a=16 n=if Dec 26 11:43:20 cavprx00 kamailio: 4(5546) ERROR: *** cfgtrace:onreply_route=[LOCATION_REPLY] c=[/etc/kamailio/kamailio-prod.cfg] l=621 a=27 n=save Dec 26 11:43:20 cavprx00 kamailio: 4(5546) DEBUG: <core> [sruid.c:182]: sruid_next(): new sruid is [uloc-586147f5-15aa-1] (1 / 20) Dec 26 11:43:20 cavprx00 kamailio: 4(5546) DEBUG: registrar [save.c:410]: pack_ci(): generated ruid is: uloc-586147f5-15aa-1 Dec 26 11:43:20 cavprx00 kamailio: 4(5546) DEBUG: <core> [sruid.c:182]: sruid_next(): new sruid is [uloc-586147f5-15aa-2] (2 / 20) Dec 26 11:43:20 cavprx00 kamailio: 4(5546) DEBUG: registrar [save.c:410]: pack_ci(): generated ruid is: uloc-586147f5-15aa-2 Dec 26 11:43:20 cavprx00 kamailio: 4(5546) DEBUG: usrloc [ucontact.c:1004]: db_update_ucontact_ruid(): ruid:uloc-5860b463-10c5-1 Dec 26 11:43:20 cavprx00 kamailio: 4(5546) DEBUG: usrloc [ucontact.c:1133]: db_update_ucontact_ruid(): contact:sip:4300@10.18.130.27:5060;transport=udp ----> LAN side contact Dec 26 11:43:20 cavprx00 kamailio: 4(5546) DEBUG: db_postgres [km_val.c:163]: db_postgres_val2str(): PQescapeStringConn: in: 10 chars, out: 10 chars Dec 26 11:43:20 cavprx00 kamailio: 4(5546) DEBUG: db_postgres [km_val.c:163]: db_postgres_val2str(): PQescapeStringConn: in: 21 chars, out: 21 chars Dec 26 11:43:20 cavprx00 kamailio: 4(5546) DEBUG: db_postgres [km_val.c:163]: db_postgres_val2str(): PQescapeStringConn: in: 33 chars, out: 33 chars Dec 26 11:43:20 cavprx00 kamailio: 4(5546) DEBUG: db_postgres [km_val.c:163]: db_postgres_val2str(): PQescapeStringConn: in: 40 chars, out: 40 chars Dec 26 11:43:20 cavprx00 kamailio: 4(5546) DEBUG: db_postgres [km_val.c:163]: db_postgres_val2str(): PQescapeStringConn: in: 20 chars, out: 20 chars Slava.

2 7

Kamailio v5.0 - development frozen
by Daniel-Constantin Mierla 05 Jan '17

05 Jan '17

Hello, development (master) branch of Kamailio enters now in pre-release phase for version 5.0.0. Therefore, no new feature should be pushed to master until we create a dedicated branch for 5.0 (expected to be in about 4 weeks or so). If in doubt to push or not a commit to master, push it first on a personal branch (or attach to an email) and discuss it on sr-dev. The new modules can be a bit more dynamic if there is need to get them to the right shape (e.g., like decision to rename functions, parameters or adjust database structure). We hope to get many people involved in testing, to reach a stable state before releasing 5.0.0. If you want to get involved and need assistance, don't hesitate to write to mailing lists. Besides the new features, there were two major changes for 5.0: 1) source code tree restructuring - this should not affect the stability of the code, only installation scripts or packaging may still need tuning 2) mi (management/control interface) code has been removed. SIP routing code should not be affected by this change that much, but testing of RPC commands needs a special care. There are few RPC commands not ported yet from the MI code, they can be done during the testing period Moreover, help with updating the wiki page for migration from 4.4 to 5.0 as well as what is new in 5.0 is very appreciated. I will try post updates about them very soon. Many thanks to everyone involved in development of 5.0 and the early testers that played with master branch so far. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com

1 0

unexpected char [#015]
by AL S 04 Jan '17

04 Jan '17

Hi, Kamailio is complaining about unexpected char [#015] in TO header of INVITE: Jan 3 14:55:41 tpa-ar-openser01 /usr/sbin/kamailio[4782]: ERROR: <core> [parser/parse_to.c:626]: ERROR: parse_to : unexpected char [#015] in status 6: <<<sip:2057030997@72.31.12.161;tag=gK006cb08b>> . Jan 3 14:55:41 tpa-ar-openser01 /usr/sbin/kamailio[4782]: ERROR: <core> [parser/msg_parser.c:180]: ERROR: get_hdr_field: bad to header Jan 3 14:55:41 tpa-ar-openser01 /usr/sbin/kamailio[4782]: INFO: <core> [parser/msg_parser.c:353]: ERROR: bad header field [To: <sip:2057030997@] Jan 3 14:55:41 tpa-ar-openser01 /usr/sbin/kamailio[4782]: ERROR: tm [t_lookup.c:1118]: ERROR: reply cannot be parsed Here is the TO header for the same call in both text and hex format. I am unable to see any ^M char in this TO header. To: <sip:2057030997@72.31.12.161;tag=gK006cb08b 546f3a203c7369703a323035373033303939374037322e33312e31322e3136313e3b7461673d674b30303663623038620d0a Any help would be appreciated. AS,

2 2

IMPORTANT: MI code removed (or disabled)
by Daniel-Constantin Mierla 04 Jan '17

04 Jan '17

Hello, as of now, no active MI reladed code should be in master branch -- the internal library kmi and the mi_datagram, mi_fifo, mi_xmlrpc, mi_rpc and pua_mi modules were removed. Couple of modules still have some mi code disabled with ifdefs, they are pending the port to RPC commands. These are: - carrierroute - ims_dialog - mohqueue - p_usrloc - pdb - rtpengine - userblacklist - utils They should be updated in the next few days. With MI code removed, the code is slimmer and the development effort is reduced -- in the recent past there were various issue rising due to usage of the old line-based MI commands. >From now on, the RPC interface has to be used for interacting with kamailio at runtime. The tools: - kamctl - was already migrated to use RPC via jsonrpcs module. - kamcmd - was developed to use only RPC interface via ctl module. - kamcli - is also working with RPC via jsonrpcs module Helping with testing the RPC commands is very appreciated -- open an issue on bug tracker whenever you discover a problem. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com

1 0

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