Recovery on timer expiry

-


564789: Feb  3 04:20:29.742: ISDN Se0/2/0:23 Q931: RX <- SETUP pd = 8  callref = 0x01B0
        Bearer Capability i = 0x8090A2
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA98381
                Exclusive, Channel 1
        Facility i = 0x9F8B0100A1080201010201008400
                Protocol Profile =  Networking Extensions
                0xA1080201010201008400
                Component = Invoke component
                        Invoke Id = 1
                        Operation = CallingName
                                Name not available
        Calling Party Number i = 0x1183, '91XXXXXXXXXX'
                Plan:ISDN, Type:International
        Called Party Number i = 0x80, 'XXXX'
                Plan:Unknown, Type:Unknown
564823: Feb  3 04:20:29.766: ISDN Se0/2/0:23 Q931: TX -> CALL_PROC pd = 8  callref = 0x81B0
        Channel ID i = 0xA98381
                Exclusive, Channel 1
564824: Feb  3 04:20:39.801: ISDN Se0/2/0:23 Q931: RX <- RELEASE pd = 8  callref = 0x01B0
        Cause i = 0x82E6 - Recovery on timer expiry
564825: Feb  3 04:20:39.801: ISDN Se0/2/0:23 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x81B0

As it seems to be timer issue, in my case the problem was overlapping dial-peer.

Comments

Post a Comment

Popular posts from this blog

Status: Local Agent is not responding. This may be due to Master or Local Agent being down.

-
If you have read my previous post , you would understand why LA and MA services are important for such a scenario and no component has backed-up, rather you get the above error message. Symptoms -   All Disaster Recovery Framework (DRF) services are down, and no new devices, schedules, or statuses can be viewed from the DRF console. Also, when you access the DRF admin pages, the above error message is received. Affected CM releases 6.1.5 and later. Resolution In order to resolve it, first, verify if the Certificate Serial Number in the keystore of Publisher is present in the Truststore of all Subscribers. Complete these steps: Log on to CUCM OS Administration page of Publisher server of the cluster setup. Choose Security > Certificate Management . The Certificate List window displays. You can use the Find controls in order to filter the certificate. Click on the ipsec.pem file and check the serial number of the certificate. Log on to CUCM OS Administr
Read more

Understanding code yellow

-
Understanding sample code yellow alert- Oct 3 01:00:10, cms01, Error, Cisco CallManager, ccm: 147896: Oct 03 05:00:10.616 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowEntry: CodeYellowEntry Expected Average Delay:362 Entry Latency:20 Exit Latency:8 Sample Size:10 Total Code Yellow Entry:14 High Priority Queue Depth:2 Normal Priority Queue Depth:12 Low Priority Queue Depth:70 Cluster ID:StandAloneCluster Node ID:cms01, 3652 The above alert is about code yellow entry, it shows the time when server enters code yellow state. There are no specifications to note at this alert, CM enters code yellow when it achieves the mentioned conditions for code yellow state as mentioned in service parameters. Oct 3 01:00:12, cms01, Error, Cisco CallManager, ccm: 147897: Oct 03 05:00:12.268 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowExit: CodeYellowExit Expected Average Delay:0 Entry Latency:20 Exit Latency:8 Sample Size:10 Time Spent in Code Yellow:2 Number of Calls Rejected Due to C
Read more