triggering a callback without Obi answering the call
lk96:
thanks.
I like replacing the $1 variable with the fully expanded and unambiguous phone # to be dialed
when the left hand rule is matched.
L.
RonR:
Quote from: lk96 on January 09, 2012, 12:55:35 pm
I like replacing the $1 variable with the fully expanded and unambiguous phone # to be dialed
when the left hand rule is matched.
In this case, so do I.
The $1 variable can be quite useful, however, in cases where you have multiple or wild-card matches, such as:
{(12341111111|12342222222|12343333333):aa($1)}
or
{(12341234xxx):aa($1)
lk96:
one follow up question:
suppose I want the AA to call back through 2 accounts/interfaces simultaneously (ie through both SP1 and SP2).
Does the Obi config allow such a possibility ?
The use case here would be as follows: in my case I tend to use really cheapo
providers when I'm in the US because I have plenty of options and choices
and ways to recover when some provider is out.
When I'm in Europe with a mobile in my hand, it will be critical to
get the call back. By forking the outbound calling from Obi through two providers,
the chances that at least one of the two providers is operational is much better.
I'm thinking that instead of using the variable $1 or the exact phone number in the AA( ... ) parameter,
a trunk group could be used instead? in this case the trunk group would consiste of the
2 cheapo SIP providers. If so, what does a TG syntax/config looks like ?
thanks
L.
Stewart:
I don't believe that you can fork two AA instances. However, the AA could call back into the OBi via the loopback address, e.g. 55555@127.0.0.1:5061. Then, the inbound route for SP2 could detect the 55555 and fork via two VGx. However, I suspect that you'll have problems with that approach. For example, a call with no or one-way audio arrives first, preventing the "good" path from getting through.
IMO, you should simply have two (or more) ways to trigger a callback, which would then use different providers. Possibilities include what number you call, e.g. your GV or IPKall DID, or what caller ID is sent, e.g. calling direct or via Rebtel. You might make use of free DIDs from UKDDI, ippi.fr or messagenet.it, or set up Localphone so calling a local number rings to your iNum (with any provider).
RonR:
Quote from: lk96 on January 13, 2012, 11:34:00 am
suppose I want the AA to call back through 2 accounts/interfaces simultaneously (ie through both SP1 and SP2).
Does the Obi config allow such a possibility ?
No. There is only one instance of the Auto Attendant and it can only initiate a single callback.
Quote from: lk96 on January 13, 2012, 11:34:00 am
When I'm in Europe with a mobile in my hand, it will be critical to
get the call back. By forking the outbound calling from Obi through two providers,
the chances that at least one of the two providers is operational is much better.
The OBi does not support forking outbound calls.
Quote from: lk96 on January 13, 2012, 11:34:00 am
I'm thinking that instead of using the variable $1 or the exact phone number in the AA( ... ) parameter,
a trunk group could be used instead? in this case the trunk group would consiste of the
2 cheapo SIP providers. If so, what does a TG syntax/config looks like ?
A Trunk Group doesn't guarantee that a call goes through. It simply allows specifying multiple trunks to be used in case the resources of one or more trunks are not available. You can set the Auto Attendant PrimaryLine to Trunk Group 1 and then define multiple trunks at Trunk Group1 -> TrunkList.
Navigation
[0] Message Index
[#] Next page
[*] Previous page