Part 1 – Overview and Architecture
To read other parts in this series, please click the links below:
Part 1: Overview and Architecture
Part 2: Azure Prep Work
Part 3: Skype for Business 2015 On-Prem Deployment
Part 4: AudioCodes Mediant Virtual Edition (VE) Deployment
Part 5: SIP Trunk Setup (IntelePeer – AudioCodes – Skype for Business)
Part 6: Office 365 and Skype for Business Online Deployment (Hybrid)
Part 7: On-Prem PSTN Connectivity with Hybrid (OPCH) setup and Tenant Dial Plans
Part 8: Cloud Connector Edition (CCE) Deployment
Part 9: Legacy PBX Deployment and SfB Integration
“Chance favors the prepared mind” ~ Louis Pasteur.
A question I get asked a lot is “how do I learn Skype for Business Voice”. Let’s face it, most Microsoft IT professionals don’t have a telephony background; likewise, most telephony professionals don’t have a Microsoft background.
My answer always begins with some form of “what does your lab look like?” After all, where better to learn a new skill than in a lab. That typically gets a response of “I have a lab, but how I don’t even know where to start!” Which is a fair statement.
My goal in this series is to do just that. Provide the building blocks for a Skype for Business Voice lab that anyone can build. I hope this helps you in your journey!
P.S. I’ll admit, I take a few shortcuts along the way by making references to some great articles to keep from duplicating work that’s already done.
The lab I built for this series was done entirely in Azure. Which keep in mind is completely unsupported and should not be attempted in a production environment. I believe it’s critical to continue investing in yourself by having labs to build new skill-sets, but who says you need run a mini data-center at your house. I completed this lab for “free” using Azure credits allotted via a Microsoft Action Pack Subscription (MAPS), taking care to shut down my virtual machines daily as to not incur any additional charges. MAPS isn’t free so I suppose it’s not totally free, but there weren’t any additional Azure costs as a result. YMMV with PSTN SIP Trunks as well.
Note 1: At the time of writing, OPCH and CCE coexistence is not yet supported. I’m hoping that by the time I finish writing this series, it will be supported, and I get to walk through the configuration.
Note 2: At the time of writing, nested virtualization does not exist in Azure. I won’t be able to deploy CCE in Azure, or better yet, attempt to deploy CCE in Azure until DV3/EV3 servers are released. Scheduled for Q4 FY17.
|System Name||Description||Internal IP||DMZ Internal IP||DMZ External IP|
|SfB01||Skype for Business 2015 Standard Edition Server||10.0.0.5||N/A||N/A|
|Edge01||Skype for Business Edge Server||N/A||192.168.2.4||192.168.1.7|
|App01||App Server (OOS)||10.0.0.9|
|SBC01||AudioCodes Mediant Virtual Edition (VE)||10.0.0.6||N/A||192.168.1.9|
|PBX01||Legacy PBX (3CX)||10.0.0.8|
That’s it for Part 1. In this part we set the stage for what’s to come, and highlighted the high-level architecture.
Continue the series where next we will ready the foundation of our Azure lab. Part 2: Azure Prep Work
As always, feel free to post any questions or comments.