REVE Session Controller

REVE Session Controller

Advanced & Intelligent Routing
RSC has intelligent routing capabilites with advanced algorithm not only to facilitate routing to suit versatile  business rquirements but also to  ensure quicker call routing. The Route Management System of RSC is easy-tomanage, configure and deploy.
Destination Code / Digit-wise Routing
With RSC you can set your routing preferences destination-wise or digitwise. Destination codes can be easily changed to change the routing paths. Say for example, if a call comes as 8801871418234, while you added the routes 919 and 8801, then system will pass call with 8801 route.

Priority Based Routing
In case you have set two routes for the same destination. Then you can set one of them as Priority 1 and the other as Priority 2. The system will try to pass the call through Priority 1 route first, and if it is unable to do so, then it will automatically pass it through Priority 2.

Longest Destination Code Based Routing
If a route is set with a long destination code, then system will pass the call with only the route that matches with the longest destination.

For example, if you have set routes as 880, 8801 and 88018, and a call comes in as 8801871418234. Then the system will try to pass it with only 88018 route, and if it fails then the system will not try the next available routes, i.e. 8801 and 880.

If this facility is disabled, then the system will first route the calls with the longest destination, and if it fails then it will automatically route through the next matching shorter destination code.

Loss Less Routing (LLR)
RSC has loss-protect facility configured. And if this facility is enabled, then the system will not pass any call if its originating rate is lower than its termination rate in the system or if its selling rate is lower than its buying rate in the system.


Time Based Routing
The system can be configured to pass calls for specified time periods with specific vendors to make sure that the cheapest routes are used to increase your profitability.

Least Cost Routing (LCR)
In this configuration, if the destination and priority happen to be the same in the system, then system would automatically check the route that offers the least cost for passing a call, and will route it likewise to ensure greater profitability.

Quality Based Routing
System automatically selects the termination vendor with the best ACD and ASR values, and passes the calls through them to ensure best quality service for the origination carrier.

Note: Group LCR will not be effective in this configuration but LLR will work to protect against losses.

Quality Based LCR Routing
RSC has advanced tools to give best quality within the LCR. If any termination fails to maintain standard ACD and ASR then the system will automatically stop forwarding calls to that route or set it at lowest priority for terminating calls.

Note:  This facility works along with Percentage Based Routing.

Percentage Based Routing
In percentage based routing user can share call volume for a specific desitantion within a group of routes according to preset percentages.
Loss Less Routing and Least Cost Routing will become automatically disabled for the specific destination for which  Percentage Based Routing is enabled.

Note: Group LLR and LCR will not work with this facility.

Prefix Based Routing
User can take calls from origination carriers with Multiple Prefixes and terminate them as per their different rates for the same destination.

Protocol Based Routing
RSC supports multiple protocol so you can take calls with H.323 protocol and route it for SIP termination, and vice versa.

Client-wise Specific Routing
The system can be configured in such a way that specific routes can be passed through specific terminators as per demands of the originators or to maintain higher quality routes.

Port Capacity Based Routing
If your termination provider allows you 100 ports, then you can configure the system in such a way that only 100 calls get transferred to the desired destination. For example, say you have 30 calls for destination 8801, 40 calls for destination 919 and 30 calls for destination 92, if call capacity gets exhausted for a specific destination to a termination vendor, then system will automatically pass the leftover calls of that prefix to other available routes for the same destination.

Stop Route Retry Facility
Sometimes for specific destinations, termination vendors provide special rate offers. For instance, let’s say out of the following mentioned destinations; 880, 8801, 88018, 88017, 88019, only 88019 has a special rate offer. So user can enable ‘Stop Retry’ while adding 88019 route so that when any call like 8801934516784 comes, then system will pass that call only through 88019 destination route.

Also, if this route fails, then the call will not pass through any other available routes like 880 or 8801.

Translation Based Routing
With this, the user has authority to take calls with different prefixes and rates for the same destination, and can send them to any termination with a fixed destination code.

Disconnect Cause Code-wise Stop Route Retry
With this facility if the switch finds the destination number called as busy (e.g. 486 Cause Code for User Busy), then it will not retry dialling that same number with another route. The switch will simply stop calling, thereby reducing route-retry overload on switch and ultimately reducing the PDD.

Media Routing

Optional Media Termination:
Users can configure each origination vendor on full media forwarding or non-media mode, to pass the calls for termination.

Media NAT Traversal:
RSC ensures full security while media packets pass from private networks to public network.

Call Simulation
RSC comes with call simulator. The call simulator helps users to debug by telling whether the call will pass or not with the available route list. Users can check whether routes are getting eliminated from the route list due to Loss Less or Blocked routes. Users can also check the LCR sequence from the available route list and which routes can take calls  first, and so on. If for an origination vendor, the call doesn’t pass to a specific destination then user can easily check whether he has available Balance, Rate and Route to pass the call.

No comments:

Post a Comment


Related Posts Plugin for WordPress, Blogger...

Find us on Facebook