Cloud Connector Edition 2.0 - What's new?

-

Hi all,

i have listed the updates and improvements made with Cloud connector Edition Version 2.0
The both first improvements are the most interesting ones.

The CCE installation now supports more Cloud PBX User and a much higher call volume.
With a support of 500 concurrent SIP Call per CCE, it was in the past possible to run with 4x CCE 1.500 simultaneous calls, while 1 CCE was reserved for High Availability.
The ratio of 1:10 meaning, we had support for up to 15.000 Cloud PBX User pre CCE Site.

Now with the improvement for up to 16 Node:
  • we can have up to 7.500 simultaneous calls, this is Large Enterprise ready!
  • we support up too 75.000 Cloud PBX Users per CCE Site.
More details and configuration information you will finde here:
http://www.uclabs.blog/2017/05/media-bypass-with-cloud-connector-editon.html
Lets have a look into all important feature added:
  • Media Bypass
  • Support of 16 Cloud Connector Editions per one PSTN Site
  • Ability to manipulate SIP headers for billing or interoperability purposes
  • Use of Office 365 Skype for Business account instead of a Global Administrator account
  • Autogenerated passwords for local administrators of Cloud Connector instances
  • Hybrid Voice flag in Mediation Service User Agent to better distinguish Cloud Connector calls in the Call Quality Dashboard
  • Improvements to self-monitoring and self-troubleshooting process
  • Disabling SSL 3.0 by default for all services used by Cloud Connector Edition
    https://technet.microsoft.com/library/security/3009008
The Technet planning link to Cloud Connector Edition  is here:


More details about the History-Info and ForwardPAI headers can be found here http://download.microsoft.com/download/2/4/5/245583A7-E9E1-403B-BD15-AB711C7DF744/Lync%202013%20Head...


 Author:

Comments

Post a Comment

Popular posts from this blog

How to hide users from GAL if they are AD Connect synchronized

-
Image
How to hide and un-hide users from Global Address List (GAL) in Exchange Online if they are AD Connect synchronized Hiding User from GAL isn't possible if those are synchronized form On-Premises Active Directory. The local AD is the leading system for all important attributes, like SMTP, UPN and hiding from GAL. Especially during a cross-tenant migration, you do not want to see not migrated user in the GAL. Those User aren't actively working until their cut-over day. Since the Exchange Online attribute  msExchHideFromAddressList s is an AD on-premises parameter, we have two possible ways hiding user in BME from GAL.   Modify the AD Connect for your teant with a custom rule, by using a extensionAttribute to set the HidefromGAL. In this rule, for users which have an entry in the extensionAttribute, hiding / un-hiding will be controlled by AD Connect This is the best option for Cross-Tenant Migration, if you run 2 or more AD Connect system We direct modif...
Read more

Cannot join external Lync Meeting: Lync Edge Server Single IP Address (Lync Edge Server Single IP Web Conferenceing Problem)

-
Image
Lync Edge Server FQDN and IP PORTS (Version 1.2, Update 26.11.2014) As we all know, we can configure Lync Edge Server in several way. 1) Single Edge Server with a SINGLE IP ADDRESS 2) Single Edge Server with MULTIPLE IP ADDRESSES (3x IPs) 3) Multiple Edge Server in a Pool, with MULTIPLE IP ADDRESSES (Zx 3 IPs) Regardless what we are going to configure, there are common / well-known TCP Port necessary making Lync work, which are: Access: Port: 443 and 5061 Conferencing: Port: 443 and (444) AV: Port: 443 (I have not listed other ports, e.g. STUN or the dynamic port range. This is not required for the topic discussed here) External FQDN with single IP address: What can we see here? If we are going to choose a single IP address, we would have TCP Port overlapping. Therefore the only way avoiding this is assigning other ports. Additionally we will also see and are reminded that Lync highly depends on DNS. If we have single IP, we must have use single, uniqu...
Read more

MFA with Guest Access and different tenants settings

-
Image
There is an update regarding MFA Multi Factor Authentication. If you are guest with a different Tenant, the MFA Settings are now reflecting the settings of all tenants in a different way. Each MFA setting is reflected and you can setup your MFA device as per tenant and the admin settings allow. Login to your Profile in Office 365/ Azure AD: https://account.activedirectory.windowsazure.com/r/#/profile or https://myapps.microsoft.com Go to your PROFILE: Sign in to https://myapps.microsoft.com Select your account name in the top right, then select profile. Select Additional security verification. If might be happen, your admin hast configured MFA, so you wouldn't see this menu. Simply switch the tenant to the guest tenant where you need to configure MFA. Once you go back to your profile and you will find the MFA device and other settings a usual:
Read more