Proposed Solution

Procedure

On the MPP, navigate to the $AVAYA_MPP_HOME/logs/process/SessMgr directory and open the SessionSlot###.log files.
Where ### is a three-digit ID number.
To see if Converse-on data is received by the MPP, check the Session Manager logs for entries that contain the following text:
```
waiting for ConverseOnData
received converse on digits
```
If the Session Manager logs indicate that Converse-on data is:
- Not received, go to Step 4.
- Received, go to Step 5.
Verify with the Communication Manager programmer or administrator that the vector is properly configured and is sending the expected data.
Navigate to the $AVAYA_MPP_HOME/logs/process/VB directory and open the SessionSlot###.log files.
Where ### is a three-digit ID number.
To verify that the Converse-on data is added to the query string that is sent to the application, search the VB logs for the term "converse":
In these logs, the Converse-on digits collected by the Session Manager should be part of a query string sent to the application server as:
```
&session vpconverseondata=###...
```
Where ###... is the sequence of digits sent.
On the application server, verify that the Converse-on data is being received.
Contact your application developer if you need assistance.