sr-users January 2004

sr-users@lists.kamailio.org

142 participants
338 discussions

[Serusers] [Vocal] Call for participants: SIP<>H323 Gateway
by Arnd Vehling 22 Jan '04

22 Jan '04

Hello, as the current versions of Vovidas siph323csgw doesnt support connections to H323 Gatekeepers i.e.: SIP UA <> SIP Proxy <> SIPH323csgw <> H323 Gatekeeper <> H323 Gateway we would like to enhance the software with that functionality and make it open source. Right now we have someone who is willing to programm the neccessary features into the siph323csgw for about EU 1000,-. Therefore i am asking who would be interested in donating to the project so we can all have a fully functional, industrial strength SIP to H323 converter. If we get like 4 more "donators" the total cost per participant would be EU 200,- (thats approx USD 215,- atm) Please contact me via email if interested. best regards, Arnd _______________________________________________ vocal mailing list vocal(a)vovida.org To unsubscribe, please go to http://www.vovida.org/mailman/listinfo/vocal

1 0

[Serusers] Draytek flooding iptel.org
by Jan Janak 22 Jan '04

22 Jan '04

Hello, Several users of iptel.org are using Draytek phones. Those phones are broken -- they are constantly flooding our server with REGISTER messages even if they got 200 OK (and the expires value is long enough). If you have such a phone please don't use it and ask the manufacturer to fix it. If you have direct contact to Draytek engineers (not technical support), please mail it to me. Jan.

1 0

[Serusers] SIP server compatibility
by Annie Sasidar 22 Jan '04

22 Jan '04

Hi, I am working on windowsce.net4.2. The voip architecture in this OS is based on SIP (RFC2543). I have been trying to register on the Linux SIP server running ser using a Provisioning.xml file which has the details required. I am getting the error " Unable to register, check server settings". I am running the ser-0.8.12 version on the linux box which is based on RFC 3261. Do you think there is a compatibility issue here? Does ser allow clients which are based on older RFC's to register? Any pointers will be greatly appreciated. Thanks, Annie

1 0

RE: [Serusers] error starting ser daemon with persistency support
by Klaus Darilion 22 Jan '04

22 Jan '04

be aware, the syntax has changed: (from 'sql' to 'mysql') modparam("usrloc", "db_url", "mysql://ser:xxxxx@localhost/ser") regards, klaus -----Original Message----- From: Bogdan-Andrei IANCU [mailto:iancu@fokus.fraunhofer.de] Sent: Thu 22.01.2004 17:23 To: Ziying Sherwin Cc: serusers(a)lists.iptel.org Subject: Re: [Serusers] error starting ser daemon with persistency support Hi, in config script, when setting the parameters for the usrloc module, you have something like: modparam("usrloc", "db_url", "sql://ser:xxxxx@localhost/ser") the sql url has this format: sql://user:password@host/database so, please update this URL conforming to your configuration. Bogdan Ziying Sherwin wrote: >Thank you very much for the help with the debug level. Now we can finally find >where the problem is. It seems that it has something to do with the MySQL >database access. We changed the username and password in both ser_mysql.sh >and serctl. So we got the following error message from the ser debug output: > > 0(29503) connect_db(): Access denied for user: 'ser@localhost' (Using password: YES) > 0(29503) db_init(): Error while trying to connect database > 0(29503) mod_init(): Error while connecting database > 0(29503) init_mod(): Error while initializing module usrloc >ERROR: error while initializing modules > >We did not find any place to reset the password and username in the ser.cfg >file, does that mean that those passwords and usernames are hard-coded into >the C files? Which files should we change to reflect the password/username >modification we made? > >Thanks again. > >Ziying Sherwin > > >On Thu, 22 Jan 2004, Bogdan-Andrei IANCU wrote: > > > >>Hi, >>increase the debug level in configuration file and you will see the line >>were the error lays in config script. >> >>Bogdan >> >>Ziying Sherwin wrote: >> >> >> >>>We are trying to compile ser 0.8.12 on Solaris 2.8 using gcc 3.3. The >>>compilation and installation go smoothly until we tried to start the ser >>>daemon with persistancy support. >>> >>>We followed the instructions listed on the website. First, we modified the >>>MySQL configuration file to increase the maximun connections allowed. Second >>>we restart the MySQL daemon. Third, we modified the ser_mysql.sh file to >>>set the username, password and path properly and used it to create the MySQL >>>tables. Then we modifid ser.cfg file and uncommented the following lines: >>> >>> loadmodule "/depot/package/ser_0.8.12/lib/ser/modules/mysql.so" >>> loadmodule "/depot/package/ser_0.8.12/lib/ser/modules/auth.so" >>> loadmodule "/depot/package/ser_0.8.12/lib/ser/modules/auth_db.so" >>> modparam("usrloc", "db_mode", 2) >>> modparam("auth", "calculate_ha1", yes) >>> modparam("auth_db", "password_column", "password") >>> >>>uncommented and modified the following lines: >>> >>> if (!www_authorize("<our domain name>", "subscriber")) { >>> www_challenge("<our domain name>", "0"); >>> break; >>> }; >>> >>>Finally, we tried to start the ser daemon by directly calling the binary "ser", >>>and the got the following error message: >>> >>> >>> >>> >>> >>>>ser >>>> >>>> >>>> >>>> >>>ERROR: bad config file (1 errors) >>> >>>How can we find where the error is? All the modules listed in the configuration >>>file are present in the directory. What else could go wrong? >>> >>>Thank you very much in advance. >>> >>>Ziying Sherwin >>> >>> >>>_______________________________________________ >>>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

1 0

[Serusers] nesws regarding vigros eternities
by Ric 22 Jan '04

22 Jan '04

pieces, How Vigras works. And you can better understand, what Vigras can do for you. If you are sensible about your health, reflect on what you can do for your seual health, to keep the chances that you will need Vigras as low as possible. puzzlings rituals secede, jailers. http://www.effectiveherbs.com/index.php?pid=genviag Inrease Seks Drive Bost Seual Performance Fuller & Harder Erecions Inrease Stamna & Endurance Quicker Rechages alleles Plainview floats, snores. machine intention profiteers, Abyssinia. Happy holidays, medicine

1 0

[Serusers] Problem with 0.8.13-dev-23-merged
by Andrea Girardi 22 Jan '04

22 Jan '04

Andrea Girardi writes: Hi when I start this version I can see in /var/log/messages that ser start correctly but when I try to check server status with serctl moni or simply by connect with MSN ser doesn't work. [cycle #: 1; if constant make sure server lives and fifo is on] I've tried to find some error on log but I didn't found nothing. I'm using a ser.cfg that correctly works with 0.8.12 Any idea? thanks, Andrea

1 0

RE: [Serusers] error starting ser daemon with persistency support
by Klaus Darilion 22 Jan '04

22 Jan '04

try to start ser in debug mode. at the begin of ser.cfg: debug=7 fork=no log_stderror=yes this will give you a lot of information and hints to the error! regards, klaus -----Original Message----- From: Ziying Sherwin [mailto:sherwin@lhc.nlm.nih.gov] Sent: Thu 22.01.2004 16:48 To: pelinescu-onciul(a)fokus.fraunhofer.de Cc: info(a)iptel.org; serusers(a)lists.iptel.org Subject: [Serusers] error starting ser daemon with persistency support We are trying to compile ser 0.8.12 on Solaris 2.8 using gcc 3.3. The compilation and installation go smoothly until we tried to start the ser daemon with persistancy support. We followed the instructions listed on the website. First, we modified the MySQL configuration file to increase the maximun connections allowed. Second we restart the MySQL daemon. Third, we modified the ser_mysql.sh file to set the username, password and path properly and used it to create the MySQL tables. Then we modifid ser.cfg file and uncommented the following lines: loadmodule "/depot/package/ser_0.8.12/lib/ser/modules/mysql.so" loadmodule "/depot/package/ser_0.8.12/lib/ser/modules/auth.so" loadmodule "/depot/package/ser_0.8.12/lib/ser/modules/auth_db.so" modparam("usrloc", "db_mode", 2) modparam("auth", "calculate_ha1", yes) modparam("auth_db", "password_column", "password") uncommented and modified the following lines: if (!www_authorize("<our domain name>", "subscriber")) { www_challenge("<our domain name>", "0"); break; }; Finally, we tried to start the ser daemon by directly calling the binary "ser", and the got the following error message: >ser ERROR: bad config file (1 errors) How can we find where the error is? All the modules listed in the configuration file are present in the directory. What else could go wrong? Thank you very much in advance. Ziying Sherwin _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

1 0

[Serusers] SER crashing because of too many interfaces
by Jan Knoppers 22 Jan '04

22 Jan '04

Hi, Our application requires a lot of PPP interfaces to be configured on our server (thousands of them). This causes SER (0.8.11) to crash (segmention fault) when started. Is this a known problem and is a fix available? Kind regards, Jan Knoppers

2 1

Re: [Serusers] Please help with PSTN
by Jiri Kuthan 22 Jan '04

22 Jan '04

move the gateway forwarding before lookup of IP users, that's it. -jiri At 04:40 AM 1/22/2004, Andy Singh wrote: >All, > >Please take a look at my ser.cfg . My sip domain is sipserv.foo.com. I can dial <mailto:3603@foo.com>3603(a)foo.com which is a PSTN number off of a PBX but can't dial <mailto:3603@sipserv.foo.com>3603(a)sipserv.foo.com. I get 404 not found. What can I change in my config file so I can dial <mailto:3603@sipserv.foo.com>3603(a)sipserv.foo.com. > ># > ># $Id: ser.cfg,v 1.21.4.1 2003/11/10 15:35:15 andrei Exp $ > ># > ># simple quick-start config script > ># > ># ----------- global configuration parameters ------------------------ > >#debug=3 # debug level (cmd line: -dddddddddd) > >#fork=yes > >#log_stderror=no # (cmd line: -E) > >/* Uncomment these lines to enter debugging mode > >debug=7 > >fork=no > >log_stderror=yes > >*/ > >check_via=no # (cmd. line: -v) > >dns=yes # (cmd. line: -r) > >rev_dns=no # (cmd. line: -R) > >#port=5060 > >#children=4 > >fifo="/tmp/ser_fifo" > ># ------------------ module loading ---------------------------------- > ># Uncomment this if you want to use SQL database > >loadmodule "/usr/lib/ser/modules/mysql.so" > >loadmodule "/usr/lib/ser/modules/sl.so" > >loadmodule "/usr/lib/ser/modules/tm.so" > >loadmodule "/usr/lib/ser/modules/rr.so" > >loadmodule "/usr/lib/ser/modules/maxfwd.so" > >loadmodule "/usr/lib/ser/modules/usrloc.so" > >loadmodule "/usr/lib/ser/modules/registrar.so" > ># Uncomment this if you want digest authentication > ># mysql.so must be loaded ! > >loadmodule "/usr/lib/ser/modules/auth.so" > >loadmodule "/usr/lib/ser/modules/auth_db.so" > ># ----------------- setting module-specific parameters --------------- > ># -- usrloc params -- > >#modparam("usrloc", "db_mode", 0) > ># Uncomment this if you want to use SQL database > ># for persistent storage and comment the previous line > >modparam("usrloc", "db_mode", 2) > ># -- auth params -- > ># Uncomment if you are using auth module > ># > >modparam("auth_db", "calculate_ha1", yes) > ># > ># If you set "calculate_ha1" parameter to yes (which true in this config), > ># uncomment also the following parameter) > ># > >modparam("auth_db", "password_column", "password") > ># -- rr params -- > ># add value to ;lr param to make some broken UAs happy > >modparam("rr", "enable_full_lr", 1) > ># ------------------------- request routing logic ------------------- > ># main routing logic > >route{ > > # initial sanity checks -- messages with > > # max_forwards==0, or excessively long requests > > if (!mf_process_maxfwd_header("10")) { > > sl_send_reply("483","Too Many Hops"); > > break; > > }; > > if ( msg:len > max_len ) { > > sl_send_reply("513", "Message too big"); > > break; > > }; > > # we record-route all messages -- to make sure that > > # subsequent messages will go through our proxy; that's > > # particularly good if upstream and downstream entities > > # use different transport protocol > > record_route(); > > # loose-route processing > > if (loose_route()) { > > t_relay(); > > break; > > }; > > # if the request is for other domain use UsrLoc > > # (in case, it does not work, use the following command > > # with proper names and addresses in it) > > if (uri==myself) { > > if (method=="REGISTER") { > ># Uncomment this if you want to use digest authentication > > if (!www_authorize("sipserv.foo.com", "subscriber")) { > > www_challenge("sipserv.foo.com", "0"); > > break; > > }; > > save("location"); > > break; > > }; > > # native SIP destinations are handled using our USRLOC DB > > if (!lookup("location")) { > > sl_send_reply("404", "Not Found"); > > break; > > }; > > }; > ># forward to current uri now; use stateful forwarding; that > > # works reliably even if we forward from TCP to UDP > > if (!t_relay()) { > > sl_reply_error(); > > }; > > attempt handoff to PSTN > >if (uri=~"^sip:3[0-9]*") { ## This assumes that the caller is > > log("Forwarding to PSTN\n"); ## registered in our realm > > forward( 156.151.96.253, 5060 ); ## Our Cisco router > > break; > > }; > >} > > > >Please help > >Thanks > >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

1 0

Re: [Serusers] ser not stopping -syslog error
by Annie Sasidar 22 Jan '04

22 Jan '04

Hi, I tried the "make install" . I get the message that all the modules are updated. However when i try to stop ser i get the same error in the syslog. module version mismatch for /usr/lib/ser/modules/dbtext.so; core:0.8.11;module:0.8.12 Please help. Thanks, Annie

3 2

← Newer
1
...
11
12
13
14
15
16
17
...
34
Older →

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 January 2004