【Issue Description】
In private and public networking, a public network software client successfully registers with the SC in SIP mode. When a conference is initiated, the software client leaves the conference soon after joining the conference.
【Possible Causes】
A timeout interval is specified on the router mapping table. If the keepalive interval of the software client registration is less than the timeout interval of the router mapping table, the router will allocate a new port in the subsequent keepalive process, resulting in a call failure.
【Troubleshooting Procedure】
Modify the SIP registration keepalive interval of the SC to ensure that the keepalive interval is less than the timeout interval of the router mapping table.
- Log in to the SMC 2.0 web interface.
- Select the specified SC and click Edit.
- Change the value of Registration keepalive interval for SIP to a value less than the timeout interval specified on the router mapping table.