sr-users

sr-users@lists.kamailio.org

7 participants
37522 discussions

cnxcc-web error
by Infinicalls Infinicalls 01 Aug '16

01 Aug '16

Hi, I am really struggling to get the cnxcc-web installed. the /var/log/apache2/error.log says [Mon Aug 01 02:52:00.177725 2016] [:error] [pid 17534] [client 115.241.40.163:1851] PHP Deprecated: ServiceManagerAwareInterface is deprecated and will be removed in version 3.0, along with the ServiceManagerAwareInitializer. Please update your class ZfcUser\\Authentication\\Adapter\\Db to remove the implementation, and start injecting your dependencies via factory instead. in /usr/local/cnxcc/cnxcc-web/vendor/zendframework/zend-mvc/src/Service/ServiceManagerConfig.php on line 129, referer: http://xxxxxxxx.com/user/login I am getting the login screen and it freezes there. Can somebody guide me how to go about? Or is there a simple php (without Zend framework) interface available for cnxcc? thanks Ganesh Kumar

2 1

manage rtp with or without RTP Proxy
by Achintha 01 Aug '16

01 Aug '16

hi I have configured kamailio and freeswitch on two Ubuntu servers as follows. Sip_TRUNK------> kamailio-------> freeswitch i wan to manage rtp through the kamailio server, first i want to know, 1. can i do it without RTP Proxy ? anyway i tried it with RTP Proxy as follows, I installed rtpproxy on kamailio server and start it using “rtpproxy –F -l pu.bl.ic.ip -s udp:localhost :7722 -u root” it was working Then I put modparam("rtpproxy", "rtpproxy_sock", "udp:localhost:7722") modparam("rtpproxy", "rtpproxy_retr", 2) modparam("rtpproxy", "ice_candidate_priority_avp", "$avp(ice_priority)") mhomed=0 route[FROM_TRUNK] force_send_socket("pu.bl.ic.ip "); rtpproxy_manage("","pu.bl.ic.ip "); $du="sip:ip.of.free.switch:5080"; route(RELAY); then call is received to user and disconnected on freeswitch console get some errors [ERR] switch_core_media.c:7179 AUDIO RTP REPORTS ERROR: [Remote Address Error!] [ERR] mod_sofia.c:2290 CODEC NEGOTIATION ERROR. SDP: v=0 o=- 3679035755 3679035755 IN IP4 pu.bl.ic.ippu.bl.ic.ip s=pjmedia b=AS:84 t=0 0 a=X-nat:0 m=audio 4167841678 RTP/AVP 123 8 0 101 c=IN IP4 pu.bl.ic.ippu.bl.ic.ip b=TIAS:64000 a=rtpmap:123 opus/48000/2 a=fmtp:123 maxplaybackrate=16000;sprop-maxcapturerate=16000;maxaveragebitrate=16000;useinbandfec=1 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=rtcp:4167941679 a=nortpproxy:yes a=nortpproxy:yes please advice me thank you

2 1

function to check if string is an ipv4 address
by Juha Heinanen 29 Jul '16

29 Jul '16

I did not find in textops or utils modules a function to check if a string is an ipv4 address. Does it exist somewhere else? -- Juha

2 2

RTPEngine Kamailio crashed because someone tried to do something
by Andrew Tan 29 Jul '16

29 Jul '16

I'm getting below every 2-3 weeks someone tried to connect through the CLi of RTPengine and crashed Rtpengine. Anyone knows what to make out of this ? Thanks Andrew 82440 Jul 28 16:24:21 sipr /usr/local/sbin/kamailio[13020]: INFO: <script>: HTTP Request Received 182441 Jul 28 16:24:21 sipr /usr/local/sbin/kamailio[13020]: ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 16) 182442 Jul 28 16:24:21 sipr /usr/local/sbin/kamailio[13020]: ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<HTTP/1.1 404 Not Found#015#012Sia: SIP/2.0/TCP 89.163.135.117:63413#015#012Server: kamailio (4.3.3 (x86_64/linux))#015#012Content-Length: 0#015#012#015#012> 182443 Jul 28 16:24:21 sipr rtpengine[1224]: New cli connection from 89.163.135.117:63587 182444 Jul 28 16:24:21 sipr rtpengine[1224]: Got CLI command: 182445 Jul 28 16:24:21 sipr rtpengine[1224]: New cli connection from 89.163.135.117:63838 182446 Jul 28 16:24:21 sipr /usr/local/sbin/kamailio[13028]: WARNING: <script>: HTTP request received on 5080 182447 Jul 28 16:24:21 sipr /usr/local/sbin/kamailio[13021]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request 182448 Jul 28 16:24:21 sipr /usr/local/sbin/kamailio[13021]: ERROR: <core> [tcp_read.c:1303]: tcp_read_req(): ERROR: tcp_read_req: error reading 182449 Jul 28 16:24:21 sipr /usr/local/sbin/kamailio[13020]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request 182450 Jul 28 16:24:21 sipr /usr/local/sbin/kamailio[13020]: ERROR: <core> [tcp_read.c:1303]: tcp_read_req(): ERROR: tcp_read_req: error reading 182451 Jul 28 16:24:21 sipr /usr/local/sbin/kamailio[13021]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request 182452 Jul 28 16:24:21 sipr /usr/local/sbin/kamailio[13021]: ERROR: <core> [tcp_read.c:1303]: tcp_read_req(): ERROR: tcp_read_req: error reading 182453 Jul 28 16:24:21 sipr /usr/local/sbin/kamailio[13028]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request 182454 Jul 28 16:24:21 sipr /usr/local/sbin/kamailio[13028]: ERROR: <core> [tcp_read.c:1303]: tcp_read_req(): ERROR: tcp_read_req: error reading 182455 Jul 28 16:24:22 sipr /usr/local/sbin/kamailio[13020]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request 182456 Jul 28 16:24:22 sipr /usr/local/sbin/kamailio[13020]: ERROR: <core> [tcp_read.c:1303]: tcp_read_req(): ERROR: tcp_read_req: error reading 182457 Jul 28 16:24:22 sipr /usr/local/sbin/kamailio[13021]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request 182458 Jul 28 16:24:22 sipr /usr/local/sbin/kamailio[13021]: ERROR: <core> [tcp_read.c:1303]: tcp_read_req(): ERROR: tcp_read_req: error reading

2 1

Kamailio LB: how to get Asterisk to do the RTP
by Tickling Contest 28 Jul '16

28 Jul '16

With the help of members from this mailing list (many thanks!), I finally got Asterisk fronted by Kamailio for LB and REGISTERs and I am able to make a call using the setup that looks like this: [Kamailio 4.4.2]<->[Asterisk 13.7.2] Kamailio manages REGISTERs, but also forwarding them to Asterisk. I am able to make a call, but I get only one way audio or no audio depending on which client made the call (SipDroid->Zoiper I hear one way audio on Zoiper, but no audio if the call is made the other way). I noticed that Kamailio forced direct media between the endpoints in this situation, but my application really needs Asterisk to handle it. How do I do this? Should I start by forwarding INVITEs to Asterisk? How do I do that? Any help is appreciated. Thanks!

5 5

undefined symbol: EVP_sha1 when using outbound module
by Francisco Burgos 28 Jul '16

28 Jul '16

Hi, I am trying to use kamailio as an edge proxy to forward requests and media to an sbc. when compiling the cfg file included on the examples. i get: undefined symbol: EVP_sha1 I believe this problem is being caused by the outbound module and after some research i managed to read that it is caused by the linking between the gcc libcrypto. I would like some help since this project requires urgency. Thanks in advance.

2 5

TM: t_relay([host, port]) DNS Queries
by Louis-Olivier Roof 27 Jul '16

27 Jul '16

Dear Kamailio users, Ref: http://kamailio.org/docs/modules/4.2.x/modules/tm.html#tm.f.t_relay Using t_relay([host, port]) to relay messages to a specific host does not seem to generate DNS queries to the said host after Kamailio has initially processed the configuration file. It resolves the host once at startup then continues using the same IP after. Is that expected behavior? Anyone has had this issue before and found a way to work around it? Note that for this specific application, messages need to be relayed to a specified host (different from current R-URI) and this host needs to be resolved by DNS during normal operation, not only at startup. Thanks! Louis-Olivier

2 4

Checking for 200ok Response to a REGISTER request kamailio-Asterisk
by Jonathan Hunter 27 Jul '16

27 Jul '16

Hi Guys, So currently on our network we have a kamailio server which users register against, we then replicate the register messages to 2 Asterisk boxes sat behind it so that all entities are aware of the registration state of the users. REGISTER--->KAMAILIO---->ASTERISK A ---->ASTERISK B With a REGISTER---200OK exchange between Kamailio and Asterisk. We have an issue where at some points the Asterisk servers when under load dont respond with a 200 ok(something being investigated) to the register messages sent to kamailio, so I am just working on some logic for the register message to be resent using the t_replicate and t_set_fr functions. This works well should both Asterisk servers not respond, however, as I am using replicate and it is parallel forking, if say Asterisk A answers first and is available with a 200ok then that in turn cancels the register message branch being sent to Asterisk B(which I know is fine), however there could be a scenario where Asterisk B doesnt respond, and we wont know about it to try and resend the Register message, as the branch is cancelled. Hope that makes sense? I am looking at checking that both the Asterisk servers have responded and sent a 200ok, which I can grab in an onreply route but Im just wondering if someone has done something similar or has any suggestions as it is tricky to achieve currently. I have also thought about stateless working but I really need kamailio to keep retransmitting the register until it gets a response. Many thanks Jon

2 4

Segfault in dialog.so with 4.4.2 stable
by Dirk Teurlings - Signet B.V. 26 Jul '16

26 Jul '16

Hi, Running Kamailio on Debian from the Kamailio repository with 4.4.2 stable (unpatched). Getting some random segfaults with it now, here's the relevant backtrace from the generated core. Core was generated by `/usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.'. Program terminated with signal 11, Segmentation fault. #0 run_dlg_callbacks (type=type@entry=64, dlg=dlg@entry=0x7fceb400e2f0, req=req@entry=0x7fced4f093c8, rpl=rpl@entry=0x0, dir=<optimized out>, dlg_data=dlg_data@entry=0x0) at dlg_cb.c:253 253 if ( (cb->types)&type ) { (gdb) bt #0 run_dlg_callbacks (type=type@entry=64, dlg=dlg@entry=0x7fceb400e2f0, req=req@entry=0x7fced4f093c8, rpl=rpl@entry=0x0, dir=<optimized out>, dlg_data=dlg_data@entry=0x0) at dlg_cb.c:253 #1 0x00007fcead3648f9 in dlg_terminated (dir=<optimized out>, dlg=0x7fceb400e2f0, req=0x7fced4f093c8) at dlg_handlers.c:368 #2 dlg_onroute (req=0x7fced4f093c8, route_params=<optimized out>, param=<optimized out>) at dlg_handlers.c:1354 #3 0x00007fceb10ab0e2 in run_rr_callbacks (req=req@entry=0x7fced4f093c8, rr_param=rr_param@entry=0x7fceb12b77a0) at rr_cb.c:96 #4 0x00007fceb10952c5 in after_loose (_m=0x7fced4f093c8, preloaded=0) at loose.c:919 #5 0x000000000042b618 in do_action (h=h@entry=0x7ffeb0b3ed80, a=a@entry=0x7fced4cb4338, msg=msg@entry=0x7fced4f093c8) at action.c:1060 #6 0x000000000042a10a in run_actions (h=h@entry=0x7ffeb0b3ed80, a=0x7fced4cb4338, msg=0x7fced4f093c8) at action.c:1549 #7 0x0000000000437544 in run_actions_safe (h=h@entry=0x7ffeb0b402b0, a=<optimized out>, msg=<optimized out>) at action.c:1614 #8 0x000000000053b2e8 in rval_get_int (h=0x7ffeb0b402b0, msg=<optimized out>, i=0x7ffeb0b3f1e0, rv=rv@entry=0x7fced4cb4d58, cache=cache@entry=0x0) at rvalue.c:912 #9 0x000000000054261c in rval_expr_eval_int (h=h@entry=0x7ffeb0b402b0, msg=msg@entry=0x7fced4f093c8, res=res@entry=0x7ffeb0b3f1e0, rve=rve@entry=0x7fced4cb4d50) at rvalue.c:1910 #10 0x000000000042bc91 in do_action (h=h@entry=0x7ffeb0b402b0, a=a@entry=0x7fced4cb8f88, msg=msg@entry=0x7fced4f093c8) at action.c:1030 #11 0x000000000042a10a in run_actions (h=h@entry=0x7ffeb0b402b0, a=0x7fced4cb8f88, msg=msg@entry=0x7fced4f093c8) at action.c:1549 #12 0x000000000042bcf2 in do_action (h=h@entry=0x7ffeb0b402b0, a=a@entry=0x7fced4cb91e8, msg=msg@entry=0x7fced4f093c8) at action.c:1049 #13 0x000000000042a10a in run_actions (h=h@entry=0x7ffeb0b402b0, a=0x7fced4cb3f48, msg=msg@entry=0x7fced4f093c8) at action.c:1549 #14 0x000000000042bde0 in do_action (h=h@entry=0x7ffeb0b402b0, a=a@entry=0x7fced4ac3d70, msg=msg@entry=0x7fced4f093c8) at action.c:678 #15 0x000000000042a10a in run_actions (h=h@entry=0x7ffeb0b402b0, a=a@entry=0x7fced4ac1698, msg=msg@entry=0x7fced4f093c8) at action.c:1549 #16 0x00000000004375d0 in run_top_route (a=0x7fced4ac1698, msg=msg@entry=0x7fced4f093c8, c=c@entry=0x0) at action.c:1635 #17 0x0000000000504386 in receive_msg (buf=<optimized out>, len=<optimized out>, rcv_info=<optimized out>) at receive.c:240 #18 0x00000000005f5bd4 in udp_rcv_loop () at udp_server.c:495 #19 0x00000000004b2625 in main_loop () at main.c:1600 #20 0x0000000000427e2b in main (argc=<optimized out>, argv=<optimized out>) at main.c:2616 And from syslog the relevant messages before this dump: Jul 15 08:55:03 server /usr/sbin/kamailio[16470]: WARNING: dialog [dlg_handlers.c:1219]: dlg_onroute(): unable to find dialog for BYE with route param 'd4c.26d1' [3149:7522] Jul 15 08:56:01 server /usr/sbin/kamailio[16481]: WARNING: dialog [dlg_handlers.c:1219]: dlg_onroute(): unable to find dialog for BYE with route param 'fc.99f1' [207:8089] Jul 15 08:56:27 server /usr/sbin/kamailio[16470]: CRITICAL: dialog [dlg_timer.c:200]: update_dlg_timer(): Trying to update a bogus dlg tl=0x7fceb3f7d920 tl->next=(nil) tl->prev=(nil) Jul 15 08:56:27 server /usr/sbin/kamailio[16470]: ERROR: dialog [dlg_handlers.c:1377]: dlg_onroute(): failed to update dialog lifetime Jul 15 08:57:01 server /usr/sbin/kamailio[16482]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Duplicate entry '9584-3854-435' for key 'hash_index' (1062) Jul 15 08:57:01 server /usr/sbin/kamailio[16482]: ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query Jul 15 08:57:01 server /usr/sbin/kamailio[16482]: ERROR: sqlops [sql_api.c:265]: sql_do_query(): cannot do the query [INSERT INTO `dialog_extra` (`h_i] Jul 15 08:57:01 server /usr/sbin/kamailio[16482]: ERROR: auth [api.c:119]: auth_check_hdr_md5(): auth:pre_auth: Credentials are not filled properly Jul 15 08:57:01 server /usr/sbin/kamailio[16483]: ERROR: auth [api.c:119]: auth_check_hdr_md5(): auth:pre_auth: Credentials are not filled properly Jul 15 08:57:54 server /usr/sbin/kamailio[16506]: NOTICE: dialog [dlg_hash.c:245]: dlg_clean_run(): dialog in delete state is too old (0x7fceb3f64470 ref 4) Jul 15 08:57:54 server /usr/sbin/kamailio[16473]: WARNING: dialog [dlg_handlers.c:1348]: dlg_onroute(): inconsitent dlg timer data on dlg 0x7fceb3f64470 [1182:5803] with clid '09ad128753e2535d24bde58e3d7eda04@192.168.10.232:5060' and tags 'as1b497b34' '5788890C-EC6F55F-3E86ED0C' Jul 15 08:57:54 server /usr/sbin/kamailio[16469]: ERROR: dialog [dlg_handlers.c:334]: dlg_terminated_confirmed(): failed to get dialog from params! Jul 15 08:58:49 server /usr/sbin/kamailio[16467]: WARNING: dialog [dlg_handlers.c:1219]: dlg_onroute(): unable to find dialog for BYE with route param '6d2.2581' [726:6226] Jul 15 08:59:24 server /usr/sbin/kamailio[16506]: NOTICE: dialog [dlg_hash.c:245]: dlg_clean_run(): dialog in delete state is too old (0x7fceb400e2f0 ref 4) Jul 15 08:59:25 server /usr/sbin/kamailio[16464]: WARNING: dialog [dlg_handlers.c:1219]: dlg_onroute(): unable to find dialog for BYE with route param '3e4.b5c1' [1251:7259] Jul 15 08:59:25 server /usr/sbin/kamailio[16465]: WARNING: dialog [dlg_handlers.c:1348]: dlg_onroute(): inconsitent dlg timer data on dlg 0x7fceb400e2f0 [1251:7259] with clid '87791a#015#012Call-ID: 25750e286a5654361ef9405d72edbc' and tags '' 'as148f41b1' Jul 15 08:59:25 server kernel: [203670.830521] kamailio[16465] general protection ip:7fcead34b3a5 sp:7ffeb0b3e220 error:0 in dialog.so[7fcead330000+88000] Jul 15 08:59:26 server /usr/sbin/kamailio[16511]: CRITICAL: <core> [pass_fd.c:275]: receive_fd(): EOF on 33 Jul 15 08:59:26 server /usr/sbin/kamailio[16458]: ALERT: <core> [main.c:739]: handle_sigs(): child process 16465 exited by a signal 11 Jul 15 08:59:26 server /usr/sbin/kamailio[16458]: ALERT: <core> [main.c:742]: handle_sigs(): core was generated Jul 15 08:59:26 server /usr/sbin/kamailio[16458]: INFO: <core> [main.c:754]: handle_sigs(): terminating due to SIGCHLD Any insight would be appreciated! Cheers, Dirk

2 12

CANCEL message within transaction not being relayed
by Ali Soltani 26 Jul '16

26 Jul '16

Hi, We tested the following on Kamailio 3.x and 4.x and observed the same behavior. INVITE and CANCEL are sent to Kamailo from the same source within the same transaction. (branch value in the first via header are the same in both INVITE and CANCEL message. Also FROM and TO header are same as well). However, Kamailio does not relay CANCEL message. UAC keep sending CANCEL till timeout. Apparently, t_check_trans() returns false. Can anyone help me on this issue on why Kamailio does not relay CANCEL message? Thanks, AS INVITE received by Kamailio INVITE sip:1111111@10.10.10.10:5060;user=phone SIP/2.0 Via: SIP/2.0/UDP 20.20.20.20:5060;branch=z9hG4bKkjhg4n100gagvkoup741.1 Max-Forwards: 69 From: <sip:2222222@20.20.20.20>;tag=SDl9eu701-1c1026774897 To: <sip:1111111@10.10.10.10;user=phone> Call-ID: SDl9eu701-36d75c874d3f463f6c83c5c94cc98b77-8q7ug02 CSeq: 1 INVITE Contact: <sip:2222222@20.20.20.20:5060;transport=udp> Supported: em,timer,replaces,path,resource-priority,sdp-anat Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUBSCRIBE,UPDATE User-Agent: CS-CustomerName/v.6.60A.274 Content-Type: application/sdp Content-Length: 237 P-Asserted-Identity: tel:2222222 P-Asserted-Identity: sip:2222222@192.168.0.1 after 70 msec CANCEL received by Kamailio in the same transaction CANCEL sip:1111111@10.10.10.10:5060;user=phone SIP/2.0 Via: SIP/2.0/UDP 20.20.20.20:5060;branch=z9hG4bKkjhg4n100gagvkoup741.1 CSeq: 1 CANCEL Max-Forwards: 69 From: <sip:2222222@20.20.20.20>;tag=SDl9eu701-1c1026774897 To: <sip:1111111@10.10.10.10.;user=phone> Call-ID: SDl9eu701-36d75c874d3f463f6c83c5c94cc98b77-8q7ug02 Content-Length: 0 Reason: Q.850 ;cause=16

2 1

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