sr-users November 2017

sr-users@lists.kamailio.org

89 participants
110 discussions

t_relay_to_udp - 500 server error occurred (6/SL)
by Donat Zenichev 09 Nov '17

09 Nov '17

Hi all. I have a problem with t_relay_to_udp function. My topology: UAC -> tcp -> kamailio <-> udp <-> asterisk Kamailio processes requests from clients over TCP and relays requests to asterisk over UDP. Kamailio gets INVITE from client, relays it to asterisk, then he sends 100 trying to user client and abruptly sends 500 internal error to client (after 100 trying). But the main interesting thing is, that asterisk answers on INVITE and dialog continues between kamailio and asterisk (without user agent client) - it reaches the destination then, without originator : ) How error on kamailio looks like: Nov 8 15:23:37 ip-10-2-1-229 kamailio[10339]: ERROR: tm [t_fwd.c:1716]: t_forward_nonack(): ERROR: t_forward_nonack: no branches for forwarding Nov 8 15:23:37 ip-10-2-1-229 kamailio[10339]: ERROR: sl [sl_funcs.c:363]: sl_reply_error(): ERROR: sl_reply_error used: I'm terribly sorry, server error occurred (6/SL) The same problem is, when I change transport protocol between kamailio and asterisk to TCP, using the t_relay_to_tcp function. When I use t_relay function, it works fine, nothing happens that can drop dialogs between kamailio and clients. Relaying code part: if ($var(to_asterisk)=="1") { xlog("L_NOTICE","Relaying to asterisk - change socket to udp:10.1.1.1:5070 \n"); force_send_socket(udp:10.1.1.1:5070); if (!t_relay_to_udp()) { sl_reply_error(); } } I need to use t_relay_to_udp with force_send_socket, because kamailio changes the source port (source socket) every time he generate new INVITEs to asterisk and this is irrelevant. Dump between kamailio and user agent client: INVITE sip:1111111111example@kam1.domain.com:5070;transport=TCP SIP/2.0 Via: SIP/2.0/TCP uac.domain.example:5065;branch=z9hG4bK-d8754z-67b9ad24dbc5c1d0-1---d8754z- Max-Forwards: 70 Contact: <sip:debug.device-example@uac.domain.example:5065;transport=TCP> To: <sip:1111111111example@kam1.domain.com:5070;transport=TCP> From: <sip:debug.device-example@kam1.domain.com:5070 ;transport=TCP>;tag=93394e63 Call-ID: NzQ1NWU5NzUxYmY4ZWVjMjYwNDYwMTBmYzYxODZkZmM. CSeq: 2 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Content-Type: application/sdp Proxy-Authorization: Digest username="debug.device-example",realm=" kam1.domain.com ",nonce="WgQGlVoEBWnhH3CF6DE77uKxKJx0tT4e",uri="sip:1111111111example@kam1.domain.com:5070 ;transport=TCP",response="4753aa849715d26d0dde1b3c2314c843",a orithm=MD5 Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri User-Agent: Z 3.3.25608 r25552 Allow-Events: presence, kpml Content-Length: 241 v=0 o=Z 0 0 IN IP4 uac.domain.example s=Z c=IN IP4 uac.domain.example t=0 0 m=audio 8000 RTP/AVP 8 3 110 0 98 101 a=rtpmap:110 speex/8000 a=rtpmap:98 iLBC/8000 a=fmtp:98 mode=20 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv SIP/2.0 100 trying -- your call is important to us Via: SIP/2.0/TCP uac.domain.example:5065;branch=z9hG4bK-d8754z-67b9ad24dbc5c1d0-1---d8754z-;rport=43486 To: <sip:1111111111example@kam1.domain.com:5070;transport=TCP> From: <sip:debug.device-example@kam1.domain.com:5070 ;transport=TCP>;tag=93394e63 Call-ID: NzQ1NWU5NzUxYmY4ZWVjMjYwNDYwMTBmYzYxODZkZmM. CSeq: 2 INVITE Server: MS Lync Content-Length: 0 SIP/2.0 500 I'm terribly sorry, server error occurred (6/SL) Via: SIP/2.0/TCP uac.domain.example:5065;branch=z9hG4bK-d8754z-67b9ad24dbc5c1d0-1---d8754z-;rport=43486 To: <sip:1111111111example@kam1.domain.com:5070 ;transport=TCP>;tag=9a78ee8ed9a3d4ba441c41d83ba2e904.4113 From: <sip:debug.device-example@kam1.domain.com:5070 ;transport=TCP>;tag=93394e63 Call-ID: NzQ1NWU5NzUxYmY4ZWVjMjYwNDYwMTBmYzYxODZkZmM. CSeq: 2 INVITE Server: example Content-Length: 0 Thanks in advance for hints. -- -- BR, Donat Zenichev Wnet VoIP team Tel: +380(44) 5-900-800 http://wnet.ua

1 0

Topoh module configuration for SIP proxy and SIP registrar
by Christian Conus 08 Nov '17

08 Nov '17

Hello, I am trying to configure the topoh module for kamailio 5.0.2. I read the documentation but some points are still not clear to me. The topology of my network is as follow: - Two SIP proxies - Two SIP registrars - Only one SIP proxy is running (the other take over automatically in case the first fails) - Both registrars are running (proxy sends requests to both registrars using round robin algorithm) Text mode graph of the topology (hope it helps understand): I tried to enable topoh on SIP proxy only, on both proxy and registrars, with same mask_key everywhere and with different mask_key between proxy and registrars but everytime I could still see parts of the SIP header which was not obfuscated. My questions are: - Is it necessary to enable topoh module on each SIP proxy and SIP registrar ? - The mask_key should be the same on each server or it should be different between proxy and registrars? - the mask address should be the same on each server or it should be different between proxy and registrars ? Thanks in advance for your help, Christian -- Sent from: http://sip-router.1086192.n5.nabble.com/Users-f3.html

2 10

evapi_async_relay() failed
by Abdul Basit 07 Nov '17

07 Nov '17

Hi list, I am configuring CGRateS with kamailio 4.4 using deb packages on debian 8. I am facing a issue while processing event_route[dialog:start] for answering call INVITE at evapi_async_relay("{\"event\":\"CGR_CALL_START\", with following error /usr/sbin/kamailio[13887]: ERROR: evapi [evapi_mod.c:288]: w_evapi_async_relay(): failed to suspend request processing However, after discussion with Dan on IRC i replaced function evapi_async_relay() with evapi_relay() resolved the issue. Whats causing this error? Can anyone suggest some way out for keep using evapi_async_relay? -- regards, abdul basit

2 1

Kamailio SIP-I
by Saleem Manasfi 07 Nov '17

07 Nov '17

Dears, Please if you can let us know how does Kamailio reads the SIP-I body (ISUP)? Is there any document or link that may help?

2 1

Re: [SR-Users] Regarding Opensource DID Routing Solution using Kamailio
by surendra tiwari 06 Nov '17

06 Nov '17

Hi All, I have used the kamailio and redis to create the DID routing solution.please find below in github.this repository is created to help the person who want to setup there own DID routing solution with following feature: 1. Inbound Termination with Carrier IP validation. 2. Carrier LCR for DID/TFN to PSTN forwarding. 3. Inbound Abuse Block. 4. CDR in MongoDB. 5. IPTables Block for Sip-Scanners. 6. Integration with RtpEngine. 7. RedisDB for quick DB Access. https://github.com/surendratiwari3/KamInboundSIP On Mon, Nov 6, 2017 at 9:56 PM, Daniel-Constantin Mierla <miconda(a)gmail.com> wrote: > Hello, > > your email was addressed to kamailio-announce mailing list (I took your > message from its bounces filter), but that list is only for announcement > issued by Kamailio project (major news about our releases, security > incidents, events, etc...). > > News from community members are welcome and can be sent to: > > - sr-users(a)lists.kamailio.org for non-commercial announcements > > - business(a)lists.kamailio.org for announcements related to commercial > offerings/products (but here you can also send non-commercial announcements) > > Your announcement is not commercial and can be sent to sr-users. Once it > will be there, I will also make a news article on kamailio.org website. > > I didn't have the time yet to check in detail what you put together, but > sounds interesting. > > Thanks for sharing, > Daniel > > (cc-ed Fred as he is moderator for kamailio announce mailing list) > > On 01.11.17 18:46, surendra tiwari wrote: > > Hi All, > > I have used the kamailio and redis to create the DID routing > solution.please find below in github.this repository is created to help the > person who want to setup there own DID routing solution with following > feature: > > > 1. Inbound Termination with Carrier IP validation. > 2. Carrier LCR for DID/TFN to PSTN forwarding. > 3. Inbound Abuse Block. > 4. CDR in MongoDB. > 5. IPTables Block for Sip-Scanners. > 6. Integration with RtpEngine. > 7. RedisDB for quick DB Access. > > > https://github.com/surendratiwari3/KamInboundSIP > > -- > With Regards, > Surendra Tiwari > VoIP Application Developer, > +91-9967609476 <+91%2099676%2009476> > > > -- > Daniel-Constantin Mierlawww.twitter.com/miconda -- www.linkedin.com/in/miconda > Kamailio Advanced Training, Nov 13-15, 2017, in Berlin - www.asipto.com > Kamailio World Conference - www.kamailioworld.com > > -- With Regards, Surendra Tiwari VoIP Application Developer, Plivo Comm +91-9967609476

1 0

Sipcapture HEP Values
by Soltanici Ilie 06 Nov '17

06 Nov '17

Hi all, How can i get the Destination IP from HEP packet? I tried $hep(dst _ip) like in documentation (https://www.kamailio.org/wiki/cookbooks/devel/pseudovariables#sipcapture_mo…) - but is not working. (pvar "hep" has an invalid name param [dst_ip]). Thank You.

1 0

Invalid JSON when dumping htable with JSONRPC-S
by Marrold 03 Nov '17

03 Nov '17

Hi All, I am currently trying to retrieve the contents of a htable using the JSONRPC-S module over HTTP, however I have observed if a slot contains multiple values, the JSON returned has duplicate keys which could be considered invalid. Here are the relevant lines from kamailio.cfg - event_route[xhttp:request] { if ($hu =~ "^/carrier") { jsonrpc_exec('{"jsonrpc": "2.0", "method": "htable.dump", "params" : {"htable": "carrier"}, "id": 1}'); xhttp_reply("200", "OK", "text/html", "$jsonrpl(body)"); } } And the output, showing a slot with two items- { "entry": 5, "size": 2, "slot": { "item": { "name": "carrierA", "value": "90", "type": "str" }, "item": { "name": "carrierB", "value": "190", "type": "str" } } } And the same from `kamcmd -s unix:/tmp/kamailio_ctl htable.dump carrier` - { entry: 5 size: 2 slot: { item: { name: carrierA value: 90 type: str } item: { name: carrierB value: 190 type: str } } } Would it be possible to change it to something like the following - { "entry": 5, "size": 2, "slot": [ { "name": "carrierA", "value": "90", "type": "str" }, { "name": "carrierB", "value": "190", "type": "str" } ] } Any other suggestions or work arounds would be appreciated, Thanks Matthew

2 1

Contacts in 302
by Diego Nadares 03 Nov '17

03 Nov '17

Hi Guys, I'm generating a 302 reply from kamailio. In this 302 I append new branches with new contacts. if($var(routing)=~"redirect"){ jansson_get("contacts_len", "$var(evmsg)", "$var(contacts_len)"); xlog("L_INFO", "Contacts len $var(contacts_len)"); $var(i) = 0; while ($var(i) < $var(contacts_len)){ jansson_get("contacts[$var(i)]", "$var(evmsg)", "$var(contact)"); append_branch($var(contact), "0.5"); $var(i) = $var(i) + 1; } send_reply("302", "Moved Temporarily"); exit; } The problem i'm facing is that I can't delete the original contact *<sip:1111@188.111.111.111:5060 <http://sip:1111@188.111.111.111:5060>>* The resulting conctact: Contact: *<sip:1111@188.111.111.111:5060 <http://sip:1111@188.111.111.111:5060>>*, <sip:1111@188.111.111.112>;q=0.5, <sip:1111@188.111.111.112>;q=0.5 I all ready tried with remove_hf('Contact') and adding the new ones after that but it doesn't worke either. The problem is that one gw takes the first contact over and over again and never the other two. Thanks in advance. Diego.

2 4

Multiple IPs
by Oz Mortimer 03 Nov '17

03 Nov '17

Hi all, I have Kamailio set as an SBC with freeswitch behind - that all works fine. Freeswitch can send calls out VIA Kamailio to external IP address’, but if I try sending a call to another IP hosted by Kamailio the seems to go nowhere… Supplier -> Kamailio -> Customer1 -> Kamailio -> Customer2 The Kamailio server has multiple assigned IPs, which are used to multi-tennant - but I cant for the like of me to get Tennant to tenant calls to work (via freeswitch) Any pointers?

2 13

onreply_route block not processing replies
by José Seabra 03 Nov '17

03 Nov '17

Hi there, I'm facing an issue regarding with replies coming to kamailio that aren't processes inside of onreply_route block. Anyone here can help me understand why these replies (1XX) aren't entering on onreply_route bock? is there any situation already identified on Kamailio that can originate this behavior? The Kamailio version used is 5.0.1. Thank you Regards -- José Seabra

2 3

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 November 2017