Hi Matt, That's somewhat closer to what I do in my dialplan as well. But Dan apparantly wants to add new contexts in his `extensions` table.
Zeeshan A Zakaria -- www.ilovetovoip.com On 2010-08-18 6:02 PM, "Matt Riddell" <[email protected]> wrote: We don't use a context for that. We set up dialplan code in a non asterisk part of MySQL called "routing types". When a customer selects a DDI number they can choose a routing type to use with it. These routing types allow for variable substitution - i.e. if someone adds the routing type "Direct Routing With Failover", there is a variable with this type called failover routing. The call is then sent to their SIP or IAX2 device (if not on the same machine that has the DDI number it uses DUNDI to find the appropriate machine). If somebody is unavailable on all machines, it sets the account code to the customer and goes to the outbound context for dialling. The difference is that in the routing type we don't use extensions (just applications). When someone adds the routing type to their DDI realtime extensions are created with extension 5551234 (or whatever their DDI number is) and priorities which increase. It makes some things a bit harder, but you can always use labels and the read application. -- Cheers, Matt Riddell _______________________________________________ http://www.venturevoip.com/news.php (Daily Asterisk News) http://www.venturevoip.com/exchange.php (Full ITSP Solution) http://www.venturevoip.com/st.php (SmoothTorque Predictive Dialer) -- _____________________________________________________________________ -- Bandwidth and Colocation Pr...
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
