Networking Magix

[cajuntank]

We have a school system that has 5 campus locations and a central office(using as the hub). Currently have Point-to-Point T1's from the campuses back to CO(school not telco). We have two Magix r2.2 both with two 100dcd cards. One in each for PRI to telco, the other for channelized voice/data communication between each other. One of the systems is on a 3 school campus(High school where Magix is physically located, Middle school which has Partner(getting CO lines from Ananlog ext. ports off of Magix), Elementary school using High school system). The Elementary is wanting to implement Magix for themselves which makes 2 systems and maxes out cards for High School.OK. Putting in another system at another campus just like previous; however, instead of 2 systems, will have 3 systems tied together.OK.
These two campuses will/are going back to the school system's CO (again because of PRI and T1's, I'm maxed out at this location). I have 3 remaining campuses; one has large Partner installation so I'm using Multi-Tech Analog VoIP back to CO location for them, the other two using MCK's; but now, they are wanting to implemtn Magix also. This makes an additional two connections my main CO system will not be able to do on top of having the possible nightmare with so many systems linked together. Because of certain circumstances, Definity is out of the question, but an IP office solution is not. To bad Avaya does not have a IP trunking card for the Magix, this would solve my problem big time. Anyone have any thoughts about this? Is this definetly too many systems? is there such an card(IP trunking) out there from Avaya maybe r3? any 3rd party hardware that can be implemented?
Sorry about so much info and so many questions.
Just would like to hear a couple of peoples thoughts.
TIA

 

[ttech]

You could take a look at

http://www.multitech.com

for some VOiP stuff for the magix.

-Don

 

[mrpeabody]

Samsung Manufactures a VoIP Media Gateway that will work with any system. Model number SMG 3200/400.

 

[cajuntank]

To re-cap... I have Multi-tech VoIP devices providing analog co lines to remote Partner systems off from the main Magix system. Since the Magix system can only have 3 T1/PRI cards in each, I will somehow need to connect two additional T1 connections for the two sites that are wanting to switch from MCK connectivity to their own Magix system. So the questions still are; is there a IP trunking card coming out for say r3? or any 3rd party channel bank that will still work with the propriotary info the Magix sends out on it's PRI?

 

[Ghostin]

Can you make one of the sites the main hub? If so, move the magix from that site and replace with a small Definity system. Network each of the Magix systems to the Definity. If these are all local switches, you could save money by routing all the calls and voice mail through the Definity. The Definity does not have the 3 T-1 card limitations that the Magix has. It might sound daunting, but it will be your best and most cost effective solution in the long run.

 

[cajuntank]

How about one of the IP solutions... could one be used instead of the Definity?

 

[Ghostin]

Are you refering to the Avaya IP Office? I think the jury is still out on that one. We haven't had to deal with them, so I can't really give you any specs.

 

[Pepperz]

I've connected Multi-tech gateways with an E&M card (a 2 way DID card) which can give 8 trunks for IP telephone. In your situation, it may work pretty well

TipHelp@charter.net

 

[jdoc]

All of the above are valid fixes. What you may want to do is to rethink your networking and get away from the main hub theory and go to a linear network for your magix. This only requires that 2 “100dcd” cards be in each system and there are good examples of this in the documentation. This also helps prevent the single week point from taking the whole system down. You can renumber the extensions so that they are all unique and establish call routing plans, ARS and UDP.
ARS will make allow you to keep calls that are internal from tying up your outside lines.
UDP will allow all the magix to act as one system for extension purposes.

JD

 

[kristiandg]

You may also be able to use a single 100DCD card in each system and go into a VoIP gateway (such as the cisco solutions) that can route calls based on the number dialed. Now each system only requires a single TIE line.

The number dialed is sent out via PRI to the Cisco, which looks in it Dialpeer table (similar to UDP Table) and routes the call, via IP, to the required PBX and out that far-end Cisco into that specific Legend/Magix.

If you already have Cisco equipment, it may simply be a matter of upgrading the IOS to v11 or v12.

Hope this helps.

Kris

 

[cajuntank]

I am very interested in the Cisco approach since we would like to possibly evolve to a Cisco IP Telephony integration with the AVAYA equipment. Are there any docs or links that I can look at regarding the two technologies working together?

 

[kristiandg]

Yes and no. We're implimenting it here at 100 sites and we're working out the bugs now. Its very complicated for the initial setup.

Your best bet is to get a Cisco person who understands DialPeers and VoIP Gatekeepers.

Kris

 

[kristiandg]

In fact, our Cisco people supplied the necessary people at no charge since we were buying equipment for 100 sites.

Kris

 

[GoKings]

Have you considered SDN dialing since you have PRI's back to Telco?