sr-users

sr-users@lists.kamailio.org

34 participants
37543 discussions

NATHELPER issue
by Ali Taher 20 Jul '18

20 Jul '18

Hello, I'm using Kamailio 4.2 as proxy with nathelper enabled. Yet , the ACK packet sent from the proxy to the origination's private IP. The ACK is sent as reply on the following 200 OK sent from the origination : 8m2EJN41BN/6WSIP/2.0 200 OK From: <sip:+4444331234567@X.X.X.X;user=phone>;tag=XQBQNjvjgp4Ze To: <sip:+905362695933@172.16.45.65;user=phone>;tag=12033368836000 Via: SIP/2.0/UDP X.X.X.X:5065;branch=z9hG4bK2959.233ecbc5eff949f946d8763ce25e5e6d.0;received= X.X.X.X,SIP/2.0/UDP X.X.X.X;received=X.X.X.X;rport=5060;branch=z9hG4bKN93cXvv26vDDN Record-Route: <sip:X.X.X.X:5065;lr;ftag=XQBQNjvjgp4Ze> Call-ID: CbeX8453909200habfGhEfElPce(a)BC00.XXXXXXXXXXXXXX CSeq: 125698370 INVITE Accept: application/sdp Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,UPDATE P-Charging-Vector: icid-value=B0912C3D70-0720-09394507;icid-generated-at=BC00.XXXXXXXXXXXXXX.XX ;orig-ioi=MXXXXXXXXXXXXXX Content-Type: application/sdp Contact: <sip:172.16.45.65:5060;transport=UDP> Content-Length: 268 v=0 o=- 5838243 5838244 IN IP4 BC00.XXXXXXXXXXXXXX s=- c=IN IP4 172.16.45.144 t=0 0 a=sendrecv m=audio 47588 RTP/AVP 18 96 c=IN IP4 172.16.45.144 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=yes a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-15 a=maxptime:20 Following is the header of the sent ACK packet: Request-Line: ACK sip:172.16.45.65:5060;transport=UDP SIP/2.0 Record-Route: <sip:X.X.X.X:5065;lr;ftag=XQBQNjvjgp4Ze> Via: SIP/2.0/UDP X.X.X.X:5065;branch=z9hG4bK2959.871535fd341bbe3099d0bf60d6460e18.0 Via: SIP/2.0/UDP X.X.X.X;received=X.X.X.X;rport=5060;branch=z9hG4bKQUpy0jy90etjc Max-Forwards: 69 From: <sip:+4444331234567@X.X.X.X;user=phone>;tag=XQBQNjvjgp4Ze To: <sip:+905362695933@172.16.45.65;user=phone>;tag=12033368836000 Call-ID: CbeX8453909200habfGhEfElPce(a)BC00.XXXXXXXXXXXXXX CSeq: 125698370 ACK Content-Length: 0 Where X.X.X.X is Kamailio server public IP. Following is part of my config file : route { route(NATDETECT); record_route(); if(!mf_process_maxfwd_header("10")) { sl_send_reply("483", "Too Many Hops"); exit; } # Maybe some sanity_check() here. if(has_totag()) { if(loose_route()) { route(DLGURI); if(!t_relay()) sl_reply_error(); exit; } else { if(is_method("ACK")) { route(DLGURI); if(t_check_trans()) { t_relay(); } } else sl_send_reply("403", "Forbidden"); } exit; } ..... } route[NATDETECT] { #!ifdef WITH_NAT force_rport(); if (nat_uac_test("19")) { if (is_method("REGISTER")) { fix_nated_register(); } else { add_contact_alias(); } setflag(FLT_NATS); } #!endif return; } route[DLGURI] { #!ifdef WITH_NAT if(!isdsturiset()) { handle_ruri_alias(); } #!endif return; } Can you please check why the ACK is still sent on private IP ? Thanks Ali Taher

1 0

The problem of get_aor_hash function
by tyd 20 Jul '18

20 Jul '18

Dear all, I'm trying Kamailio 5.1.4 and IMS module. When registering to Kamailio IMS using the same ip and port for 30 users (different contact user part), the P-CSCF get the same hash number and aor value. The function get_aor_hash(_d, &_ci->via_host, _ci->via_port, _ci->via_prot) in ims_usrloc_pcscf pcontact.c seems the problem. Because hashing with host, port, prot will get the same hash value. Anyone can help this ?

3 3

dialog module : questions about dialog states
by Abdoul Osséni 19 Jul '18

19 Jul '18

Hello list, When the dialog state for a call is < 4, is it possible to use dlg_bye() function to end the call? Best regards Abdoul OSSENI Ingénieur DevOps chez Néo-Soft Co-Fondateur de ON SERVICES Tél : +33 601 135 167

2 5

Locking htable entries
by Alex Balashov 19 Jul '18

19 Jul '18

Hi, Sorry if this question has been answered before, but I'm rather puzzled as to the intent behind sht_lock() / sht_unlock(). Presumably, "thread"-safe / shm mutex locking is already implemented in htable query and mutation operations, otherwise htable would be unusable in a route script context. So what is the purpose of this higher-level lock? Is it to create a way to block config script execution in multiple processes as to serialise operations? Why would one want to do this under any ordinary circumstances? Perhaps it is a failure of my imagination... Thanks, -- Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

2 4

executing python routine on demand
by Walter Martín Villalba 18 Jul '18

18 Jul '18

Hello, TL;DR How can I execute a routine in my Kamailio python module (kamailio_python.py) on demand? For example, using kamcmd from the command line. I know you can execute *app_python.reload *but I don't need to reload the whole python module, and furthermore, docs for this call say it's unstable and can even crash your kamailio instance. So my goal is to execute one single python routine on demand. https://www.kamailio.org/docs/modules/5.1.x/modules/app_python.html#app_pyt… Full explanation: I'm currently implementing OIDC token authentication for Kamailio. I have a python routine that extracts the token from a custom SIP header, and validates the token as per the OIDC spec (I'm using pyjwt plus other custom checks for this). In order to do offline validation of the token, you need the Identity Provider (IdP) Server's certificate, which I get in advance and cache in a local file on my Kamailio server. I also have an external python script which I can run to get the latest certificate from the IdP server and update it locally. The part I'm missing is how to tell Kamailio to reload the value of the certificate from the local cache, WITHOUT stopping kamailio or interrupting any sessions. This is needed in case the certificate is updated (e.g. due to expiration or compromise) on the IdP server; if you don't update it so that Kamailio can use the latest one, all token verification will fail (tokens signed by IdP server using latest private key corresponding to latest certificate, but Kamailio trying to validate the signature using the public key extracted from previous certificate -- this results in a signature error, as Kamailio needs to be using the public key corresponding to the private one that was used to sign the token). By being able to execute one single python routine on demand (e.g. using kamcmd), I can tell Kamailio to reload the certificate value from the local cache, which I just updated by running my other (external and unrelated to Kamailio software) python script. Hope this makes sense, and hopefully I can get some tips on how to achieve this. Thanks, Martín.

1 0

in-dialog requests
by Ali Taher 18 Jul '18

18 Jul '18

Hello, I'm using Kamailio as a proxy behind freeswitch to alter some packets (183 packets precisely). Here is my scenario: (---Customer---) --> ((port 5065)---Kamailio---) --> ((port5060)---Freeswitch---) --> (---Supplier---) Here is my request route : route{ if (is_method("INVITE")) { xlog("L_INFO","INSIDE request route $si \n"); insert_hf("X-AUTH-IP: $si\r\n"); } route(FWD); } reply_route { #xlog("L_INFO","INSDE reply \n"); if (status == "183") { change_reply_status(180, "Ringing"); exit; } } route[FWD] { #xlog("L_INFO","INSIDE FWD \n"); forward(X.X.X.X,5060); } Where X.X.X.X is the Freeswitch IP This script is working normally as long as the customer is sending the requests(INVITE,BYE,ACK,CANCEL..) . But when the supplier or freeswitch initiated the request , above script causes loop where the packet is bounced between kamailio and freeswitch. As I know , loose_route is used to handle such requests , but I'm not sure how to forward these packets to the customer after receiving them from freeswitch. I'm not sure also if what's I'm doing is statefull or stateless. Any help is appreciated. Thanks, Ali Taher

2 4

Kamailio dialog presence (BLF)
by Michal Škuta 18 Jul '18

18 Jul '18

Hello, I am trying make presence module work with Kamailio. Right now I am testing these modules: presence, presence_xml, presence_dialoginfo, pua and pua_dialoginfo. I had some success, the BLF is working only when the monitored extension is calling. When the monitored extension is calling, then the BLF changes its color (red). After end of the call the BLF changes color to green. My problem is when a User comes on-line then it sends SUBSCRIBE with *Event: dialog* and don't get notified of its subscribers state and BLF is not changed. I found similar problem in this mail list : https://lists.kamailio.org/pipermail/sr-users/2017-March/096314.html But is not working for me. Second question is about BLF and offline state. I can not found anything in RFC, there is no offline state, no way to turn off the BLF lamp from green to OFF. I found only this pdf from grandstream: http://www.grandstream.com/sites/default/files/Resources/GXP21x0_Eventlist_… mentioning offline state on page 8. Does anyone have experience with it?

2 2

Using the SIP related functions in a lib
by Bobby Mah 18 Jul '18

18 Jul '18

Hello all, Is it worth my time to try and create a SIP lib out of the SIP functionality available in Kamailio? Thanks for all your input, Bobby

2 1

SIP re-invite Packets
by Ali Taher 18 Jul '18

18 Jul '18

Hello, I'm using below routing logic to change the 183 reply to 180 and send it back to the origination. Noting that Kamailio is listening on 5065. route{ if (is_method("INVITE")) { xlog("L_INFO","INSIDE request route $si \n"); insert_hf("X-AUTH-IP: $si\r\n"); } route(FWD); } reply_route { #xlog("L_INFO","INSDE reply \n"); if (status == "183") { change_reply_status(180, "Ringing"); exit; } } route[FWD] { #xlog("L_INFO","INSIDE FWD \n"); forward(x.x.x.x,5060); } Below is the scenario , where the customer is sending packets to Kamailio , and Kamailio is forwarding them the supplier (with IP x.x.x.x) , then the supplier reply back to kamailio and kamailio relay the reply to the customer ----Customer---- --> ----Kamailio ---> ---Supplier--- I have a case where the supplier sends in some cases an in-dialog invite (Re-Invite) , which is considered I think as SIP-Request and thus as per above routing logic , kamailio is sending it back to the supplier , yet I need to send it to the customer. How can I solve this issue? Thanks Ali Taher

3 6

Error on Kamailio 4.3.7 and dialog
by Laura 18 Jul '18

18 Jul '18

Hi guys, on a test server with kamailio 4.3.7 statefull configuration with dialog I see a lot of messages like this.. Jul 16 15:20:26 vm-nextaitz-01 /usr/sbin/kamailio[31288]: ERROR: dialog [dlg_req_within.c:340]: send_bye(): terminating non-confirmed dialogs not supported Jul 16 15:20:26 vm-nextaitz-01 /usr/sbin/kamailio[31288]: ERROR: dialog [dlg_req_within.c:340]: send_bye(): terminating non-confirmed dialogs not supported Jul 16 15:20:26 vm-nextaitz-01 media-dispatcher[31555]: error: failed to end dialog: 500 Operation failed I'm not find the issue and the way for fix.. Any idea ? Regards Laura

3 8

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