[Serusers] CPL-C and call forward on busy or no answer
Brinker, Oliver
Oliver.Brinker at t-systems.com
Tue Jun 8 17:05:31 CEST 2004
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
Bogdan-Andrei IANCU [mailto:iancu at fokus.fraunhofer.de] wrote
Hi Oliver,
First there is a small problem in your ser cfg. To enable CPL lookup
node you have to set the cpl param "lookup_domain" ( it missing was
reported at start up by "cpl_init: no lookup_domain given -> disable
lookup node").
Just add to you script the following line:
modparam("cpl-c","lookup_domain","location")
Second, there was a small error in lookup node reported by Richard. So,
please update you cpl-c module before retrying. Also, it will be more
easier for you to debug your CPL scripts by inserting some log nodes
to see the if lookup succeed of not, or if proxy was ok, etc.
Regards,
Bogdan
Brinker, Oliver wrote:
>Hi Bogdan,
>
>please find attached my ser.cfg and the CPL script for call forwarding
>on no answer. Could it be a failure in my SER configuration?
>
>Many thanks,
>Oliver
>
>-----------------------------------------------------------------------
>---------------------
>
>#
># $Id: ser.cfg,v 1.24 2003/11/11 15:32:36 andrei Exp $
>#
># simple quick-start config script
>#
>
># ----------- global configuration parameters ------------------------
>
>debug=9 # debug level (cmd line: -dddddddddd)
>fork=yes
>log_stderror=no # (cmd line: -E)
>
># Uncomment these lines to enter debugging mode
>#fork=no
>#log_stderror=yes
>
>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 Aliases
>alias="t-systems.com"
>
># ------------------ 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/cpl-c.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"
>
># 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 module --
>modparam("cpl-c","cpl_db","mysql://ser:???@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)
>
># ------------------------- 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()) {
> t_relay();
> break;
> };
>
> lookup("aliases");
> setflag(1);
>
> # 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("t-systems.com", "subscriber")) {
> www_challenge("t-systems.com", "0");
> break;
> };
>
> # handle REGISTER messages with CPL script
> cpl_process_register();
>
> save("location");
> break;
> };
>
> # process INVITE
> if (method=="INVITE") {
> # cpl interpreter requires a pre-created transaction for the processed INVITE
> if (!t_newtran()) {
> # it's a retransmission
> break;
> };
> if (!cpl_run_script("incoming")) {
> # script execution failed
> t_reply("500", "CPL script execution failed");
> };
>
> # we get here only if the CPL interpreter decided that server
> # should follow it default behavior
>
> # mark that there is already a created transaction for current INVITE
> setflag(3);
> };
>
> # native SIP destinations are handled using our USRLOC DB
> if (!lookup("location")) {
> sl_send_reply("404", "Not Found");
> break;
> };
> };
> # forward current uri now
> if (!isflagset(3)) {
> # build a new fresh transaction and forward
> if (!t_relay()) {
> sl_reply_error();
> };
> }
> else {
> # transaction exists -> do just forward
> if (!t_forward_nonack_uri()) {
> sl_reply_error();
> };
> };
>}
>
>-----------------------------------------------------------------------
>---------------------
>
><?xml version="1.0" encoding="UTF-8"?>
>
><!DOCTYPE cpl PUBLIC '-//IETF//DTD RFCxxxx CPL 1.0//EN' 'cpl.dtd'>
>
><cpl>
> <incoming>
> <lookup source="registration" clear="yes">
> <success>
> <proxy timeout="5">
> <noanswer>
> <location url="sip:613 at t-systems.com" clear="yes">
> <proxy />
> </location>
> </noanswer>
> </proxy>
> </success>
> </lookup>
> </incoming>
>
>-----------------------------------------------------------------------
>---------------------
>
>
>Bogdan-Andrei IANCU wrote
>
>Hi Oliver,
>
>can you send me your CPL script - it will help me to understand your
>problem.
>
>Thanks,
>Bogdan
>
>Brinker, Oliver wrote:
>
>
>
>>Hi!
>>
>>I've successfully tested a handful CPL based services on SER 0.8.12
>>and
>>most of them are working correctly. Only call forward on busy and/or no
>>answer doesn't work. Enabling logging (debug=9) I get no error messages
>>in the log file, but a NOTICE message that no lookup domain is given
>>("cpl_init: no lookup_domain given -> disable lookup node"). It seems
>>to me that all services with blocking (i.e. call screening, time of day
>>screening) and direct redirection to another host (i.e. call forward
>>unconditional, time of day routing) are working correctly. When SER
>>first tries to reach a client before redirecting to another host (i.e.
>>call forward busy or no answer) it seems that the proxy server doesn't
>>returns to CPL script processing.
>>
>>Does anybody know a reason for this behaviour or has a correct working
>>CPL implementation for call forward on busy or no answer?
>>
>>many thanks,
>>Oliver
>>
>>_______________________________________________
>>Serusers mailing list
>>serusers at lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
>>
>>
>>
>>
>>
>
>_______________________________________________
>Serusers mailing list
>serusers at lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
>
>
>
More information about the sr-users
mailing list