[Serusers] SER with pa module including publish (ERROR)

[Jesús M. Movilla]

Hi Jamey,

Thank you for your quick answer. I do not know where to look the startingup
process logs. I looked into the /var/logs/message and I just see:

ser: parse error (1,1-2):syntax error

Before the startup I ran the script modules/pa/pa.sql script to create the
tables for pa module.

Next, I include the ser.cfg that I have in case it helps.


#
# $Id: ser.cfg,v 1.27 2005/03/10 14:16:25 andrei Exp $
#
# simple quick-start config script
#

# ----------- global configuration parameters ------------------------

debug=7         # debug level (cmd line: -dddddddddd)
fork=yes
log_stderror=yes # (cmd line: -E)
#memlog=5 # memory debug log level
#log_facility=LOG_LOCAL0 # sets the facility used for logging (see
syslog(3))

/* 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"
#user=ser
#group=ser
#fifo_user=ser # owner of the ser fifo
#fifo_group=ser
#fifo_mode=0660 # fifo's permissions
#disable_core=yes #disables core dumping
#open_fd_limit=1024 # sets the open file descriptors limit
#mhomed=yes  # usefull for multihomed hosts, small performance penalty
#disable_tcp=yes
#tcp_accept_aliases=yes # accepts the tcp alias via option (see NEWS)

#

# ------------------ 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/pa.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"

# 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)

# -- pa params --
#
modparam("pa", "default_expires", 3600) #Set default_expires parameter
modparam("pa", "default_priority_percentage", 50) #Set
default_priority_percentage parameter
modparam("pa", "db_url", "mysql:ser:heslo at localhost/ser") #
modparam("pa", "pa_domain", "hi.inet") #


# -------------------------  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=~"hi.inet" {
  # 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=~"hi.inet") {

  if (method=="REGISTER") {

# Uncomment this if you want to use digest authentication
   if (!www_authorize("hi.inet", "subscriber")) {
    www_challenge("hi.inet", "0");
    break;
   };

   save("location");
   break;
  };

  lookup("aliases");
  if (!uri=~"hi.inet") {
   append_hf("P-hint: outbound alias\r\n");
   route(1);
   break;
  };

  if (method=="PUBLISH") {
       if (!t_newtran()) {
           log(1, "newtran error\n");
           sl_reply_error();
       };
       handle_publish("registrar");
       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();
 };
}


******************************************

Thnak you very much in advance

Jesús

----- Original Message ----- 
From: "Jamey Hicks" <jamey.hicks at hp.com>
To: "Jesús M. Movilla" <jmms03 at tid.es>
Cc: <serusers at lists.iptel.org>
Sent: Thursday, June 09, 2005 2:48 PM
Subject: Re: [Serusers] SER with pa module including publish (ERROR)


> Jesús M. Movilla wrote:
>
> > Hi to all,
> >
> >     I would like to know the way to install SER with PUBLISH support
> > in the pa module. I tried to compile the pa module from CVS version
> > and inserted within the 0.8.14 version but it didn´t work:I
> > obtained the following error when starting up:
> >
> > /l/
>
> The PA module has dependences on the core of SER, so it is unlikely to
> work with a different version of SER.
>
> > I also tried compiling the whole CVS version (0.10.99) but when I
> > start up I obtain the ERROR bad config file (1 errors). I also
> > tried with the config file ser.cfg from the 0.8.14 version but I
> > obtained the same error. So, could someone tell me how to proceed in
> > order to have a SER server with a pa module implementing REGISTER,
> > SUSBSCRIBE AND PUBLISH.
> >
>
> Please look at the messages to see which lines of ser.cfg it was unhappy
> with.  If that does not help, please post the message and the offending
> lines of the config file here so we can help.
>
> The README in modules/pa does document much of the configuration
> process.  The SQL script modules/pa/pa.sql needs to be run in your MySQL
> database to add the tables that PA uses.
>
> Hope this helps,
> Jamey
>