The obi web portal has an interface for "trusted callers" which is then used to created the inbound call routing to determine if an incoming call is routed to the AA or directly to ring the phone.
There are numerous options that can be programed into the incoming call route. Automatic call return, or automatic call through to a specific number are just two of the available possibilities.
The problem however, is that if the obitalk default programing is changed in anyway, the "trusted caller" list created with the obitalk web portal is discarded in the inbound call route, and must be entered manually either directly into the modified inbound call route, or into a user defined digit map which can then be used where ever it is needed.
Obi, made a large effort into managing trusted callers from the web portal, but then dropped the ball by limiting its usefulness to only the default programing.
It would be very easy to just create an automatically generated digitmap of "trusted callers" to be used anywhere, from the structure all ready incorporated into the web portal.
If anyone could use this feature please respond to this post.
Larry