SfB Broadcast: Ep. 51 Five tips for planning your time at Ignite–Session Summary

Seems i missed this broadcast last Friday but just noticed this posted on YouTube and thought it may help some folks going to Ignite, unfortunately ill be watching from afar.

YouTube Video – https://www.youtube.com/watch?v=6vWPBGj8ixM


Note before you go Episode!

First message from Delanda is a message regarding the impact to people with the recent hurricane and thought and prayers are with everyone.


Two guest today, Laurie and Praveen.

  • Laurie Pottmeyer – Community Manager on SfB & Teams Team
  • Praveen Maloo – product marketing manager on Microsoft team

I see the shift of the SfB broadcast series into Teams has already started!

Little bit about Ignite

  • Microsoft largest conference
  • every year
  • Orlando, Florida
  • WC 25th Sept
  • 6 Days



1000s of hours of content on all Microsoft Content, windows, surface, xbox, SfB or Teams lots of content.


Slide on all things going on, demos, happy hour, customer success, show cases, ask the experts etc

If you cant be there in Person LIKE ME then watch out for ways to watch on demand and broadcasts

1st TIP – Attend the general session


Attend general session on SfB and Microsoft Teams only

Session two speakers


Lori and Bob.

Monday 4pm after initial keynote!

Laurie and Praveen excited

23K attendees largest tech event

TIP 2 – Plan to attend session across Teams & Skype for Business


Over 45 session on Teams and SfB!


List to help to prepare and what to focus on.

Quick break down of key pillars

  • Overview sessions and introductions
  • Deep dive sessions – talk about portfolio from meetings to voice, collaboration, security
  • Adoption and deployment sessions, best practices
  • key success stories

IT Pros level 300 and 400 – network planning and bandwidth, troubleshooting, video interop

How to build schedule today ?

Be prepared when your there

  • Ignite website there is a schedule builder!
  • Mobile App as well



  • You can login and build schedule
  • filter sessions topics and levels
  • Break down products
  • Add to schedules and view open slots and recommendations will be suggested
  • Make sure you update your profile this helps maps sessions to you

TIP 3 – ask the experts or watch is live from Ignite!


If you wont be there general sessions will be recorded and available after.

The show will be going to podcast studio


Schedule above, Jamie original host of this show.

Josh Blalock with views from Community and MVP

  • Wednesday 1PM
  • Thursday 11am

Microsoft Mechanics session as well.

Also cool give always and Surface laptops

TIP 4 – Join the community activities


Microsoft Tech Community to get together

Expo Booth


  • MVP
  • Product Team
  • Demos
  • Swag

Make sure to stop by the booth

This is a community central and is spot of expo floor down the hall and that is a s opportunity to come and speak to people about community and tech community.

Wednesday 11-2pm SfB and Teams representation of Office take over day! Play ping pong and have fun!

If you not there

8.30 – 5.30 EST time live events streamed and all sessions recorded and easy to ignite.microsoft.com for all sessions and live streams

Social channels

follow on Twitter and Facebook to get latest and greatest updates

Make sure you join Tech community as well

Rolls into TIP 5

TIP 5 – Follow our MVPs


MVP are most valved professional or know the insides of the product and engaged in Community and Laurie owns this

Announcement for MVPs

1st time to let everyone know of new MVP for Teams


SfB and Teams fall under Office Serer and Servers

Awarded month of September

first official Teams MVPs

and SfB MVPs

David will be in Orlando and make sure you say hello

Other fun things

13 MVPs representing 26 sessions

Blogging sessions



You can watch videos, live streams and MVPs will blog content as well.

Also have 15 community reporters covering all products and services


Tom representing Teams and SfB reporting, be sure to check out Tom and all on twitter. Follow Tom on twitter and tech community links.




Those are the 5 tips for Ignite!

Q and A time

1. How do i become MVP teams and SfB

go to mvp.microsoft.com and learn all about the program and what it means

Also where you nominate yourself or someone can nominate you monthly. Trigger email for form things to look at

Social presence




Product feedback

If nominated continue to put activity in tool and revisit it.


2. Cant go to ignite how can i get involved in other ways

Join UC User groups

17 UC User groups and meet quarterly SkypeUG.com


3. How do i connect with Laurie and other member here today

Microsoft Tech communities

@msdelanda on twitter



Look forward to seeing everyone in Ignite

1. General Sessions

2. Make sure you plan for breakouts

3. Watch us live

4.Join community activaties, talk to experts

5. Follow the MVPs



Also on Ignite make sure you check out Mark Vales Blog on getting Microsoft Teams set up for Ignite! here, check out the RSS feeds, twitter hastags etc



Skype Academy presents : Media Bypass in Cloud Connector Edition V2 (CCE) Summary

Next up on my summary list following CCE V2 is Media bypass session by Carolyn Blanding link here to the full video here

If you want to plan and deploy CCE check out the links in this post as well.

For Media Bypass with CCE you need CCE v2 and Supported clients!

With the first release of media bypass, the only supported client is the Skype for Business 2016 Windows Client that is part of Office 365 ProPlus, version 16.0.7870.2020 or greater.

Lets go!



Training disclaimer, this session recorded July 2017 and features described are current as of this date. Office 365 is on going innovation.


About Carolyn, she’s been with Microsoft for 5 years, senior supportability program manager. Member of extended hybrid voice team and working with developers on CCE.

Key Learning’s





Also check this https://technet.microsoft.com/en-us/library/mt808733.aspx

Without Media Bypass



In order to plan your network for media bypass we need to understand both signalling and media flows

  • Media and Signalling without media bypass
  • All signalling and mediation go via Mediation server

SfB client connected on internal network and making outbound call the signalling flows out the client and out the external network to office 365 and back from Office 365 to corporate Edge server to mediation server to the SBC. Media traffic goes from client though internal corporate firewall to mediation server and then transcoded as G711 to SBC.

With Media Bypass


Signalling continue to flow via Mediation but media will flow from SfB client directly to SBC / Gateway.


Removed connection points (Hops) for Media going through firewalls and server

Benefits of Media Bypass


As we saw before we can improve quality by reducing latency, packet loss and single points of failure by allowing media to flow directly to pstn gateway from the SfB client and also reduce number of CCEs as Mediation server is removed so no transcoding from one codec to another is required so then allow larger number of voice streams on the same hardware. Win Win !

Network Considerations


First important to understand with Media bypass enabled on the client media will ALWAYS bypass this is different to on premises SfB Server / Lync Server deployments. where is is possible to configure when media will bypass per network location. CCE media bypass is always bypass mode.

External clients and unsupported clients will never use bypass so important to know how users will connect, numbers of external and also client versions (I believe from what ive read only click to run SfB client supports CCE Media bypass)

Requires direct connectivity to the PSTN gateway!

Media over VPN is not supported this doesn’t differ from SfB server, if you block media over VPN you need to block all traffic ! recommendation block all SfB from VPN connections.

Client to PSTN gateway traffic typically uses G711 codec, inbound calls mediation server will negotiates G711, outbound gateway negotiates.

Centralised CCE Deployment

More great on the TechNet link for planning media bypass https://technet.microsoft.com/en-us/library/mt808733.aspx


Need to consider G711 will transverse the WAN twice, CCE in central DC with local SBCs in local offices, centralised SBC with cloud connector routes calls to local gateways.

This type G711 media traffic for media bypass clients will transvers the wan twice

1. client media flow associated with CCE deployment


2. outbound from sbc through same wan in office to sbc / gateway out to the PSTN


Centralised Deployment – External Caller


User from Zurich on the Internet, places outbound, both signalling and media flow to office 365 through external firewall in Amsterdam to CCE through internal network to SBC Gateway in Amsterdam over the corporate WAN to Zurich to SBC and pstn in local branch office.

Configure Media Bypass


Also check this deploy guide on TechNet https://technet.microsoft.com/en-us/library/mt808734.aspx


Each CCE Mediation server has a web service to provide media bypass information that is configured as part of V2

Summary of steps

  • Detailed in the following slides
  • Administrator defines web service url for web service
  • Admin creates DNS A Record in internal dns for this url resolving to the ip address of each mediation server
  • Administrator enabled media bypass using SfBO PowerShell
  • Media Bypass settings replication to cloud connector mediation servers
  • Internal supported clients sign out and back in to pick up media bypass settings

Web Service URL


Admin defines web service url for media bypass

Pick a name that could be anything hybridvoice,mediabypass as examples, name can be in any domain namespace can be any internal domain name that resolvable in internal dns.

Does not need to be in a namespace that matches CCE deployment

Only one name is defined per deployment. we don’t need separate for separate PSTN sites.

Above they have used hybridvoice.contoso.com and there is an example of the URL, your webservice would be the same after .com

http is used to avoid admin overheard, as only returning information to internal client. DOES NOT RESOLVE TO EXTERNAL CLIENTS



Client are required to resolve internal DNS, so it can resolve the host name to mediation server ips.

One host A record for IP of mediation servers

Each mediation requires a host record

with 3 mediation servers you need three a records resolve to web service url.

recommendation to use Geo DNS to resolve local mediation servers ips based on client location. recommendation not requirement.

Single Web service url resolving to ips of all mediation server.

Windows 2016 Geo DNS


Windows Server 2016 can provide GEO DNS for the web service url

A sample config is above

  • First creates dns client subnet for each locations
  • DNS zone scope for each location
  • DNS records in each zone scope for each mediation server
  • DNS policies that connection client subnets to matching zone scopes, please reference url for further info


Enable Media Bypass in O365 Tenant


admin manual enables on Office 365 tenant by using remote PowerShell with SfB admin creds and sets the internal web service url as defined previously.

Use set-cstenanthybridconfiguration cmdlet as defined above

Second you need to enable mediabypass settings in two steps

  • create bypass settings in memory $mediabypass = New-csNetworkMediaBypassConfiguration –Enabled $true
  • modify network configuration with the new settings. Set-CsNetworkConfiguration – MediaBypassSettings $mediabypass

Confirm Media Bypass


After enabling you should confirm is configured correctly.

Confirm Media Bypass – On SfB Online


First confirm SfB Online Media bypass settings in remote PowerShell

Confirm the web service url is replicated to the local server store using get-cstenanthybridconfiguration –localstore | select hybridconfigserviceinternalurl hybridconfigserviceinternalurl

here you can view the webservice url

Then confirm media bypass settings replicated to local server store

get-csnetworkconfiguration –local | select-expandproperty Mediabypasssettings

Two settings to check

1. Enabled is true

2. Bypass ID – this is the bypass id clients should be received. this is different to online bypass id. All tenants and all users in V2 will use the same ID.

Confirm Media Bypass – On CCE


On admin PowerShell on each CCE Mediation server and run

Get-CsNetworkConfiguration – localstore | select –ExpandProperty MediaBypassSettings

Check three things here

  • Enabled is True
  • AlwaysBypass is True (Always True. this is static setting)
  • BypassID – Same bypass ID as before

Confirm Media Bypass in Calls

Option 1 – Performance Monitor


Configure and use PerfMon on CCE Mediation Servers to monitor the following

  • LS:MediationServer – Inbound Calls – Total inbound media bypass calls
  • LS:MediationServer – Outbound Calls – Total outbound media bypass calls

Sample above has active calls, works well for basic but does not captures transfers, its good to get an idea of how calls are bypassing media.

Option 2 – Network Tracing


You can use a network trace to confirm network activity for calls, apply a filter to view traffic between client ip and PSTN gateway

  • When you traffic between client and PSTN gateway then bypass is enabled
  • If disable client would connect to mediation server and the mediation server connecting to the PSTN Gateway.

Option 3 – Tracing Logs


You can check for bypass if trace logs and search for a=x-bypassid

three items per call

  • invite: SDP
  • 183 session progress: SDP
  • 200: OK

Open traces with snooper.

Media Bypass in Clients


Detailed look into clients

Supported Clients and obtaining media bypass settings


Clients retrieves web server url during in band provisioning

  • client resolves hostname
  • then client connects to web service url
  • if connection successful and client supported version then bypass will be enabled and bypass id set
  • if not successful media bypass will be disabled

note if client connected in external network (Internet) then the client MUST NOT resolve the web service URL. if resolvable there would be issues.

Troubleshooting supported clients


If client are not making media bypass clients

first checked hybrid voice url is being picked up by client – check this is log with snooper

Sample trace log for user


Zoom in on important bit


Here you can see the url from the trace tab in snooper. Here the client has received the web service url.

Next check DNS resolution for the web service name.

Use command prompt and ping the url and the mediation server ip is resolvable and reachable

Perform web traffic trace to make sure the web service url is successful.

Demo web capture using Charles you can also use fiddler to trace


First check build number on client


Greater than supported 7870.2020 so were good

Check IP config of the client and confirm on internal network


Next sign in with web tracing enabled


Check web service url is contacted and also bypass enabled is true


you can also see the bypass id of the mediation server

Next confirm the media is bypassing

Check Client IP again –

Check SBC IP – and is pingable


Lets make a call


From network trace it show media flowing directly from client .123 to SBC .8


Media is going directly between client and SBC.

Client Bypass Log Details


Open log file from tracing file with snooper

Look at bottom of SDP for bypass id

180 ringing we will use gateway SDP of

Service out record for VQ report for local user agent, client agent , mediation bypass flag is true.

What about unsupported clients ?


Windows desktop 2013 and SfB unsupported version will attempt the URL and CCE will check version and disable media bypass.

Also other client 2010, mobile and mac there is no logic and will not attempt to connect to the web service url and media bypass disabled.

Unsupported client walkthrough



Check Client version and this the Lync 2013 client upgraded to SfB using Office Pro Plus 2013 (this is an unsupported client)

Clients signs in


Check and we see successfully connection to web service url BUT bypass is false and OFF


Client Media Connectivity Failures


If you have implemented media bypass and you are having call failures

Call rings but client says connecting, signalling via mediation is working but media is failing to connect to PSTN gateway

Confirm is client and PSTN gateway can connect (ping)

Collect logs on CCE hosts admin PowerShell and reproduce scenario

Invite and SDP logs

Network trace to define network failure

Review gateway logs could be failure on gateway and not on your network












More great material !

TechNet Plan for Media Bypass with CCE v2


Deploy Media Bypass with CCE v2


SOF: Number Porting Training Summary

Great to have training for people on their SOF journey for number porting and the importance and timelines for planning and setting the right expectations. One important note is that timelines, process and potential delays are industry wide and not just for porting to Skype for Business Online.

Also making sure you submit the correct information is key! as incorrect information can start the number porting process again and can lead to huge time delays. So check check check, got your mate to check and his mate before you submit.

Also planning for porting subscriber numbers for users and service numbers for Calls queues, auto attendants and PSTN conferencing numbers is key to know upfront.

Other useful Number Porting Links



Link to video here




SOF is a living framework and feedback is important, this is April 2017 version of this training. This training is subject to Change.

Check out out SOF for latest content.



Provide information on updates on SOF as part of Plan, deliver and operate.

Plan for number porting


Why ?

Number porting will increase with new Org AA and Call Queues

Understanding number porting will help with project timelines


This training assume you know SOF

Number porting is mostly policy based

include planning for number porting in your SOF journey



When do you need number porting ?

With PSTN Calling you can use new or port existing

subscriber number assigned to end users

service number assigned to AA, call queues and PSTN conferencing

UK you cannot port non geographic or shared telephone numbers

List of service providers for Porting available. (This links / info seems to be gone missing which is odd. I’ve seen this list before but its not available now it seems)



Carriers may define their own timelines


Setting the right timelines expectations is important.

These challenges are throughout the whole industry not just porting to SfB Online



Can take up to 30 Days!


Takes 17 days to get a port order scheduled in this example !

I like this diagram as it show the amount of processes for a single port and show multiple carriers involved.

The LOA must be completed with the correct information



Number porting added as critical project risk

Number porting challenges is industry wide not just to SfB Online

Full port and partial porting only applicable to US.


Full Port not available in all countries. This is available in the US.

All numbers usually as subscriber numbers

You can change a subscriber number to a service number with a support ticket open and will trigger another number port.

Office Main Line numbers will likely need to be service numbers !

Option 1 – Port all subscriber number then raise ticket to port some numbers to service numbers. Downtime required.

Option 2 – partial port of subscriber number then port remaining numbers as service numbers. Takes longer to port from existing carrier. Advantage is downtimes is minimised.



No updates to deliver phase.

Set correct project timelines based on decision in plan phase.



Skype Academy presents On-premises PSTN connectivity using Cloud Connector Edition (CCE) Summary

In the series of Cloud PBX Skype academy videos this is Cloud PBX using on-premises PSTN connectivity using Cloud Connector Edition (CCE). This is where you don’t have an existing Lync or Skype for Business Server deployment so greenfield but you have the requirement to use your existing PSTN connection with Cloud PBX.

CCE is a smaller footprint on premises deployment than deployed a full server deployment. Users are all homed online and CCE is used to connect to your on premises PSTN for Cloud PBX users.


Brian nice, principal program manager in Skype product group at Microsoft.

This is based on CCE version 1.4.1 release

What is Cloud Connector and Architecture


Cloud Connector is an extension to SfB Online Service

provides PSTN interconnect for SfB Online users.

Users are homed in SfB Online but PSTN is coming via the on premises Cloud Connector. User still leaves in the cloud but interconnect for PSTN is deployed on-premises.

Cloud connector is a dedicated hypervisor running Hyper-V that has set of sealed virtual machines (4), the VMs perform discrete functions such as Edge, Mediation server, domain controller and CMS.

This is a dedicated appliance and the components work in tandem with each other. The Active Directory deployed in CCE is for the its own environment it has NO communication or integration with an existing on premises active directory. Its its own forest.

The appliance has sip trunks to PSTN Gateways, dial plans is assigned online based on where the user is located. There are options online to restrict internally dialling.

External DNS (SRV and lyncdiscover) is pointed to SfB online not on premises! (There are External DNS records required for CCE but client discovery is pointed to SfB Online)

Key to note in version 1.4.1 there is no support for co-existence with an existing on premises Lync or SfB Servers. Key to note.

There is no media bypass so media always flows via the mediation server!

Users can be created on premises or created in the Cloud. Most organisations will have AD sync via Azure AD connect so users are synced to online.

Below Johns signing in to Skype for Business Online, his SfB client talks to SfB online when John makes a PSTN call now the call signalling is routed from SfB online down to Cloud connector. The call signalling from SfB Online infrastructure to CCE edge to CCE mediation to CCE PSTN GW.


Media traffic will flow via CCE Edge as John is external and on the internet then from CCE Edge to CCE Mediation then from CCE Mediation to PSTN GW.

Media bypass cant be used as discussed earlier




Follow TechNet documentation using the link below


Also worth checking is Skype operations framework

Capacity and PSTN connectivity types are key as these can be different at each site.

Firewall – make sure all required ports are open.

Make sure you have your office 365 Administrator credentials.



Critical one to start with no existing on premises deployment of Lync or Skype for Business server deployed on premises. The current version does not support co-existence!

Qualified PBX / SIP trunk / SBC / Gateway for a full list go here

Dedicated hardware is required for hyper v. the hardware is dedicated for CCE.


Capacity is key and with two different flavours based on hardware specs.

  • Large – typically 500 calls per cloud connector
  • Small – 50 calls per cloud connector (Great for Proof of concepts or smaller call concurrency site requirements)

Hardware spec from above URL

The necessary hardware to support installation of the 4 VMs for each Cloud Connector Edition in your deployment.

  • The following configurations are recommended: (Large 500 simultaneous calls)

    • 64-bit dual processor, six core (12 real cores), 2.50 gigahertz (GHz) or higher

    • 64 gigabytes (GB) ECC RAM

    • Four 600 GB (or better) 10K RPM 128M Cache SAS 6Gbps disks, configured in a RAID 5 configuration

    • Three 1 Gbps RJ45 high throughput network adapters

  • If you choose to deploy the smaller version of Cloud Connector Edition that supports up to 50 simultaneous calls, you will need the following hardware:

    • Intel i7 4790 quad core with Intel 4600 Graphics (no high end graphics needed)

    • 32 GB DDR3-1600 non ECC

    • 2: 1TB 7200RPM SATA III (6 Gbps) in RAID 0

    • 2: 1 Gbps Ethernet (RJ45)

General guidelines, you can up to four Cloud Connecters per PSTN site.

PSTN site is defined in cloud connector when registering. If you have N+1 model with 500 per CCE and 3 active and one idle that gives 1500 simultaneous calls.

N+1 allows for one CCE to fail and still keep 1500 simultaneous call. You could go for all 4 CCEs active and have max 2000 but if one failed you will lose 500 straight away and there’s a risk.

With smaller CCE you can do the same but call capacity is lower with 50 calls per cloud connector, with N+1 again 50 * 3 = 150 simultaneous calls.

Deployment Planning


Host server runs Hyper-V and require internet access, public DNS resolutions and remote PowerShell.

GPO required to prevent forceful unload of user registry at logoff.

Base VM requires internet access and public dns resolutions

External DNS records are required for CCE Edge server and with HA if you have 3 CCEs in one site in HA then you have to have that edge name listed three times. External DNS is critical.

External certificates are required, certificate requests and have certificate available in .pfx format so it can be imported as part of the installation process of CCE. Details available here

CloudConnector.ini – CCE Configuration file


The CloudConnector.ini is critically important and controls almost everything.

IP Addresses, small or large CCE.

Don’t mess this up if there is a mistake is a start over job.

There a deployment checklist, this is printable and recommended to be printed so all details can be written and ensured.


There isn’t a CloudConnector.ini file by default but you can generate one as noted above using export-ccConfigurationsamplefile.

You have to have this file updated before you create a base VM and you need the values for the base VM and the base VM needs internet access.

There’s alot of settings in the .ini recommended to visit here


HA and Multi side Planning considerations


Really important if designing with HA and multi site in mind that you consider the information above. Some parts are the same and some are not with multisite.

Single site with HA (Multiple CCEs up to 4)

Shared folder – same shared folder on all CCEs instances

Virtual machine domain – same across instance

SIP domains – same

Site name – same as they are in the same site

External FQDN – (Access edge) same across all CCEs instance in the same site

External IP – different across instances

Hybrid tenant – peer destination is where a call exits office 365 it needs to know where to send the traffic to the edge single site. Multisite you can set failback as multiple sites.

Firewall Requirements – Internal



When deploy CCE appliance these are deployed in a DMZ as they need to allow connections from Internet and also be able to communicate with internal network.

Usually there will be an internal firewall protecting internal networks this table is for the internal firewall. so mediation server to PSTN Gateway.

Talk across internal firewall to internal network.

Default port range marked by * above this the default port range on mediation 4 ports required per call. These can be adjusted.

Gateway port is an example could be 5060 or 5061 this needs updating as required.

You can limit port ranges as well.

Firewall Requirements – External (Minimum)


There are the minimum ports required for external side of CCE this is between the internet and the external firewall. If you follow the minimum there may be some hair pinning issues.

Firewall Requirements – External (Recommended)


Here you can see the Cloud Connector Edge external interface is different, this allows for optimal media flow.


Following the planning is time to prepare the first host appliance and follow the steps above. Items in bold are required for first appliance only.

The share needs permissions for all CCEs in the same site.

Windows server 2012 iso is required to generate the base vhdx. this can be copied and pasted and used for other appliances.

Public certificate required upfront.

All appliances will be registered prior to deploying them, this registers with Office 365 so Office 365 is aware of all appliances in the site.

Last of all configure the PSTN gateways.

Deeper dive in to deployment


Who do we register ?

Management and HA.


i can view the PSTN sites and then view access edge for each site and if auto update is enabled.


All appliances need to know about each other for HA, by registering the appliance we know all the mediation servers on all appliance in a PSTN site.


Two different appliances with two different mediation server.

You can export this information as well and view


High Availability


You can have up to 4 Cloud Connector per one PSTN calling site.

Calls are distributed in random order between the cloud connectors. In the image below CC 1 and CC 2 are two different appliances.

Capacity planning is key, Large 500 per CCE 4 * 500 = 2000 with N+1 = 3 * 500 = 1500 allowing for one CCE to fail

Johns signs into Office 365, johns calls a pstn number, this call will be routed to the PSTN via CCE, johns account is assigned to a PSTN site so when call does out the online infrastructure will route out to one of the CCE edges then from edge to mediation to PSTN GW.

Media is sent edge to mediation and mediation to PSTN GW.


Second user signs into Office 365 and this time the call is routed to CCE 2 on the same site and signalling and media flow is the same.


Manage HA Mediation Pool


First you register then install and all is working, all mediation knows about each other.

But now i want to add more and add a third

so i register, the third appliance knows about all of them but the first two don’t. On the first and second appliance we need to update their configuration  by running publish-ccappliance cmdlet and this instructs existing appliances to update their topology and it will show a third was added.

What happened if i need to remove one we now unregister from Office 365 and again we need to publish and ensure the remaining appliances know one has been removed.

Media flow – outbound PSTN call from internal user


Dave is on internal network, he signs into Office 365, now he makes external pstn call, when the call reaches Office 365 first it does reverse number lookup to check if its a number for a sfb user, its not so the call is routed to Cloud Connector so its routed to Dave sites Edge, then mediation then gateway.

Media – Dave is inside the network so the media can be sent to the mediation server direct. Dave cant send his media direct to PSTN gateway as media bypass is not supported.

Media flow – Inbound PSTN call to internal user

Inbound call comes into the PSTN GW and into the mediation server then to the edge server then to SfB Online and then SfB online looksup the number and finds this is Dave and send an invite and can answer the call.

The media will go PSTN gateway to CCE Mediation then to Dave as he’s internal.


Gateway Affinity


On premises you have M:N one mediation pool can talk to multiple gateway and multiple gateways can talk to multiple mediation servers.

Same with Cloud Connector, All PSTN GWs can talk to all Mediations, PSTN GW chosen is round robin, If GW1 cant accept call it can be rerouted. With HA CC you need multiple GWs.

For planning you also need to consider PSTN GW and PSTN capacity.

Multi site scenario


Multiple Cloud Connectors with multiple sites.

Above Seattle (PSTN Site 1) within this site it has two Cloud Connector appliance deployed this provides HA

Secondary site Amsterdam (PSTN Site 2) also with multiple Cloud Connectors deployed.

Here we can assign users to specific sites. John is assigned to PSTN site 1 and Komanal is assigned to PSTN site 2.

Johns calls will go via PSTN site 1 and Kormmels via PSTN site 2

There is NO DR between sites. In the event Amsterdam (PSTN Site2) goes offline there’s no automatic failover so calls go out the US (PSTN Site1). This is manual DR but considerations for inbound calls are required.

You can change the users site associated to PSTN site 1 but this would work only for outbound as inbound relies on Sites 2 PSTN connections. Also remember calls will be routed out of another country which could have legal implications and network latency may not be optimal.

Post Deployment


Once all appliances are deployed and ready to go, you configure your tenant and enabled sharesipaddress space and set peer destionation and useonpremdialplan to false.

Best practice to assign users to PSTN sites but –peer destination is a failback.

New in 1.4.1 is auto updates, this automatically update the hosted and machines and Cloud Connector edition, auto updates takes care of this.

You need to configure a time windows for these updates to occur in. As improvements are made to the SfB Online service auto update will keep CCE inline as well.

It builds a new set of VMs in the background side by side and then drain active traffic and switch to new VMs. Existing VMs remain in place incase we need to switch back to them.

Thinks of the VMs as sealed VMs so don’t add antivirus or customise them as they will be replaced. Host can have AV but vm are sealed.

Post Deployment – Auto Update Configuration


Check its enabled and then check when its enabled for.

You can create custom autoupdate time windows and defines days and week and time.

you can have up to 20 custom time windows

You need to assign the custom update time window to the PSTN site.

Post Deployment – Configure Users


Now for user you need to assign cloud PBX licence and enable users.

Dial in conferencing is from the service you cant bring a conferencing number with Cloud Connector. It comes from PSTN Conferencing from SfB online only.

Voicemail is provided by Azure Voicemail, Exchange UM does not provided voicemail services, but the client wants part of Exchange UM enabled.

Assign user to PSTN Site (Case sensitive) this is where you associate user to cloud connector site.

You can restrict international calls as well.



Cloud Connector has a management service for auto recovery, auto update and event viewer has CceManagementService

The management service can show errors on remote PowerShell sessions


Above you can see Registration status is showing error and then an error message is displayed RTCSRV not found or not running

The management service can try and recover these and below its fixed it.

Updating to version 1.4.1


Recommended to upgrade to version 1.4.1 if your running an older version, 1.4.1 would be the last manual upgrade method.

You need to uninstall older version from host and install the new version.

You need to get new .ini file version and make sure its updated with your information on each cloud connector. The upgrade process is straight forward. start download, register and install with upgrade switch.

With existing HA do one at a time.

You can update credentials as well.


Skype Academy Presents Cloud PBX with on premises PSTN via on premises server Pool Summary

Another in the series of the Cloud PBX technical training available on Skype Academy.

This is a summary of the Cloud PBX with on premises PSTN calling session. Name a little confusing but its covering Cloud PBX with on premises PSTN via on premises server Pool

This scenarios is where you have an existing Lync Server or SfB Server deployment deployed on premises and also have requirement to use existing PSTN connection deployed on-premises. Cloud PBX users are homed on SfB Online.

Lets go!


As always the training disclaimer


Cloud Features and functionality is subject to change and new features are continually being added so important to ensure you look out for the latest training videos. This is Jan 2017 and again presented by Thomas Binder, senior Program manager in Customer experience and deployment team


Topics for this session


Key Learning’s


Use Cloud PBX with your existing infrastructure and on premises PSTN connections which may still be in contract.

Phased transition  of moving users to Cloud PBX

Important to enable users on premises first and then move to Office 365.

What’s in scope for this training?


Similar to Cloud PBX introduction here is structure of training available and this is the session for on premises PSTN connectivity. White boxes are training sessions and blue are for structuring purposes only.

Goal to understand Cloud PBX via on premises pool




Allows you to use existing Lync / SfB server on premises to connect to the PSTN and place and receive calls.

You must have hybrid with SfB Online and share the same sip domain.

This allow you to move users seamlessly between on premises and online depending on users requirements

For Cloud PBX with on premises PSTN connectivity users will be required to be move online but the online users can leverage the on premises PSTN connection.

Signalling and media, once user is homed in SfB online all signalling for user will go to SfB online however for media will go directly to SfB on premises infrastructure.



Utilise existing environment, SBCs, PSTN contracts, PBXs

Users homed in Office 365 and leverage existing investments

Cloud PBX with PSTN calling may not be available in your region

Provides a simple migration path to SfB online and you can slowly migrate users to use Cloud PBX

Smaller hardware footprint / Less load on server as workloads on premises will move to SfB online such as signalling, meetings , IM and presence.

When to use Cloud PBX with on premises PSTN connectivity?


Touched on above but you could have users in a region where Cloud PBX with PSTN calling is not available. (Currently PSTN calling is only available in US, Puerto Rico, UK, France and Spain) more regions coming soon.

requirement to keep existing carrier contracts for example you could have a 5 year PSTN contract to preserve low call rates.

Slowly move users to Office 365 this is a great way to start and validate SfB Online and you can use existing investments on premises.



You need to meet all the requirements

  • Your existing Lync / SfB server deployment must have a SfB Edge server role deployed for external connectivity and federation enabled. (Not sure on the requirement for a SfB 2015 edge as i believe 2013 edge is supported for hybrid as mentioned here)
  • Front end and mediation servers can be Lync Server 2013 or SfB Server 2015
  • Server must meet Cumulative update requirement, latest update is recommended.
  • SfB need to be configured for Hybrid, more details here.
  • Active directory synchronization
  • Correct firewall config in place
  • Enterprise Voice deployed so mediation server role is deployed with PSTN connectivity fully configured.

On premises planning considerations


Mentioned above was the potential for reducing workloads and load on existing on premises infrastructure but there also potential for increasing load as well.

Reduced load can come from offloading meetings, pstn conferencing

Media by pass is not supported for Cloud PBX with on premises PSTN connectivity

PSTN calls for all users will need transcoding on the mediation server!

If you have media bypass enabled today and users are moved then there could be extra load on the mediation servers.

Service Numbers


Required for certain cloud pbx services and offers high capacity for call queues, Auto attendant and PSTN conferencing.

You can get new or port existing numbers.

You can have toll or toll free, toll means caller pays to call the number, toll free means you will pay for the call and PSTN consumption billing is required for this.

Telephone numbers – New of bring your own


New numbers are easiest method and is available via the Office 365 admin portal, user number and service numbers are available from supported countries, regions, cities.

You can bring your own numbers as well via porting process, where users can keep their existing numbers which will be moved to SfB online so no new business cards or communication of new numbers is required. More details are found in the Cloud PBX will PSTN calling session here

Consumption based billing


Very important for use of toll free numbers and important to ensure their is funds available otherwise services will not work. Funds can be one time or auto recharge, with one time funding you need to be very careful your funds don’t run out so auto recharge is recommended for safety and not to stop services.

Use for Toll free dial in conferencing, call queues or AA (CQ and AA in preview currently)

Dial out conferencing – dialling out to a country that not included in PSTN conferencing subscription

Users with Domestic PSTN calling plan that want to call internationally.

You can see that PSTN consumption although optional is used in a number of scenarios so be careful.

Call routing and call flows



Two scenarios

  • Inbound call flow
  • Outbound call flow

Inbound call flow

  • A caller calls a users the DDI / DID of the user, this use will terminate on premises PSTN gateway.
  • Call is first route to on premises SfB to check if the user is homed on-premises or online using AD lookup
  • Request is proxies out via the edge server on premises to SfB Online (using federation route, so signalling goes to SfB online)
  • From SfB all endpoints of signed in use will now ring.
  • Is the call is accepted, media is routed locally (if user is internal to the network) or through companies edge server (if user is external to your network)
  • If call rejected media is routed to Cloud PBX Voicemail (VM provided by Azure VM in Office 365)

Outbound Call Flow

  • The SfB User initiates a PSTN call
  • SfB client normalises the number based on assigned on premises dial plan
  • Client sends invite from Office 365 to On premises front end and then call is routed to PSTN



User hosted in Office 365

First client signs in and use DNS and in hybrid this point to on premises in step 2, the user will authenticate and redirect to Skype for Business online in step 3. The user signs in against Skype for Business Online. from this point forward all signalling will go to Office 365.

Peer to Peer Call Flow (Online user to online user)


Dave calls john, both users are online users, Dave types the phone number of john in his client, SfB does a reverse number lookup and finds john which the phone number and johns on SfB so don’t call via PSTN do a direct peer to peer to call. The invite is change from phone number to sip Uri. John is informed Dave is calling. Media will flow peer to peer. There are on the same network.

Peer to Peer (On premises user to Online user)


Kathy is homed on premises, she wants to call Dave, again she dial Dave’s phone number, the invite sent to FE server and again does reverse number lookup, FE discovers user is SfB online user so FE sends to edge server to Office 365 and invite is sent to Dave. Both users are internal so media will flow point to point.

Incoming PSTN call – SfB Online user on internal network


Dave receives an incoming call from PSTN to PSTN GW to FE, the FE find Dave is in SfB Online, signalling is sent to Edge Server to Office 365 and invite is sent to all endpoints. Dave answers call and media is established, media 5a flow from Dave whos local to Front end and 5b from FE to PSTN GW. Media cant flow directly from Dave to PSTN GW as media bypass is not supported with Sfb Online.

Incoming PSTN call – SfB Online user on external network (Internet User)


John is connected on the internet and connected to Office 365, incoming call from PSTN to PSTN GW, to FE to Edge server to Office 365 and invite goes to JOhn. Same process as internal user.

John answers call, John cant talk to the front end server so must speak to Edge server , to FE server to PSTN GW. If John cant talk to Edge server on premises then John may have to send traffic to Edge server in Office 365 then to the on premises Edge Server to FE to PSTN Gateway.

Media will stay as local as possible. John is external so must connected via Edge server.

Outgoing PSTN Call – SfB Online users on internal network


Dave wants to call a PSTN number, dave homed on SfB online, and signalling goes to Office 365, Office 365 attempts to do reverse number lookup if it matches a number for a user, it doesnt so it goes to edge server, front end server, FE check if dave is allowed to call this number and to check what PSTN GW to use. Media will go as direct as possible, Call goes from dave to Mediation to PSTN GW. No media bypass so media does to Mediation server first.

Outgoing call – SfB Online user on External network (Internet)


John is outside of the internal network on the internet, john want to dial a PSTN number, step 1 signalling does to Office 365, Office 365 does reverse number lookup to check if number belong to a user, If it doesnt match from Office 365 sends to Edge server, to FE to PSTN GW. For media as john is external john cant talk direct to mediation server so must first go route via the edge server to the front end to the PSTN GW.

Outgoing Call – Multi site scenario call flow – more complex


John is external to the network on the internet but we have two sites, (Redmond and Amsterdam).

Johns a US number so calls should ideally route via the US site in Redmond


Signalling is sent to Office 365 and reverse number lookup is performed


Reverse number lookup fails so signalling sent to On premises to the federation route Edge server which is Redmond in this example


Signalling sent from Edge server to Front End server, Redmond FE checks voice policies and the PSTN GW to route to.


then from front end server to Redmond PSTN gateway


Overall signalling path


Media path for the call

Media will go to the local edge server for the mediation server that is being used which is Redmond in this example, media travels direct from John to Redmond edge, from edge to mediation to PSTN Gateway.,


John now dials a Europe number


This environment is configured for all calls in europe are through amsterdam gateway.

again signalling is sent to Office 365 infrastructure for reverse number lookup which fails so its a pstn call.


Signalling sent to federation route edge server which is Redmond (NOT Amsterdam),


Edge server sends to Redmond front end server and the Redmond front end server detects the call is supposed to be routed via Amsterdam. So the Redmond front end sends the signalling to the Amsterdam front end server which has collocated mediation server role


From here the signalling goes to the Amsterdam PSTN GW


Media flow


The media will flow to the local edge server which the mediation server role is being used which is Amsterdam.

Media will travel from John to Edge in Amsterdam, to Mediation server to PSTN GW. Media direct from user to edge server.

If this flow is not direct john will send all media to Office 365 then Office 365 to On premises edge, mediation and PSTN GW.

This routing logic is configurable in your environment, where calls can go to local breakouts for least cost routing or all calls can go via a single site for example Redmond.

User enablement


How do we enable users for Cloud PBX for on premises PSTN calling, there are a number of steps that are required to be configured on premises AND online!

Recommend Deployment Workflow


Steps shown above are the recommend way, there are other ways but are not as easy. recommended to follow this.

1. Starting with configuration with PSTN ingress point.

This could be a PBX acting as PSTN gateway or an SBC or direct sip trunk into SfB. this needs to be completed only once. New offices and new locations will need to be added as required.


2. select group of SfB online user to be enabled for Cloud PBX

Important to select the right people and select the people that will benefit most from using Cloud PBX. Start with a small group and learn and expand to more users.


3. Enable users for enterprise voice and assign a DID / DDI. Can be done later but easier to do this now.


4. Assign dial plan and voice policy


5. Ensure you have Active Directory synchronisation (AAD Connect) so it ensure all the users information is replicated to Office 365 and Office 365 will be aware of these users. This is needed for reverse number lookup and which policies are assigned.

6. Now we move to action Online and assign Cloud PBX licence to the users (E3 add on or E5)


7. Move users to SfB Online (All previous steps are to be completed whilst users is homed on premises)


8. Enable for Cloud PBX and enable voicemail



Features and Class of services


Table shows features defined, dial plan and PSTN usage records with on premises and Cloud PBX. Some settings are different.

For on premises users features are defined in on premises voice policy, for online users this is defined in Online pre defined voice polices.

Dial plans are managed differently on premises or online, online dial plans are currently pre configured only until online custom dial plans are released.

PSTN usage records use both on premises voice routing policies

Actions in the Cloud


In SfB Online you need to assign policy for hosting voicemail and enable users.

Here you can see a cloud pbx licence is assigned but enterprisevoiceenabled and hostedvoicemail are both false so these need to be enabled using set-csuser.




Now they are both true.



Now users are enabled how to manage and monitor


Configuration is complete and for user management we have on premises Control Panel and Management Shell, for cloud users we can use admin portal for remote PowerShell. Most user management can be done on premises and are synced to Office 365.

Monitoring is key to understand.

  • CDR are collected on premises so you need the monitoring role deployed
  • QoE (Quality of Experience) is reported online and available in Call Quality Dashboards



  • Cloud PSTN with on premises allow you to continue using existing investments, PBX, PSTN Gateways, PSTN carriers.
  • Allows for phased transition and migration.
  • Must enable users on premises first then move to SfB Online
















Skype Academy Cloud PBX with PSTN calling Summary

Continuing with the summaries from Skype Academy i wanted to continue with Cloud PBX videos following on from the Cloud Voice Introduction.

There’s are number of Cloud PBX videos so ill release them one by one.

Part 1 – Cloud Voice Introductions Summary here

This is part 2 – Cloud PSTN with PSTN Calling


Lets go


Usual training disclaimer


This is January 2017 recording.



Key Learning’s


  • Microsoft Service for PSTN needs
  • Microsoft is your one stop shop
  • Microsoft provides phone numbers and service
  • New Services and countries are continually being added so its key to keep update
  • Networking is SUPER important from users to Office 365, its key to ensure a good user experience. Please refer and follow SOF



Diagram shows all training available for Cloud PBX.

White boxes so training available on Skype Academy, Blue boxes provide structure.

This session is CLOUD PBX with PSTN Calling. Understand and configure Cloud PBX with PSTN Calling.

What is Cloud PBX is out of scope, covered in Cloud PBX Voice introduction here

Dedicated training is available for subject like voicemail and networking.



  • Microsoft provide the service
  • One bill for all communication
  • One portal
  • Seamless user experience
  • easiest and best way to deliver PSTN connectivity to CLOUD PBX users
  • Flexibility for phones numbers with new or existing number via porting
  • Easy to manage, all configuration in one place
  • Support from one place
  • No need for servers on premises, No pbx or gateways or SBCS
  • All provided by SfB Online

When to use CLOUD PBX with PSTN Calling


  • If its available in your region (Currently USA, Puerto Rico, UK, France and Spain Only)
  • No need to keep existing Infrastructure
  • No long term contracts PSTN or PBX
  • Ideal for new deployments or new offices or end of life PBXs

High Level Overview of Cloud PBX with PSTN Calling


Endpoints deployed on premises and connected to Office 365 and Office 365 is connected to the PSTN network

Signalling and media go from on premises to Office 365



Any jitter, packet loss or delay it will affect user experience

Network from user to Office 365 is generally three networks

  • On premises network (in office wired or wireless)
  • From company network (internconnect network to office 365) usually internet service provider
  • Then Office 365 Network

Customer responsible for on premises network and interconnect network. This mean provide good performance, SOF network readiness planning will help to plan for this and test your network.

PSTN Calling Service Availability


Spain is not listed but is not available, so shows its important to check the most up to date information. Tried the URL listed but didn’t seem to work so i found this

Its defined on the user location not tenant location

It doesn’t matter if your Tenant location is not in a country listed for PSTN Calling service, if you have users located in a supported country they can use Cloud PBX with PSTN calling service.

In the future more countries will be added in preview first.  https://www.skypepreview.com/

Last Friday i noticed on Twitter Tom Arbuthnot mentioned that Ireland and the Netherlands are now available for preview so most likely will be coming next to GA soon. Toms post here and can be found on the Skype preview site here

PSTN Calling Plans


The Cloud PBX licence is included with E5 plans and is an add on for E1 and E3. Having Cloud PBX alone does not allow for PSTN calling this is additional.

Users require a PSTN calling plan and there are two available in

  • Domestic (Calls within country)
  • Domestic and International (Calls within and outside your country up to 190)

Most countries are included.

PSTN Calling Service Minutes


  • Minutes are outbound only.
  • Inbound minutes are free.
  • Number of minutes for each user per month is dependent on the location and calling plan.
  • US get 3000 domestic and 600 international calling
  • UK and France 1200 domestic and 600 international calling

Minutes are pooled for users in the same country with the same plan.

For example two users in France with domestic plans a user may have used all their minutes but another user has only used half their minutes, the first user can use the remaining minutes of the other user.

If all minutes are consumed emergency calling will still work and go through

Consumption based billing can be used if all minutes are consumed

Premium rate numbers are not part of PSTN Calling service, all calls to premium rate number are blocked.

I did find however in the UK for companies lower than 10 users its allowed. More details here in section 10.

PSTN Consumption based billing


Optionally feature

Number of scenarios where its used

  • Conferencing Dial out
  • Toll free numbers for Dial in conferencing, call queues or AA
  • Used for users who use Cloud PBX with pstn calling, if they are calling a country that is not included in their pstn calling plan, users who only have domestic plan who want to call international

funding options

  • one time funding
  • Auto recharge

Recommended auto recharge, one time funding if used up it could block functionality from working which wouldn’t be good.

Phone Numbers and Porting



Bring your own numbers or new numbers from Microsoft

If you want to have new numbers its simple process and search by country state region. You can acquire more numbers than licences and theres a formula for this below.

You can bring your own so users can keep their phone numbers, no new business cards.

If you want to keep your own phones you need to create a port request.

Service Numbers


There are different to user numbers !

They support high volume of incoming calls

Configured differently in the backend

These can be toll or toll free

toll free requires pstn consumption with credit

You can port existing service numbers

How many numbers can i have / request ?

Number of phone numbers


User numbers

There is a calculation

its the number of domestic + domestic and international voice calling plans * 1.1 +10 so 50 users =

50 *1.1 +10 = 65

Service Numbers

Its different looking at licences for Cloud PBX and PSTN Conferencing

This using the table above.

if you have 1 – 24 you can have 5 service numbers and 5 toll free

Porting existing Phone Numbers


  • Important not to disconnect service with existing carrier, they are to participate in the porting process.
  • Turn off any special carrier features if applicable
  • Create port request, all numbers need to be from single carrier
  • if multiple carriers then each carrier will need its each port request
  • Company name is important
  • Billing telephone number and account number if set up
  • LOA signed by authorised party that proves these numbers can be ported
  • You can chose full or partial port where only some numbers are ported.
  • Number porting example in Office 365 admin portal

LOA examples and downloads can be found at the bottom of the post.


This is the middle of a porting request

You can only port numbers using the portal in the US

Other countries you will need to open a support request

In the US you can enter single or number ranges

You can port maximum 999 numbers if more a service request is required.

You can transfer all or a subset.

Types or porting


  • Standard
  • Project
  • Complex

Standard porting in the US can be done via portal, complex via service request

  • Single billing telephone number, single carrier single address. usually done in 7 business days providing porting request not rejected.
  • Project based above 100 numbers with single addresses, carrier, address  3 – 4 weeks
  • Complex – more than 999 multiple address, billing telephone numbers, single carrier. manually handling usually 3 – 4 weeks assuming no rejections. Service request required. Recommended if first time, test with single numbers to learn the process before moving all of them.

Emergency Services Dialling


Location is required so numbers are routed correctly to the emergency calling centre

Required when acquired or assigned to a user

In US its required when assigning to a user

Is other counties required when acquiring phone number

Important – emergency locations should be added up front.

Also different calling behaviour for rich client (windows or mac) calls will be placed within SfB, Mobile clients will be sent via mobile carrier for better service.

Flow of Emergency Calling (US )


Diagram is US specific!

Step 1 – Administrator defines location

Step 2 – address validated against master street address guide (US Only)

(Other countries uses Bing Maps to ensure address exists)

Step 3 – users Assign phone number and location and this information is stored in Step 4. Automatic location identification used in case of emergency. Users is configured but has not placed an emergency call

Step 5 – Users dials emergency phone number and is connected to operator (Call Screener) and confirms address with caller and transfer call to PSAP public safety answering point. US Only

(Other countries calls do direct to emergency service local the address, no call screener)

Address confirmed and address is set to dispatcher and emergency service and user is connected to local emergency services.

Additional Configurations


Dial Plans are used to normalise phone numbers

Users in the US don’t want to dial the +1 and want to dial 555 123 456

SfB will use the dial plan to normalise with the +1 in front

Today Dial Plans are defined on user locations, US phones will be normalised to US.

Tenant/ Custom dial plans are in preview now so recommend signing up at https://www.skypepreview.com/  You can also use extensions

Outgoing Caller ID Manipulations


By default the outgoing caller ID will be the user telephone number.

You can change this via PowerShell

Can be changed to a different phone number or block the caller ID being sent so unknown is displayed.

You can do this for all your users, per user or service numbers

Cloud PBX with PSTN Calling In Action


Lets take a look at this in action.

New Numbers


Administrator is signed into Office 365 admin portal and is requesting new telephone numbers for a new user.

Choosing new user number for a user, next we need to select country, region and city so we can get a the correct area code.


Chose the city, above US and California is selected.

You can also see above the quantity you can acquire

You enter the number you require and you can select the telephone numbers you want.

Define Emergency Locations


In the US this is done after acquiring a phone number but in other countries this must be done before acquiring telephone numbers.

The address is required to be validated as shown above and it will prompt if not correct as shown above.


Once Emergency location is added this listed under Emergency locations

You can select the location and add floor information as highlighted in red box below.


Next we need to assign the phone number to the user.


From Voice users tab select the user and from the drop down select a number and emergency location.

Emergency Calling disclaimer – Please read


  • Please note how Emergency calling is different with Cloud PBX with PSTN Calling due to the nature of SfB and its mobile use.
  • It will tell you emergency service centre may not know the exact locations as the user may be at home, travelling or customer so will prompt for the users location
  • There is situations where operator may ask for users actual location
  • If users has no power, network or internet SfB wont be able to call emergency services
  • If travel international then emergency calls shouldn’t be used as emergency wont be routed to the in country emergency services.

Once accepted the number is assigned to the user


You can also view the Unified Messaging (Voicemail) status for the user. If the users mailbox is on Exchange Online this will automatically be setup. If users mailbox on premises this will required setting up. More info can be found here

Operational Considerations


A quick summary for more details on maintaining health for SfB there is more training on Skype academy.



Any network impact will impact SfB users and their user experience

Monitor call quality via Call Quality Dashboard (CQD) some more info here

In case of outages and issue, check service portal on Office 365, open tickets if required.

PSTN Calling Usage Reports

For the past 90 days in Office 365 admin console


Exportable to csv

Who called what/who phone number at what time and duration, call type, call or conference

Microsoft provide this information so consumption can be viewed.

Summary and Key Leanings to Recap


Cloud PBX with PSTN calling is from Microsoft, one service, one bill, one provider

Best experience for providing PSTN for Cloud PBX users.

New features and countries are coming

Networking is super important, be sure to leverage SOF network assessment.

More CLOUD PBX training


You can mix and match Cloud PBX with PSTN calling users and  users with Cloud PBX with on premises PSTN.

Also Cloud Connector Edition (CCE) a small appliance for providing on premises PSTN connectivity to users homed in Office 365 using Cloud PBX.

Additional Trainings


Community and Blog




SOF Blog



Other useful Cloud PBX with PSTN Calling Links


Countries and regions that are supported for Skype for Business Online PSTN Services


Change the toll or toll-free numbers on your dial-in conferencing bridge


Manually submit a custom service request


Download a Letter of Authorization (LOA)


LOA Download Forms


What phone service providers or carriers are supported?


Transfer phone numbers to Skype for Business Online


Set up PSTN Calling for Skype for Business


What is PSTN calling?


PSTN Calling plans for Skype for Business


Getting phones for Skype for Business Online


Emergency calling terms and conditions


Skype for Business Online: Emergency Calling (911) disclaimer


What are emergency locations, addresses and call routing?


Skype for Business Online PSTN services use terms


Skype for Business PSTN calling – code of practice for United Kingdom


Skype for Business PSTN calling – complaint handling code for United Kingdom


Skype for Business add-on licensing


What is PSTN Consumption billing?


PSTN Consumption Rate Table


Set up dial-in or PSTN conferencing for Skype for Business


Here’s what you get with Cloud PBX


Set up Cloud PBX voicemail – Admin help


Configure Skype for Business Cloud Connector Edition


Customer issues between ExUM and Azure Voicemail


Add funds and manage Skype for Business PSTN Consumption


Skype Academy Presents Cloud Voice Introduction Summary

In the series of Cloud PBX videos on Skype academy this is the first in the series and the introduction to Cloud PBX. (Cloud Voice)

Great session give an introduction and overview of Cloud PBX and PSTN connectivity options, Cloud PBX features, planning and network considerations.

Lets go!


Disclaimer to start


Office 365 and SfB Online are evolving quickly with new features and new functionality.

Make sure you check out the latest version of the training.

This is the January 2017 video.

A introduction to the speaker Thomas Binder


Thomas is Senior Program manager in customer services and deployment team at Microsoft.



Key Learning’s from the session


Cloud PBX provides telephony to users in SfB Online with rich set of features and administrators get management tools and reporting for Cloud PBX users.

Cloud PBX has multiple options PSTN Connectivity

  • Full telephony services including PSTN connectivity from Microsoft (Cloud PBX with PSTN Calling)
  • Bring and use your own PSTN on premises and allow Cloud PBX users to use with PSTN connectivity method. (Cloud PBX with on premises PSTN) Hybrid / Cloud Connector Edition.

Scope of the sessions


There’s a number of Cloud PBX related sessions on Skype Academy and this layout shows a logical view of them. This is the first in the series and its the Cloud Voice Introduction, Understanding Cloud PBX, features set of Cloud PBX and PSTN connectivity options.

Blue boxes are topic groups to structure the trainings. White boxes are training sessions.

What is Cloud Voice ?


Anatomy of a traditional PBX Deployment


  • PBX (Private Branch Exchange) provides voice features, connects and switches calls between users. PBX is the phone system within your business and is the heart of the phone system.
  • Endpoints connect to the PBX to place and receive phone calls
  • The PBX has trunks that connect to the PSTN network which allows users to place and receive calls to the PSTN network. The trunks usually are ISDN or SIP trunk based.

Taking Voice to the Cloud


So how do we take our PBX to the cloud.

End points – and client are SfB clients, windows, mac, mobile client and ip phones. Cloud PBX will be able to leverage all features IM, Presence conferencing and Cloud PBX.

PBX – provided by Skype for Business Cloud PBX providing users have the required Cloud PBX licence associated.

Trunks – Multiple options with Cloud PBX

  1. Cloud PBX with PSTN Calling (Requires PSTN Calling Plans as well Cloud PBX licence) Microsoft provides the phone numbers all services are provided by Office 365)
  2. Utilising existing PSTN connections on premises
  • Cloud PBX with on premises PSTN calling via on premises pool (Lync Server or Skype for Business Server)
  • Cloud PBX with on premises PSTN calling via Cloud Connector Edition (CCE)

Universal Communication Solution


Don’t forget as well as Cloud PBX for voice SfB also provides Instant Messaging, presence, collaboration, online meetings and dial in conferencing within and across other companies via federation.

Skype for Business Online


Integrated into Office 365 and integration with Exchange Online, SharePoint Online.

Office 365 Service Level Agreement


Microsoft provide SLAs and are accountable, SfB is covered in Office 365 SLA and service credits are used. Availability is measured for IM and Meetings and PSTN calling and PSTN conferencing.

  • Quality SLA have specific requirements so key to ensure you meet them including
  • Certified IP Phone with wired Ethernet connections. Certified IP Phone list here
  • Media issues need to due to Microsoft Networks on customer on premises networks.

Lets break down into each part of a traditional PBX deployment in more detail


Endpoints / Clients


Full rich clients on PC and MAC

Mobile clients on IOS, Andriod and windows

IP Phones – Polycom, AudioCodes and Yealink


IP Phones are tested and certified against Office 365

Phone venders build firmware and third party tests and validated.

As well are unified user experience, manageability is important and phones can leverage in band provisioning and updates. IP Phones usually have their own SfB version so be careful when purchasing.

Plug and Play and venders offer additional features and a new web sign in option is available. Allows pairing without having to enter users credentials into the device.

Compare each device and ensure they meet their requirements. Yealink are now certified as well.

Cloud PBX Features


back to the diagram of traditional PBX deployment


Now we home in on the PBX and features


Once Cloud PBX is enabled the Voice tab is displayed.


You can type the numbers including words in the US or search for users

Dial pad available as well via mouse or touch


Also you can view your own phone number as well which is handy


Play and manage voicemails as well. Very handy feature saves dialling in and listening.


Mange Call forwarding settings – Allows users to manage this themselves


Cloud PBX Basic Calling features



DID numbers hosted by Microsoft or customer, each user will have their own phone number.

Device switching, start with PC and transfer to mobile phone

Distinctive ringing based on relationship setting, you can set different ringtones for them. Not seen this before so will check it out.

Call history for users, placed and received and Call details records for administrators

Advanced call features


Teams calls can receive incoming calls but cant makes call on behalf of team members.


Emergency Calling is supported


Dependent on PSTN connectivity method

Power and internet is required for emergency calls

Based on static location information, users could travel and be something else.

Cloud PBX Voicemail


All Cloud PBX users get Voicemail which is delivered by Azure Voicemail not Exchange Unified Messaging for Cloud PBX.

Supported with Exchange Online and Exchange on premises. Exchange on-premises has specific requirements so please check this here.

Auto Attendant


Currently in Preview for more information there’s a Skype academy session or for my summary go here

AA preview features are subject to change. GA is planned for March 2017 but could change.

AA is intelligent virtual receptions you can search for users by keypad or by speech and can transfer calls.

Also operator can be added instead of virtual receptionist.

Custom speech to text and greetings or upload audio files.

Define different call flows for inside and outside business hours.

Service numbers are required either toll or toll free.

Call Queues


Currently in Preview for more information there’s a Skype academy session or for my summary go here

GA planned for March 2017 but could change.

Cloud PBX users can be agents in Call queues, calls will wait in the queue until an agent is available. Call control options available.

Service numbers are used either toll or toll free.

Service Numbers


Services numbers are required for

  • Auto Attendant
  • Call Queues
  • PSTN conferencing

Service numbers route differently to user numbers and allow for higher call capacity

Provided by Microsoft or bring your own via porting process

Service numbers can be toll or toll free

  • Toll – callers pay the regular call charges
  • Toll Free – You absorb the costs for the caller call. PSTN consumption billing is required.



Via a GUI or PowerShell

PowerShell great for provisioning in bulk and automating tasks.



Allows admin to view usage and quality.

Call Quality Dashboard and location enhanced reporting so you drill down and check quality for building and networks.

PSTN Usage Report example


Shows date, time username, call type and duration. You can download as CSV and download via PowerShell.

Call Quality Dashboard Example


Audio streams, daily, monthly trends.

Insight into users quality and experience.

Connecting to PSTN


How do we connect Cloud PBX to the PSTN ?

Back to the diagram and we are now focusing on Trunks



In general there are two options

  • PSTN Calling
  • On premise PSTN Connectivity (On premise PSTN Connectivity has two ways this can achieved)

PSTN Calling – Available in supported regions only (Currently 5 US, Puerto Rico, UK, France and Spain), solely cloud based, no on premises requirement, Microsoft provide the whole service, Microsoft are the PSTN carrier and provide new or bring your own phone numbers via porting. Mostly tightly integrated with Office 365 and Skype for Business Online.

On Premises PSTN Connectivity – Use existing Lync or SfB Server deployment that already connected to the PSTN or use Cloud Connector Editions. CCE for new deployment only and cant co exist with an existing Lync / SfB server deployment on premises. Small footprint with packaged virtual machines. Available in Sonus and AudioCodes SBCs are well now.

Leverage existing PSTN carriers and circuit

Cloud PBX with PSTN Calling


Delivered end to end by Microsoft including PSTN connectivity

Not available in all countries currently.

Administrators use a single interface to administrator users and the service.

Spain is now supported

Cloud PBX with on premises PSTN Connectivity


Delivered in two ways

  • Via existing Lync / SfB Server deployment
  • Or via Cloud Connector Edition (CCE can not exist with an existing Lync / SfB server deployment)

Allows existing PSTN carrier / PBX contracts you can keep these contracts and use this for your users homed in Office 365.

Cloud Connector has a smaller footprint

All meetings, IM , presence are all delivered by Office 365, existing Server deployment will see workloads reduce.

Cloud PBX with On premises PSTN Available worldwide !

Network Considerations – VERY IMPORTANT


Network is key, user quality is only as good as the network allows.

In general three networks are at play

On premises network

Interconnect network – ISP connecting on premises to Office 365

Office 365 network – optimised for Voice

The on-premises and interconnect need to be optimised for voice to ensure quality. There are tools and guidance for network planning and assessment.

Planning Considerations


User locations – Users can be homed on premises, online with hybrid. Only SfB online users can leverage Cloud PBX.

Coexistence – is there an existing Lync or SfB Server deployment then this must used if not CCE can be used.

Is there a requirement to use on premises PSTN connectivity ?

Mix and Match – For example US users can use Cloud PBX with PSTN Calling and users in Germany can use Cloud PBX with on premises PSTN connectivity.

Features in SfB online and on premises are NOT the same.

Skype for Business On premises has all voice functionality, when moving users to online its key to ensure the functionality they use today can be provided by Online.

SOF can be leveraged for migrations

Decisions Tree


What’s your business requirements ?

Which option meets these requirements, feature requirements, continue to leverage existing PSTN providers

Where are the supported regions, where are users locations

Start with the people that will benefit most from moving to Skype for Business Online and Cloud PBX






Further Cloud PBX trainings





Skype Operations Framework



Community and Blog