The Sansay VSXi session controller is a high-performance software-based SBC that provides critical functions for communications service providers, including security and DDoS protection, network address translation, protocol interworking and traffic management. The VSXi selects optimal routes for voice communications traffic and assures effective interworking with outside networks. For subscriber-facing traffic management, the session controller provides packet-header manipulation and digit mapping for automatic number identification (ANI) and dialed number identification services (DNIS) manipulation. It is currently the highest performing session control platform on the market.
Additional resources:
VSXi datasheet (pdf download)
VSXi knowledgebase (note that you must be logged into your Sansay account in order to view knowledge articles other than the API)
Instructions for Configuring Sansay SBC's VSXi Session Controller
In this activity you will:
Pre-requisites
Ensure that your Telnyx Mission Command Portal is configured properly
RECOMMENDED: Enable TLS to encrypt your traffic
Set up your Sansay SBC with your IP-PBX and have one or more clients configured and running calls between them
Setting up your Telnyx SIP portal account so you can make and receive calls:
Note: Video walkthrough for Sansay SBC/Telnyx configuration coming soon. Check back as we update our docs. |
1. Create Resources
Log into your Sansay portal and select Resources from the navigation.
Create two new resources, one for your inbound trunk, and one for an outbound trunk.
2. Define resource settings for your inbound trunk
In this section, you'll configure the SIP server information for inbound trunks.
For the first trunk, provide the following settings:
Resource Type: Inbound
Resource Type: Peering
Protocol: SIP
SIP Profile: SIP_Peering:0
Under General Info
SIP Trunk ID: 1000
Trunk name: Telnyx Inbound
Company Name: Telnyx
Route Table: :0
Remote Port: 5060
Service Port: SIP Public Default 1:1
Aggregate Capacity: 1200
Average CPS Limit: 500
Authorized RPS: 500
Unauthorized RPS: 500
Group Policy: Round Robin
Digit Mapping Table: no-translation:0
Min Call Duration: 0
Max Call Duration: 43200
RTP TOS: B8
Direction: Both
Service State: inservice
Allow Direct Media: No
No Answer Timeout: 120
No Ring Timeout: 30
Option Poll: Disable
Cause Code Profile: Default:0
Stop Route Profile: Default:0
PAI: Disable
Under Digit Translation & RN Handling
Ingress & Egress: can be set to all
Outbound ANI: pass
Tech Prefix: default
Under Codec Info:
Policy: enforced
Codec 1: g711u64k
Codec 2: None
Codec 3: None
Codec 4: None
Codec 5: None
Codec 6: None
Codec 7: None
Codec 8: None
Under Fqdns Info:
Depending on which of our SIP Proxies and media servers you interact with, based on your location, we recommend reviewing our signalling IP addresses & media IP addresses articles.
Signalling IPs:
Media IP's:
Click save as & then submit. Now we can work on the outbound trunk.
3. Define resource settings for your outbound trunk
In this section, you'll configure the SIP server information for outbound trunks.
Provide the following settings for your outbound trunk:
Resource Type: Outbound
Resource Type: Peering
Protocol: SIP
SIP Profile: SIP_Peering:0
Under General Info
SIP Trunk ID: 1001
Trunk name: Telnyx Outbound
Company Name: Telnyx
Route Table: :0
Remote Port: 5060
Service Port: SIP Public Default 1:1
Aggregate Capacity: 1200
Average CPS Limit: 500
Authorized RPS: 500
Unauthorized RPS: 500
Group Policy: Round Robin
Digit Mapping Table: no-translation:0
Min Call Duration: 0
Max Call Duration: 43200
RTP TOS: B8
Direction: Both
Service State: inservice
Allow Direct Media: No
No Answer Timeout: 120
No Ring Timeout: 30
Option Poll: Disable
Cause Code Profile: Default:0
Stop Route Profile: Default:0
PAI: Disable
Under Digit Translation & RN Handling
Ingress & Egress: can be set to all
Outbound ANI: pass
Tech Prefix: default
Under Codec Info:
Policy: enforced
Codec 1: g711u64k
Codec 2: None
Codec 3: None
Codec 4: None
Codec 5: None
Codec 6: None
Codec 7: None
Codec 8: None
Under Fqdns Info:
Depending on which of our SIP Proxies and media servers you interact with, based on your location, we recommend reviewing our signalling IP addresses & media IP addresses articles.
Signalling IPs
Media IPs
Click Save as & submit to create your trunk. This will push the configuration to Sansay.
That's it! You've now configured resources for your inbound and outbound trunks.
Additional Resources
Review our getting started with guide to make sure your Telnyx Mission Control Portal account is setup correctly!
Additionally, check out:
VSXi datasheet (pdf download)
VSXi knowledgebase (note that you must be logged into your Sansay account in order to view knowledge articles other than the API.