Voice Routing Quick Start Guide
Back to Articles
VoIP SIP Routing Telecom LCR Call Routing Howto

Voice Routing Quick Start Guide

October 11, 2018 2 min
Aivis Olsteins

Aivis Olsteins

In a new series of articles on our Documentation site we have just published a Voice Routing Quick Start Guide. It shows how to set up advanced routing of voice calls on a step by step basis.

Here, I only want to touch some of the most important points.

1. Routing engine should be consistent, and should operate on a single. centralized code list (Master Code List). Many vendors have their own destination code lists, and it is common for them to overlap and conflict. It is for an administrator to decide which breaoust should be used and which not, but the list should be the same across the system.

2. It is designed to never interrupt the production traffic. Threfore it features a versioned Master Code list. It is possible to upload or manually create a new master code list while keeping the current one active. Many carriers announce their dates of changes in advance (price changes, codes etc), so it is also possible in SAARA system to schedule new code list activation dates so they can match with the carrier announced dates.

3. Most specific breakout matching is the basis of routing. It is logical and well established system in voice call routing (and pricing) to base code allocations on the longest matching prefix basis. Once the most specific prefix is found, the routing decision is made within this group. It can be manual priority, LCR or any other method. The search for less specific breakout can be enabled or disabled by adminsitrator according to their preferences.

4. Least Cost Routing (LCR) works with incosistent vendor price lists. As mentioned above, not all vendors will supply their rates with code breakouts which match your Master List and which may differ between themselves. The LCR engine takes this problem and adjusts routes according to the breakouts in your Master List while respecting the fact that carriers have different definitions of breakouts and they will charge accordingt to their breakouts. This feature is very imprtant as it prevents from accidentally being charged much higher price if the breakout falls into different destinations as it was assigned in Master Code list.

A view of the SAARA Voice Routing Screen:

{$image1}

 

Share this article

Aivis Olsteins

Aivis Olsteins

An experienced telecommunications professional with expertise in network architecture, cloud communications, and emerging technologies. Passionate about helping businesses leverage modern telecom solutions to drive growth and innovation.

Related Articles

How Voice AI Reduces Agent Burnout and Boosts Satisfaction

How Voice AI Reduces Agent Burnout and Boosts Satisfaction

Reduce Burnout with Voice AI: Offload Repetitive Calls, Real‑Time Agent Assist, 40–80% Less ACW, Calmer Escalations, Healthier Occupancy, Proactive Deflection & PCI‑Safe Flows—Happier Agents, Faster Resolutions, Better Coaching, Faster Ramp

Read Article
Seamless Voice AI Integrations: Salesforce, HubSpot, and ERP Systems

Seamless Voice AI Integrations: Salesforce, HubSpot, and ERP Systems

Seamless Voice AI Integrations with Your Stack: Salesforce & HubSpot CRM + SAP/Oracle/NetSuite/Dynamics ERP; OAuth2 & mTLS Security; Real‑Time Read/Write (Cases, Orders, Payments, Scheduling); Warm Transfers, Context; Audit Logs, SLAs, iPaaS Support

Read Article
Measuring Voice AI Success: The KPIs That Matter—CSAT, Containment, Speed, Accuracy, Reliability, and ROI

Measuring Voice AI Success: The KPIs That Matter—CSAT, Containment, Speed, Accuracy, Reliability, and ROI

Voice AI KPI Scorecard: CSAT/NPS, FCR & Containment, Time‑to‑First‑Word & p95 Latency, Intent/Slot Accuracy & ASR WER, Groundedness, Tool Success (Payments/IDV/Scheduling), Warm Xfers, Uptime/Reliability, Consent/Redact, Cost per Resolution & ROI

Read Article
Sensitive Data in Voice AI: PCI‑Safe Payments, HIPAA‑Compliant PHI, Redaction & Tokenization

Sensitive Data in Voice AI: PCI‑Safe Payments, HIPAA‑Compliant PHI, Redaction & Tokenization

Managing Sensitive Data in Voice AI: PCI‑Safe Payments (DTMF Masking, Tokenization), HIPAA‑Compliant PHI Segregation, Redaction/De‑Identification, End‑to‑End Encryption, Zero‑Trust Access, Residency/Retention, DSAR Deletion, SIEM‑Audited Trails

Read Article

SUBSCRIBE TO OUR NEWSLETTER

Stay up to date with the latest news and updates from our telecom experts