Networking 2 Norstars with Centralized voicemail

[808user]

We are setting up 2 Norstars MICS 7.1 with Centralized
voicemail (Callpilot). Each switch has their own copper
PSTN trunks and are tied together with PRI-SL1/MCDN.
Switch A (w/Callpilot) will have DNs 2XX and 3XX while
Switch B will have DNs 4XX and 5XX. I was told that
all I would need to do is create destination codes and
point it to the PRI route for each switch. If I'm using
a CDP dialing plan, the system will only allow me to
program one PrivNet ID (PNI), which is the leading
digit for the stations. Am I missing something? How
can Switch B call station numbers 2XX and 3XX in switch A
using CDP?

 

[CBasicAsslember]

The short answer is you can't, use 4 digit DN's and save yourself a whole lot of headaches.

 

[hawks]

The PNI does not have to be the starting digit you can do it the way you are going. don't forget about the target lines in each system to rout the inbound calls.

 

[808user]

By reading the Norstar documentations you would think that
the PNI is the leading digit, but if you say it doesn't have
to be, then the PNI for Norstars is similar for the Meridian
PBX. In any case, we will lab the switches and try all the
options and let you folks to know what happens. Thank you
all for the replys.

 

[bwtc]

Perhaps I'm misunderstanding something, but is it possible that the "B" channels, or hunt groups, at each site have a leading digit that is conflicting with the dest code being able to be setup?

Switch A (w/Callpilot) will have DNs 2XX and 3XX while
Switch B will have DNs 4XX and 5XX.

If at switch A you try dialing 4 (or 5), do you get an "Invalid number" message, or is it waiting for the next digit? If at switch B you try dialing 2 (or 3), do you get an "Invalid number" message?

If you do not get an "Invalid number" message, something is conflicting with allowing you to setup the Dest code, and you'll need to renumber whatever is conflicting.

By reading the Norstar documentations you would think that the PNI is the leading digit, but if you say it doesn't haveto be

Because of the range of DID's that we received, we are using the first 2 or 3 numbers (depending on what the first 2 are) to determine where the call will route (we are not using centralized vm). So it doesn't matter if you use more than 1 digit.

The short answer is you can't, use 4 digit DN's and save yourself a whole lot of headaches.

CBasicAssembler, I couldn't agree with you more!

 

[CBasicAsslember]

Remember that each port will require 2 DN's. If my assumption that you have over 100 ports per site then your going to spend a lot of time renumbering.

 

[hawks]

Private Network Identifier (PNI)
This is an identifying digit or set of digits assigned to each system in a private network with a Meridian system. These codes are provided by the Meridian system administrator when the node is brought on to the network.

Good luck and let us know how it goes.

 

[CBasicAsslember]

Private Network Identifier (PNI)
This is an identifying digit or set of digits assigned to each system in a private network with a Meridian system.

In this case the private network does not involve a Meridian, it is 2 Norstars. When the network is exclusively Norstar's, Nortel uses the terminology "steering code". IOW, under these circumstances PrivNetID: = steering code. Nortel states:

Coordinated Dialing Plan: (CDP)
This dialing plan uses a steering code to identify each node in a private network. This one-digit code becomes part of the set DN number rather than a separate code. In this way, system A might have codes in range 2100 to 2999, whereas system B might have codes in range 3100 to 3999.

Under programming "steering codes":

Note: If you are specifying a private network that has been created using SL-1 (MCDN) lines, the private network id is part of the set DN (for instance, system A might have DNs from 3201 to 3299, whereas system B might have a DN range starting with 2, such as 2201 to 2299). However, you must enter a number, so enter the number
that appears first on the set DNs. This code is defined by the network coordinator and must be unique to each system.

It appears to me that Meridian/ no Meridian are two different animals with the "no Meridian" being somewhat more restrictive. The more powerful Meridian lends more flexibility to the network (it acts as the administrator) that is not available in the Norstar only configuration. If you don't set it up as stated by Nortel I don't believe centralized voice mail will work as well as the assorted features. At this point I will stick with my original answer.

 

[hawks]

I stand corrected according to the books sorry for the miss information. But I have installed them with Centralized voicemail and the PNI for each system not matching the DN. Let us know how you make out in the test lab.

 

[808user]

We setup the two Norstars with a PRI TIE using a modified patch cord (that's another story) and we were able to call across to the other switch with PNIs that don't match our station DNs leading digit, which defies all logic or Nortel documentations. We haven't finished programming/testing yet so I'll let you know the final results.

By the way, the patch cord setup we used was wiring:
pins 1 of plug A to pin 5 of plug B; pin 2 of plug A to pin 4 of plug B (and vice versa).

 

[CBasicAsslember]

...we were able to call across to the other switch with PNIs that don't match our station DNs leading digit, which defies all logic or Nortel documentations.

Not really. The advantage of a private network is the ability to use features accross the network. Set up a voice mail box for one of the sets that is not on the same switch as the call pilot. Leave a message in that mailbox. If you have it set up correctly the message waiting lamp will light on the set.

 

[808user]

Everything seems to be working except stations on the remote switch are getting a generic greeting when calling the callpilot on the main switch over the PRI-Sl1 tie (callpilot doesn't recognize the remote station).

 

[hawks]

Are the lines set for external messaging?

 

[CBasicAsslember]

Since you were going to try different options we kind of need to know how you configured it.

 

[808user]

CBasicAsslember": I have PRI-A programmed as Route 1 with destination code '5' to call the remote switch. Target line on the remote switch was built with the correct received digits. On the remote switch, I built the same configuration except destination code is set to '2' to reach the main switch. Dialing Plan is configured as CDP on both switches with PrivNet ID set for '1' on the main switch and '2' remote switch. On the hardware settings for the PRI-A, the main and remote sites are programmed with the PrivNet ID of the other switch's ID. All network settings work fine without the voicemail...... but since "hawks" mentioned "external messaging", I don't recall seeing the "Extl Msg" prompt in the set's "Telco" settings. I'll have to go back to the lab and double check it. If it's not present in the database, how can I confirm this? I'm more familiar with Meridian programming where the keycodes will activate the "PKG". Is there something similar in the Norstar?

 

[hawks]

Look at the 6.1 Installer Guide Page 159. Also did you turn everything on in the Call Pilot such as Redirect DN, Ect...

 

[CBasicAsslember]

808user,

See my post 16 Jan 07 19:56. Specifically the 3rd quote. The PrivNet ID for the switch with DN's starting with 5 should be 5, the switch with DN's starting with 2 should be 2. I am assuming that you are set up with 4 digit extensions. Also, the protocol on the PRI is SL-1.

 

[hawks]

Do a search for "Centralized VoiceMail" under the FAQ section there are a couple there.

 

[808user]

Hawks",

Yeah, we forgot to configure the callpilot. Now it picks up the calls correctly. The callpilot is asking the remote station to initialize the mailbox. Now I gotta read up on how to program "remote feature codes" because I won't be able to use "feature 981". I'll have to dial the remote access code then dial "* 981" instead. Thanks for steering me in the right direction.

"CBasicAsslember",
The PNIs 1 and 2 for the host and remote switches works the same as when I program it as PNIs 2 and 5. I'll leave it as PNIs 2 and 5 to keep it in line with Nortel documentations and to avoid confusions later. Thanks everybody for the support and advise.

 

[CBasicAsslember]

I'll have to dial the remote access code then dial "* 981" instead.

I believe you can just dial the Call Pilot extension number to access the voice mail. I know for certain that will work at the local switch.