The terminal register failure through GK on the SMC

Dear all!

Have a good day!

Today I'll share with you how to deal with the problem that the terminal register failure through GK on the SMC.

Symptom 

When a conference is held on the SMC2.0, the terminals at two sites fail to register with the SMC2.0.

After restarting the terminals, the problem is resolved.

Analysis

1. Analysis of the terminal interface and logs.

   1. Check the terminal interface, the interface displays that the number has logged in to another terminal.

   2. Check the terminal logs to confirm that no registration record is generated from January 28 to the time when the terminal restarts. 

   3. Check the logs before the 28th. It is found that the terminal is forcibly deregistered by the SC at 20:12 on the 27th. The log is as follows:

      
      

      

      According to the terminal policy, SC does not initiate a registration request after deregistering the terminal.

      After the terminal is restarted, the system initiates a registration request again and the terminal is registered successfully.  Therefore, this problem can be solved by restarting the terminal.

2. Analyze SC logs to determine the reason why the SC deregisters the terminal.

   According to the SC logs, the reason why the terminal numbers at the two sites are forcibly deregistered is 0x21100101. Query the error code table. 0x21100101 is the registration name conflict. That is, the same number is registered and the same number is kicked out.

Solution

Modify the same-number kick-out policy of the SC. Set 'When the same URI is used for registration' to 'Reject new registration'. Set 'Conflicting alias processing policy' to 'Check'.

This is all, thanks for reading!