sr-users

sr-users@lists.kamailio.org

48 participants
37555 discussions

[Serusers] problem with phone authentication
by lgfausak＠august.net 18 Jan '03

18 Jan '03

This works with my eStara soft phone client: --------------cut # route[1], REGISTER block # REGISTER messages destined for our realm are forwarded here. # after a successful registration a customer can receive calls. # route[1] { if(!www_authorize("augustvoice.net", "subscriber")) { www_challenge("augustvoice.net", "0"); break; }; log("here is a register"); if(!save("location")) { sl_reply_error(); }; break; } ---------------uncut However, when I try to get my Cisco 7960 to authorize it fails. I've appended the ngrep trace of the failed transaction. The only difference I can see is that the line argument algorithm=MD5 is in the WWW-Authenticate line. Do I have to do something special to accept a MD5 password??? ---greg Greg Fausak ngrep trace: --------cut # U 216.87.128.66:5060 -> 64.90.42.25:5060 REGISTER sip:64.90.42.25 SIP/2.0. Via: SIP/2.0/UDP 216.87.128.66:5060;branch=f6645848fea927b96489c6a32e39a956.0. From: sip:2424377@64.90.42.25. To: sip:2424377@64.90.42.25. Call-ID: 003094c4-3d2f0002-23a6c56d-0dcb5c8f(a)192.168.100.101. Date: Sat, 18 Jan 2003 00:42:54 GMT. CSeq: 101 REGISTER. Contact: <sip:2424377@216.87.128.66>. Expires: 3600. Content-Length: 0. . # U 64.90.42.25:5060 -> 216.87.128.66:5060 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 216.87.128.66:5060;branch=f6645848fea927b96489c6a32e39a956.0. From: sip:2424377@64.90.42.25. To: sip:2424377@64.90.42.25;tag=af30b122c950f7c4343d8a73d2eaf455.2313. Call-ID: 003094c4-3d2f0002-23a6c56d-0dcb5c8f(a)192.168.100.101. CSeq: 101 REGISTER. WWW-Authenticate: Digest realm="augustvoice.net", nonce="3e28a43a000000005b6a30b9fa105b98b2fd9d1aa59c4c72", algorithm=MD5. Server: Sip EXpress router (0.8.10 (i386/linux)). Content-Length: 0. Warning: 392 register.augustvoice.net:5060 "Noisy feedback tells: pid=2262 req_src_ip=216.87.128.66 in_uri=sip:64.90.42.25 out_uri=sip:64.90.42.25 via_cnt==1". . # U 216.87.128.66:5060 -> 64.90.42.25:5060 REGISTER sip:64.90.42.25 SIP/2.0. Via: SIP/2.0/UDP 216.87.128.66:5060;branch=e71832739a0647b7ba91baa50bcc1497.0. From: sip:2424377@64.90.42.25. To: sip:2424377@64.90.42.25. Call-ID: 003094c4-3d2f0002-23a6c56d-0dcb5c8f(a)192.168.100.101. Date: Sat, 18 Jan 2003 00:42:54 GMT. CSeq: 102 REGISTER. Authorization: Digest username="2424377",realm="augustvoice.net",uri="sip:64.90.42.25",response="039cee96c9321217973c4914314fc3ed",nonce="3e28a43a000000005b6a30b9fa105b98b2fd9d1aa59c4c72",algorithm=MD5. Contact: <sip:2424377@216.87.128.66>. Expires: 3600. Content-Length: 0. . # U 64.90.42.25:5060 -> 216.87.128.66:5060 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 216.87.128.66:5060;branch=e71832739a0647b7ba91baa50bcc1497.0. From: sip:2424377@64.90.42.25. To: sip:2424377@64.90.42.25;tag=af30b122c950f7c4343d8a73d2eaf455.2581. Call-ID: 003094c4-3d2f0002-23a6c56d-0dcb5c8f(a)192.168.100.101. CSeq: 102 REGISTER. WWW-Authenticate: Digest realm="augustvoice.net", nonce="3e28a43a000000005b6a30b9fa105b98b2fd9d1aa59c4c72", algorithm=MD5. Server: Sip EXpress router (0.8.10 (i386/linux)). Content-Length: 0. Warning: 392 register.augustvoice.net:5060 "Noisy feedback tells: pid=2263 req_src_ip=216.87.128.66 in_uri=sip:64.90.42.25 out_uri=sip:64.90.42.25 via_cnt==1". .

3 2

[Serusers] ata
by Jan Janak 18 Jan '03

18 Jan '03

Hello, your messages about CISCO ATA reminds me that I have also one (a preproduction unit originally made by Komodo), so I upgraded firmware to 2.15 and tried it behind a symmetric NAT. It works, I had to enable portforwarding for signalling and media and setup properly outer address of the NAT box in the phone. Once you finish your NAThelper module, I would like to give it a try and see if it works without modifications of the NAT box. So I can help you to test the code if you want. regards, Jan.

1 0

[Serusers] [HEADS UP] security vulnerability in ser 0.8.10
by Maxim Sobolev 18 Jan '03

18 Jan '03

Folks, While playing with SER I found that I can trigger repeatable crash when doing REGISTER multiple times. Quick glance at the code in question revealed that indeed, when constructing reply to REGISTER message, SER uses fixed-lengh buffer to put all non-expired contacts for that user and doesn't bother to check for overflow. The bug could be easily exploited by a complete stranger on servers that don't perform authentification of REGISTER requests, and by an user with a valid credintals on server that do authentification. Mounting attack leads to denial of service. Attached please find fake REGISTER message, which if sent to open server kills it (nc -u my.sip.server 5060 < register.killser), and patch to fix the problem. -Maxim

3 2

[Serusers] Fwd: Guest Passes to TMC Internet Telephony Conference & Expo
by Jiri Kuthan 18 Jan '03

18 Jan '03

just in case someone would like to show up there. first come, first served. -jiri >Hello! > >Internet Telephony Conference & Expo is right around the corner! As a speaker and participant in the conference program, TMC would like to offer you (2) conference passes free of charge. These passes can be given to colleagues, clients, or guests that you would like to invite to hear you speak and to the show. These passes would be full conference passes and would allow that person to go to the entire event, not just to your session. > >If you would like to take advantage of this offer all you need to do is e-mail the following >information for each person: > >Name >Title >Company name >Address >Phone >Fax >E-mail > >Put "Internet Telephony Miami Speaker Conference Program" in the subject line and you are done! The pass will be sent to them in the mail. > >As a speaker, you will already have your speaker pass prepared. Please pick up your pass at the event registration. > >PLEASE NOTE - this program is not to replace an existing conference pass. No monies that might have been paid will be refunded.

1 0

RE: [Serusers] Password problem with ser and mysql
by Klaus Darilion 17 Jan '03

17 Jan '03

Yes, that was my problem! Thank you very mutch! Are you involved in the SHIP (http://voip.sh.cvut.cz/about.shtml) project? (because of your emailaddress). I read that you are using Vocal as voice mail server. Do you have an installation guide how to setup such a system with vocal and ser? regards, Klaus > -----Original Message----- > From: Jan Janak [mailto:J.Janak@sh.cvut.cz] > Sent: Friday, January 17, 2003 1:14 PM > To: Klaus Darilion > Cc: serusers(a)lists.iptel.org > Subject: Re: [Serusers] Password problem with ser and mysql > > > Hello, > > auth is not the only module that uses database. If you have > enabled support for database in usrloc (by modparam("usrloc", > "db_mode", 1) or modparam("usrloc", "db_mode", 2) then you > have to change usrloc's password as well. Try to use the > following: modparam("usrloc", "db_url", > "sql://ser:klaus@localhost/ser") > > regards, Jan.cd > > On 17-01 11:56, Klaus Darilion wrote: > > Hello Jan! > > > > Comments inline. > > > default username and password for auth module is > > > serro:47serro11, if you are able to login as ser:heslo, then > > > username and password can be changed. > > > > > If you change your password in mysql, you must change it for > > > ser@localhost For example: grant ALL on ser.* to > > > ser@localhost identified by 'klaus'; > > > > I changed it for localhost, but it won't work. > > > > > If you use something like grant ALL on ser.* to ser > > > identified by 'klaus'; then the server will be unable to > > > login to the database. > > > > > > Try also the following: > > > mysql -h localhost -u ser -p ser > > > > I changed the password of ser@localhost to 'klaus'. I can > connect to > > mysql with mysql -h localhost -u ser -p ser > > and password 'klaus'. I changed the password in ser.cfg to 'klaus' > > modparam("auth", "db_url", "sql://ser:klaus@localhost/ser") > > , but still the ser server can't start: > > : connect_db(): Access denied for user: 'ser@localhost' (Using > > password: YES) > > > > > > I still think there must be a bug somewhere, so that ser tries to > > connect with the 'heslo' password. > > > > regards, > > Klaus > > > > > This will prompt for password, if you are unable to login > > > with your password, ser will be unable to login as well > > > (probably because you changed password for ser and not for > > > ser@localhost) > > > > > > regards, Jan. > > > > > > On 16-01 18:34, Klaus Darilion wrote: > > > > Hello! > > > > > > > > I have sucessfully installed the ser server (0.8.10 from > > > rpms) with an > > > > mysql database. When I use the standard password for the user > > > > "ser" > > > > everything works fine. But if I change the password from > > > "heslo" to a > > > > new one, for example "klaus" instead of "heslo" (of > course in the > > > > mysql-database und in the config file) the ser server > can not start > > > > up. > > > > > > > > Following are some different configurations and my suggestions > > > > what > > > > could be the problem. > > > > > > > > ser.cfg: modparam("auth", "db_url", > > > > "sql://ser:heslo@localhost/ser") > > > > mySQL-root-password: XXXXX > > > > mySQL-ser-password: heslo > > > > ---> works fine > > > > > > > > ser.cfg: modparam("auth", "db_url", > > > > "sql://ser:klaus@localhost/ser") > > > > mySQL-root-password: XXXXX > > > > mySQL-ser-password: klaus > > > > ---> doesn't work: connect_db(): Access denied for user: > > > > ---> 'ser@localhost' > > > > (Using password: YES) > > > > should work, so I tried another user > > > > > > > > ser.cfg: modparam("auth", "db_url", > > > "sql://root:XXXXX@localhost/ser") > > > > mySQL-root-password: XXXXX > > > > mySQL-ser-password: heslo > > > > ---> works fine > > > > > > > > ser.cfg: modparam("auth", "db_url", > > > "sql://root:XXXXX@localhost/ser") > > > > mySQL-root-password: XXXXX > > > > mySQL-ser-password: klaus > > > > ---> doesn't work: connect_db(): Access denied for user: > > > > ---> 'ser@localhost' > > > > (Using password: YES) > > > > very strange, because I told ser to connect as root. Is ser > > > using the > > > > default user/password instead of the configured one? > > > > > > > > ser.cfg: modparam("auth", "db_url", > > > "sql://root:YYYYY@localhost/ser") > > > > mySQL-root-password: XXXXX > > > > mySQL-ser-password: heslo > > > > ---> doesn't work: connect_db(): Access denied for user: > > > > 'root@localhost' (Using password: YES) > > > > of course it doesn't work, wrong password. So ser cares > about the > > > > settings in ser.cfg > > > > > > > > So my suggestion is that ser connects several times to the > > > > database > > > > whereas one time it uses the configured user/password and > > > another time > > > > it uses the default user/password - maybe a bug in the auth > > > > module? > > > > > > > > Or does somebody of you changed the password successfuly? > > > > > > > > It would be nice if you can help me. > > > > > > > > Thanks, > > > > Klaus > > > > > > > > My system is: > > > > Linux version 2.4.18-14 (bhcompile(a)astest.test.redhat.com) > > > (gcc version > > > > 3.2 20020903 (Red Hat Linux 8.0 3.2-7)) #1 Wed Sep 4 > > > 12:13:11 EDT 2002 > > > > MySQL 3.23.52 > > > > ser-0.8.10-2.i386.rpm > > > > ser-mysql-0.8.10-2.i386.rpm > > > > _______________________________________________ > > > > 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 > > >

2 1

RE: [Serusers] Password problem with ser and mysql
by Jiri Kuthan 17 Jan '03

17 Jan '03

At 01:59 PM 1/17/2003, Klaus Darilion wrote: >Yes, that was my problem! Thank you very mutch! > >Are you involved in the SHIP (http://voip.sh.cvut.cz/about.shtml) >project? (because of your emailaddress). Jan is. >I read that you are using Vocal >as voice mail server. Do you have an installation guide how to setup >such a system with vocal and ser? I tried to deploy the vocal voicemail a while ago and it did not meet me expectations. We are working on our own now. -Jiri

1 0

RE: [Serusers] Password problem with ser and mysql
by Klaus Darilion 17 Jan '03

17 Jan '03

Hello Jan! Comments inline. > default username and password for auth module is > serro:47serro11, if you are able to login as ser:heslo, then > username and password can be changed. > If you change your password in mysql, you must change it for > ser@localhost For example: grant ALL on ser.* to > ser@localhost identified by 'klaus'; I changed it for localhost, but it won't work. > If you use something like grant ALL on ser.* to ser > identified by 'klaus'; then the server will be unable to > login to the database. > > Try also the following: > mysql -h localhost -u ser -p ser I changed the password of ser@localhost to 'klaus'. I can connect to mysql with mysql -h localhost -u ser -p ser and password 'klaus'. I changed the password in ser.cfg to 'klaus' modparam("auth", "db_url", "sql://ser:klaus@localhost/ser") , but still the ser server can't start: : connect_db(): Access denied for user: 'ser@localhost' (Using password: YES) I still think there must be a bug somewhere, so that ser tries to connect with the 'heslo' password. regards, Klaus > This will prompt for password, if you are unable to login > with your password, ser will be unable to login as well > (probably because you changed password for ser and not for > ser@localhost) > > regards, Jan. > > On 16-01 18:34, Klaus Darilion wrote: > > Hello! > > > > I have sucessfully installed the ser server (0.8.10 from > rpms) with an > > mysql database. When I use the standard password for the user "ser" > > everything works fine. But if I change the password from > "heslo" to a > > new one, for example "klaus" instead of "heslo" (of course in the > > mysql-database und in the config file) the ser server can not start > > up. > > > > Following are some different configurations and my suggestions what > > could be the problem. > > > > ser.cfg: modparam("auth", "db_url", "sql://ser:heslo@localhost/ser") > > mySQL-root-password: XXXXX > > mySQL-ser-password: heslo > > ---> works fine > > > > ser.cfg: modparam("auth", "db_url", "sql://ser:klaus@localhost/ser") > > mySQL-root-password: XXXXX > > mySQL-ser-password: klaus > > ---> doesn't work: connect_db(): Access denied for user: > > ---> 'ser@localhost' > > (Using password: YES) > > should work, so I tried another user > > > > ser.cfg: modparam("auth", "db_url", > "sql://root:XXXXX@localhost/ser") > > mySQL-root-password: XXXXX > > mySQL-ser-password: heslo > > ---> works fine > > > > ser.cfg: modparam("auth", "db_url", > "sql://root:XXXXX@localhost/ser") > > mySQL-root-password: XXXXX > > mySQL-ser-password: klaus > > ---> doesn't work: connect_db(): Access denied for user: > > ---> 'ser@localhost' > > (Using password: YES) > > very strange, because I told ser to connect as root. Is ser > using the > > default user/password instead of the configured one? > > > > ser.cfg: modparam("auth", "db_url", > "sql://root:YYYYY@localhost/ser") > > mySQL-root-password: XXXXX > > mySQL-ser-password: heslo > > ---> doesn't work: connect_db(): Access denied for user: > > 'root@localhost' (Using password: YES) > > of course it doesn't work, wrong password. So ser cares about the > > settings in ser.cfg > > > > So my suggestion is that ser connects several times to the database > > whereas one time it uses the configured user/password and > another time > > it uses the default user/password - maybe a bug in the auth module? > > > > Or does somebody of you changed the password successfuly? > > > > It would be nice if you can help me. > > > > Thanks, > > Klaus > > > > My system is: > > Linux version 2.4.18-14 (bhcompile(a)astest.test.redhat.com) > (gcc version > > 3.2 20020903 (Red Hat Linux 8.0 3.2-7)) #1 Wed Sep 4 > 12:13:11 EDT 2002 > > MySQL 3.23.52 > > ser-0.8.10-2.i386.rpm > > ser-mysql-0.8.10-2.i386.rpm > > _______________________________________________ > > Serusers mailing list > > serusers(a)lists.iptel.org > > http://lists.iptel.org/mailman/listinfo/serusers > > >

2 1

[Serusers] SER & IPv6
by Antonino Mendes Monteiro 17 Jan '03

17 Jan '03

Hello, I would like to know if SER supports IPv6. If not, do you have any plans for it ? When ? Thanks in advance, Antonino

2 1

[Serusers] Password problem with ser and mysql
by Klaus Darilion 16 Jan '03

16 Jan '03

Hello! I have sucessfully installed the ser server (0.8.10 from rpms) with an mysql database. When I use the standard password for the user "ser" everything works fine. But if I change the password from "heslo" to a new one, for example "klaus" instead of "heslo" (of course in the mysql-database und in the config file) the ser server can not start up. Following are some different configurations and my suggestions what could be the problem. ser.cfg: modparam("auth", "db_url", "sql://ser:heslo@localhost/ser") mySQL-root-password: XXXXX mySQL-ser-password: heslo ---> works fine ser.cfg: modparam("auth", "db_url", "sql://ser:klaus@localhost/ser") mySQL-root-password: XXXXX mySQL-ser-password: klaus ---> doesn't work: connect_db(): Access denied for user: 'ser@localhost' (Using password: YES) should work, so I tried another user ser.cfg: modparam("auth", "db_url", "sql://root:XXXXX@localhost/ser") mySQL-root-password: XXXXX mySQL-ser-password: heslo ---> works fine ser.cfg: modparam("auth", "db_url", "sql://root:XXXXX@localhost/ser") mySQL-root-password: XXXXX mySQL-ser-password: klaus ---> doesn't work: connect_db(): Access denied for user: 'ser@localhost' (Using password: YES) very strange, because I told ser to connect as root. Is ser using the default user/password instead of the configured one? ser.cfg: modparam("auth", "db_url", "sql://root:YYYYY@localhost/ser") mySQL-root-password: XXXXX mySQL-ser-password: heslo ---> doesn't work: connect_db(): Access denied for user: 'root@localhost' (Using password: YES) of course it doesn't work, wrong password. So ser cares about the settings in ser.cfg So my suggestion is that ser connects several times to the database whereas one time it uses the configured user/password and another time it uses the default user/password - maybe a bug in the auth module? Or does somebody of you changed the password successfuly? It would be nice if you can help me. Thanks, Klaus My system is: Linux version 2.4.18-14 (bhcompile(a)astest.test.redhat.com) (gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)) #1 Wed Sep 4 12:13:11 EDT 2002 MySQL 3.23.52 ser-0.8.10-2.i386.rpm ser-mysql-0.8.10-2.i386.rpm

2 1

[Serusers] problems getting started with ser/serweb
by Stephan Reiff-Marganiec 16 Jan '03

16 Jan '03

Hi, I have installed ser and was amazed how easy it was to install (we have previously experimented with sipd, which finally runs ...). I have run through the archives and also looked at all the documentation, but some things still don't work. I use kphone 2.11 as client, but have tried sipc on a solaris box to the same extend. I am running kphone and ser 0.8.10 on redhat 8. MySQL is 3.23.52. I have set the domain/realm things to cs.stir.ac.uk and restarted ser. I have then set up a user using "serctl add srm test srm(a)cs.stir.ac.uk". Now, on serweb in user_interface/index I cannot login with this user. In kphone, I cannot register (it works ok on the columbia server): ----kphone says------------------------------------------ SipTransaction: Retransmit 1 (4000) SipClient: Sending: 15:09:37.098 -------------------------------- REGISTER sip:cs.stir.ac.uk SIP/2.0 Via: SIP/2.0/UDP 139.153.254.196:5062 CSeq: 488 REGISTER To: "Stephan" <sip:srm@cs.stir.ac.uk> Expires: 900 From: "Stephan" <sip:srm@cs.stir.ac.uk> Call-ID: 1902284369(a)139.153.254.196 Content-Length: 0 User-Agent: KPhone/2.11 Event: registration Allow-Events: presence Contact: "root" <sip:root@139.153.254.196:5062;transport=udp>;methods="INVITE, MESSAGE, INFO, SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK" SipClient: Receiving message... SipClient: Received: 15:09:39.724 --------------------------------- SIP/2.0 478 Unresolveable destination (478/TM) Via: SIP/2.0/UDP 139.153.254.196:5062 CSeq: 488 REGISTER To: "Stephan" <sip:srm@cs.stir.ac.uk>;tag=0a96755a1d32d0360b3e454593e5079b-9b73 From: "Stephan" <sip:srm@cs.stir.ac.uk> Call-ID: 1902284369(a)139.153.254.196 Server: Sip EXpress router (0.8.10 (i386/linux)) Content-Length: 0 Warning: 392 139.153.254.196:5060 "Noisy feedback tells: pid=5138 req_src_ip=139.153.254.196 in_uri=sip:cs.stir.ac.uk out_uri=sip:cs.stir.ac.uk via_cnt==1" --- end kphone ----------------------------------------------------- ser does answer, the Replied locally counter in serctl moni reflects this ok. what is wrong? do you need any other files? In case you need more detail, where exactly is the server log?? by the way, I have tried this with auth turned on and off in ser.cfg. and without persistence. always the same ... thanks S -- Dr Stephan Reiff-Marganiec Research Fellow Department of Computing Science; University of Stirling email: srm(a)cs.stir.ac.uk tel: 01786 46 7448 -- The University of Stirling is a university established in Scotland by charter at Stirling, FK9 4LA. Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not disclose, copy or deliver this message to anyone and any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of the University of Stirling shall be understood as neither given nor endorsed by it.

2 1

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