dslreports logo
 
    All Forums Hot Topics Gallery
spc
uniqs
33
OldCoalMiner
join:2004-05-20

1 edit

OldCoalMiner to RonR

Member

to RonR

Re: Dial Plan Generator for OBi100/110/202

Interesting. Thanks for this.

Edit to add: Are you taking additional feature requests? Because there's something I've never figured out how to do on an Obi110 dial plan, but yet is seems simple enough. And have never seen a clear solution on the Obi forums.
RonR
join:2003-10-10
Ash Flat, AR

RonR

Member

said by OldCoalMiner:

Are you taking additional feature requests?

I'm willing to listen and consider them.
Mango
Use DMZ and you get a kick in the dick.
Premium Member
join:2008-12-25
www.toao.net

Mango to OldCoalMiner

Premium Member

to OldCoalMiner
said by OldCoalMiner:

there's something I've never figured out how to do on an Obi110 dial plan, but yet is seems simple enough. And have never seen a clear solution on the Obi forums.

Don't keep us in suspense.
Ostracus
join:2011-09-05
Henderson, KY

Ostracus to RonR

Member

to RonR
Dealing with ObiPLUS?
OldCoalMiner
join:2004-05-20

OldCoalMiner to RonR

Member

to RonR
I was thinking a check box for second dialtone with **x, for when an SPx is not directly associated to PHx. That seemed hard to figure out when I first started using an Obi, it's buried deep away in the documentation.

I have one more that will add/describe when more time allows.
RonR
join:2003-10-10
Ash Flat, AR

RonR

Member

said by OldCoalMiner:

I was thinking a check box for second dialtone with **x, for when an SPx is not directly associated to PHx.

The dial plan created by OBiCfg omits the service route access code (**n) for any SPn/VGn that has its checkbox unchecked (the first row in the upper panel). As a result, dialing **n for a non-existent trunk receives an immediate fast-busy. I hope that accomplishes the goal you had in mind.
OldCoalMiner
join:2004-05-20

2 edits

OldCoalMiner to Mango

Member

to Mango
said by Mango:

said by OldCoalMiner:

there's something I've never figured out how to do on an Obi110 dial plan, but yet is seems simple enough. And have never seen a clear solution on the Obi forums.

Don't keep us in suspense. :)

Here goes, I hope this makes sense:

Background/Usage:
- This applies to an Obi110 only, because of the Line port.

- Its for a remote administered Obi110, the type people describe as Grandma lives in timbuktu and I moved her to an Obi that I administer remotely. She keeps her laneline but all LD calls go via GV with no special dialing codes needed.

Want to implement doing using these four things:
1. Route seven digit dialed numbers to L1 or SP1/GV based on the NXX code. Examples and explanations Ive looked all do routing based on the area code.
1.a For local calls dialed as NXX-1234, route directly to the line port.
1.b For all non-local calls dialed as NXX-1234, prefix with 1-717 (or whatever area code), and send to SP1 (GV).
- The local telco allows seven digit dialing for certain numbers and bills as regional long distance (or whatever name they use). This is about half of the monthly bill.
2. Isolate the list of NXX codes in one place only, such as a user defined map. I could never get this to work. Im hoping it was only a syntax issue.

Ill be happy to get 1a and 1b working, will be very nice to get #2 working.

For #2, the local NXX codes look like this in digit map syntax.

What Ive tried:

This. It got too long, want something more compact:

<500>xxxxS0|<509>xxxxS0|<554>xxxxS0|<590>xxxxS0|<644>xxxxS0|<648>xxxxS0|<672>xxxxS0|<712>xxxxS0|<738>xxxxS0|<875>xxxxS0|<933>xxxxS0|<985>xxxxS0|

For this:
the “!” (Not) operator and the <1717> syntax (prepend 1717) did not work the way intended, ie, if seven digit code is not in this list, the prepend 1717 to make it an eleven digit number and sent to SP1/GV.

(500|509|554|590|644|648|672|712|738|875|933|985)xxxxS0:L1, !<1717>(500|509|554|590|644|648|672|712|738|875|933|985)xxxxS0:SP1

Let’s say a user created digit map is “LocalRateNXX”, it’s value is (500|509|554|590|644|648|672|679|682|689|691|712|738|875|933|985)

I was hoping to get something like this to work:
(MLocalRateNXX)xxxxS0:L1, !<1717>(MLocalRateNXX)xxxxS0:SP1

Edit: In the preceding digit map syntax, replace [ ] with left and right brackets, for some reason the posted version is completely removing anything between "left bracket" and ">", but in the edit window version it's still there.

Edit #2: Fixed code blocks, for readability.

StillLearn
Premium Member
join:2002-03-21
Streamwood, IL

2 edits

StillLearn

Premium Member

said by OldCoalMiner:

Edit: In the preceeding digit map syntax, replace [ ] with left and right brackets, for some reason the posted version is completely removing anything between "left bracket" and ">", but in the edit window version it's still there.

To post <something>, write that as &LT;something&GT;

Alternatively, put the strings in a code block (enclose in <code> and </code>) as RonR does. Here is a code block:
<something>
RonR
join:2003-10-10
Ash Flat, AR

RonR to OldCoalMiner

Member

to OldCoalMiner
Assuming Google Voice is configured on SP1...

PrimaryLine: SP1

ITSP Profile A DigitMap: (<**8>(Mlcl)|<1717>[2-9]xxxxxx|<1>[2-9]xx[2-9]xxxxxx|1[2-9]xx[2-9]xxxxxx|(00|011)xx.)

LINE Port DigitMap: ([2-9]11S0|[2-9]xxxxxx|[2-9]xx[2-9]xxxxxx|1[2-9]xx[2-9]xxxxxx)

User Defined Digit Mapx
Label: lcl
DigitMap: ([2-9]11S0|(486|500|509|554|590|644|648|672|712|738|875|933|985)xxxx)
OldCoalMiner
join:2004-05-20

OldCoalMiner

Member

(<**8>(Mlcl)|<1717>[2-9]xxxxxx|

Interesting construction. Compact and clean.

I'll confess I had to look at it for a minute or two to figure out what it's doing: If the dialed seven digit (or three digit x11) string is in the user defined digit map, then prepend **8, which via the OutBound Call Route DigitMap will be sent to the li port after being processed by the li digit map.

I notice you put S0 at the end of 911s, but do not use it elsewhere, such as at the end of the xxxx in the Mlcl.

Thanks very much.
RonR
join:2003-10-10
Ash Flat, AR

RonR

Member

said by OldCoalMiner:

I notice you put S0 at the end of 911s, but do not use it elsewhere, such as at the end of the xxxx in the Mlcl.

x11 is reserved and no other numbers can start with that sequence, so it's safe to force the interdigit timer to zero, forcing the rule to match. 7-digit numbers can still grow, so the interdigit timer has to be left running.