[SR-Users] kamailio asterisk

Slava Bendersky volga629 at networklab.ca
Wed Feb 25 15:47:37 CET 2015 

Hello Daniel, 
I found this bug report 

http://sourceforge.net/p/openser/bugs/226/ 

Is this still valid ? 

Slava. 



From: "Slava Bendersky" <volga629 at networklab.ca> 
To: miconda at gmail.com 
Cc: "sr-users" <sr-users at lists.sip-router.org> 
Sent: Wednesday, February 25, 2015 9:11:54 AM 
Subject: Re: [SR-Users] kamailio asterisk 

Hello Everyone, 

Feb 25 09:12:33 canlvprx01 kamailio: 11(4104) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio-asterisk.cfg] l=506 a=25 n=subst_uri 
Feb 25 09:12:33 canlvprx01 kamailio: 11(4104) DEBUG: <core> [re.c:448]: subst_run(): subst_run: running. r=1 
Feb 25 09:12:33 canlvprx01 kamailio: 11(4104) DEBUG: <core> [re.c:517]: subst_str(): subst_str: no match 

I tried something like 

if (proto==TLS) 
{ 
#subst_uri('/^sips.+)$/sip:\1/'); 
subst("/sips:/sip:/g"); 
} 

but there some cases where client use ;transport=TLS which need remove too. 

Slava 



From: "Daniel-Constantin Mierla" <miconda at gmail.com> 
To: "Slava Bendersky" <volga629 at networklab.ca>, "sr-users" <sr-users at lists.sip-router.org> 
Sent: Wednesday, February 25, 2015 5:44:53 AM 
Subject: Re: [SR-Users] kamailio asterisk 

Hello, 

change the r-uri to use sip instead of sips. 

You can try with: 

subst_uri('/^sips:(.+)$/ sip:\1/ '); 

Cheers, 
Daniel! 

On 25/02/15 01:14, Slava Bendersky wrote: 



Hello Everyone, 
I wonder in my case why kamailio is not bridging between TLS and UDP ? Is there additional configuration required ? 

Slava. 


From: "Slava Bendersky" <volga629 at networklab.ca> 
To: miconda at gmail.com 
Cc: "sr-users" <sr-users at lists.sip-router.org> 
Sent: Tuesday, February 24, 2015 11:42:02 AM 
Subject: Re: [SR-Users] kamailio asterisk 

Hello Everyone, 
Here link to core dump bt full. 

http://fpaste.org/189799/79603014/ 

password the same 

Slava. 


From: "Daniel-Constantin Mierla" <miconda at gmail.com> 
To: "volga629" <volga629 at skillsearch.ca> , "Slava Bendersky" <volga629 at networklab.ca> , "sr-users" <sr-users at lists.sip-router.org> 
Sent: Monday, February 23, 2015 3:56:48 AM 
Subject: Re: [SR-Users] kamailio asterisk 

You don't need to run kamailio through gdb. If it crashes, then you get 
a corefile -- in the logs it says the name of the file. It is usually 
located in / or in the path you gave to -w parameter. 

After you reproduced the crash, locate the corefile and run gdb like: 

gdb /path/to/kamailio /path/to/corefile 
bt full 

The /path/to/kamailio should be /usr/sbin/kamailio if you installed from 
rpms. 

If you have improvements to init or sysconfig kamailio file, send a 
patch and we will include the changes in kamailio repository. 

Cheers, 
Daniel 

On 23/02/15 01:00, Slava Bendersky wrote: 
> Hello Everyone, 
> I upgraded to 4.2.3 version, but crash still there. What is my options to meet case like this. 
> 
> Client TLS -------> KAMAILIO Proxy ------ UDP/TCP ----> asterisk 
> | 
> | 
> Public Private 
> 
> I will try try run gdb to get backtrace on crash. 
> Also here link for Fedora 21 server rpms. There are couple small fixes for init file and sysconfig/kamailio 
> 
> http://ftpsrv01.networklab.ca/fedora/21/RPMS/x86_64/ 
> 
> Slava. 
> 
> Sent from mobile device typos are expected. 
> 
> From: Daniel-Constantin Mierla <miconda at gmail.com> 
> Sent: Feb 22, 2015 5:34 PM 
> To: Slava Bendersky <volga629 at networklab.ca> ;sr-users 
> Subject: Re: [SR-Users] kamailio asterisk 
> 
> 
> 
> Hello, 
> 
> looking at the logs, the process routing the register is forwarding it, 
> by opening a tls connection -- that is because the uri has sips as schema. 
> 
> The crash is reported in another process that doesn't print much logs 
> messages. As Olle suggested, can you get the backtrace with gdb from the 
> core file? That will help to see where the crash happened. 
> 
> gdb /path/to/kamailio /path/to/corefile 
> bt full 
> 
> And again, it would be good to upgrade to 4.2.3 -- it is same config and 
> database, just install new version and restart. In this way we rule out 
> issues that were fixed already, avoiding to spend time on something fixed. 
> 
> Cheers, 
> Daniel 
> 
> On 20/02/15 15:03, Slava Bendersky wrote: 
>> Hello Everyone, 
>> Thank you for reply, 
>> On client I configured user @ domain.org and proxy point to kamailio 
>> Here 1 debug where on client after doamin.org port is left configured 
>> to 5061 
>> 
>> http://fpaste.org/188145/44047614/ 
>> 
>> Second debug where port set to 0 and kamailio tries resolve and crashed 
>> 
>> http://fpaste.org/188148/24440702/ 
>> 
>> Here config file 
>> 
>> http://fpaste.org/188149/24440841/ 
>> 
>> 
>> Thank you, 
>> Slava. 
>> 
>> 
>> ------------------------------------------------------------------------ 
>> *From: *"Olle E. Johansson" <oej at edvina.net> 
>> *To: *"Daniel Constantin Mierla" <miconda at gmail.com> , "sr-users" 
>> <sr-users at lists.sip-router.org> 
>> *Sent: *Thursday, February 19, 2015 4:34:04 AM 
>> *Subject: *Re: [SR-Users] kamailio asterisk 
>> 
>> We also need to check the core file from the crash. 
>> /O 
>> On 19 Feb 2015, at 09:30, Daniel-Constantin Mierla < miconda at gmail.com 
>> <mailto:miconda at gmail.com> > wrote: 
>> 
>> Hello, 
>> 
>> can you send the REGISTER request received by kamailio and your 
>> config to me? 
>> 
>> As you receive it over TLS, you can get the register by adding the 
>> next line in kamailio.cfg at the beginning of request_route: 
>> 
>> xlog("received request: [[$mb]]\n"); 
>> 
>> I will like to double check if the issue is still present. 
>> 
>> You should upgrade to 4.2.3, because it is the latest stable, you 
>> have 4.2.1 and there were many fixes meanwhile. 
>> 
>> If you preserve sips as uri schema, then you force tls further for 
>> forwarding. You should change that to sip:domain ... 
>> 
>> Cheers, 
>> Daniel 
>> 
>> On 18/02/15 00:37, Slava Bendersky wrote: 
>> 
>> Hello Everyone, 
>> I have standard case where kamailio play role of proxy for 
>> asterisk servers. 
>> Kamailio configured use TLS transport on public side and on 
>> private side UDP 5060. 
>> When client (SIP soft phone) connect to TLS socket everything 
>> goes well until kamailio trying forward request. Kamailio 
>> tries DNS resolve tls transport srv records instead of udp 
>> then it just crashed when no tls configured on private side of 
>> kamailio. 
>> 
>> Do I need manually fix sips in URI ? Or some different miss 
>> configuration ? 
>> 
>> 
>> [root at canlvprx01 kamailio]# rpm -qa | grep kamail 
>> kamailio-carrierroute-4.2.1-4.2.fc21.x86_64 
>> kamailio-mysql-4.2.1-4.2.fc21.x86_64 
>> kamailio-outbound-4.2.1-4.2.fc21.x86_64 
>> kamailio-4.2.1-4.2.fc21.x86_64 
>> kamailio-tls-4.2.1-4.2.fc21.x86_64 
>> 
>> 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> 
>> [parser/msg_parser.c:625]: parse_msg(): method: <REGISTER> 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> 
>> [parser/msg_parser.c:627]: parse_msg(): uri: 
>> <sips:domain.org> ---> Client come with TLS transport 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> 
>> [parser/msg_parser.c:629]: parse_msg(): version: <SIP/2.0> 
>> 
>> 
>> 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> 
>> [socket_info.c:583]: grep_sock_info(): grep_sock_info - 
>> checking if host==us: 13==12 && [domain.org 
>> <http://domain.org> ] == [10.18.130.46 <callto:10.18.130.46> ] 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> 
>> [socket_info.c:587]: grep_sock_info(): grep_sock_info - 
>> checking if port 5060 (advertise 0) matches port 5060 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> 
>> [socket_info.c:583]: grep_sock_info(): grep_sock_info - 
>> checking if host==us: 13==11 && [domain.org 
>> <http://domain.org> ] == [67.34.12.56] 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> 
>> [socket_info.c:587]: grep_sock_info(): grep_sock_info - 
>> checking if port 5081 (advertise 0) matches port 5060 
>> Feb 17 11:13:49 canlvprx01 kernel: [4130713.518667] 
>> kamailio[22484]: segfault at 88 ip 00000000004bd30c sp 
>> 00007fffa2f73a20 error 4 in kamailio[400000+3b8000] 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> 
>> [forward.c:448]: check_self(): check_self: host != me 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) ERROR: *** 
>> cfgtrace:request_route=[SIPOUT] 
>> c=[/etc/kamailio/kamailio-asterisk.cfg] l=850 a=25 n=append_hf 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) ERROR: *** 
>> cfgtrace:request_route=[SIPOUT] 
>> c=[/etc/kamailio/kamailio-asterisk.cfg] l=851 a=5 n=route 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) ERROR: *** 
>> cfgtrace:request_route=[RELAY] 
>> c=[/etc/kamailio/kamailio-asterisk.cfg] l=567 a=16 n=if 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) ERROR: *** 
>> cfgtrace:request_route=[RELAY] 
>> c=[/etc/kamailio/kamailio-asterisk.cfg] l=563 a=25 n=is_method 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) ERROR: *** 
>> cfgtrace:request_route=[RELAY] 
>> c=[/etc/kamailio/kamailio-asterisk.cfg] l=571 a=16 n=if 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) ERROR: *** 
>> cfgtrace:request_route=[RELAY] 
>> c=[/etc/kamailio/kamailio-asterisk.cfg] l=567 a=25 n=is_method 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) ERROR: *** 
>> cfgtrace:request_route=[RELAY] 
>> c=[/etc/kamailio/kamailio-asterisk.cfg] l=574 a=16 n=if 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) ERROR: *** 
>> cfgtrace:request_route=[RELAY] 
>> c=[/etc/kamailio/kamailio-asterisk.cfg] l=571 a=24 n=t_relay 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: tm 
>> [t_lookup.c:1373]: t_newtran(): DEBUG: t_newtran: msg id=1 , 
>> global msg id=1 , T on entrance=(nil) 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: tm 
>> [t_lookup.c:527]: t_lookup_request(): t_lookup_request: start 
>> searching: hash=48550, isACK=0 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: tm 
>> [t_lookup.c:485]: matching_3261(): DEBUG: RFC3261 transaction 
>> matching failed 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: tm 
>> [t_lookup.c:709]: t_lookup_request(): DEBUG: t_lookup_request: 
>> no transaction found 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: tm 
>> [t_hooks.c:380]: run_reqin_callbacks_internal(): DBG: 
>> trans=0x7f598a9ced40, callback type 1, id 0 entered 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: tm 
>> [t_hooks.c:380]: run_reqin_callbacks_internal(): DBG: 
>> trans=0x7f598a9ced40, callback type 1, id 0 entered 
>> Feb 17 11:13:49 canlvprx01 kernel: kamailio[22484]: segfault 
>> at 88 ip 00000000004bd30c sp 00007fffa2f73a20 error 4 in 
>> kamailio[400000+3b8000] 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> 
>> [md5utils.c:67]: MD5StringArray(): DEBUG: MD5 calculated: 
>> 0475e0d0dd9778e889618cb724403b4d 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> 
>> [dns_cache.c:566]: _dns_hash_find(): 
>> dns_hash_find(_sips._tcp.networklab.ca 
>> <http://tcp.networklab.ca> (24), 33), h=646 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> 
>> [resolve.c:967]: get_record(): get_record: skipping 1 NS 
>> (p=0xa1f556, end=0xa1f588) 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> 
>> [resolve.c:983]: get_record(): get_record: parsing 2 ARs 
>> (p=0xa1f568, end=0xa1f588) 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> 
>> [dns_cache.c:1772]: dns_get_related(): 
>> dns_get_related(0x7f598a9e89b0 (_sips._tcp.domain.org 
>> <http://tcp.domain.org> , 33), 33, *0x7f5995bd55e0) (0) 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> 
>> [dns_cache.c:869]: dns_cache_add_unsafe(): dns_cache_add: 
>> adding _sips._tcp.domain.org <http://tcp.domain.org> (24) 33 
>> (flags=0) at 646 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> 
>> [dns_cache.c:869]: dns_cache_add_unsafe(): dns_cache_add: 
>> adding camsgsrv02.domain.org 
>> <http://camsgsrv02.domain.org> (24) 1 (flags=0) at 967 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> 
>> [dns_cache.c:566]: _dns_hash_find(): 
>> dns_hash_find(camsgsrv02.domain.org 
>> <http://camsgsrv02.domain.org> (24), 1), h=967 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> 
>> [msg_translator.c:2871]: create_via_hf(): create_via_hf: id 
>> added: <;i=1>, rcv proto=3 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> 
>> [tcp_main.c:1818]: tcp_send(): tcp_send: no open tcp 
>> connection found, opening new one 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> 
>> [ip_addr.c:243]: print_ip(): tcpconn_new: new tcp connection: 
>> 10.18.130.50 <callto:10.18.130.50> 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> 
>> [tcp_main.c:1073]: tcpconn_new(): tcpconn_new: on port 5061, 
>> type 3 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> 
>> [tcp_main.c:1382]: tcpconn_add(): tcpconn_add: hashes: 3263:0:0, 2 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) WARNING: <core> 
>> [tcp_main.c:1221]: tcp_do_connect(): 10.18.130.50 
>> <callto:10.18.130.50> :5061: could not find corresponding 
>> listening socket for 10.18.130.46 <callto:10.18.130.46> , using 
>> default... 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: tls 
>> [tls_server.c:184]: tls_complete_init(): Using TLS domain 
>> TLSc<default> 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: tls 
>> [tls_domain.c:700]: sr_ssl_ctx_info_callback(): SSL handshake 
>> started 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: <core> 
>> [tcp_main.c:2697]: tcpconn_1st_send(): pending write on new 
>> connection 0x7f598a9d4678 (-1/129 bytes written) 
>> Feb 17 11:13:49 canlvprx01 kamailio: 15(22484) DEBUG: <core> 
>> [tcp_main.c:3565]: handle_ser_child(): handle_ser_child: read 
>> response= 7f598a9d4678, 5, fd 31 from 11 (22480) 
>> Feb 17 11:13:49 canlvprx01 kamailio: 15(22484) DEBUG: <core> 
>> [io_wait.h:388]: io_watch_add(): DBG: io_watch_add(0x9daf00, 
>> 31, 2, 0x7f598a9d4678), fd_no=19 
>> Feb 17 11:13:49 canlvprx01 kamailio: 11(22480) DEBUG: tm 
>> [t_funcs.c:394]: t_relay_to(): SER: new transaction fwd'ed 
>> 
>> 
>> 
>> Thank you Slava. 
>> 
>> 
>> _______________________________________________ 
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list 
>> sr-users at 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 
>> Kamailio World Conference, May 27-29, 2015 
>> Berlin, Germany - http://www.kamailioworld.com 
>> 
>> _______________________________________________ 
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing 
>> list 
>> sr-users at lists.sip-router.org <mailto:sr-users at lists.sip-router.org> 
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users 
>> 
>> 
>> 
>> _______________________________________________ 
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list 
>> sr-users at 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 
Kamailio World Conference, May 27-29, 2015 
Berlin, Germany - http://www.kamailioworld.com 

_______________________________________________ 
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list 
sr-users at 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 Kamailio World Conference, May 27-29, 2015
Berlin, Germany - http://www.kamailioworld.com 


_______________________________________________ 
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list 
sr-users at lists.sip-router.org 
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20150225/ea76baa3/attachment.html>

More information about the sr-users mailing list