ClickCease

How to Configure an AudioCodes Mediant for a Viirtue SIP Trunk with PRI Handoff

Configure audiocodes blog title card with Viirtue branding.
Configuring an AudioCodes Mediant for a Viirtue SIP trunk with PRI handoff bridges modern VoIP connectivity with legacy PBX systems. This step-by-step guide walks you through setup essentials — from proxy sets and IP profiles to PRI configuration, E.164 normalization, TLS, and routing rules. Whether you’re an MSP deploying for a new customer or a telecom engineer standardizing edge devices, these steps ensure secure, reliable SIP-to-PRI integration that aligns with Viirtue’s best practices and current AudioCodes firmware.

Configuring an AudioCodes Mediant for a Viirtue SIP trunk with PRI handoff bridges modern VoIP connectivity with legacy PBX systems.

This step-by-step guide walks you through setup essentials — from proxy sets and IP profiles to PRI configuration, E.164 normalization, TLS, and routing rules.

Whether you’re an MSP deploying for a new customer or a telecom engineer standardizing edge devices, these steps ensure secure, reliable SIP-to-PRI integration that aligns with Viirtue’s best practices and current AudioCodes firmware.

Prerequisites to Configure an Audiocodes Mediant

  • Viirtue trunk credentials and SIP domain or SBC FQDN

  • List of DIDs, emergency calling plan, and caller ID policy

  • Mediant with PRI module and current GA firmware, for example, v7.2 or later per current manuals (AudioCodes)

  • Static public IP or NAT traversal plan, NTP reachable, and syslog target

High-level topology to Configure an Audiocodes Mediant

Internet or private peering to Mediant (SIP TLS recommended), Mediant to PBX via T1 PRI NI2. AudioCodes documentation covers PRI and trunk group setup, plus SIP proxy and routing pages referenced below. (AudioCodes)

Step-by-step Process to Configure an Audiocodes Mediant

  1. Basic system and network

    1. Set management IP, default route, DNS, and NTP. Save and reboot if required.

    2. Confirm date and time are correct to avoid TLS issues.

  2. Create the Proxy Set and SIP definitions

    1. VoIP > SIP Definitions > Proxy and Registration.

    2. Add Proxy Set with Viirtue SBC FQDN and desired transport. Enable TLS if your trunk is TLS based. Set keepalives and DNS resolve method. AudioCodes quick guides show these exact screens. AudioCodes

  3. SIP Interface and IP Profile

    1. Define the SIP Interface that listens on the Mediant toward the provider side.

    2. Create an IP Profile that sets DTMF to RFC 2833, allows 100rel if needed, sets privacy, and enables SRTP if your contract requires it. See user manual 7.2 and later for parameter locations. (AudioCodes)

  4. IP Group for Viirtue

    1. VoIP > Control Network > IP Groups, create an IP Group that points to your Proxy Set and uses the IP Profile from step 3. The Swisscom configuration note illustrates the IP Group, Proxy Set, and Trunk flow, which is identical in principle. (AudioCodes)

  5. Configure the PRI T1 side

    1. Trunks and Groups > Trunks. Set Protocol Type to T1 NI2 ISDN or the switch type your PBX expects. Set line coding to B8ZS, framing ESF, and clocking based on your design. The BroadCloud quick setup shows the PRI page and fields, and the guides describe T1 NI2 ISDN. (AudioCodes)

  6. Trunk Group and Channel Map

    1. Build a Trunk Group that includes the PRI span and channels you plan to use. The quick setup guide shows this workflow. (AudioCodes)

  7. Number normalization

    1. Normalize inbound numbers to E.164 and map outbound from the PBX to E.164 before sending to Viirtue. Use Message Manipulation or IP‑to‑Tel and Tel‑to‑IP routing rules. The manuals show where these tables live. (AudioCodes)

  8. Registration or IP authentication

    1. If the Viirtue trunk is registered, supply the trunk user and password on the Proxy and Registration page. If IP authenticated, ensure the correct source IP and FQDN are used. The quick guide illustrates registration fields. (AudioCodes)

  9. Media and fax

    1. Set codec list to G.711 mu-law as default, enable T.38 with G.711 fall back if you must support fax. Grandstream and other vendor sheets show T.38 is standard in this class; AudioCodes also supports it. (Grandstream)

  10. TLS certificates

    1. Upload the Viirtue CA or intermediate if required, then enable TLS on the SIP Interface. Validate via OPTIONS and REGISTER flow.

  11. Routing

    1. Create IP‑to‑Tel rule: source IP Group Viirtue to destination Trunk Group PRI

    2. Create Tel‑to‑IP rule: source Trunk Group PRI to destination IP Group Viirtue. The Swisscom and BroadSoft notes show the same constructs. (AudioCodes)

  12. Test and monitor

    1. Place inbound and outbound calls, check Status > Active Calls, Syslog, and SIP Message traces. Many AudioCodes guides include these verification steps. (AudioCodes)

Once your AudioCodes Mediant is configured, you’ll have a stable, fully functional bridge between your Viirtue SIP trunk and the on-prem PBX — complete with TLS encryption, proper clocking, and normalized routing.

AudioCodes’ reliability paired with Viirtue’s SIP infrastructure ensures smooth call delivery, predictable failover, and simpler long-term maintenance.

If you’re a Viirtue partner, access the latest interop notes, sample configs, and SBC templates directly in your partner portal to streamline future deployments.

Not yet a partner? Visit viirtue.com to learn how our white-label platform helps MSPs and IT providers deploy SIP trunks, UCaaS, and PRI gateways faster — and profit more from every connection.

Deploy a Fully-Featured Class 5 Softswitch under your own branding

Start Selling VoIP Today

AI Solutions

VoIP & Fax

Viirtue’s free, full-service tool for MSPs.
Free for all Viirtue partners, ViiBE makes quoting and billing seamless, so you can grow your business efficiently while serving your clients better.