Configure a trunk with media bypass in Lync Server 2013
Topic Last Modified: 2014-02-07
Follow these steps to configure a trunk with media bypass enabled. To configure a trunk with media bypass disabled, see Configure a trunk without media bypass in Lync Server 2013. Media bypass is useful when you want to minimize the number of Mediation Servers deployed. Typically, a Mediation Server pool will be deployed at a central site, and it will control gateways at branch sites. Enabling media bypass allows media for public switched telephone network (PSTN) calls from clients at branch sites to flow directly through the gateways at those sites. Lync Server 2013 outbound call routes and Enterprise Voice policies must be properly configured so that PSTN calls from clients at a branch site are routed to the appropriate gateway.
We strongly recommend that you enable media bypass. However, before you enable media bypass on a SIP trunk, confirm that your qualified SIP trunk provider supports media bypass and is able to accommodate the requirements for successfully enabling the scenario. Specifically, the provider must have the IP addresses of servers in your organization’s internal network. If the provider cannot support this scenario, media bypass will not succeed. For details, see Planning for media bypass in Lync Server 2013 in the Planning documentation.
Note
Media bypass will not interoperate with every public switched telephone network (PSTN) gateway, IP-PBX, and Session Border Controller (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 that are listed on Unified Communications Open Interoperability Program – Lync Server at https://go.microsoft.com/fwlink/p/?linkId=214406.
A trunk configuration as described below groups a set of parameters that are applied to trunks assigned this trunk configuration. A particular trunk configuration can be scoped globally (to all trunks that do not have more specific site or pool configuration), or to a site, or to a pool. The pool-level trunk configuration is used to scope a specific trunk configuration to a single trunk.
To configure a trunk with media bypass
Log on to the computer as a member of the RTCUniversalServerAdmins group, or as a member of the CsVoiceAdministrator, CsServerAdministrator, or CsAdministrator role. For details, see Delegate setup permissions in Lync Server 2013.
Open a browser window, and then enter the Admin URL to open the Lync Server Control Panel. For details about the different methods you can use to start Lync Server Control Panel, see Open Lync Server 2013 administrative tools.
In the left navigation bar, click Voice Routing, and then click Trunk Configuration.
On the Trunk Configuration page, use one of the following methods to configure a trunk:
Double-click an existing trunk (for example, the Global trunk) to display the Edit Trunk Configuration dialog box.
Click New, and then select a scope for the new trunk configuration:
Site trunk: Choose the site for this trunk configuration from Select a Site, and then click OK. Note that if a trunk configuration has already been created for a site, the site does not appear in Select a Site. This trunk configuration will be applied to all trunks in the site.
Pool trunk: Choose the name of the trunk that this trunk configuration applies to. This trunk can be the root trunk or any additional trunks defined in Topology Builder. From Select a Service, click OK. Note that if a trunk configuration has already been created for a specific trunk, the trunk does not appear in Select a Service.
Note
After you select the scope of the trunk configuration, it cannot be changed.
The Name field is prepopulated with the name of the trunk configuration’s associated site or service and cannot be changed.Specify a value in Maximum early dialogs supported. This is the maximum number of forked responses a public switched telephone network (PSTN) gateway, IP-PBX, or ITSP Session Border Controller (SBC) can receive to an INVITE that it sent to the Mediation Server. The default value is 20.
Note
Before you change this value, consult your service provider or equipment manufacturer for details about the capabilities of your system.
Select one of the following Encryption support level options:
Required: Secure real-time transport protocol (SRTP) encryption must be used to help protect traffic between the Mediation Server and the gateway or private branch exchange (PBX).
Optional: SRTP encryption will be used if the service provider or equipment manufacturer supports it.
Not Supported: SRTP encryption is not supported by the service provider or equipment manufacturer and therefore will not be used.
Select the Enable media bypass check box if you want media to bypass the Mediation Server for processing by the trunk peer.
Important
For media bypass to work successfully, the PSTN gateway, IP-PBX, or ITSP Session Border Controller must support certain capabilities. For details, see Planning for media bypass in Lync Server 2013 in the Planning documentation.
Select the Centralized media processing check box if there is a well-known media termination point (for example, a PSTN gateway where the media termination has the same IP as the signaling termination). Clear this check box if the trunk does not have a well-known media termination point.
If the trunk peer supports receiving SIP REFER requests from the Mediation Server, select the Enable sending refer to the gateway check box.
Note
If you disable this option while the Enable media bypass option is selected, additional settings are required. If the trunk peer does not support receiving SIP REFER requests from the Mediation Server and media bypass is enabled, you must also run the Set-CsTrunkConfiguration cmdlet to disable RTCP for active and held calls in order to support proper conditions for media bypass. For details, see the Lync Server 2013 Management Shell documentation.
Alternatively, you can select Enable refer using third-party-call control if you want transferred calls to be media bypassed, and the gateway does not support SIP REFER requests.(Optional) To enable inter-trunk routing, associate and configure PSTN usage records to this trunk configuration. The PSTN usages associated to this trunk configuration will be applied for all incoming calls through the trunk that is not originating from a Lync endpoint. To manage PSTN usage records associated to a trunk configuration, use one of the following methods:
To select one or more records from a list of all PSTN usage records available in your Enterprise Voice deployment, click Select. Highlight the records you want to associate with this trunk configuration and then click OK.
To remove a PSTN usage record from this trunk configuration, select the record and click Remove.
To define a new PSTN usage record and associate it with this trunk configuration, do the following:
Click New.
In the Name field, specify a descriptive name for the record that is unique.
Note
The PSTN usage record name must be unique within the Enterprise Voice deployment. After the record is saved, the Name field cannot be edited.
Use one of the following methods to associate and configure routes for this PSTN usage record:
To select one or more routes from the list of all available routes in your Enterprise Voice deployment, click Select. Highlight the routes you want to associate with this PSTN usage record, and click OK.
To remove a route from the PSTN usage record, select the route, and click Remove.
To define a new route and associate it to this PSTN usage record, click New. For details, see Create a voice route in Lync Server 2013.
To edit a route that is associated with this PSTN usage record, select the route, and click Show details. For details, see Modify a voice route in Lync Server 2013.
Click OK.
To edit a PSTN usage record that is already associated with this trunk configuration, do the following:
Select the PSTN usage record you want to edit, and click Show details.
Use one of the following methods to associate and configure routes for this PSTN usage record:
To select one or more routes from the list of all available routes in your Enterprise Voice deployment, click Select. Highlight the routes you want to associate with this PSTN usage record, and click OK.
To remove a route from the PSTN usage record, select the route, and click Remove.
To define a new route and associate it to this PSTN usage record, click New. For details, see Create a voice route in Lync Server 2013.
To edit a route that is associated with this PSTN usage record, select the route, and click Show details. For details, see Modify a voice route in Lync Server 2013.
Click OK.
Important
It important to associate PSTN usage records according to the Mediation Server peer that is associated to the trunk being configured. If the Mediation Server peer is a PSTN gateway or a Session Border Controller (SBC), it is strongly recommended that the trunk configuration is not associated to a PSTN usage record that routes to a PSTN destination or any other downstream systems connected via Lync Server.
Arrange the PSTN usage records for optimum performance. To change a record’s position in the list, select the PSTN usage record, and click the up or down arrows.
Important
The order in which PSTN usage records are listed in the trunk configuration is significant. Lync Server traverses the list from top to down.
Enable RTP Latching should be selected to enable bypass media for clients behind a network address translation (NAT) or firewall and an SBC that supports latching.
Enable forward call history should be selected to enable sending of call history information to the gateway peer of the Mediation Server.
Enable forward P-Asserted-Identity data should be selected to enable the P-Asserted-Identity (PAI) call originator information to be forwarded between the Mediation Server side and gateway side (and vice versa), when present.
Enable outbound routing failover timer should be selected to enable fast failover. The gateway associated with this trunk can give notification within 10 seconds that it is processing an outbound call. Rerouting to another trunk will occur if this notification is not received by the Mediation Server. On networks where latency may delay the response time or the gateway takes longer than 10 seconds to respond, the fast failover should be disabled.
(Optional) Associate and configure calling number translation rules for the trunk. These translation rules apply to the calling number for outbound calls
To choose one or more rules from a list of all translation rules that are available in your Enterprise Voice deployment, click Select. In Select Translation Rules, click the rules that you want to associate with the trunk, and then click OK.
To define a new translation rule and associate it with the trunk, click New. For details about defining a new rule, see Defining translation rules in Lync Server 2013 in the Deployment documentation.
To edit a translation rule that is already associated with the trunk, click the rule name, and then click Show details. For details, see Defining translation rules in Lync Server 2013 in the Deployment documentation.
To copy an existing translation rule to use as a starting point for defining a new rule, click the rule name and click Copy, and then click Paste. For details, see Defining translation rules in Lync Server 2013.
To remove a translation rule from the trunk, highlight the rule name and click Remove.
Warning
Do not associate translation rules with a trunk if you have configured translation rules on the associated trunk peer, because the two rules might conflict.
(Optional) Associate and configure called number translation rules for the trunk. The translation rules apply to the called number in an outbound call.
To choose one or more rules from a list of all translation rules that are available in your Enterprise Voice deployment, click Select. In Select Translation Rules, click the rules that you want to associate with the trunk, and then click OK.
To define a new translation rule and associate it with the trunk, click New. For details about defining a new rule, see Defining translation rules in Lync Server 2013 in the Deployment documentation.
To edit a translation rule that is already associated with the trunk, click the rule name, and then click Show details. For details, see Defining translation rules in Lync Server 2013 in the Deployment documentation.
To copy an existing translation rule to use as a starting point for defining a new rule, click the rule name and click Copy, and then click Paste. For details, see Defining translation rules in Lync Server 2013.
To remove a translation rule from the trunk, highlight the rule name and click Remove.
Warning
Do not associate translation rules with a trunk if you have configured translation rules on the associated trunk peer, because the two rules might conflict.
Make sure that the trunk’s translation rules are arranged in the correct order. To change a rule’s position in the list, highlight the rule name and then click the up or down arrow.
Important
Lync Server 2013 traverses the translation rule list from the top down and uses the first rule that matches the dialed number. If you configure a trunk so that a dialed number can match more than one translation rule, be sure that the more restrictive rules are sorted above the less restrictive rules. For example, if you have included a translation rule that matches any 11-digit number and a translation rule that matches only 11-digit numbers that start with +1425, be sure that the rule that matches any 11-digit number is sorted below the more restrictive rule.
When you are finished configuring the trunk, click OK.
On the Trunk Configuration page, click Commit, and then click Commit all.
Note
Whenever you create or modify a trunk configuration, you must run the Commit all command to publish the configuration change. For details, see Publish pending changes to the voice routing configuration in Lync Server 2013 in the Operations documentation.
After you have configured the trunk, continue configuring media bypass by choosing between global media bypass options, as described in Global media bypass options in Lync Server 2013 in the Deployment documentation.