This statement of compliance compares the OCNCC INAP implementation to: • ETSI defined INAP required for support of Capability Set 1 (CS1), as defined. Core-INAP-CS1-Codes &;ccitt(0) identified-organization(4) etsi(0) inDomain( 1) in-network(1) modules(0) cs1-codes(3) version1(0)} DEFINITIONS::= BEGIN. Jun 1, Intelligent Network Application Protocol (INAP); Part 1: Protocol This document describes the extensions to the ETSI Core INAP CS1 [1,2].
|Published (Last):||5 May 2010|
|PDF File Size:||16.51 Mb|
|ePub File Size:||1.83 Mb|
|Price:||Free* [*Free Regsitration Required]|
Like the various versions of AIN, INAP defines its own set of remote operations and parameters that are used at the component sublayer.
While they provide similar functionality to those used by North American AIN, they are distinct in their definition and encoding. Note that these tables do not include all INAP operations. Additional operations for communication, such as SCF-SCF, exist; however, this section focuses only on those operations that are directly related to services at an SSP. Figure shows the message flow for a basic toll-free service using INAP. The toll-free application at the SSP determines that communication with the SCP is necessary to retrieve information for the toll-free service.
The InitialDP component can include several optional parameters. Using our example in Figurethe CalledPartyNumber parameter is included to indicate the toll-free number. The Apply Charging operation indicates that charging should be applied for the call and might contain a PartyToCharge parameter to indicate whether charges should be applied to the calling or called party. In the case of a toll-free or free phone call, charges are applied to the called party. The Connect operation contains the DestinationRoutingAddress parameter to specify the routable destination number for connecting the call.
Depending on regulatory policies and agreements, information such as the Carrier parameter can be returned in the Connect component to specify a particular IXC-providing service for the freephone number.
This example is a very simple version of a toll-free service. It could also include connections to an IP, along with knap other variations in the message flow and parameters.
The example has been kept simple to provide an understanding of what a simple INAP exchange looks like for a service and to avoid the varying nuances of how the service might be deployed. However, the operations have been tailored to the needs of the European region, thus adhering to the ETSI specifications. This allows SPs to build and deploy their own services.
Several SCEs are available, each differing in features and capabilities; however, they all share a common purpose of generating program code that can be executed by the SCP.
Many SCEs provide a Graphical User Interface that allows software components to be joined together at a high level using visual tools to represent a service. Further modifications and customizations are applied by setting the properties that are associated with the high level objects and often by making software modifications at the software coding level.
The program code is then generated for the service, which can be executed at an SCP. SLPs provide the “glue” logic and overall program flow to join SIBs together into meaningful services.
Each SIB identifies a common telephony function that is used across services. SIBs are currently quite generic and lack ample detail, making them primarily useful only for high-level modeling of service functions.
An example of some SIBs include: These building blocks are easily recognizable as part of standard telephony call and feature processing. The two most common functions involving User Interaction are collecting information from the user and playing audible messages or tones.
Audible messages can be used for a number of different purposes, including the following:. Input is collected to c1 decisions about how a call should be directed and to determine the services the user needs. User input is usually provided in one of the following forms:. Figure shows an exchange between the SSP and SCP that requires the user to enter information based on voice prompts.
Example of User Interaction. The operation within ca1 User Interaction SIB that implements the collection of digits does not determine how the digits will be used. That would defeat the SIB’s “independence” aspect. As the network and services evolve, new means for interacting with the user will inevitably surface, thereby adding additional operations to the User Interaction SIB.
However, the fundamental building block of this Inal will still be needed. The SLP is the executable logic that results from the service creation process.
Radisys | INAP Software
Whether the service is constructed using graphical tools or programming libraries, the end result must be able to run on the SCP platform. The SCE allows subcomponents that make up an SIB to be joined together in a logical flow with decision branch points based on the results of the subcomponent operations.
The result is a complete logic program that can be executed. Before running it on an SCP platform, the SCE generally provides some level of simulation to determine how the service will function. Good simulators allow phone calls to be placed using resources such as recorded announcements and Voice Recognition Units, to provide a complete simulation cx1 the service.
When the service has been constructed using the SCE tools, code modules or program scripts that are eventually deployed to the SCP or Adjunct are generated. The code modules are triggered by incoming messages, which match a given criteria for the script, from imap SSP.
Published By Cisco Press. No part of this book maybe reproduced or transmitted in any form or by any means, electronic or mechanical, including photcopying or recording, or by any information storage and retrieval system, without written permission from the publisher, except for the inclusion of brief quotations in a review. Book Hosted by www.