Location Codes - In and Out - PBX Info :: Your Free PBX, PABX and Telephone Information Resource

ciscoguy · 07-09-2003, 07:58 PM

I am working on integrating several PBXes together on a large network (using Cisco VoIP gear). I have several things working in our lab, and can even light the message waiting light across PBXes.

I'm using QSIG interfaces between the Meridians with several RCAPs that let me do the various things I need (name display, MWI, etc.), and I believe everything on the VoIP side is as I need it. Now I have some basic questions on the Nortel side as I'm much newer to Nortel...

We want to assign location codes to each location. To place a call, a user dials an 8, followed by the 3-digit location code, followed by the 4-digit extension of the user. We have this mostly working - we add LOC codes for each location we have, added an AC2 of 8, and from a PBX we can dial the full string and ring a phone on the other PBX. However, to get this working I had to only deliver a 4-digit DNIS to the remote end (I forced the Cisco at the far end to strip the location code)

My first question is how can I get the remote PBX to take the full number, WITH location code? Even after setting the HLOC to the local PBXes location code, it won't take the dialed number. (I get an ISDN unallocated number message)

The reason just delivering the 4-digit DNIS to the remote end isn't acceptable is voicemail - we want the full string to be passed so that we can service users from multiple PBXes out of a single voicemail system. Because the 4-digit extensions have conflicts, we need to use location codes to allow unique numbers to be sent to CallPilot.

The PBXes in question are Option 11C's, 25.40B, using ISGF interfaces to Cisco gateways (which use a gatekeeper). There will eventually be other Meridians and probably other vendor PBXes as well, but I'm mostly concerned about the Meridian part for now.

The message waiting light now only works if I use 4-digit extensions end-to-end (completely ignore the location code), which is only satisfying in the lab where I only have two PBXes with non-conflicting ranges to worry about...

Thanks in advance for your help.

rhack · 07-09-2003, 08:21 PM

I think there are a couple of ways to do this. If you have a TIE route, you may want to try setting INAC (insert Access Code) to yes. You may have to have the HLOC defined in AC1 for this.

or

Build a LSC (Local Steering code) in LD 87 for your HLOC code. THe LSC will let you strip the 3 lead digits and terminate to the 4 digit number.

**Fletch** · 07-09-2003, 10:05 PM

Rhack is close, here is what you need.

Make sure the Cisco is passing Number Plan PRIVATE Type of Number ESN
(The TON bits are the same for a PUBLIC NATIONAL call)
You need to have INAC set up on the Routes.
Don't pass or insert AC2 (

anywhere in the dialstring
Under NET_DATA there is an AC2 prompt there, set the value to LOC
build a HLOC and apply a DMI table to strip off the LOC digits

Check you work locally on the switch. You should be able to dial AC2-HLOC-XXXX and have the call terminate on the same switch. If this works, you are ready top pass calls across the network.

Turn on DCH monitoring for the Q.Sig PRI
Place a call and capture the outbound DCH message to the Cisco, as well as the Inbound DCH messages at the far end.

If the call wont work, paste the data here and we can have a look. Sounds like you are the right track, just need a bit of guidance to the finish line.

ciscoguy · 07-15-2003, 05:00 PM

Okay, I'm actually in the lab now trying to work this out. The calls are all going through as Private/National. We turned on INAC on the routes, I can't really see what effect that had however. I also don't see what the HLOC accomplishes, though I think I know what it's supposed to accomplish (recognition of a local number when AC2+LOC is dialed, or comes in on a trunk, right?)

One thing that I'm confused about right off is if I strip the LOC digits with a DMI, how will my voice gateway know where to route the call? Won't this strip the LOC for any AC2+LOC number I dial, or am I using the DMI incorrectly? Currently my only DMI strips nothing and inserts an 8, if I strip the LOC then the gateway doesn't get the LOC at all, which means it won't know how to route it.

Just so I have things straight in my head, how should the calls come in to the PBX and leave the PBX? Here's what I'm expecting now:

PBX -> Gateway - PBX sends "8LOCXXXX"
Gateway -> PBX - Gateway sends "8LOCXXXX"

I have the PBX-> Gateway working the way I expect because I have a DMI to insert an 8 and it leaves the LOC alone. It doesn't recognize a number as "local" if the LOC=HLOC however, I don't know if this is supposed to work or not.

The Gateway->PBX I thus far have had to strip the 8+LOC at the gateway and just deliver the 4-digit extension, I have yet to figure out how to get this working.

Also, I'd like the callING number to reflect the full number with LOC (and preferrably the access code as well), but I'm not sure what the best way is to make this happen. Now the calling number is always just the person's 4-digit extension, which will cause problems with our centralized voicemail system (and users won't be too happy either).

I'll be working on this again on Thursday, if we're still having trouble I'll be sure to post the relevant portions of the Meridian config since we seem to be missing some things.

Thanks very much for your help, I apologize if I'm asking stupid questions or questions that don't make sense, I'm pretty new to Meridian (and some PBX concepts) but trying desperately to understand... as you can guess I'm coming from the data side. Our Meridian person I'm working with has never worked with LOC codes before, and is used to small phone networks with MCDN trunks, so this is a good learning experience for both of us.

Twisted · 07-16-2003, 05:55 AM

we have a simular setup ...beiong multible locations using one voice mail with conflicting digits. we chose to use 7 digits mailboxes..There is a certain configuration of the mailbox. a alias of a 7 digit number ( if ytour voice mail has that ability) LOC-XXXX might work.

ciscoguy · 07-17-2003, 12:36 PM

Anyone have insight on the location code/dial string handling? What configs do I need for the location code to be recognized inbound on the PBX, and do I send the AC2 or not?

Thanks all for your help.

**Fletch** · 07-17-2003, 09:12 PM

The destination PBX is built with a HLOC.
The HLOC has a DMI that locally strips the LOC off the digit string
You DO NOT send the 8 if you use INAC

Calls throught the netowrk pass as LOC-xxxx PVT/NATL or PVT/ESN depending on who decodes it, the bit string for ESN is the same as Natl.

Doing this will show H555-1212 in the far end (LOC-XXXX)

ciscoguy · 07-23-2003, 02:56 PM

Okay, I'm much further along now... location codes seem to be working. If a user on a system calls his own location code, the call never leaves the PBX. Using the correct location code, the call routes across properly. However, the calling number is still the unqualified, 4-digit extension. How do I fix this? I just want the system to insert its HLOC on outbound numbers.

Thanks all for your help (especially you Fletch), I've made a lot of progress with your guidance!

**Fletch** · 07-25-2003, 11:34 PM

You need to set up your CLID Tables in LD 15 under NET_DATA. Fill in the fields marked HLOC and you will send the call with HLOC-XXXX for AC2 calls. The default CLID table is '0'. Each DN on a phone is assigned to a CLID table you define. The PDN of the phone should be built as:

KEY 00 SCR 6150 0 <----That last 0 tells the PBX to use CLID table 0
KEY 01 SCR 286150 D <----The 'D' says to use the default CLID table for this (CLID 0)

This 'D' is important for 2 reasons:

1.) On an ESN call it will send HLOC-6150 for calls made from key 1, if the 'D' was left as '0', the switch would use CLID 0 and send it as HLOC-286150, not a valid number.

BTW-I use 6 or 7 digit secondary DN's, ACOD's, etc to save on number waste inthe switch.

2.) Most importantly, on 911 calls and PSTN calls will be sent correctly. In the above example, you may not own NPA-NXX-2861 (the 50 would be trimmed at the CO), and will come up witha bogus name to the person called, or worse the E911 PSAP.

You're almost there.

[Edited on 26/7/2003 by Fletch]

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)