ManageEngine releases new Distributed Edition of VQManager-version 7.0 which is highly scalable for mid and large Enterprises and Service Providers with geographically distributed locations.

VQManager Distributed Edition is built on a Central – Probe architecture. Central Server provides a centralized console UI to view the data collected periodically from all the sites(probe server installed at individual sites). With this latest release, you can monitor more than ~1000 concurrent calls spread across multiple VLANs in a single location as well as your geographically distributed VoIP network by installing multiple probes.

The Central server UI makes it easy to identify and troubleshoot VoIP problems and to provide more insight into your VoIP network. Apart from troubleshooting, VoIP Administrators can also get input on maintaining their VoIP user base and utilize the bandwidth accordingly.

Setting up and Configuring VQManager Distributed Edition:

Central server should be installed and started before starting the Probe server. Once the Central is up and running, If the Probe server is started, it should be registered to the corresponding Central server. The registration process will fail if Central server is not started / not reachable at first place. In such situation, please shutdown the Probe server and start the Central first. If the Central server is running and still registration fails, make sure that Central server is reachable from the Probe server installed machine or check if the Central server details provided to the Probe server are correct. All the network VoIP traffic needs to be port-mirrored to the Probe server to monitor the VoIP calls in that Site.

Once the Probe server is registered to Central server, you have to add sites for each Probe server and associate them. A Site is a logical representation of a group of IP Phones monitored by a single Probe Server. Each Site should be associated with a single Probe Server which monitors that Site and provides data to the Central Server periodically. To see the list of all the registered Probe Servers with the Central Server, go to Admin tab and click the Probe under System Settings.

When the Probe servers are associated with their sites, Center Server dashboard will provide the details of the VoIP calls happening in the associated sites. Here is some introduction to VQManager Central Dashboard.

Call Volume

The Call Volume graph provides us the percentage of distribution of the Successful, Error, Unanswered and Unmonitored calls across all the Sites in a graphical view (left side of the page) and the actual counts of these calls in the tabular view (right side of the page). Clicking on a single site in the bar graph provides an hourly based call volume trend for that site. On further drill down, it will lead to the corresponding Probe details page.Refer the screen-shot shown below.

Voice Quality

The Voice Quality graph provides the percentage distribution of the Successful calls as Good, Tolerable, Poor calls and No MOS based on the MOS value of the site. This can also be seen in graphical and tabular format. The tabular format can be toggled to graphical format (Line graph) by clicking on the graph icons present at the top right corner of the Voice Quality graph. A sample graph is shown below

Alarms

The tabular view provides the count of Critical, Major and Warning alarms generated in the corresponding sites. For configuring the alarm profiles, login into the Probe Server.

Concurrent Calls

The graph depicts the hourly trend of concurrent calls for each site. The graph can also be plotted based on Minimum, Average and Maximum concurrent c
alls for each site by selecting the corresponding button present above the graph. You can also see the concurrent calls for each site individually by clicking on the icons present before the legend under the graph. Click on the corresponding sites to show/hide the graph for an individual site.

Traffic Monitor

The Traffic Monitor graph provides a detailed information on the type of traffic flowing in each site. You can see the amount of bandwidth consumed by SIP/Skinny/H.323 traffic, and Voice traffic in your VoIP network. Clicking on the percentage distribution graph for any site provides the graphical representation of the bandwidth utilized by the signaling traffic and voice traffic. You can select either tabular format and graphical view by clicking on the graph icons present on the top right corner of the Traffic Monitor graph.

]]>https://blogs.manageengine.com/_eol/vqmanager/2011/05/30/manageengine-vqmanager-distributed-edition-ga-released.html/feed0VoIP industry leaning towards SIPhttps://blogs.manageengine.com/_eol/vqmanager/2010/06/20/voip-industry-leaning-towards-sip.html
https://blogs.manageengine.com/_eol/vqmanager/2010/06/20/voip-industry-leaning-towards-sip.html#commentsMon, 21 Jun 2010 06:06:41 +0000https://blogs.manageengine.com/vqmanager/2010/06/20/voip-industry-leaning-towards-sipThe latest VoIP market trends show a strong inclination towards SIP(Session Initiation Protocol). It is definitely encouraging to see the VoIP industry converge toward a common standardto get rid of all the interoperability problems and pass on the true …]]>The latest VoIP market trends show a strong inclination towards SIP(Session Initiation Protocol). It is definitely encouraging to see the VoIP industry converge toward a common standardto get rid of all the interoperability problems and pass on the true benefits of VoIP to the consumer. And no surprises seeing Microsoft, Cisco and Skype who started out with their own proprietary standards now adopting SIP.

Here at VQManager, we started our VoIP monitoring solution by supporting SIP, due to it’s simplicity, capabilities & in-depth design details. Along the way, we ensured that the major VoIP protocols – SIP, Cisco SCCP and H.323, were also covered. If you dig a little into VQManager you’ll realize that a number of features are available on the SIP side of things and not present for the other protocols e.g. SIP end-point registration tracking, SIP error code based alarms, reports etc. We come across a lot of customers who migrate to SIP phase-by-phase and we having support for the major protocols has helped such customers.

I’m picking a few quotes I found online mentioning the growing importance of SIP as a common standard for VoIP.

Avaya is the leading player in VoIP, recently Avaya acquired Nortel. In the latest update Avaya is planning to use Session Initiation Protocol (SIP) for all its VoIP deployment, also planning to migrate the existing customer base of both Avaya & Nortel smoothly.

Now-a-days, the SIP based Open source VoIP server Asterisk is gaining popularity in SMB’s and VoIP Service providers.

Skype and ShoreTel, Inc., (NASDAQ: SHOR), the leading provider of brilliantly simple IP phone systems with fully integrated Unified Communications (UC), announced interoperability between ShoreTel’s UC system and the beta version of Skype for SIP. ShoreTel is the world’s first UC vendor to achieve interoperability with Skype for SIP.

Skype is taking business internet communications to a whole new level withSkype for SIP Open Beta.

Google reports that they are working on adding new features such as supporting SIP in a future release, which would broaden the user base for the program.

Steven J. Johnson is President of Ingate Systems

We are seeing a strong adoption of SIP in enterprises of all sizesand this adoption has been accelerated by SIP trunking as a service from multiple ITSPs. From our experience with customers, we’ve found that cost benefits of SIP trunking seem to be most pronounced in organizations of up to 500 people.

Why the wide acceptance of SIP:

Since SIP is a text-based implementa
tion, development and debugging is easier compared to the other protocols (Syntactically, SIP is very similar to HTTP)

SIP’s simplicity doesn’t compromise on power/capabilities

Supports a wide range of media types

It is a peer to peer protocol that requires no centralized server to work. The user agents themselves do the communication

SIP can run on UDP/TCP

SIP allows changing features of a session while it is in progress (e.g. changing addresses or ports, inviting more participants, adding or deleting media streams, etc.)

SIP has been standardized and governed primarily by the IETF, while other protocols, such as H.323, have traditionally been associated with the International Telecommunication Union (ITU)

SIP was accepted as a 3GPP signaling protocol and permanent element of the IP Multimedia Subsystem (IMS) architecture for IP-based streaming multimedia services in cellular systems

The protocol can be used for creating, modifying and terminating two-party (unicast) or multiparty (multicast) sessions consisting of one or several media streams

Google Talk, which extends XMPP to support voice, plans to integrate SIP.

Moving forward, VQManager will look at reporting on the entire SIP suite based on market need and priority. While the industry undergoes the slow transformation and convergence towards SIP, we at VQManager will also focus on ensuring businesses and consumers enjoy a smooth transition.

Today we’ll see what’s present in the all new ‘Calls Report‘ section, found under VQManager’s “call” tab.

For the sake of simplicity, VQManager broadly categorizes calls as either Successful or Unsuccessful calls. Further categorization is done based

…]]>

Today we’ll see what’s present in the all new ‘Calls Report‘ section, found under VQManager’s “call” tab.

For the sake of simplicity, VQManager broadly categorizes calls as either Successful or Unsuccessful calls. Further categorization is done based on the call tear down status.

Unsuccessful Calls split

Analysis has to be started once a call fails, ie an Unsuccessful call. It is almost impossible to debug each and every unsuccessful call that happens in the network so VQManager’s ‘Unsuccessful Calls split’ pie chart lists the ‘Top 10′ reasons for unsuccessful calls. In a call center or large enterprise the ‘Busy Here’ reason will be of greater concern unlike the small enterprise where other failure categorizes such as ‘Server error’ or ‘Not found’ will be of high priority. Real troubleshooting of failed/error/unanswered calls begins here. Picture pasted below shows the hybrid environment running SIP, SCCP and H.323 protocol and the pie chart is consolidated across protocols to give greater visibility into call failures.

Successful Calls split based on quality

Once a call is categorized as successful, further concern is whether that call has acceptable quality? How was the user experience? A successful call will have call initiation signaling packets, media traffic (RTP) and tear down signaling. VQManager segregates a successful call with media (RTP) traffic into Good, Tolerable or Poor based on the MOS (Mean Opinion Score) of a call. MOS is a consolidated QoS metric, which is derived from a ITU-T formula, which takes into consideration other quality metrics such as delay, jitter, loss, codec etc.,. The new ‘Quality Split’ pie chart under ‘Calls report’ of VQManager 6.3 helps in identifying call quality – whether they are Good, Tolerable or Poor. QoS distribution percentage and the call numbers are provided on mouse-over. Further troubleshooting of Poor, Tolerable quality calls begins here.

Explore the ‘Calls Report’ along with call quality trend graphs for actionable insights into VoIP call and quality failures.

https://blogs.manageengine.com/_eol/vqmanager/2010/05/31/know-why-voip-calls-failed-or-had-poor-quality.html/feed1What is being cooked @VQManager – Part Ihttps://blogs.manageengine.com/_eol/vqmanager/2010/01/16/what-is-being-cooked-vqmanager-part-i.html
https://blogs.manageengine.com/_eol/vqmanager/2010/01/16/what-is-being-cooked-vqmanager-part-i.html#commentsSat, 16 Jan 2010 10:01:45 +0000https://blogs.manageengine.com/vqmanager/2010/01/16/what-is-being-cooked-vqmanager-part-iWhile monitoring your VoIP set-up, two high priority areas to be tracked areQoS(Quality of Service)and Call drops. In our upcoming release, we have added two new graphs which help in quicker troubleshooting ofpoor call quality and call …]]>While monitoring your VoIP set-up, two high priority areas to be tracked areQoS(Quality of Service)and Call drops. In our upcoming release, we have added two new graphs which help in quicker troubleshooting ofpoor call quality and call drops.

1. The ‘Call Quality Trend’ graph

This new graph is a line chart plotted every hour, showing the successful calls categorized based on quality distribution [Good, Tolerable and Poor]. One can click on any of the data points and drill-down to the call list showing the calls that contributed to the bad quality and further debug by accessing individual Call Details pages. Based on the history data range chosen in the calendar, one gains insight on the call quality deterioration on an hourly/daily/weekly/monthly basis. As always, you can easily compare various weeks’ peaks and lows to analyze traffic patterns and foretell network capacity needed.

NOTE: In VQManager, the quality of a call is determined based on the MOS score of a call. The MOS score takes into account all other quality metrics such as delay, jitter, loss, codec etc., in a call. The MOS thresholds are user configurable. Here’s the default VQManager scale of call quality using MOS values.

Good MOS > 3.6Tolerable MOS > 3.1 && MOS < 3.6Poor MOS < 3.1

2. The ‘Call By Status’ pie chart

‘Call By Status’ is a pie chart having percentage of Successful calls, Unanswered calls, Error calls & Unmonitored calls. With this, one can easily identify which type of calls are largely prevalent in the VoIP network. In call centers, one would not want a high number of unanswered calls. In the case of an enterprise or VoIP service provider,it is Error calls that will be a source of headache. The mouse-over on the pie will show you the number of calls contributing to the particular call status. By clicking on the link one gets all the respective calls in a list view, from where one can either drill down to the Call Details page or search for the Initiator and Participant to drill down and troubleshoot.

Wait for a few more weeks and you can use the above graphs live in your environment.

It’s again time for good news from our side. Get ready to shed the old and embrace the new. We happily announce the release of VQManager 6.1.1,

…]]>

Hey all,

Hope things are fine and in the best of spirits.

It’s again time for good news from our side. Get ready to shed the old and embrace the new. We happily announce the release of VQManager 6.1.1, a milestone release quickly following VQManager 6.1. The 6.1.1 version comes with feature enhancements, a cool new User Interface and also some fixes. Thanks to you all for the valuable feedback and the suggestions.

You can get hold of VQManager 6.1.1 from here . And here are the Release Notes.

Will ring you soon with another update.

So long…

]]>https://blogs.manageengine.com/_eol/vqmanager/2008/09/09/vqmanager-611-out.html/feed0Europe – ManageEngine’s next door this September!https://blogs.manageengine.com/_eol/vqmanager/2008/08/29/europe-manageengines-next-door-this-september.html
https://blogs.manageengine.com/_eol/vqmanager/2008/08/29/europe-manageengines-next-door-this-september.html#commentsFri, 29 Aug 2008 17:08:53 +0000https://blogs.manageengine.com/vqmanager/2008/08/29/europe-manageengines-next-door-this-septemberPost the H.323 release, VQManager continues to go places and this time we are accompanying a big ManageEngine team alongside dedicated ManageEngine European partners. Mark Miller’s team at VoIPPlannet and TMCnet gave us just the right beginning to our “shout-out-loud” …]]>Post the H.323 release, VQManager continues to go places and this time we are accompanying a big ManageEngine team alongside dedicated ManageEngine European partners. Mark Miller’s team at VoIPPlannet and TMCnet gave us just the right beginning to our “shout-out-loud” plans on letting the VoIP world know of a truly simplified, complete, cost-effective VoIP monitoring solution ;). Now that VQManager supports most VoIP protocols in the market, we’re quickly adding features and improving on performance – expect the next product release very soon!

So Europe, we’re coming over to meet u in your neighbourhood. We’re arranging a Roadshow from Denmark to Sweden, France, Italy, Germany, Portugal, Poland and the UK on September 8th to October 3rd.

This screen appears when a user logs into VQManager for the first time. All first-time users can now breeze through the steps to set up VQManager to start reporting

…]]>

We’ve built you a configuration wizard that’s more than just pretty.

This screen appears when a user logs into VQManager for the first time. All first-time users can now breeze through the steps to set up VQManager to start reporting on VoIP traffic. Access the help card found on the top right corner of the wizard for more details on each screen.

So it’s not just the product log-in screen that’s got prettier in the latest VQManager 6.1

As we had promised, here we are with the inbuilt option to get a packet capture of your VoIP traffic for troubleshooting.

If you felt even one is more, no problemo.. Enough of the sniffer.exe…command, the option blah blah

…]]>

As we had promised, here we are with the inbuilt option to get a packet capture of your VoIP traffic for troubleshooting.

If you felt even one is more, no problemo.. Enough of the sniffer.exe…command, the option blah blah for the capture.

Here’s how simple it is!!

As you click on the ‘Create the latest support information file‘ from the ‘Support’ tab, you get this form to fill up the details. Just check the ‘Add packet capture file to support log information’ checkbox and enter the details.

Click on ‘Send’. In a few moments, the job’s done. The rest we don’t need to say, do we??

The team includes Sujith Regan from VQManager. Go ahead and get to know in and out of VQManager with this guy! Technical feasibilities, product direction, VQManager – the beginnings, deployment advise, limitations, tips.. Regan’s the man.