826 mml controlled call control parameters.pdf

FEATURE 826: MML ControlledCall Control Parameters

DN03303769Issue 3-0 en

# Nokia Siemens Networks 1 (85)

MSCDOCM14NEDFDMSC/HLR, Rel. M14.0, Feature Documentation,v. 6

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended for theuse of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted inany form or means without the prior written permission of Nokia Siemens Networks. Thedocumentation has been prepared to be used by professional and properly trained personnel,and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomescustomer comments as part of the process of continuous development and improvement of thedocumentation.

The information or statements given in this documentation concerning the suitability, capacity, orperformance of the mentioned hardware or software products are given “as is” and all liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia Siemens Networks and the customer. However,Nokia Siemens Networks has made all reasonable efforts to ensure that the instructionscontained in the document are adequate and free of material errors and omissions. NokiaSiemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues whichmay not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NOEVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUTNOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESSOPPORTUNITY OR DATA, THAT MAYARISE FROM THE USE OF THIS DOCUMENT OR THEINFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights andother intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark ofNokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners,and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2008. All rights reserved.

2 (85) # Nokia Siemens Networks DN03303769Issue 3-0 en

FEATURE 826: MML Controlled Call Control Parameters

Contents

Contents 3

List of tables 4

List of figures 5

1 Introduction 7

2 Benefits for the operator 9

3 Description of the feature 113.1 Requirements for using the feature 113.1.1 Software 113.1.2 Hardware 113.1.3 Products 113.2 Functionality 113.2.1 General 113.2.2 Files 143.2.3 Parameters 143.2.4 Statistics 143.2.5 Charging 143.3 Capacity 143.4 Restrictions 143.5 Related and interworking features 143.6 Compliance 14

4 Interfaces 154.1 Operator interfaces 154.1.1 MMLs 154.1.1.1 Incoming call control parameters 154.1.1.2 Outgoing call control parameters 494.1.2 Alarms 784.2 Subscriber interfaces 784.3 External interfaces 78

5 Main changes in the feature 79

Glossary 81

References 84



Contents

List of tables



List of figures

Figure 1. Trunk- and PBX-originated call 12

Figure 2. Mobile-originated call 12

Figure 3. Trunk- and PBX-terminated call 12

Figure 4. Mobile-terminated call 13



List of figures

1 Introduction

In call control parameters, you can define circuit group and route-specificdata used by the call control programs. One outgoing parameter set andone incoming set must be defined per each route or circuit group.

The incoming call control parameter sets are stored to the Incoming CallControl Parameter File (IP0FIL), the outgoing parameter sets to theOutgoing Call Control Parameter File (OP0FIL).



Introduction

2 Benefits for the operator

This feature enables you to define circuit group and route-specific dataused by the call control programs.



Benefits for the operator

3 Description of the feature

3.1 Requirements for using the feature

3.1.1 Software

This feature has no special requirements for software.

3.1.2 Hardware

This feature has no special requirements for hardware.

3.1.3 Products

This feature functions both in i-series products and the subrack products.The functionality is the same.

3.2 Functionality

3.2.1 General

In call control parameters, you can define circuit group and route-specificdata used by the call control programs. One outgoing parameter set andone incoming set must be defined per each route or circuit group.

The incoming call control parameter sets are stored to the Incoming CallControl Parameter File (IP0FIL), the outgoing parameter sets to theOutgoing Call Control Parameter File (OP0FIL). The effect of theparameters on the handling of the call is illustrated below:



Description of the feature

Figure 1. Trunk- and PBX-originated call

Figure 2. Mobile-originated call

Figure 3. Trunk- and PBX-terminated call

CMECGR INSIGN

IP0FIL

parameters

Inc. CGR No.

insignindex

ccparindex

INSIGN

IP0FIL

parameters

insignindex

ccparindex

fixedfixed

OUSIGN

OP0FIL

parameters

ccparindex

ousignindex

OUTROU

parameters

routeindex

RTASEB RBCSEB



Figure 4. Mobile-terminated call

In special cases, when there is no incoming circuit group or outgoing routefor the call, call control uses special incoming or outgoing parameter setsreferenced by a fixed pointer:

. inter-MSC handover

. terminating PAD call

. forwarded call

. external IP

. CCBS recall

. SSAP connection

The call control parameters are handled by the commands of the CPcommand group. For more information, see Call Control ParametersHandling, CP Command Group.

The Incoming Call Control parameters file (IP0FIL) is a one-dimensionaltable with bitmap and it contains circuit group dependent parameters. Youcan change the values of these parameters through the Call ControlParameters Handling MML, CP Command Group. The counter process,ZCPPRB, writes the changed data to IP0FIL. The incoming call control,ICxPRB, reads parameters from IP0FIL.

The Outgoing Call Control parameters file (OP0FI), is also a one-dimensional table with bitmap and it contains circuit group dependentparameters. You can change the values of these parameters through theCall Control Parameters Handling MML, CP Command Group. Thecounter process, ZCPPRB, writes the changed data to OP0FIL. The callcontrol, ICxPRB and OCxPRB reads parameters from OP0FIL.

OUSIGN

OP0FIL

parameters

ousignindex

ccparindex

fixedfixed



Description of the feature

3.2.2 Files

This feature does not affect any files that are directly visible to the operator.

3.2.3 Parameters

The related parameters are discussed in the MMLs chapter of thisdocument.

3.2.4 Statistics

This feature has no effects on statistics.

3.2.5 Charging

This feature has no effects on charging.

3.3 Capacity

This feature has no effects on capacity.

3.4 Restrictions

There are no restrictions relevant to the functionality of this feature.

3.5 Related and interworking features

The related features are listed in the References chapter.

3.6 Compliance

This feature is Nokia-specific.



4 Interfaces

4.1 Operator interfaces

4.1.1 MMLs

4.1.1.1 Incoming call control parameters

ACMF

1. Description

ACM free

ACMFThis parameter determines whether the 'free call' indicator inthe Address Complete Message (ACM) is supported byincoming signalling. The possible values are:

Y free call indicated by ACM acceptable

N free call indicated by ACM not acceptable

The default value is N.

2. MML command example on how to modify the parameter

ZCPM:NCCP=<name of parameter set>::::ACMF=Y;

3. Related parameters. ACMF on the outgoing side.

4. Additional information



Interfaces

If the MSC defines a call to be free the ACMF parameter determinesif the free call indication is sent in an ACM message to the precedingnetwork element. The MSC can define call to be free by ANSWERor/and ACM or/and from charging analysis.

ACOL

1. Description

Additional connected line identity <optional>

ACOLThis parameter indicates whether COL or additional COL ispresented to the calling subscriber when additional COL isavailable and the calling subscriber is using the overridecapability (this is an originating-MSC function). The possiblevalues are:

Y additional COL is presented

N COL is presented

The default value is Y.

This parameter is optional.


ZCPM:NCCP=<name of parameter set>:::::::ACOL=N;


The parameter is used in mobile-originated calls.

The parameter is used in connection with Feature 628: ConnectedLine Identification Services.

ANMF

1. Description

ANSWER free

ANMFThis parameter determines whether the 'free call' indicator inthe answer message is supported by incoming signalling. Thepossible values are:



Y free call indicated by ANM acceptable

N free call indicated by ANM not acceptable



ZCPM:NCCP=<name of parameter set>::::ANMF=Y;

3. Related parameters. ANMF on the outgoing side.


If the MSC defines a call to be free the ANMF parameter determinesif the free call indication is sent in an ANSWER message to thepreceding network element. The MSC can define call to be free byANSWER or/and ACM or/and from charging analysis.

ASKCLI

1. Description

get calling line identity before routing

ASKCLIThis parameter determines whether Calling Line Identity (CLI)is inquired from the preceding exchange, in the set-up phaseof the call, if the call control does not have it. The possiblevalues are:

Y CLI is inquired

N CLI is not inquired

The default value is NO.


ZCPM:NCCP=<name of parameter set>:::ASKCLI=Y;

3. Related parameters. NOASK (incoming call control parameter set): call control can

be prohibited from requesting the calling line identity. NOASKoverrides ASKCLI.


If the value is N, CLI can still be required at a later point (terminatingPBX or BSSAP).



Interfaces

ASKCPC

1. Description

get calling party category before routing

ASKCPCThis parameter determines whether call control inquires thecategory of subscriber A before routing. The possible valuesare:

Y category of subscriber A inquired before routing

N category of subscriber A not inquired before routing



ZCPM:NCCP=<name of parameter set>:::ASKCPC=Y;

CALLNS

1. Description

Calling number sending to charging and statistics <optional>

CALLNSThis parameter determines whether the CLI of PBX is sent tothe charging and statistics. The possible values are:

Y calling number is sent to charging and statistics

N calling number is not sent to charging and statistics




ZCPM:NCCP=<name of parameter set>:::CALLNS=Y;

3. Related parameters. CLIS: the value of CLIS determines whether screening is

carried out also for calling line identification and call-backpurposes. If the value of CALLNS is Y, but the value of CLIS isN, screening is carried out only for charging and statistics.




The parameter is used in PBX-originating calls.

To ensure CLI screening to function properly, define the call numberand subnumber range. The call number is created with the SDCcommand of the Digital Branch Exchange Handling MML. Thesubnumber range is defined with the SAC command of the DigitalBranch Exchange Supplementary Services MML.

The parameter is used in connection with Feature 227: Primary RateAccess.

CDBTRIG

1. Description

Originating side trigger key <optional>

CDBTRIGThis parameter indicates whether triggering in a Call DropBack call to IN services based on an originating-side triggerkey (a trigger key obtained from the VLR, incoming circuitgroup or PBX data) is allowed. The possible values are:

Y originating-side triggering in CDB is allowed

N originating-side triggering in CDB is not allowed

INTTONTON is used, if the connected number is an internationalnumber

BOTHTONTON is used, if the connected number is a national orinternational number




ZCPM:NCCP=<name of parameter set>:::::::CDBTRIG=Y;


The parameter is used in connection with Feature 1093: AdvancedCall Drop Back for VMS Interface.



Interfaces

CDR

1. Description

CDR generation

CDRThis parameter indicates whether a Charging Record (CDR) isgenerated. The possible values are:

Y CDR is generated

N CDR is not generated



ZCPM:NCCP=<name of parameter set>:::::::CDR=Y;

3. Related parameters. VPS (incoming call control parameters)


Used in trunk and PBX-originated calls.

The value of this parameter has an effect also on the mobileaccounting part of the trunk circuit charging. That is, if the CDRparameter has value 'N' all the charging is counted into the 'OWN…'-counters. If the CDR parameter has 'Y' the charging is countedinto their own counters in question, that is, into 'VPS …'-counters incase of VPS-originated/terminated calls, into 'PSTN …'-counters incase PSTN-originated/terminated calls and into 'OWN …'-countersin case of PBX-originated/terminated calls.

If the value is N, all charging data is collected in OWN counter filesinstead of call type-specific files (for example, VPSO / POC / PBXO).

The parameter is relevant only if the call types in which CDRs aregenerated have been defined in the CDR generation parameter(defined by theGTM command of the Detailed Charging HandlingMML).

CFO

1. Description

Call forwarding override



CFOFor every incoming circuit, it is possible to determine whethercall forwarding on that circuit is allowed or not. The possiblevalues are:

Y request for Call Forwarding Override is set

N request for Call Forwarding Override is not set



ZCPM:NCCP=<name of parameter set>::::CFO=Y;


In case of MOC calls the parameter has no effect.

The parameter is used in connection with Feature 306: CallForwarding Override.

CHRNI

1. Description

Charge number indicator

CHRNIThis parameter indicates whether the charge number definedfor a circuit group is used as the charge number for the call.The possible values are:

Y circuit group-specific charge number used as a call-specific charge number

N calling party number used as a call-specific chargenumber



ZCPM:NCCP=<name of parameter set>:::CHRNI=Y;

3. Related parameters. OLI (Incoming call control parameters): The Originating Line

Information parameter is relevant only if the value of CHRNI isY.




Interfaces


The parameter is used in connection with Feature 840: Primary RateAccess (PBX: CLIP Charging) / 23B+D.

CIPAL

1. Description

Carrier identification parameter is allowed <optional>

CIPALThis parameter determines whether the ANSI ISUP CarrierIdentification Parameter (CIP) is allowed in the Initial AddressMessage (IAM). The possible values are:

Y ANSI ISUP carrier identification parameter allowed inIAM

N ANSI ISUP carrier identification parameter not allowed inIAM




ZCPM:NCCP=<name of parameter set>::::CIPAL=Y;

3. Related parameters. Has effect only when TSAL is allowed.


If this value is used and the IAM includes an ANSI ISUP CIP, the callis cleared with clear code 0827 - CARRIER IDENTIFICATION NOTALLOWED FROM INCOMING CIRCUIT.

CLIA

1. Description

calling line identity asking

CLIAThe parameter determines whether or not calling line identity isinquired before the HLR enquiry if it has not been received inthe call set-up. The possible values are:



Y CLI inquired before HLR enquiry

N CLI not inquired before HLR enquiry



ZCPM:NCCP=<name of parameter set>:::CLIA=Y;

3. Related parameters. NOASK. ASKCLI. INQLOC: If the value of CLIA is Y, CLI is enquired after an 'n'

number of digits of the called number have been received; 'n'is defined in the INQLOC parameter.

The NOASK parameter overrides CLIA.

CLIRAON

1. Description

CLIR override for AON PSTN <optional>

CLIRAONWith the help of this optional parameter you can override theCLIR indication in PSTN-originated call if the called partysubscriber has CLI-Inquiry-ServiceNode service (used to call'AON service' as well). The possible values are:

Y CLIR indication is overriden for AON subscribers

N CLIR indication is not overriden for AON subscribers




ZCPM:NCCP=<name of parameter set>:::CLIRAON=Y;


The parameter is used in connection with Feature 1547: SN andsubscription based CLI inquiry.



Interfaces

CLIS

1. Description

calling line identity screening

CLISThis parameter defines whether the correctness of calling lineidentity is checked. The possible values are:

Y screening is done

N screening is not done



ZCPM:NCCP=<name of parameter set>:::CLIS=N;

3. Related parameters. CLIT determines whether or not the screening should be done

for charging and statistics.

If the value of CLIS is N, but the value of CLIT is Y, screening iscarried out for charging and statistics.


This parameter is used in PBX-originated calls.

To get the CLI screening functionality to work properly the callnumber and subnumber range must be defined. The call number iscreated with the SDC command and the subnumber space isdefined with the SAC command.

The parameter is used in connection with Feature 227: Primary RateAccess.

CLIT

1. Description

calling line identity screening for statistics

CLITThis parameter determines whether the CLI screening is donefor statistics. The possible values are:



Y CLI screening is done for statistics

N CLI screening is not done for statistics



ZCPM:NCCP=<name of parameter set>:CLIT=Y;

3. Related parameters. CLIS: determines whether or not the screening should be done

for identification and call back.


This parameter has an effect in PBX-originating calls.

To get the CLI screening functionality to work properly the callnumber and subnumber range must be defined. The call number iscreated with the SDC command and the subnumber space isdefined with the SAC command.

CONNF

1. Description

connected party number format

CONNFThis parameter determines the format of the connected partynumber, which is sent to the incoming signalling if it has beenrequested in IAM. The possible values are:

NO not specified

INTLinternational

PREFNATpreferred national

FORCNATforced national

The default value is PREFNAT.


ZCPM:NCCP=<name of parameter set>:::::::CONNF=INT;



Interfaces

3. Related parameters. If the value is 'NO' then the value of the CONNPR parameter

has no effect.


Connected Number is sent back to the incoming signalling in ACMand ANMmessages when a call terminates to a mobile subscriber orto PBX.

Exceptions:. If CONNF=NO, no Connected Number is sent.. In case of ISUP incoming signalling the Connected Number is

sent in an ACM or ANM message only if it has been requestedin a IAM message.

. In case of ISUP-2 incoming signalling Connected Number issent only in ANM message and only if it has been requested inIAM message.

CONNPR

1. Description

connected party number presentation restriction

CONNPRThis parameter determines the indicator of the connectedparty number presentation for the incoming signalling. Thepossible values are:

PASSpassed

ALLOWallowed

RESTRrestricted

The default value is RESTR.


ZCPM:NCCP=<name of parameter set>:::::::CONNPR=RESTR;

3. Related parameters. If the value of the CONNF parameter is 'NO', the value of the

CONNPR parameter has no effect.



CPGF

1. Description

CPG free allowed

CPGFThis parameter determines whether the 'free call' indicator inthe Call Progress Message (CPG) is supported by incomingsignalling. The possible values are:

Y free call indicated by CPG is acceptable

N free call indicated by CPG not acceptable



ZCPM:NCCP=<name of parameter set>::::CPGF=Y;

3. Related parameters. CPGF on the outgoing side.


If the MSC defines a call to be free, the CPGF parameter determinesif the free call indication is sent in a CPG message to the precedingnetwork element. The MSC can define a call to be free by ANSWERor/and ACM or/and from charging analysis.

CUGISUP

1. Description

CUG ISUP indicator

CUGISUPThis parameter controls the handling of a call case-specificISUP Preference Indicator (IPI) in mobile-originating and PBX-originating CUG calls. The possible values are:

NO ISUP indicator not modified

NOTREQoutgoing ISUP route not required



Interfaces

PREFERoutgoing ISUP route preferred

REQoutgoing ISUP route required



ZCPM:NCCP=<name of parameter set>:::::::CUGISUP=PREFER;

3. Related parameters. OVISUP Override ISUP indicator parameter sets ISUP

preference indicator of all outgoing calls to the given value.. ISUP64 parameter sets ISUP preference indicator to the given

value in case of call with transmission medium requirement 64kbit/s unrestricted.

Note

If several ISUP requirement conditions for IPI are valid during a call,parameter value 'REQ' has the highest priority and 'NO' has the lowest.


If the value is NOTREQ, the type of the outgoing signalling can be,for example, TUP or R2. If the value is PREFER and no outgoingISUP routes are available, the call is routed via another type of route(for example, TUP or R2). If the value is REQ and no outgoing ISUProutes are available, the call is cleared.

If several ISUP requirement conditions for IPI have been defined forthe same call, parameter value REQ has the highest priority and NOhas the lowest. For example: if CUGISUP = PREFER and ISUP64 =REQ, the preference indicator used for an incoming CUG call withTMR = 64 kbit/s is REQ.

The transfer capability of CUG information for a route is defined bythe RRM command of the Route Handling MML (FCL parameter ). Aroute, which does not have the CUG facility cannot transfer CUGinformation: a call made by a CUG subscriber can be directed to thiskind of a route only if the subscriber has CUG with outgoing access.

A route to the BSC is always treated as an outgoing ISUP route.



ECINFO

1. Description

Echo canceller information

ECINFOThis parameter defines whether the sending of connect-echo-canceller information to the network is allowed. The possiblevalues are:

Y connect-echo-canceller information is allowed to be sentto the network

N connect-echo-canceller information is not allowed to besent to the network



ZCPM:NCCP=<name of parameter set>::::ECINFO=Y;

3. Related parameters. ECINFO parameter on the outgoing side.


The parameter is used in connection with Feature 1146: SSP EchoCancelling and Conference Bridging Enhancements.

FECHO

1. Description

forced connection of echo canceller

FECHOThis parameter determines whether the outgoing echocanceller is forcibly connected, if an echo canceller has beenequipped in the incoming circuit. The possible values are:

Y echo canceller forcibly connected

N echo canceller not forcibly connected





Interfaces

ZCPM:NCCP=<name of parameter set>:::::::FECHO=Y;

3. Related parameters. FECHO in outgoing call control parameters.


This parameter has effects only if the echo canceller is equipped tothe incoming circuit.

In case of Data call this parameter does not have an effect.

FIXRCI

1. Description

override routing control indicator

FIXRCIThis parameter controls alternative routing and continuousretry of circuit hunting. This parameter controls alternativerouting depending on the incoming ciruit group The possiblevalues are:

0 alternative routing allowed, continuous retry allowed

1 alternative routing barred, continuous retry allowed

2 alternative routing allowed, continuous retry barred

3 alternative routing barred, continuous retry barred

4 alternative routing allowed once, continuous retryallowed

5 alternative routing allowed once, continuous retry barred

F unused

Value 2 is used as routing control information.


ZCPM:NCCP=<name of parameter set>:FIXRCI=0;


Emergency calls use FIXRCI = 0.

GSMC

1. Description

gsmc t bcsm allowed



GSMCWith this parameter, you can determine whether the trigger keyfor the gmsc t-bcsm is returned, which means that the HLRenquiry is performed in two phases, or whether the returnednumber is the roaming number, in which case the HLR enquiryis performed in the normal way (that is, in one phase). Thepossible values are:

Y trigger key for gmsc t-bcsm returned

N roaming number returned



ZCPM:NCCP=<name of parameter set>:GSMC=Y;


In a mobile-terminating call, the HLR checks whether the gatewayMSC is acting as a service switching point. If it does, and there is atrigger key defined for the subscriber, the HLR does not normallyfetch the mobile subscriber roaming number but returns the triggerkey to the gmsc for a possible Service Control Point (SCP) enquiry.

HOCDR

1. Description

Handover Ticket Generation

HOCDRThis parameter indicates whether CDR is generated in anMTC/PTC/POC handover. The possible values are:

Y HOCDR is generated

N HOCDR is not generated



ZCPM:NCCP=<name of parameter set>::::::::HOCDR=Y;

3. Related parameters. HOCDR on the outgoing side.



Interfaces

INQLOC

1. Description

inquiry location

The parameter determines the number of received digits of thecalled party number after which calling line identity is enquired. It canhave values between 0 and 31.


ZCPM:NCCP=<name of parameter set>::INQLOC=5;

3. Related parameters. ASKCLI (incoming call control parameters): must be defined

with value=Y to make this parameter relevant.. NOASK (incoming call control parameters): overrides the

functionality of these two parameters.. CLIA (incoming call control parameters): determines whether

the calling line identity is inquired before the HLR enquiry, if ithas not been received in call set-up. If the value is Y, CLI isenquired after an n number of digits of the called number havebeen received; n is defined in the INQLOC parameter.


The parameter is used only in R2 signalling.

ISUP64

1. Description

64kbit ISUP indicator

ISUP64Handling of the call case-specific ISUP Preference Indicator(IPI). If this parameter is set and transmission mediumrequirement of an incoming call is 64 kbit/s unrestricted, theoriginal ISUP preference indicator is modified to the givenvalue.


NOTREQOutgoing ISUP-route is not required, it can be any type.



PREFEROutgoing ISUP-route is preferred.

REQOutgoing ISUP-route is required.


ZCPM:NCCP=<name of parameter set>:::::::ISUP64=REQ;

3. Related parameters. OVISUP: Override ISUP indicator parameter sets ISUP

preference indicator of all outgoing calls to the given value.. CUGISUP: sets ISUP preference indicator to the given value

in case of CUG call.

Note

If several ISUP requirement conditions for IPI are valid during a call, the'REQ'parameter value has the highest priority and 'NO' has the lowest.For example, an incoming CUG call with TMR=64 kbit/s andCUGSUP=PREFER; ISUP64=REQ. In this case the used ISUPpreference indicator is REQ, with the highest priority.


The parameter is used in mobile- and PBX-originated calls.

If NOTREQ Calls to TUP and R2 routes succeed.

If PREFER First the MSC tries to route calls through ISUProute. If outgoing ISUP route is not found, call isrouted through other type of route, for example,TUP or R2. 'Outgoing ISUP-route preferred' isdefault for all mobile originated calls.

If REQ The MSC tries to route calls through outgoingISUP route. If there is no ISUP route, the callfails. Route to the BSC is always handled as anoutgoing ISUP route.

ISVERS

1. Description

in signalling reference to the SCF



Interfaces

ISVERS This parameter indicates the version of theoutgoing signalling. The value can range from 0to 255.

The default value is 0.


ZCPM:NCCP=<name of parameter set>:::::::ISVERS=0;


It can be used only in BSSAP, TUP, NUP, ISUP, DPNSS, DSS1, R2,and PAD connections.

The parameter is used in connection with Feature 739: Core INAPCS-1 v3.

MODCFC

1. Description

modify call forwarding counter

MODCFCThis parameter determines whether the call forwardingcounter is modified. The possible values are:

Y call forwarding counter is modified

N call forwarding counter isnot modified



ZCPM:NCCP=<name of parameter set>:RESGR=1:::::MODCFC=Y;

3. Related parameters. The new counter value is given in the NEWCFC parameter.


The parameter is used in connection with Feature 319: Support forMultiple Call Forwardings.



NATCLI

1. Description

use national default CLI

NATCLIThis parameter defines whether to use the national defaultcalling line identity when the actual CLI is not available. Thepossible values are:

Y national default CLI used when actual CLI is notavailable

N national default CLI not used when actual CLI is notavailable


ZCPM:NCCP=<name of parameter set>:NATCLI=Y;

3. Related parameters

This parameter also requires the activation of NATCLI in outgoingcall control parameters.. NOASK


Situation where the actual CLI is not available:. CLI is not received in the setup message (like in R2 signalling)

AND. NOASK parameter in incoming call control parameters is

activated, so CLI cannot be inquired OR. CLI is not received (not available information) when inquired. The parameter has effect only on outgoing IAM.

NCLIC

1. Description

no calling line identity conversion

NCLICThis parameter determines whether or not the conversion ofcalling line identity is made. The possible values are:



Interfaces

Y calling line identity is not converted

N calling line identity is converted



ZCPM:NCCP=<name of parameter set>:NCLIC=Y;


If NCLIC = Y, no CLI conversion is done, but CLI is formattedaccording to the instructions of the parameters in outgoing callcontrol parameter set.

If NCLIC = N, CLI is converted according to the instructions of theCLI conversion.

The parameter is used in connection with Feature 827: CLI HandlingImprovement.

NEWCFC

1. Description

new call forwarding counter

NEWCFCThis parameter determines a new value (0...5) for the callforwarding counter. The call control sets this value only if theMODCFC parameter has been set.

NEWCFC0...5


Note

'0' value means that all call forwarding data is zero.


ZCPM:NCCP=<name of parameter set>:RESGR=1:::::NEWCFC=3;



3. Related parameters. The parameter has meaning only when the value of MODCFC

is Y.


The parameter is used in connection with Feature 319: Support forMultiple Call Forwardings.

NOANM

1. Description

no answer message

NOANMThis parameter determines whether an answer message issent after a prompt and collect information operation has beenreceived from the Service Control Point (SCP). The possiblevalues are:

Y no answer message sent after prompt and collectoperation

N answer message sent after prompt and collect operation



ZCPM:NCCP=<name of parameter set>::::NOANM=Y;


This parameter defines if 'prompt and collect information operation'is chargeable or not.

The parameter is relevant only in BSSAP and ANSI ISUP signalling.


NOASK

1. Description

calling line identity request prohibited



Interfaces

NOASKWith this parameter, the call control can be prohibited fromrequesting the Calling Line Identity (CLI). The possible valuesare:

Y requesting of CLI prohibited

N requesting of CLI not prohibited



ZCPM:NCCP=<name of parameter set>:::NOASK=Y;

3. Related parameters. ASKCLI. CLIA. ASKCPC. INQLOC

If it is set, this parameter overwrites ASKCLI and CLIA.

OLI

1. Description

Originating line information

OLIThis parameter defines the originating line information. Thepossible values are:

POTSplain old telephone service

MULTIPARTYmultiparty line

ANIFAILANI failure

STATLEVELstation level rating

OPERREQspecial operator handling required

AIODautomatic identified outward dialing listed DN sent

DBACCESScoin or non-coin on calls using database access



SERV800800 service call

COINcoin

BLANKintercept blank

TROUBLEintercept trouble

REGULARintercept regular

TELCOOPERtelco-operator-handled call

CELLTYPE1cellular service (type 1)-cellular carrier identified

CELLTYPE2cellular service (type 2)-mobile DN identified

CELLROAMcellular service (roaming)

PRIVPAYprivate paystations

VIRTUALNWaccess to private virtual network types of service

The default value is POTS.


ZCPM:NCCP=<name of parameter set>::::OLI=PRIVPAY;

3. Related parameters. CHRNI (Incoming call control parameters): the parameter OLI

is relevant only if the value of CHRNI is Y.



The parameter is used in connection with Feature 234: Completionof Calls to Busy Subscribers (CCBS) and Feature 840: Primary RateAccess (PBX: CLIP Charging) / 23B+D.

OMITCOL

1. Description

Omitting connected line identity <optional>



Interfaces

OMITCOLThis parameter indicates whether COL is sent to theoriginating exchange. The possible values are:

Y COL is not sent to the originating exchange

N COL is sent to the originating exchange

IFPIRECOL is not sent, if the connected subscriber hasactivated COLR (the PI is restricted)




ZCPM:NCCP=<name of parameter set>:::::::OMITCOL=IFPIRE;


The parameter is relevant only in trunk-originating calls.


OVISUP

1. Description

Override ISUP Indicator

OVISUPThis parameter controls the handling of a call case-specificISUP Preference Indicator (IPI) in mobile-originating and PBX-originating calls. The possible values are:


NOTREQoutgoing ISUP route not required

PREFERoutgoing ISUP route preferred

REQoutgoing ISUP route required





ZCPM:NCCP=<name of parameter set>:::::::OVISUP=NOTREQ;

3. Related parameters. CUGISUP parameter sets ISUP preference indicator to the

given value in case of a CUG call.. ISUP64 parameter sets ISUP preference indicator to the given

value in case of a call with transmission medium requirement64 kbit/s unrestricted.

Note

If several ISUP requirement conditions for IPI are valid during a call,parameter value 'REQ' has the highest priority and 'NO' has the lowest.


If the value is NOTREQ, the type of the outgoing signalling can be,for example, TUP or R2. If the value is PREFER and no outgoingISUP routes are available, the call is routed through another type ofroute (for example, TUP or R2). If the value is REQ and no outgoingISUP routes are available, the call is cleared.

If several ISUP requirement conditions for IPI have been defined forthe same call, parameter value REQ has the highest priority and NOhas the lowest. For example: If OVISUP = PREFER and ISUP64 =REQ, the preference indicator used for an incoming call with TMR =64 kbit/s is REQ.

A route to the BSC is always treated as an outgoing ISUP route.

PREACM

1. Description

Premature (that is, early) ACM

PREACMThis parameter determines whether the call control sends apremature Address Complete Message (ACM) when the callsetup lasts too long. The possible values are:

Y premature ACM sent by call control

N premature ACM not sent by call control




Interfaces


ZCPM:NCCP=<name of parameter set>:PREACM=Y;

3. Related parameters

This parameter also requires the activation of NATCLI in outgoingcall control parameters.


Timer value is set with the ZCT command, PAT parameter

Premature ACM is sent when PAT timer expires.

PREVTMR

1. Description

Long paging preventive timer

PREVTMR This parameter determines the value of thelong paging guard timer.

If the bearer establishment is delayed interminating MSC server until paging responseis received from the mobile, there is a likelihoodthat the intermediate (G)MSC server canrelease the call. This is because the COT timerexpires before the paging response is receivedin the case of long paging. To support thepossibility of continuing call set-up after asuccessful long paging, a new guard timer isintroduced in the terminating MSC server.

If the guard timer expires, the network sidebearer establishment is started in theterminating MSC server, this way the expiry ofCOT timers in the preceding servers can beavoided.

The value can be 1-14 (in seconds).



ZCPM:NCCP=<name of parameter set>:::PREVTMR=13;




The parameter has meaning only if the call control signalling usedtowards the preceding server is BICC or SIP.

PROG

1. Description

send progress message backward (M11, M12)

CLIAThis parameter indicates whether the backward progressmessage is used. The possible values are:

Y backward progress message is sent

N backward progress message is not sent



ZCPM:NCCP=BSSAP::::PROG=Y;


A backward progress message can be used to reset the mobile timerT310, which defines the limit to alerting or connecting time. It isrelevant in mobile-originating calls in which the network cannot sendthe answer message (for example, in a free call to the emergencycentre).

RABER

1. Description

Late RAB assignment in emergency call

RABERThis parameter determines whether the RAB assignment islate in anemergency call, that is, assignment goes onseparately from call proceeding. The possible values are:

Y late RAB assignment in emergency call

N no late RAB assignment in emergency call




Interfaces


ZCPM:NCCP=<name of parameter set>:::RABER=Y;


The parameter is used only in the MSC server.

RABIU

1. Description

Early RAB assignment in IU call

RABIUThis parameter determines whether RAB assignment is earlyin IU call, that is, assignment is done right after the callproceeding phase. The possible values are:

Y early RAB assignment in IU call

N no early RAB assignment in IU call



ZCPM:NCCP=<name of parameter set>:::RABIU=Y;



RABSERV

1. Description

Late RAB assignment in service (group) call

RABSERVThis parameter determines whether RAB assignment is late inservice/service group call, that is, assignment goes onseparately from call proceeding. The possible values are:

Y late RAB assignment in service (group) call

N no late RAB assignment in service (group) call





ZCPM:NCCP=<name of parameter set>:::RABSERV=Y;



REROU

1. Description

call rerouting point

REROUThis parameter determines whether the call is rerouted when acall drop back indication is received from the outgoingnetwork. The possible values are:

Y call is rerouted if call drop back received

N call is not rerouted if call drop back received


ZCPM:NCCP=<name of parameter set>:REROU=Y;


The parameter is used in connection with Feature 401: Call DropBack and Feature 1093: Advanced Call Drop Back for VMSInterface.

SANN

1. Description

special announcement handling

SANNThis parameter indicates whether an announcement is givenwhen announcement ability or inability information is receivedfrom the preceding exchange. The possible values are:



Interfaces

NOANNannouncement is not given even if the announcementinability of the preceding exchange has been indicated insignalling

ANNannouncement is given even if the announcement abilityof the preceding exchange has been indicated insignalling

NORMannouncement is given according to the announcementability of the preceding exchange information given insignalling

The default value is NORM.


ZCPM:NCCP=<name of parameter set>:::::SANN=NOANN;


The parameter is used in connection with the trunk signallingparameter announcement ability, which indicates whether thepreceding MSC-SSP is able to handle announcements. When anannouncement ability indication is received, the receiving MSC doesnot give an announcement even if the call fails. If the MSC is actingas a gateway-MSC or as transit exchange, it has to pass theinformation to the visited MSC, and the announcement responsibilityremains in the preceding exchange.

SATIND

1. Description

satellite indicator

SATINDThis parameter indicates whether satellite connection is usedif other routing alternatives are available. The possible valuesare:

NO no preference over route with satellite connection

SATavoid outgoing route with satellite connection





ZCPM:NCCP=<name of parameter set>:::::::SATIND=NO;


The parameter affects the satellite indicator sent in an outgoing IAM.

If the value is SAT, a subdestination without a satellite connection issearched; if no such route is available, the call is directed to the firstfree subsdestination that meets the other routing requirementsdefined for the call.

The parameter is used only in mobile-originating calls.

TNSAL

1. Description

Transit network selection parameter is allowed <optional>

TNSALThis parameter determines whether the transit networkselection parameter is allowed in the Initial Address Message(IAM). The possible values are:

Y transit network selection parameter allowed in IAM

N transit network selection parameter not allowed in IAM




ZCPM:NCCP=<name of parameter set>::::TNSAL=Y;

3. Related parameters. It has effect only when CIPAL is allowed.


If this value is used, and the IAM includes a TNS, the call is clearedwith clear code 0827 - CARRIER IDENTIFICATION NOTALLOWEDFROM INCOMING CIRCUIT.



Interfaces

TONSUP

1. Description

Connected party number type of number support <optional>

TONSUPThis parameter indicates whether TON is used with theconnected party number. If TON is not supported, the COLnumber is sent in an unknown form with national orinternational prefixes. The possible values are:

NOTONTON is not used with national or international connectednumber

NATTONTON is used, if the connected number is nationalnumber

INTTONTON is used, if the connected number is internationalnumber

BOTHTONTON is used, if the connected number is national orinternational number

The default value is BOTHTON.



ZCPM:NCCP=<name of parameter set>:::::::TONSUP=NOTON;

3. Related parameters. OMITCOL



VPS

1. Description

call is from voice processing system



VPSThis parameter determines what kind of CDR is used forcharging if the incoming call is from voice processing system.If the parameter is cleared (N), PSTN-Originating Call (POC)tickets are generated.

This parameter is usually set (Y) when the call comes from theVoice Mail System (VMS), thus VPSO tickets are generated.The possible values are:

Y VPSO tickets are generated

N POC tickets are generated



ZCPM:NCCP=<name of parameter set>:::VPS=Y;

3. Related parameters. CDR


This parameter also restricts inband information to voice processingsystem.

4.1.1.2 Outgoing call control parameters

ACMF

1. Description

ACM free allowed

ACMFThis parameter controls the handling of free-of-chargeinformation in transit exchange. The possible values are:

Y the received free charge indication in ACM fromoutgoing signalling is accepted

N reject free call indication received in ACM



ZCPM:NCCP=<name of parameter set>::::ACMF=Y;



Interfaces

3. Related parameters. ACMF parameter in the incoming call control parameter file


This is a transit MSC functionality.

If ACMF=N Charging is determined by charging informationobtained as a result of the routing and charginganalysis for the called party number.

Even if the value of ACMF of the outgoing route is 'Y', but the valueof ACMF of the incoming circuit is 'N', a free call indication isrejected. Also, if several free call indications are received in differentmessages and analyses, the MSC acts according to the latest one.

ADDID

1. Description

Additional ID supported

ADDIDThis parameter determines which information element iscarried in IAM. These can be Location Information, CalledNumber Before Translation, sending both, or restricting both.The possible values are:

BOTHRESTBoth of them are restricted

NBEFORETRSend Called Number Before Translation

LOCINFOSend Location Information

SENDBOTHSend both of them

The default value is BOTHREST.


ZCPF:NCCP=<name of used parameter set>:::ADDID=LOCINFO;


The parameter is used in connection with Feature 1445: Support forAdditional Identity.



ANICLI

1. Description

ANI-CLI relation <optional>

ANICLIThis parameter determines which number is sent to the nextexchange in a call set-up when the format of CLI and ANI / CNis the same. The possible values are:

NOTEXno ANI / CN defined

CLI send CLI

ANIsend ANI

BOTHsend both CLI and ANI

The default value is NOTEX.



ZCPF:NCCP=<name of parameter set>:::::ANICLI= BOTH:;

ANIMODE

1. Description

ANI mode <optional>

ANIMODEThis parameter defines the format of Charge Number (CN) /Automatic Number Identification (ANI), which determineswhether the CN / ANI is sent to the next exchange in the ISUPIAM or in MF. The possible values are:

NOTEXno CN / ANI defined

DENIEDCN / ANI not sent

SUBSsubscriber format preferred

NAT



Interfaces

national format preferred

INTinternational format preferred

DEFsend a default value (HRNFIL default CLI)




ZCPF:NCCP=<name of parameter set>:::::ANIMODE= INT:;

3. Related parameters. CIPAL: CIP parameter is allowed. SENDCIP: sending of CIP

NOTEX cannot be given if the value of SENDCIP is ALWAYSor IFDIFF.

ANMF

1. Description

answer free allowed

ANMFThis parameter controls the handling of free-of-chargeinformation in transit exchange. The possible values are:

Y the received free charge indication in ANM fromoutgoing signalling is accepted

N reject free call indication received in ANM



ZCPM:NCCP=<name of parameter set>::::ANMF=Y;

3. Related parameters. ANMF parameter in the incoming call control parameter file





If ANMF=N Charging is determined by charging informationobtained as a result of the routing and charginganalysis for the called party number.

Even if the value of ANMF of the outgoing route is 'Y', but the valueof ANMF of the incoming circuit is 'N', a free call indication isrejected. Also, if several free call indications are received in differentmessages and analyses, the MSC always acts according to themost recent one.

Free information is not supported on R2.

CDBSUB

1. Description

Charged Subscribers in CDB <optional>

CDBSUBThis parameter indicates the charged subscriber, if no chargednumber is received from the VMS/SN. The possible valuesare:

ASUBsubscriber A is charged in CDB call

BSUBsubscriber B is charged in CDB call

CSUBsubscriber C is charged in CDB call

NONEsubscriber is not defined

The default value is NONE.



ZCPF:NCCP=<name of parameter set>::::::CDBSUB=CSUB;


The parameter is used in connection with Feature 1093: AdvancedCall Drop Back for VMS Interface.



Interfaces

CDR

1. Description

CDR generation

CDRThis parameter indicates whether a CDR is generated in aspecific call case. The possible values are:

Y CDR is generated

N CDR is not generated



ZCPF:NCCP=<name of parameter set>::::::CDR=Y;

3. Related parameters. The parameter is relevant only if the call types in which CDRs

are generated have been defined in the CDR generationparameter (defined by the GTM command of the DetailedCharging Handling MML).

. If the value is N, all charging data is collected in OWN counterfiles instead of call type-specific files (for example, VPSO,VPST / POC, PTC / PBXO, PBXT).


All the relevant CDRs have to be 'activated' with the GTM commandto get their generation controlled by the CDR parameter in OP0FIL.

The value of this parameter has an effect also on the mobileaccounting part of the trunk circuit charging. That is, if the CDRparameter has value 'N', all charging is counted into the 'OWN …'-counters. If the CDR parameter has value 'Y', the charging iscounted into their own counters in question, that is, into 'VPS …'-counters in case of VPS originated/terminated calls, into 'PSTN …'-counters in case PSTN originated/terminated calls and into 'OWN…'-counters in case of PBX originated/terminated calls.

CLI

1. Description

calling line identity sending



CLI This parameter indicates whether calling line identity is sent inthe set-up message. The possible values are:

Y include CLI in IAM

N CLI not included in IAM



ZCPF:NCCP=<name of parameter set>:CLI=Y;


If CLI presentation is restricted CLI is not sent to the network, andCLI presentation status is changed into 'cli not available'.


CPGF

1. Description

CPG free allowed

CPGFThis parameter controls the handling of free-of-chargeinformation in transit exchange. The possible values are:

Y accept free call indication received in CPG

N reject free call indication received in CPG



ZCPM:NCCP=<name of parameter set>::::CPGF=Y;

3. Related parameters. CPGF parameter in the incoming call control parameter file



If CPGF=N Charging is determined by charging informationobtained as a result of the routing and charginganalysis for the called party number.



Interfaces

Even if the value of CPGF of the outgoing route is Y, but the value ofCPGF of the incoming circuit is N, a free call indication is rejected.Also, if several free call indications are received in differentmessages and analyses, the MSC acts according to the latest one.

ECINFO

1. Description

Echo canceller information

ECINFOThis parameter defines whether the sending of connect-echo-canceller information to the network is allowed. The possiblevalues are:

Y connect-echo-canceller information is allowed to be sentto the network

N connect-echo-canceller information is not allowed to besent to the network



ZCPF:NCCP=<name of used parameter set>::::ECINFO=Y;

3. Related parameters. ECINFO parameter on the incoming side


The parameter is used in connection with Feature 1146: SSP Echocancelling and conference bridging enhancements.

EMER

1. Description

Emergency indication

EMERThis parameter defines whether emergency indication isforwarded to signalling. The possible values are:

Y emergency indication is sent

N no emergency indication is sent





ZCPF:NCCP=<name of used parameter set>:::EMER=Y;


The parameter is used in connection with Feature 820: EnhancedEmergency Service (E911).

FECHO

1. Description

identify forced connection of ECHO canceller

FECHOThis parameter indicates whether the incoming echo cancelleris forcibly connected, if an echo canceller has been equippedin the outgoing circuit. The possible values are:

Y echo canceller is forcibly connected

N echo canceller is not forcibly connected



ZCPF:NCCP=<name of parameter set>:FECHO=Y;


The parameter does not affect data calls.

FIXRCI

1. Description

override routing control indicator

FIXRCIThis parameter controls alternative routing and continuousretry of circuit hunting. The possible values are:

0 alternative routing allowed, continuous retry allowed

1 alternative routing barred, continuous retry allowed

2 alternative routing allowed, continuous retry barred



Interfaces

3 alternative routing barred, continuous retry barred

4 alternative routing allowed once, continuous retryallowed

5 alternative routing allowed once, continuous retry barred

F unused

The default value is F.


ZCPF:NCCP=<name of used parameter set>::::FIXRCI=F;


The parameter is used only in NUP signalling.

FORCIP

1. Description

format of CIP <optional>

FORCIPThis parameter indicates the format of the Carrier IdentificationParameter (CIP). The possible values are:

NOTEXformat of CIP not defined

THREEsend three-digit CIP

FOURsend four-digit CIP




ZCPF:NCCP=<name of parameter set>:::::FORCIP= FOUR:;

3. Related parameters. CIPAL: CIP parameter is allowed. SENDCIP: sending of CIP

NOTEX cannot be given if the value of SENDCIP is ALWAYSor IFDIFF.




The parameter is used in connection with Feature 1296: CarrierSelection.

FORTNS

1. Description

format of TNS <optional>

FORTNSThis parameter indicates whether the transit network selectionindicator is sent to the next exchange in a call set-up. Thepossible values are:

NOTEXformat of TNS not defined

THREEsend three-digit TNS

FOURsend four-digit TNS




ZCPF:NCCP=<name of parameter set>:::::FORTNS=FOUR:;

3. Related parameters. TNSAL: TNS parameter is allowed. SENDTNS: sending of TNS

NOTEX: cannot be given if the value of SENDTNS is ALWAYSor INT



FTCIND

1. Description

Forward through-connection indicator

FTCIND



Interfaces

This parameter controls the content of the 'through-connection'indicator, which is packed into the ISUP v3 'UID capability'parameter in the IAM message. The possible values are:

Y value 'through-connection modification possible' given inIAM, so a through-connection can be established atACM/CPG according to the instructions given by thenext exchange

N value 'no indication' given in IAM, a through-connectioncannot be made



ZCPF:NCCP=<name of used parameter set>::::FTCIND=N;



FT9IND

1. Description

Forward T9 timer indicator

FT9INDThis parameter controls the content of 'T9 timer' indicator,which is packed into the ISUP v3 'UID capability' parameter inthe IAM message. If this parameter is sent to the nextexchange, it allows the receiving exchange to stop 'waiting foranswer' timer in the sender exchange by issuing CPG or ACMmessage with the 'UID action' parameter. The possible valuesare:

Y value 'stopping of timer possible' given in IAM, and theT9 timer stops as instructed by the next exchange

N value 'no indication' given in IAM, and the T9 timer is notallowed in the sender exchange



ZCPF:NCCP=<name of used parameter set>::::FT9IND=N;





HOCDR

1. Description

Handover Ticket Generation

HOCDRThis parameter indicates whether CDR is generated in anMTC/PTC/POC handover. The possible values are:

Y HOCDR is generated

N HOCDR is not generated



ZCPF:NCCP=<name of parameter set>::::HOCDR=Y;

3. Related parameters. HOCDR parameter on the incoming side

IDDCLI

1. Description

set incomplete indicator with default CLI

IDDCLIThis parameter indicates the IC indicator status of the defaultCLI, if default CLI is used as CLI. The possible values are:

Y set incomplete indicator to default CLI

N incomplete indicator not set to default CLI



ZCPF:NCCP=<name of parameter set>:IIDCLI=Y;



Interfaces

3. Related parameters. RICLI parameter in outgoing call control parameters

If IIDCLI=Y and also RICLI=Y in the same call controlparameter set and the default CLI is to be used the CLI iscompletely removed. If IIDCLI=N and RICLI=Y and the defaultCLI is to be used then the default CLI is passed forward.

. CFI parameter in CLI-conversion

If CFI parameter in CLI-conversion is set either as 'NATDEF' or'INTDEF', the incomplete indicator of the CLI to be used is setaccording to the value of IIDCLI parameter.

. IC parameter in CLI-conversion

. LONGCLI: too long CLI handling

. NOCLI: calling line identity restriction

. CLI: calling line identity sending

. NATCLI: use national default CLI

. MAXCLI: maximum length of calling line identity

. MSCCLI: the MSC default CLI presentation


If the default value is used, and the value of RICLI is Y, the defaultCLI is removed, that is, no calling line identity is sent to the network.If the value of IIDCLI is N and the value of RICLI is Y, the default CLIis sent to the network.

If the CLI format instruction (defined in the CFI parameter of theCalling Line Identity Handling MML) is NATDEF or INTDEF, thevalue of IC indicator is determined by the value of IIDCLI.

IHOPC

1. Description

ISUP HOP Counter <optional>

IHOPC This parameter is used to minimise the impactof looping. The parameter determines themaximum number of contiguous ISUPinterexchange circuits that are allowed tocomplete the call, assuming that all thesubsequent intermediate exchangesdecrement the hop counter. If the hop counterreaches '0', the call is released and the



management system is notified. The ISUP hopcounter parameter can have values between0...31. Value '0' indicates that the parameter isnot in use.




ZCPF:NCCP=<name of used parameter set>::IHOPC=1;


The parameter is used in connection with Feature 1267: HopCounter.

INEMO

1. Description

add EMO IN category key <optional>

INEMOThis parameter indicates whether EMO IN category key isadded to the called number. The possible values are:

Y category key is added to called number

N category key is not added to called number




ZCPF:NCCP=<name of parameter set>:::INEMO=Y;


The ICK (IN category key) is added to the B-number if theinstructions in the outgoing call control parameter file require.

An ICK can be allocated for a mobile subscriber in the HLR. Using ofICK makes it possible to route the mobile-originating call towards anexternal SSP with modified B-number. If the ICK is allocated for thesubscriber, it is stored into the MOC CDR. In the Billing System the



Interfaces

ICK value may have influence on the billing of the subscriber; forexample, the calling mobile subscriber is not charged based on theMOC CDR at all but the chargeable CDR is generated in the externalSSP.

The ICK is not included in the FW or MTC CDR.

The parameter is used in connection with Feature 498: Mobile INCategories.

ISVERS

1. Description

IN signalling version to the SCF

ISVERS This parameter indicates the version of theoutgoing signalling. It can be used only onBSSAP, TUP, NUP, ISUP, DPNSS, DSS1, R2and PAD connections. The value ranges from 0to 255.



ZCPF:NCCP=<name of parameter set>:ISVERS=0;


This value is sent beside the signalling code extension to IN platformin InitialDP operation. The definition and usage of this parameter isoperator-specific.


ITCMOD

1. Description

Incoming call control parameter concerning ITC modification<optional>

ITCMODThis parameter is used to change the Information TransferCapability (ITC) of modem services into Unrestricted Digital(UDI). The possible values are:



0 ITC is not changed

1 ITC is changed into UDI




ZCPF:NCCP=<name of used parameter set>:ITCMOD=1;


If value 1 is used, also the Transmission Medium Requirement(TMR) has to be changed.

The parameter is used in connection with Feature 1295: 3.1kHz toUDI Call Change Capability.

LONGCLI

1. Description

too long CLI handling

LONGCLIThis parameter indicates whether the national default callingline identity is used as CLI, if the CLI to be sent to the networkis longer than what has been defined in MAXCLI. The possiblevalues are:

Y use national default CLI

N national default CLI not used



ZCPF:NCCP=<name of parameter set>:LONGCLI=Y;

3. Related parameters. MAXCLI parameter in outgoing call control parameter file must

be defined if LONGCLI parameter is used


The national default CLI is defined with the WVS command of theGSM Network and MSC/HLR Specific Number Handling (MSC)MML; the program stores the value to the GSM Network andNetwork-Element-Specific Number File (HRNFIL).



Interfaces

Too long CLI is replaced with NATDEF CLI from HRNFIL.

MAXCLI

1. Description

maximum length of calling line identity

MAXCLI This parameter indicates the maximum lengthof calling line identity. The value ranges from 1to 32.

The default value is 32 digits.


ZCPF:NCCP=<name of parameter set>:MAXCLI=32;

3. Related parameters. The value of LONGCLI parameter determines whether the

national default CLI is used as CLI if the length of CLI exceedsthe limit value defined in this parameter.

MCU

1. Description

MAP CLI usage <optional>

MCUThis parameter indicates which kind of subscribers the CLIreceived from the MAP is used instead of the CLI receivedfrom the signalling. The possible values are:

NONEno subscribers

ROCroamer from other country

RHCroamer from home country

RHOroamer from home and other country

OWNhome subscriber

HROhome subscriber and roamer from other country



HRHhome subscriber and roamer from home country

ALLall subscribers

The default value is ROC.



ZCPF:NCCP=<name of used parameter set>:MCU=OWN;


The parameter is used in connection with Feature 1125: CLI supportfor roaming subscriber.

MMLINMCF

1. Description

Multiple Call Forwarding

MMLINMCFThis parameter indicates whether Redirected Party number(REDIR) or Original Called Party (OCD) number is used toforward the call. The possible values are:

MCFFSDPNSS1

In PNP calls, OCD is used as the first choice when it isavailable. If OCD is unavailable or it is inapplicable butREDIR is available, REDIR is used. If REDIR and OCDare both unavailable or inapplicable, no LI is used.

In non-PNP calls, REDIR is used, if it is available. IfREDIR is unavailable, no LI is used.

DSS1

In PNP calls, both OCD and REDIR are translated intothe private format.

In non-PNP calls, both OCD and REDIR are translatedinto the public format.

Trunk

Both OCD and REDIR are used.

MCFLAST <optional>



Interfaces

DPNSS1

REDIR is used as the first choice in PNP calls, but if it isunavailable or inapplicable, OCD is used, if it isavailable. If REDIR and OCD are both unavailable orinapplicable, no LI is used.

In non-PNP calls, no LI is used if REDIR is not available.

This value can be used only in DPNSS1.

MCFFIRST <optional>DPNSS1

OCD is used as the first choice in PNP calls, but if it isunavailable or inapplicable, REDIR is used, if it isavailable. If REDIR and OCD are both unavailable orinapplicable, no LI is used.

In non-PNP calls, no LI is used if OCD is not available.

This value can be used only in DPNSS1.

MCFOCDREDIR is copied to OCD.

This value can be used in DPNSS1, DPNSS1 and trunksignalling.

MCFREMBoth REDIR and OCD are removed.

This value can be used in DPNSS1, DPNSS1 and trunksignalling.

The default value is MCFFS.



ZCPF:NCCP=<name of used parameter set>:::MMLINMCF=MCFLAST;

MSCCLI

1. Description

the MSC default CLI presentation

MSCCLIThis parameter indicates the presentation status of the defaultcalling line identity defined in the HRNFIL. The possible valuesare:



Y presentation of MSC default CLI restricted

N presentation of MSC default CLI not restricted



ZCPF:NCCP=<name of parameter set>:MSCCLI=Y;


Normally, the default CLI is used when:. CLI formatting instruction (defined in the CFI parameter of the

Calling Line Identity Handling MML) is NATDEF or INTDEF. CLI conversion fails and CLI handling instruction (defined in

the HCI parameter of the Calling Line Identity Handling MML)is NATDEF or INTDEF

. the original CLI is not available (that is, it has not beenreceived from the incoming signalling) and the value ofNATCLI both in IP0FIL and OP0FIL is Y

The default CLI numbers are stored in the HRNFIL file.

NATCLI

1. Description

use national default CLI

NATCLIThis parameter indicates whether the national default callingline identity is used, if CLI is not available. The possible valuesare:

Y use national default CLI if CLI not available

N national default CLI not used if CLI not available



ZCPF:NCCP=<name of parameter set>:NATCLI=Y;



Interfaces

3. Related parameters. This parameters also requires the activation of the NATCLI

parameter in incoming call control parameters incorresponding incoming side.

. If the NOASK parameter in incoming call control parameters inthe corresponding incoming side is activated and CLI is notsent in a setup message, the national default CLI is alwayssent if NATCLI=Y.


Situation where the actual CLI is not available:. CLI is not received in the setup message (like in R2 signalling)

AND. NOASK parameter in incoming call control parameters is

activated, so CLI cannot be inquired OR. CLI is not received (not available information) when inquired. The parameter has effect only on outgoing IAM.

In these cases, the national default CLI is sent.

NOCLI

1. Description

calling line identity sending restriction

NOCLIThis parameter indicates whether the CLI can be inquired inthe call set-up. The possible values are:

Y CLI inquiry prevented

N CLI inquiry allowed


If the value is Y, CLI presentation status is changed into restricted.


ZCPF:NCCP=<name of parameter set>:NOCLI=Y;

3. Related parameters. CLI: calling line identity sending

If the value of NOCLI is Y, this parameter (CLI) has no effect.





OPCX

1. Description

route is to operator centrex

OPCXThis parameter is used to execute the CLIR override function,that is, to determine that CLI is sent to the PBX although thepresentation indicator shows that presentation is prevented.The possible values are:

Y send CLI to network

N handle CLI according to PI



ZCPF:NCCP=<name of parameter set>:::OPCX=Y;

3. Related parameters. If the value is Y, the VPS parameter cannot be given

RIAMPAR

1. Description

restricted IAM parameter <optional>

RIAMPARThis parameter controls the sending of some parameters inISUP IAM message.The possible values are:

ATPrestrict the sending of Access Transport Parameter(ATP)

NONEdo not restrict any parameters





Interfaces

ZCPF:NCCP=<name of parameter set>::::RIAMPAR=ATP:;

RICLI

1. Description

remove incomplete calling line identity

RICLIThis parameter indicates whether calling line identity isremoved if its IC status is incomplete. The possible values are:

Y remove incomplete calling line identity

N incomplete calling line identity not removed



ZCPF:NCCP=<name of parameter set>:RICLI=Y;

3. Related parameters. IIDCLI parameter in outgoing call control parameters

RUC

1. Description

restriction of unidentified calls <optional>

CLI This parameter indicates whether an emergency call isreleased if it has been made without the SIM card and CLIpresentation status is restricted. The possible values are:

Y unidentified emergency calls are released

N unidentified emergency calls are not released




ZCPF:NCCP=<name of parameter set>:RUC=Y;


The parameter is used in connection with Feature 820: EnhancedEmergency Service (E911).



SART

1. Description

use of forwarding number roaming status in convert

SARTThis parameter indicates whether the roaming status used inCLI conversion is that of the forwarding subscriber or thenormal (A-subscriber) roaming status. The possible valuesare:

Y forwarding number roaming status is used in CLIconversion

N normal roaming status is used in CLI conversion. Normalroaming status usually means the roaming status fromsubscriber A



ZCPF:NCCP=<name of parameter set>:SART=Y;

3. Related parameters. If the value is Y, calling party roaming status (defined in the

CGRSTAT parameter of the Calling Line Identity HandlingMML) is set according to the forwarding party number.

. Also, if the value of the parameter UNU of the Calling LineIdentity Handling MML is FORWPTY, the number used as CLIis the forwarding party number and the calling party roamingstatus is determined accordingly.

SBRN

1. Description

set subscriber B number to CLI when B roaming abroad

SBRNThis parameter indicates whether the number presented asCLI is the B-number when the called subscriber is roamingabroad. This means that also the number sent to charging as acalling party number is the B-number. The possible values are:



Interfaces

Y subscriber B-number presented as CLI

N subscriber B-number not presented as CLI



ZCPF:NCCP=<name of parameter set>:SBRN=Y;

3. Related parameters. The called party number (or the forwarded-to party number) is

set to CLI if SBRN=Y and the called party (or the forwarded-toparty) is roaming abroad. In this case the UNU parameter hasno influence on CLI.


The called party number (or the forwarded-to party number) is alsoset to the presentation number and to the generic number ifSBRN=Y and the called party (or the forwarded-to party) is roamingabroad,

Optionally the SBRN parameter can have an effect to the originalcalled party number and to the redirecting party number as well.

The parameter does not affect call forwarding.

SENDSP

1. Description

Send Subscriber Profile

SENDSPThis parameter indicates whether the subscriber profile is sentto the outgoing route. The possible values are:

Y subscriber profile is sent

N subscriber profile is not sent



ZCPF:NCCP=<name of used parameter set>::::SENDSP=Y;


The parameter is used only in mobile-originating, trunk-terminatingcalls.



SEECLIR

1. Description

CLIR Indication <optional>

SEECLIRThis parameter determines whether the calling subscriber's'CLIR active' status is indicated to the called subscriber, if thecalled subscriber is using the CLIR override function. Thepossible values are:

Y CLIR indication is used

N CLIR indication is not used




ZCPF:NCCP=<name of used parameter set>:::SEECLIR=N;


The parameter has effect in MOC calls.

If the SEECLIR parameter is Y, # character is added to the beginningand end of the calling number when the calling subscriber has CLIRactive, and the called subscriber is using the CLIR override function.

The parameter is used in connection with Feature 1235: CLIRoverride indication.

SENDCIP

1. Description

sending of CIP <optional>

SENDCIPThis parameter indicates whether the Carrier IdentificationParameter (CIP) is sent to the next exchange in call set-up.The possible values are:

NOTEXno CIP defined

NO remove CIP from the set-up message



Interfaces

ALWAYSsend CIP in every call set-up

IFDIFFsend CIP only if CIP differs from TNS




ZCPF:NCCP=<name of parameter set>:::::SENDCIP=IFDIFF:;

3. Related parameters. CIPAL: CIP parameter is allowed. FORCIP: format of CIP

If the value is ALWAYS or IFDIFF, the value of FORCIP cannotbe NOTEX.



SENDTNS

1. Description

sending of TNS <optional>

SENDTNSThis parameter indicates whether the transit network selectionindicator is sent to the next exchange in a call set-up. Thepossible values are:

NOTEXno TNS defined

NO remove TNS from set-up message

ALWAYSsend TNS in every call set-up

INTsend TNS only in international calls






ZCPF:NCCP=<name of parameter set>:::::SENDTNS=INT:;

3. Related parameters. TNSAL: TNS parameter is allowed. FORTNS: format of TNS

If the value of SENDTNS is ALWAYS or INT, the FORTNSparameter must be other than NOTEX.



SPICK

1. Description

Starting point of ICK <optional>

SPICK This parameter indicates the starting pointwhere EMO IN category key is added to thecalled number.

The starting point of ICK can have valuesbetween 1 and 32.




ZCPF:NCCP=<name of used parameter set>:::INEMO=Y,SPICK=2;

3. Related parameters. INEMO (Outgoing call control parameter) Insertion of EMO IN

category key is allowed by the INEMO parameter, so theSPICK parameter is meaningless without setting INEMO first.(INEMO=Y)


The parameter is used in connection with Feature 1428: RoutingBased on IN Categories and Feature 498: Mobile IN Categories.



Interfaces

VPS

1. Description

route is to voice processing system

VPSThis parameter indicates whether the type of CDR used for thecharging of an outgoing call is VPST. The possible values are:

Y the type of CDR is VPST

N the type of CDR is PTC



ZCPF:NCCP=<name of parameter set>:::VPS=Y;

3. Related parameters. When the value of VPS is Y, the OPCX parameter cannot be

given.. CDRs are generated only if it is indicated in the CDR

parameter.


Value Y is normally used in VMS-terminating calls, and the callingsubscriber is given a tone or an announcement telling that the callwas directed to the voice mail.

4.1.2 Alarms

There are no alarms related to this feature.

4.2 Subscriber interfaces

The feature has no subscriber interfaces.

4.3 External interfaces

The feature has no effects on the external interfaces of the MSC/HLR.



5 Main changes in the feature

This feature is implemented in M13.1.

Changes between M13.1 and M12

The following changes have been made between M13.1 and M12:

The RIAMPAR parameter has been introduced into outgoing call controlparameters to control the sending of parameters in ISUP IAM message.



Main changes in the feature

Glossary

Abbreviations

ACM Address Complete Message

ALI Additional Line Identity

ANI Automatic Number Identification

ANM Answer Message

CCBS Call Completion to Busy Subscriber

CDR Charging Record

CF Call Forwarding

COL Connected Line Identity

COLP Connected Line Identification Presentation

COLR Connected Line Identification Restriction

CPC Calling Party Category

CPG Call Progress message

CUG Closed User Group

HO Handover

IAM Initial Address Message

LDLI Last Diverting Line Identity

LI Line Identity

OCD number Original Called Party Number

OCN Original Called Number

PAD Packet Assembler Disassembler

PBX Private Branch Exchange



Glossary

POC PSTN-Originated Call

PI Presentation Indicator

RN Redirecting Number

SCP Service Control Point

TON Type of Number

Terms

Circuit group Group of circuits which are traffic-engineered as a unit.

Route A group of hunted circuit groups which have the same direction and usethe same register signalling.





Glossary

References

1. Route Handling MML, RR Command Group.

2. Circuit Group Handling MML, RC Command Group.

3. End-of-Selection and Function Analysis Handling MML, RXCommand Group.

4. Call Control Parameters Handling MML, CP Command Group.

5. Feature 56: Satellite connections, Feature description.

6. Feature 227: Primary Rate Access, Feature description.

7. Feature 234: Completion of Calls to Busy Subscribers (CCBS),Feature description.

8. Feature 306: Call Forwarding Override, Feature description.

9. Feature 319: Support for Multiple Call Forwardings, Featuredescription.

10. Feature 401: Call Drop Back, Feature description.

11. Feature 498: Mobile IN Categories, Feature description.

12. Feature 628: Connected Line Identification Services, Featuredescription.

13. Feature 739: Core INAP CS-1 v3, Feature description.

14. Feature 820: Enhanced Emergency Service (E911), Featuredescription.

15. Feature 827: CLI Handling Improvement, Feature description.

16. Feature 840: Primary Rate Access (PBX: CLIP Charging) / 23B+D,Feature description.

17. Feature 1093: Advanced Call Drop Back for VMS Interface, Featuredescription.

18. Feature 1125: CLI support for roaming subscriber, Featuredescription.



19. Feature 1146: SSP Echo Cancelling and Conference BridgingEnhancements, Feature description.

20. Feature 1235: CLIR override indication, Feature description.

21. Feature 1267: Hop Counter, Feature description.

22. Feature 1295: 3.1kHz to UDI Call Change Capability, Featuredescription.

23. Feature 1296: Carrier Selection, Feature description.

24. Feature 1428: Routing Based on IN Categories, Feature description.

25. Feature 1445: Support for Additional Identity, Feature description.

26. Feature 1547: SN and subscription based CLI inquiry, Featuredescription.



References

826 mml controlled call control parameters.pdf

Documents

nokiasiemens networks

feature documentation

whichthe document

software products

mentioned hardware

operator interfaces

free of material errors

list of tables