News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

Please Help nub with outbound routing

Started by Bogolisk, November 23, 2015, 11:50:20 AM

Previous topic - Next topic

Bogolisk

Hi

This is my phone digitmap:

(*9[7-8]|**7<8835100>xxxx xxxx|**3(Mpbx)|**[1-2](Mnanp)|(Mnanp)|(Mott11)S0|(Mott7)S1)

None of the nanp, ott11,ott7 has *,@ nor X in them.

The outbound routing is:
{(<**1:>XX.):sp1},{(<**2:>XX.):sp2},{(<**3:>XX.):sp3},{(<**7:>XX.):vg7},{((Mnanp)|*9[7-8]|911):tg3}

**1... works
**2... works
**3... works (**31 routed to sp3 as 3101)
**7: not, **700000094 got sent literally as **700000094, i.e. no inum prefix!


I just can't figure out why **7 is such a stubborn special case!!!! Please Help

Thanx

Bogolisk

#1
More info for the (non working for inum) dialplan"

User Defined Digitmaps:
nanp: (011xx.|1? [2-9]xx xxx xxxx)
ott11: (911|<211:6137619076>|<311:6135802400>|<511:18669294257>|<811:18667970000>)
ott7: (<613>xxx xxxx)
pbx: (<10>x)
can: (1? (204|226|236|249|250|289|306|343|365|403|416|418|431|437|438|450|506|514|519|579|581|587|600|604|613|622|639|647|705|709|778|780|782|819|873|902|905) xxx xxxx)
tollfree: (1? (800|844|855|866|877|888) xxx xxxx)


SPx digitmaps:
sp1: (*98|(Mcan)|(Mtollfree)|911)
sp2: (*97|(Mnanp))
sp3: (10[1-9]|883 5100 xxxx xxxx)

TG and VG:
tg3: sp1, sp2

vg7 access number: SP3(sip.inum.net)
vg7 digitmap: (xx.)

phone digitmaps:
(*9[7-8]|**7<8835100>xxxx xxxx|**3(Mpbx)|**[1-2](Mnanp)|(Mnanp)|(Mott11)S0|(Mott7)S1)

outbound route:
{(<**1:>XX.):sp1},{(<**2:>XX.):sp2},{(<**3:>XX.):sp3},{(<**7:>XX.):vg7},{((Mnanp)|*9[7-8]|911):tg3}



Bogolisk

I got it working but the conclusion is the obi is f***ing buggy:

phone digitmap:
(*9[7-8]|**7<8835100>xxxx xxxx|**3(Mpbx)|**[1-2](Mnanp)|(Mnanp)|(Mott11)S0|(Mott7)S1)

after dialing **7 0000 0091, the dialing sequence would be transformed into: **7 883 5100 0000 0091

outbound routing:
{((Mnanp)|*9[7-8]|911):tg3},{(<**1:>XX.):sp1},{(<**2:>XX.):sp2},{(<**3:>XX.):sp3},{(<**7:>XX.):vg7}

The outbound routing would then chop it back to: 883 5100 0000 0091 before sending out.

But I have to add 883 5100 again in the vg7 digitmap to make it work.
vg7 DigitMap:
(<883 5100>xxxx xxxx)

So it basically means that the <...> syntax kinda work some times. If the inner string was too long, it seems kinda stop working randomly.

Man, I just can't believe such highly touted ATA is that buggy in one of its fundamental functionality.

ianobi

I should say first up that I can't see why your **7 numbers are not working correctly. Your config is a little unusual, but that's no reason for it not working.

Some call tracing can be done within the OBi for calls that actually route to somewhere, even if it's the wrong digits going to the wrong places. After making a call look at:
Physical Interfaces > PHONE Port > LastDialedNumber
This will show the number after it has been selected/transformed by the Phone Port DigitMap before it gets sent to the Phone Port OutboundCallRoute.
Next Look at Status > Call History. This will show the number after it has been selected/transformed by the Phone Port OutboundCallRoute and also show to where it was routed.

I just tried your rule **7<8835100>xxxx xxxx in my Phone Port DigitMap and {(<**7:>XX.):vg7}
in my Phone Port OutboundCallRoute and it works every time. I actually used {(<**7:>XX.):sp3} which should make no difference. This is not a full test as you have very different rules in your config, but it does show the rule can work consistently.

OBi digit maps can be frustrating and confusing, but I've always found them consistent. My latest digit maps include multiple ipaddress/ports within the digit maps. I've still got the dent in my head from banging it on the walls trying to sort that one out   :)


Bogolisk

Hi Ian,

Unlike your experience, I found the obi200 fairly inconsistent. I did try: {(<**7:>XX.):sp3}.
With sp3, sometimes the <> works, some times not. I.e.
sometimes, **7<883 5100>0000 0091 would be mapped as 883 5100 0000 0091, sometimes it just stays **700000091. With vg7, it's always **700000091 unless I change vg7 digitmap. I always look at the "Call Status" for the routed number.

I have to write "**[1-2](Mnanp)" instead of "**[12](Mnanp)" because the latter sometimes would only match **2... and not **1...

It's so frustrating because there are many things not working as documented.

ianobi

That's all very odd. I've never heard of that sort of inconsistent behaviour for any OBi model. Maybe there is something wrong with your OBi - corrupted firmware, power supply problems, electrical interference?

It's drastic, but you could try a factory reset (paper clip method) and start again.  I know that would mean a lot of work setting things back up. If you do that, then see if it works with its default settings before you start making changes.