Troubleshooting Tip: FortiFone desktop softclient active call widget not refreshing automatically
| Description | This article describe a situation where an active call widget on the FortiFone desktop softclient does not automatically refresh call status. Manually refreshing solved the issue. |
| Scope | FortiVoice v7.0.4 GA, FortiFone desktop softclient 7.0.0.85. |
| Solution | Steps to reproduce:
For example:
At 10:59, a call enters the queue. It has been picked up by agent 3160 (Alex Barreto).
A manual refresh is required at 11:00AM to reflect the correct state.
At 11:01AM after the transfer, a manual refresh is required to reflect the transfer to ext-3159.
The root cause is the race condition. When an agent picks up a queue call, the FVCallStatusUpdateCalleeNumName, and AgentConnect events will be sent by the AMI.
The prior event is to update callee_name and callee_num, and the later event is to retrieve data from rt_call_status and send the message to the front side. Sometimes however, the data query happens before the update operation, so the msg.to_name, msg.to_num retrieves the outdated data.
Upgrade the FortiVoice to v7.0.6 (see Resolved issues) or 7.2.0 to fix the issue. |




