sr-users May 2005

sr-users@lists.kamailio.org

230 participants
522 discussions

RE: [Serusers] check_ser plugin for nagios.

by Ricardo Martinez

Hello. Thanks for your answers. Finally i was able to monitor my SER with NAGIOS and SIPSAK, maybe not a easy task for those who never used NAGIOS. I'm aware that sipsak support NAGIOS compliant responses, but despite of this the interaction between NAGIOS and SIPSAK is not so clear. I used the script that i found in http://lists.iptel.org/pipermail/serusers/2004-January/005195 with some modifications for the anwswers. I would like to ask one more question. What other kind of test would be useful to monitor SER using NAGIOS? Can i use sipsak to monitor a B2BUA? Thanks! Ricardo.- > -----Mensaje original----- > De: Matt Schulte [mailto:mschulte@netlogic.net] > Enviado el: Lunes, 02 de Mayo de 2005 11:45 > Para: Edgardo O. Gonzales II; Ricardo Martinez; serusers(a)lists.iptel.org > Asunto: RE: [Serusers] check_ser plugin for nagios. > > > I just implemented sipsak this morning for Nagios, sipsak natively > supports Nagios compliant responses. This accomplishes the following > that check_tcp doesn't. > > layer7 response (layer3 is fine and dandy but why not go all the way) > checks for correct callflow > checks authentication (if needed??) > > > Ironically enough I just slapped it in and it works fine. > sample syntax: > sipsak -s sip:+10005551234@full.uri.blah -H your.local.hostname -u > sip_user -a sip_password -N > > The -N makes it respond in compliance to Nagios. > > > -----Original Message----- > From: Edgardo O. Gonzales II [mailto:edgardo.g@pacific.net.ph] > Sent: Friday, April 29, 2005 7:37 PM > To: Ricardo Martinez; 'serusers(a)lists.iptel.org' > Subject: Re: [Serusers] check_ser plugin for nagios. > > > > use the tcp check on nagios then monitor the port ex : 5060 > > thanks, > ed > > At 04:05 AM 4/30/2005, Ricardo Martinez wrote: > >Hello list. > > I'm trying to use nagios to check my ser status, so far i > >found a script in : > >http://lists.iptel.org/pipermail/serusers/2004-January/005195. html and >i tested it without any luck. Does someone have any check_ser that >works ok?. I will really appreciate. > >Thanks > >Ricardo Martinez.- > >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

19 years, 6 months

[Serusers] installing php

by Llanos Serna García-Conde

19 years, 6 months

[Serusers] Proxy-to-Proxy authentication

by Victor Huertas Garcia

Hi all! I'm newie in this mailing list and I am working with SER at this momen in a project. However I have a doubt I would like to clarify. Does anyone know if there is a way to perform SIP Proxy to SIP Proxy authentication (I mean in SIP protocol in general)? If a SIP proxy receives an INVITE from another SIP Proxy, how does the proxy which receives the INVITE that the originating proxy can be trusted? I have read something about TLS but I took it from an article of 2003... Which is the most used method nowadays? Thank you very much for your attentio Regards Victor

19 years, 6 months

[Serusers] ser to asterisk (another domain)

by "Sebastian Kühner"

Hello, I want to make a call from ser to asterisk but it doesn't work. My asterisk-Server is running on 192.168.1.222 and my ser-Server on 192.168.1.223. If I want to make a call to sip:12@192.168.1.222 there appears the message: "Proxy Authentication Required". For routing to asterisk I use the following code: if (!(uri==myself)) { route(2); break; }; route[2] { # outbound requests are allowed only for registered BigU users if (!(src_ip==192.168.1.223) & !(proxy_authorize("192.168.1.223", "subscriber"))) { # ACK and CANCEL have no security mechanisms so they are just # noted /*if (method=="ACK" | method=="BYE") { log(1, "LOG: failed outbound authentication for ACK granted\n"); } else if (method=="CANCEL") { log(1, "LOG: failed outbound authentication for CANCEL granted\n"); }else {*/ proxy_challenge("192.168.1.223", "0"); break; #}; }; # to maintain credibility of our proxy, we check From in INVITEs if (!src_ip==192.168.1.223 & method=="INVITE" & !check_from()) { log(1, "LOG: Spoofed from attempt\n"); sl_send_reply("403", "Use From=id next time"); break; }; append_hf("P-hint: OUTBOUND ON INTERNET\r\n"); if (!t_relay()) { sl_reply_error(); break; }; } Thanks! -- +++ Neu: Echte DSL-Flatrates von GMX - Surfen ohne Limits +++ Always online ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl

19 years, 6 months

[Serusers] RE: confirm a7b970894e016f5f9dd51266a05184244f831ebc

by Victor Huertas Garcia

>From: serusers-request(a)lists.iptel.org >Reply-To: serusers-request(a)lists.iptel.org >To: vhuertas(a)hotmail.com >Subject: confirm a7b970894e016f5f9dd51266a05184244f831ebc >Date: Mon, 02 May 2005 17:50:52 +0200 > >Mailing list subscription confirmation notice for mailing list >Serusers > >We have received a request from 213.170.46.30 for subscription of your >email address, "vhuertas(a)hotmail.com", to the serusers(a)lists.iptel.org >mailing list. To confirm that you want to be added to this mailing >list, simply reply to this message, keeping the Subject: header >intact. Or visit this web page: > > >http://lists.iptel.org/mailman/confirm/serusers/a7b970894e016f5f9dd51266a05… > > >Or include the following line -- and only the following line -- in a >message to serusers-request(a)lists.iptel.org: > > confirm a7b970894e016f5f9dd51266a05184244f831ebc > >Note that simply sending a `reply' to this message should work from >most mail readers, since that usually leaves the Subject: line in the >right form (additional "Re:" text in the Subject: is okay). > >If you do not wish to be subscribed to this list, please simply >disregard this message. If you think you are being maliciously >subscribed to the list, or have any other questions, send them to >serusers-owner(a)lists.iptel.org.

19 years, 6 months

RE: [Serusers] check_ser plugin for nagios.

by Matt Schulte

I just implemented sipsak this morning for Nagios, sipsak natively supports Nagios compliant responses. This accomplishes the following that check_tcp doesn't. layer7 response (layer3 is fine and dandy but why not go all the way) checks for correct callflow checks authentication (if needed??) Ironically enough I just slapped it in and it works fine. sample syntax: sipsak -s sip:+10005551234@full.uri.blah -H your.local.hostname -u sip_user -a sip_password -N The -N makes it respond in compliance to Nagios. -----Original Message----- From: Edgardo O. Gonzales II [mailto:edgardo.g@pacific.net.ph] Sent: Friday, April 29, 2005 7:37 PM To: Ricardo Martinez; 'serusers(a)lists.iptel.org' Subject: Re: [Serusers] check_ser plugin for nagios. use the tcp check on nagios then monitor the port ex : 5060 thanks, ed At 04:05 AM 4/30/2005, Ricardo Martinez wrote: >Hello list. > I'm trying to use nagios to check my ser status, so far i >found a script in : >http://lists.iptel.org/pipermail/serusers/2004-January/005195.html and >i tested it without any luck. Does someone have any check_ser that >works ok?. I will really appreciate. > >Thanks > >Ricardo Martinez.- > >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

19 years, 6 months

[Serusers] ser to asterisk

by "Sebastian Kühner"

Hello, I want to make a call from ser to asterisk but it doesn't work. My asterisk-Server is running on 192.168.1.222 and my ser-Server on 192.168.1.223. If I want to make a call to sip:12@192.168.1.222 there appears the message: "Proxy Authentication Required". For routing to asterisk I use the following code: if (!(uri==myself)) { route(2); break; }; route[2] { # outbound requests are allowed only for registered BigU users if (!(src_ip==192.168.1.223) & !(proxy_authorize("192.168.1.223", "subscriber"))) { # ACK and CANCEL have no security mechanisms so they are just # noted /*if (method=="ACK" | method=="BYE") { log(1, "LOG: failed outbound authentication for ACK granted\n"); } else if (method=="CANCEL") { log(1, "LOG: failed outbound authentication for CANCEL granted\n"); }else {*/ proxy_challenge("192.168.1.223", "0"); break; #}; }; # to maintain credibility of our proxy, we check From in INVITEs if (!src_ip==192.168.1.223 & method=="INVITE" & !check_from()) { log(1, "LOG: Spoofed from attempt\n"); sl_send_reply("403", "Use From=id next time"); break; }; append_hf("P-hint: OUTBOUND ON INTERNET\r\n"); if (!t_relay()) { sl_reply_error(); break; }; } Thanks! -- +++ Lassen Sie Ihren Gedanken freien Lauf... z.B. per FreeSMS +++ GMX bietet bis zu 100 FreeSMS/Monat: http://www.gmx.net/de/go/mail

19 years, 6 months

[Serusers] SERWEB problems

by harry gaillac

Hello, I posted to you and serusers mailing list many mails about serweb in the past . You have been adding new features to serweb however I would have liked finding more documentation and roadmap for serweb project . Could you tell me more about XXL ? I downloaded the latest release two day ago (unstable) by hoping it would run well with ser (unstable) . I still wish to test accounting, missed call, message stored, ... but after setting up serweb I get these messages after a user is logged. Regards Harry Warning: require_and_agregate_methods(../../data_layer/method.clear_proxy_xxl.php): failed to open stream: No such file or directory in /var/www/serweb/html/data_layer.php on line 120 Fatal error: require_and_agregate_methods(): Failed opening required '../../data_layer/method.clear_proxy_xxl.php' (include_path='.:/usr/share/php:/usr/share/pear') in /var/www/serweb/html/data_layer.php on line 120 ___________________________________________________________________________________________________ Le nouveau Yahoo! Messenger est arrivé ! Découvrez toutes les nouveautés pour dialoguer instantanément avec vos amis. A télécharger gratuitement sur http://fr.messenger.yahoo.com

19 years, 6 months

[Serusers] starting SER - ld.preload.so

by Gerard Wagener

Hello, I have some problems with launching SER. When I start it, I receive no error, the return value of SER is 0, but I cannot find SER's PID (ps -A | grep "ser"). when I started SER with strace (strace ser start) I noticed that the access to ld.preload.so fails, because I have no such file. Does anybody know where I can obtain this library? Has the glibc to be pachted? Or is the problem somewhere else? Here's my configuration: Suse Linux 9.3 ser 0.9.0 glibc 2.3.3-118 kernel 2.6.8-24.14 gcc 3.3.4 bison 1.875 flex 2.5.4 make 3.80 sed 4.1.2 coreutils 5.2.1 Ser was installed as follows tar -vzxf ser-0.9.0_src.tar.gz cd ser-0.9.0 make all make install Thanks a lot, G�rard __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

19 years, 6 months

[Serusers] don't succeed the install

by michael p

hi everybody i don't succeed to install ser on my debian written: "... dev:/var/www/dev/michael# dpkg -i ser_0.8.14_i386.deb (Lecture de la base de données... 45264 fichiers et répertoires déjà installés.) Préparation du remplacement de ser 0.8.14 (en utilisant ser_0.8.14_i386.deb) ... Stopping ser: ser. Dépaquetage de la mise à jour de ser ... Paramétrage de ser (0.8.14) ... Restarting ser: serERROR: loading config file(/etc/ser/ser.cfg): No such file or directory invoke-rc.d: initscript ser, action "restart" failed. ser failed to (re)start. Perhaps your configuration requires additional modules (e.g. ser-mysql-module, ser-jabber-module or ser-radius-modules). Next try to install any additional ser modules you might need and then (re)start ser by executing the command '/etc/init.d/ser start|restart'. ..." i try to install ser-mysql-module but it doesn't change please help me thanks Michael ps: the install notes are not very well understanding . is there something else?

19 years, 6 months

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