sr-users

sr-users@lists.kamailio.org

20 participants
37472 discussions

[Kamailio-Users] [presence] getting "record not found in hash_table" error
by Pascal Maugeri 14 Nov '08

14 Nov '08

Hi We get very ofter this error message when subscribing to presence: Nov 14 16:20:01 server2-operations /usr/local/sbin/kamailio[6224]: ERROR:presence:get_stored_info: record not found in hash_table Nov 14 16:20:01 server2-operations /usr/local/sbin/kamailio[6224]: ERROR:presence:handle_subscribe: getting stored info ... using kamailio 1.4 So far I haven't managed to find a way to reproduce it. Is there any solution or workaround ? Regards, Pascal

2 2

[Kamailio-Users] How can i use the FIFO
by ALAEDDINE abbech 14 Nov '08

14 Nov '08

hi all I read the doc but i don't understand how can i use the FIFO to have many statistc. Can you give me a simple exemple. thanks.

2 4

[Kamailio-Users] [OT] about scalability, experiences, demands
by Henning Westerholt 14 Nov '08

14 Nov '08

Hello all, recently some statement came to my attention that "there is a common consent that the current design/architecture of [..] OpenSER (inherited from SER) is no longer able to deliver and to meet the present requirements and demands". I don't want to argue that much about this opinion, in fact the demands to a Voice over IP solution depends very much on the certain setup. But i want to share some details from my experiences in developing and operating a big VoIP infrastructure here at 1&1. We've about 2 million customers on our platform, that uses over 5 million individual numbers and terminate about 1 billion minutes per month. We're able to provide a good service with the actual architecture of OpenSER without any real problems. Of course there is always some room for improvements, but so far the main challenges we faced were not in the scalability or performance areas. More important issues are e.g. the inherent complexity of the SIP protocol and the maintainance of a good quality assurance and integration process. We started some years ago with OpenSER 0.9.5, which we then extended a lot in house. For example we implemented more than 25 own modules, a own path implementation, did a lot of bug fixing and workarounds for certain problems we've found. We're able to reduce this amount of proprietary code a lot in the past, because of progress in the OpenSER development, intregration of our "key" modules and a lot of other contributions. We're using now something between OpenSER 1.3 and Kamailio 1.4 with only a few private extensions. So in my opinion the actual design of our server is not "[..] an inevitable dead-end that needs to be avoided.". I rather think that we'll be able with continuing improvements to tackle the upcoming challenges well, especially as we will work together in the future with the SER developers in improving important areas of this software. But this is just my personal opinion, everybody is of course free to have their own position. With best regards, Henning Westerholt -- Henning Westerholt - Development Consumer Products / DSL Core 1&1 Internet AG, Ernst-Frey-Str. 9, 76135 Karlsruhe, Germany Vorstände: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Thomas Gottschlich, Robert Hoffmann, Markus Huhn, Hans-Henning Kettler, Dr. Oliver Mauss, Jan Oetjen - Aufsichtsratsvorsitzender: Michael Scheeren Amtsgericht Montabaur / HRB 6484

2 1

Re: [Kamailio-Users] Problems with counter $var(i)
by ingdavidcespedes＠cable.net.co 14 Nov '08

14 Nov '08

Ok, now I understand. So the answer is, that you can't do that with script variables (http://www.kamailio.net/dokuwiki/doku.php/pseudovariables:1.4.x#script_vari…) there it says: Note: A script variable persists over the OpenSER process in which it was initialized, so be sure of giving it a new value before reading it or you'll get the value asigned in any other previous message processed by the same OpenSER process (pid). ----- Mensaje original ----- De: Ricardo Martinez <rmartinez(a)redvoiss.net> Fecha: Jueves, Noviembre 13, 2008 2:07 pm Asunto: Re: [Kamailio-Users] Problems with counter $var(i) > Hi David. > Yes, that exactly what i want, set the variable to 0 in the main > route,so every call that arrive it start the process again... > The problem is that in the failure_route the variable keeps the > value..and is not resetting to 0 > > Ricardo.- > > -----Mensaje original----- > De: ingdavidcespedes(a)cable.net.co [ingdavidcespedes(a)cable.net.co] > > Enviado el: jueves, 13 de noviembre de 2008 16:15 > Para: Ricardo Martinez > CC: users(a)lists.kamailio.org > Asunto: Re: [Kamailio-Users] Problems with counter $var(i) > > Hi > > In which place of your main route are you writing var(i)=0. Maybe > that'sthe problem, each time you enter in the main route you are > setting the i > variable to 0. > > David Cespedes > > _______________________________________________ > Users mailing list > Users(a)lists.kamailio.org > http://lists.kamailio.org/cgi-bin/mailman/listinfo/users >

1 0

Re: [Kamailio-Users] Problems with counter $var(i)
by ingdavidcespedes＠cable.net.co 13 Nov '08

13 Nov '08

Hi In which place of your main route are you writing var(i)=0. Maybe that's the problem, each time you enter in the main route you are setting the i variable to 0. David Cespedes Hello I realized that the counter $var(i) in the failure_route[1] seems not to be resetting to 0 when the 2nd , 3th ..etc call arrive. So for the second call I have the counter 0 in the main route, the route(3), route(1) but in the failure_route is set to 3 (the last values from the last call) I keep trying to figure it out why this is happening.. Anyone? Thanks, Ricardo.- De: users-bounces(a)lists.kamailio.org [mailto:users-bounces@lists.kamailio.org] En nombre de Ricardo Martinez Enviado el: jueves, 13 de noviembre de 2008 11:46 Para: users(a)lists.kamailio.org Asunto: [Kamailio-Users] Problems with counter $var(i) Sorry ¡ i forgot to put the subject. Hello list. I'm having some problems trying to build a counter for my kamailio.cfg file. This is what I have.. main() ... load avp from radius} var(i)=0; route(3); ... route[1] { t_on_failure("1"); if (!t_relay()) { sl_reply_error(); }; xlog("L_INFO","[$ci] $rm t_relay a $ru"); exit; } route(3) ... $var(nr)=$avp(s:caller_nr); If ( var(i) < $var(nr) ); $var(i) = $var(i) + 1; route(1); else exit; failure_route[1] { xlog("L_INFO", "[$ci] $rm:$ru failure_route\n"); if (t_was_cancelled()) { xlog("L_INFO", "[$ci] $rm:$ru t_was_cancelled en failure_route\n"); exit; } if (!next_gw()) { xlog("L_INFO", "[$ci] No hay mas gateways para $rm:$ou\n"); route(3); } else { xlog("L_INFO", "XXXXX"); } t_on_failure("1"); t_relay(); } After I restart the service the first time a call arrives the counter seems to go OK, the counter goes from 0 to 2 (if the caller_nr=3). But the second time the $var(i) at the main and route(3) it's = 0, but in the failure_route it keeps the value = 3. What I'm doing wrong? Can someone help me here? Thanks Ricardo Martinez.- _______________________________________________ Users mailing list Users(a)lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users

2 1

[Kamailio-Users] Using other media gateways
by Ruchir 13 Nov '08

13 Nov '08

I have a question. We can use media proxy to handle media through media proxies. I was wondering if it is possible to use any media servers for rtp by just specifying ip address of the media gateway.

2 1

[Kamailio-Users] help understanding kamailio.cfg and processing call flow
by Fabian Borot 13 Nov '08

13 Nov '08

hello I have been struggling to get the grasp on kamailio for weeks now. My prob is not understanding the call flow but how to translate it using the functions provided by the modules and the core. I do not have clear the scope or reach of several functions,provided by either the core or the modules. Example: Register with Auth: 1- user sends REGISTER request w/o the encripted credentials 2- kamailio answers with 401 and sends the challenge 3- the uac sends the REGISTER again, this time with the right credentials and after verifying kamailio sends 200 OK 4- if the user is behind a NAT we can fix the contact info before saving it to the location db. With the help of the forum and the tutorials I have found in the internet I have been able to accomplish it with these commands: route{ if (uri==myself) { if (method=="REGISTER") { xlog("L_INFO","mylog: starting to process REGISTER.Info.\n"); if (!www_authorize("", "subscriber")) { xlog("L_INFO","mylog: REGISTER came without auth, sending challenge.\n"); www_challenge("", "0"); exit; }; if (nat_uac_test("1")){ xlog("L_INFO","mylog: REGISTER-Device behind NAT.\n"); fix_nated_register(); } force_rport(); save("location"); xlog("L_INFO","mylog: save-location successful.\n"); exit; } route(1); } route[1] { if (t_relay()) { xlog("L_INFO","mylog: Route 1 section. Method [$rm]."); } else { sl_reply_error(); xlog("L_INFO","mylog: Route 1 section. T_Relay failed. Method [$rm]."); }; exit; } but here come the first questions: 1- when the uac sends the first REGISTER, the function www_challenge() is the one that actually sends the "401" message? or the "exit" just exit out the "if" block and the script will continue with route(1) which in turns executes "t_relay()? ++from the doc, www_challenge() function++++ The function challenges a user agent. It will generate a WWW-Authorize header field containing a digest challenge, it will put the header field into a response generated from the request the server is processing and send the reply. +++++++++++++++++++++++++++++++++ 2- the "exit" after the save("location") function I assume would stop the execution of the script and at that point kamailio responds with "200 ok"? or just exit out the "if" block, the script then reaches the "route(1)" section and the "t_relay()" sends the "200 ok"? ++ from the doc, core-cookbook, exit() function+++++++ Stop the execution of the configuration script – it has the same behaviour as return(0). It does not affect the implicit action to be taken after script execution. ++++++++++++++++++++++++++++ 3- the "t_relay" function: does that function creates and sends the approriate response for each request? ex1: an INVITE is received, does t_relay() "know" that it can send "100 trying" automatically? ex2: a "200 OK" is received as a response to an INVITE, does t_relay knows that it has to send an "ACK"? ++++++from the doc, t_relay() funcion ++++++++++ >From user's perspective, the major function is t_relay(). It setup transaction state, absorb retransmissions from upstream, generate downstream retransmissions and correlate replies to requests. +++++++++++++++++++++++++++++ 4- why do I see ";" even after a "}", is it needed sometimes? 5- is "exit" the same as "exit()"? These may sound like dumb questions for some of the experienced users, but for a newbie they are not. Also, if this sounds like " hey, code my config file for me" I assure you that that is not the intended purpose. I would appreciate any help and thank everybody in advance. Fabian _________________________________________________________________ Color coding for safety: Windows Live Hotmail alerts you to suspicious email. http://windowslive.com/Explore/Hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_safety…

2 2

[Serusers] Fw: SER COLP & COLR implementation
by Erman ÇAKMAK 13 Nov '08

13 Nov '08

Hello all, I could not find any information about SER whether it supports the COLP & COLR call features or not. Does anyone have an idea about it? Regards, Erman Cakmak

1 0

[Kamailio-Users] 488 Not acceptable here
by Ricky Gutierrez 13 Nov '08

13 Nov '08

Hi list, I am giving him returned script from openser trying to find the problem to this message " 488 acceptable Not here" , I have my openser integrated recently with asterisk and the voicemail recently adds rtpproxy to solve problems of nat and was almost a success, some details to improve, but after adding the rtpproxy when I call to UAC and it does not answer the call on the telephone shows a 488 message to me No Aceptable, it does not jump to the voicemai.. I have 2 networks cards in my server, and looking at the sip log, I see twice in the sdp the interfaz it public any idea as solving this problem? regards rickygm # U +1.675624 192.168.10.1:5060 -> 192.168.10.1:5070 INVITE sip:u120@192.168.10.1:5070 SIP/2.0 Record-Route: <sip:192.168.10.1;lr=on;ftag=69372fe200a41663> Via: SIP/2.0/UDP 192.168.10.1;branch=z9hG4bK78e7.cd89b213.1 Via: SIP/2.0/UDP 192.168.10.28:5060;rport=5060;branch=z9hG4bK286620c52595f4b3 From: <sip:119@192.168.10.1>;tag=69372fe200a41663 To: <sip:120@192.168.10.1> Contact: <sip:119@192.168.10.28:5060;nat=yes;nat=yes> Supported: replaces, timer, path Call-ID: 7c55e4667d473f76(a)192.168.10.28 CSeq: 12216 INVITE User-Agent: Grandstream GXV3000 1.1.3.14 Max-Forwards: 69 Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK Content-Type: application/sdp Content-Length: 604 P-hint: inbound->inbound P-hint: Route[20]: Rtpproxy P-hint: Route[20]: Rtpproxy v=0 o=119 8000 8001 IN IP4 192.168.10.28 s=SIP Call c=IN IP4 192.168.1.64192.168.1.64 t=0 0 m=audio 3504835048 RTP/AVP 18 4 3 2 0 101 a=sendrecv a=rtpmap:18 G729/8000 a=rtpmap:4 G723/8000 a=rtpmap:3 GSM/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:0 PCMU/8000 a=ptime:20 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-11 m=video 3505035050 RTP/AVP 99 34 a=sendrecv a=rtpmap:99 H264/90000 a=fmtp:99 profile-level-id=428014; packetization-mode=0; sprop-parameter-sets=Z0KADJWgUH5A,aM4CXID= a=rtpmap:34 H263/90000 a=fmtp:34 CIF=2 MaxBR=1280 a=framerate:20 a=nortpproxy:yes a=nortpproxy:yes # U +0.000052 192.168.10.1:5060 -> 192.168.10.27:5060 CANCEL sip:120@192.168.10.27:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.10.1;branch=z9hG4bK78e7.cd89b213.0 From: <sip:119@192.168.10.1>;tag=69372fe200a41663 Call-ID: 7c55e4667d473f76(a)192.168.10.28 To: <sip:120@192.168.10.1> CSeq: 12216 CANCEL Max-Forwards: 70 User-Agent: OpenSER (1.3.2-notls (i386/linux)) Content-Length: 0 # U +0.000411 192.168.10.1:5070 -> 192.168.10.1:5060 SIP/2.0 488 Not acceptable here Via: SIP/2.0/UDP 192.168.10.1;branch=z9hG4bK78e7.cd89b213.1;received=192.168.10.1 Via: SIP/2.0/UDP 192.168.10.28:5060;rport=5060;branch=z9hG4bK286620c52595f4b3 From: <sip:119@192.168.10.1>;tag=69372fe200a41663 To: <sip:120@192.168.10.1>;tag=as4f1165d5 Call-ID: 7c55e4667d473f76(a)192.168.10.28 CSeq: 12216 INVITE User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Supported: replaces Content-Length: 0 # U +0.000120 192.168.10.1:5060 -> 192.168.10.1:5070 ACK sip:u120@192.168.10.1:5070 SIP/2.0 Via: SIP/2.0/UDP 192.168.10.1;branch=z9hG4bK78e7.cd89b213.1 From: <sip:119@192.168.10.1>;tag=69372fe200a41663 Call-ID: 7c55e4667d473f76(a)192.168.10.28 To: <sip:120@192.168.10.1>;tag=as4f1165d5 CSeq: 12216 ACK Max-Forwards: 70 User-Agent: OpenSER (1.3.2-notls (i386/linux)) Content-Length: 0 # U +0.000144 192.168.10.1:5060 -> 192.168.10.28:5060 SIP/2.0 488 Not acceptable here Via: SIP/2.0/UDP 192.168.10.28:5060;rport=5060;branch=z9hG4bK286620c52595f4b3 From: <sip:119@192.168.10.1>;tag=69372fe200a41663 To: <sip:120@192.168.10.1>;tag=as4f1165d5 Call-ID: 7c55e4667d473f76(a)192.168.10.28 CSeq: 12216 INVITE User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Supported: replaces Content-Length: 0 P-hint: Onreply-route - fixcontact # U +0.000787 192.168.10.27:5060 -> 192.168.10.1:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.10.1;branch=z9hG4bK78e7.cd89b213.0 From: <sip:119@192.168.10.1>;tag=69372fe200a41663 To: <sip:120@192.168.10.1>;tag=fb538483d0333de1 Call-ID: 7c55e4667d473f76(a)192.168.10.28 CSeq: 12216 CANCEL User-Agent: Grandstream GXV3000 1.1.3.14 Supported: replaces, timer, 100rel, path Content-Length: 0 # U +0.000544 192.168.10.27:5060 -> 192.168.10.1:5060 SIP/2.0 487 Request Cancelled Via: SIP/2.0/UDP 192.168.10.1;branch=z9hG4bK78e7.cd89b213.0 Via: SIP/2.0/UDP 192.168.10.28:5060;rport=5060;branch=z9hG4bK286620c52595f4b3 Record-Route: <sip:192.168.10.1;lr=on;ftag=69372fe200a41663> From: <sip:119@192.168.10.1>;tag=69372fe200a41663 To: <sip:120@192.168.10.1>;tag=fb538483d0333de1 Call-ID: 7c55e4667d473f76(a)192.168.10.28 CSeq: 12216 INVITE User-Agent: Grandstream GXV3000 1.1.3.14 Content-Length: 0 # U +0.000067 192.168.10.1:5060 -> 192.168.10.27:5060 ACK sip:120@192.168.10.27:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.10.1;branch=z9hG4bK78e7.cd89b213.0 From: <sip:119@192.168.10.1>;tag=69372fe200a41663 Call-ID: 7c55e4667d473f76(a)192.168.10.28 To: <sip:120@192.168.10.1>;tag=fb538483d0333de1 CSeq: 12216 ACK Max-Forwards: 70 User-Agent: OpenSER (1.3.2-notls (i386/linux)) Content-Length: 0 # U +0.001390 192.168.10.28:5060 -> 192.168.10.1:5060 ACK sip:120@192.168.10.1 SIP/2.0 Via: SIP/2.0/UDP 192.168.10.28:5060;branch=z9hG4bK286620c52595f4b3 From: <sip:119@192.168.10.1>;tag=69372fe200a41663 To: <sip:120@192.168.10.1>;tag=as4f1165d5 Contact: <sip:119@192.168.10.28:5060> Proxy-Authorization: Digest username="119", realm="192.168.10.1", algorithm=MD5, uri="sip:120@192.168.10.1", nonce="4919edaf0a873106bfd0b18f347709360f00f7eb", response="a5a26c257b491718def2b43488a39853" Call-ID: 7c55e4667d473f76(a)192.168.10.28 CSeq: 12216 ACK User-Agent: Grandstream GXV3000 1.1.3.14 Max-Forwards: 70 Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK Content-Length: 0 # U +0.497023 192.168.10.1:5060 -> 192.168.10.28:5060 SIP/2.0 488 Not acceptable here Via: SIP/2.0/UDP 192.168.10.28:5060;rport=5060;branch=z9hG4bK286620c52595f4b3 From: <sip:119@192.168.10.1>;tag=69372fe200a41663 To: <sip:120@192.168.10.1>;tag=as4f1165d5 Call-ID: 7c55e4667d473f76(a)192.168.10.28 CSeq: 12216 INVITE User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Supported: replaces Content-Length: 0 P-hint: Onreply-route - fixcontact # U +0.999813 192.168.10.1:5060 -> 192.168.10.28:5060 SIP/2.0 488 Not acceptable here Via: SIP/2.0/UDP 192.168.10.28:5060;rport=5060;branch=z9hG4bK286620c52595f4b3 From: <sip:119@192.168.10.1>;tag=69372fe200a41663 To: <sip:120@192.168.10.1>;tag=as4f1165d5 Call-ID: 7c55e4667d473f76(a)192.168.10.28 CSeq: 12216 INVITE User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Supported: replaces Content-Length: 0 P-hint: Onreply-route - fixcontact exit 67 received, 0 dropped

2 3

[Kamailio-Users] issues with rtpproxy and kamailio
by Fabian Borot 13 Nov '08

13 Nov '08

I am trying to set up rtpproxy with kamailio and are having these 2 issues: 1- the BYEs are not relayed to the other party, I have to hang up the call at both ends 2- kamailio receives the INVITE from the calling party [behind a nat] and relays it to the called party but the connection information in the SDP has to IPs [the source IP and the RTPproxy IP together c=IN IP4 204.9.239.6765.111.185.187 user 100 is behind a NAT and user 101 is not but I want to force the RTPs to go thru the rtpproxy server [ in the same IP as kamailio] the good and weird thing is that there is audio both ways. this is my config file: if (loose_route()) { # mark routing logic in request xlog("L_INFO","mylog: Loose Route section. Method: [$rm].\n"); append_hf("P-hint: rr-enforced\r\n"); route(1); }; if (uri==myself) { if (method=="REGISTER") { xlog("L_INFO","mylog: starting to process REGISTER.Info: [$au].\n"); if (!www_authorize("", "subscriber")) { xlog("L_INFO","mylog: REGISTER came without auth, sending challenge.\n"); www_challenge("", "0"); exit; }; if (nat_uac_test("1")){ xlog("L_INFO","mylog: REGISTER-Device behind NAT.\n"); fix_nated_register(); } force_rport(); save("location"); xlog("L_INFO","mylog: save-location successful.\n"); exit; } else if (method=="INVITE") { xlog("L_INFO","mylog: Processing INVITE.\n"); if (!proxy_authorize("","subscriber")) { xlog("L_INFO","mylog: INVITE came without auth, sending challenge.\n"); proxy_challenge("","0"); exit; }; consume_credentials(); if (nat_uac_test("1")){ xlog("L_INFO","mylog: INVITE-Device behind NAT.\n"); #fix_nated_contact(); fix_nated_sdp("10"); } force_rtp_proxy(); if (!lookup("location")) { sl_send_reply("404", "Not Found"); xlog("L_INFO","mylog: lookup-location failed, sending 404 Not Found. Method: [$rm].\n"); exit; }; append_hf("P-hint: usrloc applied\r\n"); }; }; route(1); } route[1] { # send it out now; use stateful forwarding as it works reliably # even for UDP2TCP t_on_reply("1"); if (t_relay()) { xlog("L_INFO","mylog: Route 1 section. Method [$rm]."); } else { sl_reply_error(); xlog("L_INFO","mylog: Route 1 section. T_Relay failed. Method [$rm]."); }; exit; } onreply_route[1] { force_rtp_proxy("","65.111.185.187"); } thank you in advance Fabian _________________________________________________________________ Stay up to date on your PC, the Web, and your mobile phone with Windows Live http://clk.atdmt.com/MRT/go/119462413/direct/01/

3 4

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