Cisco Cisco Unified Customer Voice Portal 10.0(1)
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
A-20
Cisco Internet Service Node (ISN) Configuration and Administration Guide
OL-1251-03
Appendix A Troubleshooting
ICM
The contents of an ECC
Variable configured in Script
Editor are truncated after
passing through the
Application Server.
Variable configured in Script
Editor are truncated after
passing through the
Application Server.
For example, the
Text-To-Speech (TTS) text
that is spoken to the caller is
not the complete text that was
configured. Another example
of this behavior is where
there are media fetch failures
and the URL to the media file
is only a subset of the
expected URL.
Text-To-Speech (TTS) text
that is spoken to the caller is
not the complete text that was
configured. Another example
of this behavior is where
there are media fetch failures
and the URL to the media file
is only a subset of the
expected URL.
Possible Cause:
The cause of this problem may be that the length of the ECC Variable
value that was set in Script Editor is longer than the maximum length of
the ECC Variable configured at setup time.
value that was set in Script Editor is longer than the maximum length of
the ECC Variable configured at setup time.
Possible Solution:
The solution is to make the maximum length of the ECC Variables
longer. This is done using the ICM Configuration Manager. If you do
alter the maximum length of ECC Variables, you need to restart the
Application Server after making the change.
longer. This is done using the ICM Configuration Manager. If you do
alter the maximum length of ECC Variables, you need to restart the
Application Server after making the change.
Note: In a NAM/ICM environment, the length needs to be identical on
all NAM and ICM or the variable does not pass.
all NAM and ICM or the variable does not pass.
A new call arriving at the ISN
receives a default route label
from the ICM. You do not see
an Application Server or
Voice Browser error for this
type of ICM timeout.
receives a default route label
from the ICM. You do not see
an Application Server or
Voice Browser error for this
type of ICM timeout.
Possible Cause:
The ICM is taking a long time to handle new call requests.
Possible Solution:
Ensure there are no wait nodes in the ICM script prior to the Run VRU
Script node. For more information, see the Cisco ICM Software
Scripting and Media Routing Guide.
Script node. For more information, see the Cisco ICM Software
Scripting and Media Routing Guide.
Table A-7
ICM Troubleshooting (continued)
Symptom
Possible Cause and Solution