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!

SCN accross 8 sites

Status
Not open for further replies.

SoGaIPO

Vendor
Feb 9, 2012
110
US
Just in the beginning stages of engineering a new customer with 8 branch offices. All will be 9.1 with centralized voicemail with back up VMPro. Although I am quite familiar with networking IPO's with 2 sites, I haven't had the opportunity to set up 8. My question to all the guru's is do I need to set up an ip route in each system to each of the other 7, or should I choose one to be the hub and have all systems route to it? Also do I need H.323 lines to each of the 7 other systems or to the hub only. Am prepared for either. Just want the best solution.
Thanks in advance for any help
 
Avaya says that a full meshed design works. But from my experience a star layout works better. Or linear or a combination of both. But only one path from one system to the other.

To make it more complicated in server edition solution AVAYA creates a double star. Two central systems and all satellite systems connect to those two central systems.
 
I would look into the server edition for this type on install.
I think the h323 lines should match you WAN network. Where I'm located all the MPLS circuits come back to the main HQ. No tunnels exist Node to Node. My WAN isn't meshed, so my phone systems are not meshed. I have 1 H323 line going from the hub (HQ) to all the nodes.
 
So correct me if I',m wrong, a star layout would have one system as a hub with H.323 lines to all other systems and all the other systems only have H.323 lines to hub (center)?
 
No, you are indeed right :)
Just setup your SE, configure 500v2 with correct IP, read config of SE with Manager, go to Solution and on the right side there should be something like "Add Expansion System" -> click that, enter IP of 500v2 and the SCN lines will be set up for you.
Just make sure that you edit all lines to proprietary SCN trunks afterwards and your SCN should be ready to go :)

ptc.png
 
As far as I understood we are not talking about server edition in this case. SE was only an example how Avaya builds the SCN.

I would go with a star or double star layout with the headquarter and - if double star - a second (good IP line available) site in the middle.
 
I always use a full mesh SCN and we have customers with upto 30 sites without any issue.
The most important thing is to use unique names/numbers/outgoing line IDs and when customer wants to use hotdesking over SCN then all user restriction tables must be available in all site's ( if used ).
 
just make sure that the network actually supports a full mesh as I am working with some companies where the IT guys are to lazy to create VPN's between all sites.

Joe W.

FHandw, ACSS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter
 
Thanks guys for all your input.
I did try to get the sales person to quote SE but with PRI at all but 2 sites he went with IPO 500v2 at all sites. I think full mesh may just be my best bet to eliminate chance of connectivity loss in the case of center (hub) site going down.
Meeting with IT guy on Tuesday, so I will emphasize the importance of VPN at all sites.
 
Question for Westi, you mentioned the need for vpn between all sites. Am I to understand that I will need a vpn between each sites just as the mesh ?
 
You either need a VPN between every site you want an SCN between or some form of MPLS or equivalent in order to do a meshed network.

| ACSS SME |
 
On the network side you would need to create 28 VPN tunnels to full mesh the 8 sites. Make sure you data equipement can handle this. Make sure your data people setup routing correctly. A fully meshed network can get very complicated.
 
Oh, I just saw Pepp77 response. So if the customer has an MPLS network in place, there is no need for VPN between sites?
This is a bank and I know they have MPLS set up. If they let me on this network then the IT guy will only have to setup QOS for the IP{O network.
 
Full mesh is allowed but manager will report errors if there are any more then 6 routes to any host

This pretty much limits you to a ring with a single diagonal link if you want a network that can survive a link failure.
(I have also seen networks fully meshed that exceed this without any issues)


Do things on the cheap & it will cost you dear
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top