inap cisco

Americas Headquarters:Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA

© 2007, 2009 Cisco Systems, Inc. All rights reserved.

INAP Feature Module

Document Release History

Feature History

The INAP feature is described in the following sections>

• Feature Overview, page 1

• Supported Platforms, page 14

• Provisionable Properties, page 14

• Related Documents, page 15

• Obtaining Documentation, Obtaining Support, and Security Guidelines, page 15

Feature Overview

Intelligent Network Functional ModelThe Intelligent Network (IN) is described in terms of a functional model as presented by ITU-T Q.1214 specifications. The functional entities include the:

• Service Control Function (SCF)

• Service Switching Function (SSF)

• Call Control Function (CCF)

Publication Date Comments

12/03/03 Initial version of the document.

Release Modification

9.5(2) This feature was introduced.

INAP Feature ModuleFeature Overview

2INAP Feature Module

The PGW 2200 assumes the role of Service Switching Points (SSPs) that contain both the SSF and the CCF. For the purpose of adding IN services, a portion of the CCF behavior is made visible and is described by a Basic Call State Model (BCSM). The SSF interacts directly with the CCF to make this behavior accessible to the SCF. The SSF communicates with the SCF via INAP.

A separate relationship is established between the SSF and the SCF for each call. This occurs when the SSF sends an initial request for instruction to the SCF regarding a new call. Either the SCF or the SSF, depending on circumstances, can terminate the relationship.

Basic Call State ModelThe BCSM is described using the following elements:

• Points in Call

• Detection points

• Transitions

• Events

Calls progress through a series of states that correspond to Points in Call (PICs). Each state change represents a transition that is precipitated by one or more events. Those PICs where a transfer of control can occur between SSP and SCP have an associated detection point (DP). DP processing allows the transition to be seen by the SCF through an event reporting mechanism.

Two types of DPs are defined:

• trigger DPs (TDPs)—statically armed.

• event DPs (EDPs)—dynamically armed under control of the SCF.

Detection points when armed, cause event reports to be sent to the SCP. An event report can be a notification or a request. A notification informs the SCP of an event and a request specifically requests assistance from the SCP. A request implies a transfer of control to the SCP.

For the purpose of the PGW, only the Originating BCSM is used.



Figure 1 PGW Call Model

Detection PointsDetection points (DP) are defined in the BCSM. The BCSM reflects a separation between the originating and terminating call state logic so that the BCSM is described as two state machines; the Originating BCSM and the Terminating BCSM. Since certain detection points can occur in both state machines, the DP names are prefixed with either ‘O_’ or ‘T_’ to distinguish the source.

Trigger Detection PointsFor release 9.5(1), the only trigger detection of interest is the one that occurs at the time of call origination. An armed TDP-R encountered at call origination time causes the SSF to invoke the Initial Detection Point operation.

If a DP is set to Notify and Continue mode and the the INAP operation Continue is received, then the PGW 2200 softswitch will send an abort signal and release the call completely.

Event Detection PointsSupported DPS:

• collectedInfo(DP2)

• analysedInformation(DP3)

• routeSelectFailure(DP4)

• oCalledPartyBusy(DP5)

2. Collect information

Route_Select_Failure

O_Called_Party_Busy

1166

42

O_No_Answer

Collected_Info

3. Analyze information

10 1. Null. Null

2

Analyzed_Info

4. Routing & alerting

3

6

5

4

O_Answer

O_Abandon

O_Disconnect

5. Active

7

9

6. Exception

Analyzed Information (DP3) is statically armed as a trigger detection point in the dialplan.All other detection points are armed dynamically on request in the Request Report BCSM operation (RRBE)

Numbers in boxes represent the DPs



• oNoAnswer(DP6)

• oAnswer(DP7)

• oDisconnect(DP9)

• oAbandon(DP10)

SSF to SCF (PGW 2200) OperationsThis section describes the INAP operations supported in PGW 2200 release 9.5(1).

Table 1 Operations Sent From the SSF to the SCF

Message Description

Activity Test Result (Response) This operation is used to check for the continued existence of a relationship between the SCF and SSF. If the relationship still exists, then the SSF responds. If no reply is received, then the SCF assumes that the SSF has failed and takes an appropriate action.

Apply Charging Report (ACR) This operation is used by the SSF to report charging related information to the SCF as requested by the SCF using the ApplyCharging operation.

Event Report BCSM (ERB) This operation is used to notify the SCF of a call related event previously requested by the SCF in an RequestReportBCSMEvent operation. The monitoring of more than one event can be requested with a RequestReportBCSMEvent operation. Each requested event is reported in a separate EventReportBCSM operation.

Initial Detection Point (IDP) This operation is sent by the SSF after detection of a TDP-R in the BCSM to request the SCF for instructions to complete the call.



Table 2 Operations Sent From the SCF to the SSF

Message Description

Activity Test This operation is used to check for the continued existence of a relationship between the SCF and SSF. If the relationship is still in existence, then the SSF will respond. If no reply is received, then the SCF will assume that the SSF has failed in some way and will take the appropriate action.

Apply Charging (AC) This operation is used for interacting from the SCF with the SSF charging mechanisms. The ApplyChargingReport operation provides the feedback from the SSF to the SCF.

Several connection configurations can be established during a call; ApplyCharging can be invoked at the beginning of each connection configuration for each party.

Collect Information (CI) This class 2 operation requests that the SSF perform the basic originating call processing actions that collect destination information from a calling party (normally associated with a RequestReportBCSMEvent operation to arm DP2 and to specify the number of digits to be collected).

Connect (CONN) This operation is used to request the SSF to connect the call to a specified destination.

Continue (CONT) This operation requests that the SSF proceed with call processing at the DP at which it previously suspended call processing to await SCF instructions. The SSF continues call processing without substituting new data from the SCF.

Disconnect Forward Connection (DFC) This operation is used to explicitly disconnect a connection to a resource (SRF) established previously with an EstablishTemporaryConnection operation. It is used for a forward disconnection from the SSF.

Establish Temporary Connection (ETC)

This operation is used to create a temporary connection between an initiating SSF and a SRF.

Furnish Charging Information (FCI) This operation is used to request the SSF to generate, register a call record, or include some information in the default call record. The registered call record is intended for offline charging of the call. The FCI operation can be invoked multiple times.

Release Call (RC) This operation is used to tear down (by the SCF) an existing call at any phase of the call for all parties involved in the call.

INAP Feature ModuleOperations and Parameters


Operations and ParametersThe following tables describe the supported parameters contained within the operations in Tables 1 and 2.

Note Parameters not listed against an operation are either not sent to the SCP or are discarded if received from the SCP.

Activity Test

Apply Charging

Request Report BCSM (RRBE) This operation is used to request the SSF to monitor for a call-related event (e.g., BCSM events such as busy or no-answer), then send a notification back to the SCF when the event is detected.

Send Charging Information (SCI) This operation instructs the SSF on the charging information to be sent by the SCF. The sending of charging information can either be by charge pulses or signalling or internal if SSF is located in the Local Exchange (LE). The SCI operation can be invoked on multiple times.

Table 2 Operations Sent From the SCF to the SSF (continued)

Message Description

Table 3 Activity Test

Parameter Value Notes

None N/A None

Table 4 Apply Charging


aChBillingChargingCharacteristics The content of this parameter is network operator specific.

Specifies the charging related information to be provided by the SSF and the conditions on which this information has to be reported back to the SCF via the ApplyChargingReport operation.

sendCalculationToSCPIndication TRUE or FALSE Indicates that ApplyChargingReport operations (at least one at the end of the connection configuration charging process) are expected from the SSF.



ApplyCharging Report

Collect Information

Connect

Table 5 ApplyCharging Report


CallResult The content of this parameter is network operator specific.

Provides the SCF with the charging related information previously requested using the ApplyCharging operation with its sendCalculationToSCPIndication parameter set to TRUE.

Table 6 Collect Information


None N/A Normally associated with a RequestReportBCSMEvent operation to arm DP2 and to specify the number of digits to be collected.

Table 7 Connect


destinationRoutingAddress Octet string encoded as defined in ETS-300-356-1

Contains the called party number to which the call is to be routed.

cutAndPaste Integer (0..22) Used by the SCF to instruct the SSF to delete (cut) a specified number of leading digits received from the calling party and paste the remaining dialed digits at the end of the digits supplied by the SCF in the destinationRoutingAddress.

callingPartyNumber Octet string encoded as defined in ETS-300-356-1

Used to provide an alternative to the callingPartyNumber supplied by the network.

callingPartysCategory 1 octet encoded as defined in ETS-300-356-1

Indicates the type of calling party (e.g., operator, pay phone, ordinary subscriber).

originalCalledPartyID Octet string encoded as defined in ETS-300-356-1

Carries the dialed digits if the call has met call forwarding on route to the SSP or is forwarded by the SCP.

redirectingPartyID Octet string encoded as defined in ETS-300-356-1

Indicates the directory number the call was redirected from.



Continue

Disconnect Forward Connection

ETC Establish Temporary Connection

redirectionInformation Octet string encoded as defined in ETS-300-356-1

Contains forwarding related information such as redirecting counter.

serviceInteractionIndicators The content is network operator specific.

Contains indicators sent from the SCP to the SSP for control of the network based services at the originating exchange and the destination exchange.

Table 8 Continue


None N/A None

Table 9 Disconnect Forward Connection


None N/A None

Table 10 ETC Establish Temporary Connection Parameters


AssistingSSPIPRouting Address

NQI=128

NOA= 3 (national)

NPI = 1 (ISDN)

Number Incomplete Indicator =0 (number complete)

Address signals = Routing Number

Mandatory

IVR address to connect call. One address per ICM instance is supported.

CorrelationID is appended to this address in the generic NIC for correlation of call at VRU with network request.

CorrelationID N/A Correlation Id can be used instead of appending to AssistingSSPIPRoutingAddress if required (requires customization for carrier).

SCF ID N/A Ignored

Table 7 Connect (continued)




Event Report BCSM

Extensions N/A Ignored

Service Interaction Indications

N/A Ignored

Table 11 Event Report BCSM


eventTypeBCSM 2 (collectedInfo), 4 (routeSelectFailure), 5 (oCalledPartyBusy) 6 (oNoAnswer)7 (oAnswer)9 (oDisconnect)10 (oAbandon)

Specifies the type of event being reported.

eventSpecificInformationBCSM For CollectedInfo contains the calledPartyNumber.

For AnalyzedInformation contains the calledPartyNumber.

For RouteSelectFailure contains the FailureCause, if available.

For O-CalledPartyBusy contains the BusyCause, if available.

For O-NoAnswer is empty.

For O-Answer is empty.

For O-Disconnect contains the releaseCause, if available.

Indicates the call related information specific to the event.

legID 1 (leg 1)2 (leg 2)

Indicates the party in the call for which the event is reported.

miscCallInfo monitorMode:1 (request (interrupted))2 (notification)

Indicates DP related information.

Table 10 ETC Establish Temporary Connection Parameters (continued)




FCI Furnish Charging Information

Initial Detection Point

Table 12 Furnish Charging Information


FCIBillingChargingCharacteristics The content is network operator specific.

Indicates billing and/or charging characteristics. The content is recorded in the CDR.

assistingSSPIPRoutingAddress Address signals Indicates the destination address of the SRF for assist procedure.

serviceInteractionIndicators The content is network operator specific.

Contains indicators sent from the SCP to the SSP for control of the network based services at the originating exchange and the destination exchange.

Table 13 Initial Detection Point


serviceKey Integer Identifies for the SCF, the requested IN service.

calledPartyNumber Octet string encoded as defined in ETS-300-356-1.

Contains the number used to identify the called party in the forward direction, for example, the called party number of ISUP.

callingPartyNumber Octet string encoded as defined in ETS-300-356-1.

Carries the calling party number to identify the calling party or the origin of the call.

callingPartysCategory 1 octet encoded as defined in ETS-300-356-1.

Indicates the type of calling party (e.g., operator, payphone, ordinary subscriber).

originalCalledPartyID Octet string encoded as defined in ETS-300-356-1.

Carries the dialed digits if the call has met call forwarding on route to the SSP.

forwardCallIndicators 2 octets encoded as defined in ETS-300-356-1.

Indicates whether the call is treated as a national or international call.

eventTypeBCSM 3 (analysedInformation) Indicates the armed BCSM DP event resulting i the InitialDP operation.

redirectingPartyID Octet string encoded as defined in ETS-300-356-1.

Indicates the directory number the call was redirected from.

redirectionInformation 2 octets encoded as defined in ETS-300-356-1.

Contains forwarding related information such as redirecting counter.

highlayerCompatibility Octet string encoded as defined in ETS-300-403-1.

Indicates the high layer compatibility type.



Request Report BCSM Event

Send Charging Information

Table 14 Request Report BCSM Event


eventTypeBCSM 2 (collectedInfo)4 (routeSelectFailure)5 (oCalledPartyBusy)6 (oNoAnswer)7 (oAnswer)9 (oDisconnect)10 (oAbandon)

Specifies the type of event of which a report is requested.

monitorMode 0 (interrupted)1 (notifyAndContinue)2 (transparent)

Indicates how the event is reported.

If the monitorMode is interrupted, the event is reported as a request.

If the monitorMode is notifyAndContinue, the event is reported as a notification.

If the monitorMode is transparent, the event is not reported.

legID 1 (leg 1)2 (leg 2)

Indicates the party in the call for which the event is reported.

dpSpecificCriteria

• numberOfDigits

• applicationTimer

numberOfDigits–Integer (1..255)

applicationTimer–Integer (0..2047)

Indicates information specific to the EDP to be armed.

numberOfDigits–indicates the number of digits to be collected by the SSF for the CollectedInfo event. If the indicated number of digits is collected, the SSF reports the event to the SCF.

applicationTimer–indicates the application timer for the NoAnswer event.

Table 15 Send Charging Information


sCIBillingChargingCharacteristics The content of this parameter is network operator specific.

Indicates billing and/or charging characteristics.

INAP Feature ModuleCall Flows


Call Flows

Typical Dialogue for INAP CallThe call flow below shows a typical dialogue for an INAP call involving charging operations.

1161

83

IAM

[DP3]

[DP7]

[DP9]

ISUP PGW SCP

ACM

ANM

REL

REL

InitialDp

ApplyCharging

FurnishChargingInformation

SendChargingInformation

RequestReportBCSMEvents

Connect

EventReportBCSM

EventReportBCSM

ApplyChargingReport

ReleaseCall

INAP Feature ModuleCall Flows


INAP Dialogue Involving ETC procedureThe following call flow shows an INAP call involving the Establish Temporary Connection procedure to connect the call to an SRF.

IAM

[DP3]

1161

84

[DP7]

ISUP PGW SCP

IAM[to SRF]

ANM

RLC

REL

[DP9]

REL

InitialDp

EstablishTemporaryConnection

DisconnectForwardConnection

PGW disconnects from SRF andawauts further instructions

ApplyCharging

FurnishChargingInformation

SendChargingInformation

ReleaseCall

ApplyChargingReport

RequestReportBCSMEvents

Connect

EventReportBCSM

EventReportBCSM

REL[SRF connection]

INAP Feature ModuleSupported Platforms


Supported PlatformsThe hardware platforms supported for the Cisco MGC software are described in the Release Notes for Cisco Media Gateway Controller Software Release 9.5(1).

Provisioning Exampleprov-add:APC:NAME="scp",DESC="SCP point code",NETADDR="0.111.2",NETIND=2 prov-add:SS7ROUTE:NAME="ss7r-scp",DESC="SS7 Route towards SCP",OPC="opc-pgw",DPC="scp",LNKSET="lnkset-1",PRI=1 prov-add:SS7SUBSYS:NAME="scp-ss7subs",DESC="SS7 Subsystem for SCP",SVC="scp",PRI=1,MATEDAPC="",LOCALSSN=12,PROTO="SS7-ITU",STPSCPIND=4,TRANSPROTO="SCCP",OPC="opc-pgw",SUAKEY="",REMOTESSN=12 numan-add:resultset:custgrpid="PSTN",name="INservice1"numan-add:resulttable:custgrpid="PSTN",name="INtrigger",resulttype="IN_TRIGGER",dw1="24",dw2="4",dw3="0",dw4="6",setname="INservice1"numan-add:resulttable:custgrpid="PSTN",name="Servicekey1",resulttype="IN_SERVICE_KEY",dw1="1",setname="INservice1"numan-add:resultset:custgrpid="PSTN",name="INservice2"numan-add:resulttable:custgrpid="PSTN",name="INtrigger",resulttype="IN_TRIGGER",dw1="24",dw2="4",dw3="0",dw4="6",setname="INservice2"numan-add:resulttable:custgrpid="PSTN",name="Servicekey2",resulttype="IN_SERVICE_KEY",dw1="2",setname="INservice2"numan-add:resultset:custgrpid="PSTN",name="INservice3"numan-add:resulttable:custgrpid="PSTN",name="INtrigger",resulttype="IN_TRIGGER",dw1="24",dw2="4",dw3="0",dw4="6",setname="INservice3"numan-add:resulttable:custgrpid="PSTN",name="Servicekey3",resulttype="IN_SERVICE_KEY",dw1="3",setname="INservice3"numan-add:bdigtree:custgrpid="PSTN",callside="originating",digitstring="1234561",setname="INservice1"numan-add:bdigtree:custgrpid="PSTN",callside="originating",digitstring="1234562",setname="INservice2"numan-add:bdigtree:custgrpid="PSTN",callside="originating",digitstring="1234563",setname="INservice3"

Provisionable Properties

Note The new resulttype (IN_SERVICE_KEY) has been added. DW1 is used to provision the IN service key to be used when IN triggering is initiated towards SCP.

Provisionable Properties

Property Modified value takes effect without restart

AOCInvokeType Yes

AOCDefaultTariffId Yes

INAP Feature ModuleRelated Documents


Related DocumentsThis document contains information that is related to this feature. The documents that contain additional information related to the Cisco Media Gateway Controller (MGC) are at the following url:

http://www.cisco.com/en/US/products/hw/vcallcon/ps2027/tsd_products_support_series_home.html

Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation at

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

© 2007 Cisco Systems, Inc. All rights reserved.

CCVP, the Cisco logo, and Welcome to the Human Network are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn isa service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the CiscoCertified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity,Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS,iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networkers,Networking Academy, Network Registrar, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient,and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply apartnership relationship between Cisco and any other company. (0711R)

http://www.cisco.com/en/US/products/hw/vcallcon/ps2027/tsd_products_support_series_home.html

INAP Feature ModuleObtaining Documentation, Obtaining Support, and Security Guidelines
