From VoIP.ms Wiki

This article provides general configuration guidelines for connecting an Orchid Link Session Border Controller (SBC) with VoIP.ms SIP trunking. The configuration described below focuses on two Orchid Link zones:

• Access Public: VoIP.ms-facing side of the SBC.
• Access Core: customer network, SIP platform, IP-PBX, softswitch, or core-facing side of the SBC.

Audience: Network and voice engineers familiar with SIP, VoIP.ms accounts, and basic Orchid Link administration.

Vendor confirmation pending: Supported Orchid Link software versions and deployment models should be confirmed with Cataleya before adding a component information table to this article.

Note: The screenshots and field values shown in this article are examples only. Adjust the configuration according to your own network design, security policy, licensing, and Orchid Link deployment.

The Microsoft Teams section is a high-level overview and may require additional configuration and testing.

Contents 1 Prerequisites 2 Configuration Overview 3 Access Public Zone Configuration 3.1 Step 1 - General 3.2 Step 2 - Signaling 3.3 Step 3 - Media 3.4 Step 4 - Call Admission Control 3.5 Step 5 - Security 3.6 Step 6 - Remote Peers 3.7 Step 7 - Routing 3.8 Step 8 - Transcoding 4 Access Core Zone Configuration 4.1 Step 1 - General 4.2 Step 2 - Signaling 4.3 Step 3 - Media 4.4 Step 4 - Call Admission Control 4.5 Step 5 - Security 4.6 Step 6 - Remote Peers 4.7 Step 7 - Routing 4.8 Step 8 - Transcoding 5 Final Checklist

Prerequisites

Before starting the configuration, make sure you have the following information available:

• Access to the Orchid Link administrative interface.
• A configured customer and partition in Orchid Link.
• SIP and media interfaces already created for both the public and core sides.
• The VoIP.ms server or POP information that will be used by the trunk.
• The trusted VoIP.ms source IP addresses or POPs that will be allowed through the SBC security rules.
• SIP credentials or trunk information required for the VoIP.ms side.
• The internal IP address and SIP port of the customer-side PBX, softswitch, or SIP platform.
• Any required SIP Parameters, Transparency, Media, Call Admission Control, and Routing Policy profiles.

Configuration Overview

The Orchid Link SBC configuration is separated into two main zones:

• Configure the Access Public zone first. This zone represents the VoIP.ms-facing side of the SBC.
• Configure the Access Core zone after the Access Public zone. This zone represents the customer network or PBX-facing side of the SBC.

Once both zones are created, routing is configured so that calls can pass between the VoIP.ms side and the core-side SIP environment.

Access Public Zone Configuration

The Access Public zone is the side of the SBC that communicates with VoIP.ms. This zone should be configured first.

Step 1 - General

In the General tab, configure the mandatory fields shown in the Orchid Link interface.

• Name: Enter a descriptive name for the zone, for example, VoIPMS_Public.
• Customer: Select the customer associated with this zone.
• Partition: Select the partition allocated to this customer.
• Zone Type: Select AccessPublic.
• Time Zone: Select the appropriate time zone for the customer.
• Trunk Group Type: Leave this set to None, unless your deployment requires another value.
• Service Level: Keep the default service level, for example, Gold, unless your policy requires otherwise.

Step 2 - Signaling

In the Signaling step, select the SIP-related profiles and interfaces used for the VoIP.ms-facing side.

• SIP Profile: Select the preconfigured SIP Parameters Profile from the drop-down list.

• This profile is created under Profiles > SIP Parameters.

• Transparency Profile: Select the transparency profile created for this deployment.

• This profile can be created under Profiles > Transparency.

• SIP Interface: Select the SIP Interface configured for the public access side and add it to the zone.

Step 3 - Media

In the Media step, select the media interface and media profile used for VoIP.ms traffic.

• Media Interface: Select the Media Interface configured for the public access side and add it to the zone.
• Media Profile: Select the Media Profile used for VoIP.ms traffic.

• The Media Profile is created under Profiles > Media.

Step 4 - Call Admission Control

In the Call Admission Control step, select the CAC profile that will control the number of concurrent sessions allowed for this zone.

• CAC Profile Zone: Select the CAC profile created for this zone.

• The profile is created under Profiles > Call Admission Control.
• Configure the session count according to the licensed capacity allocated for VoIP.ms traffic.

• CAC Profile UE: Select the UE CAC profile if you want to apply per-endpoint limits.

Step 5 - Security

In the Security step, configure the allowed sources and any required security parameters according to your security policy.

• Restrict access to known and trusted VoIP.ms IP addresses or POPs whenever possible.
• Avoid allowing unrestricted public SIP access unless this is specifically required and properly secured.
• Apply any additional SBC security settings required by your deployment.

Step 6 - Remote Peers

No configuration is required in this step for the Access Public zone.

• Leave the default values unless a specific deployment requires otherwise.

Step 7 - Routing

In the Routing step, define where traffic from the Access Public zone should be sent.

• Egress Zone: Select the Access Core zone as the egress destination for this Access Public zone.

Step 8 - Transcoding

If transcoding is not required, no configuration is needed in this step.

• Configure transcoding only if codec interworking is required between VoIP.ms and the customer-side SIP environment.
• The transcoding profile should match your network design and licensing.

Access Core Zone Configuration

The Access Core zone represents the customer network or PBX-facing side of the SBC. Configure this zone after the Access Public zone has been created.

Step 1 - General

In the General tab, configure the core-side zone information.

• Zone Type: Select AccessCore.
• Name: Use a clear name that identifies the customer or core-side environment.
• Customer: Select the relevant customer.
• Partition: Select the partition allocated to the customer.
• Time Zone: Select the appropriate time zone.
• Trunk Group Type: Leave as None, unless your deployment requires otherwise.
• Service Level: Use the appropriate service level for the customer or deployment.

Step 2 - Signaling

In the Signaling step, configure the SIP interface and profiles used toward the customer core network.

• SIP Interface: Select the SIP Interface configured for the core side.
• SIP Profile: Select the appropriate SIP Parameters Profile for the core network.

• This profile may be different from the profile used on the VoIP.ms-facing side.

• Transparency Profile: Select the appropriate transparency profile.

• This profile can be created under Profiles > Transparency.

Step 3 - Media

In the Media step, configure the media interface and media profile used toward the core network.

• Media Interface: Select the Media Interface configured for the core side.
• Media Profile: Select the Media Profile used for traffic toward the core network (customer network or PBX).

Step 4 - Call Admission Control

In the Call Admission Control step, select the CAC profile used for the core-facing side.

• CAC Profile Zone: Select the core-side CAC Profile Zone.

• Configure the session count according to the capacity you want to reserve for core-side calls.

• CAC Profile UE: Select the UE CAC profile if per-endpoint limits are required on the core side.

Step 5 - Security

In the Security step, configure the allowed source addresses for the core-side signaling devices.

• Only allow traffic from trusted internal networks, or core devices
• Do not expose the core-side zone to untrusted networks unless this is part of the intended design and is properly secured.

Step 6 - Remote Peers

In the Remote Peers step, configure the customer-side SIP endpoint information.

• Remote Endpoints: Configure the IP address and port of the remote core endpoint.

• Examples include an IP-PBX, softswitch, SIP application server, or another SBC.
• The Orchid Link SBC will send SIP signaling to these addresses.

Step 7 - Routing

In the Routing step, select the routing policy that will be used for traffic toward the core side.

• Routing Policy: Select the appropriate Session Routing Policy from the drop-down list.

• The policy is configured under Policy Configuration > Session Routing Policies.

Step 8 - Transcoding

Configure transcoding only if codec interworking is required between VoIP.ms and your core network.

• If transcoding is not required, no changes are needed in this step.
• If transcoding is required, select or create the appropriate transcoding profile according to the deployment requirements.

Final Checklist

After completing the configuration, review the following items:

• The Access Public zone is configured as AccessPublic.
• The Access Core zone is configured as AccessCore.
• SIP and media interfaces are assigned to the correct zones.
• The Access Public zone routes traffic toward the Access Core zone.
• The Access Core zone has the correct remote endpoint configured.
• The Session Routing Policy is selected and points to the intended routing behavior.
• Security rules only allow trusted VoIP.ms sources and trusted core-side devices.
• CAC limits match the licensed and intended concurrent call capacity.
• Transcoding is configured only when required.