Call Back via Auto Attendant on the OBi Device

(1/9) > >>

There are two ways to do a "Call Back" via Auto Attendant (AA) with your OBi.

Method 1: Use InboundCallRoute
Method 1 will require you to adjust OBi settings manually.  Therefore, your OBi should not be in Auto-Provision mode for OBiTALK management.  Note:  We will support Call Back set-up and configuration via the OBiTALK portal in the near future.

An InboundCallRoute Rule can be specified to let the AA call back the caller’s or any other number, if the caller hangs up before AA answers.  For this to work Caller ID service is required on the inbound trunk.

For example, consider the rule {(<**1>(14089913313|12121559801)):aa($1)}

It says if 14089913313 or 12121559801 calls, the call is routed to AA.

If caller hangs up before the AA answers, the AA calls the number represented by $1

Recall that $1 is expanded into the caller's number after processing by the digit map on the left side of the colon. In this case it is the caller’s number prepended by **1.

The **1 is required for outbound call routing when AA calls back.  Here, it indicates SP1 is to be used for calling back (based on the OBi's default setting).

New parameter in AA Service settings called CallbackAnswerDelay
CallbackAnswerDelay controls the number of milliseconds before the AA answers when a callback number is specified in the rule. The default value is 10000 ms (10 seconds).  This means that when the OBi is configured to Call Back a particular caller (cased on their incoming Caller ID), the caller should hang-up before the ten second answer delay timer expires if they want an automatic Call Back from the OBi.  If the caller does not want a Call Back, e.g. they want to ring the phone connected to the OBi, then they will let the OBi ring for 10 seconds, at which time the normal Inbound Call Routing Rule takes effect.

Without the ($1) argument after aa in the last example, AA behaves the normal way and the answer delay follows the parameter in the AA Service settings called AnswerDelay.

Method 2: Use (NEW) AA Main Menu Option 3: “Enter a callback number”
With this method, the Caller explicitly enters the number to be called back by the AA.  If a valid number is entered, the AA says Thank You and Goodbye, then starts calling back 2s after the current call has ended.  If number entered is invalid, the AA plays a SIT tone followed by an error message.

Tip: If the service used to connect to the OBi Attendant supports caller ID, when prompted for the call back number, just enter 00# and hang-up.  The OBi Attendant will call back whatever was indicated as the Caller ID number when you initially called the OBi.

I do see a "X_InboundCallRoute" under Voice Services -> SP1 Service, but I don't see any parameter "InboundCallRoute".

Currently it is set to "ph", if I modify as per your suggestions I should be able to get a callback from Obi, can you please confirm.


This is my Call back setup. Works great.


1) <**2> forces outgoing calls to go over my GV account in my SP2. I figured I would set it this way because I setup Trunk Group1 as my primary line . Trunk Group1 looks for first available line. I wanted to control the calls going out only on the GV channel on SP2.

2) I have a voip account. When I call through that account my CID has 15142321234 in front. The rest of the numbers should be how the phone picks up the CID. This is the section of the setup which offers the Call back service.

3) second part after the comma I have extensions from a PBX going to the AA. You could just as easily put a phone number in there.

Any other number will ring the attached phone in normal fashion. The controls based on CID is great. I have unlimited incoming on my cell. I can use the OBi to make calls on my cell  without using any of my outgoing minutes. You don't let the OBi answer the call. Immediately after the first ring, you hang up. Your OBi will call back the number identified on the CID if it matches any of the numbers in the above config.

All the examples shown above are using the SP1/SP2 Trunk (using **1 or **2) for callback service without entering AA. I have tried the LINE trunk but failed. My question is does the callback function works for LINE trunk? For example,


where 99887766 is supposed to be my HK PSTN phone number.

I can only do the callback via the LINE trunk if AA answers my call, then I leave my callback phone number by choosing the option 3.



I can confirm this is a bug in the OBi110 and we will address this in a future release.

Please email if you want to try out a test build with a fix to this problem.

Thank you for reporting the issue.


[0] Message Index

[#] Next page