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

Chapter 6 Cisco Unified Serviceability Alarms and CiscoLog Messages Error-Level Alarms OL-22523-01 - 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). - Route/SIP trunk for originating side does exist on remote peer but the port is either used for a SIP phone or a different SIP trunk. If remote peer is Unified CM, in the Unified CM Administration for the remote peer (Device > Trunk), ensure the Destination Port on the originating side is configured to be the same as the incoming port on the terminating side SIP Trunk Security Profile. - 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 the SIP trunk Security Profile assigned to the SIP trunk on the 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. To fix this issue, perform the following steps: a. In the OS Administration, choose Show > Network and verify whether the DNS details are correct. If it is not correct, configure the correct DNS server information by using the CLI command set network dns primary. b. Check the network connectivity with DNS server by using the CLI command utils network ping , and ensure the DNS server is properly configured. Cisco Unified Communications Manager Managed Services Guide 6-195