OBiApps to use OBi110 as voice gateway

<< < (4/6) > >>

jimates:
I decided to try it the way it should work, and it does.

I dialed **2 xxx xxx xxxx and it rang to the AA.

I added your rule to the inbound call route and replaced the 001 prefix with **2 & **8
{(290xxxxxx)>(xx.):SP1},{(290xxxxxx)>(<**2:>xx.):sp2},{(290xxxxxx)>(<**8:>xx.):li},{(290xxxxxx):aa},{ph}

works just like it should. dialing without a prefix uses the default line.
when I dial using **8 it rings once, then there is a ~6 second delay (waiting for the line to connect I assume) then it rings again with a different ring (from the line provider I am sure).

I do remember others asking about a feature for this and Obihai said the AA would have to be used for anything other than the default line. maybe a fix they didn't tell us about yet.

RonR:
Quote from: ckleea on April 07, 2011, 08:10:20 pm

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

You don't have the correct number of x's.  It should be:

{>(1xxxxxxxxxx):sp1},{>([2-9]xxxxxx):li},{aa}

The bigger problem I see with this is that ANYONE can make direct calls out your SP1 and LINE ports.

jimates:
Quote from: ckleea on April 07, 2011, 08:10:20 pm

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


this is the default call route with the addition of the new rules.

Obitalk Service > InboundCallRoute
{(290xxxxxx)>(xx.):SP1},{(290xxxxxx)>(<**2:>xx.):sp2},{(290xxxxxx)>(<**8:>xx.):li},{(290xxxxxx):aa},{ph}

dialing 10 digits uses the default - sp1

dialing **2 + 10 digits uses sp2

dialing **8 + 10 digits uses the line

I know RonR can shorten that up like it should be

ckleea:
Quote from: RonR on April 07, 2011, 08:22:02 pm

Quote from: ckleea on April 07, 2011, 08:10:20 pm

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

You don't have the correct number of x's.  It should be:

{>(1xxxxxxxxxx):sp1},{>([2-9]xxxxxx):li},{aa}

The bigger problem I see with this is that ANYONE can make direct calls out your SP1 and LINE ports.



My line requires eight digits. It does work for line but not sp1


Can it be like this

{(290xxxxxx)>(1x.):SP1},,{(290xxxxxx)>([2-9]xx.):li},{(290xxxxxx):aa}

RonR:
Quote from: jimates on April 07, 2011, 08:21:36 pm

I decided to try it the way it should work, and it does.

I dialed **2 xxx xxx xxxx and it rang to the AA.

I added your rule to the inbound call route and replaced the 001 prefix with **2 & **8
{(290xxxxxx)>(xx.):SP1},{(290xxxxxx)>(<**2:>xx.):sp2},{(290xxxxxx)>(<**8:>xx.):li},{(290xxxxxx):aa},{ph}

works just like it should. dialing without a prefix uses the default line.
when I dial using **8 it rings once, then there is a ~6 second delay (waiting for the line to connect I assume) then it rings again with a different ring (from the line provider I am sure).

I do remember others asking about a feature for this and Obihai said the AA would have to be used for anything other than the default line. maybe a fix they didn't tell us about yet.

Were you actually dialing [SpeedDial] * **2 xxx xxx xxxx or just **2 xxx xxx xxxx?

If the first case, it makes sense and the InboundCallRoute callee enbedded-digit-map is working like I thought it should, and maybe your initial testing with '011' removal was somehow flawed.  If it's the second case, this does not compute unless there's been a major change to the OBiTALK calling procedure and internal handling.

Dialing without a prefix should have used SP1 (maybe that's your default line by coincidence).


I think the post you were referring to is this one:

http://www.obitalk.com/forum/index.php?topic=320.msg2901#msg2901

It may get the job done, but in my opinion, it's a little hinky.   :)

It also confirms that InboundCallRoute callee enbedded-digit-map works the way one would expect it to.

Navigation

[0] Message Index

[#] Next page

[*] Previous page