Evolve Easy Zero Service¶
Evolve ® Easy Zero (Easy 0) service automates traffic calls where the called number is 0. When a caller dials “0-”, a call is usually routed directly to an operator services position. Easy 0 provides automated menu options of the most commonly requested services handled by the operation. These services are Emergency Calls (911), Directory Assistance, Repair Service, Busy-Line Verification, and Business Office. In addition, the caller is prompted to enter the appropriate digits for calling card, collect, or third party billed calls. If the caller does not make a menu selection, the call is routed to an operator.
Easy 0 allows users to customize a menu with many different options, increasing a caller’s ability to help themselves find the service that they need.
Easy 0 allows users to define the destination and the rules applied to determine the route whether the call is received via SIP or AIN protocol. In Easy 0, calls can be handled through SIP 302 Redirect, Back-to-Back User Agent (B2BUA), Attended Transfer, Authorize_Termination, and Analyze_Info.
Easy 0 includes a ready-to-use web-based user interface for easy access to all its functionality and different layouts for the various user roles to edit and prioritize the features of Easy 0.
The Easy 0 API is also available to allow developers to programmatically integrate Easy 0 with network elements and systems and gives additional flexibility with how Easy 0 is offered to customers.
Separation of Roles¶
Easy 0 is designed for multi-tenancy with three distinct roles. These roles are Platform Owners, Service Providers, and Subscribers. Each of these roles have their own responsibilities and functions.
Platform Owners
The Platform Owner is the entity that deploys the network which runs Easy 0. The Platform Owner is responsible for defining physical egress routes and other network specifics. Additionally, Platform Owners create and define Service Providers.
Service Providers
A Service Provider is the entity that offers Easy 0 as a service. The Service Provider is responsible for defining call plans.
Call Processing¶
When Easy 0 receives an incoming call, the database is checked to verify that the called number is associated with Easy 0. If the called number is not in the Easy 0 database or Easy 0 is not associated with it, the application responds with the configured No-Route Behavior.
If the called number is in the database, the application then steps through the routing engine. The called number will have one or more call plans associated with it. When a match is found, that rule is evaluated and the appropriate destination is provided in the response message. If no rule match applies to the current call, Easy 0 attempts to use the next highest priority call plan, and if no matches are found there, Easy 0 responds with the configured Default No-Route Behavior.
For each call plan, starting with the highest priority routing rule, Easy 0 analyzes the match type and the criteria. If the rule match does not apply to the current call, the next rule is analyzed.
Signaling¶
Easy 0 is deployed in the network and is designed to handle AIN and SIP signals to process call routing behavior.
The rest of this chapter details the specific call flow of various call treatments.
Note
Wireshark traces of a call flow can be viewed by clicking the link provided below the diagram.
SIP Call Treatments¶
SIP REDIRECT Method
The following diagram shows the message exchange when the SIP 302 REDIRECT connection type is selected.
SIP Attended Transfer (REFER Method)
The following diagram shows the message exchange when the Attended Transfer connection type is selected.
SIP B2BUA
The following diagram shows the message exchange when the SIP B2BUA connection type is selected.
AIN Queries and Responses¶
AIN Termination_Attempt
The following diagram shows the message exchange when Termination_Attempt is received in a no-route case.
The following diagram shows the message exchange when Termination_Attempt is received in a route case.
AIN Info_Collected
The following diagram shows the message exchange when Info_Collected is received.
AIN Info_Analyzed
The following diagram shows the message exchange when Info_Analyzed is received.
AIN Needing Media
The following diagram shows the message exchange when an IN call needs media.
