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].

Author: Tojajin Vudorr
Country: Montserrat
Language: English (Spanish)
Genre: Health and Food
Published (Last): 22 August 2007
Pages: 444
PDF File Size: 2.44 Mb
ePub File Size: 18.3 Mb
ISBN: 457-1-78936-435-8
Downloads: 85574
Price: Free* [*Free Regsitration Required]
Uploader: Murisar

The program code lnap then generated for the service, which can be executed at an SCP. Further modifications and customizations ina; 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 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.

INAP Software

Audible messages can be used for a number of different purposes, including the following:. 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. However, the fundamental building block of this SIB will still be needed. The code modules are triggered by incoming messages, which match a given criteria for the script, from the SSP.

INAP – Wikipedia

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. This allows SPs to build and deploy their own services.


Published By Cisco Press. Input is collected to make decisions about how a call should be directed and to determine the services the user needs. Several SCEs are available, each differing in features and capabilities; however, they all share a common purpose of generating program code that inxp be executed by the SCP.

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.

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 SLP is the executable logic that results from the service creation process. While they provide similar functionality to those used by North American AIN, they are distinct in their definition and encoding.

Example of User Interaction. Each SIB identifies a common telephony function that is used across services. Like the various versions of AIN, INAP defines its own set of remote operations and parameters that are used at the component sublayer. Figure shows an exchange between the SSP and SCP that requires the user to enter information based on voice prompts.

Good simulators allow phone calls to be placed using resources such as recorded announcements and Voice Recognition Units, to provide a complete simulation inp the service. Before running it on an SCP platform, the SCE generally provides some level of simulation to determine how the service will function. The two most common functions inal User Interaction are collecting information from the user and playing audible messages or tones. The Connect operation contains the DestinationRoutingAddress parameter to specify the routable destination number for connecting the call.


It could also include connections to an IP, along with many other variations in the message flow and parameters. The InitialDP component can include several optional parameters. SIBs are currently quite generic and lack ample detail, making them ccs1 useful only for high-level c1s of service functions.

Radisys | INAP Software

Note that these tables do not include all INAP operations. SLPs provide the “glue” logic and overall program flow to join SIBs together into meaningful services.

Book Hosted by www. 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. 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.

An example of some SIBs include: These building blocks are easily recognizable as part of standard telephony call and feature processing.

This example is a very simple version of a toll-free service. The toll-free application at the SSP determines that communication with the SCP is necessary to retrieve information for the toll-free service.