[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sems
Subject:    Fwd: [Sems] Re: [Semsdev] Sems + Ser mini-HOWTO - working ser.cfg
From:       aydin () verscom ! com (Aydin Pirinccioglu)
Date:       2004-11-28 0:40:03
Message-ID: 954401c4d4da$63113e50$0301a8c0 () D8100
[Download RAW message or body]

Hi Stefan,

Sorry, I've been away for a few days.  Got it all working, thanks much.

Now time to start playing with it :-)

Cheers,

Aydin



----- Original Message ----- 
From: "Stefan Sayer" <sayer@cs.tu-berlin.de>
To: "Aydin Pirinccioglu" <aydin@verscom.com>
Cc: <sems@iptel.org>
Sent: Tuesday, November 23, 2004 10:29 AM
Subject: Re: Fwd: [Sems] Re: [Semsdev] Sems + Ser mini-HOWTO - working
ser.cfg ??


> Hello Aydin,
>
> Aydin Pirinccioglu wrote:
>
> > Hi Stefan,
> >
> > First off, thanks for all your help, I think I'm making progress, sort
of,
> > except for two items:
> >
> > 1. How do I configure sems to use fifo_db ?  I was not able to find
anything
> > about this parameter for Sems and sems.cfg.
> sems uses fifo_db if it does not find the email address in an INVITE.
> you don't have to configure anything on sems side.
>
>
> >
> > 2. If I go with 1) below, ser complains about a syntax error at the
> > load_avp("ruri", "email", 0); section.  Still can't figure out what it
> > doesn't like about that syntax, it should be right.  Anyways, if I can
get
> > fifo_db_url working, then I won't need this (not yet anyways :-)
> did you load avp_db ? Have a look at the avp_db module docs, but now I
> am not sure about this any more, either. Anyway, you don't need it as
> sems can use fifo_db.
>
> >
> > 3. Outside of these little hang-ups, your ser.cfg is causing my ser to
core
> > dump on the first incoming call and I'm trying to figure out why.  I had
> > followed the same instructions to make both ser and sems.  If I use a
simple
> > nathelper/rtpproxy type ser.cfg all is fine and calls go through, I
switch
> > over to the sems ser.cfg and like clockwork it core dumps.
> Please update sip_router/modules/tm/tm_fifo.c from cvs, I think that bug
> was fixed yesterday night... (if not, do the following: add modparam(
> "tm", "tw_append", "dummy_append:hdr[Content-Length]") somewhere at the
> beginning of ser.cfg, and then to t_write_req (or t_write_unix):
>   t_write_unix("/tmp/am_sock","voicemail/dummy_append")){ or
> t_write_unix("/tmp/am_sock","bye/dummy_append")){
> )
>
>
> Stefan
>
> >
> >
> > Thanks again,
> >
> > Aydin
> >
> >
> >
>


[prev in list] [next in list] [prev in thread] [next in thread]