SCN Mesh Network

[bizhelp]

Documentation indicates that only Star and not Mesh SCN is supported. Anyone know the reasoning behind this? Anyone know if this can safely be disregarded? I'd like to create a voip line to each office from every office to assure the most direct data path possible for extension to extension dialing and also toll bypass situations.

 

[Ragnorak]

Disregarded- yes, safely- no. It creates routing loops and strange bugs. Also tech support will tell you to dump the mesh if you have any issues.

 

[kristiandg]

What you can do is set your mesh up as QSIG. That is permitted.

Hell, I've had two systems trade each others databases once over SCN (that was back on 2.1). That was a fun one.

Kris

 

[sizbut]

Not "mesh" but that doesn't mean restricted pure "hub" or "star".

The key is that between any two IP Office's in the network, their should only be one route for SCN traffic.

For example the following is fine.

A
|
B-C-D
| |
E F

Also there is a limit of 5 hops.

 

[bizhelp]

sizbut, in your example would a call from point A to point F actually traverse b and c or would the call over voip actually go point to point?

 

[kristiandg]

If DIRECT MEDIA PATH were on, it should be redirected.

Kris G.

 

[l33byt1]

Do not do Meshed. Had a weird fault here which was swapping bits of each sites configs to other units. Rebooting a switch would kill it. Regular system crashes all due to a meshed topology.

 

[bizhelp]

Thanks.. I find that extension to extension calls are being redirected as indicated above by kristiandg. One of my goals is to take outbound calls to pstn and redirect them over the network to go out another office. So, in the example above office A dials 123-456-7890 and the call comes out office F with a direct media path. Would that work?

 

[kristiandg]

I would think it should.

Kris G.