5.8.4.

2 OPTF-010005_FPH
This topic describes the configuration of the FPH feature.
Free Phone Handler (FPH) is a feature indicating the charging performance. It enables a
callee instead of a caller to pay for calls. For example, if an enterprise or individual has
the FPH feature active, the subscriber (the enterprise or individual) must pay for all calls
received. Therefore, these calls are called free phone for callers. The FPH feature is
applicable only to speech communications.
Personal FPH (PFPH) refers to the personal-level FPH feature, which requires that the
callees cannot be virtual private network (VPN) subscribers. company-level fph service
(CFPH) refers to the company-level FPH feature.

Configuring the FPH Feature (for VMSC)

Scenario

The Free Phone Handler (FPH) feature enables carriers to provide a free-charge call
service for subscribers as required. To enable the FPH feature, configure the data as
provided in this topic. Figure 1 shows the typical networking for implementation of the
FPH feature.
Figure 1 Networking for implementation of the FPH feature
Impact on the System

The FPH feature is a type of intelligent network (IN) service that is built on common
services. Therefore, the FPH feature consumes more system resources than ordinary calls.
In addition, it takes longer time to connect the call. As a result, the number of calls that
are simultaneously processed by the MSOFTX3000 decreases.

Prerequisites

Conditions
 Links between the MSOFTX3000 and the HLR and Links between the MSOFTX3000
and another MSC are configured.
 The speech files required by the personal FPH (PFPH) feature are available in the
GMSC.
 Subscribers have registered originating CAMEL subscription information (O-CSI) or
T-CSI on the HLR.
Data
Table 1 describes the data to be prepared for the configuration.

Table 1 Data to be prepared

Category Parameter Example Value How to Obtain Description

SCP address (SCPADDR) 8613977999 Consistent with -

information SCP address that configured on
the SCP

(INVER) IN CAP2 Consistent with -

protocol version that configured on
the SCP

SCP parameters (SRVKEY) 3 Consistent with Obtain the service

Service key that configured on key of the mobile
the SCP virtual private
network (MVPN)
service.

(DCH) Default CTNUCALL Determined by Set the value of

call handling the carrier the parameter
mode according to the
carrier's
requirements.

Caller number (PFX) Call eeeeeeee Determined by Set the value of

analysis data prefix the carrier the parameter
according to the
 Table 1 Data to be prepared

Category Parameter Example Value How to Obtain Description

carrier's
requirements.

(CSCNAME) SHENZHEN Determined by -

Call source name the carrier

(CLIN) Caller 13907520395 Determined by Set the value of

number the carrier the parameter
according to the
carrier's
requirements.

Workflow

1. Run ADD USRVPROC to configure the Subscriber Integrated Services Information

table. For an ordinary mobile originated call (MOC) with the call prefix *8000, set
Service attribute to PFPH Service; for an ordinary MOC with the call prefix *8010,
set Service attribute to CFPH Service and Suppress OCSI to Yes. The purpose of
configuring the Subscriber Integrated Services Information table on the VMSC is to
identify the FPH service and suppress O-CSI.
2. Run ADD CNACLD to configure the Call Prefix table based on the call prefix *8000 or
*8010 so that the local MSC can route the call to the GMSC and add A+CAC to the
end of the called number during the outgoing number pre-processing.
3. Run MOD MSFP to set bit 0 of P234 to 0 so that BC can be converted to AB.
4. Run MOD MSFP to set bit 9 of P151 to 0 so that AB can be converted to BC.
5. Run MOD MSFP to set bits 8-11 of P53 to 4 so that the CAC_PHASE5 can be used.

Procedure

1. Configure data on the MSOFTX3000.

a. Add a subscriber integrated services information record, where Function type is

Caller category, Call originator is Mobile originated subscriber side, Call
prefix is *8000 or *8010, Caller category is Ordinary, Service attribute is
PFPH Service (for the call prefix *8000) or CFPH Service (or the call prefix
*8010), and Suppress OCSI is Yes (only for CFPH).

ADD USRVPROC:
FT=CALLERCAT, CS=MUSER, PFX=K'*8000, SCT=OCSI-1,
CC=CAT10, SRVCAT=PFPHSERVICE-1, PT=DONTPROC;
 ADD USRVPROC:
FT=CALLERCAT, CS=MUSER, PFX=K'*8010, SCT=OCSI-1,
CC=CAT10, SRVCAT=CFPHSERVICE-1, SOCSI=YES, PT=DONTPROC;

b. Configure the Call Prefix table to enable the local MSC to route the call with the
call prefix a8000 or a8010 to the GMSC.

ADD CNACLD:
PFX=K'a8000, CSA=MLCT, RSNAME="10", MINL=3,
MAXL=32, ICLDTYPE=PS;
ADD CNACLD:
PFX=K'a8010, CSA=MLCT, RSNAME="10", MINL=3,
MAXL=32, ICLDTYPE=PS;

c. Configure the Number Change table to enable the local MSC to add A+CAC to
the end of the called number.

ADD DNC:
DCN="10", DCT=TYPE2, ND=K'A, NDPRI=TRUE,
OTHERSRC=http://localhost:7890/SPE;

d. Configure the Outgoing Number Pre-Processing table to enable the local MSC to
add A+CAC to the end of the called number of the call with the prefix b8000 or
b8010. The relevant software parameter supports conversion from AB to BC;
therefore, the called number is changed to b8000 or b8010.

ADD OUTNUMPREPRO: CSCNAME="0", TGN="10", P=0, PFX=K'b8000,

DDN="10";
ADD OUTNUMPREPRO: CSCNAME="0", TGN="10", P=0, PFX=K'b8010,
DDN="10";

e. Configure the relevant software parameters to support conversion between AB

and BC, and CAC_PHASE5.

MOD MSFP: ID=P53, MODTYPE=P1, BIT=8, BITVAL=0;

MOD MSFP: ID=P53, MODTYPE=P1, BIT=9, BITVAL=0;
MOD MSFP: ID=P53, MODTYPE=P1, BIT=10, BITVAL=1;
MOD MSFP: ID=P53, MODTYPE=P1, BIT=11, BITVAL=0;
MOD MSFP: ID=P234, MODTYPE=P1, BIT=0, BITVAL=0;
MOD MSFP: ID=P151, MODTYPE=P1, BIT=9, BITVAL=0;

f. Data configuration on the MSOFTX3000 is complete.

2. Configure data on the UMG8900.

a. Data configuration on the UMG8900 is not required.
Verification

1. Confirm that the data is configured successfully and correctly.

2. Make a call from subscriber A to a PFPH subscriber by dialing *800+0 or to a
company-level fph service (CFPH) subscriber by dialing *801+0.
3. Check whether the call is successfully connected and whether the charging party in
the final call detail record (CDR) is the called subscriber.
4. View the user message tracing file to check whether the outgoing called number is
correct and whether the IN service is triggered in the GMSC.

Example

Task Description
Assume that subscriber A makes a call to a PFPH subscriber by dialing *800+0 or to a
CFPH subscriber by dialing *801+0. On the VMSC, the route selection name is 10; the
outgoing trunk group name is 10; the trunk group type is ISUP.
On the GMSC, the call source name is ALL; the service key of the CFPH subscriber is 1;
the service key of the virtual private network (VPN) subscriber is 3; the SCP address is
8613977999.
Scripts
//Add a subscriber integrated services information record, where
Function type is Caller category, Call originator is Mobile originated
subscriber side, Call prefix is *8000 or *8010, Caller category is
Ordinary, Service attribute is PFPH Service (for the call prefix *8000)
or CFPH Service (or the call prefix *8010), and Suppress OCSI is Yes
(only for CFPH).

ADD USRVPROC: FT=CALLERCAT, CS=MUSER, PFX=K'*8000, SCT=OCSI-1,

CC=CAT10, SRVCAT=PFPHSERVICE-1, PT=DONTPROC;
ADD USRVPROC: FT=CALLERCAT, CS=MUSER, PFX=K'*8010, SCT=OCSI-1,
CC=CAT10, SRVCAT=CFPHSERVICE-1, SOCSI=YES, PT=DONTPROC;

//Configure the Call Prefix table to enable the local MSC to route the
call with the call prefix a8000 or a8010 to the GMSC.

ADD CNACLD: PFX=K'*8000, CSA=MLCT, RSNAME="10", MINL=3, MAXL=32,

ICLDTYPE=PS;
ADD CNACLD: PFX=K'*8010, CSA=MLCT, RSNAME="10", MINL=3, MAXL=32,
ICLDTYPE=PS;

//Configure the Number Change table to enable the local MSC to add
A+CAC to the called number.

ADD DNC: DCN="10", DCT=TYPE2, ND=K'A, NDPRI=TRUE, OTHERSRC=SPE;

 //Configure the Outgoing Number Pre-Processing table to enable the
local MSC to add A+CAC to the called number of the call with the prefix
b8000 or b8010. The relevant software parameter supports conversion
from AB to BC; therefore, the called number is changed to b8000 or
b8010.

ADD OUTNUMPREPRO: CSCNAME="ALL", TGN="10", P=0, PFX=K'b8000, DDN="10";

ADD OUTNUMPREPRO: CSCNAME="ALL", TGN="10", P=0, PFX=K'b8010, DDN="10";

//Configure the relevant software parameters to support conversion

between AB and BC, and CAC_PHASE5.

MOD MSFP: ID=P53, MODTYPE=P1, BIT=8, BITVAL=0;

MOD MSFP: ID=P53, MODTYPE=P1, BIT=9, BITVAL=0;
MOD MSFP: ID=P53, MODTYPE=P1, BIT=10, BITVAL=1;
MOD MSFP: ID=P53, MODTYPE=P1, BIT=11, BITVAL=0;
MOD MSFP: ID=P234, MODTYPE=P1, BIT=0, BITVAL=0;
MOD MSFP: ID=P151, MODTYPE=P1, BIT=9, BITVAL=0;

Configuring the FPH Feature (for GMSC)

Scenario

The Free Phone Handler (FPH) service enables carriers to provide a free-charge call
service for subscribers as required. To enable the FPH service, configure the data as
provided in this topic. Figure 1 shows the typical networking for implementation of the
FPH service.
Figure 1 Networking for implementation of the FPH service
Impact on the System

The FPH service is a type of intelligent network (IN) service. The IN service is built on
common services. Therefore, the FPH service consumes more system resources than
ordinary calls. In addition, it takes longer time to connect the call. As a result, the number
of calls that are simultaneously processed by the MSOFTX3000 decreases.

Prerequisites

Conditions
 Links between the MSOFTX3000 and the HLR and links between the MSOFTX3000
and another MSC are configured.
 The speech files required by the personal FPH (PFPH) service are available in the
GMSC.
 Subscribers have registered originating CAMEL subscription information (O-CSI) or
T-CSI on the HLR.
Data
Table 1 describes the data to be prepared for the configuration.

Table 1 Data to be prepared

Category Parameter Example Value How to Obtain Description

SCP address (SCPADDR) 8613977999 Consistent with -

information SCP address that configured on
the SCP

(INVER) IN CAP2 Consistent with -

protocol version that configured on
the SCP

SCP parameters (SRVKEY) 3 Consistent with Obtain the service

Service key that configured on key of the mobile
the SCP virtual private
network (MVPN)
service.

(DCH) Default CTNUCALL Determined by Set the value of

call handling the carrier the parameter
mode according to the
carrier's
requirements.

Caller number (PFX) Call eeeeeeee Determined by Set the value of

analysis data prefix the carrier the parameter
according to the
 Table 1 Data to be prepared

Category Parameter Example Value How to Obtain Description

carrier's
requirements.

(CSCNAME) SHENZHEN Determined by -

Call source name the carrier

(CLIN) Caller 13907520395 Determined by Set the value of

number the carrier the parameter
according to the
carrier's
requirements.

Workflow

1. Configure the Incoming Number Pre-processing table, where Number receiving

delay interval(0.1s) is set to 20, for the call prefix *8000 or *8010 to avoid the
incomplete number receiving.
2. Configure the Subscriber Integrated Services Information table. For an ordinary trunk
call, if the call prefix is *8000, set Service attribute to PFPH Service. In addition,
configure the Number Change table to delete *8000 from the called number and add
*8000 to the calling number. If the call prefix is *8010, set Service attribute to
CFPH Service.
3. Configure the Caller Feature Analysis table, where Processing type is set to Trigger
DP2 of N-CSI, for the company-level fph service (CFPH) service.
4. Configure the TDP Access Code table for the CFPH service so that the DRA in the
CONNECT message sent by the SCP cannot be updated to the dialed number.
5. Configure the FCSB table so that the PFPH calls destined for the virtual private
network (VPN) subscribers can be barred.
6. Set bit 0 of P234 to 0 so that BC can be converted to AB.
7. Set bit 9 of P151 to 0 so that AB can be converted to BC.
8. Set bits 8-11 of P53 to 4 so that the CAC_PHASE5 can be used.
9. Optional: Set bit 4 of P1205 to 0 if announcements or digit collection is not performed
after a call to a PFPH subscriber is answered. This ensures that the ACR message
sent from the MSC server to the SCP is correct when the call is released, and
charging is performed properly.
Procedure

1. Configure data on the MSOFTX3000.

a. Configure the Incoming Number Pre-processing table, where Number receiving

delay interval(0.1s) is set to 20, for the call prefix *8000 and call prefix *8010,
respectively.

ADD INNUMPREPRO: CSCNAME="0", PFX=K'b8000, DRNT=20;

ADD INNUMPREPRO: CSCNAME="0", PFX=K'b8010, DRNT=20;

b. Configure the Number Change table. In one number change record, set Number
change option to Delete number in positive sequence of designated position
so that b8000 is deleted from the called number; in the other number change
record, set Number change option to Insert number at designated position so
that b8000 is added to the beginning of the called number.

ADD DNC: DCN="20", DCT=TYPE6, DCL=5;

ADD DNC: DCN="21", DCT=TYPE1, ND=K'b8000;

c. Set Caller number change name, Called number change name, and Service
attribute in the Subscriber Integrated Services Information table based on the
call prefix b8000 or b8010, call originator, and caller category.

ADD USRVPROC:
FT=CALLERCAT, CS=ISUP, PFX=K'b8000, SCT=OCSI-1,
CC=CAT10, CLINCN="21", CLDNCN="20", SRVCAT=PFPHSERVICE-1;
ADD USRVPROC:
FT=CALLERCAT, CS=ISUP, PFX=K'b8010, SCT=OCSI-1,
CC=CAT10, SRVCAT=CFPHSERVICE-1;

d. Add a caller feature analysis record, where Processing type is set to Trigger
DP2 of N-CSI.

ADD CLICRTANA:
CSCNAME="Call source name", CF=ALL, CAT=ALL,
MAXL=32, CS=ALL, PFX=K'b8010, PT=NCSIDP2, AM=AC;

e. Configure the TDP Access Code table.

ADD TDPAC:
ACNAME="Access code name", ACODE=K'B8010, DBNSP=5,
DBNLEN=1;

NOTE:
When the network service CAMEL subscription information (N-CSI) is triggered, if the SCP is
accessed in the access code mode, you need to configure the TDP access code to obtain a
database number. The TDP access code works with the service key configured in the Intra-Office
TDP Configuration table to reference the SCP configuration information. The database number
starts from 0. In the preceding command script, the database number start position is set to 5 and
the database number length is set to 1. When the access code is B80106780050, the SCP address
index database number is 6.
f. Configure the Intra-Office TDP Configuration table.

ADD ITDPCFG:
DPNUM="DP2", ACNAME="Access code name",
SRVKEY="Service key";

g. Configure the SCP Configuration table.

ADD SCPCFG: SRVKEY="Service key", DBN=6, SCPADDRNAME0="SCP

address name 0";
ADD SCPCFG: SRVKEY="Service key", DBN=65534, SCPADDRNAME0="SCP
address name 0";

h. Configure the SCP Address Information table.

ADD SCPINFO: SCPADDRNAME="SCP address name 0", SCPADDR="SCP

address", INVER=CAP2, SCFID="SCF ID";

i. Configure the MAP Feature Configuration table.

SET MAPACCFG: CAMELVER=PHASE2;

j. Configure the service key, DP number, and call prefix in the Bill Subscriber
Type Control table so that the dialed number is not replaced.

ADD BLLUTCTL: FN=CN, SRVKEY="Service Key(HEX)", DP=DP2,

PFX=K'b8010;

k. Configure the relevant software parameters to support conversion between AB

and BC, and CAC_PHASE5.

MOD MSFP: ID=P53, MODTYPE=P1, BIT=8, BITVAL=0;

MOD MSFP: ID=P53, MODTYPE=P1, BIT=9, BITVAL=0;
MOD MSFP: ID=P53, MODTYPE=P1, BIT=10, BITVAL=1;
MOD MSFP: ID=P53, MODTYPE=P1, BIT=11, BITVAL=0;
MOD MSFP: ID=P234, MODTYPE=P1, BIT=0, BITVAL=0;
MOD MSFP: ID=P151, MODTYPE=P1, BIT=9, BITVAL=0;

l. Add a service brand record, where Standards for service brand definition is
set to Service key+calling number, Service key to the VPN service key,
Calling number to the PFPH service prefix, Handling mode to Call barred,
and Release cause value to Call reject.

ADD FCSB:
SBCRITERIA=SKCLI, SRVKEY="Service key",
CLIADDR=K'b8000, HANDLEMODE=CALLBAR, CAUSE=CV149;
 m. Optional: Set bit 4 of P1205 to 0 if announcements or digit collection is not
performed after a call to a PFPH subscriber is answered. This ensures that the
ACR message sent from the MSC server to the SCP is correct when the call is
released, and charging is performed properly.

NOTE:
For the announcement playing during an Establish Temporary Connection (ETC) flow, the
announcement and digit collection is performed by the assisting service switching point (SSP)
rather than the local MSC server.

MOD MSFP: ID=P1205, MODTYPE=P1, BIT=4, BITVAL=0;

n. Data configuration on the MSOFTX3000 is complete.

2. Configure data on the UMG8900.

a. Data configuration on the UMG8900 is not required.

Verification

1. Confirm that the data is configured successfully and correctly.

2. Make a call to a PFPH subscriber by dialing *800+0 or a CFPH subscriber by dialing
*801+0.
3. Check whether the call is successfully connected and whether the charging party in
the final call detail record (CDR) is the callee.
4. View the user message tracing file to check whether the outgoing called number is
correct and whether the IN service is triggered in the GMSC.

Example

Task Description
In the VMSC, subscriber A makes a call to a PFPH subscriber by dialing *800+0 or to a
CFPH subscriber by dialing *801+0. The route selection name is 10; the outgoing trunk
group name is 10; the trunk group type is ISUP.
On the GMSC, the call source name is ALL; the service key of the CFPH subscriber is 1;
the service key of the VPN subscriber is 3; the SCP address is 8613977999.
Scripts
//Configure the Incoming Number Pre-processing table, where Number
receiving delay interval(0.1s) is set to 20, for the call prefix *8000
and call prefix *8010, respectively.
ADD INNUMPREPRO: CSCNAME="0", PFX=K'b8000, DRNT=20;
ADD INNUMPREPRO: CSCNAME="0", PFX=K'b8010, DRNT=20;

//Configure the Number Change table. In one number change record, set
Number change option to Delete number in positive sequence of
designated position so that b8000 is deleted from the called number; in
the other number change record, set Number change option to Insert
number at designated position so that b8000 is added to the beginning
of the called number.
ADD DNC: DCN="20", DCT=TYPE6, DCL=5;
ADD DNC: DCN="21", DCT=TYPE1, ND=K'b8000;

//Set Caller number change name, Called number change name, and Service
attribute in the Subscriber Integrated Services Information table based
on the call prefix b8000 or b8010, call originator, and caller
category.
ADD USRVPROC: FT=CALLERCAT, CS=ISUP, PFX=K'b8000, SCT=OCSI-1, CC=CAT10,
CLINCN="21", CLDNCN="20", SRVCAT=PFPHSERVICE-1;
ADD USRVPROC: FT=CALLERCAT, CS=ISUP, PFX=K'b8010, SCT=OCSI-1, CC=CAT10,
SRVCAT=CFPHSERVICE-1;

//Configure the Caller Feature Analysis table.

ADD CLICRTANA: CSCNAME="0", CF=ALL, CAT=ALL, MAXL=32, CS=ALL,
PFX=K'b8010, PT=NCSIDP2, AM=AC;

//Add the TDP Access Code table.

ADD TDPAC: ACNAME="0", ACODE=K'B8010, DBNSP=5, DBNLEN=1;

//Configure the intra-office TDP Configuration table.

ADD ITDPCFG: DPNUM=DP2, ACNAME="0", SRVKEY=1;

//Configure the SCP Configuration table.

ADD SCPCFG: SRVKEY=1, DBN=6, SCPADDRNAME0="0";
ADD SCPCFG: SRVKEY=1, DBN=65534, SCPADDRNAME0="0";

//Configure the SCP Address Information table.

ADD SCPINFO: SCPADDRNAME="0", SCPADDR=K'8613977999, INVER=CAP2,
SCFID="123";

//Configure the MAP Feature Configuration table.

SET MAPACCFG: CAMELVER=PHASE2;

//Configure the service key, DP number, and call prefix in the Bill
Subscriber Type Control table so that the dialed number is not
replaced.
ADD BLLUTCTL: FN=CN, SRVKEY="1", DP=DP2, PFX=K'b8010;

//Configure the relevant software parameters to support conversion

between AB and BC, and CAC_PHASE5.
MOD MSFP: ID=P53, MODTYPE=P1, BIT=8, BITVAL=0;
MOD MSFP: ID=P53, MODTYPE=P1, BIT=9, BITVAL=0;
MOD MSFP: ID=P53, MODTYPE=P1, BIT=10, BITVAL=1;
MOD MSFP: ID=P53, MODTYPE=P1, BIT=11, BITVAL=0;
MOD MSFP: ID=P234, MODTYPE=P1, BIT=0, BITVAL=0;
MOD MSFP: ID=P151, MODTYPE=P1, BIT=9, BITVAL=0;

//Add a service brand record, where Standards for service brand

definition is set to Service key+calling number, Service key to the VPN
service key, Calling number to the PFPH service prefix, Handling mode
to Call barred, and Release cause value to Call reject.
ADD FCSB: SBCRITERIA=SKCLI, SRVKEY=3, CLIADDR=K'b8000,
HANDLEMODE=CALLBAR, CAUSE=CV149;

//(Optional) Set bit 4 of P1205 to 0 if announcements or digit

collection is not performed after a call to a PFPH subscriber is
answered. This ensures that the ACR message sent from the MSC server to
the SCP is correct when the call is released, and charging is performed
properly.
MOD MSFP: ID=P1205, MODTYPE=P1, BIT=4, BITVAL=0