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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Networking Merlin Magix
- Thread starter dquamme
- Start date
killbox
Programmer
- Aug 25, 2003
- 383
Well, no ones replied because it's not cut and dry. There's a lot the goes into it. How do you want to connect the systems?? IP of point to point's??
For IP, who'll need E&M Tie line cards and MultiTech Gateways. For, Point to Point's, you'll need, T1 cards for the systems for as many T1's to each system.
For IP, you'll need to program the E&M cards. For T1 cards, they'll need to be set up as PRI, and all the protocols need to be programmed for networking under PRI.
You'll need to set up pools for the trunks on the cards.
You'll have to set up a dialing plan. Extensions have to different, a 4 digit plan, and the UDP built.
You'll have to set up calling groups for voice mail for each system as well. But all the remotes will have to have virual ext.'s from the UDP as members of the calling groups. Ane those members will have to be members in the calling group of the centralized VM.
You most likely will have to hire a vendor to do this for you?
KILLBOX
For IP, who'll need E&M Tie line cards and MultiTech Gateways. For, Point to Point's, you'll need, T1 cards for the systems for as many T1's to each system.
For IP, you'll need to program the E&M cards. For T1 cards, they'll need to be set up as PRI, and all the protocols need to be programmed for networking under PRI.
You'll need to set up pools for the trunks on the cards.
You'll have to set up a dialing plan. Extensions have to different, a 4 digit plan, and the UDP built.
You'll have to set up calling groups for voice mail for each system as well. But all the remotes will have to have virual ext.'s from the UDP as members of the calling groups. Ane those members will have to be members in the calling group of the centralized VM.
You most likely will have to hire a vendor to do this for you?
KILLBOX
gregarican
IS-IT--Management
Personally I would step up this solution to IP Office. My company has two crosstown site locations I tied together from Merlin Legend (CVM/PSTN hub) to Merlin Magix (remote PBX). I provisioned part of the point to point as PRI voice and left the remaining upper channels as one big data pipe. We are considering adding another location, and if we want to network it I am going to up things to IP Office.
A Merlin Magix can upgrade to IP Office in pretty short fashion from what I gather. If you have current phone sets and other components. And IP Office can compress voice sessions pretty well from what I have read. Better than VoIP solutions several years ago. So you can get more bang for your buck.
But if you are mainly a telecom person I would recommend getting an outside consultant to assist as killbox recommended.
A Merlin Magix can upgrade to IP Office in pretty short fashion from what I gather. If you have current phone sets and other components. And IP Office can compress voice sessions pretty well from what I have read. Better than VoIP solutions several years ago. So you can get more bang for your buck.
But if you are mainly a telecom person I would recommend getting an outside consultant to assist as killbox recommended.
OK, I will now provide my 2 Cents worth. (only it is probably not worth that much....)
Just as killbox said, no one is answering 'cause it is not just cut and dried, it is VERY TOUGH.
WITH POINT TO POINT T1's you can easily network Legends/Magixs by telling each system that the T1 is a PRI.
That's just the start. AND, it gets very complex after that.
The LEGEND/MAGIX can SHINE in that kind of setup, but as gregarican said, the IP OFFICE is a MUCH CHEAPER way to go to network 5 other systems.
The questions that must be answered are:
1) DO THEY HAVE EXISTING LEGEND/MAGIX HARDWARE in these other locations?
-or-
2) Are they getting NEW STUFF?
If 1 is true, then the PRI route is the way to go,
If 2 is true, then IP would be worth looking into....
Again, my 2 Cents is worth about that much.......
Just as killbox said, no one is answering 'cause it is not just cut and dried, it is VERY TOUGH.
WITH POINT TO POINT T1's you can easily network Legends/Magixs by telling each system that the T1 is a PRI.
That's just the start. AND, it gets very complex after that.
The LEGEND/MAGIX can SHINE in that kind of setup, but as gregarican said, the IP OFFICE is a MUCH CHEAPER way to go to network 5 other systems.
The questions that must be answered are:
1) DO THEY HAVE EXISTING LEGEND/MAGIX HARDWARE in these other locations?
-or-
2) Are they getting NEW STUFF?
If 1 is true, then the PRI route is the way to go,
If 2 is true, then IP would be worth looking into....
Again, my 2 Cents is worth about that much.......
gregarican
IS-IT--Management
I would also suggest (if you haven't done so already) visiting Avaya's website. They have lots of useful admin, enduser, and planning docs for their product line. This might help you in your decision making.
For a link on networking Merlin systems see -->
For a link to working with the Merlin Magix INA board (the module that can break out private point to point voice/data) see -->
Hope this helps!
For a link on networking Merlin systems see -->
For a link to working with the Merlin Magix INA board (the module that can break out private point to point voice/data) see -->
Hope this helps!
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
