Using Obi 110 to block Robocalls by utilizing AA
Patriot9471:
Everyone,
I am absolutely new to Obi and Voice call routing world. I have a VoIP service that has it's own ATA and outputs to a RG11. My idea is to connect that port to OBI 110 Line port and then use AA to screen calls by messaging telemarketers to hang up if they are selling or requite the caller to use an announced 2 digit number to continue the call. Additionally I want to allow certain phone numbers to bypass AA, based on a small whitelist.
First of all, looks like this can be done however ....the policy model for OBI is quite complex and I would appreciate if someone can guide me through the settings required.
Thanks in advance.
ianobi:
What you suggest can be done. The output of your existing voip ata will look like a PSTN line to the Line Port of the OBi110. However, there’s a few things to consider:
Your existing ata coverts speech from digital to audio. If you now feed that audio to the OBi110, then it will convert the audio to digital, then back to audio to output to the Phone Port. All these conversions may lead to a lowering of speech quality, which may or may not be noticeable.
Assuming that you are in the US and you existing ata outputs CallerID in the standard North American format, then the OBi110 will add around four seconds delay while processing the CallerID before ringing its Phone Port.
Quote
My idea is to connect that port to OBI 110 Line port and then use AA to screen calls by messaging telemarketers to hang up if they are selling or requite the caller to use an announced 2 digit number to continue the call.
To do precisely what you wish would require some modification to the Auto Attendant settings. However, the default setting Main Menu starts “press 1 to continue this call”. This may be enough to stop telemarketers. After repeating the announcement three times the Auto Attendant will terminate the call if no response is received. Additionally, you would have to disable options 2 and 3 of the Main Menu – that’s not too difficult if you only intend to use the Auto Attendant for screening telemarketing calls.
Quote
Additionally I want to allow certain phone numbers to bypass AA, based on a small whitelist.
This is quite easy. If the white list is quite small than something like this would work:
Physical Interfaces > LINE Port > InboundCallRoute:
{(12222222222|13333333333|14444444444):ph},{aa}
The first rule is the white list sending calls from those numbers straight to the OBi110 Phone Port. The second rule sends all other calls to the Auto Attendant. The first rule could be made to look neater if there’s a longer list of numbers by using a User Defined Digit Map.
If you want to try this out, then post back and myself or others will help with a more detailed reply.
Patriot9471:
ianobi ... thank you for your help.
I have connected Obi 110 LINE port to my PSTN line (voip ata)
I have connected Obi 110 PHONE port to my Phone
I have a dial tone on my phone
Here is what I did in the settings
Line Port Settings
Line Port is enabled
Inboundcall route {(1XXXXXXXXXX|13333333333|14444444444):ph},{aa}
Everything else is default
AA Settings
AA is enabled
Everything else is default
AA Prompts, I have disabled prompts 2 and 3
So here is what I am getting
First
Inbound call to my home phone
When I call in using a non whitelisted number I get AA with message, "press 1 to continue the call" . When I press 1 , the phone rings and the call gets successfully established and that is great!! . Problem is that same thing happens when I call from a Whitelisted number also. Perhaps the whitelist syntax might be an issue.
Second
Outbound call from my phone
I get a dialtone and then I proceed to call a number and nothing happens. The PHONE port is enabled but everything is a default.
Thanks
ianobi:
To see what’s happening you need to look at Status > Call History after a call. This can only be viewed via the local web page. Dial ***1 for the local ip address. The username and password will both be “admin”.
I suspect that CallerID is either not be received by the OBi110 or is not being correctly interpreted – maybe your existing ata only passes on ten digits? The white list numbers have to exactly match what is shown in the Call History for the calls that you wish to go straight through to the Phone Port. Other CallerIDs or no CallerID calls will be sent to the AA.
With the outgoing problem, again look at the Call History to see where calls are routing. With default settings the OBi110 should send the call out via the Line Port. This setting should be as follows:
Physical Interfaces > PHONE Port > PrimaryLine: PSTN Line
To make sure calls are rejected by the AA when no input is received after three repeats of the announcement change this to blank:
Voice Services > Auto Attendant > NumberOnNoInput
The default is “0”. Delete that and save with a blank setting.
If you are making changes via the OBiTALK Expert Pages portal, then continue with that method. Only use the web page to view Call History and to check settings have changed.
ianobi:
Even though you have disabled prompts 2 and 3, the functions will still work. If you wish to prevent anyone who may know this taking advantage and making calls, change to these settings:
Voice Services > Auto Attendant > DigitMap:
(0)
Voice Services > Auto Attendant > OutboundCallRoute:
{0:ph}
Navigation
[0] Message Index
[#] Next page