OBiApps to use OBi110 as voice gateway
jimates:
Quote from: RonR on April 07, 2011, 06:47:34 pm
Although I don't find any such examples, I would hope that normal DigitMap syntax applies:
{(200123456|200654321)>(<011:>xx.):sp2}
I can replace the 011 with anything and it will direct the call to sp2 but it dials it as it is input, and of course google says it can't complete the call.
Since there is no outbound call route for Obitalk everything has to be in the rule for the incoming call.
RonR:
If that's the case, obi-support2 is probably the only one who can tell us what the allowable syntax is and what its behavior will be. I would have thought it would be consistent throughout the OBi, but who knows? For example, ob200123456 is a valid OBi number in an OutboundCallRoute but the 'ob' part is invalid in an InboundCallRoute.
jimates:
I understand.
can it be done at two points.
from where I am Obitalk will route the call to sp2, can we remove the prefix once it gets to the sp2 digit map or call route, or is it already past those items when Obitalk sends it to sp2.
maybe obitalk can send it to a digitmap per the prefix and then the digitmap can send it to sp2 where the prefix can be removed like other prefixes.
I remember, this is something that a couple of people have asked about doing.
RonR:
The DigitMaps and OutboundCallRoutes you're referring to don't come into play anywhere in this scenaro that I'm aware of.
If the InboundCallRoute callee embedded-digit-map behaved like an OutboundCallRoute callee embedded-digit-map, I don't think there'd be a problem to solve.
ckleea:
Wonder if something worng with this
{>(1xxxxxxxxx):sp1},{>([2-9]xxxxxxx):li},{aa}
my SP1 is google voice
Landline works but if I have 1234234234, it will go to aa instead
Navigation
[0] Message Index
[#] Next page
[*] Previous page