This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Microsoft Skype for Business StyleBook
The Skype for Business 2015 application relies on several external components to function. The Skype for Business network consists of various systems, such as servers and their operating systems, databases, authentication and authorizing systems, networking systems and infrastructure,and telephone PBX systems. Skype for Business Server 2015 is available in two versions, Standard Edition and Enterprise Edition. The primary difference is in support for high-availability features that are only included in the Enterprise Edition. To implement high availability, multiple Front-End servers must be deployed to a pool and SQL servers must be mirrored.
An Enterprise Edition deployment enables the creation of multiple servers with different roles.
The primary components in Skype for Business 2015 application are:
- Front-end servers
- Edge servers
- Director servers
- Database (SQL) servers
In the Skype for Business application, the Front-End server is the core server in your network. It provides the links and services for user authentication, registration, presence, address book, A/V conferencing, application sharing, instant messaging, and web conferencing. If you are deploying Skype for Business 2015 Enterprise edition, the topology typically consists of at least two Front-End servers load balanced in a Front-End pool with a database server that hosts the SQL Server instance holding the Skype for Business database.
Deploying Edge servers for Skype for Business is necessary if external users who are not logged into your organization’s internal network need to be able to interact with internal users. These external users could be authenticated and anonymous remote users, federated partners, or other mobile clients.
There are four types of roles in Skype For Business Edge server:
- Access Edge, which handles SIP Traffic and authenticates external connections, allows remote connection and allows federation Connection
- Web Conferencing, which handles Data Conferencing Packets, and allows external users to access Skype for Business
- A/V Conferencing, which handles A/V Conferencing Packets, and extends audio and video, app sharing and file transfer to external users
- XMPP Proxy, which handles XMPP packets, and allows XMPP based servers or clients to connect to Skype for Business.
The main function of the Director server in Skype for Business 2015 is to authenticate endpoints and “direct” the users to the pool that contains their account. In Skype for Business 2015, though the Director is a completely dedicated and specific role on a standalone server, it is an optional server. This facilitates security by making it easier to deploy or remove the configurations.
Directors are most useful where multiple pools exist because they provide a single point of contact for authenticating endpoints. Also, for remote users, a Director serves as an extra hop between the Edge pool and Front-End pool, adding an extra layer of protection against attacks.
The following figure diagrammatically represents the deployment of Skype servers in the network:
The following table lists the IP addresses used in the sample configuration included in the instructions below:
|Skype for Business Servers||Virtual IP Address||Server IP Addresses||Citrix ADC Instance|
|Edge Servers||External VIP - 22.214.171.124||126.96.36.199; 188.8.131.52||10.102.29.141|
|Internal VIP - 10.10.10.20||10.10.10.21; 10.10.10.22|
|Front-end Servers||10.10.10.10||10.10.10.11; 10.10.10.12||10.102.29.60|
|Director Server||10.10.10.30||10.10.10.31; 10.10.10.32||10.102.29.93|
To configure front-end servers
- In Citrix Application Delivery Management (ADM), navigate to Applications > Configuration, and click Create New. The Choose StyleBook page displays all the StyleBooks available for your use in Citrix ADM. Scroll down and select Microsoft Skype for Business 2015 StyleBook. The StyleBook opens as a user interface page on which you can enter the values for all the parameters defined in this StyleBook.
- In the Edge Server section, enter the following virtual IP (VIP) addresses and IP addresses of all the Edge servers in the network.
- External VIP address and IP addresses for the Edge servers that will be used for Access Edge, web conferencing Edge, and A/V Edge.
- Internal VIP address and IP addresses for the Edge servers that will be connected to the internal network.
- Two external and two internal Edge servers in your network.
- In the Front-End Server section, enter the IP address of the virtual Front-End server (VIP) that is to be created for the Skype for Business Front-End servers. Also, enter the IP addresses of all the Skype for Business Front-End servers in the network.
- In the Director Server section, enter the virtual IP address (VIP) for the Director servers that is to be created for the Skype for Business application. Also, enter the IP addresses for all the Skype for Business Director servers in the network. Create at least two Director servers for high-availability.
- The Advanced Settings section lists all the default ports configured on the Citrix ADC instances for the three Skype servers.
The following table provides you a list of all default ports and protocols:
|HTTP Port||80||HTTP||Used for communication from Front-End Servers to the web farm FQDNs when HTTPS is not used.|
|HTTPS Port||443||HTTPS||Used for communication from Front-End Servers to the web farm FQDNs.|
|AutoDiscover Internal Port||4443||HTTPS||HTTPS (from Reverse Proxy) and HTTPS Front-End inter-pool communications for AutoDiscover sign-in.|
|RPC Port||135||DCOM and remote procedure call (RPC)||Used for DCOM based operations such as moving users, user replicator synchronization, and address book synchronization.|
|SIP Port||5061||TCP (TLS)||Used by Front-End servers for all internal SIP communications.|
|SIP Focus Port||444||HTTPS, TCP||Used for HTTPS communication between the Focus (the component that manages the Skype conference state) and the individual servers.|
|SIP Group Port||5071||TCP||Used for incoming SIP requests for the response group application.|
|SIP AppSharing Port||5065||TCP||Used for incoming SIP listening requests for application sharing.|
|SIP Attendant Port||5072||TCP||Used for incoming SIP requests for the attendant (that is, for dial-in conferencing).|
|SIP Conf Announcement Port||5073||TCP||Used for incoming SIP requests for the Skype for Business server conferencing announcement service (that is, for dial-in conferencing).|
|SIP CallPark Port||5075||TCP||Used for incoming SIP requests for the CallPark application.|
|SIP Call Admission Port||448||TCP||Used for call admission control by the Skype for Business server bandwidth policy service.|
|SIP Call Admission TURN Port||5080||TCP||Used for call admission control by the bandwidth policy service for Audio/Video Edge TURN traffic.|
|SIP Audio Test Port||5076||TCP||Used for incoming SIP requests for the audio test service.|
|HTTPS External Port||443||HTTPS||Used for external ports for SIP/ TLS communication for remote user access, accessing internal Web conferences, and STUN/TCP inbound and outbound media communications for accessing internal media and A/V sessions.|
|HTTPS Internal Port||443||HTTPS||Used for internal ports for SIP/ TLS communication for remote user access, accessing internal Web conferences, and STUN/TCP inbound and outbound media communications for accessing internal media and A/V sessions.|
|SIP External Remote Access Port||5061||TCP||Used for external ports for SIP/MTLS communication for remote user access or federation.|
|SIP Internal Remote Access Port||5061||TCP||Used for internal ports for SIP/MTLS communication for remote user access or federation.|
|SIP External STUN UDP Port||3478||UDP||Used for external ports for STUN/ UDP inbound and outbound media communications.|
|SIP Internal STUN UDP Port||3478||UDP||Used for internal ports for STUN/UDP inbound and outbound media communications.|
|SIP Internal IM Port||5062||Used for internal ports for SIP/MTLS authentication of IM communications flowing outbound through the internal firewall.|
|HTTP Port||80||TCP||Used for initial communication from Directors to the web farm FQDNs.|
|HTTPS Port||443||HTTPS||Used for communication from Directors to the web farm FQDNs.|
|AutoDiscover Internal Port||4443||HTTPS||Used for HTTPS (from Reverse Proxy) and HTTPS Director inter-pool communications for AutoDiscover sign-in.|
|SIP Internal Port||5061||TCP||Used for internal communications between servers and for client connections.|
6. In the Target Instances section, select the three different Citrix ADC instance on which to deploy the three Skype for Business servers.
You can also click the refresh icon to add recently discovered Citrix ADC instances in Citrix ADM to the available list of instances in this window.
7. Click Create to create the configuration on the selected Citrix ADC instances.
Citrix recommends that you select Dry Run to check the configuration objects that must be created on the target instance before you execute the actual configuration on the instance.
When the configuration is successfully created, the StyleBook creates 25 load balancing virtual servers. That is, for each port, one load balancing virtual server is defined along with one service group, and the service group is bound to the load balancing virtual server. The configuration also adds the Front-End servers as service group members and binds them to the service group. The number of service group members created is equal to the number of Front-End servers created.
The following figure shows the objects created in each server:
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select Do Not Agree to exit.