This document defines Infinexy's accepted voice traffic profile, performance parameters for diallers, and our governance for nuisance and malicious calls, for SIP endpoints connected to the Infinexy Network. Infinexy reserves the right to limit or prevent traffic that breaches the guidelines in this policy or in the event any particular traffic presents a risk to the integrity of Infinexy's network or product platforms.
Defining accepted voice traffic profiles, performance parameters, and governance for nuisance and malicious calls.
This document defines Infinexy's accepted voice traffic profile, performance parameters for diallers, and our governance for nuisance and malicious calls for SIP endpoints connected to the Infinexy Network.
Infinexy reserves the right to limit or prevent traffic that breaches the guidelines in this policy or in the event any particular traffic presents a risk to the integrity of Infinexy's network or product platforms. This policy is in line with standard industry practice and other service providers involved in originating, transiting or terminating voice traffic may take similar action at their discretion.
In regards to nuisance and malicious calls there are two broad categories which are considered separately; however, both are as serious in their own right.
Scope: This policy applies to calls that, in some respect, transit Infinexy's network.
Infinexy's governance framework for nuisance calls, dialler standards, and CLI requirements
A Nuisance Call is one that is either unwanted or one that is "silent or abandoned" — which means that a call centre is not following the regulations on availability of live operators.
Regulatory Alignment — This Standard is a verbatim replication of the Ofcom guidelines and as such would be considered by Infinexy to be a regulatory requirement to be adhered to by any signatory to our contracts.
Infinexy's operational definition of dialler traffic to ensure network protection and service quality for all customers.
The Infinexy Operational definition of Dialler Traffic is as follows: This is traffic which typically has:
Infinexy reserve the right to limit (through call gapping or other operational intervention as we see fit in our sole discretion) which we feel may endanger the rest of the network. Any (but not limited to) of the following traffic patterns are not allowed:
Large amounts of call attempts hitting the same area or number type are not allowed. No single geographic dialling code should exceed assigned CPS unless previously agreed. Large, unexpected spikes of traffic cause network monitoring fault alarms.
Dialler traffic will be the first type to be shed during any network faults or high traffic periods to ensure network stability and service continuity.
ASRs below 40% will be deemed as suspect (e.g., Data cleansing activities). Immediate action will be taken to limit such traffic as it may indicate a breach of regulatory standards.
Each endpoint has a defined calls per second limit (typically 10 CPS). Higher CPS can be negotiated. Sending too many calls will get a 503 response and uses unnecessary SBC processor resource.
Infinexy has a wide range of network performance alerts. Sustained low ASR sent to one Mobile Operator type will produce an alarm in the NOC. False alarms can hide other network problems and divert resources.
Infinexy NOC monitors all traffic patterns 24/7. Remedial action will be taken if any dialler pattern causes alarms or red statuses on the NOC monitors.
Infinexy's operational standards for dialler traffic management and CLI presentation to ensure network integrity and regulatory compliance.
It is quite common for customer endpoints to be provisioned as normal SIP and then used for this traffic. Infinexy's Voice Quality of Service department runs daily reports which will quickly identify traffic of this nature.
The customer will be asked to stop sending this traffic but Infinexy reserve the right to reduce their capacity or turn them off to protect the integrity of the network.
Infinexy offers customers flexibility in what CLI they present. The Customer Agreement that has to be signed prior to implementation contains a condensation of the CLI Presentation regulations.
Infinexy's operation team will perform periodic audits of presentation CLIs across the network and take action to enforce these rules as required.
Additionally, some operators within the European Economic Area ("EEA") surcharge calls made from outside the EEA based on presentation and/or network CLI.
The Customer Agreement contains a condensation of the CLI Presentation regulations. The two main points are:
Infinexy's operation team performs periodic audits of presentation CLIs across the network and takes action to enforce these rules as required.
Infinexy's operational standards for outbound traffic management and protection against malicious call activity.
This follows the standards outlined in the section under Dialler and CLI Standards.
Traffic which typically has an ALOC of under 30 seconds with an ASR less than 60% is not generally acceptable.
These, like silent and abandoned calls, are also Communications Act 2003 offence and carry criminal liability.
Spam over Internet Telephony — the telephony equivalent of a Distributed Denial of Service (DDOS) attack on a website.
Calls intended to cause annoyance or offence, which may also contain content that falls into the SPIT category.
Obviously, a SPIT attack can contain content that falls into the latter category too. Both need handling in a slightly different way.
Infinexy's SIP peering framework enables seamless interconnection between enterprise and service provider networks through automated capability discovery and configuration.
Automated capability discovery eliminates manual configuration and reduces the risk of errors.
JSON-encoded capability sets provide easy parsing by automation tools for quick deployment.
Security parameters included in the capability set ensure trusted and encrypted peering relationships.
The capability set communicated by the service provider includes characteristics specific to signalling, media, transport, and security.
The enterprise edge device (typically a Session Border Controller) generates an HTTPS GET request to the service provider's Capability Server. The server responds with a JSON-encoded capability set for automated configuration.
Cloud-based phone system that delivers enterprise-grade voice, video, and collaboration without the hardware overhead.
Hosted PBX runs entirely in the cloud, eliminating the need for expensive on-premise hardware and reducing IT maintenance overhead.
Easily scale up or down as your business grows. Add or remove users, extensions, and features with just a few clicks.
Auto-attendants, call routing, voicemail-to-email, call recording, conferencing, and integration with business applications.
Scalable, reliable, and secure SIP interconnect solutions for carriers, enterprises, and service providers worldwide.
Carrier-grade SIP interconnect with 99.99% uptime SLA, handling millions of minutes daily with ultra-low latency.
Direct IP peering with 500+ carriers worldwide for cost-effective, high-quality voice routing and termination.
Cloud-based Hosted PBX solutions with advanced call features, auto-attendant, call recording, and seamless integration.
Such an attack could compromise Infinexy's network integrity, therefore it is expected that the appropriate operational teams will take whatever steps necessary to guarantee the integrity of the network as they would in a failure state; once mitigated, it should be treated as any other attempt to hack or misuse our network with appropriate investigation and involvement of law enforcement.
Where reports of these are made, they should be directed to the Network Operations Centre.