
Audiotrix C2, C4 & C8
Choose 2, 4 or 8 FXS ports for analog phones and small sites.
- Selection criterion
- Exact firmware and a real-world T.38 test when fax is required.
Evaluate T.38, G.711 pass-through, line conditions and service-provider behavior for fax and modem continuity.
A starting point for your project. Review the model data sheet before ordering.

Choose 2, 4 or 8 FXS ports for analog phones and small sites.

Connect two analog endpoints to an IP voice service.

A compact gateway for a small analog or mixed-interface installation.

Bring multiple analog extensions onto an IP network.
Every device and service is part of a live operating workflow. The diagram makes the translation point, trust boundary and acceptance target visible.
Local phones, a local IP PBX, Mediatrix gateways and Sentinel can exchange SIP calls entirely inside the organization. The voice path can remain on a private LAN, VLAN, campus network or isolated operational network.
An external connection is used only when calls must reach public numbers, remote sites or hosted services. If the required call path is entirely local, the system can stay on the private network.
Transmits documents using tones that must survive the complete IP path.
Carries data over audio and is highly sensitive to packet loss, jitter and codec changes.
Confirms basic dialing but does not prove fax or modem data integrity.
Presents the correct analog or digital interface, then converts validated traffic to SIP.
Controls extensions and internal routing on the private network. It may remain fully on-premises.
Terminates external calls and determines supported fax or modem behavior.
Receives calls, applies the dial plan and connects users or workflows.
Use-case model — field validation remains mandatory for endpoints, carriers and safety-related workflows.
A fax & modem migration design should answer each question before rollout, not after the first incident.
Safety, emergency, alarm and regulated services require approval from the responsible authority and service provider for the actual deployment.| Validation layer | Question to answer | Evidence to collect | Owner |
|---|---|---|---|
| Endpoint | Does the real device behave correctly over the new path? | Dialing, media and feature test | Customer / integrator |
| Network | Are latency, jitter, NAT and QoS controlled? | Capture and quality baseline | Network team |
| Service | Does the carrier support the required call or data behavior? | Carrier-accepted test result | Carrier / service owner |
| Failure | What happens during power, WAN or platform loss? | Failover and recovery test | Operations |
| Lifecycle | Who owns updates, certificates, backups and escalation? | Approved runbook and entitlement | Service owner |
Share the product, deployment and target outcome. M5 will identify the right technical and commercial path.