VQManager正式停產. 詳請參閱ZOHO官網End Of Life說明

VoIP质量监控软件



版本 6.2 正式发布!
性能全面提升、许可新定义、
报表计划... 查看详情!
VQManager是一款VoIP质量监控软件。
 
成功案例
" 我觉得VQManager实在无可挑剔,在业务环境中发挥了巨大的作用。"
-Julian Fletcher, ConvergenceGroup.
 
Deployment Scenarios
Data Input Options

VQManager provides monitoring, alerting, problem diagnosing and reporting of important VoIP quality information and call statistics. How does the software get the vital data from the VoIP network to perform all these functions?

VQManager collects call data in three ways:

1. The inbuilt sniffer reads and processes the SIP, H.323, Skinny, RTP and RTCP packets in the VoIP network to give the call information and QoS statistics. This method of data capture and processing allows for real-time, packet-level troubleshooting.

2. VQManager imports CDRs/CMRs log files from the CallManagers and Call servers. Depending on the information contained in these log files, VQManager will display relevant call statistics. At present, the following CDR formats are supported: Cisco CallManager(4.x and 5.x), Swyx 6.0, Vovida VOCAL, Tekelec 5.6, Shoretel 6.1, PortaOne and Asterisk CDRs. You can request support for a CDR format not present in the above list by sending a sample of the CDR file to support[at]vqmanager[dot]com.

3. VQManager can be set as syslog server to receive CDR/CMR log files periodically and display call statistics from the syslog messages. The pattern of CDR/CMR log for syslog processing is same as the CDR/CMR import option.


For configuring the data input options in VQManager refer to Obtaining Call Information in the Help document.


Deployment Scenarios

The deployment of VQManager depends on the network topology and devices used in your VoIP network set-up. For real-time monitoring of VoIP traffic using the VQManager in-built sniffer, the prime requirement is to have all VoIP traffic mirrored/directed to the NIC (Network Interface Card) on which the sniffer listens on.

In a network set-up with a managed switch , this can be achieved by enabling port-mirroring in the managed switch present in the network. Port-mirroring involves forwarding incoming and outgoing packets from all other ports in the centralized switch (connecting to VoIP devices) to one port that is connected to the NIC that is set as the sniffer interface in VQManager. For details on enabling port-mirroring in various switches such as 3Com, Cisco Systems, Linksys, NETGEAR, Avaya, Nortel etc : Enabling port-mirroring in different switches .

In a Shared Ethernet or a Hub network , packets are transmitted in broadcast mode. Here packets from one port are transmitted to all other ports, regardless of the destination intended. In this set-up, VQManager's sniffer would get a copy of all the packets in the network and would show statistics and quality information for all the calls in the network. The only setting required is to have "Promiscous Mode" sniffing to be enabled in the VQManager sniffer configuration.

In an Asterisk PBX environment , the calls are processed centrally at the Asterisk server. When a call is made from endpoint A to endpoint B, the call goes through the Asterisk server and is technically branched into two different calls with endpoint A and B talking to Asterisk server independently. In this case, by mirroring the Asterisk server's port alone to the VQManager port, you can get all VoIP call statistics as all calls (including the voice traffic) traverse the Asterisk server.

In a Hosted PBX environment, all VoIP traffic flows to and comes from an external PBX server. Here, you would need to mirror the traffic from gateway/router's port to the VQManager port.

In a multi-site VoIP network set-up there would be many sites spread across different geographies and all traffic within and across sites need to be monitored. If there is present a common gateway/call server/node that receives all traffic from the various sites, then VQManager can be installed to monitor traffic flowing through this central node so as to show statistics of all the VoIP calls. If no such central node exists, then there needs to be an installation of VQManager in each site for monitoring traffic associated with each site. Each of these installations can then be accessed from a central location by virtue of VQManager's Web Interface.

VoIP Monitoring