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@iptel.org] Sent: Thursday, June 26, 2003 1:58 PM To: Wasik, Paul Cc: serusers@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@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
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@iptel.org] Sent: Thursday, June 26, 2003 1:58 PM To: Wasik, Paul Cc: serusers@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@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-
Jan Janak -
Wasik, Paul