sr-users May 2017

sr-users@lists.kamailio.org

91 participants
116 discussions

by Nicolas Pace

Hi everyone, As I shared with you before, We are working on a mobile app to connect the Community Cellular Networks (that uses 2G Cellular Networks) with the rest of the world via SIP, and we are considering using Kamailio for this. We choosed to build a Progresive Web App (PWA) through WebSockets to reduce the friction involved in using a new tool. My question is, is there a reference config to use a web client through WebSockets? I don't have a clue on how to get from the stock config: https://gist.github.com/nicopace/9d44bf813fe309df69ff4cd0affe8324#file- _etc_kamailio_kamailio-conf to a fully functional WebSocket-enabled config. I've already read the WebSocket module documentation, but it is hard to understand as it assumes you already know how Kamailio works... too many moving parts :( I tried with https://github.com/caruizdiaz/kamailio-ws but it is giving me some errors: May 02 13:37:13 ubuntu kamailio[2329]: : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/modules.cfg, line 48, column 12-25: failed to load module May 02 13:37:13 ubuntu kamailio[2329]: ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command ws_handle_handshake (params 0) May 02 13:37:13 ubuntu kamailio[2329]: : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 143, column 41: unknown command, missing loadmodule? Which relates with: https://github.com/caruizdiaz/kamailio-ws/blob/master/modules.cfg#L48 and https://github.com/caruizdiaz/kamailio-ws/blob/master/kamailio-ws.cfg#L 143 What I'm trying to accomplish is to have a PWA that sends SIMPLE messages and CALLS to and from SIP Users (the 2G users are behind a FreeSwitch, so it could be done). Just to give you some context, we will also add Push Notifications as 'ringing' or 'meesage recieved' alert, and that would be all (we also don't know how to do it). Well... hope to hear from you guys! Thanks!

6 years, 11 months

TCP read/write buffer size on per connection or per module basis

by M S

Hi, I have a kamailio v4.4.5 deployment that serves TCP clients for SIP and XCAP requests (without SIP presence). The kamailio's core TCP parameters allow us to set TCP read and write buffer sizes which are set globally for all TCP connections. However, i noticed that in general SIP over TCP request is much smaller (<8KB for audio + video SIP INVITE request) then XCAP requests (say to support up to 500 contacts we need TCP buffers =~ 64KB). So, if I set global TCP buffer size according to XCAP service needs (e.g. 64KB), they waste too much RAM for SIP connections (assuming max SIP packet is 8KB, there is 56KB buffer space wasted per connection). On the other hand, if i set global TCP buffer sizes to SIP service needs (e.g. 8KB) then it is insufficient for XCAP (only 70-80 contacts would fix in XCAP list). Therefore, i am looking for a way to allow TCP buffer size settings per connection OR per module basis. Is it possible? If so then how? Thank you.

6 years, 11 months

Retrieving the custom header parameter value from contact header

by vivek＠advaitamtech.com

Hi, Am trying to extract a custom parameter from the contact header. Below it the example of contact header, Eg: Contact: <sip:fayazat@XXX.XXX.XXX.XXX:5060;tgrp=tg_0615_prsw1> I want to extract the parameter value of "tgrp" Tried using @hf_value.contact.p.tgrp . But it is giving me complete contact header. I want only "tgrp" paramter value "tg_0615_prsw1". Anyone , any sugeestions? Thanks, Vivek.

6 years, 11 months

TCP port re-using when doing HTTP transfer

by Ramachandran, Agalya (Contractor)

Hi Giacomo, I am using http_async_client module to do http transfer. Currently am testing the HTTP service with a mock server. If I send the HTTP response immediately for the POST request, then the TCP connections are reused from kamailio. In the mock server if I send the response with a delay of 1 sec then, TCP port are opened and closed for every HTTP transfer. Is there a way or any configuration to limit the number of TCP port opening for the HTTP transfers? Please clarify me. Regards, Agalya

6 years, 11 months

Kamailio IMS - Handling 2 SIP transports in an IMS client

by Haggerty, Paul (phaggert)

Hi, Our client registers with the IMS core using UDP but uses TCP when the packet size is over 1300 bytes. When the client sends the TCP reques, the PCSCF replies with 403 Forbidden "you need to reg with the SCSCF" We've traced this back to the code in the PCSCF and it looks like it is checking the via headers and the received ip/port combinations for a match. The actual contact header looks like it matches the registered client. Question is what do we need to do in the client to ensure that the PCSCF recognizes the request as one from a registered client? We've tried the config options is_registered_fallback2ip , ignore_contact_rxport_check and they don't seem to be used. I'm attaching a network trace and included here are some debug messages from the PCSCF. In the network trace the client is 10.8.0.6. PCSCF Trace messages ------------------------------------------- 34207) DEBUG: ims_registrar_pcscf [service_routes.c:208]: getContactP(): This is a request - using first via to find contact 10(34207) DEBUG: ims_registrar_pcscf [service_routes.c:216]: getContactP(): searching for contact with host:port:proto contact [2://10.8.0.6:49946] 10(34207) DEBUG: ims_usrloc_pcscf [udomain.c:457]: get_pcontact(): Searching for contact with AOR [sip:mcpttuser1@10.8.0.6:44580;ob;alias=10.8.0.6~44580~1;alias=10.8.0.6~49946~2] in P-CSCF usrloc based on VIA [2://10.8.0.6:49946] Received [2://10.8.0.6:49946], Search flag is 0 10(34207) DEBUG: ims_usrloc_pcscf [udomain.c:463]: get_pcontact(): Have an AOR to search for 10(34207) DEBUG: ims_usrloc_pcscf [udomain.c:468]: get_pcontact(): checking for rinstance10(34207) DEBUG: ims_usrloc_pcscf [udomain.c:480]: get_pcontact(): no rinstance param 10(34207) DEBUG: ims_usrloc_pcscf [usrloc.c:148]: get_aor_hash(): Returning hash: [1662767777] 10(34207) DEBUG: ims_usrloc_pcscf [udomain.c:503]: get_pcontact(): get_pcontact slot is [161] 10(34207) DEBUG: ims_usrloc_pcscf [udomain.c:507]: get_pcontact(): comparing contact with aorhash [1662767777], aor [sip:mcpttuser1@10.8.0.6:44580;ob;alias=10.8.0.6~44580~1] 10(34207) DEBUG: ims_usrloc_pcscf [udomain.c:508]: get_pcontact(): contact host [10.8.0.6:44580] 10(34207) DEBUG: ims_usrloc_pcscf [udomain.c:509]: get_pcontact(): contact received [1:10.8.0.6:44580] 10(34207) DEBUG: ims_usrloc_pcscf [udomain.c:543]: get_pcontact(): contact not found in memory 10(34207) INFO: ims_registrar_pcscf [service_routes.c:258]: getContactP(): Contact not found based on Contact-header, trying IP/Port/Proto 10(34207) DEBUG: ims_usrloc_pcscf [udomain.c:457]: get_pcontact(): Searching for contact with AOR [sip:mcpttuser1@10.8.0.6:44580;ob;alias=10.8.0.6~44580~1;alias=10.8.0.6~49946~2] in P-CSCF usrloc based on VIA [2://10.8.0.6:49946] Received [2://10.8.0.6:49946], Search flag is 1 10(34207) DEBUG: ims_usrloc_pcscf [udomain.c:463]: get_pcontact(): Have an AOR to search for 10(34207) DEBUG: ims_usrloc_pcscf [udomain.c:468]: get_pcontact(): checking for rinstance10(34207) DEBUG: ims_usrloc_pcscf [udomain.c:480]: get_pcontact(): no rinstance param 10(34207) DEBUG: ims_usrloc_pcscf [usrloc.c:148]: get_aor_hash(): Returning hash: [1662767777] 10(34207) DEBUG: ims_usrloc_pcscf [udomain.c:503]: get_pcontact(): get_pcontact slot is [161] 10(34207) DEBUG: ims_usrloc_pcscf [udomain.c:507]: get_pcontact(): comparing contact with aorhash [1662767777], aor [sip:mcpttuser1@10.8.0.6:44580;ob;alias=10.8.0.6~44580~1] 10(34207) DEBUG: ims_usrloc_pcscf [udomain.c:508]: get_pcontact(): contact host [10.8.0.6:44580] 10(34207) DEBUG: ims_usrloc_pcscf [udomain.c:509]: get_pcontact(): contact received [1:10.8.0.6:44580] 10(34207) DEBUG: ims_usrloc_pcscf [udomain.c:543]: get_pcontact(): contact not found in memory 10(34207) DEBUG: ims_registrar_pcscf [service_routes.c:263]: getContactP(): No entry in usrloc for 10.8.0.6:49946 (Proto 2) found! 10(34207) DEBUG: ims_registrar_pcscf [service_routes.c:300]: getContactP(): Asserted identity not set10(34207) ERROR: *** cfgtrace:request_route=[Orig_Initial] c=[/opt/OpenEPC/etc/pcscf2.cfg] l=975 a=26 n=xlog 10(34207) WARNING: <script>: 2.1 10(34207) ERROR: *** cfgtrace:request_route=[Orig_Initial] c=[/opt/OpenEPC/etc/pcscf2.cfg] l=976 a=26 n=send_reply Appreciate any help we can get, - Paul

6 years, 11 months

handle_uri_alias persists through failure_route

by David Wilson

Hello All, We use registrar servers (call them A,B) for TLS connections from clients and a central routing proxy (P) that authenticates and manages all call routing. On INVITE, P uses lookup(“location”) and handle_uri_alias() to route the INVITE to A or B depending on the AOR from REGISTER. In failure_route I’m trying to send INVITE to a voicemail URI at host (V), using alias_db_lookup to retrieve it and sending with t_relay(). However, despite showing V as the host in the URI, the message is sent to A (or B) as if the handle_uri_alias is still in effect. I’ve tried calling revert_uri() before the alias_db_lookup(), but this doesn’t seem to help. Is there a way to reset the uri_alias? The failure_route (simplified) looks like this: failure_route[1] { if (method == "INVITE") { revert_uri(); if (alias_db_lookup("dbaliases")) { t_relay(); } } } I have also tried using t_relay(“$rd”, “$rp”) after confirming (by logging) that the uri contains the desired values, but kamailio failed to start, with this error logged: ERROR: tm [tm.c:672]: fixup_hostport2proxy(): TM module:fixup_hostport2proxy: bad port number <$rp> Any suggestions? Best regards, Dave.

6 years, 11 months

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