sr-users April 2006

sr-users@lists.kamailio.org

188 participants
431 discussions

by Jan Bollen

Hi, Last week when I installed SER on Debian, I encounterd the same problem. The MySQl manual gives you a couple of courses of actions: See http://downloads.mysql.com/docs/refman-4.1-en.a4.pdf section A.2.3 ------------------------------------------------------------ A.2.3. Client does not support authentication protocol MySQL 4.1 and up uses an authentication protocol based on a password hashing algorithm that is incompatible with that used by older clients. If you upgrade the server to 4.1, attempts to connect to it with an older client may fail with the following message: shell> mysql Client does not support authentication protocol requested by server; consider upgrading MySQL client To solve this problem, you should use one of the following approaches: 1 Upgrade all client programs to use a 4.1.1 or newer client library. 2 When connecting to the server with a pre-4.1 client program, use an account that still has a pre-4.1-style password. **3 Reset the password to pre-4.1 style for each user that needs to use a pre-4.1 client program. This can be done using the SET PASSWORD statement and the OLD_PASSWORD() function: mysql> SET PASSWORD FOR -> 'some_user'@'some_host' = OLD_PASSWORD('newpwd'); Substitute the password you want to use for �newpwd� in the preceding examples. MySQL cannot tell you what the original password was, so you'll need to pick a new one. - Tell the server to use the older password hashing algorithm: ** 1. Start mysqld with the --old-passwords option. ------------------------------------------------------------ The actions marked with ** above is what I did and after restarting MySQl it worked fine. cheers, Jan =========================================================== Hi again, Thank you for your quick answer. Here is my error log output. Serweb [error] file:/usr/home/dev/serweb-0.9.4/html/data_layer.php:465 DB Error: connect failed - [native code = Client does not support authentication protocol requested by server; consider upgrading MySQL client] ** mysql://ser:heslo@localhost/ser When i read MySQL Reference Manual i see that, MySQL changed its password style in 4.1 or newer versions. (in Serweb install manual it writes MySQL 4.0, i didn't think that it could be a problem and installed 4.1.13) What do you advice me to do? Gokay

18 years, 7 months

[Users] Which RFC openser support ?

by Nguyen Duc Phi

Hello, Could you let me know "Does Operser support the following RFC?" RFC 2445 Time definition RFC 2869 RADIUS Extensions RFC 2868 RADIUS Attributes for Tunnel Protocol Support RFC 2867 RADIUS Accounting Modifications for Tunnel Protocol Support Best regards, Nguyen

18 years, 7 months

Re: Re: [Serusers] Serweb problem

by Gokay Tosunoglu

Hi again, Thank you for your quick answer. Here is my error log output. Serweb [error] file:/usr/home/dev/serweb-0.9.4/html/data_layer.php:465 DB Error: connect failed - [native code = Client does not support authentication protocol requested by server; consider upgrading MySQL client] ** mysql://ser:heslo@localhost/ser When i read MySQL Reference Manual i see that, MySQL changed its password style in 4.1 or newer versions. (in Serweb install manual it writes MySQL 4.0, i didn't think that it could be a problem and installed 4.1.13) What do you advice me to do? Gokay Hi, the problem is, that serweb cannot connect to your mysql. Check your serweb log (logging have to be enabled in serweb config). There should be more descriptive info. Karel Gokay Tosunoglu napsal(a): > Hi, > I'm a new ser user and have a problem with serweb. > I installed a new system of Freebsd 6.0, apache 1.3.33, php 4.3.11, > mysql 4.1.13, ser-0.9.6 and serweb-0.9.4 . > All configurations are seem to be ok. (ser_mysql.sh is ok, too.) I enter > the admin login screen of serweb and write admin:heslo as > username:password. The js automatically completing the username to my > default domain so it becomes "admin(a)multitekarge.com" and i can't login. > The error message is : > " > DB Error: connect failed > Bad username or password > " > Altough for database, name is "ser", user is "ser" and pass is "heslo" > in config_data_layer.php, it cannot connect. > > I also added a new user to ser by typing > " > serctl add gokay(a)multitekarge.com gokay gokay.tosunoglu(a)avrupayazilim.com > " > and tried to enter with that user in user login screen. I got the same > error. > > I'll got lot of pleasure of any help. > Thanks, > Gokay > > _______________________________________________ > Serusers mailing list > serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers

18 years, 7 months

[Serusers] Problem with forwarding - 480 response.

by Tomasz Stafin

Helo Thanks for help but my gateway is isdn gateway. This kind of gateway send a response "486" to server when user is busy and 480 when isdn is offline. T_on_failure will forward a transaction when 486 return but i wanted to forward only if 480 response return to server. Thanks for help. TS

18 years, 7 months

[Serusers] Ser as a presence server with other SIP prox as registrar and rtp proxy

by İlker Aktuna (Koç.net)

Hi, I am using the following routing configuration for testing Ser as a presence server only. The aim is to route all register, invite and other audio related messages to the main SIP and RTP proxy while keeping presence messages to SER. But there are some configuration parts that I don't understand: 1- if I remove the following lines from route[2] , client can't register through Ser. if (!t_newtran()) { log(1, "newtran error\n"); sl_reply_error(); break; }; 2- What is the meaning of : if (uri==myself) { ? I just commented this out and it seems to work. 3- Can anyone explain me the meaning of following lines: # if (!method=="REGISTER") record_route(); # if (loose_route()) { # # mark routing logic in request # append_hf("P-hint: rr-enforced\r\n"); # route(1); # break; # }; Thanks, İlker Below is my full routing configuration: # main routing logic route{ # XML RPC if (method == "POST" || method == "GET") { create_via(); dispatch_rpc(); break; } # 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 # if (!method=="REGISTER") record_route(); # subsequent messages withing a dialog should take the # path determined by record-routing # if (loose_route()) { # # mark routing logic in request # append_hf("P-hint: rr-enforced\r\n"); # route(1); # 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 (!lookup_domain("To")) { #xlog("L_ERR", "URI=MYSELF\n"); #xlog("L_ERR", "to: %tu from: %fu\n"); # log(1, "Unknown domain - message should be forwarded?"); # route(1); # break; # } # } if (method=="REGISTER") { xlog("L_ERR", "REGISTER\n"); xlog("L_ERR", "to: %tu from: %fu\n"); append_hf("P-hint: outbound\r\n"); save_noreply("location"); route(2); break; }; if (method=="INVITE") { xlog("L_ERR", "INVITE\n"); xlog("L_ERR", "to: %tu from: %fu\n"); if (!lookup("location")) { route(2); break; }; if (lookup("location")) { route(1); break; }; }; if (method=="MESSAGE") { xlog("L_ERR", "MESSAGE\n"); xlog("L_ERR", "to: %tu from: %fu\n"); if (!lookup("location")) { sl_send_reply("404","Not found"); break; }; route(1); break; }; if (method=="NOTIFY") { xlog("L_ERR", "NOTIFY\n"); xlog("L_ERR", "to: %tu from: %fu\n"); if (!lookup("location")) { sl_send_reply("404","Not found"); break; }; route(1); break; }; if (method=="SUBSCRIBE") { xlog("L_ERR", "SUBSCRIBE\n"); xlog("L_ERR", "to: %tu from: %fu\n"); if (!t_newtran()) { # creates a new transaction sl_reply_error(); break; }; handle_subscription("registrar"); break; }; if (method=="PUBLISH") { xlog("L_ERR", "PUBLISH\n"); xlog("L_ERR", "to: %tu from: %fu\n"); if (!t_newtran()) { sl_reply_error(); break; }; handle_publish("registrar"); break; }; xlog("L_ERR", "OTHER\n"); xlog("L_ERR", "to: %tu from: %fu\n"); if (!lookup("location")) { route(2); break; }; if (lookup("location")) { route(1); break; }; # append_hf("P-hint: outbound\r\n"); # route(2); # break; } route[1] { xlog("L_INFO","t_relay()\n"); if (!t_relay()) { sl_reply_error(); }; } route[2] { if (!t_newtran()) { xlog("L_ERR", "newtran error ?????\n"); log(1, "newtran error\n"); sl_reply_error(); break; }; if (!t_forward_nonack("10.100.200.97", 5060)) { sl_reply_error(); }; xlog("L_ERR", "FORWARD\n"); } <http://387555.sigclick.mailinfo.com/sigclick/04090107/04074E00/07094A00/171…> _____________________________________________________________________________________________________________________________________________ Bu e-posta mesaji kisiye ozel olup, gizli bilgiler iceriyor olabilir. Eger bu e-posta mesaji size yanlislikla ulasmissa, icerigini hic bir sekilde kullanmayiniz ve ekli dosyalari acmayiniz. Bu durumda lutfen e-posta mesajini kullaniciya hemen geri gonderiniz ve tum kopyalarini mesaj kutunuzdan siliniz. Bu e-posta mesaji, hic bir sekilde, herhangi bir amac icin cogaltilamaz, yayinlanamaz ve para karsiligi satilamaz. Bu e-posta mesaji viruslere karsi anti-virus sistemleri tarafindan taranmistir. Ancak yollayici, bu e-posta mesajinin - virus koruma sistemleri ile kontrol ediliyor olsa bile - virus icermedigini garanti etmez ve meydana gelebilecek zararlardan dogacak hicbir sorumlulugu kabul etmez. This message is intended solely for the use of the individual or entity to whom it is addressed , and may contain confidential information. If you are not the intended recipient of this message or you receive this mail in error, you should refrain from making any use of the contents and from opening any attachment. In that case, please notify the sender immediately and return the message to the sender, then, delete and destroy all copies. This e-mail message, can not be copied, published or sold for any reason. This e-mail message has been swept by anti-virus systems for the presence of computer viruses. In doing so, however, sender cannot warrant that virus or other forms of data corruption may not be present and do not take any responsibility in any occurrence. _____________________________________________________________________________________________________________________________________________

18 years, 7 months

[Users] Need urgent help/pointers reg. Mediaproxy

by Dave

I had posted the following a few days ago and received no response. Can someone please help! Hello,I have the following setup: UA<->NAT<-->SER/MediaProxy<->Prepaid(B2BUA)<-->PSTNGW | IVR Nat'd user calls a number that is forwarded (t_relay) to Prepaid and the user is prompted for PIN#/Destination Phone# and all works fine. Mediaproxy is invoked and a mediaproxy port# (35774) is assigned during the whole process. Once the user enters the destination number, the Prepaid forwards the call to the PSTNGW and the PSTN phone rings (Call signalling working fine). When the PSTN phone is answered, no media can be heard!!! I did some investigation and here is what is happening: Once the user enters the destination# to dial, The Prepaid/B2BUA does two things: 1) Sends a re-invite to put the UA on hold. 2) Sends an INVITE to the PSTN GW and retrieves the SDP from the response from PSTN GW 3) Sends a second-reinvite to the UA via SER with the SDP info of the PSTNGW 4) SER invokes the mediaproxy (since it is reinvite) and assigns the SAME MEDIAPROXY PORT# as earlier on when the media was flowing fine (SDP has audio port# 35774) 5) SER forwards the re-INVITE TO UA 6) UA responds with a 200 OK and sends 200 OK to SER. SER agains invokes mediaproxy and assigns the SAME MEDIAPROXY PORT# (audio port 35774) and forwards the response to Prepaid (which sends it to PSTNGW). I checked on Cisco PSTNGW that it is creating a session with the mediaproxy (port:35774). BUT NO AUDIO CAN BE HEARD IN ANY DIRECTION. Can anyone please help? Is this a mediaproxy issue that when reinvites are sent and mediaproxy is invoked multiple times, issues arise? I am running the latest mediaproxy version. --------------------------------- Have a question? Yahoo! Canada Answers. Go to Yahoo! Canada Answers

18 years, 7 months

[Users] comparing an avp to a null value

by Tavis P

I've been trying to make a comparison, using avp_check, between a pseudo variable (copied to an avp) and a null value (which is a valid state for some pseudo varibles currently) I havn't had any luck in being able to determine if an avp is null short of using a regex (which i try to avoid) so i thought i would mention this here, perhaps this functionality may be seen as useful to others or simply useful in general (tm) Here is a quick example of what i'm currently doing ---- # Store the destination IP into an AVP avp_printf("i:450", "$dd"); In this case, $dd is null because the destination set contains a domain for this branch avp_printf("i:451", "$si"); if ( avp_check("i:450", "re/^.{0,0}$/g") ) { xlog("L_WARN", "[$fU] Route{4}: AVP I:450 was empty"); } ---- I think it was probably thought that an avp should never have a null value therefor there was no logic added to any of the functions used to check/print/write avps which allowed for the creation/evaluation of NULL, however it would be advantageous in the least to include this functionality somewhere (other than regex matches) a few things that i've tried, that were no successful ---- # Store the destination IP into an AVP avp_printf("i:450", "$dd"); avp_printf("i:451", "$si"); avp_printf("i:452", ""); This will break script compilation avp_write("i:452", ""); This will break script compilation avp_write("i:452", "s:"); This will break script compilation if ( avp_check("i:450", "eq//g") ) { xlog("L_WARN", "[$fU] Route{4}: AVP I:450 was empty"); } if ( avp_check("i:450", "eq/0x/g") ) { xlog("L_WARN", "[$fU] Route{4}: AVP I:450 was empty"); } if ( avp_check("i:450", "eq/i:452/g") ) { xlog("L_WARN", "[$fU] Route{4}: AVP I:450 was empty"); } ----

18 years, 7 months

[Users] Error using subst function

by Dmitry Lyubimkov

We need to make 2 transformations in URI and To field 1. Convert telephone number to to format E.164 2. To correct a domain part of the address if it is set incorrectly by stupid UA All this is done through set of if operators because every of transformations can be absent or can be done on own algorithm. Let's consider a special case. We have on an input 799111(a)62.33.22.14 and on an output should receive 78142799111(a)voapp.ru URI will be transformed by these commands subst_uri("/^sip:([0-9]+)@(.*)/sip:78142\1@\2/i"); subst_uri("/^sip:([0-9]+)@(.*)/sip:\1@voapp.ru/i"); To field will be transformed by these commands subst("/^To:(.*)sip:([0-9]+)@(.*)/To:\1sip:78142\2@\3/i"); subst("/^To:(.*)sip:([0-9]+)@([0-9]+)\.([0-9]+)\.([0-9]+)\.([0-9]+)(.*)/ To:\1sip:\2@voapp.ru\7/i"); We test and get dump of messages using tcpdump We receive from UA INVITE sip:705353@62.33.22.14 SIP/2.0 Via: SIP/2.0/UDP 192.168.13.15 From: ......._1 <sip:gan@192.168.13.15>;tag=22683200-29298-10909 To: <sip:705353@62.33.22.14> ............ We make transformation and sent following: INVITE sip:78142705353@voapp.ru SIP/2.0 Max-Forwards: 10 Record-Route: <sip:62.33.22.14;ftag=22683200-29298-10909;lr> Via: SIP/2.0/UDP voapp.ru:5060;branch=z9hG4bKa4db.e5fa9a02.0 Via: SIP/2.0/UDP 192.168.13.15;rport=53809;received=217.107.59.194 From: ......._1 <sip:gan@192.168.13.15>;tag=22683200-29298-10909 To: <sip:78142705353@62.33.22.14> To: <sip:705353@voapp.ru> ............... As you can see URI was transformed correctly And instead of To field we have 2 To fields everyone corresponding to one of transformations. It is a bug? Or it is feature OpenSER? Whether it is possible to bypass this restriction? I understand that it is possible to make one subst call instead of two calls. subst("/^To:(.*)sip:([0-9]+)@([0-9]+)\.([0-9]+)\.([0-9]+)\.([0-9]+)(.*)/ To:\1sip:78142\2@voapp.ru\7/i"); But in a reality the algorithm is much more complex. And that instead of several consecutive transformations to leave one it is required to use a many of if operators. It is very inconvenient, conducts to mistakes and reduces readability of a code. Dmitry

18 years, 7 months

[Serusers] Serweb problem

by Gokay Tosunoglu

Hi, I'm a new ser user and have a problem with serweb. I installed a new system of Freebsd 6.0, apache 1.3.33, php 4.3.11, mysql 4.1.13, ser-0.9.6 and serweb-0.9.4 . All configurations are seem to be ok. (ser_mysql.sh is ok, too.) I enter the admin login screen of serweb and write admin:heslo as username:password. The js automatically completing the username to my default domain so it becomes "admin(a)multitekarge.com" and i can't login. The error message is : " DB Error: connect failed Bad username or password " Altough for database, name is "ser", user is "ser" and pass is "heslo" in config_data_layer.php, it cannot connect. I also added a new user to ser by typing " serctl add gokay(a)multitekarge.com gokay gokay.tosunoglu(a)avrupayazilim.com " and tried to enter with that user in user login screen. I got the same error. I'll got lot of pleasure of any help. Thanks, Gokay

18 years, 7 months

[Serusers] ser /tmp/webfifo errors, please help me

by mkumar＠mantragroup.com

Hi All, Everything was working fine until today when I started getting errors like below but still I am able to make and receive calls. 1(9504) ERROR: open_reply_pipe: open error (/tmp/webfifo_452863019): No such file or directory 1(9504) ERROR: fifo_stats: file /tmp/webfifo_452863019 bad: No such file or directory 1(9504) ERROR: fifo_server: command (t_stats) processing failed 1(9504) ERROR: open_reply_pipe: open error (/tmp/webfifo_109612442): No such file or directory 1(9504) ERROR: fifo_stats: file /tmp/webfifo_109612442 bad: No such file or directory 1(9504) ERROR: fifo_server: command (t_stats) processing failed Some settings with my machine might have changed as we worked on some system changes. Please tell me the reason for this errors and how to fix them? Thanks, Manoj.

18 years, 7 months

← Newer
1
...
34
35
36
37
38
39
40
...
44
Older →

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 April 2006