[Serusers] Need Routing Help

[Wasik, Paul]

Jan,

My SER SIP server works fine with the default config script. As soon as I
add some simple static routing such as:

if (uri=~"^sip:9[0-9]*@rtcsol.local) {
        forward( 159.63.73.165, 5060 );

to the script and restart ser, my log looks like the attached. There is a
ser process running but it is not normal and no network SIP ports ie 5060
are opened.

The command line returns:

[root at FFDCTSERSIP ser]# /etc/rc.d/init.d/ser stop
Stopping ser:                                              [  OK  ]
[root at FFDCTSERSIP ser]#
[root at FFDCTSERSIP ser]# /etc/rc.d/init.d/ser start
Starting ser: Terminated
[root at FFDCTSERSIP ser]#
[root at FFDCTSERSIP ser]# /etc/rc.d/init.d/ser status
ser (pid 7309) is running...
[root at FFDCTSERSIP ser]#

I'm running the 0.8.11pre29 for test bed only on a Red Hat 9 system. What
could I be doing wrong?

Paul

-----Original Message-----
From: Jan Janak [mailto:jan at iptel.org]
Sent: Thursday, June 26, 2003 2:02 PM
To: Wasik, Paul
Cc: serusers at lists.iptel.org
Subject: Re: [Serusers] Need Routing Help


Edit your configuration file and set log_stderror to yes. By default the
server uses syslog to do the output so you will find it in
/var/log/messages or /var/log/daemon (depending on your distribution).
If you set the variable then ser will output all messages to the
standard output.

  Jan.

On 26-06 14:01, Wasik, Paul wrote:
> Jan,
> 
> I don't see any error output on the command line. Is there a log file
> somewhere? All I see is "Terminated" when attempting to start SER.
> 
> Paul
> 
> -----Original Message-----
> From: Jan Janak [mailto:jan at iptel.org]
> Sent: Thursday, June 26, 2003 1:58 PM
> To: Wasik, Paul
> Cc: serusers at lists.iptel.org
> Subject: Re: [Serusers] Need Routing Help
> 
> 
> Hello,
> 
> and what is the problem ? If your ser doesn't start anymore then your
> configuration file contains some mistake. In that case the output of ser
> tells you on what line the mistake is, for example:
> 
> 0(6704) parse error (75,36-37): syntax error
> 0(6704) parse error (75,36-37): invalid  route  statement
> 0(6704) parse error (75,38-39): 
> ERROR: bad config file (3 errors)
>    
> means that there is an error on line 75 of the configuration file.
> 
>   Jan.
> 
> 
> On 26-06 13:53, Wasik, Paul wrote:
> > Hi all,
> > 
> > I've got SER running on a Red Hat 9 platform. I've got MySQL and serweb
> > working and using the default ser.cfg file I can register UAs and make
> local
> > calls within the proxy. What I have not been able to do is get routing /
> > dial plan stuff to work via a Cisco SIP gateway. I cannot get SER to run
> > once I add any routing information to the ser.cfg script. I tried
> following
> > the examples like the following from the "How to" guide:
> > 
> > # attempt handoff to PSTN
> > if (uri=~"^sip:9[0-9]*@mydomain.com") { ## This assumes that the caller
is
> 
> > log("Forwarding to PSTN\n"); ## registered in our realm
> > t_relay_to( "192.168.0.2", "5060"); ## Our Cisco router
> > break;
> > };
> > Anyone have any ser.cfg script files that work succesfully for simple
dial
> > plan / routing to a SIP gatewat they could share? I'm having a hard time
> > with the routing.
> > Thanks,
> > Paul
> > 
> > 
> > _______________________________________________
> > Serusers mailing list
> > serusers at lists.iptel.org
> > http://lists.iptel.org/mailman/listinfo/serusers

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: serlog.txt
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20030627/18bc47b2/attachment.txt>