Networkli.ng 2 Norstars

[salo0920]

Hi All,

I have 2 Norstars networked together (private network)
with a T1 span using all 24 channels as E&M emulation.

Problem is that when a call comes in on an outside trunk (Real PRI to telco) on System A and the call is for an extension on System B, the call gets routed to System B properly (destination code to target line)but I loose the CallerID information through the span.

ITAS says that I need a PRI span in order to pass the CallerID info and that an E&M trunk will not pass callerID data.

Before I sink another $500 into this test project (purchase a PRI keycode)I was wondering if any of you "experienced" users had some feedback for me or words of advice.

Thanks,
Harold

 

[Roldan]

I don't think you'll be able to pass the caller ID info across, but I could be wrong. However, if you have a PRI on the system now you won't need to purchase keycodes for another one. So if you do decide to add another PRI you're already setup for it with your original keycode.

 

[hawkflorida]

If you networking two MICS units and are using 6.0 and PRI you will also need the MCDN(Advanced Private Networking) key code also in each unit too.

2 MICS 6.0
2 Pri Keycodes
2 MCDN APN Keycodes


Also, can do CAA and CVM using one NAM 3G with 4.1 software.

Consulting -
"If You're Not A Part Of The Solution, There's Good Money To Be Made In Prolonging The Problem."

 

[salo0920]

Roldan,

I think that I wont need another PRI keycode for System A (Where the PRI to telco loop is) but I cant see how to get around buying one for System B if I am going to setup the span as a PRI span. Any suggestions would be appreciated.

 

[salo0920]

Redhawk,

Can you explain to me about MCDN? Is this necessary? A requirement? What features will it provide me with? Actually, the one thing I DONT want is centralized AA. My whole point in adding System B is that I need more different auto attendants ( I have many separate companies sharing my switch ( I provide a Centrex like service in my office building) and each company wants their own AA and CCR) Would you have a solution that would allow more than 4 AA's on a NAM? OR more NAMS than 1 on a switch????

I am really stuck on this one. The only solution I can come up with is to network 2 MICS, each with its own NAM. At least then I can have 8 AA's.

The 1 real PRI on System A will provide enough inbound channels for 120 + users in my case.

Thanks,
Harold

 

[Roldan]

Salo,
You are right, if system B does not already have a PRI keycode and you are going to add a PRI you will need one.

 

[hawkflorida]

It sounded like you were talking about a private network "point to point". If you are then you need SL-1 protocol. I wasn't sure what you had in the sytems. So what I was giving you was the minimum for two private networked MICS systems using the SL-1 protocol. Not sure what your software is but on MICS 5.0 and above you need the MCDN Keycodes.

MCDN is signaling that is used to privately network a Norstar system to a Meridian 1 PBX, or other Norstar systems. If you don't have the key you can't privately network the sytems over PRI. The SL-1 choice isn't there.
Consulting -
"If You're Not A Part Of The Solution, There's Good Money To Be Made In Prolonging The Problem."

 

[salo0920]

Redhawk,

Are you saying that you cannot use a PRI to connect 2 private networks without SL-1 and that SL-1 requires MCDN keycodes and that these are only available in DR5 or later?

If so, how did you network 2 MICS before DR5?

If the answer is T1 with E&M protocol then thats where I already am but I cant get the CallerID to pass through. Is that about right?

 

[hawkflorida]

For point to point PRI you need the MCDN/APN key for SL-1 networking on >5.0 software. Maybe some Guru/Genie out there can tell us otherwise... but I dont' think so.


For PRI the SL-1 protocol was available without a MCDN key before 5.0. But it wasn't offering APN either!
Consulting -
"If You're Not A Part Of The Solution, There's Good Money To Be Made In Prolonging The Problem."

 

[hawkflorida]

I will try to run our test units with NI-2 back to back but I don't think it will work.

Please note.... if you are running MICS 5.0 now and let's say you decided to downgrade to 4.1. You will probably reset your System ID on the KSU making your PRI code worthless. Just a heads up.
Consulting -
"If You're Not A Part Of The Solution, There's Good Money To Be Made In Prolonging The Problem."

 

[samh30]

If your software is below 5.0 ,then your only choice is T1 in between (E&M) and it will not pass the caller ID informations.If you have 5.0 then you can connect one MICS 5.0 and any option system with PRI in between and you can pass caller ID then,but if you want two MICS then you will need like previous posts mentioned,MICS 6.0 in each location ,PRI card and PRI enabler in each location and MCDN key code to enable the networking between the two locations.

 

[salo0920]

Thanks Redhawk,

I will look forward to hearing your test results. Specifically, my System B is a 4.1XC and my System A is a 5.0. I presently have a PRI key for System A but NOT for system B. As I said, my only interest is connecting the 2 systems together so that they can share the Incoming PRI traffic from the telco connected to System A, but I need the CallerID passed on to System B when DID calls are routed over to it.

Thanks,
Harold