[serusers] pa module

Jesús M. Movilla jmms03 at tid.es
Wed Jun 22 11:10:32 CEST 2005


Hi Michael

I will try to answer what I learned those days in SER, but do not expect too
much!! :-)

> hi
>
> i'm wroting you cause i saw that you wrote a lot about pa module and you
> finally succeed to install it.
>
> congratulations!
>
> i 'm still trying and only one person answered me...
>
> please can you help me?
>
> my problems and questions are :
>
> 1. did you find more docs about pa module cause the README is not very
> long.?

No, I just reviewed those docs. However I should tell you that I have tried
to male the pa module work with
several "SER releases" and I just got it with the following cvs version:
ser_0.10.99+cvs20050519


> 2. how install it? what the difference between handle_subscription
> ("registrar") and publish ?

I took the source code and I compiled it including tha pa modules (Makefile
has an exclude_modules variables with those modules
that are not compiled, removed the pa module from that list).

I do not know the "difference in code"  between
handle_subscripton("regstrar") and handle_publish(""). I just used
handle_subscription for the SUBSCRIBE method and handle_publish() for the
PUBLISH method. I did not have time enough to go through the code.

> 3. how i have to use the pa module and mysql ? i saw in one of your
message
> your ser.cfg but i don't know where you found all the informations to
write
> the lines about pa modules...

I have use pa module and mysql without no problem. I thind you shoud exceute
first the script pa.sql in order to create the tables that pa module will
use.
I found the information about pa modules from this list... Mainly, if I well
remember from e-mails posted in that list. In that sense Jamey´s e-mails has
been of very good help.

> 4. pa module works with all the softphone (i'm using a softphone from Xten
> (eyebeam))? how do they know to communicate with this module of SER? how
can
> i do test?

I do not know if that works with all softphone. In fact, what I include in
my previous mails were SIP messages that I sent to SER. I could not see in
any SIP client that one of my contacts change
the presence state from connected to busy, for example. From Jamey´s answers
It seems that pa module just support the <status> <basic> tag from pidf but
not any other. So SER server only gives the "connecting information" i.e if
yoru contacts are connected (<status>OPEN<status>) or disconnected
(<status>CLOSED<status>).

I hope my e-mails has been of any use to you.

Thanks.

    Jesús

>
> please help me it's very important
>
> thanks a lot
>
> Michael
>
>


I agin include the ser.cfg

Good luck!!


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

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

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

debug=3         # debug level (cmd line: -dddddddddd)
#fork=yes
#log_stderror=no # (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=yes
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
fifo_db_url="mysql://ser:heslo@localhost/ser"
#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)

#Connection 'mysql://ser:heslo@localhost/ser' not found in pool
# ------------------ 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"
loadmodule "/usr/local/lib/ser/modules/pa.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)
modparam("usrloc", "db_url", "mysql://ser:heslo@localhost/ser")

# -- 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")
#aumodparam("auth_db", "db_url", "mysql://ser:heslo@localhost/ser")

# -- rr params --
# add value to ;lr param to make some broken UAs happy
modparam("rr", "enable_full_lr", 1)

# --pa -- params
modparam("pa", "db_url", "mysql://ser:heslo@localhost/ser")
# -------------------------  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) {
 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;
  };

  if (method=="SUBSCRIBE") {

   log(1,"Subscribe\n");
   if (t_newtran()) {
    log(1,"Register\n");
    handle_subscription("registrar");
   };
   break;
  };


  if (method=="PUBLISH") {

   log(1,"Publish\n");
   if (!t_newtran()) {
    log(1,"newtran error\n");
    sl_reply_error();
   };
   handle_publish("registrar");
   log(1,"publish handled\n");
   break;
  };

  lookup("aliases");
  #if (!uri==myself) {
  if (!uri=~"hi.inet") {
   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();
 };
}




More information about the sr-users mailing list