[OpenSIPS-Users] error in config file - invalid routing table number

[Brett Nemeroff]

Chances are, if you can't route with 100 route blocks, you're doing
something inefficient. Of course, this is debatable, but there are many
mechanisms to route calls other than route blocks. Check out drouting for
example.
-Brett



On Tue, May 19, 2009 at 4:00 PM, Patrick <phigaro at dmv.com> wrote:

> Would having more than 100 route tables mean I might run into issues
> with private memory?  The is no command argument to change that
> (unlike shared mem)...
>
>
> On May 19, 2009, at 4:57 PM, Norman Brandinger wrote:
>
> Take a look at config.h, specifically the following setting:
>
> #define RT_NO 100
>
> You'll have to recompile after changing the value.
>
> Regards,
> Norm
>
> Patrick wrote:
> > Hello,
> >     I've run into a limitation in the config file.   I'm defining
> > routes tables as
> >
> > route[1] {
> >    ...
> > }
> >
> > ....
> >
> > route[100] {
> >    ...
> > }
> >
> >
> > opensips: CRITICAL:core:yyerror: parse error in config file, line
> > 2000, column 1-2: invalid routing table number
> >
> >
> > Is there a limit of only 1-99 for routing tables?   Also, do these
> > numbers have to be sequential?
> >
> >
> >
> > Thanks,
> >
> > Patrick
> >
> > _______________________________________________
> > Users mailing list
> > Users at lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
> >
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20090519/a7451432/attachment-0001.htm