Cisco MCS-7825-H3-IPC1 Service Guide - Page 522

Warning-Level Alarms Chapter 6 Cisco Unified Serviceability Alarms and CiscoLog Messages Recommended Action The available peer list is for notification purposes only; no action is required. For unavailable peers, the following corrective action should be taken. • For Remote = 503, the possible reasons are: - Route/SIP trunk for originating side does not exist on remote peer. If remote peer is Unified CM, add a new SIP trunk in Unified CM Administration for the remote peer (Device > Trunk) and ensure the Destination Address and Destination Port fields are configured to point to the originating host (the originating host is the same node on which this alarm was generated). Also ensure the new SIP trunk has the incoming port in associated SIP Trunk Security Profile configured to be the same as originating side SIP Trunk destination port. - Route/SIP trunk for originating side does exist on remote peer but port is either used for SIP phone or other SIP trunk. If remote peer is Unified CM, in the Unified CM Administration for the remote peer (Device > Trunk), ensure the incoming port in associated SIP Trunk Security Profile is configured to be same as originating side SIP Trunk destination port. - Remote peer has limited resources to handle new calls. If remote peer is administered by a different system administrator, communicate the resource issue with the other administrator. • For Remote = 408, the possible reason includes: - Remote peer has limited resources to handle new calls. If remote peer is administered by a different system administrator, communicate the resource issue with the other administrator. • For Local = 1, the possible reason could be that no responses are received for OPTIONS request after all retries, when UDP transport is configured in SIP Trunk Security Profile assigned to the SIP trunk on originating side. To fix this issue, perform the following steps: - If remote peer is Unified CM, in the remote peer Serviceability application, choose Tools > Control Center (Feature Services) and ensure the Cisco CallManager service is activated and started. - In the Unified CM Administration for the remote peer, choose Device > Trunk, and ensure the SIP trunk exists with the incoming port in associated SIP Trunk Security Profile configured to be same as originating side SIP Trunk destination port. - Check the network connectivity by using the CLI command utils network ping at the originating side. • For Local = 2, the possible reason could be that Unified CM is unable to create the socket connection with remote peer. To fix this issue, perform the following steps: - If remote peer is Unified CM, in the remote peer Serviceability application, choose Tools > Control Center (Feature Services) and ensure the Cisco CallManager service is activated and started. - In the Unified CM Administration for the remote peer, choose Device > Trunk, and ensure the SIP trunk exists with the incoming port in associated SIP Trunk Security Profile configured to be same as originating side SIP Trunk destination port. - Check the network connectivity by using the CLI command utils network ping at the originating side. • For Local = 3, the possible reason could be that DNS server is not reachable, or DNS is not properly configured to resolve the hostname or SRV which is configured on the local SIP trunk. 6-288 Cisco Unified Communications Manager Managed Services Guide OL-22523-01