Showing results for 
Search instead for 
Did you mean: 
Walkthrough Wednesdays

User receives the "Could not start the Cisco Desktop VoIP Monitor Server service on Local Computer" error message in a dual NIC environment or unable to do voice monitoring when using dual NIC cards with the VoIP monitor server


Core Issue

In a VoIP monitor server with a dual Network Interface Card (NIC) configuration, the VoIP monitor server does not start. It can also fail with the Could not start the Cisco Desktop VoIP Monitor Server service on Local Computer error message and sometimes reports The monitor server was unable to open the specific device.


Disable the second NIC to resolve this issue. If the problem goes away, then the issue is with the dual NIC configuration.

Verify under the HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\NetworkCards registry key that the service name of the spanning NIC is consistent with the value under the HKEY_LOCAL_MACHINE\Software\Spanlink\FastCall VoIP MonitorServer\Setup\MonitorDevice registry key.

If this is not consistent, change it to the correct value as this example shows:

\Device\Splkpc_{Service Name of the Spanning NIC}

Note: Restart the system after the necessary changes in the registry key are made.

Special attention needs to be paid to the configuration of dual NICs on a VoIP monitor server.

Refer to the Using Multiple NIC Cards with the VoIP Monitor Server section of the VoIP Monitor Server 4.2 Best Practices Configuration Guide to configure a dual NIC configuration.

Refer to the Cisco Agent Desktop Problems section of Diagnosing and Correcting Cisco CRA Problems for more information.