deploying voxbone with skype for businessmicrosoft skype for business server provides the software...
TRANSCRIPT
Tel. +1 805 880 9800 Copyright © 2015 Voxbone
Email: [email protected] All Rights Reserved page 1 of 23
These materials are the copyright of Voxbone, SA and any dissemination, distribution, or unauthorized use is strictly
prohibited. All other trademarks are the property of their respective owner.
DEPLOYING VOXBONE WITH SKYPE FOR BUSINESS
+
Version 1.0
July 29, 2015
Tel. +1 805 880 9800 Copyright © 2015 Voxbone
Email: [email protected] All Rights Reserved page 2 of 23
These materials are the copyright of Voxbone, SA and any dissemination, distribution, or unauthorized use is strictly
prohibited. All other trademarks are the property of their respective owner.
Table of Contents Preface ............................................................................................................................................................................... 3
Assumptions ....................................................................................................................................................................... 4
Behavior in a Skype for Business Hybrid environment ...................................................................................................... 5
Configure Skype for Business environment ........................................................................................................................... 5
Configure Mediation Server ............................................................................................................................................... 5
Adding PSTN gateways ....................................................................................................................................................... 6
Configure Voice Routing: ................................................................................................................................................. 10
Dial-in Access numbers .................................................................................................................................................... 16
Display Dial-In conferencing numbers on meeting invites .............................................................................................. 17
Setting the users PIN code ............................................................................................................................................... 18
Configure Voxbone portal .................................................................................................................................................... 20
Purchase numbers and channels ..................................................................................................................................... 20
Configure Defaults ........................................................................................................................................................... 20
Configure URI ................................................................................................................................................................... 21
Configure numbers .......................................................................................................................................................... 22
Testing .............................................................................................................................................................................. 23
Appendix 1: Firewall Configuration.................................................................................................................................. 23
Tel. +1 805 880 9800 Copyright © 2015 Voxbone
Email: [email protected] All Rights Reserved page 3 of 23
These materials are the copyright of Voxbone, SA and any dissemination, distribution, or unauthorized use is strictly
prohibited. All other trademarks are the property of their respective owner.
Preface This document will describe how to integrate VoxDID with Lync Server 2013 and Skype for Business Server 2015. All
screenshots will be from Skype for Business Server 2015, but the configuration is identical for Lync Server 2013 and the
configuration interfaces are only cosmetically different.
Voxbone Service Overview
Voxbone believes in a world where ordering and configuring telecom services is as simple as buying any internet
service. Voxbone's role is to provide an automated and quality access to the global voice network infrastructure by
combining the main advantages of the current system with the advantages of all-IP. Voxbone's mission is to simplify
telecommunications by bringing local voice services to the cloud.
As the market leader in providing worldwide geographical, toll-free and iNum® telephone numbers, Voxbone delivers
high quality inbound communications (often referred to as direct inward dialing, or DID) from more than 55 countries
and more than 8,000 cities. Voxbone enables Internet communications services providers, global carriers and national
operators to extend the reach of their voice services internationally, rapidly and with limited costs.
Voxbone is the only operator of its kind with self-owned licenses, telephone number ranges and network infrastructure
in its footprint. In 2014, Voxbone's private global VoIP network carried 4+ billion minutes of voice traffic. The company
excels through its quality of service, best-in-industry management tools and regulatory compliance. Voxbone has more
than 850 wholesale customers around the globe, including Skype, IDT, Level(3), inContact, 8x8 and Voxeo. Founded in
2005, Voxbone is privately held with headquarters in Brussels and offices in the United States.
Voxbone and Skype For Business Server
In today's global marketplace, your employees, customers and partners need to connect, communicate and collaborate
all around the world. A number from Tokyo can ring on an engineer's desk in Chicago, a New York City number on an
executive's desk in Sao Paolo. Or co-workers and customers from all continents can meet each other in multimedia
conference rooms by dialing a local telephone number. Telephone numbers serve as a virtual local door through which
customers, employees and partners may enter from their traditional and mobile phones to communicate with your
global organization.
Microsoft Skype for Business Server provides the software framework and tools to enable real-time communication
globally, and Voxbone provides the local telephone numbers to localize your customer, prospect and employee
experience. Voxbone is proud to have its VoxDID and Vox800 International inbound SIP trunking products qualified for
Microsoft Skype for Business Server.
With Voxbone as your International Inbound SIP trunking Provider, Microsoft Skype for Business enabled organizations
can source DID and toll-free numbers supporting voice, fax and SMS. These numbers can be used as dial-in numbers for
audio conferencing or as virtual international phone numbers for contact centers. Voxbone is the only Microsoft Skype
for Business qualified SIP trunking provider offering service in all of Europe and licensed in all 28 member countries of
the European Union. Voxbone also offers extensive coverage in Asia, Africa, Australia, as well as North and South
America.
Tel. +1 805 880 9800 Copyright © 2015 Voxbone
Email: [email protected] All Rights Reserved page 4 of 23
These materials are the copyright of Voxbone, SA and any dissemination, distribution, or unauthorized use is strictly
prohibited. All other trademarks are the property of their respective owner.
The primary benefits of Voxbone's services include:
International inbound SIP trunking with large coverage
Number portability from a large list of countries
Easy to use portal and powerful API that allow instant provisioning and collaboration
Quality backed by carrier licenses, 24/7 NOC and redundant global IP network
Joint Use Cases Audio Conferencing
One of the most compelling areas for increasing efficiency, utility and cost savings with Skype for Business and Voxbone
is Audio Conferencing. Skype for Business and Lync Servers have built in Audio Conferencing (MCU) capabilities. By
combining these features with Voxbone SIP trunk/ DID numbers in 55+ countries, enterprises can dramatically increase
conference reachability while lowering communications and conferencing costs.
Contact Centers
Skype for Business and Voxbone can be used together to enable international customer service, technical support, sales
support build on top of Skype for Business server.
Unified Communications
Voxbone can port in numbers in over 30 countries so as enterprises migrate desk and office phones from legacy PBX to
advanced Unified Communications, existing numbers can be kept and consolidated across countries and managed
through Voxbone's centralized portals and APIs.
Assumptions
This configuration guide will focus on Audio Conferencing application for Voxbone and Skype For Business. Set up and
configuration of Microsoft servers are not covered in this document. The following solution prerequisites are made in
this document:
- Lync Server 2013 or Skype for Business Server 2015 environment is configured and tested, including at least
o One working Standard Edition Front End server or Enterprise edition Front End pool
o Collocated or Standalone mediation server
o Optional Edge server and reverse proxy set up for external access, external meeting join and federation
with other Skype for business/Lync organizations.
- Basic knowledge of Skype for Business/Lync configuration concepts and user interfaces like Deployment wizard,
Topology Builder, Lync Control Panel and PowerShell.
Tel. +1 805 880 9800 Copyright © 2015 Voxbone
Email: [email protected] All Rights Reserved page 5 of 23
These materials are the copyright of Voxbone, SA and any dissemination, distribution, or unauthorized use is strictly
prohibited. All other trademarks are the property of their respective owner.
Behavior in a Skype for Business Hybrid environment
A Skype for Business hybrid environment is a Skype for Business topology where an Office 365 and On-Prem
deployment are integrated, and users share the same SIP domain namespace. Some users will be homed in Office 365
Skype for Business and some on On-Prem Skype for Business.
Because of limitations in Office 365 no part of the On-Prem enterprise voice functionality is available to a user homed
in Office 365 in a hybrid deployment. When deploying a Voxbone DID in a hybrid environment it will only be possible to
enable for enterprise voice or assign a Dial Plan to users homed On-Prem, and not to users homed in Office 365. It is
therefore only possible for users “homed” to the Skype For Business Server to host conferences on the enterprise
server and use Voxbone numbers to access these conferences. Users “homed” in Office 365 Skype for Business cannot
take advantage of these Server features.
Hybrid Users hosted On-Prem will have the same experience as users in a standalone deployment.
Microsoft has made available an explanation for the limitations in this blog post from the Lync team:
http://blogs.technet.com/b/nexthop/archive/2013/05/13/lync-hybrid-offers-simplified.aspx
Configure Skype for Business environment
Configure Mediation Server On the Mediation Server, there are three critical components that need to be configured correctly to work with a
Voxbone trunk
- The Mediation server needs to have a NIC with a public IP address
- The Mediation server must have TCP listening ports enabled
- The listening port needs to be set correctly
We will go through each point in detail.
Mediation Server NIC
While a NAT deployment may work, Voxbone does not support delivery of SIP signaling or voice media over NAT. So the
Mediation server needs to be configured with one NIC with a publicly routable IP address and one NIC placed in an
internally routable network. The general recommendation, like with an Edge server, is to place the external NIC in a
public DMZ and the internal NIC in an internal DMZ. It is also strongly recommended to only allow traffic between the
external mediation server NIC and the Voxbone Points of Presence.
The ports that need to be open between Voxbone and the external NIC and between the internal NIC and internal
networks are described in Appendix 1
NOTE: The following steps must not be done on a Mediation server that is already configured with PSTN gateways and
trunks. While the Mediation server supports multiple PSTN gateways, the other gateways need to be reconfigured to
Tel. +1 805 880 9800 Copyright © 2015 Voxbone
Email: [email protected] All Rights Reserved page 6 of 23
These materials are the copyright of Voxbone, SA and any dissemination, distribution, or unauthorized use is strictly
prohibited. All other trademarks are the property of their respective owner.
use the new PSTN IP address if you want to use the same Mediation server. If this is not possible it is recommended to
use a separate Meditation server for Voxbone.
To configure the mediation server
1. On the Mediation server, add the correct IP addresses to the corresponding NICs
2. Open up Topology Builder and locate the Mediation server that is going to receive the calls from Voxbone and
open up its properties.
3. Select “Limit service usage to selected IP addresses
4. Under “Primary IP address” type the address of the internal NIC
5. Under “PSTN IP address” type the address of the external NIC
6. Publish the topology
7. After the topology changes has replicated, rerun Step 2 of the deployment wizard on the mediation server to
reconfigure it with the changes
Mediation server listening ports
To receive calls from Voxbone, the Mediation server needs to be configured to accept SIP over TCP. By default, only SIP
over TLS is enabled.
The server also needs to be configured with a TCP listening port. The default TCP listening port on the Mediation server
is port 5068. By default, Voxbone uses the default SIP TCP port which is port 5060.
NOTE: If the use of another port than 5060 is required this will need to be taken in to consideration when setting up
the URI in the Voxbone portal.
To enable TCP and configure the listening port the following steps are needed
1. Open up Topology Builder and locate the Mediation server that is going to receive the calls from Voxbone and
open up its properties.
2. Under PSTN gateway, check the “Enable TCP port” checkbox
3. Enter 5060-5060 in the “TCP” boxes
4. Click “OK” and publish the topology
Adding PSTN gateways
The next task will be to add all the Voxbone points of presence (PoP) to the Skype for Business/Lync topology. The
Voxbone PoPs are
Tel. +1 805 880 9800 Copyright © 2015 Voxbone
Email: [email protected] All Rights Reserved page 7 of 23
These materials are the copyright of Voxbone, SA and any dissemination, distribution, or unauthorized use is strictly
prohibited. All other trademarks are the property of their respective owner.
Belgium BE 81.201.82.45
Hong Kong CN 81.201.86.45
Germany DE 81.201.83.45
Los Angeles US-LA 81.201.84.195
New York US-NY 81.201.85.45
While each number is configured to use a specific PoP, all PoPs should be added to the topology. In case of an outage
the traffic may be rerouted through another PoP and if it is not present in the topology, the Mediation server will not
accept the connection.
To add the PoPs to the topology:
1. Open up topology builder and expand “Shared components”. Right click on “PSTN gateways” and select “New
PSTN Gateway to open the “Define new IP/PSTN Gateway” wizard
2. In the “FQDN field, enter the IP address of the PoP and click next
Tel. +1 805 880 9800 Copyright © 2015 Voxbone
Email: [email protected] All Rights Reserved page 8 of 23
These materials are the copyright of Voxbone, SA and any dissemination, distribution, or unauthorized use is strictly
prohibited. All other trademarks are the property of their respective owner.
3. On the “Define the IP Address” page, confirm that “Enable IPv4” and “Use all configured IP addresses” are
selected and click next
4. On the “Define the root trunk” page
a. Confirm that “Trunk name” is the same as the IP address to the PoP
b. Under “Listening port for IP/PSTN gateway” enter 5060
c. Select “TCP” under “SIP Transport Protocol”
d. Select the correct Mediation server
e. Under “Associated Mediation Server port” enter 5060
Tel. +1 805 880 9800 Copyright © 2015 Voxbone
Email: [email protected] All Rights Reserved page 9 of 23
These materials are the copyright of Voxbone, SA and any dissemination, distribution, or unauthorized use is strictly
prohibited. All other trademarks are the property of their respective owner.
f. Click “Finish”
5. Repeat step 1-4 for all Voxbone PoPs
Configure Voice Routing Voice Routing is configured in the Skype for Business/Lync Control Panel and is accessed by clicking the “Voice Routing”
tab in the Control Panel. Since Voxbone only provides inbound calls, we only need to configure two of the categories,
Dial Plan and Trunk Configuration.
Tel. +1 805 880 9800 Copyright © 2015 Voxbone
Email: [email protected] All Rights Reserved page 10 of 23
These materials are the copyright of Voxbone, SA and any dissemination, distribution, or unauthorized use is strictly
prohibited. All other trademarks are the property of their respective owner.
Trunk Configuration
We need to create Trunk configuration so that the Mediation server will know how to handle the signaling and media
that comes from the Voxbone PoPs.
There are three types of Trunk configurations – global, site and pool. The server will apply the most specific
configuration to the trunk. This means that when the server decides which configuration to apply to a trunk it will first
check if there exists a pool configuration for the trunk, if not it will check for a site configuration. If no site configuration
exists it will use the global configuration.
Practically this means that
- If you are only using Voxbone PSTN gateways, you can use the global configuration
- If you have other PSTN gateways, but have put the Voxbone gateways in a separate Skype for Business site, you
can use a site configuration. This is not very likely
- If you have other PSTN gateways and none of the above applies, you will have to create a pool configuration for
each of the Voxbone PoPs.
In this example we will create a pool configuration
1. In Skype for Business Control Panel, click “Voice Routing” -> “Trunk Configuration” -> “New” -> “Pool Trunk”
Tel. +1 805 880 9800 Copyright © 2015 Voxbone
Email: [email protected] All Rights Reserved page 11 of 23
These materials are the copyright of Voxbone, SA and any dissemination, distribution, or unauthorized use is strictly
prohibited. All other trademarks are the property of their respective owner.
2. Select one of the Voxbone PoPs
3. Type a description and verify that
a. “Maximum early dialogs supported” are 20
b. “Encryption support level” is “Optional” or “Not supported”
c. “Refer support” is “Enable sending refer to the gateway”
d. “Centralized media processing” is checked
e. All other checkboxes should be unchecked
4. Click OK
5. Repeat step 1-4 for all Voxbone PoPs
6. “Click Commit -> “Commit all”, review the changes and click OK
Tel. +1 805 880 9800 Copyright © 2015 Voxbone
Email: [email protected] All Rights Reserved page 12 of 23
These materials are the copyright of Voxbone, SA and any dissemination, distribution, or unauthorized use is strictly
prohibited. All other trademarks are the property of their respective owner.
7. Verify that you get “Successfully published voice routing configuration”
If using the global or site configurations, the settings in step 3 will have to be set there.
Dial Plan
Since Skype for Business and Lync only support full E164 type numbering, the Dial Plan is normally used to ensure that
the users are only able to dial numbers that the server understands. It does this by applying normalization rules to the
number entered in the client, transforming any non-E164 numbers to E164.
Since we will not do any outbound dialing using the Voxbone trunk, we will not cover normalization rules. However,
Dial-In conference endpoints need to be linked to a region to be able to present the closest numbers on a users
meeting invite. We will configure Dial Plans to support two Dial-In conference numbers, Norway and United Kingdom.
Dial Plans are configured in the Control Panel
1. Click “Voice Routing” -> “Dial Plan” -> “New” -> “User Dial Plan”
Tel. +1 805 880 9800 Copyright © 2015 Voxbone
Email: [email protected] All Rights Reserved page 13 of 23
These materials are the copyright of Voxbone, SA and any dissemination, distribution, or unauthorized use is strictly
prohibited. All other trademarks are the property of their respective owner.
2. Fill inn
a. Name
b. Simple name will be filled in automatically
c. Description
d. Dial-in conferencing region
e. Leave the default Normalization Rule
Tel. +1 805 880 9800 Copyright © 2015 Voxbone
Email: [email protected] All Rights Reserved page 14 of 23
These materials are the copyright of Voxbone, SA and any dissemination, distribution, or unauthorized use is strictly
prohibited. All other trademarks are the property of their respective owner.
3. Click OK
4. Repeat step 1-3 for every dial-in conferencing region you want to create
5. Click “Commit” -> “Commit all” and verify the changes. Click OK
Tel. +1 805 880 9800 Copyright © 2015 Voxbone
Email: [email protected] All Rights Reserved page 15 of 23
These materials are the copyright of Voxbone, SA and any dissemination, distribution, or unauthorized use is strictly
prohibited. All other trademarks are the property of their respective owner.
6. Verify that you get “Successfully published voice routing configuration”
Tel. +1 805 880 9800 Copyright © 2015 Voxbone
Email: [email protected] All Rights Reserved page 16 of 23
These materials are the copyright of Voxbone, SA and any dissemination, distribution, or unauthorized use is strictly
prohibited. All other trademarks are the property of their respective owner.
NOTE: If you have outbound PSTN gateways, these Dial Plans will probably already exist. In that case, verify that the
Dial-In Conferencing region field is populated on each of the Dial Plans where you will have dial-in access numbers.
Dial-in Access numbers
To be able to receive incoming calls to a Skype for Business or Lync conference, we will need to configure Dial-in Access
numbers. These will be linked to the dial-in conferencing regions we created on the Dial Plans.
Dial-in access numbers are configured in the Control Panel.
1. Click “Conferencing” -> “Dial-In Access Number” -> “New”
2. Fill in
a. Display Number
b. Display Name
c. Line URI – This needs to be on format tel:+{e164}, example tel:+4712345678
d. SIP URI – This is the internal Lync URI for the endpoint. Needs to be on format
sip:[email protected], example sip:[email protected]
e. Select the Front End pool that the endpoint will be homed on
f. Select the Primary language for the endpoint
g. Click “Add” and select any other languages that will be supported on this endpoint, max 4.
3. Under “Associated Regions”, click “Add” and select the corresponding region from the Dial Plans and click OK
4. Click “Commit”
5. Repeat step 1-4 for all dial-in access numbers
Display Dial-In conferencing numbers on meeting invites
Enterprise Voice Enabled users
Enterprise voice enabled users will have a Dial Plan assigned to them as part of their Enterprise voice configuration.
Ensure that all Dial Plans are associated with a Dial-In conferencing region to display the Dial-In conferencing number
closest to the user on their meeting invites.
Tel. +1 805 880 9800 Copyright © 2015 Voxbone
Email: [email protected] All Rights Reserved page 17 of 23
These materials are the copyright of Voxbone, SA and any dissemination, distribution, or unauthorized use is strictly
prohibited. All other trademarks are the property of their respective owner.
Non-Enterprise Voice Enabled users
Normally a user not enabled for enterprise voice will not have the Dial-In access numbers displayed on their meeting
invites. To enable this, we need to grant them access to the Dial Plan for the number that is closest to where they are
located. This can only be done using Powershell. We use the following cmdlet to configure this:
Grant-CsDialPlan <username> -PolicyName <dialplansimplename>
This can also be combined with other cmdlets like this
Get-CsUser | Grant-CsDialPlan –PolicyName Norway
This will grant all enabled users access to the “Norway” Dial Plan.
Further, we can use this command to filter the users. So to grant all users in the “Norway” OU access to the “Norway”
Dial Plan we can use these cmdlets
Get-CsUser –OU “OU=Norway,DC=vox,DC=lab” | Grant-CsDialPlan –PolicyName Norway
We can also filter on ldap attributes.
Get-CsUser –LdapFilter “c=no” | Grant-CsDialPlan –PolicyName Norway
Will grant all users with the AD field “Country/region” set to “Norway” access to the dialplan
Full documentation of the Get-CsUser cmdlet is available here: https://technet.microsoft.com/en-
us/library/gg398125.aspx
When set, the user will have the nearest number displayed in meeting invites
If the receiving user clicks the “Find a local number” link, they will be taken to the dialin conferencing web page where
all configured dial-in access numbers will be listed together with conference control DTMF codes.
Setting the users PIN code
If the users are dialing in to their own meeting from a telephone instead of a Skype for Business or Lync client, they will
have to authenticate themselves as meeting leader. Setting the PIN code can be done in several ways
- Skype for Business/Lync Control Panel
- Powershell
- The user can set it through the Dial-In page
Tel. +1 805 880 9800 Copyright © 2015 Voxbone
Email: [email protected] All Rights Reserved page 18 of 23
These materials are the copyright of Voxbone, SA and any dissemination, distribution, or unauthorized use is strictly
prohibited. All other trademarks are the property of their respective owner.
Dial-In web page method
If the user is enabled for enterprise voice, they can set the PIN themselves from the Dial-in page. This is not possible for
users not enabled for enterprise voice. The users need to sign in to the page and follow the instructions there.
Control Panel Method
1. Open up Control Panel and click Users
2. Search for the user you want to set the pin for
3. Mark it and click “Action” -> “Set Pin”
4. Click “Automatically generate a valid PIN” or “Manually enter a specific PIN” and click OK
Tel. +1 805 880 9800 Copyright © 2015 Voxbone
Email: [email protected] All Rights Reserved page 19 of 23
These materials are the copyright of Voxbone, SA and any dissemination, distribution, or unauthorized use is strictly
prohibited. All other trademarks are the property of their respective owner.
5. If you click on “Show PIN” the new PIN will be displayed. If you run Control Panel from a computer with an
email client installed, you can also create an email and send it to the user.
6. Click close
The disadvantage of using the Control Panel method is that it is not possible to set PIN codes in bulk, it is only possible
on a single user at the time.
Powershell method
By using Powershell we can set the PIN in bulk. The cmdlet used is
Set-CsClientPin <username> -PIN <pin>
If –PIN is not specified, a valid PIN will be generated. We can also combine this cmdlet with Get-CsUser to bulk set the
PIN
Get-CsUser | Set-CsClientPin | Export-Csv c:\temp\userspin.csv
Will automatically generate a PIN and export them to a CSV file so they can be distributed
Documentation of the Set-CsClientPin can be found here:
https://technet.microsoft.com/en-us/library/gg398929.aspx
Tel. +1 805 880 9800 Copyright © 2015 Voxbone
Email: [email protected] All Rights Reserved page 20 of 23
These materials are the copyright of Voxbone, SA and any dissemination, distribution, or unauthorized use is strictly
prohibited. All other trademarks are the property of their respective owner.
Configure Voxbone portal
Purchase numbers and channels
Before you can configure numbers and URIs for Skype for Business/Lync, you will need to order numbers and channels.
This is covered in this document: https://www.voxbone.com/resources/Voxbone%20User%20Guide%20-
%20Ordering%20v2.1.pdf
Configure Defaults
This will configure the default settings for your numbers.
1. In the Voxbone portal, click “Configure” –> “Default”
2. Set
a. Default PoP: set it to your closest PoP location
b. Under Media
b.i. Select “RFC 2833” as DTMF Delivery method
b.ii. Verify that at least “G711a” and “G711µ” under “Narrwoband Voice Codecs” are checked
b.iii. None of the other mediacodecs are needed for Skype for Business/Lync, so you can uncheck
them if you want
Configure URI
When you have gotten assigned numbers and channels the first thing that needs to be configured is the URI that
voxbone will link the number to. This is the URI that will be presented to the Mediation server.
1. In the Voxbone portal, click “Configure” -> “URIs” -> “All URIs”
2. In the “Create or modify a voice URI” box, enter
a. URI: +{E164}@mediationserverIP;transport=TCP, example +{E164}@94.246.xxx.xxx;transport=TCP
a.i. This will send the incoming call to the mediation server on port 5060 as
a.ii. If you want to use another port than 5060, you need to enter the URI as
+{E164}@mediationserverIP:port;transport=TCP, example
Tel. +1 805 880 9800 Copyright © 2015 Voxbone
Email: [email protected] All Rights Reserved page 21 of 23
These materials are the copyright of Voxbone, SA and any dissemination, distribution, or unauthorized use is strictly
prohibited. All other trademarks are the property of their respective owner.
+{E164}@94.246.xxx.xxx:5068;transport=TCP, this will send the incoming call to port 5068 on
the mediation server
b. Description: Enter a description for the URI
3. Click save. The URI will be listed in the table below
4. In the Technical Information box, enter the version and type of the Skype for Business or Lync server
environment and click “Save”. This will help improve support if needed
Configure numbers
The last task is to map the URI to your numbers. This page is available under “Configure” -> “Numbers”
To Map the URI to the numbers
1. Click the “Voice URI” tab
2. Select the URI that was created for the Mediation Server
3. Either
a. Click “Apply to all” to map this URI to all available numbers
b. Put a checkmark on the numbers you want to map and click “Apply to selected”
PoP
Verify that the PoP is set to the PoP that is geographically closest to your Mediation server. If not
1. Click the “PoP” tab
2. Select the PoP you want to apply
3. Either
a. Click “Apply to all” to use this PoP with all available numbers
b. Put a checkmark on the numbers you want to use this PoP with and click “Apply to selected”
Tel. +1 805 880 9800 Copyright © 2015 Voxbone
Email: [email protected] All Rights Reserved page 22 of 23
These materials are the copyright of Voxbone, SA and any dissemination, distribution, or unauthorized use is strictly
prohibited. All other trademarks are the property of their respective owner.
DTMF
Click the DTMF tab and verify that the DTMF method is set to “RFC 2833”. If not
1. Select the “RFC 2833” radio button
2. Either
a. Click “Apply to all” to apply RFC 2833 all available numbers
b. Put a checkmark on the numbers you want to use for Skype for Business/Lync and click “Apply to
selected”
Codecs
Click the Codecs tab and verify that at least “G711a” and “G711µ” is set on the numbers. If not
1. Check at least “G711a” and “G711µ”. The other codecs are not needed
2. Either
a. Click “Apply to all” to apply these codecs on all available numbers
b. Put a checkmark on the numbers you want to use for Skype for Business/Lync and click “Apply to
selected”
Testing The configuration should now be done and you can start making test calls to your numbers to ensure that they are
picked up.
Tel. +1 805 880 9800 Copyright © 2015 Voxbone
Email: [email protected] All Rights Reserved page 23 of 23
These materials are the copyright of Voxbone, SA and any dissemination, distribution, or unauthorized use is strictly
prohibited. All other trademarks are the property of their respective owner.
Appendix 1: Firewall Configuration
These are the default ports that need to be open in the environment:
Role/Protocol/Port Source IP Address Destination IP address Notes
SIP/TCP/5070 Front End Server Mediation Server internal SIP Signaling between Front End and Mediation
SIP/TCP/5070 Mediation Server internal Front End Server SIP Signaling between Front End and Mediation
SIP/TCP/5061 Front End Server Mediation Server internal SIP Signaling between Front End and Mediation
SIP/TCP/5061 Mediation Server internal Front End Server SIP Signaling between Front End and Mediation
RTP/TCP/UDP/49152-57500
Any internal Mediation Server internal Media between internal clients/servers and Meditation server
SIP/TCP/5060 Mediation Server PSTN Voxbone PoPs SIP signaling between Mediation server and Voxbone
SIP/TCP/5060 Voxbone PoPs Mediation Server PSTN SIP Signaling between Front End and Mediation
RTP/UDP 49152-57500 Voxbone PoPs Mediation Server PSTN Media between Voxbone and Mediation Server
RTP/UDP 10000-20000 Mediation Server PSTN Voxbone PoPs Media between Mediation Server and Voxbone
NOTE: These are the standard ports used. Both SIP listening ports and Media ports on the Mediation server are
configurable. These may be changed in your deployment for various reasons, i.e. QoS configuration, and need to be
verified with the system documentation before deployment.
Visit https://technet.microsoft.com/en-us/library/gg398833.aspx for full documentation of all the default ports used
internally in a Lync and Skype for Business deployment.