Wednesday, April 19, 2017
Deploying a Sonus Cloud Link CCE
Deploying a Sonus Cloud Link CCE
I recently was working on a Sonus v2 Cloud Connector Edition (CCE) working with the new hardware, testing the install, etc. when I ran into a deployment snag. In general, I find the there are a lot of post and blogs about when to use CCE and when you cannot, but few on how to properly deploy CCE let alone the Sonus version.
I decided to show a walk through on the process I used to deploy, why I used the names/options that I did, and the errors and gotchas I ran into.
To start, I am working with a Sonus SBC 1k Cloud Link with the CCE package installed. From a Sonus part number, that would be SBC-1K-SIP-E-CL. The Cloud Link version includes an imbedded Windows 2012 R2 Server with 32 GB of RAM, dual Xeon quad-core 1.7GHz (that�s 8 physical cores. 16 logical), and a 512GB SSD drive. All-in-all, not a bad server and very capable of running the �small� CCE build. That, along with the nicely integrated SBC makes this solution simple�as long as you know the answers to the questions.
Starting off the build of the ASM is not any different from other ASM buildouts � the only difference being the Task option on the Cloud Link version shows Office 365� Cloud Connector Edition vs. Skype �for Business Survivable Branch.
No comments:
Post a Comment