Database-Driven Call Routing Using Regex and Override Rules
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional call routing mechanisms, which rely on hard-coded rules, are costly, require software modifications, and are slow to implement, necessitating a more efficient and flexible approach.
Innovation Solution
A system that uses regular expressions and databases to dynamically determine call routing based on call parameters, allowing for internal and external calls to be processed through separate query processes, including the use of override routes and outbound/inbound route databases to create dial plans.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If hard-coded rules are used for call routing, then routing accuracy can be maintained, but the system becomes costly to modify and slow to implement changes
Solution Approach 1:
The patent extracts routing rules from hard-coded software and places them into external databases. This separation allows rules to be modified independently of the core software, enabling flexible updates without costly software modifications while maintaining routing accuracy through structured database queries.
Solution Approach 2:
The system transitions from static hard-coded rules to dynamic database-driven rules that can be modified in real-time. The routing logic adapts to changing conditions by querying updated database entries, allowing the system to respond flexibly to new routing requirements without software changes.
2Productivity
If hard-coded rules are used for call routing, then system stability is maintained, but implementation speed decreases
Solution Approach 1:
The system segments routing functionality into separate database tables for different call types (internal calls, external calls, override routes). This segmentation allows independent modification of specific routing rules without affecting the entire system, enabling rapid implementation while maintaining overall system stability through modular changes.
3Measurement precision
If separate query processes are used for internal and external calls, then routing precision is improved, but system complexity increases
Solution Approach 1:
The system uses a universal query interface that handles both internal and external calls through standardized database schemas. While separate query processes exist for different call types, they all follow the same fundamental pattern of querying routing rules from databases, reducing perceived complexity through consistent methodology across different call scenarios.
Data Source
AI summary
Mechanisms (which can include, systems, methods, and media) for routing calls are provided. The mechanisms including: receiving a first message containing first information corresponding to a first telephone call; performing a series of queries based on at least a portion of the first information to determine whether the first telephone call matches a route in a first database, wherein at least one of the queries uses a first regular expression; identifying a first route in response to performing the series of queries; and creating a first dial plan based on the first route. In some embodiments, the mechanisms further comprise: determining whether an override route applies to the first telephone call prior to performing the series of queries. In some embodiments, the first telephone call is an external call. In some embodiments, the first information includes trunk group information (TGI) and the first regular expression is evaluated against the TGI.