- sr-users - kamailio.org

Anybody in Beijing interested in Kamailio related project cooperation ?
by Thierry Luo 29 Sep '15

29 Sep '15

很报歉通过这个邮件列表打扰大家。我们是一个创业团队，刚刚拿到投资，正在组建核心团队，现需要一位在OpenIMSCore （或Kamailio/OpenSIPS）方面有经验的C/C++开发工程师加盟，待遇优厚，期权可谈，职位在北京。请有意者速与 luoyongheng(a)nane.cn <mailto:luoyongheng@nane.cn> 联系。谢谢！打扰见谅！罗

1 0

Best practices for troubleshooting deadlocks?
by Alex Balashov 29 Sep '15

29 Sep '15

Hello, Very occasionally, we encounter what appear to be deadlocks in all UDP receiver threads. All Kamailio processes are running, but no SIP messages are being processed. On one of our high-volume installation, this happens extremely infrequently -- maybe once every month or two. On these occasions, the operator restarts the proxy before we get a chance to go in and figure out what's going on. So, I'm trying to provide the operator with a procedure to execute prior to restarting the proxy on these occasions, so that we can see a snapshot of where the receiver threads are stuck. As far as I can tell, unless Kamailio itself segfaults, there's no specific PID that one can attach GDB to in order to get an overhead snapshot of all the child processes. Here's what I came up with: --------------------------------------------- #!/bin/bash kamcmd -s /tmp/kamailio_ctl ps > thread_log.txt echo >> thread_log.txt while read PID; do gdb --pid=$PID<<EOF>>thread_log.txt set print elements 0 thread apply all bt full generate-core-file detach EOF done < <(kamcmd -s /tmp/kamailio_ctl ps | grep 'udp receiver' | awk '{print $1}') --------------------------------------------- As far as I can tell, this should give me the most ample visibility into the state of the threads, with further core dumps to inspect if follow-up is needed. Hopefully this will result in some fixes back to the project. However, if there are any other suggestions for information to grab in such a scenario, I'm all ears. Thanks in advance! -- Alex -- Alex Balashov | Principal | Evariste Systems LLC 303 Perimeter Center North, Suite 300 Atlanta, GA 30346 United States Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

3 5

Kazoo db_url required?
by Asgaroth 29 Sep '15

29 Sep '15

Hi, I am doing some tests with the kazoo module, I only want to use it for some amqp related tasks. In our particular case, we do not require kazoo to hook into the presence tables, however, if I do *not* set the db_url parameter for kazoo, then kamailio fails to start with the following error: /usr/sbin/kamailio[11557]: CRITICAL: kazoo [kazoo.c:361]: mod_child_init(): child_init: database not bound /usr/sbin/kamailio[11557]: ERROR: <core> [sr_module.c:900]: init_mod_child(): Error while initializing module kazoo (/usr/lib64/kamailio/modules/kazoo.so) Is it possible to run the kazoo module without specifying the db_url parameter, we only need it for sending/recieving amqp messages. Additionally, I noticed that the amqp_connection parameter has a max limit of 50 characters, is it possible to increase this at all? I had a case where my url was 64 characters long and kazoo would fail with max character limit exceeded for the module parameter. Any tips much appreciated. Thanks

1 2

Kamailio recvfrom out of bounds
by José Seabra 28 Sep '15

28 Sep '15

I have one kamailio server listening in 2 network interfaces, kamailio receives sip messages from interface A and then send it to destine through interface B. When we start kamailio service then run gdb for each kamailio network interface process, execute the command "bt full" the result is the following: *tmp = 0x5f801b994c4715bd <Address 0x5f801b994c4715bd out of bounds>* interface - A bt full #0 0x00007fb01bfa40c3 in recvfrom () from /lib64/libc.so.6 No symbol table info available. #1 0x000000000047f2ba in udp_rcv_loop () at udp_server.c:421 len = 13 buf = '\000' <repeats 65535 times> tmp = 0x5f801b994c4715bd <Address 0x5f801b994c4715bd out of bounds> from = 0x7faf9bf38bb8 fromlen = 16 ri = {src_ip = {af = 2309178400, len = 32765, u = {addrl = {5458819, 4284160}, addr32 = {5458819, 0, 4284160, 0}, addr16 = {19331, 83, 0, 0, 24320, 65, 0, 0}, addr = "\203KS\000\000\000\000\000\000_A\000\000\000\000"}}, dst_ip = {af = 2, len = 4, u = {addrl = {80026686, 0}, addr32 = {80026686, 0, 0, 0}, addr16 = {7230, 1221, 0, 0, 0, 0, 0, 0}, addr = ">\034\305\004", '\000' <repeats 11 times>}}, src_port = 55576, dst_port = 5060, proto_reserved1 = 0, proto_reserved2 = 0, src_su = {s = {sa_family = 32687, sa_data = "\000\000\200D\243\211\375\177\000\000\213\337D"}, sin = {sin_family = 32687, sin_port = 0, sin_addr = {s_addr = 2309178496}, sin_zero = "\375\177\000\000\213\337D"}, sin6 = {sin6_family = 32687, sin6_port = 0, sin6_flowinfo = 2309178496, sin6_addr = {__in6_u = {__u6_addr8 = "\375\177\000\000\213\337D\000\000\000\000\000p", <incomplete sequence \372\233>, __u6_addr16 = {32765, 0, 57227, 68, 0, 0, 21616, 39930}, __u6_addr32 = {32765, 4513675, 0, 2616874096}}}, sin6_scope_id = 32687}}, bind_address = 0x7faf9becd7d8, proto = 1 '\001'} __FUNCTION__ = "udp_rcv_loop" #2 0x0000000000525eae in main_loop () at main.c:1573 i = 0 pid = 0 si = 0x7faf9becd7d8 si_desc = "udp receiver child=0 sock=62.28.197.4:5060 \000\000\000\000\000\000\001\000\000\000\000\000\000\000\260\244r\023n\000\000\000\071\263q\000\000\000\000\000\020\243q\000\000\000\000\000\b\000\000\000\001\000\000\000\260\373\371\233\257\177\000\000\220E\243\211\375\177\000\000|\351O\000\000\000\000\000\000\266\253\023\257\177\000\000\260\244r\023\257\177\000" ---Type <return> to continue, or q <return> to quit--- nrprocs = 32 __FUNCTION__ = "main_loop" #3 0x000000000052c395 in main (argc=11, argv=0x7ffd89a34848) at main.c:2533 cfg_stream = 0x2296010 c = -1 r = 0 tmp = 0x7ffd89a35f61 "" tmp_len = 0 port = 0 proto = 32688 options = 0x725010 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:" ret = -1 seed = 1641321572 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x7ffd89a34710 p = 0x7fb01bf4c646 <intel_check_word+166> "H\205\300t\025\017\266P\003\017\266\312D9\371\017\204", <incomplete sequence \305> __FUNCTION__ = "main" interface B bt full #0 0x00007fb01bfa40c3 in recvfrom () from /lib64/libc.so.6 No symbol table info available. #1 0x000000000047f2ba in udp_rcv_loop () at udp_server.c:421 len = 45 buf = '\000' <repeats 65535 times> tmp = 0x13cb2f24296000e9 <Address 0x13cb2f24296000e9 out of bounds> from = 0x7faf9bf38bb8 fromlen = 16 ri = {src_ip = {af = 2309178400, len = 32765, u = {addrl = {5458819, 4284160}, addr32 = {5458819, 0, 4284160, 0}, addr16 = {19331, 83, 0, 0, 24320, 65, 0, 0}, addr = "\203KS\000\000\000\000\000\000_A\000\000\000\000"}}, dst_ip = {af = 2, len = 4, u = {addrl = {2764381246, 0}, addr32 = {2764381246, 0, 0, 0}, addr16 = {7230, 42181, 0, 0, 0, 0, 0, 0}, addr = ">\034Ť", '\000' <repeats 11 times>}}, src_port = 56136, dst_port = 5060, proto_reserved1 = 0, proto_reserved2 = 0, src_su = {s = {sa_family = 32687, sa_data = "\000\000\200D\243\211\375\177\000\000\213\337D"}, sin = {sin_family = 32687, sin_port = 0, sin_addr = {s_addr = 2309178496}, sin_zero = "\375\177\000\000\213\337D"}, sin6 = {sin6_family = 32687, sin6_port = 0, sin6_flowinfo = 2309178496, sin6_addr = {__in6_u = { __u6_addr8 = "\375\177\000\000\213\337D\000\000\000\000\000p", <incomplete sequence \372\233>, __u6_addr16 = {32765, 0, 57227, 68, 0, 0, 21616, 39930}, __u6_addr32 = {32765, 4513675, 0, 2616874096}}}, sin6_scope_id = 32687}}, bind_address = 0x7faf9becda08, proto = 1 '\001'} __FUNCTION__ = "udp_rcv_loop" #2 0x0000000000525eae in main_loop () at main.c:1573 ---Type <return> to continue, or q <return> to quit--- i = 0 pid = 0 si = 0x7faf9becda08 si_desc = "udp receiver child=0 sock=62.28.197.164:5060 \000\000\000\000\001\000\000\000\000\000\000\000\260\244r\023n\000\000\000\071\263q\000\000\000\000\000\020\243q\000\000\000\000\000\b\000\000\000\001\000\000\000\260\373\371\233\257\177\000\000\220E\243\211\375\177\000\000|\351O\000\000\000\000\000\000\266\253\023\257\177\000\000\260\244r\023\257\177\000" nrprocs = 32 __FUNCTION__ = "main_loop" #3 0x000000000052c395 in main (argc=11, argv=0x7ffd89a34848) at main.c:2533 cfg_stream = 0x2296010 c = -1 r = 0 tmp = 0x7ffd89a35f61 "" tmp_len = 0 port = 0 proto = 32688 options = 0x725010 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:" ---Type <return> to continue, or q <return> to quit--- ret = -1 seed = 1641321572 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x7ffd89a34710 p = 0x7fb01bf4c646 <intel_check_word+166> "H\205\300t\025\017\266P\003\017\266\312D9\371\017\204", <incomplete sequence \305> __FUNCTION__ = "main" [root@c4-srv1 kamailio]# kamctl stats shmem shmem:fragments = 2552 shmem:free_size = 2082764040 shmem:max_used_size = 66449600 shmem:real_used_size = 64719608 shmem:total_size = 2147483648 shmem:used_size = 54355992 Can anyone explain the meaning of *tmp = 0x5f801b994c4715bd <Address 0x5f801b994c4715bd out of bounds>* Best Regards José Seabra

2 6

Kamailio with Radius authentication
by Ciolpan Ionut-Marian 28 Sep '15

28 Sep '15

Hi, I want to implement Kamailio with Radius authentication. To be more exactly I want to register SIP users (PhonerLite and/or Jitsi) based on the credentials stored in radcheck table from radius database. First of all, I have tried to register SIP users based on the credentials stored in users file from /etc/raddb directory. In order to do this,I am using auth_radius module (you can find the content of my kamailio.cfg file in the attachements) but without success. All of the SIP users are registeres successfully even if they are not specified in users file. Can you provide me some help to achieve this task? and also, can you explain to me how should I do this authentication based on the credentials stored in radcheck table? The content of users file in /etc/raddb: usertest@mydomain_name Auth-Type := Digest, User-Password == "*89Lob?p" Reply-Message = "Authenticated" Thank you for any help you can provide ! Best regards PS: kamailio 4.0.5 freeradius 2.2.0 radclient 2.2.0 PPS: I managed to register SIP users based on the credentials stored in subscriber table from kamailio db.

2 10

Releasing Kamailio v4.3.3
by Daniel-Constantin Mierla 28 Sep '15

28 Sep '15

Hello, I am considering to release Kamailio v4.3.3 by end of this week, most likely of Friday, Oct 2. As usual, announce any issues that you are aware and not reported to sr-dev or bug tracker. Also, if some patch was no backported and you think it has to be, write to sr-dev mailing list. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com

1 0

GeoIP and multiple rtp
by Infinicalls Infinicalls 28 Sep '15

28 Sep '15

Hi, I have installed Kamailio in one instance and want to have multiple RTP instances for geo loadbalancing. I can understand that rtp_cluster will do that based on number of parameters, but geo_IP is missing. Can somebody tell me how do I go about with it? Is it possible to get with Kamailio's geoip module and "instruct" rtp? regards Ganesh Kumar

3 2

passing multiple values in mqueue
by Thibault Gueslin 28 Sep '15

28 Sep '15

I want to pass several arguments to a mqueue to process them asynchronously. (like in the example of sip sweet). How could it be done ? Other possibility is to generate a string and parse it in the lua script. But there should something more simple ? thibault

2 1

MSRP over Websockets
by vamsi 25 Sep '15

25 Sep '15

Hi, I am trying to configure MSRP over websocket and using Crocodilr-msrp client for connecting the same but when I try to transfer any file it gives me the below error. Any thoughts is appreciated. I am able to do audio, vedio and messaging using SIP-JSSIP client and working fine. Error - Log -------------- Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: tls [tls_server.c:208]: tls_complete_init(): Using initial TLS domain TLSc<default> (dom 0x7f35500d4858 ctx 0x7f355013d620 sn []) Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: tls [tls_domain.c:701]: sr_ssl_ctx_info_callback(): SSL handshake started Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: ERROR: <core> [tcp_main.c:2654]: tcpconn_1st_send(): connect 10.205.64.24:8084 failed (RST) Connection refused Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: ERROR: <core> [tcp_main.c:2664]: tcpconn_1st_send(): 10.205.64.24:8084: connect & send for 0x7f35501bca20 failed: Connection refused (111) Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: <core> [tcp_main.c:2858]: tcpconn_chld_put(): destroying connection 0x7f35501bca20 (24, -1) flags 0060 Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: ERROR: msrp [msrp_netio.c:178]: msrp_relay(): forwarding frame failed Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: exec: *** cfgtrace:request_route=[DEFAULT_EVENT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=1202 a=2 n=exit Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: <core> [tcp_read.c:1153]: ws_process_msg(): WebSocket Message: [[>>>#012??#011?i#036'?$Mu?Ik#022?#001,I?#005>t?'Z*?=q#012?#010jO?IsT?#031m#035?F/#027?[.#022?_*#011?]$#037?Q*#010?G/#027?\&#011?G+#021?]*#020?^*#034?#012n#007?#032lW?S1#010?Y0#025?\0#021?G,#023?Q.#037?Fm#011?Y*#022?G)#011?P)#021?\(#021?RjD?IsT?#031$#010?<<<]] Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: websocket [ws_conn.c:429]: wsconn_get(): wsconn_get for id [22] Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: websocket [ws_conn.c:437]: wsconn_get(): wsconn_get returns wsc [0x7f3550140930] refcnt [2] Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: websocket [ws_frame.c:415]: decode_and_validate_ws_frame(): decoding WebSocket frame Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: websocket [ws_frame.c:456]: decode_and_validate_ws_frame(): supported non-control frame: 0x2 Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: websocket [ws_frame.c:555]: decode_and_validate_ws_frame(): Rx (decoded): MSRP u5xh2ntl SEND#015#012To-Path: msrps:// 10.205.64.24:8084/s.10458.4.561447274;tcp msrps:// 10.205.64.24:8084/s.10453.7.297645663;tcp msrp://i64fn3tc.invalid:2855/g14o60krz6;ws#015#012From-Path: msrp://grtsrfd0.invalid:2855/505z40k5b1;ws#015#012Message-ID: 3652053096.cr4l1e1q#015#012Success-Report: yes#015#012Failure-Report: yes#015#012Byte-Range: 2049-4096/68240#015#012Content-Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document#015#012#015#012 Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: websocket [ws_frame.c:671]: ws_frame_receive(): Rx MSRP frame:#012MSRP u5xh2ntl SEND#015#012To-Path: msrps://10.205.64.24:8084/s.10458.4.561447274;tcp msrps://10.205.64.24:8084/s.10453.7.297645663;tcp msrp://i64fn3tc.invalid:2855/g14o60krz6;ws#015#012From-Path: msrp://grtsrfd0.invalid:2855/505z40k5b1;ws#015#012Message-ID: 3652053096.cr4l1e1q#015#012Success-Report: yes#015#012Failure-Report: yes#015#012Byte-Range: 2049-4096/68240#015#012Content-Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document#015#012#015#012 Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f3550140930] refcnt [2] Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f3550140930] refcnt [1] Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: msrp [msrp_parser.c:171]: msrp_parse_fline(): MSRP FLine: [1] [MSRP] [u5xh2ntl] [SEND] [1] [] Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: msrp [msrp_parser.c:327]: msrp_parse_headers(): MSRP Header: (0x7f3558c0d1b8) [To-Path] [2] [msrps://10.205.64.24:8084/s.10458.4.561447274;tcp msrps:// 10.205.64.24:8084/s.10453.7.297645663;tcp msrp://i64fn3tc.invalid:2855/g14o60krz6;ws] Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: msrp [msrp_parser.c:327]: msrp_parse_headers(): MSRP Header: (0x7f3558c0c918) [From-Path] [1] [msrp://grtsrfd0.invalid:2855/505z40k5b1;ws] Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: msrp [msrp_parser.c:327]: msrp_parse_headers(): MSRP Header: (0x7f3558c0ed80) [Message-ID] [4] [3652053096.cr4l1e1q] Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: msrp [msrp_parser.c:327]: msrp_parse_headers(): MSRP Header: (0x7f3558c0ee10) [Success-Report] [7] [yes] Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: msrp [msrp_parser.c:327]: msrp_parse_headers(): MSRP Header: (0x7f3558c1a868) [Failure-Report] [0] [yes] Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: msrp [msrp_parser.c:327]: msrp_parse_headers(): MSRP Header: (0x7f3558c0c9a8) [Byte-Range] [5] [2049-4096/68240] Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: msrp [msrp_parser.c:327]: msrp_parse_headers(): MSRP Header: (0x7f3558c107d8) [Content-Type] [8] [application/vnd.openxmlformats-officedocument.wordprocessingml.document] Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: msrp [msrp_parser.c:356]: msrp_parse_headers(): MSRP Body: [2050] [[#012#012]] Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: msrp [msrp_mod.c:468]: msrp_frame_received(): executing event_route[msrp:frame-in] (3) Sep 23 23:11:36 ip-10-205-64-24 kamailio[10460]: DEBUG: <core> [parser/msg_par *********** Kamailio.cfg **************** #!ifdef WITH_MSRP event_route[msrp:frame-in] { msrp_reply_flags("1"); if ((($Rp == MY_WS_PORT || $Rp == MY_WSS_PORT) && !(proto == WS || proto == WSS)) && $Rp != MY_MSRP_PORT) { xlog("L_WARN", "MSRP request received on $Rp\n"); msrp_reply("403", "Action-not-allowed"); exit; } if (msrp_is_reply()) { msrp_relay(); } else if($msrp(method)=="AUTH") { if($msrp(nexthops)>0) { msrp_relay(); exit; } if (!www_authenticate("MY_DOMAIN", "subscriber", "$msrp(method)")) { if (auth_get_www_authenticate("MY_DOMAIN", "1", "$var(wauth)")) { msrp_reply("401", "Unauthorized", "$var(wauth)"); } else { msrp_reply("500", "Server Error"); } exit; } if ($hdr(Expires) != $null) { $var(expires) = (int) $hdr(Expires); if ($var(expires) < MSRP_MIN_EXPIRES) { msrp_reply("423", "Interval Out-of-Bounds", "Min-Expires: MSRP_MIN_EXPIRES\r\n"); exit; } else if ($var(expires) > MSRP_MAX_EXPIRES) { msrp_reply("423", "Interval Out-of-Bounds", "Max-Expires: MSRP_MAX_EXPIRES\r\n"); exit; } } else { $var(expires) = MSRP_MAX_EXPIRES; } $var(cnt) = $var(cnt) + 1; pv_printf("$var(sessid)", "s.$(pp).$(var(cnt)).$(RANDOM)"); $sht(msrp=>$var(sessid)::srcaddr) = $msrp(srcaddr); $sht(msrp=>$var(sessid)::srcsock) = $msrp(srcsock); $shtex(msrp=>$var(sessid)) = $var(expires) + 5; # - Use-Path: the MSRP address for server + session id $var(hdrs) = "Use-Path: msrps://MY_IP_ADDR:MY_MSRP_PORT/" + $var(sessid) + ";tcp\r\n" + "Expires: " + $var(expires) + "\r\n"; msrp_reply("200", "OK", "$var(hdrs)"); } else if ($msrp(method)=="SEND" || $msrp(method)=="REPORT") { if ($msrp(nexthops)>1) { if ($msrp(method)!="REPORT") { msrp_reply("200", "OK"); } msrp_relay(); exit; } $var(sessid) = $msrp(sessid); if ($sht(msrp=>$var(sessid)::srcaddr) == $null) { # one more hop, but we don't have address in htable msrp_reply("481", "Session-does-not-exist"); exit; } else if ($msrp(method)!="REPORT") { msrp_reply("200", "OK"); } msrp_relay_flags("1"); msrp_set_dst("$sht(msrp=>$var(sessid)::srcaddr)", "$sht(msrp=>$var(sessid)::srcsock)"); msrp_relay(); } else { msrp_reply("501", "Request-method-not-understood"); } } Thanks, Vamsi

2 3

Kamailio & VoLTE (powered by ng-voice) at ITU Telecom World in Budapest 2015
by Carsten Bock 25 Sep '15

25 Sep '15

Hi Everyone, We will have our own small LTE (and VoLTE enabled) network at the ITU Telecom World 2015 in Budapest. Since we are on the exhibitor list, we are pleased to share a complimentary Exhibition Visitor pass for you to visit our booth there (no. P07 in Hall F). Register at http://telecomworld.itu.int/take-part/attend/ following the guidelines, embedding the promotional code C-00001092 when prompted. Thanks, Carsten -- 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 5247593-0 Fax +49 40 5247593-99 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/

1 0

RPC ul.dump
by Loïc Boissy 25 Sep '15

25 Sep '15

Hello, As mentionned in the doc, ul.dump command dumps the content of the location table. I use MULTIDOMAIN domain configuration, and i would like to use a RPC command to recover all contact present in my database (for all domains). Is there a solution to do that? Thanks you for you help. Loic BOISSY -- Visit Digigram at IBC2015 at Stand 8.C51, Sept. 11-15 in Amsterdam Register here <http://www.ibc.org/page.cfm/link=478> for your *FREE* pass with Digigram's Exhibitor Customer Code *4462*

3 5

Kamailio Asterisk MWI
by Ansuman Manna - Asergis Telecom 25 Sep '15

25 Sep '15

Hi, I am working on MWI (message waiting indication). I am using Kamailio as SIP registrar, Asterisk is for call routing. I can send notify to Kamailio from my VM server but thing is Kamailio is not handling the notify. If you have some suggestion about this. Regards, Ansuman Manna Software Developer Asergis Telecom Services Private Limited Office Tel: +91 11 6606 8400 Office Fax: +91 112554 5156 http://www.asergis.in <http://www.asergis.in>

3 3

Ragarding reginfo handling in kamailio
by Ram Anji 25 Sep '15

25 Sep '15

Hi, I am facing issue with reginfo handling in kamailio, I am getting proper notify when user is registered and deregistered properly. But i am not getting same when user's registration is expired[with out refresh/ when entry is removed from location], Can anyone suggest me how can i achieve this. I am using 4.3.1 kamailio Regards, Raman

2 1

OpenSev -> Kamailio Migration?
by Matthew Harris 25 Sep '15

25 Sep '15

Hello everyone! I am new to the VOIP world and currently researching a solution to upgrading or migrating from an antiquated openser sip server to kamailio. Has anyone ever had to do this? If so: What challenges should I expect to face? Warmest regards, Matt

2 1

SIP account.
by Grendell 25 Sep '15

25 Sep '15

Hi A few says ago I registered an account user name 08031955. However I have been unable to connect using 2 different SIP phones. Can you please check if this account is active yet. Can you advise if my user name has to include ....(a)iptel.org on the end of it? many thanks Graham Rendell

2 1

regEvent feature
by Stefan Ljung 25 Sep '15

25 Sep '15

(A continuation on an old thread) In the RFC 3680 it is described how a UE can subscribe to its own registration state(s). As soon as it's own registration state changes in any way - like a refresch registration - a NOTIFY is send to the subscribing terminal. What made me hopeful was when I in the Overview's use case section for the module pua_reginfo read the line: "A client could subscribe to it's own registration-status, so he would get notified as soon as his account gets administratively unregistered." That's in line with how I would like to use it - Is it in any way possible to achieve that in the Kamailio? /Stefan From: Stefan Ljung Sent: den 18 februari 2015 09:32 To: miconda(a)gmail.com Subject: RE: [SR-Users] Event reg - questions >From the pua_regInfo module description: Use cases for this might be: Keeping different Servers in Sync regarding the location database Get notified, when a user registers: A presence-server, which handles offline message storage for an account, would get notified, when the user comes online. A client could subscribe to it's own registration-status, so he would get notified as soon as his account gets administratively unregistered. ... So it's the last line I want to deploy. Maybe Im over-interpreting "A client could subscribe to it's own registration-status" I want to be able to simulate (As close a possible) a VoLTE clients reg events handling. Only the part between to and from the UE. So no PUBLISH is needed - Kamailio needs to notify the UE about its registration status. /Stefan From: Daniel-Constantin Mierla [mailto:miconda@gmail.com] Sent: den 16 februari 2015 17:43 To: Kamailio (SER) - Users Mailing List; Stefan Ljung Subject: Re: [SR-Users] Event reg - questions Hello, afaik, the pua_reginfo is for publishing details of location records to another sip server node, main purpose being location replication. I don't think it is something for an end UA. If you want publishing online/offline states for an user based on its registration state, look at pua_usrloc module. On 12/02/15 15:17, Stefan Ljung wrote: I made a test configuration for trying the pua_regEvent module. There were two things I want to ask about. First - when the SUBSCRIBE to event 'reg' following a UEs registration to the Kamailio is responded with a NOTIFY - there was no body in the NOTIFY. I expected a XML body with registration status. Second - When the UE re-registers to Kamailio - I expected a NOTIFY to be send on the existing 'reg' subscription, but nothing happened. Or am I missing some configuration ? Here's some of the conf script: [..] modparam("pua_reginfo", "publish_reginfo", 0) Btw, with the above parameter value, the module is no longer sending PUBLISH requests, in other words, it is not informing the other peers that there is some update to location records. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com

2 1

Kamailio PSTN with User/Pass authentication
by Infinicalls Infinicalls 24 Sep '15

24 Sep '15

Hi, I am trying to add PSTN gw for terminating my calls. I have changed the IP in the kamailio.cfg file, but this provider wants digest auth and so I need to pass api/pass to them. Can somebody guide me how and where to add the username+pass to the config file. thanks regards Ganesh Kuamr

4 8

Re: [SR-Users] [Kamailio 4.2] Crash during burn-in test
by Daniel-Constantin Mierla 24 Sep '15

24 Sep '15

Hello, the first frames of the backtrace don't have the symbol table, do have other core files from where you can extract the bt full? Also, 4.2.3 is old in its series, newer versions in branch 4.2 were released. Can you update the latest version in branch 4.2 and reproduce again? That will rule out is not a side effect of an issue fixed after 4.2.3. You don't need to change anything in config or database, just grab the latest sources from branch 4.3 and install over the old binaries. Cheers, Daniel On 08/09/15 07:58, Jack Wang wrote: > Hi, > > The result of 'kamailio -v' is: > > version: kamailio 4.2.3 (arm/linux) 87ca6e-dirty > flags: STATS: Off, EXTRA_DEBUG, USE_TCP, USE_TLS, TLS_HOOKS, > USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, > SHM_MMAP, PKG_MALLOC, F_MALLOC, DBG_F_MALLOC, USE_FUTEX, > USE_PTHREAD_MUTEX, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, > USE_DST_BLACKLIST, HAVE_RESOLV_RES > MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, > BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB > poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. > id: 87ca6e -dirty > compiled on 16:15:00 Sep 4 2015 with arm-marvell-linux-gnueabi-gcc > > > It can be reproduced not only once, steps like wrote before. > > Following link is the result of `bt full` from the core file generated: > > https://gist.github.com/BroWater/dd759897f4b88672720a#file-gistfile1-txt > > FYI > > > > >Hello, > > > >can you give the exact version: kamailio -v? > > > >Also, the log message indicates that a core file was generated, sent the > >backtrace taken from gdb: > > > >gdb /path/to/kamailio /path/to/corefile > >bt full > > > >Could you reproduce the issue, or did it happen only once? > > > >Cheers, > >Daniel > > > >On 03/09/15 04:50, Jack Wang wrote: > >> > >> [Steps] > >> > >> 1. one MCU call multi-endpoints > >> 2. MCU hangup all endpoints > >> > >> repeatedly. And all through Kamailio proxy. > >> > >> [Results] > >> > >> For a while, Kamailio crashed. > >> > >> Followings are related logs: > >> > >> > >> ========================================== > >> > >> Sep 2 19:08:34 ./kamailio[3712]: : tm [t_fwd.c:1632]: > >> t_send_branch(): BUG: t_send_branch: retr. already started for > 0x41848fa0 > >> Sep 2 19:08:34 ./kamailio[3712]: ERROR: sl [sl_funcs.c:387]: > >> sl_reply_error(): ERROR: sl_reply_error used: Unfortunately error on > >> sending to next hop occurred (477/SL) > >> > >> At this point the related behavior is that Kamailio received two INFO > >> requests simultaneously. I wonder whether this is the cause. > >> And maybe it's related to the later crash? > >> > >> Sep 2 19:08:35 ./kamailio[3713]: CRITICAL: <core> [pass_fd.c:293]: > >> receive_fd(): EOF on 11 > >> Sep 2 19:08:35 ./kamailio[3703]: ALERT: <core> [main.c:784]: > >> handle_sigs(): child process 3704 exited by a signal 11 > >> Sep 2 19:08:35 ./kamailio[3703]: ALERT: <core> [main.c:787]: > >> handle_sigs(): core was generated > >> Sep 2 19:08:35 ./kamailio[3703]: : <core> [mem/f_malloc.c:586]: > >> fm_free(): BUG: fm_free: bad pointer 0x7239b6c4 (out of memory > >> block!), called from tm: h_table.c: free_cell(157) - aborting > >> > >> > >> Any suggestions? > >> > >> Thanks. > >> > >> ========================================== > >> > >> > >> _______________________________________________ > >> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > >> sr-users at lists.sip-router.org <http://lists.sip-router.org> > >> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com Kamailio Advanced Training, Sep 28-30, 2015, in Berlin - http://asipto.com/u/kat

2 2

Re: [SR-Users] load 2 500 000 rows from dialplan
by Никитенко Виталий 24 Sep '15

24 Sep '15

>Hello > > >On 24/09/15 11:06, Никитенко Виталий wrote: >> Hi! >> I have kamailio-4.2.3. And in table dialplan there is 2 500 000 rows. When i started kamailio i see error >> >> ERROR: dialplan [dp_repl.c:74]: repl_exp_parse(): out of shm memory >> ERROR: dialplan [dp_db.c:393]: build_rule(): failed to compile replacing expression >> ERROR: dialplan [dp_db.c:111]: init_db_data(): failed to load database data >> ERROR: dialplan [dialplan.c:188]: mod_init(): could not initialize data >> ERROR: <core> [sr_module.c:968]: init_mod(): Error while initializing module dialplan (/usr/local/lib64/kamailio/modules/dialplan.so) >> >> then i set modparam("dialplan", "fetch_rows", 2500000) and started kamailio i see >> >> ERROR: db_mysql [km_dbase.c:422]: db_mysql_fetch_result(): no memory left >> ERROR: dialplan [dp_db.c:231]: dp_load_db(): failed to fetch >> ERROR: dialplan [dp_db.c:111]: init_db_data(): failed to load database data >> ERROR: dialplan [dialplan.c:188]: mod_init(): could not initialize data >> ERROR: <core> [sr_module.c:968]: init_mod(): Error while initializing module dialplan (/usr/local/lib64/kamailio/modules/dialplan.so) >> >> Please say me how i can load to memory 2500000 rows dialplan? >/usr/local/kamailio/sbin/kamailio -h | grep '\-[mM]' > -m nr Size of shared memory allocated in Megabytes > -M nr Size of private memory allocated, in Megabytes > >In you particular case, you need more shared memory (-M). > >Regards Thanks, it works!

1 0

load 2 500 000 rows from dialplan
by Никитенко Виталий 24 Sep '15

24 Sep '15

Hi! I have kamailio-4.2.3. And in table dialplan there is 2 500 000 rows. When i started kamailio i see error ERROR: dialplan [dp_repl.c:74]: repl_exp_parse(): out of shm memory ERROR: dialplan [dp_db.c:393]: build_rule(): failed to compile replacing expression ERROR: dialplan [dp_db.c:111]: init_db_data(): failed to load database data ERROR: dialplan [dialplan.c:188]: mod_init(): could not initialize data ERROR: <core> [sr_module.c:968]: init_mod(): Error while initializing module dialplan (/usr/local/lib64/kamailio/modules/dialplan.so) then i set modparam("dialplan", "fetch_rows", 2500000) and started kamailio i see ERROR: db_mysql [km_dbase.c:422]: db_mysql_fetch_result(): no memory left ERROR: dialplan [dp_db.c:231]: dp_load_db(): failed to fetch ERROR: dialplan [dp_db.c:111]: init_db_data(): failed to load database data ERROR: dialplan [dialplan.c:188]: mod_init(): could not initialize data ERROR: <core> [sr_module.c:968]: init_mod(): Error while initializing module dialplan (/usr/local/lib64/kamailio/modules/dialplan.so) Please say me how i can load to memory 2500000 rows dialplan?

2 1

JSONRPC commands
by Loïc Boissy 23 Sep '15

23 Sep '15

Hello I am trying to use JSONRPC-S Kamailio module to request for example the content of the location table. More generally, i would like to send RPC commands to my kamailio server using http request. For the moment, kamailio server always returns "400 bad request: corrupted packet". To send my request, i use curl. For example: curl --header 'Content-Type: application/json' --data-binary "{"id": 1, "jsonrpc": "2.0", "method": "ul.dump" }" http://XXX.XXX.XXX.XXX/RPC/ Is there specific syntax to respect? Kamailio server version is 4.3.2. Thank you in advance. Loic BOISSY -- Visit Digigram at IBC2015 at Stand 8.C51, Sept. 11-15 in Amsterdam Register here <http://www.ibc.org/page.cfm/link=478> for your *FREE* pass with Digigram's Exhibitor Customer Code *4462*

2 7

auth_radius module
by Marian Pandoranum 23 Sep '15

23 Sep '15

2 1

loose_route function select wrong next hop!
by Yasin CANER 22 Sep '15

22 Sep '15

3 4

Two suggestions
by 天 22 Sep '15

22 Sep '15

May this mailing list have a search function? This function will make us convient to find what we concern about. OpenIMSCore mailing list have this function, and I felt it Improved productivity. And the mailing list archive system seems to be operated manually. Can the mails be archived automatically? So it can be more instant to developers from asia. BR WangXinXin

2 2

What SIP stack does Kamailio or OpenIMSCore implements?
by 天 22 Sep '15

22 Sep '15

Hi, I am a rookie in SIP related area. I run into OpenIMSCore in recent days, and then I was introduced to Kamailio. Now I am wondering what SIP stack does Kamailio or OpenIMSCore implements? Or neither of them use a SIP stack? Can anybody help me on this? Thanks !

2 1

Re: [SR-Users] Question about in call both side redirection
by Андрей Ярин 22 Sep '15

22 Sep '15

sr-users-request(a)lists.sip-router.org пишет: > Hello On 04/09/15 07:57, ?????? ???? wrote: >> >Hello (sorry for my bad english) - i try to create voice record >> >service by request. User A call to user B. In call by pressing >> >combination like *55 Kamailio must redirect both sides to asterisk, >> >whitch create dynamic conference room with recording. As i understand >> >i need to use dlg_refer() from dialog module, but in log file i get: >> >Konsole output >> >Sep 4 10:45:14 voipc-node2 /usr/local/sbin/kamailio[18941]: ERROR: >> >dialog [dlg_req_within.c:85]: build_dlg_t(): no contact available >> >Sep 4 10:45:14 voipc-node2 /usr/local/sbin/kamailio[18941]: ERROR: >> >dialog [dlg_transfer.c:188]: dlg_refer_callee(): failed to create dlg_t >> > >> > >> >In script i try to refer with: >> >dlg_refer("callee","sip:100@10.10.9.209"); >> >dlg_refer("caller","sip:100@10.10.9.209"); >> > > in what context do you use the above actions? In other words, do you > execute them when you process a specific request? If yes, which one? > > Another question, how do you capture when *55 is pressed? Is dtmf sent > via sip info request? > > Cheers, > Daniel > > -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - > http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - > http://www.asipto.com Kamailio Advanced Training, Sep 28-30, 2015, in > Berlin - http://asipto.com/u/kat For now i try to use event_route[dialog:start] - i testing - can kamailio redirect both sides to external service, and will it work with event_route[dispatcher:dst-down]. If it will work, i will add SIP INFO processing for service codes -- Ярин Андрей Инженер ООО "И.С.-Телеком" 8(351)7786878 доб 113 8(351)2555724 доб 113 8(351)2555787 доб 113

2 2

carrierroute module cannot use prefix that start with +
by José Seabra 21 Sep '15

21 Sep '15

Hello there, I'm using carrierroute module to route calls based on prefix, everything was working until i tried use prefixes that start with +, kamailio core doesn't allow me use the + on carrierroute prefix, i get the following message from kamailio logs: INFO: carrierroute [cr_carrier.c:100]: add_domain_data(): adding domain 1 'main' to carrier 1 'carriers'35(17196) DEBUG: carrierroute [cr_carrier.c:101]: add_domain_data(): domain position 0 (domain_num=1, first_empty_domain=0)35(17196) INFO: carrierroute [cr_data.c:414]: get_domain_data_or_add(): added domain 1 'main' to carrier 1 'carriers'35(17196) INFO: carrierroute [cr_data.c:470]: add_route(): found carrier and domain, now adding route 35(17196) ERROR: <core> [dtrie.c:130]: dtrie_insert(): cannot insert non-numerical character 35(17196) ERROR: carrierroute [cr_domain.c:168]: add_route_to_tree(): cannot insert route flags into d-trie anyone can help in order allow use + in carrierroute prefix. Best regards José Seabra

3 4

dispatcher.list reversed by dispatch.c reindex_dests()
by Giovanni Maruzzelli 21 Sep '15

21 Sep '15

Hello, dispatcher gives me destination sets with entries in reverse order: I have installed from Kamailio deb repository packages version 4.3.2+jessie. # kamailio -V version: kamailio 4.3.2 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, DBG_F_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 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 4.9.2 I configured dispatcher: modparam("dispatcher", "use_default", 1) modparam("dispatcher", "list_file", "/etc/kamailio/dispatcher.list") modparam("dispatcher", "flags", 3) modparam("dispatcher", "dst_avp", "$avp(AVP_DST)") modparam("dispatcher", "grp_avp", "$avp(AVP_GRP)") modparam("dispatcher", "cnt_avp", "$avp(AVP_CNT)") modparam("dispatcher", "sock_avp", "$avp(AVP_SOCK)") modparam("dispatcher", "ds_ping_interval", 5) modparam("dispatcher", "ds_probing_mode", 1) I have this dispatcher.list: 1 sip:192.168.1.144:5060 2 1 sip:192.168.1.145:5060 2 1 sip:192.168.1.146:5060 2 2 sip:192.168.1.146:5060 2 2 sip:192.168.1.145:5060 2 So, I expect dispatcher to have: set 1 first two destinations in distribution via hash on callid, and third destination as failover (192.168.1.146 <http://192.168.1.146:5060>) . set 2 all traffic on first destination, and if first fails, all traffic will failover to second destination (192.168.1.145 <http://192.168.1.146:5060>). Instead reindex_dests shuffle the sets upside down: DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [1/1] <sip: 192.168.1.144:5060> DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [1/2] <sip: 192.168.1.145:5060> DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [1/3] <sip: 192.168.1.146:5060> DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [2/1] <sip: 192.168.1.146:5060> DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [2/2] <sip: 192.168.1.145:5060> DEBUG: dispatcher [dispatch.c:494]: reindex_dests(): found [2] dest sets DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 2 sip: 192.168.1.145:5060 2 0 (,0,0) DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 2 sip: 192.168.1.146:5060 2 0 (,0,0) DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 1 sip: 192.168.1.146:5060 2 0 (,0,0) DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 1 sip: 192.168.1.145:5060 2 0 (,0,0) DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 1 sip: 192.168.1.144:5060 2 0 (,0,0) DEBUG: dispatcher [dispatcher.c:347]: mod_init(): loaded dispatching list So, Kamailio give me set 1 and set 2 as per post-reindex_dests, and failover is 192.168.1.144 for set 1, and 192.168.1.146 for set 2. Is this the expected behavior? Am I doing something wrong in configuration? Thank you all in advance, -giovanni Sincerely, Giovanni Maruzzelli Cell : +39-347-2665618

2 3

Compiling Kamailio for Cubie/RaspberryPi/others ARM arch from main repos
by nadie 21 Sep '15

21 Sep '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 #!/bin/bash # Compiling Kamailio for Cubie/RaspberryPi/others ARM arch from main repos: echo 'deb-src http://deb.kamailio.org/kamailio43 jessie main' > /etc/apt/sources.list.d/kamailio.list wget -O- http://deb.kamailio.org/kamailiodebkey.gpg | sudo apt-key add - dpkg --add-architecture i386 apt-get update apt-get install bison debhelper erlang-dev gcj-jdk libconfuse-dev libdb-dev libev-dev libfreeradius-client-dev libgeoip-dev libhiredis-dev libjansson-dev libjson-c-dev liblua5.1-0-dev libmemcached-dev libmono-2.0-dev libmysqlclient-dev libperl-dev libpq-dev libpurple-dev librabbitmq-dev libreadline-dev libsasl2-dev libsctp-dev libsnmp-dev libsqlite3-dev libunistring-dev libval-dev libxml2-dev python-dev unixodbc-dev uuid-dev adduser python libc6 libncurses5 libpcre3 libreadline6 libtinfo5 snmpd mkdir kamailio && cd kamailio/ apt-get -b source kamailio dpkg --remove-architecture i386 rm /etc/apt/sources.list.d/kamailio.list apt-get update dpkg -i *.deb cd .. && rm -rf kamailio/ # end :-) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJV+BKUAAoJEG5DH1ilMeeenM8P/jqzMKtxmRheDDT4pqxzo9W1 lSNpg+UhYr5CC/IXCgGXkP5Sup87/qiAVYz/u902pS9hdIBfdbup2PUsvTX4QK+1 Dybxli9ym4Fup9m6MuB+VLIjkiOOwtGnvChbnPgjJnMxDjzBbDFEmositlfAeiFU XcyIfjYDndvd2+0a1UkTVVuGBEbY6BdVkANvINy2BkZUkolstTgVr7jirYUSTEsa U9M+lX98Dbau5gfvyx87a6CkcW8fyKCgZGBYqjBIyr1TrPgtGcXdcgC77iD2pziW wkU9DIRX0sOaIiAb76hX64SL8U9b+dJr2t17PXjiEEcVWuc7YtV2R0YURAfquw9O ycSh+PWFJgc1PZx5dFZlWceDXjdffnPiWt3Fys3HuVNWLY6iVfOSFv7sMcJ4NyaT N+u81Dr4T9blZ2yRmibRUzlmSlcq4at2yKE19/AsejphXI7mnaARuNlHZUq+4RY9 EF4zlr5zTHmPhvLoh7rjzqWGLmun4g7a7mCnbMDUKKbndqb24QKhO9czvkTvYLGR vbAK56kM96jh3OBLenjl58YzK4qBbJ5sM+UCw6DA5HnF+/jh+oK4zeKL28yqEaG0 SxS/xuG4xxi2wPvGJ36Rg6gIB5cHAxizGLMEPGUPTKCPhKLFIbtunabNu2gj+6nh bpe/fyLw0ZKHF8R4tifU =Ty41 -----END PGP SIGNATURE-----

2 2

Kamailio ACK retransmission
by Yasin CANER 21 Sep '15

21 Sep '15

1 0

Kamailio - Asterisk ACK retransmission problem
by Yasin CANER 21 Sep '15

21 Sep '15

1 0

Kamailio presence shared DB_text
by Ewgeny 21 Sep '15

21 Sep '15

Hi list! We use Kamailio 4.2 for presence BLF with DB_TEXT. And i want to make cluster with a few Kamailio's presences, to load balance. Can you please tell me - is that possible to use same shared DB_TEXT database with 2 or more Kamailio servers ? modparam("presence", "subs_db_mode", 3) modparam ("presence","dburl","/tmp/share/dbtext") 1-st server will handle SUBSCRIBE's and this Subscribe's should be accessible also from 2-nd server. Then PUBLISH'es will be sent to both servers in round robin algorithm. Will Kamailio's work with one shared DB or - i'll got some errors ? Maybe i'm wrong somewhere ? Thanks in advance. Kind regards Ewgeny

2 3

Proxy-Require: privacy error
by Chad 21 Sep '15

21 Sep '15

When a call comes in with a SIP header: "Proxy-Require: privacy" line kamailio throws this error: Aug 21 14:27:57 load1 /usr/sbin/kamailio[29447]: ERROR: <core> [parser/hf.c:224]: dump_hdr_field(): DEBUG: dump_hdr_field: type=18, name=Proxy-Require, body=privacy, parsed=(nil), next=0x7efc42f15150 Aug 21 14:27:57 load1 /usr/sbin/kamailio[29446]: ERROR: <core> [parser/hf.c:224]: dump_hdr_field(): DEBUG: dump_hdr_field: type=18, name=Proxy-Require, body=privacy, parsed=(nil), next=0x7efc42f0a7b0 Aug 21 14:27:58 load1 /usr/sbin/kamailio[29447]: ERROR: <core> [parser/hf.c:224]: dump_hdr_field(): DEBUG: dump_hdr_field: type=18, name=Proxy-Require, body=privacy, parsed=(nil), next=0x7efc42f13180 Aug 21 14:27:58 load1 /usr/sbin/kamailio[29446]: ERROR: <core> [parser/hf.c:224]: dump_hdr_field(): DEBUG: dump_hdr_field: type=18, name=Proxy-Require, body=privacy, parsed=(nil), next=0x7efc42f0dfb8 Anyone know why that happens or how to fix it? -- ^C Chad

2 5

Fw: Re: Busy Tone.. Call not coming
by Mr ankush 19 Sep '15

19 Sep '15

1 0

Dialog module isn't decreasing the profile size, and isn't entering on event routes
by José Seabra 18 Sep '15

18 Sep '15

Hi there, I'm using a dialog module in a small kamailio script that only does routing based on prefix, and relay the invite from one ipaddr to another ip addr (diferent interfaces) using $fs variavel. Now i was introducing the dialog module to limit the number of concurrent calls, and i noticed that it only can increasing the number of dialogs, and it isn't decreasing when receives the "BYE", I also noticed that when kamailio receives "BYE" the dialog event route for state "end" is not executed. To count the number of concurrent calls I'm using the following logic in main route: if (is_method("INVITE")) { setflag(FLT_ACC); # do accounting dlg_manage(); if(get_profile_size("concurrentcalls","local","$avp(s:size)")) { if($avp(s:size) != $null) { xlog("L_INFO", "Number of calls for this server : $avp(s:size) - ID=$ci\n"); if($avp(s:size) >= 15000) { xlog("L_INFO", "Concurrent_max calls exceeded $avp(s:size) for caller '$fU' - R=$ru ID=$ci\n"); sl_send_reply("503", "Channel limit exceeded\n"); exit; } } } set_dlg_profile("concurrentcalls","local"); } Please check out the attachment with logs. Best Regards -- José Seabra

2 5

Issue with too many "listen" statements
by Sven Neuhaus 18 Sep '15

18 Sep '15

Hi, we've observed a bug with Kamailio (we are using 4.3.1): When using more than 81 "listen" statements, Kamailio starts acting up. In our case, it handles ACK packets (that follow "200 OK" messages) incorrectly: It forwards them to itself (src ip == dst ip) in a garbled form (on the loopback interface). We need more than 80 "listen" statements at the moment so I hope there's a way to increase the limit substantially. The number of file handles has been set to 32000 btw. Regards, -Sven Neuhaus

2 6

Adding user to kamailio database
by Priyaranjan Nayak 17 Sep '15

17 Sep '15

Hi All, I wanted to use kamailio with authorization. How can I add public identity and private identity to kamailio database for a user ? Thanks Priyaranjan

2 1

Hex to Dec conversion
by Yufei Tao 17 Sep '15

17 Sep '15

Hi Daniel, I've tested the patch on top of v4.2.5 and it works. Thank you very much! Yufei

1 0

Re: [SR-Users] Hex to Dec conversion
by Yufei Tao 17 Sep '15

17 Sep '15

Hi, Thanks for the replies! The first thing I looked at was the encode/decode.hexa transformations but it only transforms between ASCII characters and Hex numbers. Then I used exec_avp to call a bash command (for example, 'echo $((0x123))' gives you 291) which works. But calling something external may not be optimal I thought? I found OpenSIPS has hex2dec and dec2hex transformations and wonder if we could have these in Kamailio as well? Cheers, Yufei

2 1

Authentication issue during registration
by Austin Einter 17 Sep '15

17 Sep '15

Hi All I have a typical requirement, where I have a forwarding SBC between an endpoint and kamailio as shown below. Endpoint ----> SBC ------> Kamailio >From endpoint I am sending REGISTER request. It reaches SBC. SBC sends the REGISTER request to Kamailio, Kamailio challenges it (401), and challenge response is received at endpoint through SBC. Next endpoint adds authorization header and sends REGISTER to SBC, SBC forwards it to Kamailio. Now Kamailio again responds with 401. When we analysed Kamailio logs, we can see Kamailio log authorization response token and response token that was sent by Endpoint are same. So my question is, why Kamailio sends 401 repeatedly even if it received proper Authorization header. Is it because Kamailio received REGISTER from IP address different from endpoint. Please guide, how can I avoid this issue. Thanks Austin

3 4

add to wishlist: htable.dump type of value
by Juha Heinanen 16 Sep '15

16 Sep '15

looks like htable.dump does not tell what is the type of the value, e.g. { entry: 53 size: 1 slot: { item: { name: foo::bar value: 0 } } } -- juha

2 7

Next IRC Devel Meeting - Sep 16, 2015
by Daniel-Constantin Mierla 16 Sep '15

16 Sep '15

Hello, I would like to propose organizing the next IRC devel meeting to sync on the plans for Kamailio short term evolution. A wiki page has been created to keep track of what should be discussed there. Feel free to add your suggestions there: * http://www.kamailio.org/wiki/devel/irc-meetings/2015b First proposed date is next week on Wednesday, September 16, at 14:00 UTC (15:00 London, 16:00 Berlin, ...). The date can be changed based on availability of people willing to attend -- add your preferred date and time there. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com Kamailio Advanced Training, Sep 28-30, 2015, in Berlin - http://asipto.com/u/kat

1 2

OT: IIT RTC Conference discount
by Daniel-Constantin Mierla 16 Sep '15

16 Sep '15

Hello, I have some discount code for IIT RTC Conference & Expo, taking place in Chicago, IL, USA, during October 6-8, 2015. It gives an 100USD discount, which can save a bit or make some of the available tickets completely free (like Expo Plus admission). Should someone be interested, contact me directly via email. More details about the event can be found at: * http://www.rtc-conference.com/ I will be at the event during Oct 7 and 8, presenting on the morning of Oct 8, if anyone here coming to the event or happening to be in Chicago area and want to meet and chat about Kamailio, drop me an email as well. Cheers, Daniel -- Daniel-Constantin Mierla http://www.asipto.com

1 0

assign_hf_value, hf_value_exists and exclude_hf_value broken in 4.3.2?
by Björn Bylander 15 Sep '15

15 Sep '15

Hello, 4.3.1 works well for us apart from the issue fixed by 93b297e16134b0e74cf83e3604da01355a52e700. Since 93b297e16134b0e74cf83e3604da01355a52e700 is included in 4.3.2 I tried upgrading one of our servers and now Kamailio won't even start as it apparently finds the way assign_hf_value, hf_value_exists and exclude_hf_value are used in our configuration to be incorrect. I enabled debug logging (WITH_DEBUG) and found the following: > 0(1894) DEBUG: <core> [route.c:872]: fix_actions(): fixing assign_hf_value() > 0(1894) ERROR: textopsx [textopsx.c:596]: fixup_hname_param(): ERROR: textops: cannot parse header near 'Privacy' > 0(1894) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:642 > 0(1894) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:644 > 0(1894) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:661 > ERROR: error -6 while trying to fix configuration Line 642 looks like this: assign_hf_value("Privacy", "id") Commenting it out leads to the following output: > 0(2217) DEBUG: <core> [route.c:872]: fix_actions(): fixing hf_value_exists() > 0(2217) ERROR: textopsx [textopsx.c:596]: fixup_hname_param(): ERROR: textops: cannot parse header near 'Privacy' > 0(2217) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:1016 > 0(2217) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:1019 > 0(2217) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:1023 > ERROR: error -6 while trying to fix configuration Line 1016 looks like this: if (hf_value_exists("Privacy", "none")) { Commenting it out leads to the following output: > 0(2292) DEBUG: <core> [route.c:872]: fix_actions(): fixing exclude_hf_value() > 0(2292) ERROR: textopsx [textopsx.c:596]: fixup_hname_param(): ERROR: textops: cannot parse header near 'Accept' > 0(2292) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:1020 > 0(2292) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:1023 > ERROR: error -6 while trying to fix configuration Lines 1020 and 1021 look like this exclude_hf_value("Accept", "application/media_control+xml"); exclude_hf_value("Accept", "application/x-broadworks-call-center+xml"); Commenting them out makes Kamailio start without complaining. Btw, "kamailio -c" thinks the configuration file is fine. So, is our use of assign_hf_value, hf_value_exists and exclude_hf_value incorrect (looking at the textopsx documentation I can't see how) or was a bug introduced with 4.3.2 which causes this behaviour? Regards, Björn Bylander

2 1

Kamailio challenges repeatedly
by Austin Einter 15 Sep '15

15 Sep '15

I am trying to register with Kamailio server from my custom endpoint. I have below call flows Register -> 401 Register -> 401 When I saw Kamailio log, I do not see any error. Looks auth response is fine. Then why 401 repeatedly. Log is given blow. Please guide to fix this issue. Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: auth_db [authorize.c:208]: get_ha1(): HA1 string calculated: 8749f9da135d71526725a337008df1d5 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: auth [api.c:211]: auth_check_response(): check_response: Our result = '4aa70d676021329550b3d17e17238fac' Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: auth [api.c:218]: auth_check_response(): check_response: Authorization is OK Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_res.c:81]: db_free_columns(): freeing 1 columns Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_res.c:85]: db_free_columns(): freeing RES_NAMES[0] at 0x7f8a24d5e1d0 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_res.c:94]: db_free_columns(): freeing result names at 0x7f8a24d7ceb0 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_res.c:99]: db_free_columns(): freeing result types at 0x7f8a24d7cef0 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_res.c:54]: db_free_rows(): freeing 1 rows Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_row.c:97]: db_free_row(): freeing row values at 0x7f8a24d5e260 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_res.c:62]: db_free_rows(): freeing rows at 0x7f8a24d5e218 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_res.c:136]: db_free_result(): freeing result set at 0x7f8a24d7ce18 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: auth [challenge.c:127]: get_challenge_hf(): build_challenge_hf: realm='10.10.64.125' Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: auth [challenge.c:269]: get_challenge_hf(): auth: 'WWW-Authenticate: Digest realm="10.10.64.125", nonce="VfbImFX2x2yEeE8kEuL2IXqW2TgKu+eC"#015#012' Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: sl [sl.c:296]: send_reply(): reply in stateless mode (sl) Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [msg_translator.c:206]: check_via_address(): check_via_address(10.3.2.18, 10.3.2.18, 0) Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [tcp_main.c:2283]: tcpconn_send_put(): tcp_send: send from reader (2650 (9)), reusing fd Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [tcp_main.c:2518]: tcpconn_do_send(): tcp_send: sending... Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [tcp_main.c:2552]: tcpconn_do_send(): tcp_send: after real write: c= 0x7f8a1c5dbe78 n=445 fd=9 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [tcp_main.c:2553]: tcpconn_do_send(): tcp_send: buf=#012SIP/2.0 401 Unauthorized#015#012Via: SIP/2.0/TCP 10.3.2.18:6970;branch=z9hG4bK1875333638#015#012From: < sip:262099922700000@10.10.64.125;user=phone>;tag=209355482#015#012To: < sip:+499922700000@10.10.64.125;user=phone>;tag=8345fd11d20ec1ca026994bf51313cb0.a2c6#015#012Call-ID: 1340939517(a)10.10.64.125#015#012CSeq: 3 REGISTER#015#012WWW-Authenticate: Digest realm="10.10.64.125", nonce="VfbImFX2x2yEeE8kEuL2IXqW2TgKu+eC"#015#012Server: kamailio (4.2.5 (x86_64/linux))#015#012Content-Length: 0#015#012#015#012 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) Sep 14 18:41:08 necs107 kamailio[2650]: message repeated 5 times: [ DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)]

2 1

Hex to Dec conversion
by Yufei Tao 14 Sep '15

14 Sep '15

Hi, I want to convert a Hex number string into a Dec number string, e.g. Hex number "123" into Dec number "291". What is the best way? I didn't find any transformation for this. Thank you! Yufei

5 4

Very high load average after upgrade to Kamailio v4.3.2
by M S 14 Sep '15

14 Sep '15

Hi, Over last weekend i upgraded one of my test servers from Kamailio v4.3.1-4d1b65 to latest stable release v4.3.2-07690f and now kamailio goes crazy even with single call (I am using same db and configuration of course). As soon as call establishes system load average (as seen in top command) starts increasing and soon it increases beyond 6.0 and system becomes completely unresponsive, sip messages are no longer being processed by kamailio service. Even after call hangup, system remains under high load. The "htop" indicates that IO Wait time has increased substantially. Any idea what is causing this? For now i have reverted by to v4.3.1-4d1b65 but can go to v4.3.2-07690f again if you need further info or testing. Thank you.

2 6

Concurrent calls after forked invite
by Lukas Hauser 14 Sep '15

14 Sep '15

Hello, I have two UACs registered to kamailio v4.0.4 with the same URI. (bob(a)example.com) Then a third registered UAC (alice(a)example.com) sends an invite to bob(a)example.com. Both bob UACs accept the call and respond with a 200 Ok. The statefull proxy now takes the first one and cancels the second one. In my case I need both responses to be send back to alice through the proxy. I want the Invite to be forked in parallel (works) and both calls to get connected concurrently (does not work). Is there such a feature in the statefull proxy? Can this be done using a stateless proxy? I stumbled on some proposal about a "New Dialog Module Design" [1]. This is excetly what I'm looking for. Is this still just a proposal? Thanks! Lukas PS: I also posted this question in stackoverflow [2] [1] http://www.kamailio.org/dokuwiki/doku.php/modules-new-design:dialog-module-… [2] http://stackoverflow.com/questions/32519551/kamailio-concurrent-calls-after…

2 1

ha1 password authentication without plain text password
by Nabeel 14 Sep '15

14 Sep '15

Hi, My SIP client only uses the 'ha1' password column from the database to authenticate users. It does not require the 'password' column. However, I am not able to register without having the plain text password present in the 'password' column in the database. I need to change this behaviour so that user registration will occur using only the ha1 encoded password column. How can I make this change? I tried commenting out and changing the 'password_column' attribute in the config but could not get it to work.

2 1

selecting memory manager at startup
by Daniel-Constantin Mierla 14 Sep '15

14 Sep '15

Hello, (cross-posting as it is relevant to user community as well). I just pushed a bunch of patches to master branch that will allow selecting the memory manger at kamailio startup, no longer needed to re-compile sources. There are two new command line parameters: * -x name: select the memory manager for shm * -X name: select the memory manager for pkg * if -x is provided but -X is not provided, then pkg uses same memory manager as shm * name can be: * fm - fast malloc (f_malloc) * qm - quick malloc (q_malloc) * default memory manager is fm (what was default so far) Both f_malloc and q_malloc are now compiled, selecting one or the other being possible. Other managers expected to be added in the list soon, especially TLSF, added not that long ago by Camille Oudot. Maybe reviving Doug Lea malloc (existing in dl_malloc.c) worth a try now that can be easily used. The debugging mode for each memory manager is controlled by DB_SR_MEMORY define via Makefile.defs -- right now it is enabled. All enabled memory mangers must be compiled either with or without DB_SR_MEMORY (it won't work to have one memory manger with DB_SR_MEMORY and another one without). Using system malloc for private (pkg) memory is possible by removing the define of PKG_MALLOC from Makefile.defs (same as it was before). This is a mode suitable for troubleshooting using external tools such as valgrind, because it does inline replacement of pkg_malloc() with malloc(), so those tools can track the place of allocation. I plan to add a system malloc custom manager, to allow selecting it with -X (system malloc won't work for shm management, because it is only for private memory). There is no performance impact at runtime, it is only the startup procedure that replaces the pointers to memory management functions. Hopefully with the new mechanism will be able to track easier memory issues -- e.g., qm malloc is better for troubleshooting, using it no longer requires recompilation, just starting kamailio with -x qm. Feedback, especially testing, will be very appreciated! Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com Kamailio Advanced Training, Sep 28-30, 2015, in Berlin - http://asipto.com/u/kat

1 0

no response, re-route calls to a different address
by Al S 14 Sep '15

14 Sep '15

Hi, Can we make Kamailio to re-route calls from an address that does not respond to a different address? Thanks,Al

3 4

Kamailio v4.3.2 Released
by Daniel-Constantin Mierla 10 Sep '15

10 Sep '15

Hello, Kamailio SIP Server v4.3.2 stable release is out. This is a maintenance release of the latest stable branch, 4.3, that includes fixes since release of v4.3.1. There is no change to database schema or configuration language structure that you have to do on previous installations of v4.3.x. Deployments running previous v4.x.x versions are strongly recommended to be upgraded to v4.3.2. For more details about version 4.3.2 (including links and guidelines to download the tarball or from GIT repository), visit: * http://www.kamailio.org/w/2015/09/kamailio-v4-3-2-released/ RPM, Debian/Ubuntu packages will be available soon as well. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

Problem with registering softphones
by rasx0＠Safe-mail.net 10 Sep '15

10 Sep '15

Hello! New user here. I'm testing Kamailio installation in testing environment. SIP domain is reachable, Kamailio itself is working fine yet I have a problem with registering softphones. I've tried 3 sip apps and with only one I am able to register with server. Server itself is "vanilla", no changes made. There is user, domain, pwd defined and nothing else. App that successfully connects is X-Lite, after unchecking "Register with domain and receive calls" and checking "Set outbound as domain". Other apps are: Zoiper, Jitsi. After many "checks" and "unchecks" of literary every option I still can't get them to work with me. I'm looking for any kind of hints as of how to get it to register as well as where may I find kamailio logs?

2 1

Releasing Kamailio v4.3.2
by Daniel-Constantin Mierla 10 Sep '15

10 Sep '15

Hello, I am considering to release a new version from branch 4.3 later this week, on Thursday, September 10. If there are issues not yet reported, then use github tracker to do it: - https://github.com/kamailio/kamailio/issues Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com Kamailio Advanced Training, Sep 28-30, 2015, in Berlin - http://asipto.com/u/kat

2 7

No SDP offer answer -> therefore we can not do Rx AAR 1(875) ERROR
by Jan Devai 10 Sep '15

10 Sep '15

Hi Guys, can anybody help us find why we do not get SDP offer answer, see error below: dev_pcscf: 3(879) DEBUG: ims_qos [mod.c:643]: w_rx_aar(): No SDP offer answer -> therefore we can not do Rx AAR 1(875) ERROR: <script>: ACK ( sip:+4620950160102@ims.mnc004.mcc232.3gppnetwork.org <sip:+421950160102@ims.mnc003.mcc231.3gppnetwork.org> (10.50.21.133:5080) to sip:+4620950160101@ims.mnc004.mcc232.3gppnetwork.org;user=phone <sip:+421950160101@ims.mnc003.mcc231.3gppnetwork.org;user=phone>, 3FD60673-55F09407000575C3-18269700) Since we do not get the information the SubscriptionID should be imsi(a)mncxx.mccxx.3gppnetwork.org in our AAR and instead it is contructed as imsi@ip:port which creates a REJECTION in AAA. Any help about where to correct this fault, or where exactly in the code this reception happens and/or anything will be appreciated BIG TIME :-) Thank you Jan

2 1

MEM_JOIN_FREE
by Uri Shacked 09 Sep '15

09 Sep '15

Hi, Does MEM_JOIN_FREE is compiled by default in kamailio 4.X.X ? thanks, Uri

4 6

Kamailio systemd scripts
by Daniel-Constantin Mierla 09 Sep '15

09 Sep '15

Hello, anyone here familiar with systemd that can provide the scripts for kamailio? Systemd is default now on last debian, so would be good to have them as well as I want to close the issue 294: - https://github.com/kamailio/kamailio/issues/294 Any help will be appreciated. Follow up on this list or on the github issue tracker. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com Kamailio Advanced Training, Sep 28-30, 2015, in Berlin - http://asipto.com/u/kat

4 5

Dialog module issue
by Yuriy Gorlichenko 09 Sep '15

09 Sep '15

Hello. I try to manage by dialog module every signaling session, that goes through my proxy. I added newx mod params modparam("dialog", "timeout_avp", "$avp(i:10)") modparam("dialog", "dlg_flag", 4) modparam("dialog", "initial_cbs_inscript", 1) modparam("dialog", "profiles_with_value", "caller") modparam("dialog", "track_cseq_updates", 1) modparam("dialog", "ka_timer", 10) modparam("dialog", "ka_interval", 30 And at request route I added this for all invite methods if (is_method("INVITE")){ $dlg_ctx(timeout_route) = "DIALOG_END"; $avp(i:10)=43200; $dlg_ctx(timeout_bye) = 1; dlg_set_property("ka-src"); dlg_set_property("ka-dst"); dlg_manage(); xlog("L_INFO","Dialog manage is {$ct}\n"); ... } So after this As I think every session must be dialog managed session and every leg of call must be checked by keepalive OPTIONS packets but no one OPTIONS request generated wen session goes through my proxy. thanks

1 0

Using PSTN as "fallback"
by Michael Nielsen 09 Sep '15

09 Sep '15

I have Kamailio running and connected to a PSTN gateway. My subscribers are named ex. +442071234567 - same as their real GSM number from my PSTN gateway. I'm using the standard kamailio.cfg which ships with version 4.3. When I'm trying to dial SIP client to SIP client I would like to have Kamailio route the call internally if a subscriber exists with ex. +442071234567. If no subscriber exists with ex. +442071234567 it should send it to my PSTN gateway. As it is now it seems as if it are trying to both call "internally" and via the PSTN gateway. How should one fix this issue the best way?

3 5

Kamailio crash [receive_fd: EOF on 19]
by SamyGo 09 Sep '15

09 Sep '15

Hi, I'm randomly getting crash in my Kamailio with an error in log files like this: <core> [pass_fd.c:293]: receive_fd(): ERROR: receive_fd: EOF on 19 ALERT: <core> [main.c:775]: handle_sigs(): child process 6853 exited by a signal 11 ALERT: <core> [main.c:778]: handle_sigs(): core was generated INFO: <core> [main.c:790]: handle_sigs(): INFO: terminating due to SIGCHLD *Version of Kamailio is:* [root@kamailio /]#kamailio -V version: kamailio 4.1.4 (x86_64/linux) 39adca flags: STATS: Off, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, DBG_QM_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: 39adca compiled on 03:48:50 Aug 1 2014 with gcc 4.4.7 And gdb bt output is attached in text file. One thing out that is common in all the previous core files is this: #12 0x00000000004a54ab in receive_msg ( buf=0x924600 "INVITE sip:+17036833500@14.131.165.9:5073 SIP/2.0\r\nVia: SIP/2.0/UDP 14.55.2.43:5060;branch=z9hG4bK0eB8f68591a19b9b8f0\r\nFrom: \"Anonymous\" <sip:Anonymous@Anonymous.invalid>;tag=gK0e13e132\r\nTo: <sip:+170"..., len=1018, rcv_info=0x7fff3dbee970) at receive.c:212 #13 0x000000000053c9a8 in udp_rcv_loop () at udp_server.c:536 Does this mean that Kamailio can't understand the From Domain: Anonymous.invalid and hence crashes ? Thanks, Sammy

2 6

Best practise for limiting concurrent calls across a cluster
by jay binks 08 Sep '15

08 Sep '15

Hey all, So I have a cluster of Kamailio servers ( 4 servers currently, soon to be 8 ), I'm looking for suggestions about the BEST way to achieve concurrent call limiting on a per customer basis, across the whole cluster. Initially I mis-read the dialog module documentation and assumed that dialog would provide me this ability, when used with a database. however it seems that the dialog module does not pull data from the DB after the initial startup. I know I can use sql ops to increment and decrement using event_route[dialog:start] and event_route[dialog:end]. however the database I've chosen ( for other valid reasons ) does not have an atomic increment and decrement. I could add yet another DB, but that just adds more failure points. so lets forget my setup, Im wanting suggestions about the BEST setup for this sort of thing. while remaining fault tolerant, and preferably without relying on any single point of failure. Sincerely Jay

7 13

core parameter onsend_route_reply=1 doesn't execute onsend_route block for received replies
by Julia Boudniatsky 07 Sep '15

07 Sep '15

Hello, I set some logs in onsend_route and it works fine for requests. With setting core parameter onsend_route_reply=1 ( yes, on), i expect to see logs for replays also, but it not occurs. Is this a bug or I miss something? version: kamailio 4.2.6 (x86_64/linux) db77ac BR, Julia

2 4

Siremis 4.2 with PHP 5.6
by Patrick Bezensiertblubb 07 Sep '15

07 Sep '15

2 2

Kamailio + Rtpengine < - > Freeswitch + ZRTP
by Alexandru Covalschi 07 Sep '15

07 Sep '15

Hello! Was trying to perfrom subj interconnection via http://kb.asipto.com/freeswitch:kamailio-3.3.x-freeswitch-1.2.x-sbс <http://kb.asipto.com/freeswitch:kamailio-3.3.x-freeswitch-1.2.x-sbc> via that guide. Kamailio and FS are on same host on Amazon EC2. The issue is - when I have proxy_media=true on FS, ZRTP is OK, but the leg_b user can't hear anything (but his voice is transmitted OK). When I set proxy-media to false the voice is OK, but something is with ZRTP so Jitsi can't establish ZRTP handshake. When I set bypass-media=true on FS both ZRTP and voice established, but quality is sometimes bad and the delay is too big. Anyone has any ideas? Kamailio 4.3, FS 1.4 <http://kb.asipto.com/freeswitch:kamailio-3.3.x-freeswitch-1.2.x-sbc> <http://kb.asipto.com/freeswitch:kamailio-3.3.x-freeswitch-1.2.x-sbc> -- Alexandru Covalschi ABRISS-Solutions VoIP engineer and system administrator phone: +37367398493 web: http://abs-telecom.com/

2 1

Thoughts on setup with Kamailio and FreeSWITCH
by Michael Nielsen 07 Sep '15

07 Sep '15

Hello everyone... I'm testing various ways of setting up Kamailio and FreeSWITCH (as VAS-handler). I'm struggling a bit on what Kamailio should do and FreeSWITCH should do. My basic setup is to handle voicemails, internal calls between subscribers and outgoing calls to a SIP gateway to GSM. My idea is to have Kamailio handle all calls and routing between subscribers and the SIP gateway and only have FreeSWITCH handle voicemail (to save the audio file and e-mail it). How does that sound? Or should I route everything to FreeSWITCH via Kamailio and have FreeSWITCH route calls between subcsribers and SIP gateway as well? What are best practises etc...?

2 1

Question about in call both side redirection
by Андрей Ярин 07 Sep '15

07 Sep '15

Hello (sorry for my bad english) - i try to create voice record service by request. User A call to user B. In call by pressing combination like *55 Kamailio must redirect both sides to asterisk, whitch create dynamic conference room with recording. As i understand i need to use dlg_refer() from dialog module, but in log file i get: Konsole output Sep 4 10:45:14 voipc-node2 /usr/local/sbin/kamailio[18941]: ERROR: dialog [dlg_req_within.c:85]: build_dlg_t(): no contact available Sep 4 10:45:14 voipc-node2 /usr/local/sbin/kamailio[18941]: ERROR: dialog [dlg_transfer.c:188]: dlg_refer_callee(): failed to create dlg_t In script i try to refer with: dlg_refer("callee", "sip:100@10.10.9.209"); dlg_refer("caller", "sip:100@10.10.9.209"); -- Ярин Андрей Инженер ООО "И.С.-Телеком" 8(351)7786878 доб 113 8(351)2555724 доб 113 8(351)2555787 доб 113

2 1

Route all traffic from Kamailio to FreeSWITCH after inital checks...
by Michael Nielsen 07 Sep '15

07 Sep '15

I'm running the standard Debian 7 Kamailio 4.3 package. I've added the following to my kamailio.cfg: #!define WITH_MYSQL #!define WITH_AUTH #!define WITH_USRLOCDB #!define WITH_NAT #!define WITH_TLS #!define WITH_ANTIFLOOD After authentication, nat etc. is done is there an easy way to transfer everything else to FreeSWITCH? I've looked at the dispatcher module, but don't know where to put the "transfer" in kamailio.cfg?

3 4

Re: [SR-Users] webrtc
by Slava Bendersky 07 Sep '15

07 Sep '15

Hello Giovanni, I fixed webrtc call working right now. I checked debug again and I so 408 error. There was missing record_route() for first INVITE. Thank you for help. Slava. From: "Giovanni Maruzzelli" <gmaruzz(a)gmail.com> To: "sr-users" <sr-users(a)lists.sip-router.org> Sent: Saturday, 5 September, 2015 07:50:29 Subject: Re: [SR-Users] webrtc First thing, check that you can have a webRTC call directly with FreeSWITCH, without passing by Kamailio. If that works, and it does not work through Kamailio, then provide kamailio config, freeswitch config, and debug log from both. On Sat, Sep 5, 2015 at 12:51 AM, Slava Bendersky < volga629(a)skillsearch.ca > wrote: Hello Everyone, I am trying setup webrtc call with freeswitch. [root@canlvprx01 kamailio]# rpm -qa | grep kamailio kamailio-4.3.1-4.4.fc21.x86_64 Case: INTERNET eth0 | eth1 LAN | Web Browser ---->webrtc ----> kamailio ----> freeswitch Getting this error Sep 4 00:22:06 canlvprx01 /usr/sbin/kamailio[11820]: WARNING: <core> [forward.h:164]: msg_send(): TCP/TLS connection for WebSocket could not be found Sep 4 00:22:10 canlvprx01 /usr/sbin/kamailio[11817]: WARNING: <core> [forward.h:164]: msg_send(): TCP/TLS connection for WebSocket could not be found Sep 4 00:22:14 canlvprx01 /usr/sbin/kamailio[11818]: WARNING: <core> [forward.h:164]: msg_send(): TCP/TLS connection for WebSocket could not be found Tried check debug don't see any thing special. Any help thank you. Please let me know which logs will good to provide. Slava. _______________________________________________ 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 -- Sincerely, Giovanni Maruzzelli Cell : +39-347-2665618 _______________________________________________ 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

Re: [SR-Users] webrtc
by Slava Bendersky 06 Sep '15

06 Sep '15

Hello Giovanni, Here SDP webrtc call traffic capture on kamailio side http://fpaste.org/264289/15798761/ password from paste: kamailio Slava. From: "Giovanni Maruzzelli" <gmaruzz(a)gmail.com> To: "sr-users" <sr-users(a)lists.sip-router.org> Sent: Saturday, 5 September, 2015 07:50:29 Subject: Re: [SR-Users] webrtc First thing, check that you can have a webRTC call directly with FreeSWITCH, without passing by Kamailio. If that works, and it does not work through Kamailio, then provide kamailio config, freeswitch config, and debug log from both. On Sat, Sep 5, 2015 at 12:51 AM, Slava Bendersky < volga629(a)skillsearch.ca > wrote: Hello Everyone, I am trying setup webrtc call with freeswitch. [root@canlvprx01 kamailio]# rpm -qa | grep kamailio kamailio-4.3.1-4.4.fc21.x86_64 Case: INTERNET eth0 | eth1 LAN | Web Browser ---->webrtc ----> kamailio ----> freeswitch Getting this error Sep 4 00:22:06 canlvprx01 /usr/sbin/kamailio[11820]: WARNING: <core> [forward.h:164]: msg_send(): TCP/TLS connection for WebSocket could not be found Sep 4 00:22:10 canlvprx01 /usr/sbin/kamailio[11817]: WARNING: <core> [forward.h:164]: msg_send(): TCP/TLS connection for WebSocket could not be found Sep 4 00:22:14 canlvprx01 /usr/sbin/kamailio[11818]: WARNING: <core> [forward.h:164]: msg_send(): TCP/TLS connection for WebSocket could not be found Tried check debug don't see any thing special. Any help thank you. Please let me know which logs will good to provide. Slava. _______________________________________________ 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 -- Sincerely, Giovanni Maruzzelli Cell : +39-347-2665618 _______________________________________________ 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

Topoh configuration question
by Asgaroth 06 Sep '15

06 Sep '15

Hi all, I have a quick question with regards the topoh module, is it possible to have the topoh module only operate on a particular interface and direction. I have some edge proxies and I am trying out the topoh module, what I see happen is that messages originating from behind/inside the edge proxy is topoh'd out, which is exactly what I was looking for, but it appears to do the same for messages originating from the wild, so messages pushed in behind/inside the proxy is also encoded, which is not what I was expecting. Is it possible to configure the topoh module to activate for messages being sent out of the edge proxy into the "wild", but not the other way around, or, decode if it finds an encoded messages who's destination is "behind" the proxy. Any thoughts are much appreciated. Thanks

2 1

webrtc
by Slava Bendersky 05 Sep '15

05 Sep '15

Hello Everyone, I am trying setup webrtc call with freeswitch. [root@canlvprx01 kamailio]# rpm -qa | grep kamailio kamailio-4.3.1-4.4.fc21.x86_64 Case: INTERNET eth0 | eth1 LAN | Web Browser ---->webrtc ----> kamailio ----> freeswitch Getting this error Sep 4 00:22:06 canlvprx01 /usr/sbin/kamailio[11820]: WARNING: <core> [forward.h:164]: msg_send(): TCP/TLS connection for WebSocket could not be found Sep 4 00:22:10 canlvprx01 /usr/sbin/kamailio[11817]: WARNING: <core> [forward.h:164]: msg_send(): TCP/TLS connection for WebSocket could not be found Sep 4 00:22:14 canlvprx01 /usr/sbin/kamailio[11818]: WARNING: <core> [forward.h:164]: msg_send(): TCP/TLS connection for WebSocket could not be found Tried check debug don't see any thing special. Any help thank you. Please let me know which logs will good to provide. Slava.

2 1

Re: [SR-Users] CRITICAL log on kamailio startup
by Nuno Reis 04 Sep '15

04 Sep '15

Good morning. Has anyone seen this too? Looking forward to hear from you. BR, -- *Nuno Miguel Reis* | *Unified Communication** Systems* M. +351 913907481 | nreis(a)wavecom.pt WAVECOM-Soluções Rádio, S.A. Cacia Park | Rua do Progresso, Lote 15 3800-639 AVEIRO | Portugal T. +351 309 700 225 | F. +351 234 919 191 *GPS <http://maps.google.com/maps/ms?msa=0&msid=202333747613191340808.0004b4b227a…> | www.wavecom.pt <http://www.wavecom.pt/>** <http://www.wavecom.pt/>* <http://www.wavecom.pt/> <http://www.wavecom.pt/pt/> On Fri, Aug 14, 2015 at 1:41 AM, Nuno Reis <nreis(a)wavecom.pt> wrote: > Hi guys. > > I've noticed this CRITICAL log line on kamailio startup: > > CRITICAL: dialog [dlg_cb.c:137]: register_dlgcb(): DLGCB_CREATED type > registered after shutdown!?! > > > This line started to show up after upgrade from 4.2.x to 4.3 and now to > 4.3.1. > Everything seems to be working fine and a really don't see any harm > anywhere. > Could you please comment on this? > > Cheers, > > -- > > *Nuno Miguel Reis* | *Unified Communication** Systems* > M. +351 913907481 | nreis(a)wavecom.pt > WAVECOM-Soluções Rádio, S.A. > Cacia Park | Rua do Progresso, Lote 15 > 3800-639 AVEIRO | Portugal > T. +351 309 700 225 | F. +351 234 919 191 > *GPS > <http://maps.google.com/maps/ms?msa=0&msid=202333747613191340808.0004b4b227a…> > | www.wavecom.pt <http://www.wavecom.pt/>** <http://www.wavecom.pt/>* > > <http://www.wavecom.pt/> > <http://www.wavecom.pt/pt/> > > >

2 2

Sounds works differently on different clients.
by Michael Nielsen 04 Sep '15

04 Sep '15

This is my setup: Kamailio -> FreeSWITCH (for voicemail) ...SIP gateway for connecting GSM So every call is routed directly via Kamailio - between SIP clients and in/out from the GSM space. Testing with a cellular phone as one client and X-Lite on Mac OS X as the other - everything works. Testing with a cellular phone as one client and Bria on iOS as the other - everything works except there's no sounds coming into Bria. The person on the cellular can hear everything (sound coming from Bria), but Bria client cannot hear sound from cellular phone. Is it something to do with codec or could it be something else?

2 3

408 Request Timeout
by vamsi 04 Sep '15

04 Sep '15

I am an web developer and want to create a WEBRTC application. My knowledge level in SIP is beginner. I want my application to talk to kamailio and in process of setting up kamailio by following the below articles. http://nil.uniza.sk/sip/kamailio/configuring-kamailio-4x-websocket http://kamailio.org/docs/modules/4.3.x/modules/websocket.html I was able to connect (using try.jssp.net) to kamailio as multiple clients for initial setup and successfully able to get voice and video working. But I'm unable to send messages between clients and receive "408 Request Timeout" error. I have the presence and presence_xml modules loaded and have the # ----- mi_fifo params ----- modparam("mi_fifo", "fifo_name", "/var/run/kamailio/kamailio_fifo") # ----- ctl params ----- modparam("ctl", "binrpc", "unix:/var/run/kamailio/kamailio_ctl") Below is the log. Any help is appreciated. Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a76298] refcnt [2] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a76298] refcnt [1] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[AUTH] c=[/usr/local/etc/kamailio/kamailio.cfg] l=825 a=2 n=exit Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [usr_avp.c:631]: destroy_avp_list(): destroying list (nil) Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [usr_avp.c:631]: destroy_avp_list(): destroying list (nil) Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [usr_avp.c:631]: destroy_avp_list(): destroying list (nil) Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [usr_avp.c:631]: destroy_avp_list(): destroying list (nil) Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [usr_avp.c:631]: destroy_avp_list(): destroying list (nil) Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [usr_avp.c:631]: destroy_avp_list(): destroying list (nil) Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [xavp.c:446]: xavp_destroy_list(): destroying xavp list (nil) Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [receive.c:278]: receive_msg(): cleaning up Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [tcp_read.c:1153]: ws_process_msg(): WebSocket Message: [[>>>#012??#002?E?<<<]] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: websocket [ws_conn.c:429]: wsconn_get(): wsconn_get for id [2] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: websocket [ws_conn.c:437]: wsconn_get(): wsconn_get returns wsc [0x7f06a2a76298] refcnt [2] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: websocket [ws_frame.c:415]: decode_and_validate_ws_frame(): decoding WebSocket frame Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: websocket [ws_frame.c:456]: decode_and_validate_ws_frame(): supported non-control frame: 0x1 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: websocket [ws_frame.c:555]: decode_and_validate_ws_frame(): Rx (decoded): MESSAGE sip:abc123@ip-205-64-10.dqa.capitalone.com SIP/2.0#015#012Via: SIP/2.0/WS kjh0uotuqma6.invalid;branch=z9hG4bK9552000#015#012Max-Forwards: 69#015#012To: <sip:abc123@ip-205-64-10.dqa.capitalone.com>#015#012From: "xyz987" <sip:xyz987@ip-205-64-10.test.com:8088>;tag=c1joq54vne#015#012Call-ID: orel8as144p4ebuuf96n#015#012CSeq: 1977 MESSAGE#015#012Proxy-Authorization: Digest algorithm=MD5, username="xyz987", realm="ip-205-64-10.test.com", nonce="Vee3iFXntlzqK/kDTxUAIxwI55RzH/ll", uri=" sip:abc123@ip-205-64-10.test.com", response="0d513943ed7a0234b7016c5f4546b0b7"#015#012Content-Type: text/plain#015#012Allow: INVITE,ACK,CANCEL,BYE,UPDATE,MESSAGE,OPTIONS,REFER#015#012Supported: outbound#015#012User-Agent: JsSIP 0.7.4#015#012Content-Length: 13#015#012#015#012samplemsgwork Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: websocket [ws_frame.c:659]: ws_frame_receive(): Rx SIP message:#012MESSAGE sip:abc123@ip-10-255-54-20.test.com SIP/2.0#015#012Via: SIP/2.0/WS kjh0uotuqma6.invalid;branch=z9hG4bK9552000#015#012Max-Forwards: 69#015#012To: <sip:abc123@ip-10-255-54-20.test.com>#015#012From: "xyz987" < sip:xyz987@ip-10-255-54-20.test.com:8088>;tag=c1joq54vne#015#012Call-ID: orel8as144p4ebuuf96n#015#012CSeq: 1977 MESSAGE#015#012Proxy-Authorization: Digest algorithm=MD5, username="xyz987", realm="ip-10-255-54-20.test.com", nonce="Vee3iFXntlzqK/kDTxUAIxwI55RzH/ll", uri=" sip:abc123@ip-10-255-54-20.test.com", response="0d513943ed7a0234b7016c5f4546b0b7"#015#012Content-Type: text/plain#015#012Allow: INVITE,ACK,CANCEL,BYE,UPDATE,MESSAGE,OPTIONS,REFER#015#012Supported: outbound#015#012User-Agent: JsSIP 0.7.4#015#012Content-Length: 13#015#012#015#012samplemsgwork Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a76298] refcnt [2] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a76298] refcnt [1] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/msg_parser.c:606]: parse_msg(): SIP Request: Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/msg_parser.c:608]: parse_msg(): method: <MESSAGE> Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/msg_parser.c:610]: parse_msg(): uri: < sip:abc123@ip-10-255-54-20.test.com> Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/msg_parser.c:612]: parse_msg(): version: <SIP/2.0> Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/parse_via.c:1254]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK9552000>; state=16 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/parse_via.c:2642]: parse_via(): end of header reached, state=5 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/msg_parser.c:496]: parse_headers(): parse_headers: Via found, flags=2 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/msg_parser.c:498]: parse_headers(): parse_headers: this is the first via Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [receive.c:134]: receive_msg(): After parse_msg... Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [receive.c:177]: receive_msg(): preparing to run routing scripts... Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=506 a=5 n=route Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[REQINIT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=639 a=16 n=if Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[REQINIT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=634 a=25 n=mf_process_maxfwd_header Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: maxfwd [mf_funcs.c:85]: is_maxfwd_present(): value = 69 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[REQINIT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=644 a=16 n=if Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[REQINIT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=639 a=25 n=is_method Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[REQINIT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=648 a=16 n=if Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[REQINIT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=644 a=26 n=sanity_check Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/parse_addr_spec.c:894]: parse_addr_spec(): end of header reached, state=10 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/msg_parser.c:173]: get_hdr_field(): DEBUG: get_hdr_field: <To> [46]; uri=[sip:abc123@ip-10-255-54-20.test.com] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/msg_parser.c:175]: get_hdr_field(): DEBUG: to body [< sip:abc123@ip-10-255-54-20.test.com>#015#012] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/msg_parser.c:153]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <1977> <MESSAGE> Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/msg_parser.c:187]: get_hdr_field(): DEBUG: get_hdr_body : content_length=13 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/msg_parser.c:89]: get_hdr_field(): found end of header Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/parse_addr_spec.c:172]: parse_to_param(): DEBUG: add_param: tag=c1joq54vne Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [parser/parse_addr_spec.c:894]: parse_addr_spec(): end of header reached, state=29 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: sanity [mod_sanity.c:248]: w_sanity_check(): sanity checks result: 1 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=529 a=16 n=if Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=509 a=25 n=nat_uac_test Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=514 a=55 n=force_rport Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=524 a=16 n=if Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=515 a=25 n=is_method Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=524 a=16 n=if Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=519 a=24 n=add_contact_alias Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: nathelper [nathelper.c:958]: add_contact_alias_0_f(): no contact header Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=529 a=5 n=route Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[NATDETECT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=846 a=55 n=force_rport Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[NATDETECT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=857 a=16 n=if Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[NATDETECT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=847 a=25 n=nat_uac_test Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[NATDETECT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=853 a=16 n=if Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[NATDETECT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=848 a=25 n=is_method Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[NATDETECT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=853 a=16 n=if Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[NATDETECT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=851 a=24 n=is_first_hop Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: siputils [sipops.c:159]: w_is_first_hop(): no 2nd via found - first hop Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[NATDETECT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=852 a=24 n=set_contact_alias Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[NATDETECT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=854 a=39 n=setflag Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[NATDETECT] c=[/usr/local/etc/kamailio/kamailio.cfg] l=857 a=2 n=return Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=540 a=16 n=if Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=532 a=25 n=is_method Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=540 a=5 n=route Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[WITHINDLG] c=[/usr/local/etc/kamailio/kamailio.cfg] l=654 a=16 n=if Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[WITHINDLG] c=[/usr/local/etc/kamailio/kamailio.cfg] l=652 a=24 n=has_totag Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: siputils [checks.c:97]: has_totag(): no totag Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[WITHINDLG] c=[/usr/local/etc/kamailio/kamailio.cfg] l=652 a=2 n=return Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=549 a=16 n=if Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=545 a=24 n=t_precheck_trans Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=549 a=24 n=t_check_trans Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: tm [t_lookup.c:1011]: t_check_msg(): DEBUG: t_check_msg: msg id=4 global id=3 T start=(nil) Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: tm [t_lookup.c:466]: t_lookup_request(): t_lookup_request: start searching: hash=65389, isACK=0 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: tm [t_lookup.c:424]: matching_3261(): DEBUG: RFC3261 transaction matching failed Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: tm [t_lookup.c:648]: t_lookup_request(): DEBUG: t_lookup_request: no transaction found Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: tm [t_lookup.c:1080]: t_check_msg(): DEBUG: t_check_msg: msg id=4 global id=4 T end=(nil) Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=552 a=5 n=route Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[AUTH] c=[/usr/local/etc/kamailio/kamailio.cfg] l=833 a=16 n=if Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[AUTH] c=[/usr/local/etc/kamailio/kamailio.cfg] l=820 a=25 n=is_method Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [socket_info.c:563]: grep_sock_info(): checking if host==us: 31==12 && [ ip-10-255-54-20.test.com] == [10.205.64.10] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [socket_info.c:566]: grep_sock_info(): checking if port 8088 (advertise 0) matches port 8088 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [socket_info.c:563]: grep_sock_info(): checking if host==us: 31==12 && [ ip-10-255-54-20.test.com] == [10.205.64.10] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [socket_info.c:566]: grep_sock_info(): checking if port 8088 (advertise 0) matches port 8088 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [socket_info.c:563]: grep_sock_info(): checking if host==us: 31==12 && [ ip-10-255-54-20.test.com] == [10.205.64.10] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [socket_info.c:566]: grep_sock_info(): checking if port 8080 (advertise 0) matches port 8088 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [socket_info.c:563]: grep_sock_info(): checking if host==us: 31==12 && [ ip-10-255-54-20.test.com] == [10.205.64.10] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [socket_info.c:566]: grep_sock_info(): checking if port 5061 (advertise 0) matches port 8088 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [socket_info.c:563]: grep_sock_info(): checking if host==us: 31==12 && [ ip-10-255-54-20.test.com] == [10.205.64.10] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [socket_info.c:566]: grep_sock_info(): checking if port 4443 (advertise 0) matches port 8088 Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[AUTH] c=[/usr/local/etc/kamailio/kamailio.cfg] l=828 a=16 n=if Sep 2 22:54:20 ip-10-255-54-20 kamailio[10177]: exec: *** cfgtrace:request_route=[AUTH] c=[/usr/local/etc/kamailio/kamailio.cfg] l=823 a=27 n=auth_check Sep 2 22:54:20 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:457]: wsconn_get_list(): wsconn_get_list Sep 2 22:54:20 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:465]: wsconn_get_list(): counter wsc [0x7f06a2a775a8] prev => [(nil)] next => [0x7f06a2a76298] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:465]: wsconn_get_list(): counter wsc [0x7f06a2a76298] prev => [0x7f06a2a775a8] next => [(nil)] Sep 2 22:54:20 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:492]: wsconn_get_list(): wsc [0x7f06a2a775a8] id [1] ref++ Sep 2 22:54:20 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:492]: wsconn_get_list(): wsc [0x7f06a2a76298] id [2] ref++ Sep 2 22:54:25 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:501]: wsconn_get_list(): wsconn_get_list returns list [0x7f06ab4f8350] with [2] members Sep 2 22:54:25 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:511]: wsconn_put_list(): wsconn_put_list [0x7f06ab4f8350] Sep 2 22:54:25 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a775a8] refcnt [2] Sep 2 22:54:25 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a775a8] refcnt [1] Sep 2 22:54:25 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a76298] refcnt [2] Sep 2 22:54:25 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a76298] refcnt [1] Sep 2 22:54:26 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [io_wait.h:598]: io_watch_del(): DBG: io_watch_del (0xa40820, 9, -1, 0x10) fd_no=2 called Sep 2 22:54:26 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [tcp_read.c:1450]: release_tcpconn(): releasing con 0x7f06a2a8c3b8, state 1, fd=9, id=2 Sep 2 22:54:26 ip-10-255-54-20 kamailio[10177]: DEBUG: <core> [tcp_read.c:1451]: release_tcpconn(): extra_data (nil) Sep 2 22:54:26 ip-10-255-54-20 kamailio[10178]: DEBUG: <core> [tcp_main.c:3243]: handle_tcp_child(): reader response= 7f06a2a8c3b8, 1 from 3 Sep 2 22:54:26 ip-10-255-54-20 kamailio[10178]: DEBUG: <core> [io_wait.h:376]: io_watch_add(): DBG: io_watch_add(0x9fc580, 34, 2, 0x7f06a2a8c3b8), fd_no=23 Sep 2 22:54:26 ip-10-255-54-20 kamailio[10178]: DEBUG: <core> [tcp_main.c:3370]: handle_tcp_child(): CONN_RELEASE 0x7f06a2a8c3b8 refcnt= 1 Sep 2 22:54:26 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:457]: wsconn_get_list(): wsconn_get_list Sep 2 22:54:26 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:465]: wsconn_get_list(): counter wsc [0x7f06a2a775a8] prev => [(nil)] next => [0x7f06a2a76298] Sep 2 22:54:26 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:465]: wsconn_get_list(): counter wsc [0x7f06a2a76298] prev => [0x7f06a2a775a8] next => [(nil)] Sep 2 22:54:26 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:492]: wsconn_get_list(): wsc [0x7f06a2a775a8] id [1] ref++ Sep 2 22:54:26 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:492]: wsconn_get_list(): wsc [0x7f06a2a76298] id [2] ref++ Sep 2 22:54:26 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:501]: wsconn_get_list(): wsconn_get_list returns list [0x7f06ab4f8350] with [2] members Sep 2 22:54:26 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:511]: wsconn_put_list(): wsconn_put_list [0x7f06ab4f8350] Sep 2 22:54:26 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a775a8] refcnt [2] Sep 2 22:54:26 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a775a8] refcnt [1] Sep 2 22:54:26 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a76298] refcnt [2] Sep 2 22:54:26 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a76298] refcnt [1] Sep 2 22:54:27 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:457]: wsconn_get_list(): wsconn_get_list Sep 2 22:54:27 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:465]: wsconn_get_list(): counter wsc [0x7f06a2a775a8] prev => [(nil)] next => [0x7f06a2a76298] Sep 2 22:54:27 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:465]: wsconn_get_list(): counter wsc [0x7f06a2a76298] prev => [0x7f06a2a775a8] next => [(nil)] Sep 2 22:54:27 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:492]: wsconn_get_list(): wsc [0x7f06a2a775a8] id [1] ref++ Sep 2 22:54:27 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:492]: wsconn_get_list(): wsc [0x7f06a2a76298] id [2] ref++ Sep 2 22:54:27 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:501]: wsconn_get_list(): wsconn_get_list returns list [0x7f06ab4f8350] with [2] members Sep 2 22:54:27 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:511]: wsconn_put_list(): wsconn_put_list [0x7f06ab4f8350] Sep 2 22:54:27 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a775a8] refcnt [2] Sep 2 22:54:27 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a775a8] refcnt [1] Sep 2 22:54:27 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a76298] refcnt [2] Sep 2 22:54:27 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a76298] refcnt [1] Sep 2 22:54:28 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:457]: wsconn_get_list(): wsconn_get_list Sep 2 22:54:28 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:465]: wsconn_get_list(): counter wsc [0x7f06a2a775a8] prev => [(nil)] next => [0x7f06a2a76298] Sep 2 22:54:28 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:465]: wsconn_get_list(): counter wsc [0x7f06a2a76298] prev => [0x7f06a2a775a8] next => [(nil)] Sep 2 22:54:28 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:492]: wsconn_get_list(): wsc [0x7f06a2a775a8] id [1] ref++ Sep 2 22:54:28 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:492]: wsconn_get_list(): wsc [0x7f06a2a76298] id [2] ref++ Sep 2 22:54:28 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:501]: wsconn_get_list(): wsconn_get_list returns list [0x7f06ab4f8350] with [2] members Sep 2 22:54:28 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:511]: wsconn_put_list(): wsconn_put_list [0x7f06ab4f8350] Sep 2 22:54:28 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a775a8] refcnt [2] Sep 2 22:54:28 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a775a8] refcnt [1] Sep 2 22:54:28 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a76298] refcnt [2] Sep 2 22:54:28 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a76298] refcnt [1] Sep 2 22:54:29 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:457]: wsconn_get_list(): wsconn_get_list Sep 2 22:54:29 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:465]: wsconn_get_list(): counter wsc [0x7f06a2a775a8] prev => [(nil)] next => [0x7f06a2a76298] Sep 2 22:54:29 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:465]: wsconn_get_list(): counter wsc [0x7f06a2a76298] prev => [0x7f06a2a775a8] next => [(nil)] Sep 2 22:54:29 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:492]: wsconn_get_list(): wsc [0x7f06a2a775a8] id [1] ref++ Sep 2 22:54:29 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:492]: wsconn_get_list(): wsc [0x7f06a2a76298] id [2] ref++ Sep 2 22:54:31 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:501]: wsconn_get_list(): wsconn_get_list returns list [0x7f06ab4f8350] with [2] members Sep 2 22:54:31 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:511]: wsconn_put_list(): wsconn_put_list [0x7f06ab4f8350] Sep 2 22:54:31 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a775a8] refcnt [2] Sep 2 22:54:31 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a775a8] refcnt [1] Sep 2 22:54:31 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a76298] refcnt [2] Sep 2 22:54:31 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a76298] refcnt [1] Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: tm [t_reply.c:1230]: t_should_relay_response(): ->>>>>>>>> T_code=0, new_code=408 Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: tm [t_reply.c:1748]: relay_reply(): DEBUG: relay_reply: branch=0, save=0, relay=0 icode=0 Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: <core> [msg_translator.c:158]: check_via_address(): (172.18.116.115, kjh0uotuqma6.invalid, 0) Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: <core> [mem/shm_mem.c:101]: _shm_resize(): WARNING:vqm_resize: resize(0) called Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: websocket [ws_conn.c:429]: wsconn_get(): wsconn_get for id [2] Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: websocket [ws_conn.c:437]: wsconn_get(): wsconn_get returns wsc [0x7f06a2a76298] refcnt [2] Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: websocket [ws_frame.c:751]: ws_frame_transmit(): Tx message:#012SIP/2.0 408 Request Timeout#015#012Via: SIP/2.0/WS kjh0uotuqma6.invalid;branch=z9hG4bK2462101;rport=59540;received=172.18.116.115#015#012To: <sip:abc123@ip-10-255-54-20.test.com>;tag=b44d120c617c843b219e52eae8b5e9ff-3dde#015#012From: "xyz987" <sip:xyz987@ip-10-255-54-20.test.com:8088>;tag=5qg1sitf3i#015#012Call-ID: orel8dhn00r81cega00f#015#012CSeq: 862 MESSAGE#015#012Server: kamailio (4.4.0-dev2 (x86_64/linux))#015#012Content-Length: 0#015#012#015#012 Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: websocket [ws_frame.c:150]: encode_and_send_ws_frame(): encoding WebSocket frame Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: websocket [ws_frame.c:181]: encode_and_send_ws_frame(): supported non-control frame: 0x1 Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: <core> [tcp_main.c:2211]: tcpconn_send_put(): tcp connection found (0x7f06a2a8c3b8), acquiring fd Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: <core> [tcp_main.c:2221]: tcpconn_send_put(): c=0x7f06a2a8c3b8, n=16 Sep 2 22:54:31 ip-10-255-54-20 kamailio[10178]: DEBUG: <core> [tcp_main.c:3476]: handle_ser_child(): read response= 7f06a2a8c3b8, 2, fd -1 from 5 (10164) Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: <core> [tcp_main.c:2251]: tcpconn_send_put(): after receive_fd: c= 0x7f06a2a8c3b8 n=8 fd=8 Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: <core> [tcp_main.c:2430]: tcpconn_do_send(): sending... Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: <core> [tcp_main.c:2464]: tcpconn_do_send(): after real write: c= 0x7f06a2a8c3b8 n=419 fd=8 Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: <core> [tcp_main.c:2465]: tcpconn_do_send(): buf=#012?~#001?SIP/2.0 408 Request Timeout#015#012Via: SIP/2.0/WS kjh0uotuqma6.invalid;branch=z9hG4bK2462101;rport=59540;received=172.18.116.115#015#012To: <sip:abc123@ip-10-255-54-20.test.com>;tag=b44d120c617c843b219e52eae8b5e9ff-3dde#015#012From: "xyz987" <sip:xyz987@ip-10-255-54-20.test.com:8088>;tag=5qg1sitf3i#015#012Call-ID: orel8dhn00r81cega00f#015#012CSeq: 862 MESSAGE#015#012Server: kamailio (4.4.0-dev2 (x86_64/linux))#015#012Content-Length: 0#015#012#015#012 Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a76298] refcnt [2] Sep 2 22:54:31 ip-10-255-54-20 kamailio[10164]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a76298] refcnt [1] Sep 2 22:54:32 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:457]: wsconn_get_list(): wsconn_get_list Sep 2 22:54:32 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:465]: wsconn_get_list(): counter wsc [0x7f06a2a775a8] prev => [(nil)] next => [0x7f06a2a76298] Sep 2 22:54:32 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:465]: wsconn_get_list(): counter wsc [0x7f06a2a76298] prev => [0x7f06a2a775a8] next => [(nil)] Sep 2 22:54:32 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:492]: wsconn_get_list(): wsc [0x7f06a2a775a8] id [1] ref++ Sep 2 22:54:32 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:492]: wsconn_get_list(): wsc [0x7f06a2a76298] id [2] ref++ Sep 2 22:54:32 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:501]: wsconn_get_list(): wsconn_get_list returns list [0x7f06ab4f8350] with [2] members Sep 2 22:54:32 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:511]: wsconn_put_list(): wsconn_put_list [0x7f06ab4f8350] Sep 2 22:54:32 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a775a8] refcnt [2] Sep 2 22:54:32 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a775a8] refcnt [1] Sep 2 22:54:32 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:382]: wsconn_put(): wsconn_put start for [0x7f06a2a76298] refcnt [2] Sep 2 22:54:32 ip-10-255-54-20 kamailio[10173]: DEBUG: websocket [ws_conn.c:415]: wsconn_put(): wsconn_put end for [0x7f06a2a76298] refcnt [1]

2 2

Kamailio memmory leak after it does not receive response for CANCEL message
by Bui Minh Yen 03 Sep '15

03 Sep '15

Hi everyone, I am using Kamailio-4.1.5 and Kamailio-4.2.5 but with this both version I had a problem: Connection diagrams: SIP client ---- SBC --- Kamailio --- MGC/MGW --- GSM/PSTN subscriber Scenario: - Caller (SIP) make a new call to GSM (PSTN) subscriber - When GSM/PSTN is ringing or not ringing, Caller cancel call (Caller send CANCEL message) - But MGC does not send response message for CANCEL message - After about 120s (fr_inv_timer), Kamailio send 487 Request Terminated to SBC. >From this time, Kamailio have memory leak (tm does not free transactions) I reproduced this bugs 4-5 times and same problem is happen I attached capture file and log when I show shared memory (using kamcmd core.shmmem) and tm statistics (using kamcmd tm.stats). And time Kamailio start memory leak is 08-30-15-10:18:53 Could you help me solve this problem? Thank you so much! -- --------------------------- *Bui Thi Minh Yen*

2 2

A little offtop - a question about Kamailio Admin Book
by Alexandru Covalschi 03 Sep '15

03 Sep '15

Just wanted to ask when will http://www.asipto.com/sw/kamailio-admin-book/ become available in final version? Sorry for offtop, didn't know where to ask about that :) -- Alexandru Covalschi ABRISS-Solutions VoIP engineer and system administrator phone: +37367398493 web: http://abs-telecom.com/

2 1

registered4() is not adding xavp with details of the record
by Andrew Pogrebennyk 03 Sep '15

03 Sep '15

Hi, I was trying to use registered("location", "$ru", 0, 1) Last parameter is the flag according to http://kamailio.org/docs/modules/stable/modules/registrar.html#registrar.f.… flag values is as follows: 1 - set xavp_rcd with value from matched contact But I'm getting NULL instead of ruid.. While the same works after lookup("location"). So I took a quick look into the code and that confirms that registered4 does not add the xavp with details of the record (ruid), i.e. it does not do what the lookup_helper does. Is this done on purpose or an oversight? While fixing this it might be reasonable to introduce a new function for setting the XAVPs and call it from lookup and registered4 functions, especially since we are going to extend the attributes list beyond just ruid, but right now I'm struggling just to understanding how the XAVP should be built.. Ideas? Thanks, Andrew

2 1

during registration nonce expired, after backwards time shift
by Vasiliy Ganchev 03 Sep '15

03 Sep '15

Hi list! (sorry for sending first mail to wrong sub forum) Have a following issue: Server with Kamailio restart with wrong time (why - this is separate part of my investigations), timeshift e.g. for 2 hours in feature. After ntp daemon adjust correct time (move time backwards), Kamailio do not accept REGISTERs, pv_www_authenticate answer with code -4 (nonce expired) I've reade the description of: http://kamailio.org/docs/modules/4.2.x/modules/auth.html#auth.p.nonce_expire and http://kamailio.org/docs/modules/4.2.x/modules/auth.html#auth.p.nonce_auth_… This descriptions mention situation with backwards timeshift from future. As I understand, Kamailio do not authorise the registration, whose nonces where generated in future (before ntp shifted the time). But in my tests, Kamailio do not accept even REGISTER from UA, sent after time shift (with new nonces, that as I expected has to use correct time for nonce generation, and be authorised with no problem). Only Kamailio process restart help to cope with the issue. It looks like for nonce generating Kamailio use old time (in feature, that was before timeshift). I wander, does the Kamailio behave in described case - as is expected? If I am wrong in some of my assumptions, please point out. version: kamailio 4.2.5 Thank in advance! Cheers! -- View this message in context: http://sip-router.1086192.n5.nabble.com/during-registration-nonce-expired-a… Sent from the Users mailing list archive at Nabble.com.

2 12

[Kamailio 4.2] Crash during burn-in test
by Jack Wang 03 Sep '15

03 Sep '15

[Steps] 1. one MCU call multi-endpoints 2. MCU hangup all endpoints repeatedly. And all through Kamailio proxy. [Results] For a while, Kamailio crashed. Followings are related logs: ========================================== Sep 2 19:08:34 ./kamailio[3712]: : tm [t_fwd.c:1632]: t_send_branch(): BUG: t_send_branch: retr. already started for 0x41848fa0 Sep 2 19:08:34 ./kamailio[3712]: ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: Unfortunately error on sending to next hop occurred (477/SL) At this point the related behavior is that Kamailio received two INFO requests simultaneously. I wonder whether this is the cause. And maybe it's related to the later crash? Sep 2 19:08:35 ./kamailio[3713]: CRITICAL: <core> [pass_fd.c:293]: receive_fd(): EOF on 11 Sep 2 19:08:35 ./kamailio[3703]: ALERT: <core> [main.c:784]: handle_sigs(): child process 3704 exited by a signal 11 Sep 2 19:08:35 ./kamailio[3703]: ALERT: <core> [main.c:787]: handle_sigs(): core was generated Sep 2 19:08:35 ./kamailio[3703]: : <core> [mem/f_malloc.c:586]: fm_free(): BUG: fm_free: bad pointer 0x7239b6c4 (out of memory block!), called from tm: h_table.c: free_cell(157) - aborting Any suggestions? Thanks. ==========================================

2 1

Change caller id with Kamailio
by Michael Nielsen 02 Sep '15

02 Sep '15

The same way I can change called party id with $rU, is there also a way to change the caller id of the person making the call?

2 2

Add country code on incoming calls - if not present
by Michael Nielsen 02 Sep '15

02 Sep '15

I've added a custom column in my subscriber table in MySQL - called country_code. This contains +44 etc. for subscribers. Is it possible to, if a subscriber has not entered either + or 00, to append the value from country_code of the specific subscriber to the dialled number? And if the user has dialled 00, to replace it with +.

3 7

Kamailio TLS handshake fails above 6500 TLS connections
by Priyaranjan Nayak 02 Sep '15

02 Sep '15

Hi All, We are trying to make 10000 tls connection with Kamailio server for SIP signaling.When I try beyond 6500 TLS connection then TLS handshake is failing.We are running the kamailio by using below command - kamailio -f kamailio.cfg -N 40 -m 1024 -M 16 NOTE: In kamailio.cfg, we have mentioned tls_max_connections=60000 Could you please guide me, how can I improve the tls connections with kamailio ? Thanks Priyaranjan

2 1

Information
by Reaz Baksh 02 Sep '15

02 Sep '15

Hello I'm looking for information on setting SER up on Ubuntu. I have it installed along with rtpproxy but cannot get any info from this site as all documentation links are not working. What I want to do is to receive a input rtp live stream and restream it out to various TV's and decoders. Is this possible with SER ? Thanks Reaz

2 1

Re: [SR-Users] unsupported route_type 64
by Admin 02 Sep '15

02 Sep '15

Here is the output from "event_route[evapi:message-received]" Aug 30 13:18:49 everest /usr/local/kamailio/sbin/kamailio[3897]: INFO: <script>: Message received in evapi: {"Event":"CGR_AUTH_REPLY","TransactionIndex":39453,"TransactionLabel":1341515504,"MaxSessionTime":60,"Suppliers":"","Error":""} Aug 30 13:18:49 everest /usr/local/kamailio/sbin/kamailio[3897]: INFO: <script>: Event received in evapi: "CGR_AUTH_REPLY" Aug 30 13:19:00 everest /usr/local/kamailio/sbin/kamailio[3891]: ERROR: tmx [t_var.c:521]: pv_get_tm_reply_code(): unsupported route_type 64 Thanks.

3 2

OT: some github stuff
by Daniel-Constantin Mierla 01 Sep '15

01 Sep '15

Hello, wondering if people here can shed some light on few github things: 1) is possible to have a multi-line project description (the text at the top of https://github.com/kamailio/kamailio)? Maybe a special format (I tried to add \n or <br />, but they were displayed as is, not interpreted). I would like to add a short note and a link to a page with commit guidelines (http://www.kamailio.org/wiki/devel/github-contributions), so new contributors make proper formatted commits. Displying it at the top will make it easy to spot, as opposity to adding to readme, which is shown at the bottom. 2) is there any specific content/marker to add to README to have it interpreted as markdown (without adding .md extensions)? Something like a special first or last line, ... It will be displayed nicer, but renaming will result in changing lot of other places (makefiles, deb/rpm specs, etc...) and somehow README is the traditional approach for the kind of this file name for Linux/Unix apps. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com

3 5

Add PSTN gateway with authentication credentials
by Michael Nielsen 01 Sep '15

01 Sep '15

I'm trying to use a PSTN gateway with Kamailio for outbound - and incoming - calls. Everything seems to be routed correctly, except the PSTN gateway denies the call due to missing authentication. How do I add credentials for my PSTN gateway in a secure way? Best regards, Michael

3 6

blocking call in between two kamailio proxy
by sscc 01 Sep '15

01 Sep '15

i have configered kamailio with two domains sscc1.tk and sscc2.tk. it listen on both domains. each domain has users registered with it. user in domain sscc1 1 can call to user in domain sscc2. i want to allow call in between users of same domai. and block call between user of domain sscc1 to domain sscc2. please help -- View this message in context: http://sip-router.1086192.n5.nabble.com/blocking-call-in-between-two-kamail… Sent from the Users mailing list archive at Nabble.com.

3 6

authorize a client in bulk registration
by Al S 01 Sep '15

01 Sep '15

My PBX registered in bulk to Kamailio successfully.PBX --> Register --> kamailioPBX <-- 401 with nonce value <-- kamailioPBX --> Register with nonce and md5 response values --> kamailioBOX <-- 200ok <-- kamailioHowever, when one of the PBX client sends an invite out, kamailio AUTH module does not authorize this client:client (813-111-1111) --> Invite --> kamailio What would be the right way to authorize a 10-digit client to send a call out when a bulk registration and not 10-digit registration is performed. Your assistance in this matter is greatly appreciatedThanks,Al

3 3

Kamailio TLS configuration
by Alexandru Covalschi 30 Aug '15

30 Aug '15

Hello! I'm having problems with Kamailio configuration with TLS. Or, maybe, that's my misunderstanding about how it should work. So, the issue - inbound TLS works just great, I can call everyone in my domain. I have PositiveSSL certificate, so I have such files: calist.crt AddTrustExternalCARoot.crt + COMODORSAAddTrustCA.crt + COMODORSADomainValidationSecureServerCA.crt divided by \n server.key - key server.crt - cert The configuration of tls.cfg [server:default] method = SSLv23 verify_certificate = no require_certificate = no private_key = /etc/ssl/sectel.io.ssl/sip/server.key certificate = /etc/ssl/sectel.io.ssl/sip/server.crt ca_list = /etc/ssl/sectel.io.ssl/sip/calist.crt #crl = /etc/kamailio/crl.pem (however with or without ca_list nothing changes) [client:default] verify_certificate = yes require_certificate = yes And with that configuration when I'm trying to call to ostel.co (public SIP service supporting TLS) from my server I get such error: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS write:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed Putting that in tls.cfg: [client:default] verify_certificate = no require_certificate = no Make everything work. Cross-domain calling is essential and I'm just trying to figure out - what's the problem? Is that my certificate, is that ostel.co certificate or it is just the way it should be? Thanks! -- Alexandru Covalschi ABRISS-Solutions VoIP engineer and system administrator phone: +37367398493 web: http://abs-telecom.com/

3 8

Re: [SR-Users] unsupported route_type 64
by Admin 30 Aug '15

30 Aug '15

Thank you for responding to my post. Here it is. include_file "kamailio-cgrates.cfg" request_route { ... switch ($fU) { case 1001: case 1006: $dlg_var(cgrReqType) = "*prepaid"; break; case 1002: $dlg_var(cgrReqType) = "*postpaid"; break; case 1003: $dlg_var(cgrReqType) = "*pseudoprepaid"; break; default: $dlg_var(cgrReqType) = "*rated"; } $dlg_var(cgrTenant) = "cgrates.org"; $dlg_var(cgrAccount) = $fU; $dlg_var(cgrDestination) = $rU; route(CGRATES_AUTH_REQUEST); # Will be answered in CGRATES_AUTH_REPLY #route(CGRATES_LCR_REQUEST); exit; } # Here will land requests after processing them with CGRateS. # Call RELAY or other routes following this route route[CGRATES_AUTH_REPLY] { if $var(CgrError) != "" { xlog("CGR_AUTH_ERROR: $var(CgrError)"); sl_send_reply("503","CGR_ERROR"); exit; } if $var(CgrMaxSessionTime) != -1 { if $var(CgrMaxSessionTime) == 0 { // Not enough balance, do not allow the call to go through sl_send_reply("403","Insufficient credit"); exit; } else if !dlg_set_timeout("$var(CgrMaxSessionTime)") { sl_send_reply("503","CGR_MAX_SESSION_TIME_ERROR"); exit; } } if $var(CgrSuppliers) != "" { # Enforce the supplier variable to the first one received from CGRateS $dlg_var(cgrSupplier) = $(var(CgrSuppliers){s.select,0,,}); } route(RELAY); } ==================================================================== # kamailio-cgrates.cfg # Kamailio-CGRateS related route blocks # Called on new connection over evapi, should normally be the case of CGRateS engine event_route[evapi:connection-new] { $sht(cgrconn=>cgr) = $evapi(srcaddr) + ":" + $evapi(srcport); # Detect presence of at least one connection } # Called when the connection with CGRateS closes event_route[evapi:connection-closed] { $var(connClosed) = $evapi(srcaddr) + ":" + $evapi(srcport); if $sht(cgrconn=>cgr) == $var(connClosed) { $sht(cgrconn=>cgr) = $null; } } # Message received from CGRateS, dispatch it to own route event_route[evapi:message-received] { json_get_field("$evapi(msg)", "Event", "$var(Event)"); route($(var(Event){s.rm,"})); # String characters are kept by json_get_field, remove them here } # Called by Kamailio on new dialog event_route[dialog:start] { route(CGR_CALL_START); } # Called by Kamailio on dialog end event_route[dialog:end] { route(CGR_CALL_END); } # Called by Kamailio on local disconnect event_route[tm:local-request] { route(CGR_CALL_END); } # Send AUTH_REQUEST to CGRateS route[CGRATES_AUTH_REQUEST] { # Auth INVITEs with CGRateS if $sht(cgrconn=>cgr) == $null { sl_send_reply("503","Charging controller unreachable"); exit; } evapi_async_relay("{\"event\":\"CGR_AUTH_REQUEST\", \"tr_index\":\"$T(id_index)\", \"tr_label\":\"$T(id_label)\", \"cgr_reqtype\":\"$dlg_var(cgrReqType)\", \"cgr_tenant\":\"$dlg_var(cgrTenant)\", \"cgr_account\":\"$dlg_var(cgrAccount)\", \"cgr_destination\":\"$dlg_var(cgrDestination)\", \"cgr_setuptime\":\"$TS\", \"cgr_computelcr\":\"true\"}"); } # Process AUTH_REPLY from CGRateS route[CGR_AUTH_REPLY] { json_get_field("$evapi(msg)", "TransactionIndex", "$var(TransactionIndex)"); json_get_field("$evapi(msg)", "TransactionLabel", "$var(TransactionLabel)"); json_get_field("$evapi(msg)", "MaxSessionTime", "$var(MaxSessionTime)"); json_get_field("$evapi(msg)", "Suppliers", "$var(Suppliers)"); json_get_field("$evapi(msg)", "Error", "$var(Error)"); $var(id_index) = $(var(TransactionIndex){s.int}); $var(id_label) = $(var(TransactionLabel){s.int}); $var(CgrMaxSessionTime) = $(var(MaxSessionTime){s.int}); $var(CgrSuppliers) = $(var(Suppliers){s.rm,"}); $var(CgrError) = $(var(Error){s.rm,"}); t_continue("$var(id_index)", "$var(id_label)", "CGRATES_AUTH_REPLY"); # Unpark the transaction } # Send AUTH_REQUEST to CGRateS route[CGRATES_LCR_REQUEST] { # Auth INVITEs with CGRateS if $sht(cgrconn=>cgr) == $null { sl_send_reply("503","Charging controller unreachable"); exit; } evapi_async_relay("{\"event\":\"CGR_LCR_REQUEST\", \"tr_index\":\"$T(id_index)\", \"tr_label\":\"$T(id_label)\", \"cgr_tenant\":\"$dlg_var(cgrTenant)\", \"cgr_account\":\"$dlg_var(cgrAccount)\", \"cgr_destination\":\"$dlg_var(cgrDestination)\", \"cgr_setuptime\":\"$TS\"}"); } # Process LCR_REPLY from CGRateS route[CGR_LCR_REPLY] { json_get_field("$evapi(msg)", "TransactionIndex", "$var(TransactionIndex)"); json_get_field("$evapi(msg)", "TransactionLabel", "$var(TransactionLabel)"); json_get_field("$evapi(msg)", "MaxSessionTime", "$var(MaxSessionTime)"); json_get_field("$evapi(msg)", "Suppliers", "$var(Suppliers)"); json_get_field("$evapi(msg)", "Error", "$var(Error)"); $var(id_index) = $(var(TransactionIndex){s.int}); $var(id_label) = $(var(TransactionLabel){s.int}); $var(CgrMaxSessionTime) = $(var(MaxSessionTime){s.int}); $var(CgrSuppliers) = $(var(Suppliers){s.rm,"}); $var(CgrError) = $(var(Error){s.rm,"}); t_continue("$var(id_index)", "$var(id_label)", "CGRATES_AUTH_REPLY"); # Unpark the transaction } # CGRateS request for session disconnect route[CGR_SESSION_DISCONNECT] { json_get_field("$evapi(msg)", "HashEntry", "$var(HashEntry)"); json_get_field("$evapi(msg)", "HashId", "$var(HashId)"); json_get_field("$evapi(msg)", "Reason", "$var(Reason)"); jsonrpc_exec('{"jsonrpc":"2.0","id":1, "method":"dlg.end_dlg","params":[$(var(HashEntry){s.rm,"}), $(var(HashId){s.rm,"})]}'); #$jsonrpl($var(reply)); } # Inform CGRateS about CALL_START (start prepaid sessions loops) route[CGR_CALL_START] { if $sht(cgrconn=>cgr) == $null { xlog("Charging controller unreachable"); exit; } evapi_async_relay("{\"event\":\"CGR_CALL_START\", \"callid\":\"$dlg(callid)\", \"from_tag\":\"$dlg(from_tag)\", \"h_entry\":\"$dlg(h_entry)\", \"h_id\":\"$dlg(h_id)\", \"cgr_reqtype\":\"$dlg_var(cgrReqType)\", \"cgr_tenant\":\"$dlg_var(cgrTenant)\", \"cgr_account\":\"$dlg_var(cgrAccount)\", \"cgr_destination\":\"$dlg_var(cgrDestination)\", \"cgr_answertime\":\"$TS\", \"cgr_supplier\":\"$dlg_var(cgrSupplier)\"}"); } # Inform CGRateS about CALL_END (stop debit loops, perform accounting if desired in this way) route[CGR_CALL_END] { if $sht(cgrconn=>cgr) == $null { xlog("Charging controller unreachable"); exit; } $var(callDur) = $TS - $dlg(start_ts); evapi_async_relay("{\"event\":\"CGR_CALL_END\", \"callid\":\"$dlg(callid)\", \"from_tag\":\"$dlg(from_tag)\", \"cgr_reqtype\":\"$dlg_var(cgrReqType)\", \"cgr_tenant\":\"$dlg_var(cgrTenant)\", \"cgr_account\":\"$dlg_var(cgrAccount)\", \"cgr_destination\":\"$dlg_var(cgrDestination)\", \"cgr_answertime\":\"$dlg(start_ts)\", \"cgr_duration\":\"$var(callDur)\", \"cgr_supplier\":\"$dlg_var(cgrSupplier)\", \"cgr_disconnectcause\":\"$T_reply_code\"}"); }

2 1

presence_dialoginfo- first NOTIFY - force_dummy_dialog
by evoip＠ukr.net 29 Aug '15

29 Aug '15

||Hello, we use Kamailio 4.2 with Presence_DIALOGINFO module for BLF notifications (blinking lamps on phone panel). Since version 4.1 Kamailio has a new module parametr " modparam("presence_dialoginfo", "force_dummy_dialog", 1)" - this option generate first NOTIFY to Subscribed phone (without PUBLISH message) and it's lamps became GREEN ( <state>terminated</state>). Without this module parametr the first NOTIFY won't be sent to phone and lamps will stay turned off until first PUBLISH will be handled by presence server. The first NOTIFY sip message with xml body look like this: NOTIFY sip:1005@22.22.22.22:1120 SIP/2.0. To: <sip:1005@11.11.11.11>;tag=867246696. From: <sip:9095@11.11.11.11>;tag=495949c4c25d687c77ca707bd10a0818-5171. CSeq: 2 NOTIFY. Call-ID: 662126467-5060-6(a)BJC.BGI.E.CDD. Route: <sip:10.60.1.3;r2=on;lr=on>, <sip:11.11.11.11;r2=on;lr=on>. Content-Length: 272. User-Agent: kamailio (4.2.3 (x86_64/linux)). Max-Forwards: 70. Event: dialog. Subscription-State: active;expires=600. Content-Type: application/dialog-info+xml. . <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="1" ух state="full" entity="sip:9095@10.60.1.3"> <dialog direction="recipient"> <state>terminated</state> </dialog> </dialog-info> Especially pay attention on XML body. But for some SIP phones this xml body with state = terminated is not enough to turn the BLF lamp on. (for example Grandstream phones). It requires one more or two more fields: "dialog id", "call-id". <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="28" state="full" entity="sip:9093@10.60.1.3"> <dialog id="830b4fd4-c75d-1233-ca9f-0050569560f4" call-id="830b4fd4-c75d-1233-ca9f-0050569560f4" direction="recipient"> <state>terminated</state> </dialog> </dialog-info> The question is how to modify this first NOTIFY XML body message to add "dialog id" and "call-id" to </dialog>. For example latest Kamailio Kazoo fixed that already. :) Kind Regards Ewgeny

4 8

unsupported route_type 64
by Admin 29 Aug '15

29 Aug '15

Hi, I am running Kamailio (4.4.0-dev2 (x86_64/linux)) with cgrates real-time billing application. At the end of a basic call (prepaid to postpaid), I receive the following error: ERROR:tmx [t_var.c:521]:pv_get_tm_reply_code():unsupported route_type 64 8(6740) DEBUG:tmx [t_var.c:526]:pv_get_tm_reply_code():reply code is <0> What does route_type 64 mean? I checked the archive posts (FS#456) and seemed to be fixed in branch 4.1 (part of 4.1.5). Thanks.

2 1

Parser error when enabling siptrace functionality
by Asgaroth 28 Aug '15

28 Aug '15

Hi All, I have a strange issue occuring, when I enable the siptrace functionality within the routing logic, I begin to get a bunch of parser error as show below. Is this normal behaviour or, more than likely, am I doing something wrong? I enable siptrace as follows: request_route { route("InitialMessageChecks"); sip_trace(); setflag(22); ... } event_route[tm:local-request] { sip_trace(); ... } When I enable this functions in the routing logic, I begin to see alot of the following messages in the log file: ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 39) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021® #023ÄÔ#002 ÊÂÕ#035mùLàU{#002> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 39) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021® #023ÄÔ#002 ÊÂÕ#035mùLàUÞž#002> ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 35) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021® #023ÄÔ#002 ÊÂÕ#035mùLàU #011#003> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#006y|#023ÄN˜#036ÂÕ#035múLàUÅ±#012> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> INFO: <core> [parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP ERROR: <core> [parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg: message=<#002#020#002#021#023Ä#023Ä#012#007> Is there any way I can disable seeing these messages? What are these messages? Any thoughts are appreciated. Thanks

2 4

kamailio_fifo
by Sven Juhkam 28 Aug '15

28 Aug '15

After updating kamailio I get: ERROR: Error opening Kamailio's FIFO /var/run/kamailio/kamailio_fifo ERROR: Make sure you have the line 'modparam("mi_fifo", "fifo_name", "/var/run/kamailio/kamailio_fifo")' in your config ERROR: and also have loaded the mi_fifo module. Any solution? Best regards Sven

3 2

BLF state on register
by Loic Chabert 28 Aug '15

28 Aug '15

Hello everyone, I'm trying to reproduce BLF's asterisk fonctionnality with kamailio. With asterisk, on register, NOTIFY message has been sent to all suscribed users. So LED became green. How can i reproduce this function ? I have try to execute a "pua_set_publish()" on register route, but it's not work. My led stay "black", and no notify message has been sent. I have loaded presence, presence_xml, presence_mwi, presence_dialoginfo, pua, pua_dialoginfo, pua_usrloc. Any other module needed ? Thanks, Regards.

2 10

webrtc not working in different networks
by Achintha 28 Aug '15

28 Aug '15

Hi, I have configured kamailio 4.3.1 with mysql ,rtpproxy,websocket modules , then I tried to call through the two extensions using x-lite phone and get the capture. Call is connected. In that test rtp was going through the rtpproxy server, Then I configured jssip to test webrtc in this setup, call is connected I can communicate through the extensions both video and voice only in LAN. IN different networks call is connected but, voice is not hear (rtp not working). Kindly help me to configure this web rtc with kamailio. -- Best Regards.. Achintha

1 0

dmq_usrloc
by Kelvin Chua 28 Aug '15

28 Aug '15

is there any function to trigger replication? i enabled the module and dmq is working for my htables but usrloc is not replicating. "kamctl ul show" does not show anything i used ngrep to trace the KDMQ packets, i can see the frequent exchanges but nothing related to usrloc. am i doing something wrong? Kelvin Chua

3 13

multiple proxies
by Bruce Lefko 27 Aug '15

27 Aug '15

If I want to have multiple kamailio proxies in front of multiple media servers, can I balance them using plain old DNS behind a domain name? If I wanted a specific proxy to be notified about an entire SIP dialog I could set the record route to use the public IP of the proxy that received the initial INVITE. Could I leverage something like route53 tcp healthchecks to know if I should be failing over to another proxy?

3 2

multiple proxies
by Bruce Lefko 27 Aug '15

27 Aug '15

If I want to have multiple kamailio proxies in front of multiple media servers, can I balance them using plain old DNS behind a domain name? If I wanted a specific proxy to be notified about an entire SIP dialog I could set the record route to use the public IP of the proxy that received the initial INVITE. Could I leverage something like route53 tcp healthchecks to know if I should be failing over to another proxy?

1 0

kamailio presence server using db_mongodb as database
by José Seabra 27 Aug '15

27 Aug '15

Hello all, I would like to test my presence server using db_mongodb as database server instead of using mysql, but i don't find any documentation explaining how i can configure mongodb database(data structure) for presence or even for the other kamailio modules. Can someone guide me in this setup? Best Regards -- Cumprimentos José Seabra

2 12

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