This document describes how to track heartbeat messages between Customer Voice Portal (CVP) Callserver and Voice Response Unit Peripheral Interface Manager (VRU PIM) using VRU PIM logs and Wireshark capture.
Cisco recommends that you have knowledge of these topics:
Callserver and Voice Response Unit Peripheral Interface Manager (VRU PIM)
The information in this document is based on these software versions:
CVP Server 9.0 and above
UCCE 9.0 and above
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Heartbeat messages are exchanged between CVP Call Server and VRU PIM using the port configured on the ICM subsystem of the CVP Call Server. The default port number is 5000.
In order to track heartbeat messages between CVP and VRU PIM, there are several steps that need to be executed.
Step1. On the VRU PIM side, increase the level of traces. The default trace level does not show any heartbeat messages.
If you enable only hearbeat traces ( *heartbeat* /on), the logs won't show the hearbeat intearcation between CVP and VRU PIM, you see only this :
18:58:00:552 pg2A-pim1 Trace: PIMActiveHeartbeat
18:58:05:536 pg2A-pim1 Trace: PIMActiveHeartbeat
18:58:10:536 pg2A-pim1 Trace: PIMActiveHeartbeat
18:58:15:537 pg2A-pim1 Trace: PIMActiveHeartbeat
18:58:20:537 pg2A-pim1 Trace: PIMActiveHeartbeat
But if you have trace *heartbeat* /on and trace *session* /on it actually shows you the messages in the VRU PIM logs with the sequence numbers:
Here is the example on how to enable the VRU PIM traces:
Warning: Increase the level of traces in a production envorment can degradade the performance of the system.
There are 3 messages that complete one heartbeat exchange.