SIP client registrations fail
Possible cause 1: Incorrect SIP client configuration.
Solution: Verify the SIP client configuration. The SIP clients must be configured with SSM as
their outbound proxy. Also ensure that the username and password configured on the client
matches with the ones configured on the central SIP server.
Possible cause 2: SIP domain name for SIP survivability is not configured.
Solution:
Verify SSM mode using the show ssm sip-server status command. If SIP survivability
module is running in either Backup Wan Up Mode or Backup Wan Down Mode, verify that the
SIP domain name is configured using the show ssm sip-server configuration command. If none
are configured, configure the SIP domain name for the deployment using the domain CLI
command under configure/voice/service/voip/ssm/sip-server.
Figure 29: Sample SIP domain configuration
Figure 30: show ssm sip-server configuration output after SIP domain name configuration
Possible cause 3: CAC exclude pool not configured.
Solution: If the central SIP server and SIP clients are reachable through a single interface on
the Secure Router, then a special configuration is required on SSM to distinguish the SIP
clients.
Use cac exclude pool to configure the subnet mask used by SIP clients in the branch.
SSM only accepts the REGISTER requests from endpoints belonging to this pool. When SSM
rejects a REGISTER request for this reason, it adds a warning header with the string Warning:
Common issues
Troubleshooting August 2013 193
To Next Page
Loading...
