Big worry with regard to Small Comm Networking ???

[MrIPO]

We had big issues at all of our sites that were using Small Community Networking configured in a certain way with 1.3.X and 1.4.X Sites would drop off for now reason after a few weeks. After reboot they would come back for a few weeks then go again.

FSg's Avaya's answer was that you have to assign 1 master site that has VPN lines to each remote site. Each remote site only has one line pointing to the master site.

I wanted to pose the question is anybody having to configure SCN this way. ??

To me is it a huge downfull of networking IPO's using SCN. Because if a customer has purchased a fully meshed network, it's a pointless for Voice because all VoIP traffic has to route via the central site. This requires a large network tail configuration at the Master site not only for its own traffic but for every other site that has to route via it.

In my mind you should be able to configure every site to have VPN sorry VOIP lines (Version 2) to every other location so packets can route directly to each site, taking adavantage of a fully meshed network, and not have to route via the master site.

Am I wrong or this how everybody is programing IPO's with MASTER site. ??
Is version 2 different, I am re-opening my orginal Job with AVAYA, but I do not think I will get anywhere.
I think they need to inporoive the AVRIP smartness so IPO's when networked do not get confused and drop sites off.

Let me know you thoughts please

 

[itpphoneguy]

Hi MrIPO,
Just took the iP Office 2.0 course. We configured VoIP lines pointing to each ip address of the remote sites (routing). This allowed each site to "see" the other sites even if some went down. This is a network connection.
I did notice that one person configured their switch improperly and locked everyone else up. Make sure that the ip addresses for Manager, key server and voicemail are specified or the broadcast may be answered by a remote machine.
-Chris

 

[ksphoneman]

I can verify this problem still exists in 2.1(27).
So far, have not found any documentation about the SCN topology in the toolkit. Since the Customers Data Network was meshed in the Frame Relay, only made since to mesh the Voice network.(No single point of failure)
All seemed well until we brought up the eight, ninth and tenth site. Suddenly IPOs are freezing, losing partial configs, run for 3-4 days then repeat. So far, have only heard that SCN must be Star or Line topology. Would like to hear an explination as to why, other than it is recommended. Marketing is selling these systems as being able to support all topologies, and it seems difficult to get teir 3 to admit what will or will not work.