No-Media + IPv6 Logs

IPv6:

There shouldn't be any agents requiring IPv6, this means that the individuals settings have been incorrectly configured. The agent ID is specified, along with the date, to help resolve this.

If there are batches, that might be due to firewall configurations.

Solution:

Please review the link below to make sure that IPv6 is disabled.

• Certifying a client workstation

No-Media:

A lack of call data may be normal, for example if an agent calls a VM and hangs up there wouldn't be audio on their side. If the same agent has a large amount then it might pose a problem on their end.

It's more concerning if several agents are unable to communicate, usually caused by larger problems with the setup/agents involved.

Possible troubleshooting steps:  

• Diagnosing headset issues
• How to disable IPv6 or its components in Windows

If you experience any of these symptoms, and the trouble shooting articles linked above do not help, please contact your internal technical support team.