Professional Documents
Culture Documents
Home Library Wiki Learn Downloads Support Forums Blogs Resources for IT Professionals
4. Specify a name and description to identify the purpose of this new location profile. For simplicity, we will create a basic
normalization rule that prepends ‘+’ to an 11-digit dialed number to conform with the E.164 numbering format. This allows
the number to be accepted by the SIP Trunk provider, IntelePeer, so that calls will be routed correctly as shown in Figure
3.
Figure 3. Phone normalization rule
Note:
Use the Enterprise Voice Route Helper application that is in the Microsoft Office Communications Server 2007 R2
Resource Kit to simplify the process of configuring and testing phone dial plans before applying them to Office
Communications Server 2007 R2.
5. Leave the Default Policy and Usage options on their default settings (you want all calls for all users to use the dial plan
and gateway that you specify).
6. To configure the dial plan, select the Routes tabbed page, and then click Add. To keep things simple, we’ll create a “route
everything” rule that forces all calls to route to the Mediation Server as shown in Figure 4. (The Mediation Server must
already be installed and activated.) Using the target expression of a period followed by an asterisk (.*), all calls are routed
to the Mediation Server that is specified. In this example, the Mediation Server is server.domain.com:5061. Click Add to
select one or more Mediation Servers as a gateway.
Figure 4. Voice route
7. Click OK, and then click OK again to complete the creation of the location profile.
Configure the Mediation Server to Use the SIP Trunk
To configure the Mediation Server to use the SIP trunk, you will configure the IP address that your internal servers that run Office
Communications Server 2007 R2 use to communicate. Then, configure the gateway listening IP address to the IP address that
your SIP provider uses to communicate.
1. Click Start, click Programs, click Administrative Tools, and then click Office Communications Server 2007 R2 to
open the administrative tools.
2. Expand the Mediation Servers node.
3. Right-click the Mediation Server that is selected as the gateway in the route you created earlier in this article, and then
select Properties.
4. On the General tabbed page (as shown in Figure 5), select the IP addresses, the A/V Edge Server, and the default
location profile from the drop-down lists. (Assuming that Active Directory directory service replication has completed
successfully, the newly created location profile will be an option).
Figure 5. Mediation Server General tab configuration
Note:
Only valid properties are shown in the drop-down lists, meaning that you can’t manually enter any of the information.
Your server must have two IP addresses: one for internal communication and one for external communication. The Edge
Server must already be set up and configured within Office Communications Server 2007 R2.
5. Click the Next Hop Connections tabbed page to configure the outbound voice communications as shown in Figure 6.
Select the Office Communications Server pool from the FQDN drop-down list (Enterprise Edition or Standard Edition),
and then type the external SIP provider’s next hop address. Office Communications Server 2007 R2 communicates by
using Transmission Control Protocol (TCP) or Transport Layer Security (TLS) (TLS adding certificate-based encryption),
but I have found that using TCP for voice traffic meets all current requirements. IntelePeer has a DNS name of
gsxgroup1.intelepeer.net, which will route to all the GSX environments that support Office Communications Server 2007
R2.
Figure 6. Mediation Server Next Hop Connections tabbed page configuration
To give us feedback about this article or to propose a topic for an article, e-mail us at NextHop@microsoft.com.
You can also send us a tweet at http://www.twitter.com/DrRez.
© 2010 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks | Privacy Statement | Site Feedback