well, so welcome to our session on managingoffice communications server 2007. no, i'm kidding,it was eight years ago, right? >> r2.>> r2 platform. no, so we're gonna talk today aboutmanaging skype for business server. and by the term manage, we don't actually mean in termsof operations in support of it. but what we wanted to do is give youa sense of when your still managing skype for business server,
what are things that are youneed to be thinking about into the future around yourpotential trip to the cloud. as well as the new features thathave come out, so that's kind of the two main parts that we're goingto cover off in this session. if your in the wrong room, and youwanted to hear about something else, now would be the time to leave. because those doorsare gonna close and you cannot leave untilthe session is over. kidding, you can go if you want.
>> or in case of an emergency.>> so, my name is scott stubberfield. i'm a program manager atmicrosoft in the skype for business product engineering group. been at microsoft ten, elevenplus years, and i am canadian. do we have any other canadians inthe room, i know there are some, i saw ken. hey, that's a good,yeah we've got a lot more canadians. our one canadian left,and he never came back.
so why did we send him overto that room, we lost him. >> he's canadian, he got lost. >> i think it's true. >> yep.>> sorry >> yeah, so i'm bryan nyce, i am also a program manager in ourskype for business product group. i've been at microsoft a little overfive years, been doing architect and fun-stuff work forfifteen, twenty years. i am an american,i'm from california.
so i'm really diggingall the water here, cuz we don't have a lotof that where i live, so. >> [laugh]. >> but he likes canada. >> yes i do. >> so if you have anyreally hard questions, can you please address them tobryan, because i work for bryan now. so if you ask me a really hardquestion, i can't answer it, that's not gonna be good forme at the end of the year.
>> [laugh]>> it'll work out well for me, though. >> might work out well for you. >> yeah,don't even ask how titles work here. >> yeah, we don't haveenough time to explain that. so yeah, so the two things wewanted, the key objectives here, we're going to talk about howto connect to your on-premises infrastructure, you're voiceinfrastructure to skype for business online.
that's that part that i'm talkingabout how you're gonna leverage that existing skype for business on-preminvestment that you have, or maybe feature set thatyou have out there. and how you're gonna connect that,the voice pieces of that. and then we will also talk aboutsome of the latest cumulative updates that we have. the deck does reference them as cu1,cu2, cu3. the terminology you see when youpublicly release them is the july 2016 update for skype forbusiness server 2015.
i just call it cu3, right? we won't actually formallyoutside this room call it c3, but that's where thatterminology comes from. alright, so why do we wantedto paint this picture? because this is the guy,right, this is satya nadella, he leads microsoft. and this is his marching orders forthe entire company. so our strategy is to buildbest-in-class platforms and productivity services fora mobile-first, cloud-first world.
which seems to not match withthe fact that we're talking about an on-premise product, right? and so why i wanted topaint this picture for you is personally i feel, andi haven't talked to satya about this cuz we don't haveregular one on ones. but i feel that even with skype forbusiness server we can set your customers, or you if youare customer or a partner. we can still set you up to fitthis mold in this mobile-first, cloud-first world.
it's just that there'sa progression to get you from on-premise today to the cloud. and that's really what we want youto take away from this session, in terms of what does thatprogression look like? and what could i be doing with myon-premises deployment today to get to that kind of cloud deployment? so what we're callingthis is the skype for business server is the foundationof cloud deployments. okay, so
in most customers you're not gonnahave one without the other, right? how many people out there work witha customer who are greenfield skype for business online. okay, no hands, right,which is not surprising. we get that a lot inthe customers that bryan and i work with on the teamthat we're on. most customers that we go into havesome form of on-prem footprint. even if it's not skype forbusiness on-prem, it's a pbx. it's an avaya pbx, it's a nortelpbx, it's a cisco pbx, or something.
there's some form of an on-premisescomponent that we need to integrate with. >> yeah, so when we look atthe path to the cloud, right, one of the interesting things thatwe like to talk about is the fact that we want to be able toprovide the opportunity to you, to have the cloud on your terms,right? now, obviously, inside of themicrosoft ecosystem, cloud first, mobile first, right, that'sthe mantra that we're going with. but in the real world we understandthat folks can't just flip
the switch and, hey, on friday wewent home, we were on-premises. on monday we came back,we were in the cloud, doesn't quite work that way. as much as we would likeit to work that way, it doesn't work quite that way,right? so we wanna be able toprovide a path to the cloud that allows you to havethe cloud on your terms, right? now, obviously you see onthe right hand side with cloud, that's the end game thatwe're targeting for.
now, again, that's ideal for most,but not all customers, right? there are some customers that just,due to regulatory requirements or what have you,may never get to the cloud. but that's our intent,to get there, right? and you're starting point,what you see on the left, is the on-premises world,which we all know and love today. right, i have my servers1deployed on-premises, i have a featured set thati can provide on premises. and i want to be able tocontinue to leverage that.
and we, at microsoft want to be ableto continue to improve upon that and evolve that. but that middle layer that we have, the hybrid layer,that's building the bridge to allow you to start approachingthe cloud on your terms, right? being able to start dabbling inwhat we call split domain, right? where you can actually share the sipdomain across your on-premises deployment and your online tenant. now giving you that freedom to maybeselect a small portion of your
organization, right, the particularpersonas that make sense, and move them into the cloud, right? allowing them to operatein the cloud, but yet, still communicate to the folksthat are on-premises. and to an end user,they don't notice, right? nothing looks different to themfrom that perspective, right? so that's what we'll lookat in this overall path. and what we're gonna talk aboutthroughout the rest of the session is partially what are some of thepieces that we plug into this path.
but then more importantly, well hey, what about the on-premise'sworld itself, right? is it just, is it gone,is it going away? is innovation not happening thereany more, or are we adding things? and if we are adding things,what are we adding, and what have we brought forth in thelast round of cumulative updates? >> yep, so to answer the question,why hybrid, why do we feel that hybridis super important? number one, hybrid sets you up,prepares you for
future growth, okay? the more that you can workwith your users on-prem, get them using the product, get their clients updated tothe latest client releases. none of that matters, whethertheir connected to an on-prem deployment or connected toan online deployment, right? if your running the latest skype forbusiness 2016, click-to-run first release channel,and you've got that deployedacross your environment,
i don't care if you're on-prem oryour online, right? this is helping you prepare forthat future cloud growth. and then second is, why hybrid? because you've got existing assets,i touched on this before. maybe you've got an existing poolthat you deployed a year ago or a year and a half ago, andyou want to continue to use that. maybe you've got an existing pbxon-prem that you want to continue to leverage when you moveusers to the cloud pbx. maybe you're not ready to takethe jump to go to cloud pbx plus
pstn calling from microsoft. so, continue toleverage those assets. perhaps you have a carriercontract into your existing pbx. or maybe you have a sip trunkcontract that you're tied into for another year and half, two years. again, another reason why itwould be important to keep that hybrid deployment up andrunning. and then last one, which i actuallythink is probably one of the most important ones here, is generatingquality active usage today
translates into qualityactive usage in online. okay, it's super important for us at microsoft that we getthis quality active usage. cuz what happens ifyou buy licenses, and you don't get goodquality active usage? guess what,next time those licenses come up for renewal, we're notreally using that. the product doesn't reallywork well, etc., etc. so we wanna make sure that you getthat quality active usage before you
go and take that big leap to online. so there’s a coupleanalogies that people use, i have this one in my head. in my house i have a wi-fi network,i have wireless router, i have different end points,phones, computers and what not. and it’s all tied toan internet source. i'm also, at the same time, lookingat changing my internet provider because there's a new one that'scoming to town, it's cheaper, it's whatever.
when i change that internet providerfrom the old standard telco to this kind of new player in town,i don't have to change anything on the inside of my house becausethat's been set up for a while. it's tested, i know it works,it's functioning, i have good quality activeusage within my house. all i'm literally doing is changingwhere my internet is coming from. and that's what we think aboutwhen we think about this shift from an on-prem worldto an online world. that you're just literally,you know,
if you think of likea water company, right? instead of gettingwater from a well, now i'm getting waterfrom a main company. so that kinda internal activity inyour environment, client updates like i talked about, actually peopleusing it, people adopting it. making sure that it just stickswithin your organization, that can happen whetheryour on-prem or online. yeah it's an impressive analogy. i wasn't aware they hadinternet in canada.
>> [laugh]>> so [laugh] >> carrier pigeons. >> yes, carrier pigeons. yes, feed them well. so when we talk specificallyabout voice related options, there's a couple of things to thinkthrough from a terminology and from an architectural perspective. and that's kind ofwhat we're showcasing here on this slide, right?
on the left you have the pureonline environment, right? i'll just mention it in passinghere just for completeness. but we're not gonna talk aboutthis in detail here today. but basically that is you'venow moved into office 365 and you are consuming pstn,public switched telephony network. you are consuming pstn servicesfrom microsoft as your carrier. so you've either gottennew numbers from us, you've ported your existingnumbers over to us. we are your telephony provider.
that's the online world thatyou see on the left there. on the right is what i'm sure mostof you are very familiar with today which is what we callthe on-premises enterprise voice services, right? that's where we basically havethe server infrastructure deployed. that's where we doall the fun nuggets, the dial plans and usages androutes and trunks interconnecting to whatever we want that's on thatucoip program that we have right? connect to a gateway, an spc,a pbx, what have you.
that's the idea of what wehave in the on-premises world. in the middle, this is wherewe wanna focus our efforts on. because this is part of thatstory to get you to the cloud on your terms, right. and that's what we call hybrid. hybrid is one of those words,it's like site. it's a word that we overuse a lotin the microsoft vernacular unfortunately. but really what wemean here by hybrid
is the user themselves are actuallyhosted in the cloud, right? so when you've set up this hybridenvironment from a voice perspective you have an opportunity tohost the user in the cloud but provide pstn interconnects fromyour on-premises deployment, right? that's this idea of hybrid inthe guides of pstn calling, or voice interconnects, right? giving us that capability ofleveraging the investments, as scott talked about earlier. hey, i just signed a fiveyear agreement with verizon.
not getting out ofthat anytime soon. funny thing is thatactually happened to us. in corporate, we had just signedan agreement at corp for, i don't know, five years orsomething, with a telco provider. and then a couple months later weannounced the pstn calling service. so it was entertaining. but i mean you getin that situation, i'm not gonna get outof that telco contract. okay, we'll continue to use it.
i have an on-premises skype forbusiness infrastructure, continue to use it. get the user moved into the cloudto consume those cloud services, but leverage the existinginvestments that we already have. we're being asked to leave already? >> [laugh]>> keep going. >> cool, you got the clicker? thank you, sweet. you've been made redundant.
it was that canada comment,wasn't it? [laugh] cheese. so when we look at, and again, forthose of you that know microsoft, you know that our naming conventionof things is rather interesting. we like short, abbreviated names,right, yeah, no. cloud pbx withon-premises pstn connectivity, yeah, doesn't kinda roll off the tonguethere, but that's what it is, right? on-premises pstn connectivity isthat hybrid scenario that we talked about on the last slide.
so my user lives in the cloud, but i connect them to the infrastructureof the pstn through on-premises. well, why is that good? cuz i can take advantageof what i already have. whether it's an existing carriercontract, a pbx, a gateway, whatever i've alreadyinvested money in. and maybe it hasn't depreciated yet,so i can't just toss it out. i've gotta continue to leverage it,gotta continue to use it, great. i can do that with this on-premisespstn connectivity option.
and it is just as simple as once weget the hybrid topology in place, migrating users to the cloud, right? moving users from on-premto online is just like moving users from one pool to thenext in an on-premises deployment. make it that simple. preserve whatever customizationsyou have in your server deployments, right? by moving the user to the cloud, you're not changing what you've donewith your on-premises deployment.
so for the users thatremain on-premises it's business as usual for them. for the users that are capable ofbeing moved into theccloud, well, now they're able to advantagesof the cloud pbx services. and yet they still use thoseunderlying backend services that you already have. obviously, over time,as you start to sift through this, you can significantly reducethat hardware footprint, right? as more and more folks get moved online, maybe you don't have to have
a couple of pools that have12 front-end servers in them. maybe they can get scaled down tosmaller sizes because the number of users that are actually dependingon conferencing services and things of that nature,just aren't there anymore. they're being moved up intothe cloud environment. but obviously atthe end of all of this, you have to make that determinationof what makes sense for me as a customer, forme as a partner, for my customers. and that's where earlierthis week we talk about
the skype operations framework. and one of the pieces that wereleased in there was called cloud migration. and one of the areas that we gothrough in the cloud migration release is this concept of personas. and helping to understand personamappings that you do in your org, and how we can tie thatto this migration aspect. because there are some users in yourorg that maybe the cloud's not ready for them yet.
because there's a featureset that they need or there's a base set of functionalitythat's just not there. while we wanna give you theopportunity to be able to continue to leverage the on-premisesinfrastructure to do that. so here's a handy dandychart in nice ignite orange that tells us a little bit about thedifferent ways that we can connect to the pstn in this hybrid world. now i wanna call yourattention to the big black line that you see kindof almost in the middle there.
i'm gonna talk about everythingto the left of that right now, because that's here, clear,present, ready, available, right? the stuff to the right,we'll get to in just a second. so, first and foremost,put this in context, right? the context of this slide ison-premises pstn connectivity. so, i have my user homed in thecloud, but i want them to consume pstn services from my organization'son-premises environment. now one of the easiest waysto do that is, number one, your existing pools.
all right, if you already haveenterprise voice deployed today, you already have all the plumbingthat you need, right? you've developedyour voice policies, your pstn usages, your routes. you've done all of that homeworkto be able to figure out class of service, class of restriction. you've done all of the bells and whistles that you need foron-premises. well when you move them to onlinewe simply take that same logic,
put it into a hybridvoice routing policy. and boom,assign it to the user, done. i don't have any extra heavy liftingthat i need to do to get that cloud user to leverage theenvironment that i've already built. now, of course that requiresyou to set up split domain or what we call hybrid, right? to that get topology in play, once that's there you'reready to roll, right? now of course you could deploynew pools as necessary, right.
perhaps you have a pool that'sdeployed today that's servicing users in a particular region and now you wanna be able to spinup users say over in europe. and we wanna be able to doa pstn connectivity option for them over there. well i could just spin upanother pool in that region if i needed to, right? to be able to providethat pstn interconnect. that may or may not bea great strategy, cuz, again,
the end goal here it to try andreduce that hardware footprint. but we're laying out allthe various options that you have. that's definitely one of the optionsthat you can go through. the third option is ourfriend cloud connector. all right how many of you haveplayer with, heard about, or looked at cloud connector? cool, sweet. these are the interactive parts,right? if you don't answer then scott'sgonna make you get back up again and
do something else goofy so. the cloud connector editionis meant to be deployed in an environment that doesn't haveany on-premises deployment to date. so if you already have skype forbusiness server deployed or lync 2010 or 2013 deployed,cloud connector is not for you, yet, right? cuz we don't have a way todo co-existence for that. but the idea of cloud connectoris a package set of vms that get placedon a hyper-v host.
and that basically has justthe bare minimum bits that we need to provide the pstn connectivity. you can't home userson cloud connector. that's not what its intent is. its intent is literallya device that will allow us, or an appliance that will allow usto interconnect to the pstn, and that's it, right,straight simple. now the two options that you seeon the right are the evolution of the cloud connector edition.
as it stands today, cloud connectoris a set of packaged vms. so, you provide the hardware,you provide the hypervisor, which is hyper-v, andthen you go out and download the cloudconnector edition. and we go ahead and,through automation, we build everything that'sneeded to run cloud connector. and you deploy multiple forha and all that fun stuff. the idea with the two on the rightis the evolution of that making it become more of a sealed appliance.
so rather than, i buy the hardwareand then have to run this script and get it all configured,i just buy this sku and it shows up. right, andit's a box that's just a little, you know 1u rackmount appliance andyou stick it in and plug it in and you power it on and i'm done. right, that's the evolutionof cloud connector. and that's the two options thatyou see on the right, right? one that could be partner-driven,and one that's more of a sealedcloud-connected appliance.
those are future thinking items, butsomething to be aware of when you kind of look at how we do thisinterconnect to the pstn. cool. >> okay, so a couple thingsto take away from that. so as brian mentioned, we're notgonna go into all the details and the call routes and the call flows,and signaling and things like that. there are some additionaldetails in the slides in the appendix of this deck. so you can go back anddownload the deck after, and
there are a few more details there. but there are other sessionsthat cover that off. there's some really good trainingsthat we've produced as part of the skype operation framework,that go into the planning and the envisioning of allthese different options. so you can go and learn more there. a couple of key things that we dowant you to take away from, and kind of summarize whatwe just talked about. so moving to the cloud obviouslyis the strategic goal.
it's the strategic goal formicrosoft, and we feel it's the rightstrategic goal for your customers to getthem there eventually. and we realize that there are alwaysa number of different situations and issues why they can't get there. some of them are features,some of them are country, some of them are functionality,whatever. but that's the strategic goal toget to the cloud as much as we can. so to do that one ofour recommendations is
port numbers to our servicewhere possible, right? so if you have numbers thatare under some sort of long-term contract, let's get them. if you're on a country that hascloud pbx with pstn calling, let's get those numbers ported toour services as quickly as possible. the administrative flexibility thatyou gain by moving those numbers over there is super, right? you take a hundred numbers that arein your on-prem, and require a lot of difficult changes and things asyou port those over to the service.
now you take advantage ofall powershell cmdlets, the admin center controls that youhave for changing those numbers, assigning them to users,moving them around if you need to. huge advantage to get them there. leverage existing deployments. and we talked about what someof the reasons are for those. if you have no existingon-prem lync or skype for business deployment today, butyou have on-premises telephony components that you want to connectto, cloud connector is your avenue.
and then, we've also seewhere pstn-only customers can see big savings andmake a lot of traction in a hurry. so let's say your ultimate goalis to move to cloud pbx and pstn calling. well, in order to do that you needto make sure that users are using certified devices,that you're networks are stable, that you have enough bandwidthbetween all your locations. you can basically do all that, and still prove it out using pstnconferencing, which is available
in much more countries thanstraight pstn calling today. so don't look at it and think, well,pstn calling isn't available, so i can't do anything. well, no, you can. you can move to pstn conferencing,or what we callcloud pstn conferencing. you can move to that, and thenstill leverage one of those other on-premises pstn connectivityoptions that brian touched about. all right, so now is when we'regonna kinda switch gears and
talk about some of the cumulativeupdates and some of the investments that we're continuing to makein the on-premises product. because, as brian mentioned earlier,we do get a question a lot. well, is the on-premisesserver product dead? no, it's not dead. cloud is our focus, but we're still continuing to makeinvestments in the on-prem product. >> yeah, and from a cu perspective,again, kind of as scott pointed out, for the purposes of this deck we'regonna refer to things like cu1,
cu2, cu3. that's really just for us to be able to kind of put thingsinto the right buckets for you. but when you see themreleased in the wild, it's always got a dateassociated with it, right? the july 2016 cumulative update. it's also important to note, too,that when you go out to the sites to download the cus, you can only everdownload the latest cu, right? yet another reason why we typicallydon't refer to cu1, 2, 3,
is because if you look at me and go hey, cu3 looks neat but,nah, i just want cu2. yeah, good luck finding it,because you're not, right? unless you back-end throughsupport or what have you, you're not gonna find that onthe public download sites. because when we saycumulative update we mean- >> cumulative. >> cumulative, right? >> everything.right, so let's look at,
very quickly, a snapshot of whatwe did in the first two cus, and then we'll spend some moretime focusing on the most recent. >> which for time references,roughly, july 2015 to july 2016-ish. >> yes, correct. >> roughly. so one of the firstthings that we added was the concept ofshared line appearance. how many of you have usedshared line appearance? how many of you know whatshared line appearance is?
okay, that's a start, that's better. it's important to note, too, becauseeverybody has a slightly different definition of whatshared line appearance is, right? so in one of our first cu's weadded in this ability to do shared line appearance, where i canhave multiple physical handsets, have that same number showup across multiple handsets. so i can have that one didthat's actually shared across five physical phones, for example. that's our concept of shared lineappearance, and it was introduced in
one of our first cus that we did forskype for business server. it also functions specifically with the vvx line ofhandsets from polycom. and a lot of times you will see themantra is basically, we innovate in the cloud first, and then webring it to on-premises second. yet this is one the ones that webrought on-premises first, right? you don't have shared lineappearance as an available option yet through cloud pbx. we had some rgs issues fixed.
a few perf issues, right? performance issues. it's kinda the main monikerthat comes with rgs, or response group servicesis what rgs stands for. in the on-premises world, we'vemade some leaps and bounds on how they're built and scaled and,things of that nature around rgs, that were added intothese various cus. we also added this concept ofgroup call pickup from a cmdlets perspective, rather than havingto use the sefautil, right?
which was a resourcekitcmdlet that we had to run. and if you've everhad to set that up, it's generally notentertaining to set up. so we built a lot of that intothe powershell commandlets now. group call pickup, forthose of you that don't know, is meant to be used in a settingwhere your team is basically sitting in that same physical area. and a call can comeinto the group line and it rings all the membersof that group,
and anybody has the ability topick that particular call up. we tweaked the cmdlets to includea server patch version cmdlet, that actually lets yousee the patch version of the various components, yay. some of these, you just kind oflook at and go, wow, really? well, yeah, wow really. it took us a little bit, butwe got that one in there. and then probably the one that'sthe most fun to talk about on this, is the ability to set up whatwe call pin-less pstn conference
activation, right? a very common request that we sawfrom customers, and one that i worked with directly was, hey, ineed to be able to start a meeting. and i'm dialing into the meetingfrom my phone, right? i'm not using the skype client. i'm not using any kind of mobileclient, i'm actually dialing in. and when i go to dial in,if i wanna unlock that meeting, what do i have to do? well, sign in, right?
what's your conference id? what's your leader pin? what's your? my, how many buttons do i? and i just crash my car, right? so i just need to be ableto start a meeting, right? well, we added this idea of this pin-less pstn conference activation,right? being able to turnthis feature on and
say, okay, you could activate theconference without requiring a pin to be entered forthe conference itself. that probably creates a prettyinteresting situation? >> it does create someinteresting situations, yeah. so basically it's likean open bridge, that anyone, if they got the number andthe conference id, they would be in. so use that power wisely, if it's something that you'regonna deploy with your customers. make sure that they're aware of thefact that you're making that change,
and make sure that you've talkedthrough all of the potential ramifications of that. and we'll leave it at that. >> definitely fun stuff. all right, so that was kind of the,that was the cu1/cu2 stuff. quick little recap,quick little overview of that. let's talk about the mostrecent stuff that was added in the cu3 side of the house. so the first one that we're gonnalook at is the idea of busy options.
this is a feature that'sbeen requested for a very long time,from what i remember. which is basically the abilityto say, like most phone systems, hey, i'm busy. so when somebody calls me andi'm busy, i'm busy. [laugh] i don't wantsomebody to interrupt me with another phone call. now, obviously before this you coulddo things like do not disturb. i could set my presence to dnd, andthen if someone called me they would
just get routed to myvoicemail directly. yeah, fantastic, if i rememberto set my presence to dnd. the idea of busy on busy, right? you can turn on busy options forthe organization. and then you have the ability for both enterprise voice andnon-enterprise voice users to be able to turn on options thatyou see in the little chart here. one, the name as it would imply,busy on busy. right, you call me,i'm already on a call,
that means my presence is busy,you're gonna get a busy signal. call back later, right. the other option you can setis voicemail on busy which is kinda that same effect thatyou get if you're dnd, right. you call me and i'm busy, and iredirect you to my voicemail rather than redirecting you to a busy tone,or a busy signal that gets played. now, the couple littlenotes that we added here. one, regardless of how thesebusy options are configured, users in a call or a conference orthose with the call on hold
are not prevented frominitiating a new call. so if i have this option set andi'm in a conference and i go, men, this dude put me to sleep, i gonnago make another call, i can do that. i can break out of that andgo make another call for my client that's fine. this doesn't impact my abilityto make an outbound call. so it's not like when busy onbusy is set when i'm busy, it just has to do with the callsthat come inbound, right? now, there's a littlefeature that we have,
that we mentioned at the bottom, that you can't set the busyoption actiontype voicemailonbusy if the user's mailboxis in exchange online. there's actually a kb article here,and i probably should have clicked that before we got in hereto see if they resolved it. but, as of the time, at least we put the deck together,this was still an open item, right? the work around was set the policywhile the exchange mailbox is on the premises first, andthen move the mailbox to the cloud,
and then it works. but if a mailbox isalready in the cloud, setting voicemail onbusy doesn't work, right? and there is workongoing to fix that, it just didn't make it into the cu. so some considerations for this. there are admin cmdlets, right? so if you're allergic to powershell, you're probably not goingto configure busy options.
there are no ui controls inthe skype for business client. so the user doesn'thave the option to say, i would like this to be busy onbusy versus voicemail on busy. the admin sets this for the user. there is also no forward on busy,as you saw on the previous slide. it's either you get a busy tone oryou end up in my voicemail. i can't say well if i'm busyforward those calls to scott. i don't have a forward on busy yet. team call, boss admin, rgs calls,those will all be prioritized and
handled as they are today,in the response group world or the delegation world. now, what does it mean to be busy? right? we put a little list here of what does that meanwhen say busy on busy? well, what isthe definition of busy? well, there it is. you're in an active call,you have the call on hold, you're in a conference call,
you are in the process of makingan outbound call, or you're already receiving an incoming call thatyou have not yet picked up. all of those scenarios resultingyou being considered busy for the purposes ofconfiguring busy options, and then will takeaction as appropriate. >> and again, i think,you know this feature, keep in mind, this feature is not necessary foreverybody, right? what you're seeing in some otherfeatures that we've deployed in these cus is that they'revery specific features
that were requestedby certain customers. very high profile and importantcustomers that we went out and said, we're gonna unblock your deploymentby developing these features for you. >> yeah, spot on. i personally could go withouthearing a busy signal for the rest of my life. yes? >> [inaudible] >> it's not enabled by default.
>> so his question was what are the->> sorry. thank you. yeah. >> the question is what are the default options when you installcu3 and brian's answer is correct. it's just not on, right. so yup. it's not like you have to plan forit all of a sudden, when you deploy cu3. yup. now.
>> did you have a slide that shows configuration? >> yes,we do coming up here in just a bit. so when we look at the othervoice applications that we have, response group, team call,boss/admin, shared line, call parking, call conferencing,we've documented them down on the slide here, we're not gonna gothrough every gory detail here. but we've documented outon the slide here for your reference howthe busy options integrate and
inter-operate with theseother voice apps, right. so we kind of give you a singlebullet on the last slide that summed it all up and basically said, well,they're gonna respect their own. well, here's the gory detail ofthe specific use cases, right. so i have team call set up. incoming calls to users whoare set up for a team call will be prioritized to ignore busy on busyand voicemail on busy, right. so i prioritize the teamcall action and let the team call ring multiplepeople rather than immediately
sending back a busy tone,cuz that'd be kinda rude, right. maybe i'm on a call and four of my other people that are inmy team are not, well, there's no reason to send that back as a busysignal just because i'm busy. let's let the other four people,if they are available, go ahead and pick up that call. so this is a good slide to haveas a reference if your looking at inter-operability withthe other voice apps. and from a configurationstand point, right.
we need the july 2016 cu. that would be cu3, or later, ofcourse, once we release the next cu, it's cumulative, right, soyou'll install that one and you'll have busy options, if youhaven't installed this as of yet. you need to registerthe busy options application. it is a voice application that we'vebuilt on top of the front end, so we've got the new cs serverapplication cmdlt that we go ahead and run. we need to do a quick updateof the rbac roles, and
we do have to restart the rtcsrv. so obviously, if you are planningon using this feature, this is something that you want to thinkabout planning in your environment. this is not something you wanna domonday morning at 8:30 and say, hey, it'd be kinda cool toturn on busy options today. probably not, right, cuz we have to restartthe rtcsrv service on the pool. and as y'all know, if any of youknow me and you've come to any of my hidr sessions, you know how much funit is with windows fabric when you
start messing around with restartingservers in the pool, right? we should just make step 12 ofthat be update your resume. because you might need to do that ifyou're not following all the steps the right way. at the end of the day, you can actually lookin the event viewer and see the application registered. so there you see it asthe /lcs/busyoptions. yes it does read lcs.
moving on. that's how we can quickly seethat that application is there and registered. and then once wehave the app set up, i mean, still that doesn't really domuch of anything other than give us the ability now to turn onbusy options for my users. so now i can go on andcreate a new voice policy or use an existing voice policy if iwant using the set cs voice policy. busy options enable true, right?
if you remember from back in therecesses of your brain when we talk about on-premises voice stuff, youhave the concept of a voice policy. voice policies on-premisescontrol two things. they control whatfeatures are enabled. and they control cost of service, cost of restriction throughthe usages and routes. this is a featurethat you can turn on. and remember you gottaturn it on in powershell. there's no check box inthe control panel for us to do this.
so we turn busy options on,and then we can grant the voice policy as appropriateto alice, right, in this case. that basically turns onthe busy option feature. the last cmdlt hereactually says what type of busy option we are setting up foralice. is it busy on busy oris it voicemail on busy? so yeah, to wrap up the busy optionspiece, this is definitely a very pointed, specific feature that we'vehad a number of customers ask for. it is not something that i seecustomers just broadly rolling out
because and again this is kind ofmaking things behave like an old fashioned telephone system. we even have a call waiting wherei didn't get system a busy signal. so, i don't know how necessarilywould want everybody to have it but for those customers thatabsolutely needing it, we listen to that feedback, andeventually we provided access to the feature inthe on-premises world, right. this is another one of thoseoptions that it's available in the on-premises world,it's not available in the cloud.
so i'll flip over to scott and we can talk about some morefun goodies we added into cu3. >> yes, so the next big,i would say that probably, the biggest feature thatlanded in cu3 for skype for business on-premises,video based screen sharing or vbss. i've been around this product fora long time, skype for business, lync,office communications server and i would say that one of the biggestpieces of feedback that we had heard across the years was we use screensharing a lot and in environments
where network isn't great,screen sharing really suffers. why was that? the reason forthat was previously in rdp, we used tcp protocol. tcp protocol is connectionoriented protocol. if i miss packets, package dropout of order, everything suffers. we don't do that in voice. cuz the reason is you'vealready moved on. plus the brain's able toprocess what it's missing.
so our previous desktop sharingimplementations all relied on rdp, they were all tcp-based. so if you were on a network withpoor network conditions and you were ever in one of thosemeetings where someone was trying to show you something on their screen. hold on, hold on, no, i know youjust said you opened command prompt but i'm still back oninternet explorer, right. so you could get in these situationswhere you were a long ways behind where they were.
so, underlying protocols for vbss. in the legacy screen sharingperspective, we were using rdp and the maximum that we could getthere was 1.5 frames per second. with vbss we could get upto 15 frames per second. so there's a coupleadvantages there. one the additional vbss, you can nowuse this in an environment where you're running software that's maybeshowing a 3d model that's spinning. right? what did that 3d model look like before in rdp?
>> if you were lucky at all. >> yeah if you were lucky you wouldsee, it would rotate 360 degrees and you would see it move four times. right now with vbss and15 frames per second you can actually see that modelspin around back and forth. one of the big reasons was forgoing to vbss was so that we could improvethat frames per second. second one that ialready kinda touched on was aroundthe transport protocol, right.
so the fact that in vbss we've movedto udp, rather than tcp and rdp. allows us to function betterin environments where network conditions aren't great. now we will fall back. so vbss, what you'll see whenwe show the stp of this, we do negotiate both udp and tcp. so that's one myth that i've heard, where people say no,vbs is only udp. that's not actually true.
we will do udp and tcp, it's just that we prefer udp, andyou'll get a better user experience. some colleagues of ours,ricardo and jason, did a session earlier this week onvbss, kind of a deeper dive on vbss. they had a really cool video thatshows functionality side by side, rdp versus vbss. so if you want to see this inaction you can go back and watch their presentation. from a backwardscompatibility perspective,
we had to bake backwardcompatibility in out of the box. we couldn't say to the world,hey guess what, everyone in the world needs toupdate to this client release, now. >> but. >> now![laugh]. >> go, right. vbss is here. everyone, go. we couldn't, we knew that.
this is a multi staged,multi year, multi client approach, to getting us to having all of ourendpoints eventually running vbss. it is a lot of painin the short term. as you'll see in the slides thatcome up that talk about all of the inter operability scenarios,and when we fall back, and things like that. there are a lot of really weirdsituations that we had to account for but i think it was an investment inpain that will eventually pay off.
so, some of the goals of vbss. we sat down, and said,hey we wanna deploy this vbss thing, we've heard the feedback, theseare the goals that we went after. so we want to make screen sharingmore reliable compared to rdp. from both a speed perspective, butalso an initial set up perspective. when you join a conference call andaudio and video negotiate, that happens pretty quick right? you join the call, audio is on,there is video, we're good. we're in the call.
some rdp sessions in the past, ten,twelve, fifteen seconds sometimes. >> can you see my screen yet? >> can you see my screen? nope. can you see my screen? >> nope.there it is. >> okay, i got it now. right? that is what the second big goalthat we really wanted to improve
session start up time. again, some big goals andsome reasons why we went after this. as a result of that, thereare obviously some pros and cons. from a pros perspective,yes we've made it more reliable, we've increased the framesper second, and this is now a screen sharing solution that youcan use in environments where you're trying to share video or you'retrying to share 3d applications. on the con side there are certainscenarios where we will actually use more bandwidth than rdp.
so in rdp was very bursty so if you looked at the overallbandwidth that got used. we overall averagedprobably less bandwidth than what we wouldin a vbss session. however, we feel the prosfar outweigh that con. and then secondly we have heardsome feedback where it's a little blurrier to rdp, right? and so you'll jointhe session with the vbss. and maybe the initialsecond it starts and
the screens kinda blurry andthen it kinda catches up. to me that's the analogy like whenyou watch netflix at home, right. you start a movie in netflix andthe first two, three seconds may be a littleblurry as the things equalize. and then boom,now we're in a nice crisp session. so we have sacrificed someof the overall quality of the images that you do see. but again i feel andwe feel as a team that its worth it. so why is this important?
this is important because maybein your environment today, you don't have firewalls set upto account for all this stuff. one of the things we've seenwith customers is they went and hey deployed co3 and they didn't have udp ports open andnow they're using vbss over tcp and they're saying hey, this isn't anybetter than what we had before. well it's because they didn'tactually open up the udp ports to get from the clientsup to the front end servers. so you need to make sure youhave that media port range,
the tcp port range for signaling hasn't changed it's justmore important on the udp side. and then same thing onthe required client port side, you want to make sure that you'vegot udp opened up in your firewall. couple of network considerations,so we do use an h264 video codec. so basically in the client we'vewritten a custom screen scraper that actually scrapes the screen,encapsulates it in h264 and sends it across thewire as if it's a video being sent. resolution and aspect ratiodepends on the sharer's monitor.
it's not always gonna be 16:9. but that's kind of the standardthat we would go to. then we've got some maximum andminimum video payload bit rates. the important thing to remember hereis it is still an adaptive codec. so just like our audio and videocodecs are adaptive, based on packet loss, available bandwidth the vbssstock leverages that as well. so we will up the bit ratewhen we have more bandwidth. if the client senses that ithas less bandwidth available, it will actually lower the bit rate.
so we can't tell you exactlywhat the bit rate is, because it will be variable. mr. schertz did someinvestigation back when this was stillin preview in 2015. and shared some early results. or actually maybe that waswhen we deployed it online. that was probably based on a linebecause it came to online first and then we back ported it through. >> yeah it came online first andit came to peer to peer first and
then conferencing when we didthe online and then once we released cu3 that's when we added it tothe mc's here for our on premises. >> yeah, so he's got somegood information there, in terms of sometesting that he did and how much bandwidth getsused in certain situation. so, when and where? first most important thing,on the client side skype for business clients. 2016 and above.
has to be 2016. this will not work in a 2015 client, even if it's a 2015 client that'srunning the skype for business skin. okay, so very important thatyou're in the 16 range. you also need to be,at a minimum, 16.0.6330 for our click to run versions. and then one of our recommendationshere is all of these different client channels that we have,differed channel, current channel and then firstrelease for differed channel.
we originally brian andi debated we had some versions, some detailed versions up there. and we're like should we saythis is the best version for-. that stuff is changing so dynamically that it's not worth itfor us to put versions up there. just keep in mind that as of thisversion for click to run and this version for msi, we will essentiallyenable video based screen sharing. you will get the best experience,the most bugs fixed by staying the latest as you can on any ofthese click to run channels and
also on the msis. so again we could have put somereally complicated matrix. you need this version andfirst release for deferred channel. it doesn't make a lot of sense. just tell your customers thatwhatever channel they're on click to run, stay up to date andget it deployed because we are constantly fixingclient bugs that we find. and it's not that there were thingswe should have fixed it before. we're just finding different thingsas other clients get updated and
we run into all thesesort of situations. so that's the big takeaway. stay on the latest builds andyou will have the best and greatest vbss experience. on the server side, this is enabledacross every tenant worldwide and skype for business online andit will also be enabled for tenants running skype forbusiness on premise, cu3 and above. okay? when do we fall back?
pretty much a lot of the time. [laugh] that's the waythat i summarize this. i know it gets some laughs, buti did introduce this before, that there is some pain here, right? we had to do a lot ofcoding in the product to make sure that we seamlesslysupport this fall back. and if anyone's everactually seen it in action, it's pretty darn slick, right? and so we talk about inthe kinda under the covers bit
how we actually make this happen butjust keep in mind that whenever any one of these things happens ina meeting, we will fall back to rdp. and the other important thingis we do not ever fall forward. right? so someone running a down level client joins,we fall back to rdp. if they leave, we don't gohey we can go back to vbss. because we don't wantthings bouncing back and forth, doesn't make sense. right? so we try vbss,
if it doesn't work we'll fall back. so couple things under the covers. so there are somesip negotiation changes. anyone here like tolook at snooper traces? just for fun, yeah i know,it's kind of nerdy, i do myself. so one important thingthat you'll notice is that it's nowa multipart sdp offer. so we will actually negotiate inthat offer for application sharing. we will negotiate rdp andwe will negotiate for vbss.
why do we that? tell me why do we do it? why are we negotiating both? >> [inaudible]>> exactly speed of fall back. what we didn't want to havehappen is, crap, someone joined that doesn't support vbss, let'sgo back and renegotiate the media. no, we want that to be super,super seamless. so this is essentially like whatwe do with audio codex today. in audio codex we do thesemultiple negotiations.
and i tell people all the timeit's kind of like languages. so when bryan and i first meet, we set the standardof do we speak english and french? great. let's start speaking french, becausethat's our preferred language. if we can't,we'll fall back to english. but we've alreadynegotiated that up front. so as soon as that conversation inthat language of vbss fails, or we need to fail back. boom!
rdp kicks right in. on the rtcp channel, we just say,hey go to rdp, boom. both endpoints go to rdp andwe're back in rdp and it's literally seamlessinto the meeting. so there's none of this waitingin this weird translation. >> andthat would fail back really fast for me cuz i don't speak french. my french isn't very good. >> so just a quick example.
so if you are looking in a log file,so if you're trying to look at this from a peer client side perspective,it's really hard to see. it's not like we put a big flashingsign on the desktop that says, hey, guess what? this is using vbss. we don't, we just do it,we just share the desktop. if you know what to look for, you can see that kind ofgradient view on first join, you'd also be able to tellbecause of the speed of the join.
but the way that you really tellis by looking in a sip trace, right, soa couple things you wanna look for. number one, you gonna look form=applicationsharing, right. so that's his hey i'mdoing this negotiation for application sharing, and then you'llgonna see a line that says m=video. so if you see an m=video linepaired with an m=applicationsharing session, boom that tells you thatthat client is negotiating dbss. right? and so if you're having an issue,then your mind needs to go to,
hey, are you running the latestclick to run release? are you running an msi? are you fully patched? does the issue reproduceif you fall back to rdp? and you can make rdp fallback by doing things like having downloadable clients join. or the common one that i see ishaving someone request control, which forces us to fall back to rdp,make sense? and so this is one thing here thatyou'll actually see when we do that
fallback because we don't wantthat client to now bounce back and forth and try to go back to dbss,we actually get a re invite. everyone knows what a reinvite is,right? so it's an addition tothe original end invite, where basically we come back andwe set this m= video to zero. which basically says hey, thatfrench negotiation thing we did? eh, never mind. doesn't work, never mind. forget that we even talked about it.
we're only speaking english the restof this, the rest of this call. so that's, those are two ways thatyou could look in a client side log file to see whether ornot vbss was in play, number one. and number two,did we actually fall back to rdp, those are two clues thatyou could look for. >> yeah, before he jumps off ofthe slide with that, just for those of you who don't poke aroundin log files all that much, right, the sdp is the session descriptionprotocol, which is what actually tells us how we're negotiating audioand video and all the ports we're
gonna use and all the candidates andall of that good stuff. if you haven't had a chance todabble in that you can check out there's a session on friday ithink around noonish or so that the great thomas binderis going to be running on media. that'll take you all throughthe clients and back in ice and [inaudible] all that good stuff. so if you haven't hada chance to dig into what the session descriptionprotocol is and you want to know more about thathead to that session on friday.
>> okay so last two slides. one, if you need to enable thisdisable dbss client sites. so say you're runninga down level version and you identify yeah i'mrunning this version. there's a bug. right, andi don't have time to update that. you can actually disableusing dbsf's client site, you could do this in a manualregistry file, you could put this in a gpo and push it up to a bunchof people if you wanted to.
32 bit version of link, 64 bit version of link,pretty straight forward. this will apply to both peerto peer and conferencing, it just disables vbss all together. if you wanted to disable it serverside it's, set-csconferencingpolicy -identity [policyname]-applicationsharingmode rdp and then you changethe media configuration. those are both on prem commandletsbecause this is an on prem discussion, right.
if you wanted to do that for online, we don't support that just yet,so you would need to put the client side fix inif you want to deploy that. >> yeah,i think a key point when we look at, we give you the options herethat talk about disabling it. generally speaking, the firstknee jerk reaction shouldn't be, there's a problem,just let me disable it. there's a problem, let me makemicrosoft fix what the problem is. right? because we've actually had
instances where a number ofcustomers have run into an issue. and rather than tell us aboutthe issue, they just disabled it. and then a couple weeks later, weget another customer that finds it. and we discover that wow that's been happening tolots of other customers, and we could have fixed this a wholelot earlier had we known about it. so definitely if you findchallenges or problems with dbss, before you reach for that hammerto say let's turn this thing off. let's see if we can find outwhat the root cause of it is.
it could be driver related, it could be a bug in the codethat we have to fix, right? but that's part ofthe iterative process, right? we wanna get to the root causeof it, we wanna fix it, and we wanna get it out there, right? and then kind of as a last resort,or if you have a very specific use case, then you canlook at turning it off. >> yeah.>> re pro, collect logs, file a support case, done, thatway we can potentially disable it.
>> sweet. i really enjoy the vss works. works pretty well for me. one of the other big areasthat we added in and this is really more of a client drivenpiece, but we included it here for completeness sake, is thisability to send offline im's. >> some people call email. >> yeah. i always joke.
i call it email delayed im's. it's just that's kinda what it is,right? it's like sharepoint's a web server. someone's gonna throwsomething at me somewhere. offline im is pretty muchjust what it sounds like. i open up my skype forbusiness client. i have a contact in there for scott, and i see scott is listedas offline messages only. all right,because he's actually offline.
which i find kinda weirdbecause he should be online all the time, come on. but if he's not online,he's actually offline, i can just open his contact up andsay hey ping me when you get in. all right or maybe there's a botthat's running that sends some alert right out to people. well he's actually going to getthat first as an email, right? so yeah we call it email,he'll get a notification in email that basically reads you havean offline im and here it is and
on his client he'll actually geta little toast that will pop up, says you have an offline im. right, when he signs in tothe skype for business client. now this is actuallydriven by the client and we use exchange web services or ews to deposit it inthe user's exchange mailbox. that's it. it's a pretty nifty feature because,and it's something, again this is one of thosefeatures that we had a lot of
folks asking for, and we said,okay, well let's build it. this is a feature that'sgetting a lot of traction, let's put it into play. so in order for this to work, right,there's a minimum client version that we need to have, what i thinkwe've got in the deck, i hope. the version of exchange,i've seen it work with 2010, 2013, 2016, ews. i even heard rumor ofit working with 2007. but i'm not gonna sayanything about that.
so i ponied up in oneof jason's sessions. does it work with exchange 5.5? and i sorta datedmyself at that point. so that wasn't a good thing. so. the deployment considerations,there's a lot a wall of text here and i'm not gonnaread it all to you. basically, what you have tounderstand is there's a parameter, a policy setting, that we havecalled, enableimautoarchiving.
that controlsthe offline im feature. so if that's turned off,offline ims aren't gonna work. right, because we have tohave that policy in play. now, the client actuallyspools this information. right. so, my skype for business client, i'm gonna send an offlinemessage to scott. he's obviously not online. he's offline. i spool that message inmy local file system and
then send that through ews. and then he receives it asan im note missed conversation message type. right? so he can actually see it, it's different than justa traditional email. right? so it looks a little different in the client, so it can draw attention to the factthat this is a missed im. if it happens to
be an offline message that's sentthrough a federated environment. that typically will thenshow up as a generic email message that you would see in yourconversation history type thing. it doesn't have theim.note.missedconversation format to it. now we don't take you throughall the gory details as far as configing it. we give you a link to it here, and that's because there's reallynot all that much to configure.
it is client site driven. we decided to turn the policy on oroff, and away you go. all right?it's pretty straightforward. now there is a bit of a timer fromwhen an offline message is sent to when it gets picked up andshoved into ews. so if you're like me and you'rekind of impatient and you go and send that message andyou go send, did you get it? man, it must be broken. yeah, you got to wait a little bit,right?
it takes a couple minutes forit to be picked up and processed. if you look at this folder, the%localappdata%\microsoft\office\16.- 0\lync\ your sipaddress\history spooler. and you see a bunch ofemail messages in there, something broke with ews. now your client is actually notable to contact ews to deposit the messages, sothat's a bad scenario. you can use the etl log filescontained info about this and that's typically something thatyou're going to hand off to
support engineers. or if you're in beta program,bts folks of that nature. so we'll just send it all toricardo, it'll be fine, right? so that's typically where we end upwith this troubleshooting option that we have for offline ims. and kind of last feature we talkabout that that we added into cu3, i think this is the last feature. >> this is the last feature. >> could be wrong,it's been a long day.
is the concept of multipleemergency numbers. in the skype for business enterprisevoice world, you guys should know that we have the capability ofdefining emergency numbers. so i can go in and i can define an emergency numberwith emergency number masks. and then i can actuallybuild dynamic policies so that when i travel andi land in a particular location. if i'm used to dialing 911, andi travel over into the uk or something, and i accidentally dial911, it can mask that as 112 and
away we go. that works really well whenyou have one number, which that's what we do here in the usright, you dial 911 and away you go. but in other parts of the world,that actually apparently do exist outside the redmond, which is verystrange, there are multiple numbers. there's a number for fire,there's a number for police, there's different numbers thatneed to go different ways. in cu3 we added the ability to do multiple emergency numbers fora client.
so now i can go in and buildpolicy that'll allow me to have multiple emergency numbers to findrather than just a single one. so now i can support in the uk, ihave 999 and i can also support 112. so that allows me to deal, well atleast until brexit comes along. that allows me to deal with [laugh]at least multiple numbers that i have available in thistype of deployment. also useful inhealthcare environments, where we have roaming support formultiple code blue numbers that they mayhave in their hospital environment.
so just giving the ability forus to go and configure more than one number is what was added intocu3 for skype for business. now there is a powershell,this is all driven by powershell. by the way, we don't see anyupdates in the ui for this. so we use this new csemergency number commandlet. this allows us to go in and define the emergency numbersthat we want to use. now the next two sections here talkabout the set-cslocationpolicy, if you have an existing locationpolicy, or you can build a new one.
and what happens if ialready have them existing? i'm already using emergency numberstoday and i wanna add more. well, if i use thisset-cslocationpolicy, and i build these new emergency numbers,the values that are specified will take precedence overwhat was already there. so we'll basically over writewhat was already there. if i don't configure new emergencynumbers, meaning i don't use the new-csemergencynumberscommand at all, then i'm gonna continue usingthe existing numbers that are there.
so you just have to be aware of thatwhen you go to configure this to make sure you know whether you'regonna be overwriting numbers, because that's always a bad thing. if you think i'm just gonna add thisnumber to that number, actually no, it's gonna replace that. so if you wanted 999 and 112, make sure your new-csemergencynumbercommandlet has both 999 and 112. if you just put 112 in there,and then you do a new one and say well 999, it doesn't addthat to 112, it replaces 112.
and now you're going,brian told me this worked. well, it does when youconfigure it right. you have to have the correctclient versions, latest versions of the clientto be able to do this. if i remember correctly,it was the july pu. >> yeah, and it is defined inthat link under planning details. again, didn't put those numbers onthe slides because they're kinda dynamic and they->> they tend to shift, but we do need to have the correctversion of the client to support
the multiple emergencynumber feature. if you have a version of the clientthat doesn't support this, they're not out of luck. it's not like they can'tcall the emergency numbers, we'll just fall back to using thatsingular emergency number that was defined in the policy before. so if they're dialing a numberthat matches the dial string, then we don't need a dial match. so if i do 911 andthe dial string is 911, all is good,
i don't need anykind of a dial mask. the idea of a dial mask is tobe able to take numbers and flip them around. so hey, he dialled 112, butthis location policy's in the us, let's make that actuallymask over to 911. so the user, if they're travelling,doesn't have to think in an emergency, so i'm from the uk,i usually dial 112 and now i'm in the us andi have to remember to dial 91. we don't need to wait that long.
just dial 112, andwe'll flip that over to 911 and make the outbound call for you,and hopefully life is good. so a couple links there that takeyou through the planning aspects and the config aspects formultiple emergency numbers. again, this is another featureset that we've driven by customer request andalso available only in the skype for business server onpremises deployments. it's time for q and a. we don't have a q and a slide do we?
so, what else do we have in here. we got our other fun slides,we can go into that. so let's take a moment togo question and answers, if you have any questionscome up to the mic. or if you don't wanna get up,just say something. we'll just repeat questions andanything related to skype for business server. anything we talked about today, orif you have any burning skype for business server questions,we'll take them too.
all the hard questions go to scott,yes. >> any plans forbetter archiving and the ability to archiveto [inaudible]? >> yes, the question is are thereany better plans for archiving? so they way that it'soperating today, in the on premises worldarchiving has two options. you can archive to sql on premises,and you can archive toexchange on premises. and then you can have third partiesthat plug in on top of that,
actiance and all that fun stuff. in the online world you haveexchange online, and that's it. as it stands right now, that is thearchival approach and going forward in the online world, it's alwaysexchange online, that is the path. and there's some talkabout api access, and getting folks like actiance to beable to cloud enable their stuff and suck data out and what not. that's all things thatthey're thinking through, but nothing there yet.
>> nothing official yet. >> nothing that wecan make official. i think there's a questionback there, can you see? >> nope, right here. okay, this one here. [inaudible] andyou move to hybrid mode and you move your users up to the cloud,is there impact [inaudible] in current on premisethat you use [inaudible]. >> so, to repeat his question,if you move to hybrid, and
you move users up online, but your sip trunks are still hostedon-prem, is there an issue there? are you talking about specificallynumbers that would have been used out of that sip trunk in their dialin conferencing on prem before? >> just the ability to [inaudible]. >> through cloud pbx to docloud pstn conferencing? >> yeah, so the key thing to realizethere is that pstn conferencing services are provided by theenvironment that you're hosted in. so if you're moved to the cloud
you will consume pstnconferencing in the cloud. you cannot bring your pstn numbersthrough your on premises sip trunk. so you'll get that through eitherthe cloud pstn conferencing service that microsoft offers, or througha third party acp like intercall, or bti or at&t. you won't be able to bring dial inconferencing numbers through your on premises trunks and route them toan online conference, can't do that. >> but you would still be able touse the sip trunk on prem, for on prem pstn connectivity to makeoutbound calls as a right side of
the conference. >> yep. >> [inaudible]>> there is a licensing consideration, the question was, is there a licensing considerationin that model, yeah. when you move the user to the cloud,they need to have a license assigned to them that permits them touse cloud pstn conferencing. and that's eithera separate add on sku or something that you can getas part of say the e5 suite.
okay, sure, there wasquestion back here somewhere, it's really hard to seewith the light back there. >> [inaudible]>> question is, what are your plans forsupporting sql 2016? i don't have any comment on that. i know it's not on the current testbed that they're doing this quarter but i don't have anycomment on that. >> yeah, typically the waythat's worked in the past and i'm not basing this on anythingthat i know right now.
i'm just saying that typically inthe way that it's worked in the past is that we always try anddo that catch up after the fact. cuz sql 2016 comes out afterwe do the initial product. we have to go back anddo test cycles on it. so i would assume it's probablyin the works already, so just keep your eye out on thechannels that you normally would. question up front?>> [inaudible] any plans for data call recording,[inaudible] parties? >> yeah, so the questionis are there any plans for
native call recording? nothing that we can commenton right now, sorry. question in the back? >> yes.the question if you have two users that are having, so scott andi are having an im conversation and then there's a glitch in the matrix,right? and we lose connectivityto each other. will offline ims kickin at that point? >> i don't->> i don't think-
>> i don't think so- >> i don't think they will because, when i'm talking to scott at thatpoint, he's not technically offline. his present state isn't offline. right, because he hasn't, if he's having a network glitch he'snot necessarily been able to get presence updated tosay that he's offline. so i don't know thatit would kick in. honestly i can't say that i've.
>> [inaudible]>> yeah, so i mean there's a couple ofthings that could fall into that. it could be, if you have server sideconversation history which we didn't get a chance to talkabout at all here. but if you have server sideconversation history turned on, you wouldn't get the this messagehas not been sent kind of thing. it would just basically end upin his missed conversations. that wouldn't be offline im. that would be the server sidedepositing it on his behalf.
that's probably morelikely what you'll see, rather than the client spooling itand trying to shove it into ews. >> [inaudible][inaudible] client that also [inaudible]help [inaudible]>> yeah, question the survival of branch applianceswill they support features like service side conversation historyand things of that nature? in the cu3.
on a survivable branch server. the appliance i can'tcomment on because that's the vendors thathave to get that out there. it works with service sideconversation history. user home dome survival branchappliance with a back end pool that has the correct patch levels, service side conversationhistory works. you just need to get cu3 on the sbaand you need the vendors to-. >> go back there and then.
>> would mobile clients supportoffline im, i would doubt it. >> questions? >> [inaudible]. >> so the question was is therea rumor mill about text messaging coming soon? don't have any comment on that one. >> we don't generallycomment on rumors. >> yeah if it's a rumordon't comment on rumors. >> it's not a good idea.
>> not a good idea.>> especially when someone's recording. >> yes definitely not a good idea. >> so on a serious note though. if there are features thatyou're hearing customers want. absolutely we dowanna hear from that. it's skypefeedback.comyou can go to. it's a site called user voice where there's already pre-cannedkind of ideas in there.
you can add new ideas,you can vote up existing ideas. so really that's the place to go toto submit that kind of yeah hey, i want text messagingincluded in the client. go there, describe who it isthat you're working with, and we do actually read that. i know it sounds likemaybe we don't, but we do actually take thatfeedback and pull that in. and it's part of the internalplanning process we go through. >> yeah.>> [inaudible]
>> question is what about support for server 2016? probably in the same boatas what we talked about. >> same boat as sql? >> sql yeah. >> 2016.i would imagine it's coming. i just don't know whatthe test schedule is for that so, but being that server 2016,didn't that just release? so yeah, i would expect it a littlebit out, cuz we're generally not
johnny-on-the-spot with thatthe day that it releases, so. >> yeah, it takes->> but yeah, i would imagine that's on the team'sradar, just like sql 2016 is. >> [inaudible]>> i can't give a date. >> yeah, generally, again in thepast, based on how we've done it, it's that leap frog effect isgenerally within a year, but it gonna wouldn't wanna comment. no one's gonna go back andredeploy existing deployments right? so it's literally justthe net new ones.
but even that a lot of times takesmost, [inaudible] on monday, they're not ready to go, they don'thave images baked and all that. so even the customer request for ityes, it's an interesting question. but most customers probably aren'tready to start deploying server bits on 2016 forat least a couple of months anyway. >> yeah, yeah. it also depends on the agilityof your customer, right? if your customer's agileenough to start, saying, hey it's been a month since it'sout, and i'm ready to go out.
i baked my images. then yeah. your in that rock and a hard place. yeah. >> mm-hm. >> yeah so the question was aroundthe mobile client and dialing 911. let's take that offline andsee because there's been so many iterations ofthe mobile client. i don't even know what's working andwhat's not so.
[laugh] i don't wantto comment on that so. there's a question over here and then we'll take one morewe got to clear out. yeah? >> our [inaudible]have that we have new details coming out the version that the [inaudible] >> yeah, so the question was around version numbers.
as it stands right now,skype for business server 2015. the version buildschange as we do cus. right, there is planninggoing on for the next. and that likely will have adifferent version, it won't be 2015, cuz it's not 2015 anymore. so yeah, i don't know that it wouldever get synced up with the client, because the office client movesat a much more rapid pace. so you may end up with,office 2016 and then v.next. and then office 2017 or 2018 orwhatever the heck they call it.
yeah, so i don't know that thatwould ever get mapped there so. >> but yeah,no firm plans either way. >> yeah.>> so we need to wrap up cuz we're donewith recording, but we'll stick around forany other questions you have. thanks guys,hope you had a great session. >> [applause]
