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):||22 December 2010|
|PDF File Size:||17.33 Mb|
|ePub File Size:||15.36 Mb|
|Price:||Free* [*Free Regsitration Required]|
Published By Cisco Press. User input is usually provided in one of the following forms:.
Whether the service is constructed using graphical tools or programming libraries, the end result must be able to run on the SCP platform. Audible messages can be used for a number of different purposes, including the following:.
Example of User Interaction. The code modules are triggered by incoming messages, which match a given criteria for the script, from ce1 SSP. 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.
This example is a very simple version of a toll-free service. Several SCEs cs11 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.
Each SIB identifies a common telephony function that is used across services. Book Hosted by www. SIBs are currently quite generic and lack ample detail, making them primarily useful only for high-level modeling of service functions.
Depending on regulatory policies and agreements, information such as the Carrier parameter can be returned in the Connect component to specify inpa particular IXC-providing service for the freephone number.
The SLP is the executable cx1 that results from the service creation process. 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.
Input is collected to make decisions about how a call should be directed and to determine the services the user needs. The program code is then generated for the service, which can be executed at an SCP.
INAP – Wikipedia
Before running it on an SCP platform, the SCE generally provides some level of simulation to determine how the service will function. The Apply Charging operation indicates cd1 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.
SLPs provide the “glue” logic and overall program flow to join SIBs together into meaningful services. The operation within the User Interaction SIB that implements the collection of digits does not determine how the digits will be used.
The toll-free application at the SSP determines that communication with the SCP is necessary to retrieve information for the toll-free service. The result is a complete logic program that can be executed.
ca1 That would defeat the SIB’s “independence” aspect. The Connect operation contains the DestinationRoutingAddress parameter to specify the routable destination number for connecting the call. While they provide similar functionality to those used by North American AIN, they are distinct in their definition and encoding.
Using our example in Figurethe CalledPartyNumber parameter is included to indicate the toll-free number. 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 ina; of how the service might be deployed.
Like the various versions of AIN, INAP defines its own set of remote operations and parameters that are used at the component sublayer. The InitialDP component can include several optional parameters. An example of some SIBs include: It could also include connections to an IP, along with many other variations in the message flow and parameters.
However, the operations have been tailored to the needs of the European region, thus adhering to the ETSI specifications. Note that these tables do not include all INAP operations. This allows SPs to build and deploy their own services. 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 two most common functions involving User Interaction are collecting information from the user and playing audible messages or tones.
Figure shows an exchange between the SSP and SCP that requires the user to enter information based on voice prompts. 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.
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. These building blocks are easily recognizable as part of standard telephony call and feature processing. However, the fundamental building block of this SIB will still be needed.
Application context for SRF to SCF INAP CS1
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. In the case of a toll-free or free phone call, charges are applied to the called party.
Figure shows the message flow for a basic toll-free service using INAP. Good simulators allow phone calls to be placed using resources such as recorded announcements and Voice Recognition Units, to provide a complete simulation of the service.