sr-users June 2004

sr-users@lists.kamailio.org

176 participants
387 discussions

by Cyprien Simons

Hi, I'm quite new to ser, and I can't launch it. So, first things first : I got SuSE 9.1, ser 0.8.12. I placed the ser directory in /usr/local, I compile it with "make all" and install it with "make install". When I tip /usr/local/ser/ser I get "listening on <the adresses>", "aliases"... as if everything was ok, but I can't see any ser proc when I make a top. So - if ser is running - how do I do to know if it's running? And second question, how do I do to stop ser after that? regards, Cyprien

19 years, 11 months

RE: [Serusers] Calling thru serweb

by Freddy Parra

Hi Gala, I think the serweb user interface client needs to me smart in this case and send a registration request to ser, when the user logs into their serweb account. I don't think this is implemented in serweb. Now if either of the users is register to ser using some other UA client such as windows messenger or sip phone then you should be able to see from serweb that they are logged in. I know that if a user is logged in using windows messenger, that you can actually see that the user is online and even sent that UA a text message from serweb. I guess is just a question of implementing registration into serweb when a user logs into their serweb account and implementing voice calls on serweb is equivalent to a sip soft phone such as windows messenger. Regards, Freddy -----Original Message----- From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org]On Behalf Of Gala, Dipen Sent: Thursday, June 24, 2004 9:51 AM To: serusers(a)lists.iptel.org Subject: [Serusers] Calling thru serweb Hey I am playing a simple game here.i want two online users logged in to the ser through serweb. When I add the opposite person in the phone book I don't see them online, they appear offline always. I have mysql running with ser and serweb. I have not used radius server. So my question is how can I make calls between two users online through serweb? \ If any one can share is config file for ser it will be of great help. thanks Dipen K Gala Fidelity Investments System Company - Telecom Phone: (617) 563-2729 Email: Dipen.Gala(a)FMR.com

19 years, 11 months

SV: [Serusers] ENUM parsing error?

by Kerker Staffan

Hi Hm.. I noticed that one too, but the Cisco proxy is recieving exactly the same expression and then there is no problem. The NAPTR RR in DNS for extension 2210 looks like: $ORIGIN 1.2.2.e164.mydomain.com. 0 NAPTR 100 10 "u" "sip+E2U" "/^(.*)$/sip:\\1@iptel2.mydomain.com/" . Any clues? rgds, /Staffan -----Ursprungligt meddelande----- Från: Juha Heinanen [mailto:jh@tutpro.com] Skickat: den 24 juni 2004 06:54 Till: Kerker Staffan Kopia: serusers(a)lists.iptel.org Ämne: [Serusers] ENUM parsing error? Kerker Staffan writes: > The regular expression I'm getting back is like this: > > sip+E2U#/^(.*)$/sip:\1@mydomain.com/ what is sip+E2U# in front of the regexp field? can you show me how exactly the NAPTR record looks like? -- juha

19 years, 11 months

Re: [Serusers] CPL-C and call forward on busy or no answer

by Brinker, Oliver

Hi Bogdan, Exactly that was the problem ;-) After removing the proxy_route param call forward on busy or no answer works. Is it possible to control the timeout value for call forward on no answer via the CPL script? Only changing "modparam("tm","fr_inv_timer",30)" in ser.cfg seems to take effect. Again, many thanks for your help. Regards, Oliver Bogdan-Andrei IANCU [mailto:iancu@fokus.fraunhofer.de] wrote Hi Oliver, The problem is in your configuration :-). cpl-c module param "proxy_route" doesn't refer to a route that does proxy(relying) as you configure, but to a route to be processed before cpl-c does proxy (this is does internally). So. basically you were trying to do twice transaction creations and req. relaying. so, in your case, please remove the "proxy_route" param. bogdan Brinker, Oliver wrote: >Hi Bogdan, > >please find attached my ser configuration. I'm using the cvs head >version downloaded two days ago (22.06.04). Should be actual enough ;) >Thanks a lot. > >Regards, >Oliver > ># ># $Id: ser.cfg,v 1.24 2003/11/11 15:32:36 andrei Exp $ ># ># simple quick-start config script ># > ># ----------- global configuration parameters ------------------------ > ># log into /var/log/messages >debug=9 # debug level (cmd line: -dddddddddd) >fork=yes >log_stderror=no # (cmd line: -E) > >check_via=no # (cmd. line: -v) >dns=no # (cmd. line: -r) >rev_dns=no # (cmd. line: -R) >#port=5060 >#children=4 >fifo="/tmp/ser_fifo" > ># Additional Alias >alias="sip.et123lab.de" > ># ------------------ module loading ---------------------------------- > ># Uncomment this if you want to use SQL database >loadmodule "/usr/local/lib/ser/modules/mysql.so" > >loadmodule "/usr/local/lib/ser/modules/sl.so" >loadmodule "/usr/local/lib/ser/modules/tm.so" >loadmodule "/usr/local/lib/ser/modules/rr.so" >loadmodule "/usr/local/lib/ser/modules/maxfwd.so" >loadmodule "/usr/local/lib/ser/modules/usrloc.so" >loadmodule "/usr/local/lib/ser/modules/registrar.so" >loadmodule "/usr/local/lib/ser/modules/textops.so" > ># CPL-C module >loadmodule "/usr/local/lib/ser/modules/cpl-c.so" > ># Uncomment this if you want digest authentication ># mysql.so must be loaded ! >loadmodule "/usr/local/lib/ser/modules/auth.so" >loadmodule "/usr/local/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) > ># -- cpl-c params -- >modparam("cpl-c","cpl_db","mysql://xxxx:xxxx@localhost/ser") >modparam("cpl-c","cpl_table","cpl") >modparam("cpl-c","cpl_dtd_file","/usr/local/etc/ser/cpl-06.dtd") >modparam("cpl-c","log_dir","/var/log/ser/cpl") >modparam("cpl-c","proxy_recurse",2) >modparam("cpl-c","proxy_route",1) >modparam("cpl-c","lookup_domain","location") > ># -- timer settings -- >modparam("tm","noisy_ctimer",1) # this will force timeout >modparam("tm","fr_inv_timer",30) # sets the timeout for INVITE to 30 >sec (default is 120) > ># ------------------------- 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 > 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 (!uri==myself) { > # mark routing logic in request > append_hf("P-hint: outbound\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 (method=="REGISTER") { > > # Uncomment this if you want to use digest authentication > if (!www_authorize("sip.et123lab.de", "subscriber")) { > www_challenge("sip.et123lab.de", "0"); > break; > }; > > # handle REGISTER messages containing a CPL script > cpl_process_register(); > > save("location"); > break; > }; > > # process CPL script > log("cpl: start script processing now"); > cpl_run_script("incoming","FORCE_STATEFUL"); > log("cpl: script processing has been finished"); > > lookup("aliases"); > if (!uri==myself) { > append_hf("P-hint: outbound alias\r\n"); > route(1); > break; > }; > > # native SIP destinations are handled using our USRLOC DB > if (!lookup("location")) { > sl_send_reply("404", "Not Found"); > break; > }; > }; > append_hf("P-hint: usrloc applied\r\n"); > route(1); >} > >route[1] >{ > # send it out now; use stateful forwarding as it works reliably > # even for UDP2TCP > if (!t_relay()) { > sl_reply_error(); > }; >} > > > > >Bogdan-Andrei IANCU [mailto:iancu@fokus.fraunhofer.de] wrote > >Hi Oliver, > >please send me your ser.cfg - it will help me to trace the problem. >Also >be sure you are using the latest cvs head version - there were some >updates 1 or 2 weeks ago. > >Regards, >Bogdan > >Brinker, Oliver wrote: > > > >>Hi Bogdan, >> >>I solved the problem with SER startup. The reason was that I download >>the CVS head onto my notebook and copy it via ftp to the linux server. >>After downloading CVS head directly onto the linux server, compiling >>and installing it SER starts up without any error message. >> >>But I have still the problem with call forwarding on busy or no >>answer. >>Inserting log information into my CPL script I can reproduce that SER >>is never processing the <busy> or <noanswer> tag and the following >>tags. I try out the example script from the current IETF CPL draft for >>Call Forward Busy/No Answer in the following scenario: >> >>6131 forwards calls to 613 if busy -> 6131 has an active session with >>614 -> 612 calls 6131 -> 6131 is busy and SER should invite 613 >> >>After uploading the CPL script for 6131 the caller 614 cannot reach >>6131 and the syslog represents the attached error message. >> >>Can you identify any mistake I've done in my configuration? Many >>thanks. >> >>Best Regards, >> >>Oliver >> >> >> >> > > >

19 years, 11 months

[Serusers] Log out of serweb

by Gala, Dipen

Hey guys when I log in the serweb there is no button where I can click to log out. And since I don't click log out my entry from database does not get deleted and therefore I always would be online. Folks with serweb -- do u have the log out button? If yes then how can get mine. Which file deals with it. Dipen K Gala Fidelity Investments System Company - Telecom Phone: (617) 563-2729 Email: Dipen.Gala(a)FMR.com

19 years, 11 months

Re: [Serusers] CPL-C and call forward on busy or no answer

by Brinker, Oliver

Hi Bogdan, please find attached my ser configuration. I'm using the cvs head version downloaded two days ago (22.06.04). Should be actual enough ;) Thanks a lot. Regards, Oliver # # $Id: ser.cfg,v 1.24 2003/11/11 15:32:36 andrei Exp $ # # simple quick-start config script # # ----------- global configuration parameters ------------------------ # log into /var/log/messages debug=9 # debug level (cmd line: -dddddddddd) fork=yes log_stderror=no # (cmd line: -E) check_via=no # (cmd. line: -v) dns=no # (cmd. line: -r) rev_dns=no # (cmd. line: -R) #port=5060 #children=4 fifo="/tmp/ser_fifo" # Additional Alias alias="sip.et123lab.de" # ------------------ module loading ---------------------------------- # Uncomment this if you want to use SQL database loadmodule "/usr/local/lib/ser/modules/mysql.so" loadmodule "/usr/local/lib/ser/modules/sl.so" loadmodule "/usr/local/lib/ser/modules/tm.so" loadmodule "/usr/local/lib/ser/modules/rr.so" loadmodule "/usr/local/lib/ser/modules/maxfwd.so" loadmodule "/usr/local/lib/ser/modules/usrloc.so" loadmodule "/usr/local/lib/ser/modules/registrar.so" loadmodule "/usr/local/lib/ser/modules/textops.so" # CPL-C module loadmodule "/usr/local/lib/ser/modules/cpl-c.so" # Uncomment this if you want digest authentication # mysql.so must be loaded ! loadmodule "/usr/local/lib/ser/modules/auth.so" loadmodule "/usr/local/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) # -- cpl-c params -- modparam("cpl-c","cpl_db","mysql://xxxx:xxxx@localhost/ser") modparam("cpl-c","cpl_table","cpl") modparam("cpl-c","cpl_dtd_file","/usr/local/etc/ser/cpl-06.dtd") modparam("cpl-c","log_dir","/var/log/ser/cpl") modparam("cpl-c","proxy_recurse",2) modparam("cpl-c","proxy_route",1) modparam("cpl-c","lookup_domain","location") # -- timer settings -- modparam("tm","noisy_ctimer",1) # this will force timeout modparam("tm","fr_inv_timer",30) # sets the timeout for INVITE to 30 sec (default is 120) # ------------------------- 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 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 (!uri==myself) { # mark routing logic in request append_hf("P-hint: outbound\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 (method=="REGISTER") { # Uncomment this if you want to use digest authentication if (!www_authorize("sip.et123lab.de", "subscriber")) { www_challenge("sip.et123lab.de", "0"); break; }; # handle REGISTER messages containing a CPL script cpl_process_register(); save("location"); break; }; # process CPL script log("cpl: start script processing now"); cpl_run_script("incoming","FORCE_STATEFUL"); log("cpl: script processing has been finished"); lookup("aliases"); if (!uri==myself) { append_hf("P-hint: outbound alias\r\n"); route(1); break; }; # native SIP destinations are handled using our USRLOC DB if (!lookup("location")) { sl_send_reply("404", "Not Found"); break; }; }; append_hf("P-hint: usrloc applied\r\n"); route(1); } route[1] { # send it out now; use stateful forwarding as it works reliably # even for UDP2TCP if (!t_relay()) { sl_reply_error(); }; } Bogdan-Andrei IANCU [mailto:iancu@fokus.fraunhofer.de] wrote Hi Oliver, please send me your ser.cfg - it will help me to trace the problem. Also be sure you are using the latest cvs head version - there were some updates 1 or 2 weeks ago. Regards, Bogdan Brinker, Oliver wrote: >Hi Bogdan, > >I solved the problem with SER startup. The reason was that I download >the CVS head onto my notebook and copy it via ftp to the linux server. >After downloading CVS head directly onto the linux server, compiling >and installing it SER starts up without any error message. > >But I have still the problem with call forwarding on busy or no answer. >Inserting log information into my CPL script I can reproduce that SER >is never processing the <busy> or <noanswer> tag and the following >tags. I try out the example script from the current IETF CPL draft for >Call Forward Busy/No Answer in the following scenario: > >6131 forwards calls to 613 if busy -> 6131 has an active session with >614 -> 612 calls 6131 -> 6131 is busy and SER should invite 613 > >After uploading the CPL script for 6131 the caller 614 cannot reach >6131 and the syslog represents the attached error message. > >Can you identify any mistake I've done in my configuration? Many >thanks. > >Best Regards, > >Oliver > >

19 years, 11 months

[Serusers] Calling thru serweb

by Gala, Dipen

Hey I am playing a simple game here.i want two online users logged in to the ser through serweb. When I add the opposite person in the phone book I don't see them online, they appear offline always. I have mysql running with ser and serweb. I have not used radius server. So my question is how can I make calls between two users online through serweb? \ If any one can share is config file for ser it will be of great help. thanks Dipen K Gala Fidelity Investments System Company - Telecom Phone: (617) 563-2729 Email: Dipen.Gala(a)FMR.com

19 years, 11 months

RE: [Serusers] SERWEB-User Login Problems

by Freddy Parra

Hi, You need to make sure that the following parameters in config.php are set correctly. For example $this->db_host="localhost"; //database host $this->db_name="ser"; //database name $this->db_user="ser"; //database conection user $this->db_pass="heslo"; //database conection password /* your domain name */ $this->realm="xxx.xxx.xxx.xxx"; $this->domainname="xxx.xxx.xxx.xxx"; $this->default_domain="xxx.xxx.xxx.xx"; Then you need to make sure that your ser configuration file is set correctly for mysql authentication. Here is a good read on this topic: http://iptel.org/ser/doc/ser-howto/ser-Howto.html Regards, Freddy -----Original Message----- From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org]On Behalf Of kevin(a)fullcirclenetworks.net Sent: Wednesday, June 23, 2004 9:24 PM To: serusers(a)lists.iptel.org Subject: RE: [Serusers] SERWEB-User Login Problems I am still having problems with the User Login after fixing the domain names. Anyone have another suggestion? Thanks > -------- Original Message -------- > Subject: Re: [Serusers] SERWEB-User Login Problems > From: "Bill" <admin(a)vci.net> > Date: Wed, June 23, 2004 7:35 am > To: kevin(a)fullcirclenetworks.net > > I had a similar problem where the URL I was using to access SERWEB > wasn't the same as the domain name I was using. I was going to > http://192.168.1.63 but the domain name was something else. So when > someone > would login SERWEB was looking for the domain name of 192.168.1.63. I > was > able to see this by turning on the logging in /etc/my.conf and watching > the > SQL statements in /var/log/mysql.log > > Bill Dunn > > > > ----- Original Message ----- > From: kevin(a)fullcirclenetworks.net > To: serusers(a)lists.iptel.org > Sent: Wednesday, June 23, 2004 9:32 AM > Subject: [Serusers] SERWEB-User Login Problems > > > I have successfully installed the latest SERweb and am able to login > under > admin. The problem I am having now > is that none of my users can login and see their account. I have > checked > all my configurations in php,mysql > and apache but don't see any obvious errors. I have a password for > the > users and they are using the correct > one. I check the error logs and don't see any messages. Has anyone > had a > similar problem? > > _______________________________________________ > 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, 11 months

Re: [Serusers] CPL-C and call forward on busy or no answer

by Brinker, Oliver

Hi Bogdan, I solved the problem with SER startup. The reason was that I download the CVS head onto my notebook and copy it via ftp to the linux server. After downloading CVS head directly onto the linux server, compiling and installing it SER starts up without any error message. But I have still the problem with call forwarding on busy or no answer. Inserting log information into my CPL script I can reproduce that SER is never processing the <busy> or <noanswer> tag and the following tags. I try out the example script from the current IETF CPL draft for Call Forward Busy/No Answer in the following scenario: 6131 forwards calls to 613 if busy -> 6131 has an active session with 614 -> 612 calls 6131 -> 6131 is busy and SER should invite 613 After uploading the CPL script for 6131 the caller 614 cannot reach 6131 and the syslog represents the attached error message. Can you identify any mistake I've done in my configuration? Many thanks. Best Regards, Oliver Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: cpl: start script processing now Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG:cpl-c:get_dest_user: tring to get user from new_uri Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG:cpl-c:get_dest_user: tring to get user from R_uri Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG:get_user_script: fetching script for user <6131(a)10.0.60.2> Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG:get_user_script: we got the script len=90 Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG:cpl_run_script: processing CPL node Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG:cpl_run_script: processing location node Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG:cpl_run_script: processing proxy node Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: parse_headers: flags=16777216 Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: parse_headers: flags=4194304 Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: parse_headers: flags=33554432 Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: parse_headers: flags=2097152 Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: parse_headers: flags=8388608 Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG: t_newtran: msg id=2 , global msg id=0 , T on entrance=0xffffffff Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: parse_headers: flags=-1 Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: parse_headers: flags=60 Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: t_lookup_request: start searching: hash=57364, isACK=0 Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG: proceeding to pre-RFC3261 transaction matching Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG: t_lookup_request: no transaction found Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG: t_check: msg id=2 global id=2 T start=0x402ef820 Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG: t_check: T alredy found! Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG:cpl_c:cpl_proxy_to_loc_set: rewriting Request-URI with <sip:6131@10.0.60.2> Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG: t_newtran: msg id=2 , global msg id=2 , T on entrance=0x402ef820 Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: ERROR: t_newtran: transaction already in process 0x402ef820 Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: parse_headers: flags=-1 Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: check_via_address(10.0.61.4, 10.0.61.4, 0) Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: ERROR: sl_reply_error used: I'm terribly sorry, server error occured (1/SL) Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG: t_check: msg id=2 global id=2 T start=0x402ef820 Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG: t_check: T alredy found! Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG: mk_proxy: doing DNS lookup... Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: check_via_address(10.0.61.4, 10.0.61.4, 0) Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2088]: SIP Request: Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2088]: method: <INVITE> Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2088]: uri: <sip:6131@10.0.60.2> Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2088]: version: <SIP/2.0> Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2088]: parse_headers: flags=1 Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2088]: Found param type 232, <branch> = <z9hG4bK410e.de7825a6.0>; state=16 Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2088]: end of header reached, state=5 Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2088]: parse_headers: Via found, flags=1 Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2088]: parse_headers: this is the first via Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2088]: After parse_msg... Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2088]: preparing to run routing scripts... Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2088]: DEBUG : is_maxfwd_present: max_forward header already found! Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2088]: DEBUG: is_maxfwd_present: value = 10 Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2088]: parse_headers: flags=8 Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2088]: end of header reached, state=5 sipproxy1:/var/log # less messages | grep cpl Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: cpl: start script processing now Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG:cpl-c:get_dest_user: tring to get user from new_uri Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG:cpl-c:get_dest_user: tring to get user from R_uri Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG:cpl_run_script: processing CPL node Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG:cpl_run_script: processing location node Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG:cpl_run_script: processing proxy node Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG:cpl_c:cpl_proxy_to_loc_set: rewriting Request-URI with <sip:6131@10.0.60.2> Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2088]: cpl: start script processing now Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2088]: DEBUG:cpl-c:get_dest_user: tring to get user from new_uri Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2088]: DEBUG:cpl-c:get_dest_user: tring to get user from R_uri Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2088]: DEBUG:cpl_run_script: processing CPL node Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2088]: DEBUG:cpl_run_script: processing location node Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2088]: DEBUG:cpl_run_script: processing proxy node Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2088]: DEBUG:cpl_c:cpl_proxy_to_loc_set: rewriting Request-URI with <sip:6131@10.0.60.2> Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2094]: DEBUG:cpl-c:negativ_reply: ------------------------------> ---------------------------------> negativ reply receive Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2094]: DEBUG:cpl-c:failed_reply:final_reply: got a final 500 Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2094]: DEBUG:cpl-c:final_reply: code=500 --------------> --------------------------> final reply received Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2100]: cpl: start script processing now Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2100]: DEBUG:cpl-c:get_dest_user: tring to get user from new_uri Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2100]: DEBUG:cpl-c:get_dest_user: tring to get user from R_uri Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2100]: DEBUG:cpl_run_script: processing CPL node Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2100]: DEBUG:cpl_run_script: processing location node Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2100]: DEBUG:cpl_run_script: processing proxy node Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2100]: DEBUG:cpl_c:cpl_proxy_to_loc_set: rewriting Request-URI with <sip:6131@10.0.60.2> Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2097]: DEBUG:cpl-c:negativ_reply: ------------------------------> ---------------------------------> negativ reply receive Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2097]: DEBUG:cpl-c:failed_reply:final_reply: got a final 500 Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2097]: DEBUG:cpl-c:final_reply: code=500 --------------> --------------------------> final reply received Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2091]: cpl: start script processing now Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2091]: DEBUG:cpl-c:get_dest_user: tring to get user from new_uri Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2091]: DEBUG:cpl-c:get_dest_user: tring to get user from R_uri Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2091]: DEBUG:cpl_run_script: processing CPL node Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2091]: DEBUG:cpl_run_script: processing location node Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2091]: DEBUG:cpl_run_script: processing proxy node Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2091]: DEBUG:cpl_c:cpl_proxy_to_loc_set: rewriting Request-URI with <sip:6131@10.0.60.2> Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG:cpl_c:cpl_run_script: done for the moment; waiting after signaling! Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG:cpl-c:negativ_reply: ------------------------------> ---------------------------------> negativ reply receive Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG:cpl-c:failed_reply:final_reply: got a final 500 Jun 24 11:36:22 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG:cpl-c:final_reply: code=500 --------------> --------------------------> final reply received Jun 24 11:36:23 sipproxy1 /usr/local/sbin/ser[2088]: DEBUG:cpl_c:cpl_run_script: done for the moment; waiting after signaling! Jun 24 11:36:23 sipproxy1 /usr/local/sbin/ser[2078]: cpl: start script processing now Jun 24 11:36:23 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG:cpl-c:get_dest_user: tring to get user from new_uri Jun 24 11:36:23 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG:cpl-c:get_dest_user: tring to get user from R_uri Jun 24 11:36:23 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG:cpl_run_script: processing CPL node Jun 24 11:36:23 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG:cpl_run_script: processing location node Jun 24 11:36:23 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG:cpl_run_script: processing proxy node Jun 24 11:36:23 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG:cpl_c:cpl_proxy_to_loc_set: rewriting Request-URI with <sip:6131@10.0.60.2> Jun 24 11:36:23 sipproxy1 /usr/local/sbin/ser[2100]: DEBUG:cpl_c:cpl_run_script: done for the moment; waiting after signaling! Jun 24 11:36:23 sipproxy1 /usr/local/sbin/ser[2085]: cpl: start script processing now Jun 24 11:36:23 sipproxy1 /usr/local/sbin/ser[2085]: DEBUG:cpl-c:get_dest_user: tring to get user from new_uri Jun 24 11:36:23 sipproxy1 /usr/local/sbin/ser[2085]: DEBUG:cpl-c:get_dest_user: tring to get user from R_uri Jun 24 11:36:23 sipproxy1 /usr/local/sbin/ser[2085]: DEBUG:cpl_run_script: processing CPL node Jun 24 11:36:23 sipproxy1 /usr/local/sbin/ser[2085]: DEBUG:cpl_run_script: processing location node Jun 24 11:36:23 sipproxy1 /usr/local/sbin/ser[2085]: DEBUG:cpl_run_script: processing proxy node Jun 24 11:36:23 sipproxy1 /usr/local/sbin/ser[2085]: ERROR:cpl-c:run_proxy: processed INVITE is a retransmission! Jun 24 11:36:23 sipproxy1 /usr/local/sbin/ser[2085]: DEBUG:cpl_c:cpl_run_script: script interpretation done! Jun 24 11:36:23 sipproxy1 /usr/local/sbin/ser[2100]: DEBUG:cpl-c:negativ_reply: ------------------------------> ---------------------------------> negativ reply receive Jun 24 11:36:23 sipproxy1 /usr/local/sbin/ser[2100]: DEBUG:cpl-c:failed_reply:final_reply: got a final 500 Jun 24 11:36:23 sipproxy1 /usr/local/sbin/ser[2100]: DEBUG:cpl-c:final_reply: code=500 --------------> --------------------------> final reply received Jun 24 11:36:23 sipproxy1 /usr/local/sbin/ser[2078]: DEBUG:cpl_c:cpl_run_script: done for the moment; waiting after signaling! Bogdan-Andrei IANCU [mailto:iancu@fokus.fraunhofer.de] wrote Hi Oliver, There is nothing wrong with SER and you should use the CVS head version. The problem is in your configuration file - looks like you have some strange string (missing " ?) on the first line. Bogdan Brinker, Oliver wrote: >Hi Bogdan, > >I've download everything from CVS head, compile it and try to run the >SER with the basic config file (no database, authentication and cpl support), but I get the following error message in my syslog > >Jun 8 15:46:44 sipproxy1 ser: parse error (1,1-2): parse error Jun 8 >15:46:44 sipproxy1 ser: ERROR: cfg. parser: unexpected EOF in unclosed >string > >... and on the command line together with the whole ser.cfg content > >ERROR: bad config file (1 errors) > >I leave the ser.cfg unchanged because I want to try out the new >installation first. After getting these error message I check other >versions from CVS (v_0_8_13-dev-29, v_0_8_13dev-t16 ...) but the >problem is the same as before. Compilation ist no problem. Which CVS >version is the best for me to download? Many thanks for your help. > >Regards, >Oliver > >

19 years, 11 months

RE: [Serusers] Problem in MySql Setup::

by Freddy Parra

Hi, When executing ser-mysql.sh under the directory its located, in this case /usr/local/sbin, try executing it as ./ser-msyql.sh since ./ might not be set in your path. Then make sure mysql server is started, you can usually check this by executing ps ax | grep mysql. Or simply starting the service up by typing service mysql start. Regards, Freddy -----Original Message----- From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org]On Behalf Of GR S Sent: Thursday, June 24, 2004 7:08 AM To: Vanita Jain Cc: serusers(a)lists.iptel.org Subject: Re: [Serusers] Problem in MySql Setup:: Hello, You need to install mysql-client in your system, I think there are some other rpms too you need to install. Do a google search on the iptel site to find out more about your problem. google for 'mysqlclient.so site:iptel.org'. This should help... Regards, --- Vanita Jain <vanita(a)vigyana.com> wrote: > Hi, > > When try to install the package following err comes:: > > [root@localhost /]# rpm -i ser-mysql-0.8.12-0.i386.rpm > error: Failed dependencies: > libmysqlclient.so.10 is needed by ser-mysql-0.8.12-0 > > Also when I try to execute the script ser-mysql.sh ":No such file or > directory" error comes. > > What to do??? > > Thanks - > Vanita Jain ===== Girish Gopinath <gr_sh2003(a)yahoo.com> __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

19 years, 11 months

← Newer
1
...
6
7
8
9
10
11
12
...
39
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 June 2004