sr-users March 2009

sr-users@lists.kamailio.org

92 participants
149 discussions

by Alberto Listas

Hi, I am a new user and recently installed my first Kamailio. I was able to turn MySQL on, create users and do my first calls (extension to extension). But I can't get Kamailio to write the call info to MySQL. I attached Kamailio.cfg. Thanks, Alberto Furtado No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 8.0.238 / Virus Database: 270.11.31/2028 - Release Date: 03/28/09 07:16:00

15 years

[Kamailio-Users] presence in kamailio 1.5

by rachid rachid

hello, i save a sip address (sip:alice@10.193.5.112 <sip%3Aalice(a)10.193.5.112>) in data base Mysql with an equivalent MSN address (alice(a)live.fr) then when i start kamailio1.5 and i save sip adress in X-lite ,the kamailio post a error message: account alice(a)live.fr not found thank you for your help

15 years

[Kamailio-Users] CARRIERROUTE MODULE scan_prefix starting with *

by Asim Riaz

Hi List, is it possible to add a scan_prefix like *222* in carrierroute? if i add a prefix like this in DB(carrierroute), I dont get any error but Kamailio does not run. any idea why? Thanks, Asim

15 years, 1 month

[Serusers] Common Log File

by Jiri Kuthan

I'm wondering what folks think about this the Common Log File (CLF) activity in the IETF? http://www.ietf.org/internet-drafts/draft-gurbani-sipping-clf-01.txt http://tools.ietf.org/html/draft-roach-sipping-clf-syntax-00 Comments to me or directly to the authors welcome. -jiri Abstract Well-known web servers such as Apache and web proxies like Squid support event logging using a common log format. The logs produced using these de-facto standard formats are invaluable to system administrators for trouble-shooting a server and tool writers to craft tools that mine the log files and produce reports and trends. Furthermore, these log files can also be used to train anomaly detection systems and feed events into a security event management system. The Session Initiation Protocol does not have a common log format, and as a result, each server supports a distinct log format that makes it unnecessarily complex to produce tools to do trend analysis and security detection. We propose a common log file format for SIP servers that can be used uniformly for proxies, registrars, redirect servers as well as back-to-back user agents.

15 years, 1 month

[Kamailio-Users] Problems compiling with Solaris 5.10

by Victor Diaz Diaz

Hi all, I am experimenting some problems trying to compile "kamailio-1.5.0-tls" with Solaris 5.10. I have installed the next packages: Development/Languages - gcc-3.3.2 - GNU bison v1.35 - GNU flex v2.54 Development/Tools - GNU make utility v3.80 Finally I just be able to compile in "debug" mode, but in whatever other mode I obtain the next result: Makefile:491: warning: overriding commands for target `/' Makefile:482: warning: ignoring old commands for target `/' Compiling action.c gcc -g -O9 -funroll-loops -Wcast-align -Wall -minline-all-stringops -falign-loops -mtune=nocona -DNAME='"kamailio"' -DVERSION='"1.5.0-notls"' -DARCH='"x86_64"' -DOS='"solaris"' -DCOMPILER='"gcc 3.4.6"' -D__CPU_x86_64 -D__OS_solaris -D__SMP_no -DCFG_DIR='"/etc/kamailio/"' -DPKG_MALLOC -DSHM_MMAP -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DSTATISTICS -DCHANGEABLE_DEBUG_LEVEL -DUSE_LOCAL_ROUTE -DF_MALLOC -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DHAVE_GETIPNODEBYNAME -DHAVE_SYS_SOCKIO_H -DHAVE_SCHED_YIELD -DHAVE_ALLOCA_H -DUSE_SIGACTION -D_POSIX_PTHREAD_SEMANTICS -DHAVE_DEVPOLL -DHAVE_SELECT -c action.c -o action.o Assembler: action.c "/var/tmp//ccSQUbQn.s", line 294 : Syntax error Near line: " cs ; jl .L47" "/var/tmp//ccSQUbQn.s", line 395 : Syntax error Near line: " cs ; jl .L47" "/var/tmp//ccSQUbQn.s", line 417 : Syntax error Near line: " cs ; jl .L8" "/var/tmp//ccSQUbQn.s", line 1050 : Syntax error Near line: " cs ; jl .L605" "/var/tmp//ccSQUbQn.s", line 1308 : Syntax error Near line: " cs ; jle .L463" "/var/tmp//ccSQUbQn.s", line 2413 : Syntax error Near line: " cs ; jl .L605" "/var/tmp//ccSQUbQn.s", line 2506 : Syntax error Near line: " cs ; jl .L646" "/var/tmp//ccSQUbQn.s", line 2626 : Syntax error Near line: " cs ; js .L688" "/var/tmp//ccSQUbQn.s", line 3430 : Syntax error Near line: " cs ; jl .L618" "/var/tmp//ccSQUbQn.s", line 4514 : Syntax error Near line: " cs ; ja .L324" "/var/tmp//ccSQUbQn.s", line 4622 : Syntax error Near line: " cs ; jl .L318" "/var/tmp//ccSQUbQn.s", line 4743 : Syntax error Near line: " ds ; je .L510" "/var/tmp//ccSQUbQn.s", line 4761 : Syntax error Near line: " cs ; je .L624" "/var/tmp//ccSQUbQn.s", line 4813 : Syntax error Near line: " cs ; jl .L605" "/var/tmp//ccSQUbQn.s", line 5025 : Syntax error Near line: " cs ; jle .L361" "/var/tmp//ccSQUbQn.s", line 5082 : Syntax error Near line: " cs ; jle .L361" "/var/tmp//ccSQUbQn.s", line 5151 : Syntax error Near line: " cs ; jne .L497" "/var/tmp//ccSQUbQn.s", line 5229 : Syntax error Near line: " cs ; je .L361" "/var/tmp//ccSQUbQn.s", line 5282 : Syntax error Near line: " cs ; jl .L146" "/var/tmp//ccSQUbQn.s", line 5318 : Syntax error Near line: " cs ; jl .L146" "/var/tmp//ccSQUbQn.s", line 5371 : Syntax error Near line: " cs ; je .L393" "/var/tmp//ccSQUbQn.s", line 5383 : Syntax error Near line: " cs ; je .L361" "/var/tmp//ccSQUbQn.s", line 5473 : Syntax error Near line: " cs ; jl .L146" "/var/tmp//ccSQUbQn.s", line 5653 : Syntax error Near line: " ds ; jne .L718" "/var/tmp//ccSQUbQn.s", line 5766 : Syntax error Near line: " cs ; jle .L731" "/var/tmp//ccSQUbQn.s", line 6024 : Syntax error Near line: " cs ; jle .L768" make: *** [action.o] Error 1 Do you have some ideas and/or suggestions about what could happen? Thanks in advance. Victor. ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos Origin group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos Origin no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos Origin, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------

15 years, 1 month

Re: [Kamailio-Users] t_forward_nonack

by Joao Gomes Pereira

Hello X-Lite says: "500 Server error occurred". Here is the debug: [19632]: LOG: route 1 [19632]: LOG ---> T_ON_REPLY [19632]: ERROR:tm:t_forward_nonack: no branch for forwarding [19632]: ERROR:tm:w_t_relay: t_forward_nonack failed [19632]: LOG ---> T_RELAY and here is the code: # ROUTE 1 route[1] { log(3, "LOG: route 1 \n"); if (check_route_param("nat=yes")) { setbflag(6); } if (isflagset(5) || isbflagset(6)) { route(5); } /* example how to enable some additional event routes */ if (is_method("INVITE")) { #t_on_branch("1"); log(3, "LOG ---> T_ON_REPLY \n"); t_on_reply("1"); t_on_failure("1"); } if (!t_relay()) { log(3, "LOG ---> T_RELAY \n"); sl_reply_error(); } exit; } # BRACH ROUTE 1 branch_route[1] { log(3, "LOG: branch_route 1\n"); xdbg("new branch at $ru\n"); } # ON REPLY ROUTE 1 onreply_route[1] { log(3, "LOG: ON REPLY ROUTE 1\n"); xdbg("incoming reply\n"); if ((isflagset(5) || isbflagset(6)) && status=~"(183)|(2[0-9][0-9])") { force_rtp_proxy(); } if (isbflagset(6)) { fix_nated_contact(); } } # FAILURE ROUTE 1 failure_route[1] { log(3, "LOG: FAILURE ROUTE 1\n"); if (is_method("INVITE") && (isbflagset(6) || isflagset(5))) { unforce_rtp_proxy(); } if (t_was_cancelled()) { exit; } } What could be missing? Thanks Joao Pereira Daniel-Constantin Mierla wrote: > Hello, > > do you call t_relay() or route(1) in your failure route? > > Post your failure route here. Seems you try to forward a failed > transaction without adding a new branch. > > Cheers, > Daniel > > On 03/24/2009 09:31 PM, Joao Gomes Pereira wrote: >> Hello >> I'm getting this error when I try to do URI calls: >> >> LOG ---> T_ON_REPLY ERROR:tm:t_forward_nonack: no branch for forwarding >> ERROR:tm:w_t_relay: t_forward_nonack failed >> CRITICAL:tm:t_should_relay_response: pick_branch failed (lowest==-1) >> for code 408 >> >> And X-Lite says: "Server error occurred" >> >> My config is based in the sample configuration file that comes with >> Kamailio. >> Here is my route[1], where the call should be routed: >> >> >> route[1] { >> >> if (check_route_param("nat=yes")) { >> setbflag(6); >> } >> if (isflagset(5) || isbflagset(6)) { >> route(5); >> } >> >> >> /* example how to enable some additional event routes */ >> if (is_method("INVITE")) { >> #t_on_branch("1"); >> log(3, "LOG ---> T_ON_REPLY \n"); >> t_on_reply("1"); >> t_on_failure("1"); >> } >> >> if (!t_relay()) { >> sl_reply_error(); >> } >> exit; >> } >> >> >> My "branch_route", "on_reply_route" and "failure_route" are just like >> in kamailio.cfg.sample. >> >> What could be causing this errors? >> Thanks >> Regards >> Joao Pereira >> >> >> >> >> >> _______________________________________________ >> Kamailio (OpenSER) - Users mailing list >> Users(a)lists.kamailio.org >> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users >> http://lists.openser-project.org/cgi-bin/mailman/listinfo/users >> >> >

15 years, 1 month

[Kamailio-Users] Kamailio (OpenSER) v1.4.4 Released

by Daniel-Constantin Mierla

A new release in 1.4 series is out. Kamailio 1.4.4 is based on the latest version of branch 1.4, including many fixes in code and documentation, therefore those running 1.4.0, 1.4.1, 1.4.2 or 1.4.3 are advised to upgrade. /Note that latest stable version of the project is Kamailio 1.5.0, released on March 02, 2009, release that has added many new features since branch 1.4. More details about 1.5.0 at:/ http://www.kamailio.org/mos/view/Kamailio-OpenSER-v1.5.0-Release-Notes/ <http://www.kamailio.org/mos/view/Kamailio-OpenSER-v1.5.0-Release-Notes> Kamailio 1.4.4 is provided as a patch fix release for those still running 1.4.x version. Source tarballs are available at: http://www.kamailio.org/pub/kamailio/1.4.4/src/ <http://www.kamailio.org/pub/kamailio/1.4.4/src> Detailed changelog: http://www.kamailio.org/pub/kamailio/1.4.4/ChangeLog Download via SVN: svn co https://openser.svn.sourceforge.net/svnroot/openser/branches/1.4 kamailio Tag for this release can be browsed at: http://openser.svn.sourceforge.net/viewvc/openser/tags/1.4.4/ Project site at SourceForge.net (still using old name): http://sourceforge.net/projects/openser/ Modules' documentation: http://www.kamailio.org/docs/modules/1.4.x/ <http://www.kamailio.org/docs/modules/1.4.x> What is new in 1.4.x release series is summarized in the announcement of v1.4.0: http://www.kamailio.org/mos/view/KAMAILIO-v1.4.0-Released -- Daniel-Constantin Mierla

15 years, 1 month

[Kamailio-Users] Dealing with REGISTER "retransmissions"

by mayamatakeshi

Hello, we are running kamailio 1.4. Some days ago one of our subscribers SIP phone went crazy and bombarded our proxy with thousands of REGISTER requests. Actually, it didn't wait for any response of the proxy, it just kept sending REGISTER messages (same packet always). Since we are running with nonce_reuse disabled, it stalled the server due to "auth:challenge: failed to generate nonce". I don't have the whole figure but the packet capture I inspected showed that the terminal sent more than 200 thousand REGISTER messages in 15 seconds. We may not be able to replace those terminals at this moment. So to avoid this problem to happen again, we enabled nonce_reuse. However this only will solve the nonce problem but still we will have a lot of hits to database. So I was thinking, maybe I should create a transaction before sending the challenge so that REGISTER retransmissions would be absorbed. I was thinking in doing something like this: if (!proxy_authorize("", "subscriber")) { t_newtran(); proxy_challenge("", "0"); exit; } Does anyone see any problem/shortcoming with this? regards, takeshi

15 years, 1 month

[Kamailio-Users] portal for OpenSER

by Metshet Seleshi

Hi all, I am looking to build a protal for openser, I am not having much luck with serMyAdmin, anybody have used this before or any other similar portal recommendation , any sugession will be appriciated, regards

15 years, 1 month

[Kamailio-Users] xcap and pua modules

by Luntras Loredana

Hello, I am still trying to install a presence server and a RLS. What I understood is that I have to install the xcap module on Kamailio and a Xcap server. I began with the pua and xcap_client module. When installing xcap_client I have the following errors: xcap_client.c:162: attention : implicit declaration of function «curl_global_cleanup" make[1]: *** [xcap_client.o] Erreur 1 make[1]: quittant le répertoire « /opt/kamailio-1.5.0-tls/modules/xcap_client » make: *** [modules] Erreur 2 And when I am restarting kamailio server (I've added "loadmodule pua.so) I also have an error (I am in the debug mode) Mar 25 10:12:48 [11907] ERROR:core:db_check_table_version: invalid version 5 for table pua found, expected 6 (check table structure and table "version") Mar 25 10:12:48 [11907] ERROR:pua:mod_init: error during table version check. Mar 25 10:12:48 [11907] ERROR:core:init_mod: failed to initialize module pua Mar 25 10:12:48 [11907] ERROR:core:main: error while initializing modules I have kailio 1.5. Thanks for your help, Loredana

15 years, 1 month

Jump to page:

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 March 2009