26 Jun
2003
26 Jun
'03
8:57 p.m.
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(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers