URGENT - Auto attendant call back feature

<< < (2/2)

ianobi:
The AA is making both the call back to your cell phone and the onward call to the required number using its Primary Line. You may wish to change the AA Primary Line to SP2 Service, so that it automatically uses that service to make the onward call. If you do that, then to get the AA to make the call-back call to your cell phone using SP1, you will have to use this rule:

Voice Services > SP2 Service > X_InboundCallRoute:
{(<**1>(12222222222|13333333333)):aa($1)},{ … existing rules here …

If you prefer, then you could just as easily use the SP1 number for this initial "trigger call". Effectively, all this initial call (where you hang up before AA answers) is doing is leaving an instruction for what the AA should do next. This would work just as well:

Voice Services > SP1 Service > X_InboundCallRoute:
{(<**1>(12222222222|13333333333)):aa($1)},{ … existing rules here …


adler1:
I still have not gotten this issue resolved. I am now trying it now on an obi 110 with only sp1 in use (phonepower) and all other configurations as default.

I have looked at the call history as suggested and found the following:

My cell:
Call transferred

16:30:30 Transfer to SP1(Phone number) State=peer ringing, Bridge = 0,Ref=41885
16:30:31 End Call

The other line:
New Peer: SP1(caller id info)
Transfer Target, Bridge=0, Triggered by Ref:41885
End Call

----------------------
Not sure if this helps you figure out what's going wrong.

Thanks for your help thus far.

ianobi:
Please detail what you find at each step:

1. Call from cell phone to sp1 number, hang up before answer.

2. AA calls back to cell phone using sp1 and offers Options 1,2 & 3.

3. You select Option 2 and input the required digits for the new call.

4. Call established from cell phone to new number.


I have simulated your situation. However, my Obi110 is in use doing weird stuff that is nowhere near normal enough to be used for this. I have used my OBi1032 instead, so the Call History looks a bit different, but all the steps are the same and AA works the same. Unfortunately, the OBi1032 Call History does not show seconds, so making each step a little more difficult to follow.

I have annotated the Call History jpg - the blue notes all happen before the red notes. The first call is at the bottom of the jpg. 10000 is the test number I used for the called number.

When the final call is established there are two calls ongoing both from the AA via sp1 - one to the cell phone and one to the called number. The service provider on sp1 needs to be able to handle two calls at the same time - most voip providers can do this.

Before you test again, check that the AA has the correct DigitMap and OutboundCallRoute to make the call. Do this by dialling **0 from the phone connected to the OBi110. This will give you the AA, then select Option 2 and make the call.

Navigation

[0] Message Index

[*] Previous page