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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Networking Legend to Definity G3 Help Please!

Status
Not open for further replies.

rezinz28

Technical User
Sep 4, 2002
93
US
I have 2 Definity G3's networked together via cisco routers using E & M wink start. I want to bring in a Legend from another site and already have the DS1 card and cisco equipment. I also want to change the E & M wink to ISDN PRI. I need some big help with answers. Will it work to network the legend to a cisco router via ISDN? IF so what ISDN PRI signal do I need to use (5ess, 4ess, QSIG so on).
Help Please,
Steve
 
I haven't tied together a Definity G3 and a Merlin Legend so I cannot speak from experience. But looking through my Legend 6.1 Network Reference book I see the Definity ECS and Definity ProLogix Solutions mentioned as being compatible with the Merlin Legend. The Legend should be at least r6.1 to offer the best features. Personally if you DO have to upgrade the Legend I would up it to r7.0 v14.2 since that's the latest and greatest.

According to a disclaimer in the manual, a Definity and a Merlin CANNOT share a Centralized Voice Messaging system. You CAN have UDP so that all extensions appear to be pseudo-internal, ARS call routing patterns between locations, ISDN dial plans, UDP transfers, and all of the other slick features of tandem PRI. If you have a choice I would always go with PRI rather than E&M tie lines for networking phone systems.

For the Switch Type, the Merlin must be programmed to match what is defined in the Definity's Interface field. By default I believe the Definity Interface is setup as User. Then the Merlin would have to be setup as Legend-PBX. If the Definity Interface is setup as Network, then the Merlin would have to be setup as Legend-Ntwk.

For the Switch ID, the Merlin must be programmed with a unique ID number in the 41-50 range if the other end is more than 200 miles away. If the other end is less than 200 miles away, then the Merlin Switch ID must be a unique number in the 51-60 range.

The PRI signaling is internal, so it's handled differently from ordering a certain configuration from telco for PSTN dial tone. The Merlin will show the Network Service as being Electronic Tandem Network (Legend UDP). It WON'T show up as being 5ESS, DMS-100, etc. like a traditional circuit would. As for the Definity I'd check their docs on how this is defined for that end in terms of defining the Network Service type as being internal.

Check Avaya's website for the manuals if you need more details on the Merlin. The Network Reference should be out there. Hope this helps!
 
Here is my complete setup.
Definity G3 to Cisco Router (Multiflex trunk card)
Merlin Legend to Cisco Router (Multiflex Trunk Card)
I have configured the cisco router for isdn and would like to use QSIG if possible but don't know if the Legend is capable. If you have an insight on how to accomplish this thank you.

Steve
 
Here is the information as taken from the Merlin Legend System Programming Guide. The Network Service options for PRI in Merlin are the following:

1) AT&T
2) 5ESS
3) MCI
4) DMS-100
5) Legend UDP (Eletronic Tandem Networking)
6) Miscellaneous

As you can see, QSIG isn't a pre-defined option. You would have to go into the Miscellaneous option and then enter in the 5-digit binary number corresponding with the Network Facilities Information Element of the ISDN signaling protocol for QSIG. I have no idea what that number is.

This setup won't accomplish true UDP routing so that both switches give far-end resources the appearance of being internal. You would have to create different ARS entries for getting between sites and other manual workarounds. This would defeat the purpose of having a dedicated pipe.

If you aren't looking to use drop-and-insert applications or other things to split off voice and data you would be better off bypassing the Cisco stuff and going right into the DS1 boards on either end. There you would follow the path I outlined in my previous post. Define the Merlin as being either Legend-Ntwk or Legend-PBX depending on the Interface field value on the Definity. That way you would have the Electronic Tandem Networking end on the Merlin for all of the UDP features (except CVM). Then you would follow the appropriate directions for getting the Definity to see the other end of the tandem PRI. For suggestions as to specific details, try posting on the Definity board on this site...
 
Has anyone done a network connection between a Definity Prologix and a Magix? Successfully and what were the tough walls to climb

Thanks
ChiefRed
 
OK, on the Definity, set the span up for DCS. On the legend, program the PRI for LEGEND-PBX,not LEGEND-NTWK.

Then you can program your UDP stuff in that table and you should be able to get central messaging and Caller ID Name/Number.

That should work for you. Hope this helps...

Kris
 
I got everything working with the hardware I originally purchased. My Definity's can talk to everyone and my Merlin Legend's can talk to everyone all by dialing the extension and going over my Frame Relay connection for data.

Thank you to all,
Steve
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top