sr-users

sr-users@lists.kamailio.org

12 participants
37062 discussions

by lgfausak＠august.net

I am constantly seeing this warning: Warning: 392 216.87.128.67:5060 "Noisy feedback tells: pid=3961 req_src_ip=216.87.128.68 in_uri=sip:216.87.128.67 out_uri=sip:216.87.128.67 via_cnt==1". What does it mean??? ---greg

21 years, 4 months

Re: [Serusers] new release of admin guide available

by lgfausak＠august.net

Thank you for the reply. I guess what I'm asking is what does stateful do? Does it take control of all requests relating to the current call-id from that point on? So my may route logic does not need to think about ACKs and retransmissions? ---greg > >At 07:08 PM 12/9/2002, Greg Fausak wrote: >>Has this documentation always been available? >> >>This is definately making a difference for me! > >We just released this documentation update. > >Yes, forward is built-in, t_relay/t_relay_to is >part of tm modules. forward(<host>,<port>) or >t_relay_to("<host>", "<port>") sends a request >to the address in params. forward(uri:host, uri:port) >and t_relay() sends a request to the address in current >URI. > >The trade-offs between stateless forward and stateful >t_relay are described in >http://www.iptel.org/ser/doc/seruser-html/x740.html#AEN839 > >If you do not not, whether to go stateful or stateless, >you will be probably better if with stateful. > >Cheers, > >-Jiri > >-- >Jiri Kuthan http://iptel.org/~jiri/ > >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers >

21 years, 4 months

Re: [Serusers] new release of admin guide available

by lgfausak＠august.net

Has this documentation always been available? This is definately making a difference for me! I am afraid this is all I needed to start asking some real stupid questions... I'll start with this, first, a few assertions: 'forward' is built in to the routing engine? forward(host, port) As I understand it, forward simply sends the message to the hostname and port I specify, statelessly. forward(uri:host, uri:port) This sends the message to the host and port as specified by the current uri, statelessly. 't_relay' is a module, not part of the main routing engine. t_relay_to(host, port) Send the message to host and port 'statefully'. t_relay() Send the message to the host and port as specified by the current uri, statefully. OK, now a question. These two sets of operations seem very similar on the surface. I think I understand 'statelessly', the message is simply fired off and all memory of the message is gone. I am trying to grasp 'stateful'. What exactly is different when using 't_relay()'? I am having a hard time coming to understand 'stateful' transactions. ---greg Greg Fausak August.Net Services, LLC > >http://www.iptel.org/ser/admin.html > >Comments very much appreciated. > >-Jiri > >-- >Jiri Kuthan http://iptel.org/~jiri/ > >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers >

21 years, 4 months

[Serusers] new release of admin guide available

by Jiri Kuthan

http://www.iptel.org/ser/admin.html Comments very much appreciated. -Jiri -- Jiri Kuthan http://iptel.org/~jiri/

21 years, 4 months

RE: RE: [Serusers] SER/SERWeb Howto...

by Jiri Kuthan

At 05:39 PM 12/6/2002, MANSOOR Usama FTRD/DMR/LON wrote: >>> My last question/issue is about dependancies. When I started working with SER >>> I already had MySQL install, version 3.23.36 I believe. I could not get the MySQL >>> portion integration to work, and found that permissions were not correctly granted. >>> After manually correcting the permissions, I had errors about the communications >>> between SER and MySQL. I updated MySQL to the latest stable release and >>> client programs, and the integration worked with no manual intervention. >> >> I personaly use 3.23.52 for development, but I am sure that 3.23.36 works, we use it. >> What kind of communication error did you get ? Could you send me some error logs ? > >I've also had similiar trouble regarding the permissions. I've installed v3.23.52 of MySQL, and run the ser_mysql.sh script, but get the following error message: > >Dec 6 14:50:42 localhost /usr/sbin/ser[4766]: connect_db(): Access denied for user: 'user(a)localhost.localdomain' (Using password: YES) >Dec 6 14:50:42 localhost /usr/sbin/ser[4766]: db_init(): Error while trying to connect database > >When I check the permissions I see the following: > >mysql> select * from user; >Where both 'ser' and 'serro' have no privileges at all. [...] I guess that's ok -- the user database just tells that these user have no general privileges to change any database. They are granted permissions for accessing ser database in the 'db' table. I have no clue where the error might live. Try manual login using mysql with the same username and password to get closer to the problem. -Jiri

21 years, 4 months

RE: RE: [Serusers] SER/SERWeb Howto...

by Dan Austin

Are you running the script as root? Before upgrading MySQL I did use the grant command, and managed to get the correct permissions installed. I ran into other problems with the client libraries, so I did a complete upgrade. After upgrading the ser_mysql.sh script did everyting it should have and I did not need to make any changes. I'm also fairly new to MySQL, but from your error message, it looks like you are running the script from an account that does not have permissions inside the database. As root if you run mysql, does it prompt for a password? From your select statement, I would not expect it to. If it allows you to logon to the database, you can try to assign the default permissions manually. Dan -----Original Message----- From: MANSOOR Usama FTRD/DMR/LON [mailto:usama.mansoor@rd.francetelecom.com] Sent: Friday, December 06, 2002 8:40 AM To: Jan Janak; serusers(a)lists.iptel.org Subject: RE: RE: [Serusers] SER/SERWeb Howto... >> My last question/issue is about dependancies. When I started working >> with SER I already had MySQL install, version 3.23.36 I believe. I >> could not get the MySQL portion integration to work, and found that >> permissions were not correctly granted. After manually correcting the >> permissions, I had errors about the communications between SER and >> MySQL. I updated MySQL to the latest stable release and client >> programs, and the integration worked with no manual intervention. > > I personaly use 3.23.52 for development, but I am sure that 3.23.36 > works, we use it. > What kind of communication error did you get ? Could you send me some error logs ? I've also had similiar trouble regarding the permissions. I've installed v3.23.52 of MySQL, and run the ser_mysql.sh script, but get the following error message: Dec 6 14:50:42 localhost /usr/sbin/ser[4766]: connect_db(): Access denied for user: 'user(a)localhost.localdomain' (Using password: YES) Dec 6 14:50:42 localhost /usr/sbin/ser[4766]: db_init(): Error while trying to connect database When I check the permissions I see the following: mysql> select * from user; +-----------------------+-------+------------------+-------------+-------------+-------------+-------------+-------------+-----------+-------------+---------------+--------------+-----------+------------+-----------------+------------+------------+ | Host | User | Password | Select_priv | Insert_priv | Update_priv | Delete_priv | Create_priv | Drop_priv | Reload_priv | Shutdown_priv | Process_priv | File_priv | Grant_priv | References_priv | Index_priv | Alter_priv | +-----------------------+-------+------------------+-------------+-------------+-------------+-------------+-------------+-----------+-------------+---------------+--------------+-----------+------------+-----------------+------------+------------+ | localhost | root | | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | | localhost.localdomain | root | | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | | localhost | | | N | N | N | N | N | N | N | N | N | N | N | N | N | N | | localhost.localdomain | | | N | N | N | N | N | N | N | N | N | N | N | N | N | N | | % | ser | 4e633cf914a735a0 | N | N | N | N | N | N | N | N | N | N | N | N | N | N | | localhost | ser | 4e633cf914a735a0 | N | N | N | N | N | N | N | N | N | N | N | N | N | N | | % | serro | 7cb73a267cb7bd5f | N | N | N | N | N | N | N | N | N | N | N | N | N | N | | localhost | serro | 7cb73a267cb7bd5f | N | N | N | N | N | N | N | N | N | N | N | N | N | N | +-----------------------+-------+------------------+-------------+-------------+-------------+-------------+-------------+-----------+-------------+---------------+--------------+-----------+------------+-----------------+------------+------------+ Where both 'ser' and 'serro' have no privileges at all. This is my first time using MySQL, so I'm not entirely sure how to resolve this. Do I use the 'grant' command, or is did you try something different? - Usama _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

21 years, 5 months

RE: RE: [Serusers] SER/SERWeb Howto...

by MANSOOR Usama FTRD/DMR/LON

>> My last question/issue is about dependancies. When I started working with SER >> I already had MySQL install, version 3.23.36 I believe. I could not get the MySQL >> portion integration to work, and found that permissions were not correctly granted. >> After manually correcting the permissions, I had errors about the communications >> between SER and MySQL. I updated MySQL to the latest stable release and >> client programs, and the integration worked with no manual intervention. > > I personaly use 3.23.52 for development, but I am sure that 3.23.36 works, we use it. > What kind of communication error did you get ? Could you send me some error logs ? I've also had similiar trouble regarding the permissions. I've installed v3.23.52 of MySQL, and run the ser_mysql.sh script, but get the following error message: Dec 6 14:50:42 localhost /usr/sbin/ser[4766]: connect_db(): Access denied for user: 'user(a)localhost.localdomain' (Using password: YES) Dec 6 14:50:42 localhost /usr/sbin/ser[4766]: db_init(): Error while trying to connect database When I check the permissions I see the following: mysql> select * from user; +-----------------------+-------+------------------+-------------+-------------+-------------+-------------+-------------+-----------+-------------+---------------+--------------+-----------+------------+-----------------+------------+------------+ | Host | User | Password | Select_priv | Insert_priv | Update_priv | Delete_priv | Create_priv | Drop_priv | Reload_priv | Shutdown_priv | Process_priv | File_priv | Grant_priv | References_priv | Index_priv | Alter_priv | +-----------------------+-------+------------------+-------------+-------------+-------------+-------------+-------------+-----------+-------------+---------------+--------------+-----------+------------+-----------------+------------+------------+ | localhost | root | | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | | localhost.localdomain | root | | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | Y | | localhost | | | N | N | N | N | N | N | N | N | N | N | N | N | N | N | | localhost.localdomain | | | N | N | N | N | N | N | N | N | N | N | N | N | N | N | | % | ser | 4e633cf914a735a0 | N | N | N | N | N | N | N | N | N | N | N | N | N | N | | localhost | ser | 4e633cf914a735a0 | N | N | N | N | N | N | N | N | N | N | N | N | N | N | | % | serro | 7cb73a267cb7bd5f | N | N | N | N | N | N | N | N | N | N | N | N | N | N | | localhost | serro | 7cb73a267cb7bd5f | N | N | N | N | N | N | N | N | N | N | N | N | N | N | +-----------------------+-------+------------------+-------------+-------------+-------------+-------------+-------------+-----------+-------------+---------------+--------------+-----------+------------+-----------------+------------+------------+ Where both 'ser' and 'serro' have no privileges at all. This is my first time using MySQL, so I'm not entirely sure how to resolve this. Do I use the 'grant' command, or is did you try something different? - Usama

21 years, 5 months

RE: [Serusers] What are aliases for?

by Jiri Kuthan

look at iptel.cfg: lookup("aliases"); #resolve aliases first if (!lookup("location")) { # and continue with canonical usernames then.. -Jiri At 01:09 AM 12/6/2002, Dan Austin wrote: >So something like this will do what I want? > > if (!lookup("location") and !lookup("aliases")) { > sl_send_reply("404", "Not Found"); > break; > }; > ># forward to current uri now > if (!t_relay()) { > sl_reply_error(); > }; > >Dan >-----Original Message----- >From: Jiri Kuthan [mailto:jiri@iptel.org] >Sent: Thursday, December 05, 2002 3:57 PM >To: Dan Austin; serusers(a)lists.iptel.org >Subject: Re: [Serusers] What are aliases for? > > >I hope to update the admin's guide this week and it should include information on how to set up aliases. Basically, >we use another "location" table to translate aliases to canonical usernames. The aliases can be maintained via the serctl utilitity, provided SQL persistency is turned on (otherwise they are gone on reboot). > >-Jiri > >At 11:38 PM 12/5/2002, Dan Austin wrote: >>My guess based on reading the developers and admin guides is that an >>account could be aliased to a DID number, or internal extension. >> >>In testing it doesn't seem to work that way. With two accounts, on a >>Cisco IP phone and the other on MSN client, calls can be placed based >>on the SIP account name, but not the alias. >> >> >>Thanks, >>Dan >>_______________________________________________ >>Serusers mailing list >>serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers > >-- >Jiri Kuthan http://iptel.org/~jiri/ > >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

21 years, 5 months

RE: [Serusers] What are aliases for?

by Dan Austin

So something like this will do what I want? if (!lookup("location") and !lookup("aliases")) { sl_send_reply("404", "Not Found"); break; }; # forward to current uri now if (!t_relay()) { sl_reply_error(); }; Dan -----Original Message----- From: Jiri Kuthan [mailto:jiri@iptel.org] Sent: Thursday, December 05, 2002 3:57 PM To: Dan Austin; serusers(a)lists.iptel.org Subject: Re: [Serusers] What are aliases for? I hope to update the admin's guide this week and it should include information on how to set up aliases. Basically, we use another "location" table to translate aliases to canonical usernames. The aliases can be maintained via the serctl utilitity, provided SQL persistency is turned on (otherwise they are gone on reboot). -Jiri At 11:38 PM 12/5/2002, Dan Austin wrote: >My guess based on reading the developers and admin guides is that an >account could be aliased to a DID number, or internal extension. > >In testing it doesn't seem to work that way. With two accounts, on a >Cisco IP phone and the other on MSN client, calls can be placed based >on the SIP account name, but not the alias. > > >Thanks, >Dan >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

21 years, 5 months

Re: [Serusers] What are aliases for?

by Jiri Kuthan

I hope to update the admin's guide this week and it should include information on how to set up aliases. Basically, we use another "location" table to translate aliases to canonical usernames. The aliases can be maintained via the serctl utilitity, provided SQL persistency is turned on (otherwise they are gone on reboot). -Jiri At 11:38 PM 12/5/2002, Dan Austin wrote: >My guess based on reading the developers and admin guides is >that an account could be aliased to a DID number, or internal >extension. > >In testing it doesn't seem to work that way. With two accounts, >on a Cisco IP phone and the other on MSN client, calls can be placed >based on the SIP account name, but not the alias. > > >Thanks, >Dan >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

21 years, 5 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