CommView Instructions
COMMVIEW README
Thank you for purchasing the CommView software package. Our Development and
Support teams are committed to ensure you obtain the best possible performance
and value from your investment.
Key information is provided at the following links about recent product changes and
enhancements. Please read through this document in its entirety before you begin using your installed or upgraded CommView.
System Requirements
What You Can Expect
Site Prep / Installation
Site Info and Extension List
Online Tutorial
@Comm's CommView Options:
CommView Single User - All reporting is performed on the host PC/Server as a Windows application.
CommView Multi User * - Browser-based reporting module (multiple users) supplements the Windows application to securely extend reporting beyond the admin desktop.
CommView Web – An @Comm hosted service that provides secure reporting access via browser without the local hardware and administrative requirements.
* @Comm recommends end-users to set up a SSL if they need to meet secure connection requirements.
For assistance with system operation, administration or troubleshooting, please contact @Comm support.
Request Support
support@atcomm.com
(603) 628-3000
Server Requirements
Operating System:
Configuration Requirements:
|
Hardware Requirements:
|
Options & Considerations
-
CommView Multi User bundle includes WebReporter - Requires .NET Framework 4.0 and IIS 7
-
When choosing a virtual environment, IP-based polling must be implemented and it is recommended to assign a second processor at a minimum.
-
For configurations of >5,000 stations, a 2-CPU configuration is recommended to improve performance.
-
The most significant improvements in system performance can be gained by increasing the amount of RAM in the workstation/server running CommView.
-
COM Port(s) (Required if serial polling options is being used and/or serial PMS posting for hospitality)
-
For report users and administrators accessing via our Browser interface - Any Windows PC running a current browser from Microsoft, Mozilla or Google. @Comm aims to maintain compatibility with the latest browser versions of Internet Explorer, Firefox and Chrome
* Not for new deployments. Installing/operating on OS past EOL is at your own risk due to absence of security patches
- @Comm sends email notification upon processing a new system order to customer & /or partner containing assigned ticket number and general pre-installation information.
- @Comm Support contacts customer &/or partner to review reporting objectives, discuss environmental considerations and summarize responsibilities of each party.
- A target date is set for software installation & database configuration with a review of how customer directory data will be provided (extension numbers with names, departments, etc.), desired call pricing, restrictions for self-service reporting, etc.
- Customer prepares Server/Workstation including configuring user login with administrator rights, disabling User Account Control and confirming internet access.
- Customer's PBX vendor prepares and provides SMDR/CDR access to Server/Workstation. Formats and protocols are PBX specific. When an external hardware buffer is part of the configuration, the partner or customer will make the physical connections.
- Customer contacts @Comm support on agreed upon installation date.
- Customer establishes remote access session from the Server/Workstation connecting @Comm Support to target.
- @Comm commences CommView software installation & configuration. Initial focus is on SMDR/CDR acquisition and interface refinement leading to proper processing.
- @Comm imports customer provided extension list from csv file, if in proper format.
- @Comm installs and configures WebReporter for customers who have purchased Multi-User (browser-based) reporting.
- @Comm and Customer set date for customer administrator and report user training.
- @Comm provides customer training on arranged date/time via remote access. Training takes approximately 2 hours based on number of sites and customer configuration requirements.
As an option, customers or partners can begin the data gathering process by downloading and completing a general template in Microsoft Excel.
For applications that have multiple data sources, or have a single data source that is parsed into different files based on geography or function, each site should be identified and have a site license.
Report sorting and filtering as well as user restrictions to subsets of call data is configured by using the organizational structure associated to an extension end point. This template provides suggestions on possible uses of the available levels. Contact @Comm Support for assistance with any questions.
If helpful, you can view the screen shots below. The images are "Site Info" and "Extension List" tabs with examples.
Partner Rewards
Expand company offerings and help your customers in the process.
"With @Comm's Partner
Rewards Program you
now can make more
money"
Addressing PBX/IP-PBX Manufactured Product Challenges Today
This white paper provides analysis, real-world insight and offers a solution to the current telephony and technology landscape as it pertains to the end customer. Download Whitepaper.
(PDF, 1.8 MB)