Home » Posts tagged 'Skype for Business Online'

Tag Archives: Skype for Business Online

Skype Broadcast Meetings–Now Allows External Team Members to Join

Skype Broadcast Meetings seems to have had a quiet update recently. This may be already common knowledge, but I have only just discovered it. Historically we couldn’t add external team members to a broadcast meeting. By this I mean being able to delegate the presenter / producer role function to users from SIP domains not within the same tenant as the organizer.

There was a rather dirty work around by adding a service account to the meeting and allowing the external member to sign in with that to the broadcast login portal but remain signed into their Skype client as their normal organizational account.

Its seems though that this has changed, and we can now add external users as team members to a broadcast meeting.


You have to click on check names to verify the member and this will look up your contacts in Outlook  / Exchange Online (although testing with a few that I know aren’t there also seems to work). From testing it seems that if there is an object in Office 365 then this is addible, if a user does not have a 365 object then this cannot be looked up. It appears that the check names functions can look up across multiple tenants? Still not sure how accurate that is, but seems to be the case.

So requirements seem to be:

  • External presenter must be either homed on Skype for Business Online or Hybrid
  • External presenter’s Skype for Business Server must be able to federate with Office 365
  • External presenter must be assigned a licence in Office 365 that enables broadcast meetings
  • External presenter if on-premises must have their account synchronised with Azure AD

When the external user joins, they are able to authenticate with broadcast meetings using their own 365 credentials and join the broadcast as a presenter



Thanks to Shawn Harry for being my guinea pig!

Skype for Business Online CloudPBX–Calling Plans and Consumption Billing Explained

I must admit, I thought this topic was well understood, but it seems I am having the same conversations over and over, so possibly worth a blog post. First up if anyone has done this already, I apologise, I did Bingle first, and your page did not show on Page 1, I didn’t check page 2, sorry! Anyway, you should have made your SEO better! Smile #Joking.

A question I am getting a lot is:

What is Consumption Billing and do I need it?

Before I answer this question, it important that you first understand the concepts of Cloud PBX licencing.

What does the CloudPBX Licence Give You?

To begin with, CloudPBX is a licence SKU within Office 365. This is available as an add-on licence to existing E1 or E3 plans or inclusive within E5 plan. It is a “per-user” not a “per-tenant” licence, and each user that you want enabled for CloudPBX must have a unique licence applied to their Office365 account. So when you assign this licence to a user what does this user get?

Well on its own, not a great deal visually at least. But it does unlock the user to access some core CloudPBX services:

  • Dial Plans
  • Voice Routing Policies
  • Hybrid PSTN Calling
  • Azure Voicemail

The most notable feature here is the enablement of Hybrid PSTN Calling. This licence allows you to move enterprise voice users from on-premises Skype for Business to Skype for Business Online and still provide PSTN calling capability to these users via existing on-premises gateways. This is the same for existing Skype for Business hybrid setups, or using Cloud Connector Edition.

CloudPBX licence on its own does not give you any of the following cloud voice services:

  • Cloud DIDs
  • Cloud Service Numbers
  • PSTN Conferencing
  • Organizational Auto Attendant
  • Call Queues
  • Cloud PSTN Calling

What if I need PSTN Conferencing?

One consequence of moving a user from On-Prem to Online is that you change the location of conferences organised by the user. Instead of being hosted on-premises, they are now going to be hosted in Skype for Business Online. This poses some considerations for you. You may have deployed a dial-in access number to your on-premises Skype for Business conferencing service, you may have procured special conferencing SIP trunks for that service too, with several numbers in different regions for localised joins. These cannot be used to access organised conferences in Skype for Business Online.

As there is no such thing  as Hybrid PSTN conferencing, you cannot reassign dial in access numbers to the Skype for Business Online ACP service and “proxy” these via on-premises gateways like you can do with a user DDI in hybrid voice. This means that when you move a user over with just a CloudPBX licence, they are only able to organise web conferences. However, they are able to join PSTN conferences organised by someone else (e.g. on-prem user).

There are three ways in which you can enable PSTN Conferencing for a CloudPBX licenced user, in order of expense:

  1. Create a resource account on your On-Premises pool and provide details to the cloud user and they can organise on-premises hosted conferences using the Web Scheduler service and invite their cloud account as a presenter
  2. Add Microsoft PSTN Conferencing licence to their Office 365 account
  3. Bring Your Own ACP (BYOACP) service to Office365 provided by Intercall, PGi, BT Meet-me services

Expanding on the Microsoft PSTN Conferencing Licence, this is again available as an add-on to E1 and E3 plans or inclusive to E5. It is independent of the CloudPBX licence and if you have users who are not enterprise voice enabled, but require PSTN Conferencing, then this licence can be purchased / assigned without CloudPBX.

What does the PSTN Conferencing Licence Give You?

This licence grants you access to the Microsoft PSTN Conferencing network. This network consists of local PSTN dial-in numbers in over 96 (at last count) countries worldwide. This means you can host conferences in the cloud and provide cheap to no cost dial-in solutions for your participants / customers. The access numbers are Microsoft owned, and are shared amongst all Office 365 tenants / organisations consuming this service. By default, users are assigned a primary number based on the location of the user derived from their Office 365 account citizenship, but participants can join from any one of the 96+ regions using localised geographic numbers.

The PSTN conferencing licence therefore gives users an “All You Can Eat” dial-in PSTN conferencing service, without having to pay a rental fee, plus call rate minute charges, and it could work out significantly cheaper than traditional ACP providers.

However, what if you want to provide toll-free access numbers, or need the ability to dial out of a conference?

There are a few certainties in life, with one of them being “There is no such thing as free”. Therefore, for Toll-Free (TFN) dial in access, some one has to pay. Traditionally, TFN is free to the caller only in the region where the number is regarded as a TFN (i.e. 800, 888, 877 are U.S TFNs but if I call them as a UK citizen, they are chargeable to me as well), but the call charges are reversed to the custodian of the number i.e. your organisation, usually on an agreed rate card. With TFN Service numbers assigned to PSTN Conferencing in Office365, this is no different and if you want this ability, you also need to setup what is call consumption billing.

If you want to use dial out PSTN Conferencing and there are some scenarios where you will probably need to:

  • Transfer the conference to your cell phone (if you’re on the move)
  • Invite someone into the conference on their behalf, buy calling them out of the conference

Then, you also need a mechanism to pay for the outbound call. Like TFN payment, consumption billing is required. Keep this in mind for later…

What if I need PSTN Calling?

PSTN Calling is an add-on licence required for users who need enterprise voice calling features in the native Microsoft cloud i.e. not dependent on on-premises infrastructure like hybrid voice users. Currently, PSTN Calling in Skype for Business Online is available in a handful of countries and this is ever expanding (hence the ambiguity here). Like the Cloud PBX licence it is an add-on licence to existing E1, E3 and E5 plans. Yes that’s right E5 alone does not give you this licence! However, it differs slightly as a Calling Plan licence has a dependency on a Cloud PBX licence. This means to consume a calling plan licence the user must first be assigned a Cloud PBX licence.

The easiest way I can explain this is by comparing Cloud PBX with a Calling Plan licence to a mobile (cell) phone contract. You sign up with the provider for an agreed device and allocation of inclusive minutes and texts and you pay the agreed amount. That amount is split to pay the cost of the device, and the cost of the inclusive calls. The Cloud PBX licence is akin to the device rental and the PSTN Calling plan is the amount that you pay for your inclusive minutes per month.

Back to PSTN Calling plans… Depending on your country and availability, you have the choice of purchasing 2 licence models:

  • Domestic Plan
  • International Plan

For most countries the domestic plan includes 1200 minutes per calendar month that a user can consume to call numbers within their country. The U.S are slightly more spoilt, in that they get 3,000! They must talk a lot more than the rest of us! The International calling plan is slightly more complicated to understand. The international plans allow you to call numbers outside your country as well as domestic numbers. All international plans have a cap of 600 minutes for international numbers and the same amount of domestic minutes as that of the domestic plan i.e. 1200 for some, 3,000 for the the U.S. BUT and this is a BIG BUT the plan is 1200/3000 minutes domestic OR 600 minutes international, key word is OR. This means that the plan expires when either pool of minutes have been reached for that month. For example, if you make 600 minutes of international phone calls in week 1, then your plan is empty and you cannot consume the domestic minutes from this plan until it renews, the next calendar month!

Fortunately there are a few safety mechanisms in place. The first one is that all PSTN Calling plans are pooled at tenant level. This means they go into a big pot that all PSTN Calling enabled users can consume. So if one person runs out of minutes, and another is under utilising theirs then they can be consumed by the heavier user. The second is consumption billing….

What does PSTN Calling Licence Give You?

Before we delve into consumption billing, lets talk about what a PSTN Calling licence gives you. As mentioned before, it has a dependency on the Cloud PBX licence and like this licence needs to be purchased per PSTN Calling user, not per tenant. You cannot buy one PSTN Calling licence and share it out over multiple users!

There are a few things that happen when you purchase a Calling Plan licence. The purchasing (not assignment) of the licence(s) unlock all the Cloud PBX calling features:

  • Service Number Acquisitions
  • Subscriber / User Number Acquisitions
  • Call Queues
  • Organizational Auto Attendant
  • Cloud Basic E-911 capabilities

Now you’re able to port numbers into Cloud PBX from legacy carriers, acquire pools of DDIs and Service Numbers from Microsoft and assign to users and services. There is a formula that is applied on number acquisition from Microsoft. For every 1 x PSTN Calling Plan purchased, you get 10 extra numbers you can acquire and apply to services such as OrgAA, Call Queues and PSTN Conferencing as well as 1 per licenced user. However, if you port your existing numbers, there is no limit to the amount of numbers that can be assigned to your tenant. However, bear in mind that you can only assign numbers to users who have a PSTN Calling licence applied to them. You cannot port a number and assign it to a hybrid voice user (that just wouldn’t work!).

Lastly, the PSTN Calling licence allows calls to route between PSTN and the cloud user who has been assigned it (normal phone call).

PSTN Calling plans on the face of it seem a bit expensive, especially in the licencing model adopted by Microsoft. People ask, “why can’t I just buy one licence and it is a tenant licence rather than per user?”.

I don’t have the answer to this question, I am not Microsoft! But I can hazard a educated guess. The PSTN Calling Plan lights up a lot of cloud voice features, of which in other licence SKUs are not chargeable (OrgAA, Azure VM, Call Queues, SBCs, Network etc.) Running those services at scale has a cost associated. Number acquisitions for both service and DDIs, the rental of these from carriers also carry a cost. The use of the PSTN carries a cost too. These costs have been wrapped up into what you see as a PSTN Calling Plan today.

But cost is a major decision driver and anything we can do to reduce overhead is worth talking about! A lot of companies look at PSTN Calling licences and figure “my staff need to make international calls, so I must by an international calling plan for each of them”. This, if true would give the staff a liberal service, but it would not be financially viable for the company to consider.

Instead, perhaps a subset of users are heavy international callers and it is cheaper to purchased inclusive international calls for these. Perhaps another subset of users are occasional international callers, and the rest are domestic callers. It is the subset of the occasional international callers that you focus on to investigate other ways of providing this calling service without the cost of it upfront. When profiling these users out, there will be a lot of maths and algebra involved to figure out the optimum strategy, but for those where it would be cheaper to use Pay As You Go international calling rather than planned calling you can adopt consumption billing for these users…

So What is Consumption Billing?

Consumption Billing is a licence of sorts applied to your tenant by default once you have purchased Cloud PBX and / or PSTN Conferencing licences. Unlike all other licences this is a tenant licence, in that is unlimited, but is still required to be assigned to a user. What consumption billing allows you to do is top load your tenant with funds that can be used for “out of plan” calling services. A pre-paid credit card for a better analogy. Unlike other plans, it does not expire / renew on a monthly basis, it is there until the balance reaches £0, at which point you load more funds.

How is Consumption Billing Used?

Lets go back in time a little to PSTN Conferencing. Remember I said that if a hybrid user or a PSTN Conferencing user wanted to make a call out of a conference e.g. to transfer to their cell phone, or dial in a participant on their behalf? These calls need to be paid for. The cost of these calls comes out of Consumption Billing!

Remember the use of Toll-Free numbers for conferencing or other services (Call Queues, OrgAA)? The cost of the inbound call is charged back to Consumption Billing! If your balance is Zero in consumption billing, Toll-Free numbers will not connect when called!

Now onto PSTN Calling and those occasional international callers. Instead of purchasing an international calling plan, you can purchase a domestic plan and use Consumption Billing to fund their international calls. The cost of these calls are priced using the consumption billing rate card (https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/REDTZ9).

There are different rates based on the origin of the caller, the destination of the callee and the service called (landline, mobile, premium).

By default users who are assigned a domestic only calling plan are blocked from making international calls. Therefore, simply setting up Consumption Billing and assigning it to a user will not turn on international calling. Instead you need to enable international calling on the user’s PSTN settings in PowerShell

Set-CsUserPstnSettings –Identity user@domain.com –AllowInternationalCalls $True

So Consumption Billing is used in multiple scenarios over different services, and this begs the question “How much money do I need to load into Consumption Billing?”

In truth the question is rather loaded, because each organisation will have different calling habits and usage. You could spend days through CDR records and Invoices and doing some math calculations with the assistance of the top grads from MIT or you could use the recommended table from Microsoft based on the number of licenced users

Number of Licenced Users One time Funding (initial stake) Renewal Trigger
Less than 250 $1,000 $200
250-500 $1,000 $400
500-1,000 $2,000 $500
1,000-5,000 $3,000 $1,000
5,000-10,000 $5,000 $1,000
10,000-50,000 $10,000 $1,000
50,000-100,000 $15,000 $2,500
100,000-200,000 $20,000 $2,500

After the initial loading of funds, consumption billing can be closely monitored to work out actual spending which can then be used to determine what the reload amount should be.

I hope this helps people understand how the licencing of Cloud PBX and its features work.

Skype for Business – Snooper and SIP Deep Dive Refresher

This blog is mainly for myself but it may serve anyone who needs a refresher or who is beginning to enter the world of SIP and Skype for Business. Coming from a traditional Microsoft background, when I started with Lync I had no conception of voice, or SIP and spent the best part of my early career actively avoiding anything to do with the subject.

I have never been officially trained on Lync or Voice over IP. All of my knowledge has been a mixture of trial and error, death by fire and reading other people’s blogs. Some might say this is the best way to learn, and while I agree to a point, there are times where I am in a room full of people and feel like the novice still. There are still some areas where I feel I have gaps in my “data bank” as it were. As a result, I often find it difficult to grasp some concepts on how things work outside of Lync / Skype for Business. I have never deployed or administered a Cisco or Avaya PBX system for instance because I just haven’t been in a situation where I have needed to. I am Microsoft, why would I have this experience? But as a Skype consultant you’re expected to have knowledge of these systems to some degree if you are to integrate voice especially.


Skype for Business DDI Number Management using SharePoint Online [BETA]

This year I set myself a little project to see if I could use some of the tools and platforms provided in Office 365 to create something mildly useful. I wanted to start with something basic and achievable without having to spend months and months of trial and error experiments and thought that Phone Number management could be that starter project.

I will preface this blog by stating that there are already various number management solutions out there, some paid and some free and this hasn’t been created to compete with them. It is a project that enables me to learn and develop new skills but also has some use cases that may benefit you, hence the reason for sharing.

Often when I speak with customers and ask them about their number management solution, they invariably say Excel. They’d like to move towards a more suitable product but those offering these solutions are sometimes out of reach of the budget available. Using a basic Excel sheet has it’s own problems, but mainly keeping the thing up to date with all adds, moves and changes. So I thought there must be a way to leverage what is available in just an E1 Office 365 licence to create a middle ground. Something in between Excel and the paid apps must surely be possible?


Skype for Business Conference and “Mute Off” with Plantronics (and others) Headsets

I was browsing the Microsoft Tech Community last night and came across a post by a user saying “Is it possible to stop Skype from announcing Mute Off in meetings” as it was causing them to miss conversations or a chance to interject. This behaviour is not native Lync / Skype for Business. When you go into a mute state the default sound is played, which is a emphasised beep. You can find the actual WAV file in C:\Program Files\Microsoft Office\Office15\15.0\Media folder (or wherever your Office program is installed). The file you are after is LYNC_muting.wav.

When you come off mute, Lync / Skype for Business doesn’t actually play a sound at all, meaning you can interject immediately and miss no parts of the conversation.


Microsoft Teams is nothing new and Skype for Business or is it Skype? Understanding the message

At first glance you may be thinking that this post is going to be a scathing review of Microsoft technology. Well sadly for you, its not. The title is simply to grab your attention and at least make you read up to about here…. right?!?

In all seriousness, this is a contentious topic of which I am going to place my ten pence worth down on now. A lot has happened this Autumn (or fall for my American cousins). We have seen the introduction of Microsoft Teams and the announcements around Skype meetings, Skype Meeting Broadcasts and new Skype clients for the Apple family.

Those eagle eyed followers will notice that the last sentence lacked the words “for Business”. That’s not because I am lazy. In fact, I am disappointed because it means that most of my blog posts are going to be about 200 words less from now on! No, the reason is that Microsoft have been dropping the “for business” when delivering marketing messages around the Skype for Business (one last time). This has left a lot of us and our customers confused on what Microsoft are trying to convey with this.


Porting Numbers to Cloud PBX–What the blogs don’t say

There are many good blogs out there that detail how to port numbers to Cloud PBX, Microsoft pretty much have it organised in this article https://support.office.com/en-gb/article/Transfer-phone-numbers-to-Skype-for-Business-Online-47b3af8e-4171-4dec-8333-c956f108664e. However, if porting numbers is a new thing to you, there are some things you need to know when transferring your customer numbers to Cloud PBX.


Skype for Business to Office 365 Federation Issue

A customer I was working with who has an existing on-premises Lync deployment had trouble federating with with certain partner domains. After investigating the issue it was determined that the problem partner domains where using Skype for Business Online. The symptoms where that the users in the partner domain where able to see my customer’s presence information and able to send Instant Messages. However, the customer could not see the partner presence or reply to any communication (one-way federation).

I have come across one-way federation issues before whilst deploying, however, this was different in that the customer could federate with other partners fine, so I knew that the usual suspects such as certificates, DNS and firewall were probably not going to be the culprits here.

So focusing on the fact that the partner domain was in Office 365 this at least gave a starting point. Tracing the communication between the on-premises Edge server and Office 365 I was able to see that indeed the customer’s Edge server was discovering the correct federation SRV record for the partner (sipfed.online.lync.com) and from the Edge server I could establish a connection to Office 365 using Telnet. However, the Edge server received no response from Office 365 federation service and timed-out the connection, which explains why customer users aren’t able to establish a communication stream.


Skype for Business–Survivable Branch Appliance or Cloud PBX?

Skype for Business Server has been out in the general market for 14 months so far. However, one particular role seems to be dragging it’s heals towards release, and that is the Skype for Business Survivable Branch Appliance. If you are considering an SBA, then the likes of Sonus and Audiocodes have an SBA product. However, if you look under the bonnet, this will be a Windows Server 2012 (in the latest release or Windows Server 2008 R2 in older image versions) with Lync Server 2013 core components installed to act as the SBA.

There appears to be something in the pipeline to bring the SBA to full Skype for Business edition, but there seems to be no urgency to release this to the market. Why?..

Well Microsoft released Cloud PBX late last year, and have made great strides in rolling this out globally across all their Office 365 datacenters and media networks. It is clear, that this is the where their main energy, focus and direction are taking, which is a good thing! But it also begs the question over the viability of not only Skype for Business Server in the future, but the role of the SBA in todays’ ecosystem.

The purpose of the SBA was always to give some level of PSTN calling capability to a site when the connection breaks to the central site where the Skype for Business Front End Pool is located. These were ideal for long distance branch sites with poor inter-site connectivity that was prone to connection issues. Admins could guarantee a level of service to users at that site in order to provide the basic tools for “normal” business operation (Normal = basic toolset).


Skype Broadcast Meetings–A Preview–Q&A & On Demand Playback

Whilst preparing for the next Skype Show I was exploring if anything had changed on my tenant in light of the announcements made at Enterprise Connect back in April. For those who follow the Skype Show (www.theskypeshow.com) you will know I use Skype Broadcast Meetings as the main technology for these shows. So the announcements made at EC16, notably the Q&A functionality for Broadcast Meetings was particularly useful to me.

If you have ever used Broadcast Meetings, you will know that trying to engage with your audience is quite a challenge. Sure we have the ability to integrate Yammer, but this relies on the audience having a Yammer account, and then understanding enough about Yammer to join the group. This is a major put off, and people who want to engage are often put off by this. Broadcast Q&A will improve engagement 100% and I cannot wait for this feature to arrive!

And it has! At least in Technical Preview and much to my excitement!


%d bloggers like this: