Skype for Business Cloud Connector Edition release 1.4.1 is 3rd release. To learn more about Skype for Business Cloud PBX, Cloud Connector Edition and different releases, click here. Skype for Business Cloud Connector Edition version 1.4.1 was released in August 22, 2016 with the following updates:
Customization available in CloudConnector.ini file:
Site name is required and it should be unique for each site and must match with PSTN site name defined in Office 365.
Type of Hardware can be defined, by default it is set to “Normal” but it can be set to “Minimum” for smaller deployments that can support up to 50 simultaneous calls.
“CorpDNSIPAddress” must be configured in .ini file to allow windows update for the base VM image. It will be configured on internal interface of temporary VM and should provide the name resolution to the public names. Otherwise, internet connection will fail because of name resolution and deployment will not finish.
The address of WSUS server can be configured for Microsoft updates if required.
The address of WSUS server can be configured for WSUS status update if required.
ForwardPAI determines whether PAI (P-Asserted-Identity) field is forwarded from the Mediation Server to the gateways. By default, it is set to “True” but it can changed to “False”
New CCE Management service has been added on host server to manage HA Detection/Recover, binary auto-upgrade, and operating system auto-upgrade.
There has been 5 new cmdlets introduced and at the same time 3 cmdlets have been deprecated. You can refer to the Cloud Connector cmdlet reference for latest cmdlets. While 2 cmdlets have been updated Install-CcInstanceandUninstall-CcInstancetoInstall-CcApplianceandUninstall-CcAppliance.
Skype for Business Cloud Connector Edition release 1.3.8 is 2nd release. To learn more about Skype for Business Cloud PBX, Cloud Connector Edition and different releases, click here. Skype for Business Cloud Connector Edition version 1.3.8 was released in May 24, 2016 with the following updates:
This version had resolved the issues related to failures of transferring calls to a phone number. If you are facing following challenges then upgrade to latest version of Skype for Business Cloud Connector Edition.
Your Office 365 user account is configured to use Cloud PBX.
You have an active PSTN call using the Skype for Business client on Windows, where the voice for this call uses Skype for Business Cloud Connector Edition.
You start a transfer to another phone number by selecting or entering the phone number from a list of suggested phone numbers on the transfer menu.
In this scenario, the other phone number rings, and you can answer the transferred call, but you hear no audio. Additionally, the client window of the existing active PSTN call shows the following error:
Cannot complete the transfer.
This version also take care about unnecessary files after finishing deployment process such as
The temporary copies of certificates
Exported topology files for the Skype for Business Cloud Connector Edition appliance
There was one major improvement as well in terms of DNS
Now, you can specify multiple DNS IP addresses, separated by spaces, in the CloudConnector.ini file for “CorpnetDNSIPAddress” and “InternetDNSIPAddress” values.
Skype for Business Cloud Connector Edition is a revolutionary offering from Microsoft to connect on-premises voice infrastructure with Skype for Business online. I wrote a series of articles about Skype for Business Cloud PBX and Cloud Connector Edition and this post will give you a holistic view of all the Cloud Connector Edition current and upcoming releases (versions).
Below are the series of blogposts related to Skype for Business Cloud PBX and Cloud Connector Edition:
Cloud Connector Edition is an option for those customers who are new to Microsoft Real Time Communication and directly adopting Skype for Business Online (Office 365) for real time communication. At present to find an organization without any telephony system is almost impossible. When customers are looking for best RTC solution and adopting SfB online, it is crucial for them to leverage existing telephony investment while maintaining seamless user experience across all RTC modalities. Microsoft is committed to provide seamless PSTN calling experience through Cloud Connector Edition to those users who are accessing all the SfB modalities except PSTN calling form SfB online infrastructure.
Let’s discuss more about PSTN calling. In Skype for Business each conversation is divided into two pieces i.e. signaling and media. When you are using CCE all media traffic for PSTN calling will be managed by CCE and PSTN Gateway while signaling will be managed by CCE and SfB online infrastructure.
Whenever, we talk about telephony communication, it could be either inbound or outbound.
Outbound Calling: If a user place a call from internal network:
Users dial an external PSTN number in E.164 format
SIP traffic routes to Skype for Business online infrastructure
SfB online performs a reverse number lookup for the dialed number
The RNL fails because it is an external number and doesn’t belongs to any SfB user
The call is routed to the Edge component of CCE
If the PSTN routes exist Edge Server relays the traffic through Mediation component of CCE
Mediation component sends the traffic to the PSTN gateway and establish a connection between the user end point and PSTN Gateway through Mediation component for media flow
Inbound Calling: If an internal user receive a call from PSTN network:
PSTN Gateway receives a call from external PSTN number for a SfB online user who is in internal network as of now
Gateway routes the SIP traffic to Mediation component of CCE
Traffic goes out from Mediation component to SfB Online through Edge component of CCE
SfB online performs a reverse number lookup
The RNL passes and SfB online finds that this number belongs to the SfB online user
SIP signaling goes to all the point of presence of that user
Finally, Media traffic will be established between PSTN gateway and Mediation component and between Mediation component and the user end point for media flow
These are the features which are available through CCE as of now.
There are many limitation if you will compare it with Skype for Business on-premises or hybrid. Below are the list of limitations:
No call via work or remote call control
No media bypass
No response group
Active call can’t be transferred to the cell phone which is registered in your Active Directory by picking it from a list of suggested phones in the transfer menu. You can transfer to any other number.
Call between SfB user and PSTN number can’t be escalated as conference call
Users must use full number in E.164 format only
Only specific series of Polycom phones are supported as of now
No integration available with contact centers
Private lines and common area phones are also not supported
I tried to cover most of the stuffs but there is no guarantee if you face any other limitation.