OutboundCallRoute configuration

[bill-cary]

I have an OBI 100 configured with Anveo on SP1 for E911 service with no DID.
I have an OBI 200 configured with a GV # and the OBI 100 and 200 configured for OBITALK.

If I set the OBI 100/Physical Interfaces/PHONE Port/OutboundCallRoute to:
(<510511856*>(Mpli)):pp  I can make and receive calls on the assigned GV #
(911S0|933S0):SP1   I can make 933/911 calls
{(<510511856*>(Mpli)):pp},{(911S0|933S0):SP1}  I can only make OBITALK calls
{(911S0|933S0):SP1,(<510511856*>(Mpli)):pp}  I can only make 933 calls

The Tutorial suggests that this is the way to accomplish this but isn't exactly clear.
What am I missing??

[azrobert]

Try:
{(911S0|933S0):SP1},{(<510514856*>(Mpli)):pp}

What rules are in (Mpli) ?
I suspect it has a rule that matches 911 and 933.
That is why you can't have the reverse of the above as you coded.

[bill-cary]

if it works either way for just the first rule it should not be a problem with Mpli since the 911 rule doesn't deal with that.
According to the tutorial I think the {} are in the right place, but I don't think I tried that yet.

[bill-cary]

Nope, whatever is the 1st one works. It never gets to the 2nd.
Dialing a 10 digit number with the 911 rule first tells me there is no call route available.
Dialing the 933 number with that rule last just sits there and times out.

(*xx|1xxxxxxxxxx|<1828>[2-9]xxxxxx|<1>[2-9]xxxxxxxxxS0|xx.)

[azrobert]

xx. in (Mpli) will match 911 or 933.

Did you try my suggestion exactly like its coded?

{(911S0|933S0):SP1,(<510514856*>(Mpli)):pp}
I don't think you can have multiple destinations between the {} so it's ignoring the 2nd destination (pp).

You can code something like this:
{(911S0|933S0),(<510514856*>(Mpli)):pp}
I'm not suggesting you can use this. It's just an example.

[bill-cary]

This is driving me batty. Every time I reconfigure it to create a matrix, it does something different.
I will do it one more time in the AM.
SP1 is configured for Anveo E911 only service
OBITALK is configured to connect the 100 to the 200 so the 200 can make/rcv GV calls.
Isn't that multiple destinations?

This is consistent

ISTP Profile A Digi Map = (*xx|1xxxxxxxxxx|<1828>[2-9]xxxxxx|<1>[2-9]xxxxxxxxxS0)
OCR = {(911S0|933S0):SP1,(<510511856*>(Mpli)):pp}
933 > fast busy
GV > no call route

ISTP Profile A Digi Map = (*xx|1xxxxxxxxxx|<1828>[2-9]xxxxxx|<1>[2-9]xxxxxxxxxS0|xx.)
OCR = {(911S0|933S0):SP1,(<510511856*>(Mpli)):pp}
933 > dials
GV > no call route


This is inconsistent

ISTP Profile A Digi Map = (*xx|1xxxxxxxxxx|<1828>[2-9]xxxxxx|<1>[2-9]xxxxxxxxxS0|xx.)
OCR = {(<510511856*>(Mpli)):pp,(911S0|933S0):SP1}
933 > cannot complete call >> or rejected by server
GV > dials OK

ISTP Profile A Digi Map = (*xx|1xxxxxxxxxx|<1828>[2-9]xxxxxx|<1>[2-9]xxxxxxxxxS0)
OCR = {(<510511856*>(Mpli)):pp,(911S0|933S0):SP1}
933 > fast busy
GV > sometimes works sometimes mostly Rejected by server

Is it a problem that SP1 is listed as the primary line on OBI dashboard?

Thanks AZROBERT

[azrobert]

The Phone DigitMap plus the Primary Line's DigitMap will validate the dialed number. After you removed the "xx." there isn't a rule that matches 933. Add "933|" after "911|" in the Phone DigitMap.

If you want to use S0, place it after the 911 and 933 in the Phone DigitMap. The delay happens during the Phone DigitMap processing. The S0 in the OCR does nothing.

Not this:
{(911S0|933S0):SP1,(<510514856*>(Mpli)):pp}

This:
{(911|933):SP1},{(<510514856*>(Mpli)):pp}

[bill-cary]

AZ
update
The answer is - dial S.L.O.W
Once it has errored I have to delete history and/or reboot.
So how to I automate a delay so I don't have to fix it?

----------------
Something is messed up with OBI. That is the reason I have no hair.
Sometimes I get a 503 error and sometimes not.
According to wife, that has been happening at home on my 200. She will dial a number and get 503, then redial it and it will go thru.
I just made a change here and got 503, then I dialed a different # and it went thru, Then I dialed the one that errored and it went thru.
I have been using the same # to test and it usually rings 4 times then errors. The 2nd time I dial it errors without ringing.

Check this out.........
Profile A
(911S0|933S0|1xxxxxxxxxx|<1>[2-9]xxxxxxxxxS0|<1919>[2-9]xxxxxx)
Profile B
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxxS0|<1919>[2-9]xxxxxx)
OCR
{(<510511856*>(Msp2)):pp},{(911|933):sp1}

933 works
GV works -- the 1st dial, subsequent dials produce the same result as above; rings 4 times then errors. The 3rd+ times I dial it errors without ringing.

Chew on this a while...........
I DELETED THE CALL HISTORY (doing nothing else) AND TRIED THE ABOVE AGAIN DIALING MULTIPLE TIMES AND ALL IS WORKING. However...........it does not last long.

There is a timing problem here. When it errors, I delete history and it works again a few times. But then that doesn't work all the time either.

933 works consistently.

THEREFORE, if it works sometimes the config must be correct, right?
If it does similar things on the 200 (not the same SP) and this 100 is connected thru that 200 is it the 100, the 200 or OBI, or maybe GV??
When it fails on the 100 it stays that way till I do something - delete history works often but not always.
On the 200 it just "fixes" itself.

Changing Mpli to Msp2 probably does not affect it but it separates things.

Any ideas???