Hi, there!
Good day to you!
This topic describes how to deal with the problem that site call with SMC2.0 fails to be connected.
Issue Description
We have three TE endpoints registered with the embedded SC of an SMC2.0 and we want to perform a site call but it is failing for an unknown reason.
Why a site call cannot be performed in a solution with SMC?
Solution
As you know a SiteCall is a unique conference function provided by Huawei that allows users to define conferences and participants on the endpoint/s, making it simple to initiate a multi-party conference, that can be seen as a conference even on SMC even though the multi-point conference was initiated from an endpoint.
Users can create conferences using the touch panel, web interface, or remote control of the endpoint. After setting conference parameters (such as the conference name, data rate, and the number of sites), the users can start the conference.
In the solution with SMC2.0, the TE terminals must register with GK successfully otherwise the Site Call function does not work.
Therefore, I will describe here the configuration and a correct call flow of a Site Call:
The working scenario of a Site Call:
Start a conference by adding the endpoint that you wish to be called by the Site Call originator.
After the call was connected we can check as per below that the Site Call appears as an ongoing conference in SMC under which the endpoints are registered and you can even manipulate the conference from SMC, as per the below pictures:
You need to know that in order for a Site Call to work the endpoints must be registered under the SMC and also to have HTTPS mode set to Enabled:
The non-working scenario of a Site Call:
When you try to perform a Site Call you receive the following error:
Check the configuration of the HTTPS mode, if is disabled as per below you must set it as Enabled:
The reason why the HTTPS mode must be enabled in order to be able to perform Site Calls directly from the endpoints is that in a Site Call operation, the request sent by the originator endpoint towards the SC, is one of an HTTPS request which is made on 443 port:
Thanks!
