Known Issues

The following are the Known Issues in VQManager:

• At present, VQManager supports the SIP, H.323 and Skinny signaling protocols only

• As of now, it is not possible to sniff VoIP packets on multiple interfaces

• Monitoring of conference calls are not supported

• The default Admin and Guest user accounts created by VQManager MUST be present for proper functioning of VQManager. These two accounts are not to be deleted. Other accounts created by the users can be deleted.

• At present, VQManager does not have provisions to verify the authenticity of RTCP information sent by the endpoints

• Currently, VQManager supports the CDRs generated by Cisco Call Tracker, Cisco Unified Communications Manager 6.1, Cisco Call Manager 4.0 & 5.0, Shoretel 6.1, Vovida Vocal, Asterisk, Avaya S8700, PortaOne, Swyx  6.0 and Tekelec 5.6

• Incomplete call Alarm Profile does not work for the CDR imported calls

• SIP messages over TCP are not supported

• In alarm detail view the number of call represented by the Total Call link may occasionally differ from the total number of calls displayed in Call Summary UI

• Browsing for a CDR file (for importing CDR through FTP) throws "Unparseable date" exception in Linux machines with different locale than that of the server machine

• In "Mail Settings" (Admin tab), after testing the mail server setup (using the test option), if you immediately carryout certain changes in "Email Notification Settings" and try to "Save Settings", the changes do not get saved. However, when you carryout changes in "Email Notification Settings" separately and click "Save Settings", the changes will be saved

• When more columns are added to the calls list, the reports generated in PDF report would look cramped. A maximum of 10 columns can be displayed without looking cramped in the PDF reports.

• While choosing the custom time period, like, from 2011-04-20 05:00 to 2011-04-21 23:59 or from 2011-04-20 05:00 to 2011-04-21 21:59) in Call Lists, the e-mail option will not work. The page shows 'No data available'.

• After reconfiguring the QoS thresholds in Configure link, the changes will take effect in the latest data to be collected. The history data will not get altered inline with new thresholds. This may lead to data mismatch on the day of reconfiguring

• Importing CDRs containing history calls data will not get reported in the graphs present in predefined reports, custom reports under 'Reports' tab, and Unsuccessful calls split under CallsReport page.

Copyright © 2011, ZOHO Corp. All Rights Reserved.