January 2017 - sr-users

ds_is_from_list and NAPTR / SRV
by Björn Bylander 19 Jan '17

19 Jan '17

Hello, I’m trying to resolve an issue with the ds_is_from_list function from the dispatcher module. I’m calling it as follows: ds_is_from_list(”42”, "3", "sip:sip.foo.bar”) This makes Kamailio log an error: ERROR: dispatcher [dispatch.c:2327]: ds_is_addr_from_list(): could not resolve sip.foo.bar sip.foo.bar doesn’t have any A records but there are NAPTR and SRV records: $ host -t naptr sip.foo.bar sip.foo.bar has NAPTR record 20 0 "s" "SIP+D2T" "" _sip._tcp.sip.foo.bar. sip.foo.bar has NAPTR record 10 0 "s" "SIP+D2U" "" _sip._udp.sip.foo.bar. $ host -t srv _sip._tcp.sip.foo.bar _sip._tcp.sip.foo.bar has SRV record 10 0 5060 sip1.foo.bar. _sip._tcp.sip.foo.bar has SRV record 10 0 5060 sip2.foo.bar. $ host -t srv _sip._udp.sip.foo.bar _sip._udp.sip.foo.bar has SRV record 10 0 5060 sip2.foo.bar. _sip._udp.sip.foo.bar has SRV record 10 0 5060 sip1.foo.bar. $ host sip1.foo.bar. sip1.foo.bar has address 10.47.11.1 $ host sip2.foo.bar. sip2.foo.bar has address 10.47.11.2 The following DNS options are set: dns_srv_lb = yes dns_try_naptr = yes dns_naptr_ignore_rfc = no The Kamailio version is 4.2.8 (installed from the Debian binary package) on Debian Wheezy. Shouldn’t ds_is_from_list be able to resolve the NAPTR and SRV records? Can I change anything to be able to use ds_is_from_list with the specified domain? Thanks, Björn Bylander

2 1

Upgrade from 4.3 to 4.4
by Laura 18 Jan '17

18 Jan '17

Dear list, I'm planning the upgrade fromn 4.3.6 tree to 4.4.x version on Debian distribution. Can i run the apt-get update and upgrade without problem.. or is possible that i will found some error during upgrade ? Is the db schema upgraded or not from 4.3 up to 4.4 ? Regards Laura

2 1

Please explain : t_relay() vs t_relay_to_udp()
by Abdoul Osséni 18 Jan '17

18 Jan '17

hello all, I want to use kamailio like as a proxy SIP (outbound proxy) to transcode tls to udp like us: call flow is: Softphone --> tls --> Kamailio server (kamailio listen on 443 port) --> udp --> Asterisk server (asterisk listen on 5060 port) I know Kamailio can convert tls to udp. According tm documentation http://kamailio.org/docs/modules/devel/modules/tm.html, I think I must use t_relay_to_udp(). Do you confirm I must replace t_relay() function by t_relay_to_udp() function? Thank for your help. Regards Abdoul.

2 2

Re: [SR-Users] Kamailio not processing SIP TCP
by JR Richardson 18 Jan '17

18 Jan '17

Yes, this is a sipcapture node. I'm listening on a switch port that is set to mirror my VoIP traffic. I see all SIP UDP/TCP packets on the mirror port and the Ethernet port of the host node. Just don't see any TCP packets process in kamailio, debug 3. UDP packets are processed as expected. My config is using port mirror for the capture parameters: modparam("sipcapture", "capture_on", 1) modparam("sipcapture", "hep_capture_on", 0) modparam("sipcapture", "raw_ipip_capture_on", 0) modparam("sipcapture", "raw_moni_capture_on", 1) modparam("sipcapture", "raw_sock_children", 4) modparam("sipcapture", "raw_interface", "eth1") modparam("sipcapture", "raw_socket_listen", "10.99.99.99:5060-5070") modparam("sipcapture", "promiscious_on", 1) modparam("sipcapture", "raw_moni_bpf_on", 1) Is there a method I could diagnose if the SIP TCP Packets are getting from the kernel network process and the kamailio process? # ngrep -d eth1 -W byline host x.x.x.x | /var/run/kamailio/kamailio.pid Or pipe to kamailio local unix socket? I don't know, I'm just guessing. Thanks. JR > Somehow is not clear for me how you have the configuration there ... > before commenting further, this needs to be clarified. > > The node you presented the config is a sipcapture instance, right? What > is sending traffic to it? Is another kamailio with siptrace module? Or > the sipcature agent? Or you have a port mirroring in the router? > > Cheers, > Daniel > > > On 17/01/2017 16:37, JR Richardson wrote: >>> On Mon, Jan 16, 2017 at 10:29:39AM -0600, JR Richardson wrote: >>>> Yes, I'm familiar with the methods sipcapture uses, I don't use HEP, >>>> using raw socket capture, I think this may be a sipcapture issue, >>>> debuging kamailio shows normal startup and processing of UDP SIP >>>> packets, but does not show any activity with TCP packets. >>> I never used HOMER sofar but when I saw your first message my thoughts >>> was that this can't work in a simple way since for TCP you need to >>> complete a 4 way handshake before you can start to send data. >>> >> Interesting. Are you referring to handshaking on the network stack or >> SIP TCP TLS handshaking? I guess I can see it two ways. >> >> 1) if your talking about TCP/IP handshake, even though the SIP packet >> comes into the mirror port on the host node, the kernel processing the >> TCP packet is not establishing a valid connection due to no TCP >> handshake because its only a monitor port, no transmit back, then the >> kernel network stack does not pass the SIP TCP packet to the kamailio >> process for capture because it drops the packet due to no valid >> handshake? >> >> 2) the kernel network stack is passing the SIP TCP packet to the >> kamailio process, but since kamailio cannot handshake back it drops >> the packet and does not process through the sipcapture module. This >> kinda breaks the whole capture ability for homer with SIP TCP. Using >> ngrep, I see all SIP TCP packets, invite -->, trying <--, session >> progress <--, request timeout <--, ack -->, etc... >> >> So how would I diagnose if the network stack is the culprit? Debugging >> kamailio is pretty straight forward, setup and listening for SIP TCP, >> but never see any processing of any TCP packets. >> >> Thanks. >> >> JR > -- JR Richardson Engineering for the Masses Chasing the Azeotrope

2 1

Kamailio v4.4.5 Released
by Daniel-Constantin Mierla 18 Jan '17

18 Jan '17

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

1 0

Planning the release of v4.4.5
by Daniel-Constantin Mierla 18 Jan '17

18 Jan '17

Hello, I am considering to release v4.4.5 with latest fixes from branch 4.4 later this week, on Wednesday or Thursday (Jan 19 or 20). As usual, if anyone has fixes that were not backported yet, do it if you are a developer or write to sr-dev to be sure it is not missed. Sumbit also the new issues you are ware of and they are not on the bug tracker. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com

1 1

Record-Route Header Question
by Andres 17 Jan '17

17 Jan '17

Hi, I am troubleshooting some strange call setup problems using an Edgewater Networks SBC. A couple of Polycom phones sit behind the SBC and they connect to a SIP Server in the cloud. The SBC is in passthrough mode. What I see that I am not sure about is: INVITE from SIP Server to SBC IP (no Record-Route header...so far no surprise here) INVITE from SBC to Phone (Record-Route header inserted by SBC but with the IP of the SIP Server) I do not think the SBC is supposed to add a Record-Route header with the IP of the remote SIP Server. I think It should only be allowed to add Record-Route headers with its own IP. Does that sound right? The RFC lists the usage as: "20.30 Record-Route The Record-Route header field is inserted by proxies in a request to force future requests in the dialog to be routed through the proxy." It says nothing about being able to arbitrarily force future requests to go through a remote IP. Please advise. Thanks, -- Technical Support

2 2

Re: [SR-Users] Kamailio not processing SIP TCP
by JR Richardson 17 Jan '17

17 Jan '17

> On Mon, Jan 16, 2017 at 10:29:39AM -0600, JR Richardson wrote: >> Yes, I'm familiar with the methods sipcapture uses, I don't use HEP, >> using raw socket capture, I think this may be a sipcapture issue, >> debuging kamailio shows normal startup and processing of UDP SIP >> packets, but does not show any activity with TCP packets. > > I never used HOMER sofar but when I saw your first message my thoughts > was that this can't work in a simple way since for TCP you need to > complete a 4 way handshake before you can start to send data. > Interesting. Are you referring to handshaking on the network stack or SIP TCP TLS handshaking? I guess I can see it two ways. 1) if your talking about TCP/IP handshake, even though the SIP packet comes into the mirror port on the host node, the kernel processing the TCP packet is not establishing a valid connection due to no TCP handshake because its only a monitor port, no transmit back, then the kernel network stack does not pass the SIP TCP packet to the kamailio process for capture because it drops the packet due to no valid handshake? 2) the kernel network stack is passing the SIP TCP packet to the kamailio process, but since kamailio cannot handshake back it drops the packet and does not process through the sipcapture module. This kinda breaks the whole capture ability for homer with SIP TCP. Using ngrep, I see all SIP TCP packets, invite -->, trying <--, session progress <--, request timeout <--, ack -->, etc... So how would I diagnose if the network stack is the culprit? Debugging kamailio is pretty straight forward, setup and listening for SIP TCP, but never see any processing of any TCP packets. Thanks. JR -- JR Richardson Engineering for the Masses Chasing the Azeotrope

2 1

Using the auth_ephemeral module
by Hemanshu Vadehra 17 Jan '17

17 Jan '17

I'm involved in setting up a Kamailio instance and was hoping to make use of the auth_ephemeral module for authentication. But the module documentation doesn't quite make clear how exactly the module is to be employed or the web service set up. Does anyone have a working example? Regards, Hemanshu Vadehra hemanshu.v(a)directi.com

5 8

usrloc module with dbmode=2 does not insert records to database
by Vik Killa 17 Jan '17

17 Jan '17

Hello, we've noticed that the usrloc module does not "sync" all the records from memory into the database. I use a bash script to generate in-memory AoRs ( http://paste.debian.net/plain/908521) then i perform kamcmd ul.flush and no records are inserted. We have tried various usrloc parameters but none seem to work Here is our basic setup # ----- usrloc params ----- modparam("usrloc", "db_url", DBURL) modparam("usrloc", "db_mode", 2) modparam("usrloc", "use_domain", 1) modparam("usrloc", "timer_interval", 120) modparam("usrloc", "timer_procs", 4) We are using postgresql. are we missing something? Thanks /V

2 11