News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

flexibility for Circle of trust Numbers by Automatically creating a digit map

Started by larrybob, January 19, 2012, 09:30:33 AM

Previous topic - Next topic

larrybob

In addition, to changing the inbound call route with circle of trust numbers, create a digit map at the same time, with the same list of numbers. If a user wants to make any changes to the inbound call route, the circle of trust numbers are no longer used. Any changes to a caller list of numbers now must be entered through the expert configuration section. This way a non-technical user can still modify the circle of trust list from the web portal  even if the inbound call route has been modified from the default value.

My suggestion above would have the circle of trust created on obitalk automatically create Ron R's aac digit map described below , at the same time it modifies the inbound call route..

An explanation of how a digit map can be used to hold a circle of trust list was explained to me by Ron R :

___________________________________________________________________________________________Circle-of-Trust is nothing more than CallerID matching in an InboundCallRoute rule.  If you make 12341234567 a trusted number, the OBiTALK Web Portal simply makes an InboundCallRoute rule to the Auto Attendant:

...{12341234567:aa}...

If you make 12347654321 a trusted number in addition to 12341234567, the OBiTALK Web Portal simply changes the InboundCallRoute rule to:

...{(12341234567|12347654321):aa}...

If you take control of any OBi setting through the OBiTALK Web Portal (such as an InboundCallRoute), you are on your own with that setting and the OBiTALK Web Portal will not add anything back into it or touch it in any way from that point on.


Auto Attendant Option 3 has nothing whatsover to do with InboundCallRoute rules.  Option 3 collects a callback number by having the caller enter it, hangs up, and places a call to that number using the Auto Attendant DigitMap, OutboundCallRoute, and PrimaryLine.


If you have 5 trusted callers that you want to be routed to the Auto Attendant with the option of being called back if they hang up before the Auto Attendant answers, simply make the following InboundCallRoute rule and don't bother with the OBiTALK Web Portal Cirle-of-Trust:

InboundCallRoute : {(12341111111|12342222222|12343333333|12344444444|123455555555):aa($1)}

You can make it even nicer to maintain by using the following InboundCallRoute rule instead:

InboundCallRoute : {(Maac):aa($1)}

and putting all your trusted Auto Attendant Callback numbers in a User Defined DigitMap:

User Settings -> User Defined Digit Maps -> User Defined Digit MapX
Label : aac
DigitMap : (12341111111|12342222222|12343333333|12344444444|123455555555)