Using n-Command VQM to track down problems with specific calls.

[Anonymous]

I am using n-Command VQM Statistics to view traffic on one of my busiest Devices deployed.  I would like to look at specific calls with low MOS Ranges, and then track them back to a specific call and a Called or Calling Number.  Is there anything in the VQM Statistics that I can use to do this?

[Anonymous]

@rthompson - You should be able to track that call using MSP. VQM Statistics will list the calling and/or called numbers within MSP as long as the call is going through the AOS SIP proxy, SIP ALG, or B2BUA. VQM Statistics can be viewed under the VQM tab for the device that is being monitored by MSP. The VQM statistics for all monitored devices can be exported via FTP to a '.csv' file.

Let us know if you have any questions.

Thanks,

Noor

[Anonymous]

So, currently other than the time the call was placed, there is no way to use the VQM statistics gathered by n-Command to gather information and take that back to the Device and pull the call specifics?

[Anonymous]

@rthompson - I'm not sure I follow your question. The VQM statistics gathered by n-Command will contain the time, call/called number, and MOS score on a per device basis. This should all be viewable using MSP. Is there further information you are looking to gather or look up?

Thanks,

Noor

[Anonymous]

For this specific Device I am not seeing any TN information, I see "unknonwn" for both source and destination ext.  Perhaps it is the type of Configuration?

[Anonymous]

- It could be. Could you reply to this post with a screenshot of the results you are seeing as well as the configuration of the device you are monitoring? Please be sure to remove any information that may be sensitive to your company and network.

Thanks,

Noor

[Anonymous]

sorry, but I am unable to paste my screenshot... but I can tell you that both the source and destination are displaying unknown for all VQM stats.  is there anywhere in the VQM statistics that the call ID is listed?

[Anonymous]

- You will not be able to see the call ID information unless the AOS device is using its voice stack in some way. In other words, if voice traffic is just going through the AOS device's firewall but is not utilizing the AOS SIP proxy, SIP ALG, or set up for B2BUA, then you will not be able to view call ID information. You will, however, be able to get information regarding jitter, delay, lost packets, etc.,. The article below gives further details regarding voice setup in AOS.

Configuring SIP Proxy in AOS

Let us know if you have any further questions.

Thanks,

Noor

[Anonymous]

Thank you for yopur help with this.

[Anonymous]

@rthompson

I went ahead and flagged this post as “Assumed Answered.”  If any of the responses on this thread assisted you, please mark them as either Correct or Helpful answers with the applicable buttons.  This will make them visible and help other members of the community find solutions more easily.  If you still need assistance, I would be more than happy to continue working with you on this - just let me know in a reply.

Thanks,

Noor