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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IP Office SCN Engineering Documentation

Status
Not open for further replies.

Mnavickas

Technical User
Oct 11, 2012
13
US
I have a customer upgrading/installing to all 7 sites.
They are looking for documention on how a "Wagon Wheel" SCN works. That being if center IPO goes down how the SCN channels are affected as the call traverses over multiple IPO's. If the call starts at IPO-A and needs to go to IPO-D will it use the SCN licenses in B and C while the call is active?
I'm implementing a thorough Mesh (SCN to every location on every IPO)but would REALLY like to see the above in documentation, if my statement is even true :)

Thanks.
 
This is all documented in IPOffice installation doc or on the knowledgebase.
But in a mesh configuration it will use the shortest route available and yes it will use a channel for each site it uses.


BAZINGA!

I'm not insane, my mother had me tested!

 
I cannot find it ANYWHERE. Have even tried older docs..Even tried asking our Avaya reps..They all say it's in the docs but no one has been able to prove it :) Ugh!
Any help with specifics would be GREATLY appreciated.
 

Thank you so much and I'm assuming this is what I was looking for:

Allow Direct Media Path: Default = On
This settings controls whether IP calls must be routed via the system or can be routed alternately if possible within the network structure.

If enabled, IP calls can take routes other than through the system. This removes the need for a voice compression channel. Both ends of the calls must support Direct Media and be using the same protocol (H.323 or SIP). Enabling this option may cause some vendors problems with changing the media path mid call. Pre-Release 4.0, when using direct media path, it is not always possible for the extension to be recorded or monitored.

If disabled or not supported at on one end of the call, the call is routed via the system.

On pre-4.0 these calls would then require a voice compression channel even if the IP devices use the same audio codec.

On Release 4.0 and higher, RTP relay support allows calls between devices using the same audio codec to not require a voice compression channel.
 
Allow direct media path would only work if each sites handsets and system all had visibilty of each other, the would require a mesh topology though, it wouldn't be a star (whagon wheel lol) :)


Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)
 
whagon? :)


Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top