Cisco Cisco Agent Desktop 8.0 Références techniques
Cisco IP Phone Agent Problems
November 2006
243
■
If the CallManager authentication URL (one with
authenticate.asp) is used, make sure that a telecaster user with a
password of telecaster exists in CallManager and that the phone
is associated with this user.
authenticate.asp) is used, make sure that a telecaster user with a
password of telecaster exists in CallManager and that the phone
is associated with this user.
■
The agent’s phone was not rebooted after changes were made in
CallManager. If a soft reboot does not work, try a hard reboot
(unplug the power cord and plug it back in).
CallManager. If a soft reboot does not work, try a hard reboot
(unplug the power cord and plug it back in).
■
Verify that the agent is logged in to the phone.
■
Verify that if the agent logs into CAD using the same phone and
user ID, enterprise data does pop correctly.
user ID, enterprise data does pop correctly.
■
Verify that the enterprise data does not contain the following
symbols:
symbols:
left and right angle brackets (< >)
ampersand (&)
apostrophe (‘)
double quote (")
space ( )
ampersand (&)
apostrophe (‘)
double quote (")
space ( )
Problem
The agent sees nonsense characters in reason code or wrapup data.
Solution
The reason codes configured in ICM or wrapup data configured in
Desktop Administrator contain characters not supported by the phone.
Examples are multibyte Chinese or Kanji characters. Make sure that no
unsupported characters are used when configuring reason codes and
wrapup data.ge
Desktop Administrator contain characters not supported by the phone.
Examples are multibyte Chinese or Kanji characters. Make sure that no
unsupported characters are used when configuring reason codes and
wrapup data.ge
Problem
A supervisor cannot record or monitor an IP Phone Agent agent.
Solution
The phone is not set up for SPAN port monitoring.