Cisco Cisco Computer Telephony Integration Option 8.5 Troubleshooting Guide
1-35
CTI OS Troubleshooting Guide for Cisco ICM/IPCC Enterprise & Hosted Editions Release 7.1(1)
Chapter 1 Problems and Symptoms
Silent Monitor Problems (IPCC Only)
ToS/QoS Problems
Symptom
TCP packets going from CTI OS server to CTI Toolkit don’t have
TOS/QoS tagged.
Possible Cause
Ensure that the TOS/QoS is properly configured on the system
where CTI OS Server resides. Make sure that the following registry has TOS
value set to 0x68:
value set to 0x68:
HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems, Inc.\CTIOS\
CTIOS_<InstanceName>\ctios1\Server\Connection
Also make sure that the following system registry value
“DisableUserTOSSetting” is set to 0. It can be found under:
“DisableUserTOSSetting” is set to 0. It can be found under:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
Services\TcpIp\Parameters.
Note
The system needs to be restarted if the “DisableUserTOSSetting” registry value
has been changed.
has been changed.
Symptom
TCP packets going from CTI Toolkit to CTI OS server don’t have
TOS/QoS tagged.
Possible Cause
This symptom may have multiple causes:
–
TOS tagging is NOT implemented in the Java or .NET (C#) CILs. A
system using these could support one way tagging from server to client,
but traffic from the client to the server would be sent best effort.
system using these could support one way tagging from server to client,
but traffic from the client to the server would be sent best effort.
–
Ensure that the TOS/QoS is properly configured on the system where
CTI OS Server resides. If changes are made to the registry, then both CTI
OS server and CTI Toolkit need to be re-started. Make sure that the
following registry has TOS value set to 0x68
CTI OS Server resides. If changes are made to the registry, then both CTI
OS server and CTI Toolkit need to be re-started. Make sure that the
following registry has TOS value set to 0x68