Adding Label Routing to any Routing Script
From TBwiki
(Difference between revisions)
(Added filter ruby filenames) |
(Moved the examples of filters in "How to setup filters") |
||
Line 39: | Line 39: | ||
</pre> | </pre> | ||
− | <br> Note: Other filter scripts can be added to the standard scripts to add flexibility in the routing. | + | <br> Note: Other filter scripts can be added to the standard scripts to add flexibility in the routing. Please check [[How_to_Setup_Filters|How to Setup Filters]].<br> |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + |
Revision as of 15:16, 3 February 2012
Label routing can be implemented in any routing script by following these 3 simple steps:
Gateway -> Routing Script -> YourScript.rb (Edit)
1. Add a the following line on top of your script file:
require 'routesets_digit_analyzer'
2. Include the module in your routing class:
class MyRoutingClass < BaseRouting
1.
include RoutesetsDigitAnalyzer
1.
...
1.
end
2. Add a before_filter with 'routesets_digit_analyzer' method:
before_filter :method => :routesets_digit_analyzer, :trie_order => :called
Complete Example
require 'base_routing' require 'routesets_digit_analyzer' class MyRoutingClass < BaseRouting include RoutesetsDigitAnalyzer before_filter :method => :routesets_digit_analyzer, :trie_order => :called route_match :call_field_name => :called route_match :call_field_name => :calling route_match :call_field_name => :nap route_match :method => :match_nap_availability route_remap :call_field_name => :called, :route_field_name => :remapped_called route_remap :call_field_name => :calling, :route_field_name => :remapped_calling route_remap :call_field_name => :nap, :route_field_name => :remapped_nap end
Note: Other filter scripts can be added to the standard scripts to add flexibility in the routing. Please check How to Setup Filters.