mitel to meridian interconnectivity 4

[tellyteck1]

Hello, we are getting a mitel 3300 and I need to interconnect it to the meridian. Does anyone know what hardware is required including the cards on the meridian? I have heard I need an E and M card. Any help is greatly appreciated. Thank you in advance. AJK

 

[mitelman]

Wouldn't you connect over PRI sets as QSIG or a T1? I would do that rather than E&M. This would require an NSU or Dual Framer module on the 3300. ON the Meridian I have no idea.

 

[MitelInMyBlood]

To use PRI/QSIG his Meridian would need the QSIG feature which in the past has been a fairly expensive option from Nortel. I don't think he can use NI2 either because the Meridian won't let you tandem off of it to go out 9th level to the LEC. Without throwing a lot of money at the M1 the E&M may be the only way.

 

[tellyteck1]

Thank you both for helping out. I am hearing mixed messages from a few people; some say QSIG others say E and M. The biggest problem I have is I do not know where to connect to on the Meridian. I do not have a spare T1 card. We do have the QSIG. Have either of you seen where the cable plugs into on the meridian? Thanks very much AJK

 

[deanmulley]

you could try the ci-tel link controler(sorry the name escapes me) this will support a number of nortel phones direct from the icp if this is what you are looking for or is it a networking set up you are after?

 

[tellyteck1]

Hi, we have purchased the 3300 and want to interconnect it to the meridian. The main question I have is the physical requirements needed for the meridian. For example do I need to free up a TMDI card (trunk card) and put a rollover cable between the two. The purpose of interconnecting the two is have remote agents off of the mitel (voip) be fed through and ACD information on the caller. Thank you for any help;AJK

 

[jneiberger]

This doesn't answer your question but I thought I'd pass along some very important information that we just discovered last week.

If you choose the QSIG method, there are some hidden commands on the Nortel PBX that you'll want to turn on. By default, a call transfer will not trigger a QSIG Path Replacement proposal by the Meridian software. Depending on your network topology, this might leave up a lot of redundant call paths resulting in additional latency and multiple encodings.

The solution is an undocumented prompt in LD 17. There are two, actually: CTR1 and CTR2. They turn on path replacement messages for call transfers. Pick one and configure it on all of your Nortel PBXs that have QSIG connections on them. Don't try to mix them, though. Pick one of them and use it consistently.

John

 

[jneiberger]

Sorry, I forgot to mention that the CTR1 and CTR2 options are under the PR_TRIGS prompt in LD 17.

Forgive me, I am not a PBX guy and I'm especially not a Nortel guy.

John

 

[tellyteck1]

Thank you that does help. I am still at a loss though with the connectivity. I am thinking I need to free up a TGMI (trunk group card)and make a tie line between that and the NSU. Logically, I should be able to terminate each to a dax and then use a roll over cable. Does anyone have a suggestion. Thanks all for helping. AJK

 

[RainierTBeer]

I can only suggest that you call Bell West and have their technicians assist. They truely are the best.