RealTime and Priority -1?


#1

Hey.

Using a very current CVS release, both res_config_odbc and res_config_mysql will do something pretty weird…

I’ve got a context that includes another context. Both use the switch=>Realtime/@

For example:

[context1]
 include=>context2
 switch=>Realtime/@
 [context2]
  switch=>Realtime/@

What happens is, if it can't find the extension in context1 in the DB it'll search in context2. That's fine but when it searches context2 it specifies priority = '-1' (that's [b]negative[/b] one) in the SQL. 
  Anyone know why???

   Is it a bug? Or incorrect configuration on my part?

  Any insight would be greatly appreciated.
 Thanks!

j