Connecting to Skype for Business: различия между версиями
Alina (обсуждение | вклад) |
Alina (обсуждение | вклад) |
||
(не показано 6 промежуточных версий этого же участника) | |||
Строка 4: | Строка 4: | ||
VIS is a recommended Microsoft interface between the S4B network and networks of traditional VC solutions, which, in addition to call routing, also performs video stream transcoding functions. | VIS is a recommended Microsoft interface between the S4B network and networks of traditional VC solutions, which, in addition to call routing, also performs video stream transcoding functions. | ||
+ | |||
+ | '''1. Creating a trunk in S4B for Vinteo server''' | ||
It is assumed that the S4B system with all the necessary roles, including VIS, is deployed and ready to work. Access the S4B Topology Builder utility. Open the current topology. In the Video Interop Server settings, you need to disable TSL and enable TCP. | It is assumed that the S4B system with all the necessary roles, including VIS, is deployed and ready to work. Access the S4B Topology Builder utility. Open the current topology. In the Video Interop Server settings, you need to disable TSL and enable TCP. | ||
Строка 14: | Строка 16: | ||
* Select the VIS server. | * Select the VIS server. | ||
View after completing the trunk addition. | View after completing the trunk addition. | ||
+ | [[Файл:S4B настройки7.jpg|1000px|безрамки|центр|S4B настройки7]] | ||
+ | After everything is configured, click RMB -> Topology -> Publish and follow the instructions to publish the changes made to the S4B system. | ||
+ | |||
+ | Next the user settings in S4B should be as follows: | ||
[[Файл:S4B настройки 3.jpg|800px|безрамки|центр|S4B настройки 3]] | [[Файл:S4B настройки 3.jpg|800px|безрамки|центр|S4B настройки 3]] | ||
+ | Line URI - this is the SIP user number for registration on the VC. | ||
+ | |||
+ | '''2. It is necessary to create a gateway on the VINTEO server''' | ||
+ | |||
+ | Log in to the server and select "System" -> "Gateways" -> "Add gateway" from the menu. | ||
+ | [[Файл:Skype fB.jpg|800px|безрамки|центр|Skype fB]] | ||
+ | Next, add the gateway. | ||
+ | Attention! In the properties of the gateway, the BFCP parameter must be set to None, otherwise the call will be immediately terminated. | ||
+ | |||
+ | Then you need to create a ‘Loop’ type user. | ||
+ | |||
+ | Now you can create a conference and add the newly created Loop user as a participant and call it into the conference. |
Текущая версия на 11:30, 9 октября 2024
Interaction between VINTEO and Skype for Business (hereinafter referred to as S4B) is carried out through the use of the standard role of the Skype for Business server - Video Interoperability Server, abbreviated as VIS.
VIS is a recommended Microsoft interface between the S4B network and networks of traditional VC solutions, which, in addition to call routing, also performs video stream transcoding functions.
1. Creating a trunk in S4B for Vinteo server
It is assumed that the S4B system with all the necessary roles, including VIS, is deployed and ready to work. Access the S4B Topology Builder utility. Open the current topology. In the Video Interop Server settings, you need to disable TSL and enable TCP.
Next you need to create a Video gateway. To do this, go to Shared Components -> Video gateways -> (RMB) New gateway.
- Enter the full (FQDN) name of the VINTEO VC server and follow the instructions;
- Specify the name of the SIP trunk;
- Specify the SIP port of the VINTEO server (default is 5060);
- SIP transport protocol -> TCP;
- Select the VIS server.
View after completing the trunk addition.
After everything is configured, click RMB -> Topology -> Publish and follow the instructions to publish the changes made to the S4B system.
Next the user settings in S4B should be as follows:
Line URI - this is the SIP user number for registration on the VC.
2. It is necessary to create a gateway on the VINTEO server
Log in to the server and select "System" -> "Gateways" -> "Add gateway" from the menu.
Next, add the gateway.
Attention! In the properties of the gateway, the BFCP parameter must be set to None, otherwise the call will be immediately terminated.
Then you need to create a ‘Loop’ type user.
Now you can create a conference and add the newly created Loop user as a participant and call it into the conference.