This post was last edited by wangjun188 at 2018-12-11 03:34.
This post was last edited by wangjun188 at 2018-12-11 03:34.
This post was last edited by wangjun188 at 2018-12-11 03:34.
Issue Description：
An MCU fails to register with the Lync2010 or Lync2013 server.
Possbile reason：
- The registration user name or password is incorrect.
- The registration mode or port is incorrect.
- No TLS certificate is imported when the MCU registers with the Lync server in TLS mode.
Solution :
1. Log in to the MCU web interface. Move the cursor to the registration failure icon in the lower right corner to view the failure cause. Alternatively, log in to the MCU through SSH or Telnet, and run the sip reg command to view the value of regfailreason, which specifies the SIP registration failure cause.
a.If the web page displays a DNS parsing failure
Check whether the domain names configured on the DNS server and in the server address bar are correct. If they are incorrect, correct them.
b.If return code 401 or 404 is displayed for the SIP registration
This fault is caused by an authorization failure or a failure to find a number. If this occurs, ensure that the registration user name and password are correct. If they are incorrect, correct them.
c.If return code 408 or 409 is displayed for the SIP registration
This fault is caused by an error on the transport layer; that is, SIP signaling packets fail to be sent. For details about how to rectify the fault, go to Step 2.
2. Perform the following operations to rectify the fault:
a.Ensure that the protocol is TCP or TLS.
b.Ping the server address on the MCU. Ensure that the server address is correct.
c.Ensure that the SIP server port is the same as the port enabled on the endpoint.
If the registration is performed in TCP mode, ensure that the TCP port is enabled on the server and is the same as that configured on the endpoint.
If the registration is performed in TLS mode, ensure that the TLS port number is set to 5061, and that the TLS port is enabled on the server and is the same as that configured on the endpoint.
d.If the registration is performed in TLS mode, ensure that the required certificate is imported correctly.
i.Restart the endpoint after importing the certificate for it to take effect.
ii.Run the sip tls command to check whether the information in RootCert INFO is the same as the information in the certificate file. If they are different, the certificate may be incorrect. Import a correct certificate.
iii.Run the dis clock command to check whether the time on the MCU is the same as the time on the Lync server. If the time difference between them is relatively large, run the sys clock command to calibrate the time on the MCU.
iv.If the registration is performed using a server, configure static route on the Lync server and import the server certificate, private key, and private key password on the MCU. If a certificate is available on the MCU, delete the existing certificate. Related commands are described as follows:
file rm /ata00:1/certificate/server.pem: Delete the server certificate.
file rm /ata00:1/certificate/ private-key.pem: command to delete the private key.
file rm /ata00:1/certificate/private-key-password.txt: Delete the private key password.
file ll /ata00:1/certificate: Check the certificate.
v.If the registration is performed using a client, check the certificate on the MCU. If the MCU contains a certificate (including the private key and private key password), but the certificate is not the certificate of the Lync server to be registered, delete the certificate and import the correct certificate.
