Skip to main content

Voice Trunk Management

A Trunk is a connection between the Cloudonix platform and a remote SIP compliant platform. A Trunk provides connectivity to the telephony provider (carrier network) or a remotely installed UCaaS, CCaaS or CPaaS provider. For sake of simplicity, you can imagine a Trunk as the old telephone connector in your house - where you used to connect a desk phone and get a solid tone, indicating that your phone line is alive - allowing you to make outbound calls (Outbound Trunk) or receive calls (Inbound Trunk). Just like any other Model/Object in Cloudonix, an trunks have various properties, depending on their trunk direction (Inbound or Outbound).

Click here for a complete list of compatible carrier networks and vendors, that had already been connected to Cloudonix successfully.

Outbound Trunk

An Outbound Trunk carries voice calls from Cloudonix to a remote carrier or vendor platform.

Properties List

PropertyDescriptionTypeDefault
Trunk NameA unique name that identifies your outbound trunkStringNone
Transport TypeWhat transport is used by outbound trunk. Values may be UDP, TCP or TLS.StringUDP
AddressThe remote IP address or FQDN of your provider or equipmentStringNone
PortThe remote IP port of your provider or equipmentNumber5060
PrefixA string that is appended to the dialed destination as a prefixStringNone
MetricA number representing the priority of this outbound trunk. The higher the number, the higher the priority.NumberNone
Lock routing to this Cloudonix border serverForce Cloudonix to route outbound calls via a specific border gateway IP or FQDN.StringNone
Force domain name for SIPUse provided string as the SIP Domain for call via this outbound trunk.StringNone
Force SIP Request URIUse provided IP address or FQDN as the remote outbound trunk address.StringNone
Login UserA username provided by the carrier for SIP authorization.StringNone
PasswordA password provided by the carrier for SIP authorization.StringNone

An outbound trunk may also include various Trunk Profile Settings - however, these currently have no actionable effect on outbound trunk operations. Following below is a sample of the Outbound Trunk cockpit view:

Inbound Trunk

An Inbound Trunk carries voice calls from a carrier network or a remote vendor platform into Cloudonix.

Properties List

PropertyDescriptionTypeDefault
Trunk NameA unique name that identifies your inbound trunkStringNone
Transport TypeWhat transport is used by inbound trunk. Values may be UDP, TCP or TLS.StringUDP
AddressThe remote IP address or FQDN of your provider or equipmentStringNone
PortThe remote IP port of your provider or equipmentNumber5060
PrefixA string that is appended to the dialed number as a prefix. This string with automatically removed by Cloudonix, if the call is accepted for processing.StringNone

An inbound trunk may also include various Trunk Profile Settings - however, these currently have no actionable effect on outbound trunk operations.

Inbound CNAME aliasing

When a Cloudonix Domain is created, an auto generated domain alias is created, enabling a simpler way to create an inbound voice trunk. The domain CNAME alias can be obtained from the Settings screen of your Cloudonix domain. Your domain CNAME will look something like this:

-- SIP CNAME image

Once you have your CNAME, copy it to your favorite editor, then append to it the following text: .sip.cloudonix.net. The newly created FQDN represents your Cloudonix inbound trunk address. For example, assuming your CNAME alias is 1234567890-abcdefgh, then your inbound voice trunk address will be 1234567890-abcdefgh.sip.cloudonix.net.

When a remote service provider initiates a SIP call to Cloudonix, sending it to the above domain will automatically assign that inbound call to your Cloudonix domain for further voice application processing.

Inbound Full INVITE Inspection

Full INVITE Inspection is designed as an additional security tool, to ensure that calls from specific endpoint match specific criteria. Matching is performed as either an Exact Match, Partial Match or a Regular Expression. Matching can be performed based upon a specific SIP Header and its value. Let us assume the following inspection criteria:

If the inbound call SIP From: Header doesn't match the string +972391111111 the inbound call is then rejected.

Following below is a sample of the Inbound Trunk cockpit view:

Compatibility List

The following is a list of verified carrier networks and SIP equipment vendors that has successfully connected with Cloudonix, as either an Inbound Trunk, Outbound Trunk or both. Each carrier or vendor includes a rating, based upon a number of stars. The rating is based upon the number of transactions and integrations with Cloudonix performed so far. The more stars a carrier or vendor has, the deeper and more integrations had been performed with this carrier or vendor. Rating ranges from a single star (

) to 5 stars ().

Telephony Providers

info

In some places, Telephony Providers are also referred to as Carriers.

NameTypeInboundOutboundRatingCountry
DIDWWCarrierGlobal
DIDXCarrierGlobal
Bezeq InternationalCarrierIsrael
HOT TelecomCarrierIsrael
PartnerCarrierIsrael
CellcomCarrierIsrael
Halo015CarrierIsrael
VoiceTelCarrierUS
SimwoodCarrierUK
IDT ExpressCarrierUS
VoxbeamCarrierUS

Cloud PBX

info

Under this category we list services such a UCaaS, CCaaS, CPaaS or any other form of business communications cloud vendor.

NameTypeInboundOutboundRatingCountry
Twilio (via BYOC)CPaaSGlobal
TelnyxCPaaSGlobal
Plivo (via BYOC)CPaaSGlobal
SignalWire (via BYOC)CPaaSGlobal
Amazon ConnectCCaaSGlobal
FreshdeskCCaaSGlobal
3CXUCaaSGlobal
ZadarmaUCaaSGlobal
TelnyxCPaaSGlobal

Vendors

info

Under this category we listed open source projects, equipment vendors and/or software vendors.

NameTypeInboundOutboundRatingCountry
EnswitchVendorGlobal
AsteriskVendorGlobal
FreeswitchVendorGlobal
OpenSIPSVendorGlobal
KamailioVendorGlobal
3CXVendorGlobal
AvayaVendorGlobal
CiscoVendorGlobal

Can't find your carrier or vendor? no worries, you can still connect them to Cloudonix. The list above are the ones we know about and had performed testing with. If you would like to verify your carrier or vendor, simply contact us, using this contact form, and we'll help you verify your requirement.