sr-users

sr-users@lists.kamailio.org

42 participants
37519 discussions

PKG and Shared Memory statistics
by Dirk Teurlings Signet B.V. 17 Mar '15

17 Mar '15

Hi, We'd like to be able to get statistics of the used amount of memory in Kamailio. # kamctl stats shmem The above command only tells us what the shared memory is doing. Is there any way to get the committed size of memory for each of the PKG_MEMORY pools? If not, could this be added at some point? Kind regards, -- Dirk Teurlings

3 3

Deleted Domain
by Eric Fetty 17 Mar '15

17 Mar '15

Hi, I accidently deleted my domain from iptel.org. I went to re-create my account and it will not let me. Domain: kingfetty.com

2 1

478/sl and 478/sm on BYE?
by Don Fanning 17 Mar '15

17 Mar '15

I am getting these both when one end of the client sends a BYE - after the other client has already sent a BYE and got a 200 back. Config: http://pastebin.com/5gcFpJ3m /usr/local/sbin/kamailio[3259]: INFO: <script>: Request in RELAY - call is {<null>} for {1070} /usr/local/sbin/kamailio[3259]: INFO: <script>: sip:1070@df7jal23ls0d.invalid /usr/local/sbin/kamailio[3259]: ERROR: <core> [resolve.c:1726]: sip_hostport2su(): could not resolve hostname: "df7jal23ls0d.invalid" /usr/local/sbin/kamailio[3259]: ERROR: <core> [forward.c:531]: forward_request(): bad host name df7jal23ls0d.invalid, dropping packet /usr/local/sbin/kamailio[3259]: ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: Unresolvable destination (478/SL)

2 3

Re: [SR-Users] [RTPproxy] Re: [OpenSIPS-Users] Announcing rtpproxy v2.0.0
by Maxim Sobolev 17 Mar '15

17 Mar '15

Do you have any particular RFC in mind? On Mar 12, 2015 10:28 AM, "John Mathew" <john.mathew(a)divoxmedia.com> wrote: > Hi, > > Maxim, > Is there any plans for rtp header compression in future. I can't see > anything in the change log for 2.0.0 > > On Tuesday, 10 March 2015, Maxim Sobolev <sobomax(a)sippysoft.com> wrote: > >> Hi All, >> >> I'm happy to announce that we have released rtpproxy v2.0.0. >> >> You can review the release notes here: >> https://github.com/sippy/rtpproxy/releases/tag/v2.0.0 >> >> -sobomax >> >> > > -- > Sent from iPhone 6 > > -- > You received this message because you are subscribed to the Google Groups > "rtpproxy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to rtpproxy+unsubscribe(a)googlegroups.com. > To post to this group, send email to rtpproxy(a)googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/rtpproxy/CA%2BSkwpUhu9fpwmqpRFiaXsQo9_%2B… > <https://groups.google.com/d/msgid/rtpproxy/CA%2BSkwpUhu9fpwmqpRFiaXsQo9_%2B…> > . > For more options, visit https://groups.google.com/d/optout. >

2 1

Kamailio IMS: can not register
by dfretes＠ing.una.py 16 Mar '15

16 Mar '15

Hi all. I'm trying to setup Kamailio for IMS server, but I've reached a point where I can not move. Trying to register from the Boghe client, I get these errors from the pcscf: tail -f /var/log/syslog|grep './pcscf' Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[DE FAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=402 a=25 n=xlog Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: <script>: REGISTER (sip:alice@ open-ims.test (192.168.1.105:62044) to sip:alice@open-ims.test, 20236156-7eed-01 e4-daac-5072e67f99e9) Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[DE FAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=414 a=5 n=route Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE QINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=594 a=16 n=if Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE QINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=576 a=24 n=has_totag Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE QINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=584 a=16 n=if Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE QINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=590 a=16 n=if Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE QINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=584 a=24 n=pike_check_req Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE QINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=606 a=16 n=if Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE QINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=611 a=16 n=if Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE QINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=606 a=25 n=mf_process_maxfwd_heade r Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE QINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=617 a=16 n=if Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE QINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=611 a=26 n=sanity_check Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE QINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=623 a=16 n=if Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE QINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=617 a=24 n=has_totag Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE QINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=629 a=16 n=if Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE QINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=623 a=25 n=is_method Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE QINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=633 a=16 n=if Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE QINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=629 a=24 n=t_lookup_request Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE QINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=636 a=16 n=if Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE QINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=633 a=25 n=is_method Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE QINIT] c=[/etc/kamailio/pcscf/kamailio.cfg] l=634 a=26 n=send_reply Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[DE FAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=417 a=5 n=route Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[NA T] c=[/etc/kamailio/pcscf/kamailio.cfg] l=673 a=55 n=force_rport Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[NA T] c=[/etc/kamailio/pcscf/kamailio.cfg] l=694 a=16 n=if Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[NA T] c=[/etc/kamailio/pcscf/kamailio.cfg] l=675 a=25 n=nat_uac_test Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[NA T] c=[/etc/kamailio/pcscf/kamailio.cfg] l=679 a=16 n=if Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[NA T] c=[/etc/kamailio/pcscf/kamailio.cfg] l=676 a=25 n=is_method Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[NA T] c=[/etc/kamailio/pcscf/kamailio.cfg] l=679 a=39 n=setflag Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[NA T] c=[/etc/kamailio/pcscf/kamailio.cfg] l=687 a=16 n=if Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[NA T] c=[/etc/kamailio/pcscf/kamailio.cfg] l=680 a=25 n=is_method Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[NA T] c=[/etc/kamailio/pcscf/kamailio.cfg] l=681 a=24 n=set_contact_alias Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[NA T] c=[/etc/kamailio/pcscf/kamailio.cfg] l=683 a=26 n=xlog Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[NA T] c=[/etc/kamailio/pcscf/kamailio.cfg] l=684 a=24 n=nat_keepalive Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[NA T] c=[/etc/kamailio/pcscf/kamailio.cfg] l=694 a=2 n=return Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[DE FAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=424 a=16 n=if Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[DE FAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=420 a=25 n=is_method Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[DE FAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=458 a=16 n=if Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[DE FAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=424 a=24 n=has_totag Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[DE FAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=465 a=16 n=if Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[DE FAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=458 a=25 n=is_method Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[DE FAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=465 a=24 n=t_check_trans Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[DE FAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=472 a=16 n=if Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[DE FAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=467 a=25 n=is_method Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[DE FAULT_ROUTE] c=[/etc/kamailio/pcscf/kamailio.cfg] l=468 a=5 n=route Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE GISTER] c=[/etc/kamailio/pcscf/kamailio.cfg] l=812 a=16 n=if Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE GISTER] c=[/etc/kamailio/pcscf/kamailio.cfg] l=810 a=25 n=is_present_hf Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE GISTER] c=[/etc/kamailio/pcscf/kamailio.cfg] l=811 a=25 n=pcscf_save_pending Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE GISTER] c=[/etc/kamailio/pcscf/kamailio.cfg] l=812 a=25 n=t_on_reply Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE GISTER] c=[/etc/kamailio/pcscf/kamailio.cfg] l=813 a=25 n=t_on_failure Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE GISTER] c=[/etc/kamailio/pcscf/kamailio.cfg] l=861 a=16 n=if Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE GISTER] c=[/etc/kamailio/pcscf/kamailio.cfg] l=856 a=25 n=is_present_hf Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE GISTER] c=[/etc/kamailio/pcscf/kamailio.cfg] l=860 a=25 n=append_hf Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE GISTER] c=[/etc/kamailio/pcscf/kamailio.cfg] l=872 a=24 n=t_relay Jan 29 22:36:29 kamailioast ./pcscf[3841]: ERROR: *** cfgtrace:request_route=[RE GISTER] c=[/etc/kamailio/pcscf/kamailio.cfg] l=873 a=2 n=exit Jan 29 22:36:39 kamailioast ./pcscf[3845]: ERROR: *** cfgtrace:failure_route=[RE GISTER_failure] c=[/etc/kamailio/pcscf/kamailio.cfg] l=910 a=16 n=if Jan 29 22:36:39 kamailioast ./pcscf[3845]: ERROR: *** cfgtrace:failure_route=[RE GISTER_failure] c=[/etc/kamailio/pcscf/kamailio.cfg] l=908 a=25 n=t_check_status Jan 29 22:36:39 kamailioast ./pcscf[3845]: ERROR: *** cfgtrace:failure_route=[RE GISTER_failure] c=[/etc/kamailio/pcscf/kamailio.cfg] l=909 a=26 n=send_reply All the time, this messages from the scscf: tail -f /var/log/syslog|grep './scscf' Jan 29 23:50:55 kamailioast ./scscf[3874]: INFO: cdp [peermanager.c:278]: peer_timer(): peer_timer(): Peer hss.open-ims.test #011State 6 Jan 29 23:50:55 kamailioast ./scscf[3874]: WARNING: cdp [peermanager.c:313]: peer_timer(): Inactivity on peer [hss.open-ims.test], sending DWR... - if we don't get a reply, the peer will be closed and nothing from the icscf. Thank you very much for any advice, I've run out of ideas.

2 4

seturi analog for Kamailio 4.3
by Yuriy Gorlichenko 16 Mar '15

16 Mar '15

Hello. I try to call multi[ple endpoints from my server using append_branch. It works fine but when I have only one endpoint - kamailio generate 2 INVITE requests to it. As I understand it is original request and the next one is branch. I used seturi() before for sending original reqest to destination, but I can not see this function at kamailio 4.3. Kamailio 4.3 uses send() dunnction? but it works at stateless mode. I need analog of it or seturi that works at statefull mode.

3 8

Interoperability issues with older SIP clients
by Magnus Nordström 16 Mar '15

16 Mar '15

Hi, We got interoperability issues with older SIP-clients. When e.g. some parameters are included in the SIP header Record-Route the call does not get connected. Now we are looking for a solution for that. We are using kamailio as SIP-registrar/proxy and would like to know if we can keep the call state and rewrite headers that causes interoperability issues. We are aware that kamailio is not a B2BUA. The basic idea would be e.g.: 1. kamailio proxy identifies a call from a modern SIP-client to an old SIP-client 2. kamailio send the call to a interoperability module (?) 3. the interoperabilty module removes sip-headers known to cause issues and saves them. 4. the interoperabilty module makes sure it is in the SIP signaling path 5. the interoperabilty module send the call forward to the old SIP-client 6. the interoperabilty module stays in path rewriting the SIP-headers. The modern SIP-client receives the SIP-signaling as if it was not rewritten. Do you think this is possible with kamailio? Thankful for any hints or ideas. Magnus Nordström

2 1

does ipops module dns_int_match_ip(hostname, ipaddr) search all returned records?
by canuck15 16 Mar '15

16 Mar '15

I am reading the documentation for the ipops module dns_int_match_ip() function and it states the following: "Returns TRUE if ipaddr is associated by DNS to hostname. FALSE otherwise. It uses internal DNS resolver. At this moment, the function might not check all the IP addresses as returned by dns_sys_match_ip(), because the internal resolver targets to discover the first address to be used for relaying SIP traffic. Thus is better to use dns_sys_match_ip() if the host you want to check has many IP addresses, in different address famililies (IPv4/6)." I am not sure what that statement means. I will be using this for IP authentication where the records it is checking against are in a mysql database and may or may not be be using the DNS name instead of the IP. Many of those DNS names could return several IP addresses and the incoming call could be on any one of those IP addresses. So when I do a check of a hostname against an IP address I want all returned A or srv IP's to be checked against the IP. Not just the first IP returned when checked. I do not believe dns_sys_match() will be fast enough on a busy server so I would prefer to using dns_int_match_ip(). If anyone can clarify what that statement means regarding "internal resolver targets to discover the first address" and whether that would affect my use it would be greatly appreciated. On a related note, is there any way to check the contents of the dns resolver cache? I looked through kamctl and kamcmd but didn't find anything. I tried "kamctl address show" but that didn't return anything.

2 1

Re: [SR-Users] remove_hf_value
by Slava Bendersky 16 Mar '15

16 Mar '15

Hello Everyone, Here updated version. Trying remove Record-Route after the coma. My log shows Mar 14 01:25:21 canlvprx01 /usr/sbin/kamailio[751]: INFO: <script>: [SUBSCRIBE], Inbound connection from <Client Public IP> Mar 14 01:25:21 canlvprx01 /usr/sbin/kamailio[751]: ERROR: <script>: <null> Mar 14 01:25:21 canlvprx01 /usr/sbin/kamailio[751]: INFO: <script>: [SUBSCRIBE], Route for removal: '<null>' route snippet. route[ROUTE_HDR_ORG] { # Getting record routes if(is_present_hf("Route")) { xlog("L_INFO", "[$rm], Inbound connection from <$si>\n"); if(is_method("SUBSCRIBE")) { if(is_ip_rfc1918($si)) { xlog("$sel((a)hf_value.Record_Route[-1])"); xlog("L_INFO", "[$rm], Route for removal: '$sel((a)hf_value.Record_Route[-1])'\n"); remove_hf_value("Record-Route[-1]"); } else { xlog("$sel((a)hf_value.Record_Route[1])"); xlog("L_INFO", "[$rm], Route for removal: '$sel((a)hf_value.Record_Route[1])'\n"); remove_hf_value("Record-Route[1]"); } } } return; } Slava, From: "Slava Bendersky" <volga629(a)networklab.ca> To: "sr-users" <sr-users(a)lists.sip-router.org> Sent: Friday, March 13, 2015 1:00:44 PM Subject: [SR-Users] remove_hf_value Hello Everyone, I am trying adjust Record-Route, but can't match headers value And I am call route(ROUTE_HDR_ORG); right after route(WITHINDLG); route[ROUTE_HDR_ORG] { # Getting record routes if(is_present_hf("Record-Route")) { if(is_method("SUBSCRIBE")) { xlog("$sel((a)hf_value.Record_Route[1])"); xlog("L_INFO", "[$rm], Route for removal: '$sel((a)hf_value.Record_Route[1])'\n"); remove_hf_value("Record-Route[1]"); } } return; } Any help Thank you, 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

2 1

What does it mean when auth_check and auth_challenge flags are "0"?
by canuck15 16 Mar '15

16 Mar '15

I am trying to decipher a kamailio.cfg file for a particular open source project. There are problems with authentication and I am trying to understand why. They use the following lines for authentication check if (!auth_check("$fd", "subscriber", "0")) { auth_challenge("$fd", "0"); exit; The documentation only talks about using "1" and not "0". So I am trying to understand what the above statement with "0" is actually doing. Any help in this regard would be greatly appreciated.

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users