Usage Reports provide historical information of the voice traffic on the system as well as all necessary tools for CDR lookup and analysis.
Customers report – reveals trending information about traffic volumes, revenue and cost per customer. Data can be segmented by prefixes, geographically or account categories.
Carriers report – reveals trending information about traffic volumes, revenue and cost per provider. Data can be segmented by prefixes, geographically or account categories.
Failed Calls report – provides snapshot and trend report for failed calls with specific disconnect cause.
Imported CDRs report – provides information of imported CDRs in a system staging area which have to be manually inspected; the system allows import of the CDRs into the system.
CDR Lookup tool – allows administrators to lookup and inspect CDRs based on a set of filter criteria.
Current calls report – provides information about the current calls in the system
Hung calls report – provides information about the hung calls in the system
Call distribution report – provides information about the current call distribution in the system
The system provides granular per account management of charges, routes and usage counters.
Depending on assigned subscription plan a customers will inherit all charges defined in the plan. Depending on the type of charge service providers can manually fine tune what charges and how many charges are applied to specific accounts.
Service providers can monitor Usage Counters on per account basis and manually reset them if needed.
Each account can be associated with a route set which will serve both for calculating provider costs from usage of service and real time routing of account services.
Ingress number translation sets can be applied to Account to convert individual account dial plan to system acceptable numbers. A translation set may consists of one ore many translation rules based on called or calling number matching criteria.
The system provides flexible mechanism for service authentication and account identification based on multiple authentication attributes and combinations of them.
Supported account identification attributes:
Authentication and account identification based on source IP address; AVAVoIP looks up the IP address of the origination party and matches endpoint which belong to account
Authentication and account identification based on combination of source IP address and Tech Prefix. In cases when your partners are using a hosted solution with the same IP address AVAVoIP can use a tech prefix to uniquely identify each account
Authentication and account identification based on Tech Prefix. Although insecure Tech Prefixes are still widely used. AVAVoIP provides all necessary mechanisms for account identification based on Tech Prefix only
SIP Digest authentication. SIP endpoints can use secure username and password with SIP digest authentication function
Prepaid account authentication based on PIN number – used with prepaid IVR applications
Prepaid and postpaid authentication based on calling number (ANI) – used with IVR applications