No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

CloudEC V600R019C00 Troubleshooting (Enterprise On-premises, Convergent Conference)

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
An Endpoint Fails to Register with the SC Server in SIP Mode

An Endpoint Fails to Register with the SC Server in SIP Mode

Symptom

An endpoint fails to register with the SC server in SIP mode.

Possible Causes

The possible causes are as follows:

  • The registered site URI, authentication user name, or authentication password is incorrect.
  • The transmission type of the SC server is different from that of the endpoint.
  • The SSL version of the SC server is different from that of the endpoint.

Procedure

  1. Ensure that the SIP site URI,authentication user name, and authentication password added on the SMC2.0 are the same as those configured on the web interface of the endpoint.
  2. Check the consistency of the transmission type between the SMC2.0 and the endpoint.

    • Log in to the web interface of the SMC2.0 and choose Devices > Switch Centers.Click the corresponding SC in the SC list. On the Details tab page, check the transmission type supported by SIP.Three transmission types are available: TCP, UDP, and TLS.
    • Log in to the web interface of the endpoint, choose System Settings > Network,and check the value of Transmission type for SIP in H.323/SIP Settings.

  3. If the endpoint uses TLS for registration, ensure that the SSL version of the SC is the same as that of the endpoint.
  4. The SC newly installed on the VC5.2 has SSLv3 and TLS1.0 disabled by default. It supports only TLS1.1.
  5. Log in to the web interface of the endpoint, choose System Settings > Network, and check whether the value of SSL version for SIP in H.323/SIP Settings is TLS1.1. If not, change the value to TLS1.1.

    NOTE:

    The VCT endpoint has no SSL version configuration item. If the VCT needs to register with the SC of the VC5.2 in SIP mode, log in to the SC in SSH mode to enable SSLv3 and TLS1.0. The same command is used to enable or disable the two protocols. The command for querying the enable/disable status of the protocols and that for enabling the protocols are as follows:

    • Command for displaying the security level on the SC:

      <SC>dissys-config

      <SC>SYS_SSL_LEVEL:TLSv1.1 (SMC2.0 V500R002C00SPC700 and later)

    • Command for enabling diefferent security levels on the SC:

      <SC>system-view sys-config common-config ssl-lowest-level (1: SSLV3; 2: TLS1.0; 3: TLS1.1; 4: TLS1.2)

      After the modification, restart the SC.

Summary

  1. Ensure that the site number,authentication user name, and authentication password added on the SMC2.0 are the same as those configured on the endpoint.
  2. Ensure the consistency of the transmission type and the SSL version.
Translation
Download
Updated: 2019-08-07

Document ID: EDOC1100059098

Views: 20255

Downloads: 12

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next