[cisco-voip] CTIManager error - Directory Change notification request timed out

[Kevin Thorngren]

Hi Erick,

Looks like you are hitting CSCsd17315.  CSCsd17315 was found in 4.1(3) 
by Ryan but it looks as though it can be seen in 4.0(2a).  Maybe Ryan 
can expand upon this if needed but my understanding is that a CTI 
application tried to connect using OpenProvider but then was 
unexpectedly shutdown.  CSCsd17315 is a problem in the way this is 
handled by the CTI Manager.  The fix is in the way CTI Manager uses 
certain timers (actually not important for our discussion).  Restarting 
CTI Manager should alleviate the messages from appearing every minute.

WebDialer might not be the issue, it is hard to tell from the snippet 
of trace.  What I do see is that WebDialer is exchanging heartbeats 
with the server using process ID of 3,200,9,197.  The application that 
had the problem looks like it had process ID 3,200,9,201.  One would 
need to track the ID of 3,200,9,201 backwards in the traces to get more 
information regarding the application.

HTH,
Kevin

On May 5, 2006, at 1:47 AM, Erick Bergquist wrote:

> Hi,
>
> Anyone have a idea on this one by chance? These started out of blue it 
> looks like on a subscriber server and am not seeing where they are 
> coming from. WebDialer service is disabled/not-running under service 
> activation cluster wide also.  Call manager 4.0(2a) SR2c
>
> It looks like another server may be doing something with WebDialer 
> (even though it is not running cluster wide) and it is having issue 
> because the service is not active.
>
> These event log entries occur once a minute.
>
> Event Type:    Error
> Event Source:    Cisco CTIManager
> Event Category:    None
> Event ID:    3
> Date:        5/4/2006
> Time:        10:21:21 PM
> User:        N/A
> Computer:    CCMSUB
> Description:
> Error: kCtiEnvProcDevListRegTimeout - Directory change notification 
> request time out.
>   App ID: Cisco CTIManager
>   Cluster ID: StandAloneCluster
>   Node ID: 10.1.1.1
> Explanation: CTIManager registration request to EnvProcDevList timed 
> out; CTIManager will send another registration request.
> Recommended Action: If problem persists, contact TAC..
>
> CTI detailed traces only had the directory notification entry message 
> when this error occurs.
>
> CTI SDL traces have the below.
>
>
> 008817319| 06/05/04 22:20:59.465| 003| AppInfo   |                     
>                   |                               | 
> CTIHandler(3,200,9,197)         |                                 |    
>                                      | [CTI-APP] 
> [CTIHandler::OutputCtiMessage      ]     CTI   Server Heartbeat   ( 
> application name=Cisco WebDialer)
>
> 008817320| 06/05/04 22:21:10.871| 003| AppInfo   |                     
>                   |                               | 
> CTIHandler(3,200,9,197)         |                                 |    
>                                      | [CTI-APP] 
> [CTIHandler::processIncomingMessage]     CTI   Client Heartbeat   ( 
> application name=Cisco WebDialer)
>
> 008817321| 06/05/04 22:21:10.871| 003| SdlSig    | CtiHeartbeat        
>                   | ready                         | 
> CTIHandler(3,200,9,197)         | CTIHandler(3,200,9,197)         | 
> (3,200,10,1).970826-(*:*)               | [NP - HP: 0, NP: 0, LP: 0, 
> VLP: 0, LZP: 0]
>
> 008817322| 06/05/04 22:21:12.511| 003| SdlSig    | 
> CtiClientHeartbeatTimer               | ready                         
> | CTIHandler(3,200,9,197)         | SdlTimerService(3,200,3,1)      | 
> (3,200,10,1).877096-(*:*)               | [HP - HP: 0, NP: 0, LP: 0, 
> VLP: 0, LZP: 0]
>
> 008817323| 06/05/04 22:21:21.121| 003| AlarmErr  |                     
>                   |                               |                    
>              |                                 |                       
>                   | AlarmClass: CtiManagerAlarmCatalog, AlarmName: 
> kCtiEnvProcDevListRegTimeout, AlarmSeverity: Error AlarmMessage: , 
> AlarmDescription: Directory change notification request time out., 
> AlarmParameters:  AppID:Cisco CTIManager, ClusterID:StandAloneCluster,
>
> 008817324| 06/05/04 22:21:21.121| 003| AppInfo   |                     
>                   |                               | 
> CtiManager(3,200,10,1)          |                                 |    
>                                      | 
> CtiManager::ready_CtiMgrCtiHandlerSSAPIRegNotificationTimer - Sending 
> SSAPIRegistrationNotification to CTIHandler
>
> 008817325| 06/05/04 22:21:21.121| 003| SdlError  |                     
>                   |                               |                    
>              |                                 |                       
>                   | Destination process is not 
> Active:[3,200,10,1]->[3,200,9,201] - 
> [SSAPIRegistrationNotificationReq]
>
> 008817326| 06/05/04 22:21:21.121| 003| SdlExcept | SdlProcessNE        
>                   | ready                         | 
> CtiManager(3,200,10,1)          |                                 |    
>                                      | Error: 
> FSM_NO_TRANSITION_DEFINED Description: A transition is not defined for 
> the input signal. Check state machine definition in 
> initStateMachine().
>
> 008817327| 06/05/04 22:21:29.371| 003| SdlSig    | 
> CtiServerHeartbeatTimer               | ready                         
> | CTIHandler(3,200,9,197)         | SdlTimerService(3,200,3,1)      | 
> (3,200,10,1).877096-(*:*)               | [HP - HP: 0, NP: 0, LP: 0, 
> VLP: 0, LZP: 0]
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>