DirectRouting

DirectRouting

Planning

Licensing Requirements

Option 1 - Office 365 Enterprise E5

Option 2 - Office 365 Enterprise E3 + Phone System

Option 3 - Office 365 Enterprise E1 + Phone System

Option 4 - Common Area Phone

Option 5 - Common Area Phone

Optional Licenses

Design Decision

You need to decide on the licensing you will use before continuing. Licensing can be a mix of the above.

Tenant Requirements

The following settings must be enabled in the Office 365 tenant.

Enable Calling for Microsoft Teams

  1. Log on as tenant administrator.
  2. Go to Settings and Services and add-ins and select Microsoft Teams.
  3. Expand Calls and meetings and verify that Allow private calling is On.

Teams Calling Policy

Grant-CsTeamsCallingPolicy -PolicyName <policyname> -Identity <identity>

Teams Interop Policy

Grant-CsTeamsInteropPolicy -PolicyName DisallowOverrideCallingTeamsChatTeams -Identity <identity>

Design Requirements:

Calling for teams must be enabled & Users must be assigned Teams calling and Teams Interop Policies.

Comparing Features

SFB vs SFBO vs Direct Routing Features

Supported Features SFB CCE DirectRouting
Audio Conferencing Per Server Per User Per User
Busy Options Y Y Y
BtoE Y Y  
Call Delegation Y Y Y
Call Forwarding Y Y Y
Call Forwarding (Team Call) Y Y Y
Call History Y Y Y
Call Hold/Retrieve Y Y Y
Call Park Service Y Y Y
Call Queue/IVR Y Y Y
Consultive & Blind xfer Y Y Y
Least Cost Routing Y   Y
Location Based Routing Y   Y
Private line Y    
Qos/DSCP Y Y Y
Sharedline Appearance Y   Y
VDI Media Redirection Y Y  

Supported Features IP Phones

Task SFB SFBO DirectRouting
405hd y y y
420hd y   y
430hd y y y
440hd y y y
445hd y y y
450hd y y y
c450hd     y

SBC Configuration

Audiocodes Mediant

DirectRouting

Configure Direct Routing in Office 365 (Enterprise)

Install Skype for Business Online Connector

Download and Install SFB

Download and Install Skype for Business Online Connector Information available

Download from Microsoft

Connect to SFBO using PowerShell

Use PowerShell to connect to SFBO with PowerShell

Import-Module SkypeOnlineConnector
$Credential = Get-Credential
$Session = New-CsOnlineSession
Import-PsSession -Session $Session -AllowClobber

Add a new PSTN Gateway

The following example contains all the minimum parameters required to configure to pair the SBC to the tenant. Generally it is best to Enable ForwardCallHistory & ForwardPAI

Parameter Default Value example Comments
FQDN   sbc.directrouting.guide based on customer domain
SipSignallingPort 5067 5067 based on sbc config
MaxConcurrentSessions   10 based on sbc license
FailoverTimeSeconds 10 10  
ForwardCallHistory false true  
ForwardPAI false true If set Privacy:ID with SBC Manipulation
SendSIPOptions true true  
MediaBypass false true  
MediaRelayRoutingLocationOverride      
Enabled true true  

Example 1 - Create a New PSTN Gateway with minimum parameters

New-CsOnlinePSTNGateway -Fqdn "sbc.directrouting.guide" -SipSignallingPort "5067" -Enabled $true
New-CsOnlinePSTNGateway -Fqdn "sbc.directrouting.guide" -SipSignallingPort "5067" -MaxConcurrentSessions "10" -ForwardCallHistory $true -ForwardPAI $true -Enabled $true

Validating the SBC pairing

Validate in Office 365

Validate that the SBC is present in the list of paired SBCs by running Get-CSOnlinePSTNGateway

Get-CsOnlinePSTNGateway -Identity "sbc.directrouting.guide"

Validate is Syslog

Using Syslog or similar tools confirm the the SBC sends a SIP Option to office 365 and receives a 200 OK.

If SIP options are successful you will begin to see SIP options originating from Teams.

Add a new online PSTN Usage

All routes require an associated PSTN Usage that can only be added to the Global usage.

Example 1 - Add a PSTN Usage

Set-CsOnlinePstnUsage  -Identity Global -Usage @{Add="DirectRouting"}

Example 2 - Remove a PSTN Usage

Set-CsOnlinePstnUsage  -Identity Global -Usage @{Remove="Australia"}

Add online voice route

Example 1 - Voice Route for All Calls

New-CsOnlineVoiceRoute -Identity "DirectRouting" -NumberPattern ".*" -OnlinePstnGatewayList "sbc.directrouting.guide" -Priority 1 -OnlinePstnUsages "DirectRouting"

Example 2 - Online Voice Route for Australian Calls

New-CsOnlineVoiceRoute -Identity "Australia" -NumberPattern "^+61(\d{9})$" -OnlinePstnGatewayList "sbc.directrouting.guide" -Priority 1 -OnlinePstnUsages "Australia"

Add Online Voice routing Policy

Example 1 - Voice Routing for All Calls

New-CsOnlineVoiceRoutingPolicy -identity "DirectRouting" -OnlinePstnUsages "DirectRouting"

Example 2 - Voice Route for Australian Calls**

New-CsOnlineVoiceRoutingPolicy -identity "Australia" -OnlinePstnUsages "Australia"

Planning Direct Routing (Enterprise)

Licensing Requirements

Option 1 - Office 365 Enterprise E3 + Phone System

Option 2 - Office 365 Enterprise E5

Optional Licenses

Design Decision: You need to decide on the licensing you will use before continuing. Licensing can be a mix of the abo

Tenant Requirements

The following settings must be enabled in the Office 365 tenant.

Enable Calling for Microsoft Teams

  1. Log on as tenant administrator.
  2. Go to Settings and Services and add-ins and select Microsoft Teams.
  3. Expand Calls and meetings and verify that Allow private calling is On.

Teams Calling Policy

Grant-CsTeamsCallingPolicy -PolicyName <_policy name_> -Identity <_identity_>

Teams Interop Policy

Grant-CsTeamsInteropPolicy -PolicyName DisallowOverrideCallingTeamsChatTeams -Identity <identity>

Design Requirements: Calling for teams must be enabled & Users must be assigned Teams calling and Teams Interop Policies.

User Requirements

The following settings must be enabled in the Office 365 tenant.

Enable Calling for Microsoft Teams

  1. Log on as tenant administrator.
  2. Go to Settings and Services and add-ins and select Microsoft Teams.
  3. Expand Calls and meetings and verify that Allow private calling is On.

Teams Calling Policy

Grant-CsTeamsCallingPolicy -PolicyName <_policyname_> -Identity <_identity_>

Teams Interop Policy

Grant-CsTeamsInteropPolicy -PolicyName DisallowOverrideCallingTeamsChatTeams -Identity <_identity_>

Design Requirements: Calling for teams must be enables, Users must be assigned Teams Calls calling and teams Interop Policies.

SBC Requirements

You must decide what SBC you will use, a list of Approved SBC is available on docs.microsoft.com.

This cheat sheet has been tested with the following SBC’s and should work for you with very minimal modification.

Vendor   Recommended Version
AudioCodes Hyper-v SBC v.7.20A.204.222 or newer
AudioCodes Azure SBC v.7.20A.204.222 or newer

PLEASE NOTE: Inaddition to Hyper-V and Azure, you can also use VMWare,Hardware Appliances, etc. This document has only been tested on the Above two.

The following licenses are required for SBC

Each SBC that will be paired with Microsoft Teams will require at a minimum

Information Did you know you can download a trial SBC from AudioCodes that you can configure with teams? The trial license includes 3 sessions that allow you test Direct Routing with minimal investment.

Vendor Download Link
AudioCodes v7.20A - Mediant VE KVM/OpenStack File
AudioCodes v7.20A - Mediant VE Hyper-V VM Image
AudioCodes v7.20A - Mediant VE VMware OVF File
AudioCodes v7.20A - Mediant VE Azure Marketplace
AudioCodes v7.20A - Mediant VE Latest Firmware CMP

Connection Points

Connection points are load balanced automatically based on performance metricx and geographical proximity.

The FQDN’should always be placed in the correct order to

Sip Connection FQDN Priority Comments
sip.pstnhub.microsoft.com 1 Primary FQDN
sip2.pstnhub.microsoft.com 2 Secondary FQDN
sip3.pstnhub.microsoft.com 3 Tertiary FQDN

The SBC makes a DNS query to resolve sip.pstnhub.microsoft.com. Based on the SBC location and the datacenter performance metrics, the primary datacenter is selected. Failover is based on the following locations

Primary Secondary Tertiary
EU US ASIA
US EU ASIA
ASIA US EU

DNS Requirements

To enabled Direct Routing you must meet the following DNS Requirements:

Example SBC Domain Name

FQDN Type Value Comments
sbc.directrouting.guide A 104.210.65.188  
lyncdiscover.directrouting.guide CNAME webdir.online.lync.com  

Quick Tip : Each SBC must have a unique Public DNS address.

Firewall Rules

SBC- Direct Routing Interface

Service Traffic From To Source Port Destination Port
SIP Proxy SIP/TLS 52.114.148.0, 52.114.132.46, 52.114.75.24, 52.114.76.76, 52.114.7.24, 52.114.14.70 < sbc public ipaddress > 1024 – 65535 < sbc sip interface >
SIP Proxy SIP/TLS < sbc public ipaddress > 52.114.148.0, 52.114.132.46, 52.114.75.24, 52.114.76.76, 52.114.7.24, 52.114.14.70 < sbc sip interface > 5061
Media Processor UDP/SRTP 52.112.0.0 /14 < sbc public ipaddress > 49152 – 53247 < sbc media ports >
Media Processor UDP/SRTP < sbc public ipaddress > 52.112.0.0 /14 < sbc media ports > 49152 – 53247

The SIP Proxy and Media Proxy above should resolve to all IP Addresses of sip-all.pstnhub.microsoft.com When defining the Ports always a minimum of 2 ports per concurrent call

SBC - SIP Trunk Interface

Service Traffic From To Source Port Destination Port
Signalling SIP/TLS < itsp ipaddress > < sbc ipaddress > any < sbc sip interface port >
Signalling SIP/TLS < sbc ipaddress > < itsp ipaddress > < sbc sip interface port > < itsp sip interface port >
Media UDP/SRTP/RTP < itsp ipaddress > < sbc ipaddress > any < sbc media ports >
Media UDP/SRTP/RTP < sbc ipaddress > < itsp ipaddress > < sbc media ports > < itsp media ports >

SBC - Management Interface

Service Traffic From To Source Port Destination Port
Management TCP < Internal Network > < sbc ipaddress (oamp) > any 443
Management TCP < Internal Network > < sbc ipaddress (oamp) > any 23
Management TCP < Internal Network > < sbc ipaddress (oamp) > any 22
Management ICMP < Internal Network > < sbc ipaddress (oamp) > any ICMP
Management TCP/UDP < sbc ipaddress (oamp) > < Internal Network > any 53
Management TCP/UDP < sbc ipaddress (oamp) > < Internal Network > any 514

Teams Client

Service Traffic From To Source Port Destination Port
Management TCP < Internal Network >      

Certificates Requirements

Baltimore Trusted Public Root Certificate

The Baltimore Trusted Root must be installed on your SBC, it can be downloaded in either PEM or CRT format from:

Public Certificate Requirements

Each SBC deployed must have a public certificate from a supported Public CA, There are 3 options to create a certificates.

Please Note:

When generating the CSR, The private key size should be at least 2048

Also Do not try to use onmicrosoft.com domain for certificates, it will not work.

Option 1 - Single SBC per certificate

A Single certificate with a single SBC FQDN. The SBC FQDN must be in the subject, common name or the Subject Alternate name.

SN SAN
sbc.directrouting.guide  

Option 2 - Multiple SBC per certificate

A Single certificate with a multiple SBC FQDN’s. The SBC FQDN must be in the subject, common name or the Subject Alternate name.

SN SAN
sbc.directrouting.guide sbc2.directrouting.guide, sbc3.directrouting.guide, sbc7.directrouting.guide, sbc8.directrouting.guide

Option 3 - Wildcard in Subject Alternative Name (SAN)

A certificate with a Wildcard in the Subject Alternative Name (SAN)

SN SAN
sbc.directrouting.guide *.directrouting.guide

Option 4 - Wildcard in CommonName (CN)

A certificate with a Wildcard in the Common Name (CN)

CommonName
*.directrouting.guide

Supported Public CA

Microsoft currently supports the following Public CA’s only. If you are purchasing a certificate please ensure it is signed by one of these root CA’s.

The following Public CA’s have been known to work, but are not currently on the list of supported CA’s

Peering Partners

Peering is the direct interconnection between Microsoft’s network (AS8075) and another network for the purpose of exchanging traffic between these networks. If you need to determine how your network is peering with Microsoft, then this will be useful. If you dont know what peering is about, then you can safely ignore this page!

Microsoft peers are listed on the peeringdb (AS 8075)

tracert 13.107.0.68

Troubleshooting Teams

Skype Online PowerShell Module

Download and Install Skype for Business Online Module

Teams PowerShell Module

Official Teams PowerShell Module

install-module teams
import-module teams

Teams Tools PowerShell Module

Unoffical Teams Tools PowerShell Module

install-module teamstools
import-module teamstools

PowerShell SIP Tester Script

SIP Tester client is a sample PowerShell script that you can use to test Direct Routing Session Border Controller (SBC) connections in Microsoft Teams.

AudioCodes Syslog

Fiddler

Deugging with Teams client

Teams Client Download Method

To download debugging logs from Microsoft teams, press

Ctrl + Shift + Alt</kbd> + 1

This wil download two files that may contain information…

Teams Client right click method

Right Click on the Teams icon in task bar and select get logs

Clearing Teams Cache

Confirming SIP Options

Options

10:09:50.374  ---- Outgoing SIP Message to 52.114.132.46:5061 from SIPInterface #1 (DirectRouting) TLS TO(#2996) SocketID(3008) ---- [Time:16-09@10:10:10.601]

OPTIONS sip: SIP/2.0
Via: SIP/2.0/TLS :;alias;branch=z9hG4bKac1123375059
Max-Forwards: 70
From: <sip:>;tag=1c17881131
To: <sip:>
Call-ID: 14193009801692018101010@172.16.8.66
CSeq: 1 OPTIONS
Contact: <sip:{ site.data.directrouting.teams.fqdn }}:{ site.data.directrouting.teams.signallingport }};transport=tls>
Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUBSCRIBE,UPDATE
User-Agent: Mediant SW/v.7.20A.202.203
Accept: application/sdp, application/simple-message-summary, message/sipfrag
Content-Length: 0

200 ok

10:09:50.604  ---- Incoming SIP Message from 52.114.132.46:5061 to SIPInterface #1 (DirectRouting) TLS TO(#2996) SocketID(3008) ---- [Time:16-09@10:10:10.831]

SIP/2.0 200 OK
FROM: <sip:>;tag=1c17881131
TO: <sip:>
CSEQ: 1 OPTIONS
CALL-ID: 14193009801692018101010@172.16.8.66
VIA: SIP/2.0/TLS :;branch=z9hG4bKac1123375059;alias
CONTENT-LENGTH: 0
ALLOW: INVITE
ALLOW: ACK
ALLOW: OPTIONS
ALLOW: CANCEL
ALLOW: BYE
ALLOW: NOTIFY
SERVER: Microsoft.PSTNHub.SIPProxy v.2018.9.12.1 i.USEA.2

Common Solution

Sympton Solution
Missing 200 OK from Options Missing Root Certificate Change
Firewall Misconfiguration
Fail to verify peer certificate Missing Baltimore Root Certificate
403 Forbidden on options; “Provided trunk FQDN is not allowed” Contact Header missing or incorrect
Transfer fails with 603 decline from SBC Refer Support not enabled
Call connects but no audio; call disconnects shortly after Check NAT travesal
No Outbound Caller ID ForwardPAI is set to true causing all calls to be anonymous, fix with additional SBC Manipulations
“404 Not Found” for incoming calls Phone number not configured correctly, or number not normalised correctly from SBC
Outbound Call Failure Check tenant dial plan, especially the regex

Configuring an AudioCodes SBC for Direct Routing (Enterprise)

This document assumes the following:

Configure the Certificates

goto Setup > IP Network > Security > TLS Contexts

Parameter Value Comments
TLS Version TLSv1.2 Dependant on Public CA
DH Key Size 2048 (Minimum Recommended)

Recommeded CSR Settings

goto Setup > IP Network > Security > TLS Contexts > Change Certificate

Parameter Value
Subject Name[CN] sbc.directrouting.guide
Signatature Algorithm SHA1
Private Key Size 2048 Minimum recommended

Install the Certificate

goto Setup > IP Network > Security > TLS Contexts > Direct Connect > Change Certificate

Install Root and Intermediate Certifiates

goto Setup > IP Network > Security > TLS Contexts > Select DirectRouting > Trusted Root Certificates

Certificate link comments
Baltimore Certificates Baltimore Certificates  
Root CA letsencrypt.org IMPORTANT This will be based on certificate purchased for the SBC, in lab environments I use free 90 day certs from letsencrypt.org and if I need longer than that I generally use digicert.com
Intermediant CA letsencrypt.org (Cross-Signed byIdenTrust) letsencrypt.org (Signed by ISRG Root X1) IMPORTANT This will be based on certificate purchased for your SBC, in lab environments I use free 90 day certs from letsencrypt.org and if I need longer than that I generally use digicert.com

Configure NTP Settings


goto Setup > Administration > Time & Date

Parameter Required Values Comments
Enable NTP Enable  
Primary NTP pool.ntp.org As per customer Requirements
UTC Offset 3600 As per customer Requirements
Daylight Savings Enabled As per customer Requirements

Configure Syslog Settings

TroubleShoot > Logging > Syslog Settings

Syslog software can be downloaded from AudioCodes

Configure the Syslog Settings

Parameter Value Comments
Enable Syslog Enable  
Syslog Server 10.0.0.5 As per customer requirement’s
Debug Level Detailed  

Configure Default DNS Settings (Optional)

goto Setup > IP Network > DNS > DNS Settings

Parameter Value Comments
Primary DNS 1.1.1.1 As per customer Requirements
Secondary DNS 1.0.0.1 As per customer Requirements

Configure the Media Realm

goto Setup > Signaling and Media > Core Entities > Media Realms

SIPTrunk Media Realm

Parameter Value  
Index 0  
Name SIPTrunk  
Topology Location Up  
IPv4 Interface Name #0 [eth0] As per customer Requirements
Port Range Start 6000 As per customer Requirements
Number of media session legs 10 As per customer Requirements
Default Media Realm No  

Direct Routing Media Realm

Parameter Value  
Index 1  
Name DirectRouting  
Topology Location Down  
IPv4 Interface Name #0 [eth0]  
Port Range Start 7000 As per customer Requirements
Number of media session legs 10 As per customer Requirements
Default Media Realm No  

Configure the SIP Interfaces

goto Setup > Signaling and Media > Core Entities > SIP Interfaces

SIPTrunk SIP Interface

Parameter Value Comments
Name SIPTrunk  
Network Interface #0 [eth0] as per sbc configuration
Topology Location UP  
UDP port 5061 as per SIPTrunk Requirements
TCP Port 0  
TLS Port 0  
Enable TCP Keepalive Enable  
Media Realm #0 [SIPTrunk] as per sbc configuration
TLS Context Name -  
Classification Failure Response Type 500 Default

Direct Routing SIP Interface

Parameter Value Comments
Name DirectRouting  
Network Interface #0 [eth0] as per sbc configuration
Topology Location Down  
UDP port 0  
TCP Port 0  
TLS Port 5067 user defined
Enable TCP Keepalive Enable  
Media Realm #1 [DirectRouting] as per sbc configuration
TLS Context Name #1 [DirectRouting] as per sbc configuration
TLS Mutual Authentication Enable  
Classification Failure Response Type 0 Recommended to prevent DoS attacks

Configure Proxy Sets & Proxy Address

goto Setup > Signaling and Media > Core Entities > Proxy Sets

SIPTrunk Proxy Set

Parameter Value Value
Index 0
Name SIPTrunk
SBC IPv4 SIP Interface #0 [SIPTrunk]
Proxy Keep Alive Using OPTIONS

SIPTrunk Proxy Address

**Setup > Signaling and Media > Core Entities > Proxy Sets > Add Proxy Address **

Parameter Value
Proxy Address [siptrunk]:[signalling port]
Transport Type UDP

Configure Proxy Sets

Setup > Signaling and Media > Core Entities > Proxy Sets

Parameter Value Value
Index 1
Name DirectRouting
SBC IPv4 SIP Interface #1 [DirectRouting]
TLS Context Name #1 [DirectRouting]
Proxy Keep Alive Using OPTIONS
Proxy Hot Swap Enable
Proxy Load Balancing Method Random Weights

Configure Proxy Address - Direct Routing

Setup > Signaling and Media > Core Entities > Proxy Sets > Add Proxy Address

Parameter Value
Proxy Address sip.pstnhub.microsoft.com:5061
Transport Type TLS
Proxy Priorty 1
Proxy Random Weight 1
Parameter Value
Proxy Address sip2.pstnhub.microsoft.com:5061
Transport Type TLS
Proxy Priorty 2
Proxy Random Weight 1
Parameter Value
Proxy Address si3p.pstnhub.microsoft.com:5061
Transport Type TLS
Proxy Priorty 3
Proxy Random Weight 1

Configure Coder Group

Setup > Signaling and Media > Coders and Profiles > Coder Groups

Recommend you update the coder specifically for SIP TRUNK providor !

Coder Name Packetization Time Rate Payload Type Silense Suppression Coder Specific
G.711A-law 20 64 8 Disabled  
G.711U-law 20 64 0 Disabled  

Recommend you create a new coder specifically for Direct Routing !

Coder Name Packetization Time Rate Payload Type Silense Suppression Coder Specific
SILK-NB 20 8 103 N/A  
SILK-WB 20 16 104 N/A  
G.711A-law 20 64 8 Disabled  
G.711U-law 20 64 0 Disabled  
G.729 20 8 18 Disabled  

Configure IP Profiles

Setup > Signaling and Media > Coders and Profiles > IP Profiles

Configure SIPTrunk IP Profile

Parameter Value comments
Name SIPTrunk  
SBC Media Security Mode RTP As per your SIP Trunk
Extension Coders Group #1 [Audio_Coders_Groups_1]  
P-Asserted-Identity Header Mode Add Required for Anonymous calls
Remote REFER Mode Handle Locally  
Remote Replaces Mode Handle Locally  
Remote 3xx Mode Handle Locally  
Remote Multiple 18x Not Supported ONLY Required if you get Ringback then silence

Configure Direct Routing IP Profile

Parameter Value comments
Name DirectRouting  
SBC Media Security Mode SRTP  
Remote Early Media RTP Detection Mode By Media  
Extension Coders Group #1 [Audio_Coders_Groups_1]  
RTCP Mode Generate Always  
ICE Mode Disabled/Lite Only Enable Lite if you enable Media Bypass, otherwise keep disabled
SIP Update Support Not Supported  
Remote Re-Invite Support Supported only with SDP  
Remote Delayed Offer Support Not supported  
Remote REFER Mode Handle locally  
Remote 3xx Mode Handle locally  
Remote Hold Format Inactive  

Configure IP Group

goto Setup > Signaling and Media > Core Entities >_ IP Group_

Configure SIPTrunk IP Group

Parameter Value
Name SIPTrunk
Topology Location Up
Proxy Set #1 [SIPTrunk]
IP Profile #1 [SIPTrunk]
Media Realm #0 [SIPTrunk]

Configured DirectRouting Group

Parameter Value
Name DirectRouting
Topology Location Down
Proxy Set #2 [DirectRouting]
IP Profile #2 [DirectRouting]
Media Realm #1 [DirectRouting]
Classify By Proxy Set Disable
Local Host Name sbc.directrouting.guide
Always Use Src Address Yes
Proxy Keep-Alive using IP Group settings Enabled
DTLS Context #1 [DirectRouting]

Configure SRTP

goto Setup > Signaling and Media > Media > Media Security

Parameter Value
Media Security Enable
Media Security Behavior Preferable

Configure Message Condition Rule

Setup > Signaling and Media > Message Manipulation > Message Condition

Parameter Value
Index 0
Name DirectRouting-Contact
Condition header.contact.url.host contains ‘pstnhub.microsoft.com’

Configure Classification

Setup > Signaling and Media > SBC > Classification Table

Parameter Value
Index 0
Name DirectRouting
Source SIP Interface DirectRouting
Source IP Address 52.112..
Destination Host sbc.directrouting.guide
Message Condition DirectRouting-Contact
Action Type Allow
Source IP Group #2 [DirectRouting]
Parameter Value
Index 1
Name DirectRouting
Source SIP Interface DirectRouting
Source IP Address 52.113..
Destination Host sbc.directrouting.guide
Message Condition DirectRouting-Contact
Action Type Allow
Source IP Group #2 [DirectRouting]
Parameter Value
Index 2
Name DirectRouting
Source SIP Interface DirectRouting
Source IP Address 52.114..
Destination Host sbc.directrouting.guide
Message Condition DirectRouting-Contact
Action Type Allow
Source IP Group #2 [DirectRouting]
Parameter Value
Index 3
Name DirectRouting
Source SIP Interface DirectRouting
Source IP Address 52.115..
Destination Host sbc.directrouting.guide
Message Condition DirectRouting-Contact
Action Type Allow
Source IP Group #2 [DirectRouting]

Configure IP to IP Routing

Setup > Signalling and Media > SBC > Routing > IP-to-IP Routing

Option Terminate

Parameter Value
Index 0
Name OPTIONS Terminate
Source IP Group Any
Request Type Options
Destination Type Dest Address
Destination Address Internal

Refer Terminate

Parameter Value
Index 1
Name REFER
Source IP Group Any
Call Trigger Refer
ReRoute IP Group #2 [DirectRouting]
Destination Type Request URI
Destination IP Group #2 [DirectRouting]

Sip Trunk to Direct Routing

Parameter Value
Index 2
Name SIPTrunk to DirectRouting
Source IP Group #1 [SIPTrunk]
Destination Type IP Group
Destination IP Group #2 [DirectRouting]

Direct Routing to Sip Trunk

Parameter Value
Name DirectRouting
Source IP Group #2 [DirectRouting]
Destination Type IP Group
Destination IP Group #1 [SIPTrunk]
Index SourceIP subnet Start Port end Port Protocol Use Specific Interface Interface ID Allow Type
0 52.112.0.0 14 0 65535 Any Enabled #0 [eth0] Allow
1 SIPTrunk subnet 0 65535 Any Enabled #0 [eth0] Allow
49 0.0.0.0 0 0 65535 Any Enable #0 [eth0] Block

Advanced Feaures

Local Media Optimsation

DirectRouting

Resilency Options

DirectRouting

Media Bypass

DirectRouting

Resources

Links to useful resources like additional documentation, code snippets, and more. Suggest new resources on GitHub.

Direct Routing Documentation

AudioCodes Downloads