Export (0) Print
Expand All

Configure Media Bypass

 

Topic Last Modified: 2013-02-24

This section assumes that you have already published and configured either at least one or more Mediation Servers (as described in Define a Mediation Server in Topology Builder and Publish the Topology, or in Define and Configure a Front End Pool or Standard Edition Server and Publish the Topology, respectively, all in the Deployment documentation).

This section also assumes that you have defined at least one gateway peer to provide PSTN connectivity, as described in Define a Gateway in Topology Builder. If the peer you connect to is the SBC of a SIP trunking provider, make sure that the provider is a qualified provider and that the provider supports media bypass. For example, many SIP trunking providers will only allow their SBC to receive traffic from the Mediation Server. If so, then bypass must not be enabled for the trunk in question. Also, you cannot enable media bypass unless your organization reveals its internal network IP addresses to the SIP trunking provider.

noteNote:
Media bypass will not interoperate with every PSTN gateway, IP-PBX, and SBC. Microsoft has tested a set of PSTN gateways and SBCs with certified partners and has done some testing with Cisco IP-PBXs. Media bypass is supported only with products and versions listed on Unified Communications Open Interoperability Program – Lync Server at http://go.microsoft.com/fwlink/p/?linkId=214406.

This section describes how to enable media bypass to reduce the processing required of the Mediation Server. Before you enable media bypass, make sure that your environment meets the conditions required to support media bypass, as described in Planning for Media Bypass in the Planning documentation. Also make sure that you used the information in Planning for Media Bypass to decide whether to enable media bypass global settings to always bypass the Mediation Server or to use site and region information when determining whether to bypass the Mediation Server.

If you have already optionally configured call admission control (CAC), another advanced Enterprise Voice feature, note that the bandwidth reservation performed by call admission control does not apply to any calls for which media bypass is employed. The verification of whether to employ media bypass is performed first, and if media bypass is employed, call admission control is not used for the call; only if the media bypass check fails is the check performed for call admission control. The two features are thus mutually exclusive for any particular call that is routed to the PSTN. This is the logic because media bypass assumes that bandwidth constraints do not exist between the media endpoints on a call; media bypass cannot be performed on links with restricted bandwidth. As a result, one of the following will apply to a PSTN call: a) media bypasses the Mediation Server, and call admission control does not reserve bandwidth for the call; or b) call admission control applies bandwidth reservation to the call, and media is processed by the Mediation Server involved in the call.

After configuring initial settings for PSTN connectivity (dial plans, voice policies, PSTN usage records, outbound call routes, and translation rules), begin the process of enabling media bypass by using the steps in Configure a Trunk with Media Bypass.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft