Area Codes

[leeniep]

New to the Siemens world! Eeek

Where would I go to add an area code to the PBX?


Leenie P

 

[LoPath]

From my cheat sheet:

[b][u]This is administered as an LCR Dialing Pattern.[/u][/b]

It’s easiest to see all of the dial patterns in the GUI. Go to Configuration Management, Least Cost Routing, Digit Pattern.

If you switch to the Object List, you’ll see lots of entries. Some for extensions, some for menu trees, and others for actual allowed dialing patterns for outgoing calls.

As an example:
9-W-1-866-XXX-XXXX

This rule means you can dial 9, then W provides a second dial tone, dial 1-866- and any 7 digits. This is to allow dialing toll-free calls with an 866 prefix. Any time a new toll-free prefix is added, you’ll want to check in the 4000 and ensure these can be dialed. If it’s not in the list, it’s easiest to add in Expert Mode.

ADD-LDPLN:LCRPATT,0,9-W-1-844-XXX-XXXX,,18,,,1,12,,,N;
H500:  AMO LDPLN STARTED
H07: LDP HAS BEEN ADDED

AMO-LDPLN-111       ADMINISTRATION LCR DIALPLAN                                 
ADD COMPLETED;
  <
These all point to Route 18, which is TOLL FREE.

Local number examples:
9-W-402-XXX-XXXX (Original Omaha area prefix)
9-W-531-XXX-XXXX (Added Omaha area prefix)
9-W-712-XXX-XXXX (Council Bluffs are prefix)

When Nebraska implemented mandatory 10-digit dialing, it became necessary to add entries for all of the local prefixes in the 4000. These all point to Route 1, which is ATT LOCAL.
Regular long-distance calls are handled by this entry:
9-W-1-XXX-XXX-XXXX
These calls point to Route 10, which is AT&T LD.
This list can also be used to block outgoing calls, such as:
9-W-976-XXXX
These calls point to Route 0, which is undefined, therefore the call gets blocked.
Calls to 911 are handled a little differently:
9-W-911

It was decided to make it mandatory to dial 9 before dialing 911, due to fat fingers accidentally calling 911. These calls point to Route 100, which is 911.

Your PBX may be setup a little different. In this example, calls don’t route directly to LCR Routes, they route to LCR Profiles first.

[b]Type		LCR Profile Index	Name		LCR Route	Trunk Group[/b]
911		1			911		1		LOCAL PRI
Toll-Free	2			AT&T Local	10		LOCAL PRI
Local		2			AT&T Local	10		LOCAL PRI
Long-Distance	20			AT&T LD	        20		AT&T LD

ADD-LDPLN:LCRPATT,0,9-W-1-844-XXX-XXXX,0&1&2&3&4&5&6&7&8&9&10&11&12&13&14&15,,
2,,1,,,,N;
H500:  AMO LDPLN STARTED
H07: LDP HAS BEEN ADDED

AMO-LDPLN-111       ADMINISTRATION LCR DIALPLAN                                 
ADD COMPLETED;
  <

LoPath
Maintain HiPath 4000 V5 & V6, OpenScape Xpert V4, Xpressions, Contact Center

 

[donb01]

I have noted that the only time I really have to add an area code is when there is a new 8XX series added. Otherwise my normal rule is 9-1-NXX-XXX-XXXX or something like that and it's one size fits all (except for the 900 numbers and other special stuff that's blocked or routed different).

Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA

 

[LoPath]

Yeah, we have separate PRI's for our local and long distance, so we break it out to save on local calls.

LoPath
Maintain HiPath 4000 V5 & V6, OpenScape Xpert V4, Xpressions, Contact Center