Evolve Internet Single Number Access Service¶
Evolve ® Internet Single Number Access (ISNA) service allows each Internet service provider (ISP) routing based on a single telephone number for dial-up access throughout a specified area defined by geographical boundaries of local telephone service networks. When dialed, a call will be completed to the lead telephone number dedicated to the ISP.
ISNA includes a web-based user interface (web UI) for easy access to all its functionality. Each role (Subscribers and Service Providers) uses a different layout in the web UI to easily edit and prioritize the features of ISNA.
ISNA has an API that allows developers to programmatically integrate ISNA with your network elements and systems. This gives you additional flexibility with how you offer the feature to your customers.
Geographic Connections¶
ISNA offers a simple way to complete a call on a number to Internet number based on Local Access and Transport Area (LATA). Subscribers and Service Providers are able to change which numbers are forwarded with a web UI that is easy to use. Additionally, Service Providers will be able to import large number of records with the ISNA API.
Separation of Roles¶
ISNA is designed to work in a three-tiered hierarchy, with 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 ISNA. 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 ISNA features as a service to Subscribers. The Service Provider allocates users to their numbers and establishes routing plans for these numbers. The Service Provider is also responsible for defining Subscriber accounts.
Subscribers
Subscribers are the individuals or business entities that subscribe to the ISNA service. Subscribers may be given access to their own numbers and can edit call plans and routing rules as well.
Signaling¶
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 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 Back to Back User Agent (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 an Info_Collected trigger is received and routed with ISNA.
AIN Info_Analyzed
The following diagram shows the message exchange when an Info_Analyzed trigger is received and routed with ISNA.
