Routing¶

Route Path¶

graph LR A(Incoming Call) --> B[Customer] B --> C[Ingress Routing] C --> D[Customer Rate Card] D --> E[Carrier Rate Card] E --> F(Carrier IPS)

Routing in ConnexCS CloudSwitch occurs in the following stages:

An incoming call leads to customer identification and confirmed by the source IP or User / Pass Authentication.
Ingress Routing looks for prefixes and then compares them to available rate cards. There can be several ingress routes per customer.
You can build a Customer Rate Card from the carriers above it. Also, the parent of the customer card can present the call to any carrier who is the parent of the customer rate card.
The Carriers Rate Card links you with a specific carrier.
The selected carrier can have several IP addresses. Also, it makes a random call, but carrier Calls per Second (CPS) obeys the Channel limits.

Routing and Rate Cards

A rate card in ConnexCS represents a call path. If the rate card is incoming, it identifies the carrier providing that rate card.

Customer rate identifies the carrier rate cards used for its construction.

Routing Engine¶

The Routing Engine receives all calls when they enter the system and then processes them based in which the direction in the call is flowing.

Ingress¶

Ingress refers to inbound calls destined to terminate with one of our customers (UA, phone, Direct Inward Dialing (DID), etc.)

A call bound for termination with one of our customers comes into the routing engine, passes authorisation, and then goes through Ingress Routing.

This determines the call profile and where to send it.

graph LR A(Far End) --> B[PSTN] B --> C[Carrier] C --> D[ConnexCS Switch] D --> E[Routing Engine]me E --> F(Authorisation) F --> G(Ingress Routing)

Ingress Example

When a customer's switch has a DID pointing to it, it's considered Ingress because traffic is coming into the switch.

Egress¶

Egress refers to outbound calls. Egress Routing section isn't available. The Customer Rate Card includes the Egress routing, which contains 1 or more Carriers, and, optionally, a routing strategy (such as Default LCR).

UA -> Customer > Customer Rate Card > Carrier Rate Card -> Carrier -> PSTN -> Far-End

graph LR A(UA) --> B[Customer] B --> C[Customer Rate Card] C --> D[Carrier Rate Card] D --> E[Carrier] E --> F(PSTN) F --> G(Far-End)

Egress Example

When you add a customer's switch that will send traffic to terminate with a carrier, Egress is the customer's switch in that case, as it's sending calls out.

Error Codes¶

If your Session Initiation Protocol (SIP) Trace shows that an INVITE packet was received by the switch but not sent out to any providers, the failure has occurred in the Ingress Routing.

SIP Code	SIP Reason	Details
403	IP Not Authorised	The IP Address doesn't match any account in the system.
500	Unidentified Internal Switch	This is an internal error; you should never see this. If you do please contact us.
500	Server not accepting calls (Paused)	Either your account or server is disabled with ConnexCS.
503	Unknown User	Username & Passwords don't match to any known user account.
503	Unable to perform LRN	You have selected LRN (Location Routing Number) dipping for this route, so it's likely that you don't have credit with us.
503	LCR Unavailable	The system is unable to perform a Least Cost Routing (LCR) lookup.
503	Blocked by Dial plan	The prefix/number isn't matched by the allowed dial plan.
503	No Routes Available (Pre)	No rate card rule to allow the call to progress.
503	No Routes Available (U)	No routes are available either due to: Lock, Profit Assurance, Routing Strategy or ScriptForge.
503	No Routes Available (Lock)	Locking your Ingress routing has left no routing options.
503	No Routes Available (Profit Assurance)	Profit Assurance has left no routing options.
503	Dropping Call (Strategy)	Strategic Routing has dropped the call.
503	Internal Strategic Routing Error	An error with the config of Strategic Routing.
580	No Route Available	The number dialled doesn't match any ingress routing profile.
580	Switch IP Variable Not Provided	This is an internal error; you should never see this. If you do please contact us.
580	To (oU) User Missing	This is an internal error; you should never see this. If you do please contact us.
580	To (fU) User Missing	This is an internal error; you should never see this. If you do please contact us.

End Point synchronisation

When making changes, although we try to synchronise all endpoints as quickly as possible, as this is a distributed system, it can take up to 60 seconds for any changes to take effect.