HiPath 4000 critical upgrade help

Unfortunately it will take much work to resolve this situation, because you have 600 station numbers to manipulate!!! Here's an example of the problem: if there is an entry in WABE for station # 123, it is not possible to add a new entry for station # 1234, because the system will not allow "overlapping" digits. You must first delete or re-number the actual station 123 (AMO SBCSU), then delete the AMO WABE entry. You do NOT want to delete all the station numbers (SBCSU), because There are other AMOs involved - KCSU, SDAT, etc.

Unless you are very proficient with the HiPath 4000 AMOs, do NOT delete the SBCSU stations!!! In my opinion, re-numbering the station numbers will be the best solution.

The first task will be to re-number all the current 3-digit stations so that 1xx thru 6xx can be deleted from AMO WABE. Then you can re-build WABE using new 4-digit station numbers. To accomplish this goal, you will need to use "temporary" station numbers.

First, we need to select a station number such as "100" so that we can "clear a path" to a new numbering scheme in AMO WABE. Perform a REG-SBCSU on station number 100, then delete it (DEL-SBCSU:100,ALL. Then you can delete station number "100" from AMO WABE. Be sure to delete only station number 100 from WABE!!!! Now that station number 100 is deleted, you can add new WABE entries "100xxx" with a DAR=STN, where "xxx" are your 600 station numbers 1xx thru 6xx. When that is done, now start with your first station number, for example "101", and perform a CHA-SBCSU:101 <enter>. After pressing the ENTER key, the next parameter will be "NEWNO", which will allow you to re-number station 101 to any new un-used station number that exists in WABE with a DAR=STN (your new "100xxx" numbers in WABE). The actual AMO will be: CHA-SBCSU:101,100101; Immediately your station number "101" will become "100101". Perform this same procedure on all six-hundred stations: 102 >> 100102, 103 >> 100103, etc.

When done, all of SBCSU records for "1xx" thru "6xx" will have been re-numbered, so you can now delete the WABE > DAR=STN entries for all of those stations. After deleting all these WABE entries, now you can begin to re-build WABE, using whatever numbering scheme you want to use, as long as this new scheme does not begin with "100x", as that would conflict with all your "100xxx" WABE entries. For example, use 3xxx in WABE, so you'll perform ADD-WABE and create station numbers 3xxx, all with a DAR=STN. When done, now re-number all the stations AGAIN. For example, station number "100101" will now become "3101" (CHA-SBCSU:100101,3101.

You'll need to do some planning in advance, as my numbers are merely suggestions. Will these changes interfere with your DID/DDI incoming calls? Only perform these AMO changes during off-hours, so that no one is negatively impacted. Also, make sure you perform a HiPath Backup and EXE-UPDAT:BP,ALL; before starting this procedure. In the event that things get out of hand, you will be able to recover your previous database.

Don't forget to manually add the SBCSU record for station number "100" (that we deleted to start the entire process).

I highly suggest trying this on a SMALL basis first, perhaps 5 stations, so that you will develop a "feel" for the process before tacking the entire job.

Good luck.

amazing ..
I don't know how I can thank you it's seem a long term solution but very supportive thanks " Iamnothere "

But tell me how I configure the XXXX digits in my dial plan LDPLN ?

My solution would be to add a trailing zero to all of the extension numbers. With that solution you can also still take advantage of the existing DID numbers because you can set up a digit manipulation rule to add the zero onto the digits received by the phone company. I had a site once that we annexed into our network which had 4-digit extension numbers the same as our main headquarters - how to fit them in the dial plan.... Their numbers were 24xx and I wanted to change the numbers to 44xx for that site. I had the phone company just send the last 3 digits and added in the 4 at the beginning - all set to go. Five years later I actually got my hands on the 44xx block as part of a big renumbering project and then everything matched again and we were good to go!

In this case all you need to do is add-wabe, dgts, 1000&&6999, dar=STN

Then pull up each station number and add a zero to the end.

Then modify the GDTR rule to append the zero to the incoming digits.

Extensions are now 1230, 1240, 1250, 1260, etc..... Sure it spaces them out and wastes numbers, but it is a quick solution and you might be able to get some 4-digit DID blocks later on and incorporate the rest of the numbers - you would just have to modify a GDTR rule to accommodate the 4-digit block of numbers apart from the rest.

Just my 2 cents worth

Nice idea Donb01 about the new range of station numbers. But just as an FYI: "1000" cannot be added to WABE if "100" already exists. WABE must first be cleared of the potential "overlapping" digits, which is what makes this scenario challenging!

Regarding LDPLN: the "L" in LDPLN stands for "LCR" (Least Cost Routing). If your stations are all local (internal stations within a single-node of HiPath 4000), then AMO LDPLN is not used, as in-house station to station calling does not use LCR.

LDPLN is needed if perhaps all or some of your stations are REMOTE (in other nodes of HiPath 4000), and must be reached via trunk. In this case, in the USA we configure these stations by creating a RICHT entry such as "101" as type=CD, and build a partner LDAT entry "101" as type=NWLCR (Networked LCR). We refer to this method as "Closed Dialing". We then assign that "101" route number to the remote station in AMO WABE as the DESTNO. In WABE, it is easy to distinguish between the Local and Remote stations - those station entries with a DESTNO (such as "101") are Remote stations. They require access to a trunk group to reach the destination PBX.

In Europe, typically customers do not use this Closed Dialing method, but rather they use Open Dialing, which means that an access code or "exit" code is first dialed. For example, to reach station number 444 at a remote site, the caller dials 8-444. The leading 8 is configured in WABE with DAR=TIE, which starts the LCR process, and therefore there must be a corresponding digit pattern in AMO LDPLN such as 8-xxx.

So "veilside", you will need to respond before I can continue. Are all of your station numbers LOCAL, or are they all REMOTE, or do you have a mixture?

Yeah... Now that I think about it I guess I missed the point there

Then I thought about prepending a digit, hitting save, fixing WABE - but it still won't work because 101 kills 1010 and 102 kills 1020 etc, etc.... You're right... That will be a FUN task to renumber it!

Thanks all for your instant replay and provided soulotions.

Iamnothere, all numbers are local but connected to remote other sites ( our branches ) you can see my simple network diagram below ..



Link 2

Thanks all ..

When dialing between sites, do you simply dial the station number e.g. 152, or do you dial an access/exit code before the station number e.g. 8-152?

Perform DIS-LDPLN:LDP,0; and examine all of your dialing patterns for inter-site dialing.

At the 4K site where stations 150-199 & 600-699 reside, in LDPLN there should be an entry defining your dialing scheme to reach stations 200-499 at the other 4K site. If you do NOT dial an access/exit code, then I am expecting to see entries in LDPLN such as "2" or "2xx". There will probably also be entries for the 3xx and 4xx station numbers. If, however, you DO dial an access/exit code prior to the station numbers such as "8", then I am expecting to see an entry like "8-2xx".

LDPLN is very flexible, meaning that there are MANY ways that your dialing schemes could have been designed. The members of this forum need to see the entries before proceeding with suggestions.

My network is a hub and spoke concept, where I have 6 sites around a central 7th one. All of my remote sites (only 1 is a 4000 right now) have their local stations defined in WABE, and all other extension ranges are in WABE and assigned to the CorNet route back to the main site.

The main site knows what to do with all of the numbers in the entire dial plan that are currently defined. They are either local or they are assigned the CorNet route of one of the remote sites. If one remote site makes a call to one of the other ones the call first goes to the main site, which knows where to send it from there. In the event of a cornet failure the users simply dial the full (currently) 7-digit local number for the DID.

I only use LDPLN for outside call routing and trapping special circumstances. For example, we tell our staff that using the 4-digit extension numbers to dial remote site saves money because we don't pay per call, but some of them still insist on dialing the 7-digit main number for the site in question. I simply made an LDPLN entry for that specific phone number and told it to convert it to 4-digits and send it out across the private network - the users have no clue, and have the satisfaction of thinking they are pulling one over on me. I also used it a few years ago when our company was still using dial-up internet. I programmed in all of the service numbers for the local internet providers and set them up to route out the copper trunks (at 12 cents per call) vs the ISDN PRI circuits at a small cost per minute. If some Doctor dialed into the internet and stayed connected all day we only paid for that one phone call instead of several dollars in per-minute charges.

Well anyway.... )

If this was me, it's a job for the weekend.

I'd do a regen, edit the regen on your pc to reflect the new numbers including ziel dss/name keys, pickup groups, hunt groups, key systems etc. This can be done at anytime.

At the weekend, backup to mo/flash, blank the database with dbc and gendb your edited file.

Someone with 4K experience will have it done in a day, if you don't really know what you're doing with the AMOs it's quite a job.

Moriendi, I am already trying to do it exactly, but I want to explain some issues regarding my diagram i was sent before I am connected to cisco call manager that manage all our branches that connected by VPN over internet to transfer both Voice and data transmission .. other sites have a four digit extantions and when we dial from our site we need to add to digits as a trunk to dial outside our branch Ex. 99-4321 and when other side call us he do the same XX-321 so I need to reconfigure my dial plan regarding my upgrade ?

From what you've said, the answer is no, you don't need to reconfigure your LCR.

Example, there are two HP4K sites.

Site A has extensions 2000-2100
Site B has extensions 3000-3100

There are two ways to dial from site A to site B.

First way is "closed numbered". User at site A dials just the extension digits eg "3000". LCR routes the call to site B.

Second way is "open numbered". User at site A has to dial a prefix code to reach site B, eg "102-3000". The node code for site B is 102. So site A sends any digit string that starts 102 to site B. Site B will strip off the 102 as it's own node code (if the '102' was sent, it doesn't have to be) and look at the rest of the digits.

You can see from the second way, that it doesn't matter if site B uses 3, 4 or 5 digit extensions, anything that starts 102 is routed to site B.

Worth mentioning though is that in the LDPLN it could be specified as 102-Z, 102-X, 102-XXXX etc....so moving from 4 digit extensions to 3 digit extensions could cause a problem *for other 4K sites dialling you*, it depends on their routing - I don't think this affects you here, and in anycase you are going from 3 digits to 4 digits...

It sounds like you have an open numbered network, and you should be fine. Example, the other switch that dials XX-321 to reach you...well they'll just need to dial (eg) XX-3210 instead - if your switch gets those digits - the phone will ring. Can't comment on the routing for the other switch though - ie whether it will need any changes, you'll have to ask them - but you shouldn't need to do anything to yours.