Too many outbound routes?

Can you have too many outbound routes for extension routing?
I have a route that only a couple of extensions are allowed to use (route 28), you will see from the log it retrieves OK but when the goto statement runs it misses the last 2 routes, any ideas.
Here is the log:
[2014-09-11 16:15:20] VERBOSE[4407][C-0002f161] pbx.c: – Executing [[email protected]:2] Set(“SIP/4302-00002cf1”, “ROUTEUSER=4302”) in new stack
[2014-09-11 16:15:20] VERBOSE[4407][C-0002f161] pbx.c: – Executing [[email protected]:3] GotoIf(“SIP/4302-00002cf1”, “1?restrictedroute-1-3-4-5-6-7-8-9-10-11-12-13-14-15-16-17-18-19-20-21-22-23-25-26-27-28,01252792199,2:outbound-allroutes,012xxxxxxxx,2”) in new stack
[2014-09-11 16:15:20] VERBOSE[4407][C-0002f161] pbx.c: – Goto (restrictedroute-1-3-4-5-6-7-8-9-10-11-12-13-14-15-16-17-18-19-20-21-22-23-25-26,012xxxxxxxx,2)
[2014-09-11 16:15:20] VERBOSE[4407][C-0002f161] pbx.c: – Executing [[email protected]-17-18-19-20-21-22-23-25-26:2] ExecIf(“SIP/4302-00002cf1”, “0 ?Set(CDR(accountcode)=)”) in new stack***

You can run out of contexts, but usually you will only run into that if you are using custom contexts

Thank you for your reply, although we have the customer context module installed we don’t actually have any.

Could it be a bug as it looks like the variable is being truncated.
From the log the variable being returned is:
restrictedroute-1-3-4-5-6-7-8-9-10-11-12-13-14-15-16-17-18-19-20-21-22-23-25-26-27-28
But the variable being processed is:
restrictedroute-1-3-4-5-6-7-8-9-10-11-12-13-14-15-16-17-18-19-20-21-22-23-25-26

Very odd.

OK, further testing.
Context ‘restrictedroute-1-3-4-5-6-7-8-9-10-11-12-13-14-15-16-17-18-19-20-21-22-23-25-26’ doesn’t actually exist in extentions_additional.conf the closest is ‘restrictedroute-1-3-4-5-6-7-8-9-10-11-12-13-14-15-16-17-18-19-20-21-22-23-25-26-27’ which it must be doing a partial match against.

If I take out the variable and put in as a string I get the same result. If I adjust the string so it starts from 10 it is passed correctly but of course no match.

Just found this:
Context names have a maximum length of 79 characters (80 characters – 1 terminating null).

So:
restrictedroute-1-3-4-5-6-7-8-9-10-11-12-13-14-15-16-17-18-19-20-21-22-23-25-26-27-28
is 86 characters
and
restrictedroute-1-3-4-5-6-7-8-9-10-11-12-13-14-15-16-17-18-19-20-21-22-23-25-26
is 80 characters (shouldn’t really work according to that note).

So there is the problem is there a fix?

Or is it a bug in ‘Extension Routing’ that needs fixing.

I have 17 sites routing out of this PBX and we adding more sites. I also route national, international and mobile depending local and cost so I can’t really see a way to reduce my outbound routes.

There’s no limit. Uninstall custom contexts if you aren’t using it.

How do make a bug report?
Extension Routing
Fails if you have more than 26 routes.
Reason: Context names have a maximum length of 79 characters (80 characters – 1 terminating null).

At the top of the page click the Issues button to open a bug.