Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Nortel HLOC provisioning 1

Status
Not open for further replies.
Nov 18, 2007
37
US
I am implementing a large ESN using HLOC and LOC sites. Nortels NTP's (Not This Page) are rather vague when it come to the basic's. I am a very experienced Nortel tech but this is somewhat new ground. I cannot find where to provision the incoming HLOC data. LOC routing is ok. I know outbound is in LD 90 AC2 HLOC/LOC as in my case but how does that apply to LD 15 net data where HLOC I believe is defined for incoming calls for the site. I am using NRS end point reg. and have all the routing correct but the calls drop to a fast busy site to site. There has to be somewhere outside net data you define the HLOC inbound routing side of the call in the target switch with a DGT, RLB or something so the switch knows what to do with the call once it reaches there. Nothing happens magically.
 
So you need to determine if you are making it to your switch or not, or are failing in the NRS. Look at the inbound DCH to your PBX on the Virtual trunks and see if you are getting a setup message. If you are, then you are at least making it past the NRS.

If you do see a message, make sure you are seeing just the HLOC-XXXX for the called number. Also note the Call Type. This should be Private ESN.

OK, now if you are that far, make sure your HLOC entry in LD 90 has a DMI attached to it that is doing a DEL 3 to dump the HLOC digits from the Called Number.

Now check to make sure that INAC is set for the inbound route. Once you are good here, the last thing you need to look at is the AC2 prompt in NET_DATA. When you get to that prompt, enter LOC there. That tells the call server to use AC2 translations for LOC (Private/ESN) calls coming in on any route that is marked as INAC.

If you find that there is NO DCH SETUP coming in to your PBX, make sure that the originating side is sending the call out as LOC-XXXX and the Call Type is Private/ESN.

If this is good, then you have some issues in your NRS programming. Not going to go there in this post... ;-)

This should give you some pointers on the most common issues found when setting up IP Trunking through an NRS. Hope this points you in the right direction.

(Not This Page.... Funny, I thought I heard them all before. That's a new one for sure!)



911Guru
 
Ah ok so your saying the hloc in ld 90 in my case ac2 will match the net data hloc. So if I build hloc in ld 90 say 41 I would match that in net data so it references it there.
My thinking was ac1/ac2 is outbond routing only. Whats the purpose of multiple hloc entries. It appears you can build more than one. Thanks so much for the reply this is a great help.
 
Follow this link and it will explain NARS/BARS 101



This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.
 
Multiple HLOC entries are valuable in various network builds. Think of this.

HLOC A shares a CDP relationship with HLOC B
HLOC C has links to both for resiliency

Both sites have to be able to translate each others HLOC to CDP across the links between them to provide CDP and number portability in that campus.

Also you may want to do multiple HLOC to allow only on network calling, opposed to network calling with PSTN over flow. So depending on how you dialed would dictate what routing options would be available.

This was done for a company that had to guarantee a way of on network only site to site calling for sensitive calls, but still provide PSTN overflow for normal traffic.

Those are a few reasons for multiple HLOC.


911Guru
 
I see now thanks. I dont think NRS is the issue I have a site in Edinburg Scottland works fine. I didnt get a chance to talk to the tech after the cut. Thought I had it figured out but its the simple things that kick my b*** sometimes. If all I have to do is match the HLOC in 90 to my net_data in 15 Im good to go thanks again for your help.
 
No, I think you may be confused. Not the HLOC prompt in NET_DATA, but the AC2 prompt.

It probably looks like this in your system:

Code:
REQ: prt
TYPE: net
TYPE NET_DATA
CUST 0

TYPE NET_DATA
CUST 00 
OPT RTD 
AC1 INTL NPA SPN NXX LOC 
AC2 
FNP YES

and it should look like this:

Code:
REQ: prt
TYPE: net
TYPE NET_DATA
CUST 0

TYPE NET_DATA
CUST 00 
OPT RTD 
AC1 INTL NPA SPN NXX  
[COLOR=red][b]AC2 LOC[/b][/color]
FNP YES

911Guru
 
Yep I have that already setup. I guess what I am poorly trying so say is in the net_data of ld 15 the HLOC entry there represents that ID (HLOC) for that site if you will? So if you see HLOC 41 in ld 15. You should see the same entry in LD 90 of AC2 in my case. In LD 90 is HLOC 41 where you add all the rlb and dmi to represent what the switch needs to set the call up for this site? This is where Im getting confused. Thanks for the patience.
 
Thanks again for your help. I had everything good to go. I was getting hung up on where you put the hloc. Its in ld 15 under the net data and again in ld 90. The problem was had the hloc added in ld 15 buy itself and never built the table in ld 90 DUHH. Trust me it aint gonna work unless you do that. It was a slam dunk after that. I didnt realize ac2 would translate inbound either. Learn something new every day. Ive told several tech about this site its great. Count on me to help where I can.
 
The HLOC in LD 15 is so if you dial your own loc and a number, LD 15 see's it's your own loc and just dials the EXT at your site.


This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.


 
I will respectfully disagree with that Ace. If you dial AC2+HLOC-XXXX NARS/BARS is dealing with the deletion of the HLOC just like incoming calls on a trunk. Also, since a system can have multiple HLOCs, that cant be correct since it is a single entry. May have something to do with the PINX DN??

Like I said, I have never provisioned that before, although I'm sure it has *some* function.

911Guru
 
When I worked for Nortel, we had a 70 site network and used 7 digit dialing 3 for LOC and 4 for EXT, if I dialed my own loc, it just dialed the EXT number.


This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.


 
Intresting. When I tested a local site call last week and included the ESN your correct it strips HLOC and keeps the call internal and displays 4 digits. However with it in Ld 15 it did not work until I added the ld 90 HLOC table with the dmi so the system knew what to do. Ill be glad to strip the HLOC in Ld 15 and share the results its not user deployed until Wed. Im curious what its for also.
 
You know what I just had a thought. Could it be for multi cutomer HLOC deployment ?
 
We did have multi Customer on all switch's.


This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.


 
Multi customer would have nothing to do with it. Each customer on the PBX is it's own partition and only shares LD 17 values.

Like I said, the local dialing of your own HLOC and terminating on the 4 digit extension capability is 100% a NARS/BARS function.

911Guru
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top