Call forward to mutiple numbers?

<< < (9/14) > >>

RonR:
Quote from: Jorge on April 23, 2012, 03:46:47 pm

However, if that trusted caller presses '1 to continue this call', then that makes ring only my phone, the call is not forked to ob123456789.

Is there any way I can fork that call from AA?


I don't believe so.  When a caller presses '1' in the Auto Attendant, the Auto Attendant dials the number contained in:

Voice Services -> Auto Attendant -> NumberOnNoInput

The default is '0', which rings the PHONE Port.  I thought you could at least change this to **9290123456 to call your OBiON App, but in my testing, I discovered there's a nasty bug in this area.  Setting NumberOnNoInput to **anything causes the OBi to either crash and reboot or else the Auto Attendant simply disconnects before the call is completed.  The Call History indicates the call should have gone through, but nothing good ever happens.

Stewart:
Quote from: Jorge on April 23, 2012, 03:46:47 pm

Right now I have this InboundCallRoute:
{(x.123|x.456|...):aa},{ph,PP(ob123456789)}
If the trusted callers have a way to block their caller ID for one call (e.g. *67 for US callers), they could use that to bypass the AA; it would ring both your phone and the OBiTalk app.

If the above is unavailable or undesirable, please post:  Which service has the InboundCallRoute in question?  What country are the trusted callers in?  Using landline or mobile?  Would AA callback work for you?  Who is SP2 provider?  Do you have a DID with them?

dealyanodeal:
@RonR - I did the following inbound call route to forward calls at my home no to my cell no. It is working great except in the situation when cellphone is down. In that case as cell phone is down , its Vocie mail kicks in rightaway and Obi has noway to know if somebody pickedup/answered the call from cell or is it just voicemail .The call gets immeiately transferred to Cell without giving any chance to pickup the home line.

Not sure if there a workaround for this but  wanted to check as this is a scenerio which will happen frequently.



Physical Interfaces -> LINE Port -> InboundCallRoute : {1111111111:ph},{ph,sp1(1111111111)}

Stewart:
Quote from: dealyanodeal on April 30, 2012, 10:22:29 am

Not sure if there a workaround for this ...
In the OBi itself, you can delay the forward to your cell, but a value long enough to answer at home may cause the caller to give up before you can answer the cell.

Otherwise, you could forward via a service such as Google Voice that is smart about off-line cell phones, but you'll need to use a different account than that used for forwarding.

Alternatively, you could use a paid service such as Anveo, which (with proper setup) would also show the original caller's number on your cell phone.

dealyanodeal:
@Stewart..I am using GV to forward the call to my cell. Here is my setup. OOMA as PSTN-primary line and 2 GVs as SP1 and SP2. For forwarding I have setup to use Sp1 to initiate a new call to cell.

You said something about GV knowing if cell phone is down or not. Which setting is that? That might resolve my problem.

Thanks

Navigation

[0] Message Index

[#] Next page

[*] Previous page