IMS - Provisioning Guide for Retail v3.1

Huawei Technologies Co.,

Ltd.

Research Document Center

Document

Number Version Confidentiality

3.1 Open for customer

Product: IMS 72 Pages

GVT IMS Project

Provisioning Guide

(For Retail Customers)

Huawei Technologies Co., Ltd.

All rights reserved

Huawei IMS Southern South America SSA Project

Provisioning Guide

Open to GVT and Huawei

Copyright by Huawei - 2 -

Version Control Table

Reviewed by Ver Date Notes

Janir Pinheiro – SPO TSD 1.0 31-Aug-11 - First version for customer revision

Janir Pinheiro – SPO TSD 1.1 21-set-11 - Item 1.30 Voice Mail Service: Added service description and example was changed.

- Added Item 1.58: Support FAX service.

Janir Pinheiro – SPO TSD 1.2 27-set-11 - Items from 1.1 to 1.10: scripts were changed to support SIP Digest authentication

Janir Pinheiro – SPO TSD 1.3 01-nov-11 - Item 1.33 changed to “Outgoing Call Barring (Cadeado Eletrônico)”.

Yan Guang Hui – Shenzhen

R&D

Janir Pinheiro – SPO TSD

1.4.1 30-nov-11 - Added description for HSS, ENS and ATS part for creation of SIP and H248 users.

Janir Pinheiro – SPO TSD 1.4.2 11-jan-12 - Scripts for SIP and H248 part were optimized;

- Provisioning part about PABX R2 and PRA part (corporate customers) was separated in

a new document, now this document only covers the provisioning for Retail subscribers.

Janir Pinheiro – SPO TSD 1.4.3 12-Jan-12 - Error found on chapter 1.1 and 1.2 about ADD SBR script , the correct notation is SIP

URI, not TEL URI.

Janir Pinheiro – SPO TSD 1.4.4 18-Jan-12 - Chapter 1.9 - MOD SBR script changed to support MWI feature;

- Chapter 1.12 - Added CBA commands when subscriber has default K value;

- Added Chapter 1.36 – Set Temporary Suspension of Subscriber;

- Added Chapter 1.37 – Remove Temporary Suspension of Subscriber;

- Added Chapter 1.38 – List Temporary Suspension of Subscriber.

- Added Chapter 1.39 – MSAN Users – Change the Access Part and keep the Subscriber

Number

- Added Chapter 1.40 – MSAN Users – Change the Subscriber Number and keep Access

Part

Janir Pinheiro – SPO TSD 1.5 05-Mar-12 - Added Chapter 1.41 – Calling Line Identification Restriction (CLIR);

- Added Chapter 1.42 – Calling Line Identification Restriction Override (RIO);

- Added Chapter 1.43 – List CLIR;

- Added Chapter 1.44 – List RIO;

Janir Pinheiro – SPO TSD 1.6 09-Apr-12 - Changed command: USE ME now uses customized NE name to support dual homing

service;

- Added command: ADD HNNRLI must be added also for TEL URI format to support

Emergency call service;

Janir Pinheiro – SPO TSD 2.0 26-Jun-12 - Chapter 1.2 - Added parameter EMGCN for the command ADD ASBR;

Parameter NETID was changed to support geo-redundancy service.

- Chapter 2 has changed, added new solution based on ENUM index for NCOS.


Provisioning Guide



Janir Pinheiro – SPO TSD 2.1 23-Jul-12 - Changed USE ME command according to the geo-redundancy standard

- Fixed MN range for ADD ASBR command on M2000, chapter 1.2

- Updated SIFCID values for ADD HSIFC command on HSS

- Added parameter EMGCN description on chapter 1.2

- Chapter 2.3.14: MOD SBR command for NCOS 25 has changed (added ENUM index).

Janir Pinheiro – SPO TSD 2.2 13-Sep-12 - Chapter 2.3.21: Changes in NCOS 71 configuration

- Chapter 2.3.22: Changes in NCOS 72 configuration

TanGuangsheng – Shenzhen

R&D

2.3 27-Oct-12 - Add Call-out authority CCOS1 ~ CCOS16 to subscribers.

- MN parameter is optional in the command ADD ASBR.

- MENAME change to ATS in the PBX related commands.

- Add some commands for the NCOS 25.

- Add Chapter 2.4 General Blocking for Retail Subscribers.

Janir Pinheiro – SPO TSD 2.4 28-Jan-13 - Updated SIFCID values for ADD HSIFC command on HSS

- Updated parameter PRI for the command ADD ASBR on M2000 to be in accordance

with SIP digest authentication scheme.

TianZhiGang – Shenzhen

R&D

2.5 14-Mar-13 - Renew chapter “1.14 SIP PBX subscribers”

TianZhiGang – Shenzhen

R&D

2.6 27-Mar-13 - Renew the document associate with PBX service provisioning chapters.

Wangqiujing – China GSRC 2.7 20-May-13 - Update the chapter 1.2, add an IMPORTANT note and three commands at page 26.

Wangqiujing – China GSRC 2.8 24-May-13 - Update the chapter 1.2, add a description to commands ADD ANI at page 26.

Wangqiujing – China GSRC 2.9 11-Jun-13 - Add Chapter 1.45 Apply Number Change Announcement for changed number

Janir Pinheiro – SPO NIS 3.0 31-Jul-13 - Update the chapter 1.12: modify terminal command for activation when subscriber has

default K value to #66#.

- Update the chapter 1.1 and 1.2: add information for referring to “Table 1” when

configuring CSC (call source) parameter for ADD SBR command in ATS.

- “ADD SBR” adds a parameter FLBGRP to differentiate user type.

Janir Pinheiro – SPO NIS 3.1 23-Aug-13 - Added chapters 1.14.1 and 1.14.2: Procedure to configure PBX hunting group when

associated subscriber has valid number (DNH) and virtual number (DLH).


Provisioning Guide



Table of Contents

1 SUBSCRIBER CREATION AND SERVICE CONFIGURATION .................................................................................... 7

1.1 Create New SIP subscriber .................................................................................................................................................... 7

1.2 Create New H.248 subscriber .............................................................................................................................................. 14

1.3 Remove SIP Subscriber ....................................................................................................................................................... 26

1.4 Remove H.248 Subscriber ................................................................................................................................................... 27

1.5 List SIP subscriber database parameters ............................................................................................................................. 28

1.6 List H.248 subscriber database parameters ......................................................................................................................... 29

1.7 Give Conference Service Right to Subscriber ....................................................................................................................... 30

1.8 Call Waiting ........................................................................................................................................................................ 30

1.9 Voice Mail System ............................................................................................................................................................... 31

1.10 Call Forward Unconditional (CFU) ..................................................................................................................................... 33

1.11 Change Subscriber Call Source .......................................................................................................................................... 34

1.12 Outgoing Call Barring (Cadeado Eletrônico) ...................................................................................................................... 35 1.12.1 Command Description ....................................................................................................................................................... 35 1.12.2 Terminal commands ........................................................................................................................................................... 37

1.13 Calling Line Identification Presentation (CLIP) ................................................................................................................... 37

1.14 SIP PBX subscribers ........................................................................................................................................................... 38 1.14.1 PBXSBR with valid subscriber number (DNH) .................................................................................................................... 38 1.14.2 PBXSBR with virtual subscriber number (DLH) .................................................................................................................. 41

1.15 H.248 PBX subscribers ...................................................................................................................................................... 43

1.16 Change Subscriber Restriction Group from 1029 to none 65535 ....................................................................................... 44

1.17 Remove Conference Authority from Subscriber ................................................................................................................ 44

1.18 Remove Call Waiting Authority from Subscriber ............................................................................................................... 45

1.19 Remove CFU from subscriber ............................................................................................................................................ 45

1.20 Change Subscriber Call Source .......................................................................................................................................... 46


Provisioning Guide



1.21 Remove Outgoing Call Barring (Cadeado Eletrônico) from subscriber ............................................................................... 46

1.22 Remove CLIP authority from subscriber ............................................................................................................................ 47

1.23 Remove SIP subscriber from a PBX group ......................................................................................................................... 47

1.24 Remove H.248 Subscriber from a PBX group ..................................................................................................................... 48

1.25 Reset Subscriber Password to default value (Cadeado Eletrônico) .................................................................................... 48

1.26 List Call Waiting ................................................................................................................................................................ 49

1.27 List Conference ................................................................................................................................................................. 50

1.28 List Voice Mail Service ...................................................................................................................................................... 50

1.29 List CFU (Call Forwarding Unconditional) .......................................................................................................................... 51

1.30 List Call Source .................................................................................................................................................................. 52

1.31 List CLIP ............................................................................................................................................................................ 53

1.32 List PBX subscribers .......................................................................................................................................................... 53

1.33 List Outgoing Call Barring (Cadeado Eletrônico) ................................................................................................................ 54

1.34 Register CFU from IMS no subscriber intervention ............................................................................................................ 54

1.35 Support Fax Service .......................................................................................................................................................... 55

1.36 Set Temporary Suspension of subscriber ........................................................................................................................... 56

1.37 Remove Temporary Suspension of subscriber ................................................................................................................... 56

1.38 List Temporary Suspension of subscriber .......................................................................................................................... 57

1.39 MSAN Users – Change the Access Part and keep the Subscriber Number .......................................................................... 57

1.40 MSAN Users – Change the Subscriber Number and keep Access Part ................................................................................ 58

1.41 Calling Line Identification Restriction (CLIR) ...................................................................................................................... 58

1.42 Calling Line Identification Restriction Override (RIO) ........................................................................................................ 59

1.43 List CLIR ............................................................................................................................................................................ 59

1.44 List RIO ............................................................................................................................................................................. 60

1.45 Apply Number Change Announcement for changed number ............................................................................................ 60 1.45.1 Modify a current record for number change announcement: ........................................................................................... 60 1.45.2 Add a new record to apply a number change announcement: ......................................................................................... 61

2 CONFIGURATION ACCORDING TO THE CLASS OF SERVICE (NCOS) ................................................................. 62

2.1 General Rules: .................................................................................................................................................................... 62

2.2 List of NCOS ........................................................................................................................................................................ 63


Provisioning Guide



2.3 Commands for provisioning ................................................................................................................................................ 64 2.3.1 NCOS 1 ................................................................................................................................................................................. 64 2.3.2 NCOS 2 ................................................................................................................................................................................. 64 2.3.3 NCOS 3 ................................................................................................................................................................................. 65 2.3.4 NCOS 4 ................................................................................................................................................................................. 65 2.3.5 NCOS 15 ............................................................................................................................................................................... 65 2.3.6 NCOS 16 ............................................................................................................................................................................... 65 2.3.7 NCOS 17 ............................................................................................................................................................................... 66 2.3.8 NCOS 19 ............................................................................................................................................................................... 66 2.3.9 NCOS 20 ............................................................................................................................................................................... 66 2.3.10 NCOS 21 ............................................................................................................................................................................. 66 2.3.11 NCOS 22 ............................................................................................................................................................................. 66 2.3.12 NCOS 23 ............................................................................................................................................................................. 67 2.3.13 NCOS 24 ............................................................................................................................................................................. 67 2.3.14 NCOS 25 ............................................................................................................................................................................. 67 2.3.15 NCOS 30 ............................................................................................................................................................................. 67 2.3.16 NCOS 31 ............................................................................................................................................................................. 68 2.3.17 NCOS 32 ............................................................................................................................................................................. 68 2.3.18 NCOS 33 ............................................................................................................................................................................. 68 2.3.19 NCOS 34 ............................................................................................................................................................................. 68 2.3.20 NCOS 41 ............................................................................................................................................................................. 69 2.3.21 NCOS 71 ............................................................................................................................................................................. 69 2.3.22 NCOS 72 ............................................................................................................................................................................. 69

2.4 General Blocking for Retail Subscribers ............................................................................................................................... 69 2.4.1 xxxBIO .................................................................................................................................................................................. 69


Provisioning Guide



1 Subscriber Creation and Service Configuration

1.1 Create New SIP subscriber

/****************************AT SPG web portal********************************/

USE ME:MENAME=HSS;

ADD HSDAINF: IMPI="+556239901189", HUSERNAME="+556239901189", PWD="1189", REALM="ims1.gvt.net.br";

ADD HSUB: SUBID="+556239901189", IMPI="+556239901189", IMPU="sip:[email protected]", PBXUSERFLAG=FALSE;

ADD HIMPU: IMPI="+556239901189", IMPU="tel:+556239901189";

SET HVNTPLID: IMPU="sip:[email protected]", VNTPLID=1;

SET HVNTPLID: IMPU="tel:+556239901189", VNTPLID=1;

SET HREGAUTH: IMPU="tel:+556239901189", REGAUTH=TRUE;

SET HREGAUTH: IMPU="sip:[email protected]", REGAUTH=TRUE;

SET HIRS: IRSID=1, IMPULIST="\"sip:[email protected]\"&\"tel:+556239901189\"";

SET HDEFIMPU: IRSID=1,IMPU="sip:[email protected]";

SET HSPSHARE: BASEIMPU="sip:[email protected]", IMPU="tel:+556239901189";

SET HALIASPU: ALIASID=1, IMPULIST="\"sip:[email protected]\"&\"tel:+556239901189\"";

ADD HSIFC:IMPU="sip:[email protected]", SIFCID=621;

ADD HNNRLI:IMPU="sip:[email protected]",RLINDEX=1,RLI="GNA_",RLT=IEEE-802.11a;

ADD HNNRLI:IMPU="tel:+556239901189 ",RLINDEX=1,RLI="GNA_",RLT=IEEE-802.11a;

USE ME:MENAME=ENS;

ADD DNAPTRREC: E164NUM="39901189", ZONENAME="2.6.5.5.e164.arpa", ORDER=10, PREFERENCE=101, FLAGS="U",

SERVICE="E2U+sip", REGEXP="!^(.*)$!sip:+\\[email protected]\;user=phone!";


Provisioning Guide



USE ME:MENAME=ATS;

ADD TP:TEMPLATEIDX=1,TEMPLATENAME="SIP_H248_USERS",DSPIDX=65534,LP=0,CSC=0,UTYPE=IMSSIPUE,VCCFLAG=NO,VTFLAG=NO,

NSCLIP=1,NSSCCA=1,LCO=1,LC=1,LCT=1,NTT=1,ITT=1,INTT=1,IITT=1,IOLT=1,CCO1=1,CCO2=1,CCO3=1,CCO4=1,CCO5=1,CCO6=1,CCO7=1,

CCO8=1,CCO9=1,CCO10=1,CCO11=1,CCO12=1,CCO13=1,CCO14=1,CCO15=1,CCO16=1,IDDCI=1,NTCI=1,LTCI=1,RSC=65535,CIG=4294967

295,OUTRST=NO,INRST=NO,NOAT=20,RINGCOUNT=4,VMAIND=1,VDMAIND=65535,TGRP=65534,TIDHLD=HOLD,TIDCW=PLEASE_WAITIN

G,SCF=NO,LMTGRP=65534,FLBGRP=65535,SLBGRP=65535,COP="0000",G711_64K_A_LAW=1,G729=1,AMR=1,T38=1;

ADD SBR:IMPU="sip:[email protected]", LP=62, CSC=1001, FLBGRP=3, TEMPLATEIDX=1;

Command Description

• USE ME:MENAME=HSS;

Description: Select the Managed Element (ME) to do the provisioning. In this command, it selects the Home

Subscriber Server (HSS).

MENAME (V): This parameter refers to the element to be configured, it can be HSS, ENS, ATS, or M2000.

• ADD HSDAINF: IMPI="+556239901189", HUSERNAME="+556239901189", PWD="1189",

REALM="ims1.gvt.net.br";

Description: Add SIP Digest authentication configuration for this user.

IMPI (V): This is the global ID of this subscriber. In this field, must fill the number in the format + 55 AC number (8

digits)

HUSERNAME (V): The user name, used to register the subscriber on HSS. In this field, must fill the number in the

format + 55 AC number (8 digits). As a default, HUSERNAME value is the same with value of IMPI.

PWD (V): The user password, used to register the subscriber on HSS. This field can be filled by any character

excepting the symbols & “ ‘ and it has a maximum length of 32 digits.

IMPORTANT = this password is only used for registration of subscriber, it has no relation with password for

supplementary services. For SS, refer to Chapter 1.25 - Reset Subscriber Password to default value (Cadeado

Eletrônico).

REALM: (V): This field refers to the IMS domain the subscriber refers to. It can assume the follow parameters:

SPO ims1.gvt.net.br

RJO ims1.gvt.net.br

CTA ims2.gvt.net.br

MGA ims2.gvt.net.br

BHE ims3.gvt.net.br

RCE ims3.gvt.net.br

• ADD HSUB: SUBID="+556239901189", IMPI="+556239901189", IMPU="sip:[email protected]",

PBXUSERFLAG=FALSE;


Provisioning Guide



Description: Add an IMS subscription, specify an ID for the IMS subscription, and it is optional to add an IMPI and

the associated IMPU for the IMS subscription in the HSS service database.

SUBID (V): This is a unique identified on the HSS. In this field, must fill the number in the format +55 AC number (8

digits). As a default, SUBID value is the same with value of IMPI.


digits), the parameter must be defined by running ADD HSDAINF first.

IMPU (V): The IMPU value must be in SIP URI or TEL URI format. The value of the parameter is case sensitive.

Tel URI must fill the number in the format tel:+55 AC number(8 digits)

Sip URI must fill the number and character in the format sip:+55 AC number(8 digits)@domain.

PBXUSERFLAG (V): This is the PBX user flag. This parameter is optional. The default value is FALSE, if the subscriber

has the PBX service (chapter 1.35), this value must be change to TRUE.

Value range: TRUE (PBXUSER), FALSE (NOTPBXUSER)

• ADD HIMPU: IMPI="+556239901189", IMPU="tel:+556239901189";

Description: Add an IMPU for an existing IMPI to the HSS service database.


digits), the parameter must be defined by running ADD HSDAINF.





• SET HVNTPLID: IMPU="tel:+556239901189", VNTPLID=1;

Description: It sets the visited network template ID for the specified IMPU in the HSS service database. If the IMPU

belongs to an IRS, the other IMPUs in the IRS are automatically registered with the same visited network template

ID.




VNTPLID (F): This is an index value; this parameter must be set by using the ADD HVNTPL command before it is

referred to here. GVT default value is “1”, there is only one value for one IMS site.

• SET HREGAUTH: IMPU="tel:+556239901189", REGAUTH=TRUE;

• SET HREGAUTH: IMPU="sip:[email protected]", REGAUTH=TRUE;

Description: It sets the registration authority for the specified IMPU in the HSS service database.





Provisioning Guide



REGAUTH (V): The value TRUE means that the registration is allowed; the value FALSE means that the registration is

not allowed. The GVT default value is TRUE.

Value range: FALSE (False), TRUE(True)

• SET HIRS: IRSID=1, IMPULIST="\"sip:[email protected]\"&\"tel:+556239901189\"";

Description : It set the implicit registration set (IRS) attribute for multiple IMPUs in the HSS service database. In the

IRS, if a number registration is successful, then all the other numbers automatically registered.

IRSID (F): This parameter is unique on the HSS and must be filled as “1” in all the records. The value 0 means

deleting the specified IMPU from the IRS.

IMPULIST (V): The IMPU list can contain up to 10 IMPUs separated by &, The IMPU must be set by running the

operation ADD HSUB, or ADD HIMPU before it is referred to here. The IMPU value must be in SIP URI or TEL URI

format.

Example:

IMPULIST="\"sip:[email protected]\"&\"tel:+556239901189\""; Means two different names

for the same subscriber

IMPULIST="\"sip:[email protected]\"&\"tel:+556239901189\"&\"sip:[email protected]\"

"; Means three different names for the same subscriber.

• SET HDEFIMPU: IRSID=1,IMPU="sip:[email protected]";

Description: It sets the default IMPU for the specified implicit registration set (IRS) in the HSS service database. The

default IMPU provides a default value for service processing at the network side. It is used when required for

service processing.

IRSID (F): This parameter is unique on the HSS and must be filled as “1” in all the records.




• SET HSPSHARE: BASEIMPU="sip:[email protected]", IMPU="tel:+556239901189";

Description: It shares a service profile between an IMPU and the specified base IMPU in the HSS service database.

For example, If A and B share the service profile, then A and B are the same for CSCF.

BASEIMPU (V): The base IMPU whose associated service profile is to be shared. The IMPU value must be in SIP URI

or TEL URI format




• SET HALIASPU: ALIASID=1, IMPULIST="\"sip:[email protected]\"&\"tel:+556239901189\"";


Provisioning Guide



Description: This operation to set an alias group ID for multiple IMPUs in the HSS service database. The alias group

refers to a collection of the IMPUs that share the service profile in an implicit registration set (IRS). You can fulfill one

of the following tasks using the command. For example, in the alias group contains A and B, then A and B are the

same for AS.

ALIASID (F): This parameter is unique on the HSS and must be filled as “1” in all the records.

IMPULIST (V): An IMPU list can contain up to 10 IMPUs separated by &, The IMPUs contained in an IMPU list must

be set before they are referred to here. They are obtainable by running the LST HSUB operation. The IMPU value

must be in SIP URI or TEL URI format. The value of the parameter is case sensitive.

• ADD HSIFC:IMPU="sip:[email protected]", SIFCID=621;

Description (V): Add a shared initial filter criteria (iFC) set for the specified IMPU. Each IMPU can be configured with

a maximum of eight shared iFC sets.

IMPU(V): The IMPU value must be in SIP URI or TEL URI format. The value of the parameter is case sensitive.

Tel URI must fill the number in the format tel: +55 AC number(8 digits).


SIFCID (V): This is an index value. GVT standard is XX+P, where XX is according to the IMS Site: 41+P (CTA), 44+P

(MGA), 11+P (SPO), 21+P (RJO), 31+P (BHE) and 81+P (RCE).

P can assume the follow values:

1 - For intra-office traffic, used for Retail and Corporate, ex: 621

7- For traffic terminated on UGC, used only for Corporate, ex: 627

8 - For traffic terminated on BCF, used only for Vox IP service, ex 628

For more details about this parameter, please refer to the HLD documentation, table 7-2 – Share IFC Template list

• ADD HNNRLI:IMPU="sip:[email protected]",RLINDEX=1,RLI="GNA_",RLT=IEEE-802.11a;

Description: It is used to add a reference location data record for the specified IMPU to the HSS service database.

PS: FOR EMERGENCY CALL SERVICES, IT’S MANDATORY TO ADD THIS COMMAND FOR BOTH FORMATS, SIP URI

AND TEL URI.




RLINDEX (V): this is an index for this command. A subscriber can have up to 5 different location records, but for GVT

project, the value is “1” for all subscribers.

RLI (V): The field RLI (Reference Location Information) is used to mark the city where the subscriber belongs to, and

on E-CSCF to determine the emergency number (or numbers) that attends this city. The rule adopted for this field is

the Anatel notation for the city name, and using a fixed length of 4 digits, filling the last one with "_" if it doesn't

used.

Examples:

Curitiba: CTA_

São Paulo: SPO_


Provisioning Guide



Alto Rolante: ALRO

Aceguá: ACEG

RLT (F): It is the type of the reference location information. GVT default value is IEEE-802.11a.

• USE ME:MENAME=ENS;

Description: Select the Managed Element (ME) to do the provisioning. In this command, it selects the ENUM Server

(ENS).


• ADD DNAPTRREC: E164NUM="39901189", ZONENAME="2.6.5.5.e164.arpa", ORDER=10, PREFERENCE=101,

FLAGS="U", SERVICE="E2U+sip", REGEXP="!^(.*)$!sip:+\\[email protected]\;user=phone!";

Description: Add a generic NAPTR resource record for an E.164 number.

PS: This configuration is not suitable for VoxIP services, these services are still under analysis together with GVT

engineering team, and we will provide a procedure in a new chapter later.

E164NUM (V): Specifies an E.164 number or number segment. GVT specified format is a number (8digits).

ZONENAME (V): Specifies the name of a zone to which the record belongs. This parameter must be defined by the

ADD DZONE command before it is referenced here. GVT specified format is “X.X.5.5.e164.arpa”, it is the E.164

format and must be understand like this:

2.6 - > means the area code from right to left, so in this case, AC is 62

5.5 -> means the country code from right to left, so in this case, country code is 55

For Curitiba, the ZONENAME will be 1.4.5.5.e164.arpa, for Porto Alegre will be 1.5.5.5.e164.arpa and so on.

ORDER (F): Specifies the order of a NAPTR resource record. A smaller value represents a higher level of order. GVT

specified value is 10

PREFERENCE (F): Specifies the preference of a NAPTR resource record. A smaller value represents a higher level of

preference. GVT specified value is 101.

FLAGS(F): Specifies the flag for querying NAPTR resource records on a terminal. GVT default value is U.

SERVICE(F): Specifies the protocol complied with when a regular expression is mapped to a URI address. GVT default

value is E2U+sip.

REGEXP(V): Specifies the rules for mapping an E.164 number to a URI address. GVT default value is the

“!^(.*)$!sip:+\\[email protected]\;user=phone!” format. This field refers to the IMS domain the subscriber refers

to. It can assume the follow parameters:

SPO !^(.*)$!sip:+\\[email protected]\;user=phone!

RJO !^(.*)$!sip:+\\[email protected]\;user=phone!


Provisioning Guide



CTA !^(.*)$!sip:+\\[email protected]\;user=phone!

MGA !^(.*)$!sip:+\\[email protected]\;user=phone!

BHE !^(.*)$!sip:+\\[email protected]\;user=phone!

RCE !^(.*)$!sip:+\\[email protected]\;user=phone!

• USE ME:MENAME=ATS;

Description: Select the Managed Element (ME) to do the provisioning. In this command, it selects the Application

for Telephony Services (ATS).


• ADD TP:TEMPLATEIDX=1,TEMPLATENAME="SIP_H248_USERS",DSPIDX=65534,LP=0,CSC=0,UTYPE=IMSSIPUE,

VCCFLAG=NO,VTFLAG=NO,NSCLIP=1,NSSCCA=1,LCO=1,LC=1,LCT=1,NTT=1,ITT=1,INTT=1,IITT=1,IOLT=1,CCO1=1,CC

O2=1,CCO3=1,CCO4=1,CCO5=1,CCO6=1,CCO7=1,CCO8=1,CCO9=1,CCO10=1,CCO11=1,CCO12=1,CCO13=1,CCO14=

1,CCO15=1,CCO16=1,IDDCI=1,NTCI=1,LTCI=1,RSC=65535,CIG=4294967295,OUTRST=NO,INRST=NO,NOAT=20,RING

COUNT=4,VMAIND=1,VDMAIND=65535,TGRP=65534,TIDHLD=HOLD,TIDCW=PLEASE_WAITING,SCF=NO,LMTGRP=6

5534,FLBGRP=65535,SLBGRP=65535,COP="0000",G711_64K_A_LAW=1,G729=1,AMR=1,T38=1;

• ADD TP:TEMPLATEIDX=2,TEMPLATENAME="R2_PRA_USERS",DSPIDX=65534,LP=0,CSC=0,UTYPE=PSTN,






Description: This command is used to add a Subscriber Data Template to the configuration database. Each

Subscriber Data Template is identified by a unique template index. You can use the same template to define

subscribers with some common attributes.

TEMPLATEIDX (V): It defines the index of the Subscriber Data Template. In GVT project, we will use two different

data templates:

Index 1: for SIP / h248 subscribers

Index 2: for R2 / PRA subscribers

PS: For some parameters (For example: LP and CS), because it will be changed for each subscriber in the

command ADD SBR, it will not be needed to be included in the template, so you can define the template with

standard values.

NSCLIP (F): It specifies the Calling Line Identification Presentation (CLIP) service right of a subscriber. This parameter

is one of the elements Supplement Service Right. It is the default service GVT. The value is 1.

NSSCCA (F): It specifies the Collect Call(SCCA) service right of a subscriber. This parameter is one of the elements

Supplement Service Right. It is the default service GVT. The value is 1.


Provisioning Guide



Call-out authority (V): It specifies the call-out authority. By default, the system configures the following call-out

authorities for the subscriber data template: intra office, local, local toll, national toll, intra-Centrex, outgoing

Centrex, customized Operator and customized supply service.

Call-in authority (V): It specifies the call-in authority. By default, the system configures the following call-in

authorities for the subscriber data template: International call-in authority, National Toll call-in authority and Local

Toll call-in authority.

CODEC (V): It specifies the Supported Codec. By default, GVT system need support G711_64K_A_LAW,

G711_64K_U_LAW, G722, G723, G729, and AMR. The value “1” means that the codec is set, “0” means that it is not

set.

VMAIND (F): This is the Voice mailbox address index; it specifies the index of a voice mailbox address for a specified

subscriber. It must be defined by running ADD VOICEMAIL in the MML Command - ATS9900 window before being

referenced here.GVT value is 1.

• ADD SBR:IMPU="sip:[email protected]", LP=62, CSC=1001, FLBGRP=3, TEMPLATEIDX=1;

Description: It is used to add an ATS subscriber and set the related service rights and basic attributes of the

subscriber in the configuration database.

IMPU (V): It specifies the IMPU of a specific subscriber. It can be a TEL URI or a SIP URI. The rules for setting the

parameter are as follows:

To configure an IMPU in SIP URI format, type a string such as sip:[email protected] or

[email protected]

To configure an IMPU in TEL URI format, type a string such as tel:+ 556239901176 or +556239901176

LP (V): It specifies the local DN set of a subscriber. The value 65534 is a wildcard. When the IMPU is in local TEL URI

format, such as tel: 39901176, this parameter and IMPU together identify a subscriber. In this case, the parameter

must be defined by running ADD LDNSET in the MML Command - ATS9900 window before being referenced here.

FLBGRP (V): It is used to indicate the user access type. For SIP user, the value is 3.

CSC (V): It specifies the call source of a subscriber. The parameter must be defined by running ADD CALLSRC in the

MML Command - ATS9900 window before being referenced here.

Please refer to the “Table 1” for all call source codes currently used on IMS Network before adding this command.

TEMPLATEIDX (V): It specifies the index of the Subscriber Data Template. The parameter must be defined by running

ADD TP before being referenced here.

1.2 Create New H.248 subscriber

/****************************AT SPG web portal********************************/

USE ME:MENAME=HSS;

ADD HSDAINF: IMPI="+556239901189", HUSERNAME="+556239901189", PWD="1189", REALM="ims1.gvt.net.br";


Provisioning Guide



ADD HSUB: SUBID="+556239901189", IMPI="+556239901189", IMPU="sip:[email protected]", PBXUSERFLAG=FALSE;

ADD HIMPU: IMPI="+556239901189", IMPU="tel:+556239901189";


SET HVNTPLID: IMPU="tel:+556239901189", VNTPLID=1;

SET HREGAUTH: IMPU="tel:+556239901189", REGAUTH=TRUE;

SET HREGAUTH: IMPU="sip:[email protected]", REGAUTH=TRUE;

SET HIRS: IRSID=1, IMPULIST="\"sip:[email protected]\"&\"tel:+556239901189\"";

SET HDEFIMPU: IRSID=1,IMPU="sip:[email protected]";

SET HSPSHARE: BASEIMPU="sip:[email protected]", IMPU="tel:+556239901189";

SET HALIASPU: ALIASID=1, IMPULIST="\"sip:[email protected]\"&\"tel:+556239901189\"";


ADD HNNRLI:IMPU="sip:[email protected]",RLINDEX=1,RLI="GNA_",RLT=IEEE-802.11a;

ADD HNNRLI:IMPU="tel:+556239901189",RLINDEX=1,RLI="GNA_",RLT=IEEE-802.11a;

USE ME:MENAME=ENS;

ADD DNAPTRREC: E164NUM="39901189", ZONENAME="2.6.5.5.e164.arpa", ORDER=10, PREFERENCE=101, FLAGS="U",

SERVICE="E2U+sip", REGEXP="!^(.*)$!sip:+\\[email protected]\;user=phone!";

USE ME:MENAME=ATS;

ADD TP:TEMPLATEIDX=1,TEMPLATENAME="SIP_H248_USERS",DSPIDX=65534,LP=0,CSC=0,UTYPE=IMSSIPUE,VCCFLAG=NO,VTFLAG=NO,

NSCLIP=1,NSSCCA=1,LCO=1,LC=1,LCT=1,NTT=1,ITT=1,INTT=1,IITT=1,IOLT=1,CCO1=1,CCO2=1,CCO3=1,CCO4=1,CCO5=1,CCO6=1,CCO7=1,

CCO8=1,CCO9=1,CCO10=1,CCO11=1,CCO12=1,CCO13=1,CCO14=1,CCO15=1,CCO16=1,IDDCI=1,NTCI=1,LTCI=1,RSC=65535,CIG=4294967

295,OUTRST=NO,INRST=NO,NOAT=20,RINGCOUNT=4,VMAIND=1,VDMAIND=65535,TGRP=65534,TIDHLD=HOLD,TIDCW=PLEASE_WAITIN

G,SCF=NO,LMTGRP=65534,FLBGRP=65535,SLBGRP=65535,COP="0000",G711_64K_A_LAW=1,G729=1,AMR=1,T38=1;

ADD SBR:IMPU="sip:[email protected]", LP=62, CSC=1001, FLBGRP=6, TEMPLATEIDX=1;

USE ME:MENAME=M2000;

ADD ASBR: SOFTXIP="10.140.72.224", PUI="sip:[email protected]", PRI="+556239901189", REGTP=SINGLE, DID=ESL,

MN=22, EID="10.140.72.130:2944", TID="0", HNID="HNID01", NETID="VNID01", NETINFO="GNA_", PHNCON="AC62", DIGMAP=0,

PWD="1189", EMGCN=”EMG01”, DP=YES, DR=YES, CONF=0;

Note: The parameter MN (Module Number) is an optional parameter, if it is omitted, the AGCF will

automatically distribute the new subscriber based on its internal logic. i.e. The system invoking this interface

doesn’t need to input this parameter during creating new subscribers, unless it has some special reason to

manually assign the new subscriber to a specific module.

If the number of MGW exceeds the capability of the module, the system will return the 268034, and the

description is “The table exceeds the capability of the module”.

Command Description


Provisioning Guide







• ADD HSDAINF: IMPI="+556239901189", HUSERNAME="+556239901189", PWD="1189",

REALM="ims1.gvt.net.br";

Description: Add SIP Digest authentication configuration for this user.


digits)

HUSERNAME (V): The user name, used to register the subscriber on HSS. In this field, must fill the number in the

format + 55 AC number (8 digits). As a default, HUSERNAME value is the same with value of IMPI.

PWD (V): The user password, used to register the subscriber on HSS. This field can be filled by any character

excepting the symbols & “ ‘ and it has a maximum length of 32 digits.

IMPORTANT = this password is only used for registration of subscriber, it has no relation with password for

supplementary services. For SS, refer to Chapter 1.25 - Reset Subscriber Password to default value (Cadeado

Eletrônico).

EMGCN (V): Emergence Call Group Name. It specifies the name of the emergence call group that the subscriber to

be added belongs to. When this parameter is specified for a subscriber, the subscriber will be able to call the

emergency numbers defined for the specified group. GVT default value is EMG01.

REALM: (V): This field refers to the IMS domain the subscriber refers to. It can assume the follow parameters:

SPO ims1.gvt.net.br

RJO ims1.gvt.net.br

CTA ims2.gvt.net.br

MGA ims2.gvt.net.br

BHE ims3.gvt.net.br

RCE ims3.gvt.net.br

• ADD HSUB: SUBID="+556239901189", IMPI="+556239901189", IMPU="sip:[email protected]",

PBXUSERFLAG=FALSE;

Description: Add an IMS subscription, specify an ID for the IMS subscription, and it is optional to add an IMPI and

the associated IMPU for the IMS subscription in the HSS service database.

SUBID (V): This is a unique identified on the HSS. In this field, must fill the number in the format +55 AC number (8

digits). As a default, SUBID value is the same with value of IMPI.


digits), the parameter must be defined by running ADD HSDAINF first.


Provisioning Guide






PBXUSERFLAG (V): This is the PBX user flag. This parameter is optional. The default value is FALSE, if the subscriber

has the PBX service (chapter 1.35), this value must be change to TRUE.

Value range: TRUE (PBXUSER), FALSE (NOTPBXUSER)

• ADD HIMPU: IMPI="+556239901189", IMPU="tel:+556239901189";

Description: Add an IMPU for an existing IMPI to the HSS service database.


digits), the parameter must be defined by running ADD HSDAINF.




• SET HVNTPLID: IMPU="sip:[email protected]", VNTPLID=1;

• SET HVNTPLID: IMPU="tel:+556239901189", VNTPLID=1;

Description: It sets the visited network template ID for the specified IMPU in the HSS service database. If the IMPU

belongs to an IRS, the other IMPUs in the IRS are automatically registered with the same visited network template

ID.


Tel URI must fill the number in the format tel: +55 AC number (8 digits).


VNTPLID (F): This is an index value; this parameter must be set by using the ADD HVNTPL command before it is

referred to here. GVT default value is “1”, there is only one value for one IMS site.

• SET HREGAUTH: IMPU="tel:+556239901189", REGAUTH=TRUE;

• SET HREGAUTH: IMPU="sip:[email protected]", REGAUTH=TRUE;

Description: It sets the registration authority for the specified IMPU in the HSS service database.




REGAUTH (V): The value TRUE means that the registration is allowed; the value FALSE means that the registration is

not allowed. The GVT default value is TRUE.

Value range: FALSE (False), TRUE(True)

• SET HIRS: IRSID=1, IMPULIST="\"sip:[email protected]\"&\"tel:+556239901189\"";


Provisioning Guide



Description : It set the implicit registration set (IRS) attribute for multiple IMPUs in the HSS service database. In the

IRS, if a number registration is successful, then all the other numbers automatically registered.

IRSID (F): This parameter is unique on the HSS and must be filled as “1” in all the records. The value 0 means

deleting the specified IMPU from the IRS.

IMPULIST (V): The IMPU list can contain up to 10 IMPUs separated by &, The IMPU must be set by running the

operation ADD HSUB, or ADD HIMPU before it is referred to here. The IMPU value must be in SIP URI or TEL URI

format.

Example:

IMPULIST="\"sip:[email protected]\"&\"tel:+556239901189\""; Means two different names

for the same subscriber

IMPULIST="\"sip:[email protected]\"&\"tel:+556239901189\"&\"sip:[email protected]\"

"; Means three different names for the same subscriber.

• SET HDEFIMPU: IRSID=1,IMPU="sip:[email protected]";

Description: It sets the default IMPU for the specified implicit registration set (IRS) in the HSS service database. The

default IMPU provides a default value for service processing at the network side. It is used when required for

service processing.

IRSID (F): This parameter is unique on the HSS and must be filled as “1” in all the records.




• SET HSPSHARE: BASEIMPU="sip:[email protected]", IMPU="tel:+556239901189";

Description: It shares a service profile between an IMPU and the specified base IMPU in the HSS service database.

For example, If A and B share the service profile, then A and B are the same for CSCF.

BASEIMPU (V): The base IMPU whose associated service profile is to be shared. The IMPU value must be in SIP URI

or TEL URI format




• SET HALIASPU: ALIASID=1, IMPULIST="\"sip:[email protected]\"&\"tel:+556239901189\"";

Description: This operation to set an alias group ID for multiple IMPUs in the HSS service database. The alias group

refers to a collection of the IMPUs that share the service profile in an implicit registration set (IRS). You can fulfill one

of the following tasks using the command. For example, in the alias group contains A and B, then A and B are the

same for AS.

ALIASID (F): This parameter is unique on the HSS and must be filled as “1” in all the records.


Provisioning Guide



IMPULIST (V): An IMPU list can contain up to 10 IMPUs separated by &, The IMPUs contained in an IMPU list must

be set before they are referred to here. They are obtainable by running the LST HSUB operation. The IMPU value

must be in SIP URI or TEL URI format. The value of the parameter is case sensitive.







SIFCID (V): This is an index value. GVT standard is XX+P, where XX is according to the IMS Site: 41+P (CTA), 44+P

(MGA), 11+P (SPO), 21+P (RJO), 31+P (BHE) and 81+P (RCE).

P can assume the follow values:




For more details about this parameter, please refer to the HLD documentation, table 7-2 – Share IFC Template list

• ADD HNNRLI:IMPU="sip:[email protected]",RLINDEX=1,RLI="GNA_",RLT=IEEE-802.11a;

Description: It is used to add a reference location data record for the specified IMPU to the HSS service database.

PS: FOR EMERGENCY CALL SERVICES, IT’S MANDATORY TO ADD THIS COMMAND FOR BOTH FORMATS, SIP URI

AND TEL URI.




RLINDEX (V): this is an index for this command. A subscriber can have up to 5 different location records, but for GVT

project, the value is “1” for all subscribers.

RLI (V): The field RLI (Reference Location Information) is used to mark the city where the subscriber belongs to, and

on E-CSCF to determine the emergency number (or numbers) that attends this city. The rule adopted for this field is

the Anatel notation for the city name, and using a fixed length of 4 digits, filling the last one with "_" if it doesn't

used.

Examples:

Curitiba: CTA_

São Paulo: SPO_

Alto Rolante: ALRO

Aceguá: ACEG

RLT (F): It is the type of the reference location information. GVT default value is IEEE-802.11a.



Provisioning Guide




(ENS).


• ADD DNAPTRREC: E164NUM="39901189", ZONENAME="2.6.5.5.e164.arpa", ORDER=10, PREFERENCE=101,

FLAGS="U", SERVICE="E2U+sip", REGEXP="!^(.*)$!sip:+\\[email protected]\;user=phone!";

Description: Add a generic NAPTR resource record for an E.164 number.

PS: This configuration is not suitable for VoxIP services, these services are still under analysis together with GVT

engineering team, and we will provide a procedure in a new chapter later.

E164NUM (V): Specifies an E.164 number or number segment. GVT specified format is a number (8digits).


ADD DZONE command before it is referenced here. GVT specified format is “X.X.5.5.e164.arpa”, it is the E.164

format and must be understand like this:

2.6 - > means the area code from right to left, so in this case, AC is 62

5.5 -> means the country code from right to left, so in this case, country code is 55

For Curitiba, the ZONENAME will be 1.4.5.5.e164.arpa, for Porto Alegre will be 1.5.5.5.e164.arpa and so on.

ORDER (F): Specifies the order of a NAPTR resource record. A smaller value represents a higher level of order. GVT

specified value is 10

PREFERENCE (F): Specifies the preference of a NAPTR resource record. A smaller value represents a higher level of

preference. GVT specified value is 101.

FLAGS(F): Specifies the flag for querying NAPTR resource records on a terminal. GVT default value is U.

SERVICE(F): Specifies the protocol complied with when a regular expression is mapped to a URI address. GVT default

value is E2U+sip.

REGEXP(V): Specifies the rules for mapping an E.164 number to a URI address. GVT default value is the

“!^(.*)$!sip:+\\[email protected]\;user=phone!” format. This field refers to the IMS domain the subscriber refers

to. It can assume the follow parameters:

SPO !^(.*)$!sip:+\\[email protected]\;user=phone!

RJO !^(.*)$!sip:+\\[email protected]\;user=phone!

CTA !^(.*)$!sip:+\\[email protected]\;user=phone!

MGA !^(.*)$!sip:+\\[email protected]\;user=phone!

BHE !^(.*)$!sip:+\\[email protected]\;user=phone!


Provisioning Guide



RCE !^(.*)$!sip:+\\[email protected]\;user=phone!





• ADD TP:TEMPLATEIDX=1,TEMPLATENAME="SIP_H248_USERS",DSPIDX=65534,LP=0,CSC=0,UTYPE=IMSSIPUE,






• ADD TP:TEMPLATEIDX=2,TEMPLATENAME="R2_PRA_USERS",DSPIDX=65534,LP=0,CSC=0,UTYPE=PSTN,






Description: This command is used to add a Subscriber Data Template to the configuration database. Each

Subscriber Data Template is identified by a unique template index. You can use the same template to define

subscribers with some common attributes.

TEMPLATEIDX (V): It defines the index of the Subscriber Data Template. In GVT project, we will use two different

data templates:

Index 1: for SIP / h248 subscribers

Index 2: for R2 / PRA subscribers

PS: For some parameters (For example: LP and CS), because it will be changed for each subscriber in the

command ADD SBR, it will not be needed to be included in the template, so you can define the template with

standard values.

NSCLIP (F): It specifies the Calling Line Identification Presentation (CLIP) service right of a subscriber. This parameter

is one of the elements Supplement Service Right. It is the default service GVT. The value is 1.

NSSCCA (F): It specifies the Collect Call(SCCA) service right of a subscriber. This parameter is one of the elements

Supplement Service Right. It is the default service GVT. The value is 1.

Call-out authority (V): It specifies the call-out authority. By default, the system configures the following call-out

authorities for the subscriber data template: intra office, local, local toll, national toll, intra-Centrex, outgoing

Centrex, customized Operator and customized supply service.


Provisioning Guide



Call-in authority (V): It specifies the call-in authority. By default, the system configures the following call-in

authorities for the subscriber data template: International call-in authority, National Toll call-in authority and Local

Toll call-in authority.

CODEC (V): It specifies the Supported Codec. By default, GVT system need support G711_64K_A_LAW,

G711_64K_U_LAW, G722, G723, G729, and AMR. The value “1” means that the codec is set, “0” means that it is not

set.

VMAIND (F): This is the Voice mailbox address index; it specifies the index of a voice mailbox address for a specified

subscriber. It must be defined by running ADD VOICEMAIL in the MML Command - ATS9900 window before being

referenced here.GVT value is 1.

• ADD SBR:IMPU="sip:[email protected]", LP=62, CSC=1001, FLBGRP=6, TEMPLATEIDX=1;

Description: It is used to add an ATS subscriber and set the related service rights and basic attributes of the

subscriber in the configuration database.




[email protected]


LP (V): It specifies the local DN set of a subscriber. The value 65534 is a wildcard. When the IMPU is in local TEL URI

format, such as tel: 39901176, this parameter and IMPU together identify a subscriber. In this case, the parameter

must be defined by running ADD LDNSET in the MML Command - ATS9900 window before being referenced here.

CSC (V): It specifies the call source of a subscriber. The parameter must be defined by running ADD CALLSRC in the

MML Command - ATS9900 window before being referenced here.

Please refer to the “Table 1” for all call source codes currently used on IMS Network before adding this command.

FLBGRP (V): It is used to indicate the user access type. For H.248 user, the value is 6.

TEMPLATEIDX (V): It specifies the index of the Subscriber Data Template. The parameter must be defined by running

ADD TP before being referenced here.

• USE ME:MENAME=M2000;

Description: Select the Managed Element (ME) to do the provisioning. In this command, it selects the

Management Server M2000.


• ADD ASBR: SOFTXIP="10.140.72.224", PUI="sip:[email protected]", PRI="+556239901189",

REGTP=SINGLE, DID=ESL, MN=22, EID="10.140.72.130:2944", TID="0", HNID="HNID01", NETID="VNID01",

NETINFO="GNA_", PHNCON="AC62", DIGMAP=0, PWD="1189", EMGCN=”EMG01”, DP=YES, DR=YES, CONF=0;

Description: It is a configuration command, and is used to add A-CSCF subscriber data in the configuration

database. This function is used to configure functions provided by the AGCF.


Provisioning Guide



SOFTXIP (V): The IP address is the IP of AGCF site. This value is filled according to the actual situation.

PUI(V):Public User ID,The user ID used outside the IMS Core is the public user ID that is used to communicate with

others. The value of this parameter must be the same as the user ID defined on the HSS and ATS. From now on,

this will be the “facility” name of the GVT subscriber. It must have the format according to the example below

(from the GVT HLD):

Site User Type IMPU1 (TEL URI) IMPU2 (SIP URI)

SPO User tel: E.164 sip:[email protected]

RJO User tel: E.164 sip:[email protected]

CTA User tel: E.164 sip:[email protected]

MGA User tel: E.164 sip:[email protected]

BHE User tel: E.164 sip:[email protected]

RCE User tel: E.164 sip:[email protected]

PRI (V): The private user ID for IMS subscribers is a globally unique identity defined by a home network carrier. It is

used to uniquely identify a piece of subscription in the home network from a network perspective. The value of

this parameter must be the same as the user ID defined on the HSS and ATS. In GVT Network Design, we will use

the PUI notation without the sip: suffix and domain, it’s according E.164 standard.

Example: PUI="sip:[email protected]", PRI="+556239901189"

REGTP (F): Register type. It will be SINGLE register in all situations. This parameter will be fixed.

DID (F): Port type. It will be ESL in all situations. This parameter will be fixed.

MN (V): Module Number, It specifies the module number of the UACU on which the subscriber is configured. It is

valid only for ESL subscribers. The value range is 22-101. The value of the parameter must be defined in ADD BRD

before being referenced.

EID (V): Equipment ID. This is the identification of the Access Node inside the IMS. The notation is the IP address

of the AG(MSAN) + “:” + the signaling port. Example: 10.140.72.130:2944, where 10.140.72.130 is the IP of

Keymile MSAN and 2944 is the signaling port. We can compare it as the V5 ID of the V5 interface.

TID (V): Terminal ID. It specifies the physical port number of the MG to which the ESL subscriber belongs. It’s

the identification of the subscriber port for the corresponding Equipment ID. We can compare it to the L3ADDR on

V5 interface.

HNID (V): Home Network ID. This is the Index of the Home Network database. We recommend to create a index

like the table below, in case of GVT intends to set up an additional home network in the future. More information

about Home Networks, please refer to the documentation.

Site Home Network Name (for

use on ADD ASBR)

Home Network ID

SPO HNID01 ims1.gvt.net.br


Provisioning Guide



RJO HNID01 ims1.gvt.net.br

CTA HNID02 ims2.gvt.net.br

MGA HNID02 ims2.gvt.net.br

BHE HNID03 ims3.gvt.net.br

RCE HNID03 ims3.gvt.net.br

NETID (V): Visited Network ID. This is the Index of the Visited Network database. We recommend creating an

index like the table below, in case of GVT intends to set up a different Visited Network in the future. More

information about Visited Networks, please refer to the documentation.

PS: VNID in GVT Network topology is directly associated to the number of AGCFs in the network.

Site Visited Network Name (for

use on ADD ASBR)

Visited Network ID

SPO VNID01 agcf1-spo7.ims1.gvt.net.br

RJO VNID02 agcf1-rjo6.ims1.gvt.net.br

CTA VNID01 agcf1-cta7.ims2.gvt.net.br

MGA VNID02 agcf1-mga4.ims2.gvt.net.br

BHE VNID01 agcf1-bhe4.ims3.gvt.net.br

RCE VNID02 agcf1-rce3.ims3.gvt.net.br

If a new AGCF must be installed in the future, just need to follow the sequence name, for example, for CTA:

Site Visited Network Name (for

use on ADD ASBR)

Visited Network ID

CTA VNID02 agcf2-cta7.ims2.gvt.net.br

NETINFO (V): This parameter is related to the Access Network Information (ANI), and it’s used to determine

the location-info of the subscriber. This information appears on the INVITE message and it’s used for E-CSCF to

determine the emergency number (or numbers) that attends this city. The rule adopted for this field is the Anatel

notation for the city name, and using a fixed length of 4 digits, filling the last one with "_" if it doesn't used.


Provisioning Guide



Examples:

Curitiba: CTA_

São Paulo: SPO_

Alto Rolante: ALRO

Aceguá: ACEG

PS: This information must be the same as configured on the parameter RLI when creating the Reference Location

Information for an IMPU on HSS Server (item 2 below).

PHNCON (V): Phone context. It’s used to fill the A number to match the IMPU standard. For GVT Project, we use

Phone Context Database to add the information “+55AC” in front of the original A number. Example:

Curitiba-PR will have the PHNCON = AC41. Inside Phone Context table, AC41 indexes to the information “+5541”

Goiania-GO will have the PHNCON = AC62. Inside Phone Context table, AC62 indexes to the information “+5562”

DIGMAP (V): Digitmap index.

PWD (V): It specifies the password used for authentication on HSS. This password has no relation with the

password used on supplementary services. The PWD value is the same with the PWD of “ADD HSDAINF”.

EMGCN (V): It specifies the Emergency call group. Basically, it defines some dialing rules for emergency calls (like

digitmap, other). For this project, there is no need to define a new one, we will keep this parameter as EMG01.

DP (V): Download profile from AS, keep it as default.

DR (V): Send registration subscription, keep it as default.

CONF (F): Conference URI index. It specifies the conference URI index used for applying for a conference.

Specifically, the subscriber uses the domain name of the MRF server associated with the conference URI index to

instruct the AS to apply for conference resources. This parameter is fixed as 0.

IMPORTANT: Before we add subscribers’ information for new cities, we may need these commands to add

parameters for referenced:

• ADD VNID: NAME=" VNID01", VNID=" agcf2-gna9.ims2.gvt.net.br ";

Description: It is a configuration command, and is used to add a visited network ID in the configuration database.

This function is used to configure functions provided by the AGCF.

VNID (V): It is the domain name of the AGCF.

• ADD ANI: NAME=" GNA_",ANI="GNA_";

Description: this is used to add an access network ID in the configuration database. When we added a new MGW

to the network, we need to use this command to add the MGW information on AGCF, normally; we use at least

one MGW for each city.

NAME (V): this indicates an access network name provide for a AGCF subscriber. It is referenced by the command

ADD ASBR.

ANI (V): When it is set to an MGW name, it indicates that the subscriber belongs to this MGW.

• ADD PHNCT: PCN="AC62", PC="+5562";


Provisioning Guide



Description: It is a configuration command, and is used to add a number context in the configuration database.


PC (V): The parameter value is in the format of "+country code"+"area code".

1.3 Remove SIP Subscriber

/****************************AT SPG web portal********************************/

USE ME:MENAME=HSS;

RMV HSUB: SUBID="+556239901189";

RMV HSDAINF: IMPI="+556239901189";

USE ME:MENAME=ENS;

RMV DNAPTRREC: E164NUM="39901189", ZONENAME="2.6.5.5.e164.arpa";

Command Description





• RMV HSUB: SUBID="+556239901189";

Description: This command is used to remove a subscription on the HSS. Perform this operation to remove the

specified IMS subscription and the IMPI and IMPU associated with the IMS subscription from the HSS service

database. Running this command, it will also remove the data from the ATS (RMV SBR)

SUBID (V): This is a unique identified on the HSS, The subscription ID is the key parameter used to determine the

subscription data to be removed. It is obtainable by running the LST HSUB operation. The value of the parameter is

case sensitive. In this field, must fill the number in the format 55 AC number (8 digits).

• RMV HSDAINF: IMPI="+556239901189";

Description: This command is used to remove the SIP Digest data record for the specified IMPI from the HSS service

database.


digits)



(ENS).


Provisioning Guide




• RMV DNAPTRREC: E164NUM="39901189", ZONENAME="2.6.5.5.e164.arpa";

Description: This command is used to delete NAPTR resource records.

E164NUM (V): Specifies an E.164 number or number segment.GVT specified format is a number (8digits).


ADD DZONE command before it is referenced here.

1.4 Remove H.248 Subscriber

/****************************AT SPG web portal********************************/

USE ME:MENAME=HSS;

RMV HSUB: SUBID="+556239901189";

RMV HSDAINF: IMPI="+556239901189";

USE ME:MENAME=ENS;

RMV DNAPTRREC: E164NUM="39901189", ZONENAME="2.6.5.5.e164.arpa";


RMV ASBR: SOFTXIP="10.140.72.224", PUI="sip:[email protected] ";

Command Description




• RMV HSUB: SUBID="+556239901189";

Description: This command is used to remove a subscription on the HSS. Perform this operation to remove the

specified IMS subscription and the IMPI and IMPU associated with the IMS subscription from the HSS service

database. Running this command, it will also remove the data from the ATS (RMV SBR)

SUBID (V): This is a unique identified on the HSS, The subscription ID is the key parameter used to determine the

subscription data to be removed. It is obtainable by running the LST HSUB operation. The value of the parameter is

case sensitive. In this field, must fill the number in the format 55 AC number (8 digits).

• RMV HSDAINF: IMPI="+556239901189";

Description: This command is used to remove the SIP Digest data record for the specified IMPI from the HSS service

database.


Provisioning Guide




digits)



(ENS).

• RMV DNAPTRREC: E164NUM="39901189", ZONENAME="2.6.5.5.e164.arpa";

Description: This command is used to delete NAPTR resource records.

E164NUM (V): Specifies an E.164 number or number segment.GVT specified format is a number (8digits).


ADD DZONE command before it is referenced here.


Description: Select the Managed Element (ME) to do the provisioning. In this command, it selects the Management

Server (M2000).

• RMV ASBR: SOFTXIP="10.140.72.224", PUI="sip:[email protected] ";

Description: This command is used to remove A-CSCF subscriber data in the configuration database. This function is

used to configure functions provided by the AGCF.


PUI (V): This is a Public User ID; The user ID used outside the IMS Core is the public user ID that is used to

communicate with others. The value of this parameter must be the same as the user ID defined on the HSS and

ATS. From now on, this will be the “facility” name of the GVT subscriber. It must have the format according to the

example below (from the GVT HLD):








1.5 List SIP subscriber database parameters

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;


Provisioning Guide



LST SBR:IMPU="sip:[email protected]";

Command Description




• LST SBR:IMPU="sip:[email protected]";

Description: This command is used to list basic subscriber data. Unless otherwise specified, parameters related with

service authority in this command use 0 to indicate that the subscriber does not have the service authority, and 1 to

indicate that the subscriber has the service authority.




[email protected]


1.6 List H.248 subscriber database parameters

/****************************AT SPG web portal********************************/


LST ASBR: SOFTXIP="10.140.72.224", PUI="sip:[email protected]";

Command Description


Description: Select the Managed Element (ME) to do the provisioning. In this command, it selects the Management

Server M2000.

• LST ASBR: SOFTXIP="10.140.72.224", PUI="sip:[email protected]";

Description: It is a configuration command, and is used to query AGCF subscriber data in the configuration database.


SOFTXIP (V): The IP address is the IP of AGCF BAM. This value is filled according to the actual situation.

PUI (V): This is a Public User ID; the user ID used outside the IMS Core is the public user ID that is used to

communicate with others. The value of this parameter must be the same as the user ID defined on the HSS and

ATS. From now on, this will be the “facility” name of the GVT subscriber. It must have the format according to the

example below (from the GVT HLD):


Provisioning Guide










1.7 Give Conference Service Right to Subscriber

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;

MOD SS:IMPU="sip:[email protected]", NSNPTY=1;

Command Description




• MOD SS:IMPU="sip:[email protected]", NSNPTY=1;

Description: This command is used to modify supplementary service authority data of a subscriber.




[email protected]


NSNPTY (F): It specifies the Conference Call (NPTY) service right of a subscriber. You must set “0” to deactivate, “1”

to activate the feature.

1.8 Call Waiting

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;


Provisioning Guide



MOD SS:IMPU="sip:[email protected]",NSCW=1;

REG COMSS:IMPU="sip:[email protected]", CW=1;

Command Description




• MOD SS:IMPU="sip:[email protected]",NSCW=1;





[email protected]


NSCW (V): It specifies the Call Waiting (CW) service right of a subscriber. You must set “0” to deactivate, “1” to

activate the feature.

• REG COMSS:IMPU="sip:[email protected]", CW=1;

Description: This command is used to register all common supplementary service for a subscriber. When a service is

registered, the service parameter value must be set to 1 (the check box of the service is selected on the SPG2800

Web Portal). The service is activated after being registered.




[email protected]


CW (F): It specifies the call waiting (CW) service right of a subscriber. The CW service is automatically activated once

it is registered.

1.9 Voice Mail System

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;

MOD SBR:IMPU="sip:[email protected]",NSCFBVM=1,NSMWI=1,VMAIND=1;


Provisioning Guide



MOD SS:IMPU="sip:[email protected]",NSCFBVM=1;

REG COMSS:IMPU="sip:[email protected]",CFBVM=1;

Introduction

There are four options where the call can be forwarded to the voice mail system, as below:

1 – The called number is busy: In this case, the subscriber must have the supplementary service “Call Forwarding

Busy to Voice Mailbox Right” (NSCFBVM) set to 1. To register this service (REG COMSS), the parameter CFBVM must

be set to 1;

2 – The called number does not reply the call: In this case, the subscriber must have the supplementary service “Call

Forwarding No Reply to Voice Mailbox Right” (NSCFNRVM) set to 1. To register this service (REG COMSS), the

parameter CFNRVM must be set to 1;

3 – Forward all calls to voice mail: In this case, the subscriber must have the supplementary service “Call forwarding

Unconditional to Voice Mailbox Right” (NSCFUVM) set to 1. To register this service (REG COMSS), the parameter

CFUVM must be set to 1;

4 – Terminal is offline (exclusive for SIP devices): In this case, the subscriber must have the supplementary service

“Call forwarding Offline to Voice Mailbox Right” (NSCFNLVM) set to 1. To register this service (REG COMSS), the

parameter CFNLVM must be set to 1.

Addittionally, the subscriber must have a Voice Mailbox Address Index (VMAIND). This parameter refers to the voice

mail box number configured on ATS.

Command Description




• MOD SBR:IMPU="sip:[email protected]", NSCFBVM=1, NSMWI=1, VMAIND=1;

Description: This command is used to modify parameters on an existent subscriber.

IMPU (V): It specifies the IMPU of a specific subscriber. It can be a TEL URI or a SIP URI. More details refer to chapter

1.1 Create New SIP subscriber.

NSCFBVM (V): This is the supplementary service “Call Forwarding Busy to Voice Mailbox Right”. You must set “0” to

remove, “1” to allow the feature.

NSMWI (V): This is the supplementary service “Message Waiting Indication Right”. You must set “0” to remove, “1”

to allow the feature.

VMAIND (V): This parameter refers to the voice mail box number configured on ATS. For this project, we will use “1”

for all the cases. In the future, if GVT installs a new Voice Mailbox platform, it can be changed for other values,

according to the network configuration.

• MOD SS:IMPU="sip:[email protected]",NSCFBVM=1;


Provisioning Guide



Description: This command is used to enable the authority to use the feature.



NSCFBVM (V): This is the supplementary service “Call Forwarding Busy to Voice Mailbox Right”, You must set “0” to

deactivate, “1” to activate the feature.

• REG COMSS:IMPU="sip:[email protected]",CFBVM=1;

Description: This command is used to register all common supplementary service for a subscriber. When a service is

registered, the service parameter value must be set to 1 (the check box of the service is selected on the SPG2800

Web Portal). The service is activated after being registered.




[email protected]


CFBVM (F): It specifies the “Call Forwarding Busy to Voice Mailbox Right” of a subscriber. This service is

automatically activated once it is registered.

1.10 Call Forward Unconditional (CFU)

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;

MOD SS:IMPU="sip:[email protected]",NSCFU=1;

REG CFU:IMPU="sip:[email protected]", DIMPU="tel: 39901188";

Command Description




• MOD SS:IMPU="sip:[email protected]",NSCFU=1;





Provisioning Guide



NSCFU (V): This is the supplementary service “Call Forwarding Unconditional Right”, You must set “0” to deactivate,

“1” to activate the feature.

• REG CFU:IMPU="sip:[email protected]", DIMPU="tel: 39901188";

Description: This command is used to register the CFU service. If a subscriber has the CFU service registered, the

incoming calls are unconditionally forwarded to the subscriber defined by Destination IMPU.




[email protected]


DIMPU (V): This is the Destination IMPU; it specifies the IMPU of a forwarded-to subscriber. It can be a TEL URI or a

SIP URI. It can be a TEL URI or a SIP URI. The rules for setting the parameter are as follows:

To configure an IMPU in TEL URI format, type a string such as +556239901188、06239901188 or 39901188

1.11 Change Subscriber Call Source

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;

MOD SBR:IMPU="sip:[email protected]",CSC=1001;

Command Description




• MOD SBR:IMPU="sip:[email protected]",CSC=1001;


IMPU (V): It specifies the IMPU of a specific subscriber. It can be a TEL URI or a SIP URI. More details refer to

chapter 1.1 Create New SIP subscriber.

CSC (V): It specifies the call source code of the subscriber.


Provisioning Guide



1.12 Outgoing Call Barring (Cadeado Eletrônico)

/****************************AT SPG web portal********************************/

//When subscriber selects K value

USE ME:MENAME=ATS;

MOD SBR:IMPU="sip:[email protected]",NSCBA=1;

MOD SS:IMPU="sip:[email protected]",NSCBA=1, ;

//When subscriber has default K value (can only activate / deactivate the feature)

USE ME:MENAME=ATS;

MOD SBR:IMPU="sip:[email protected]",NSCBA=1, KVALUE=K3;

MOD SS:IMPU="sip:[email protected]",NSCBA=1;

1.12.1 Command Description

1.12.1.1 When subscriber selects K value




• MOD SBR:IMPU="sip:[email protected]",NSCBA=1;

Description: This command is used to modify a specific or a group of parameters on a subscriber. In this case, it

enables the subscriber to use CBA feature.



NSCBA(V): This is the supplementary service “Outgoing Call Barring Right”, You must set “0” to remove, “1” to set

the feature.

• MOD SS:IMPU="sip:[email protected]",NSCBA=1;




NSCBA(V): This is the supplementary service “Outgoing Call Barring Right”, You must set “0” to deactivate, “1” to



Provisioning Guide



1.12.1.1 When subscriber has default K value




• MOD SBR:IMPU="sip:[email protected]",NSCBA=1,KVALUE=K3;

Description: This command is used to modify a specific or a group of parameters on a subscriber. In this case, it

enables the subscriber to use CBA feature.



NSCBA(V): This is the supplementary service “Outgoing Call Barring Right”, You must set “0” to remove, “1” to set

the feature.

KVALUE(V): This is the predefined barring level for this user. It means, the subscriber can only activate or deactivate

one type of call barring. Below is a table with the available barring levels:

Barring Level Blocking Scenarios

K0 Local Mobile K1 National Long Distance K2 International Long Distance K3 0900; 0300 and 0500 K4 Local Mobile and National Long Distance K5 Local Mobile and International Long Distance K6 Local Mobile; 0900; 0300 and 0500 K7 National and International Long Distance K8 National Long Distance; 0900; 0300 and 0500 K9 International Long Distance; 0900; 0300 and 0500 K10 Mobile; National and International Long Distance K11 Mobile; International Long Distance; 0900; 0300 and 0500 K12 National and International Long Distance; 0900; 0300 and 0500 K13 Mobile; National and International Long Distance; 0900; 0300 and 0500


Description: This command is used to enable the authority to use the feature for a predefined K value.



NSCBA(V): This is the supplementary service “Outgoing Call Barring Right”, You must set “0” to deactivate, “1” to



Provisioning Guide



1.12.2 Terminal commands

1.12.1.1 When subscriber selects K value

* 66 * PPPP * KK # = Activate CBA feature. PPPP is the password with 4 digits, KK is the K value from 00 to 13.

# 66 * PPPP # = Deactivate CBA feature. PPPP is the password with 4 digits.

*# 67*OPWD*NPWD # = Change the user password.

1.12.1.1 When subscriber has default K value

# 66 # = Activate CBA feature.

# 66 * PPPP # = Deactivate CBA feature. PPPP is the password with 4 digits.

*# 67*OPWD*NPWD # = Change the user password.

1.13 Calling Line Identification Presentation (CLIP)

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;

MOD SS:IMPU="sip:[email protected]",NSCLIP=1;

Command Description




• MOD SS:IMPU="sip:[email protected]",NSCLIP=1;




NSCLIP (V): This is the supplementary service “Calling Line Identification Presentation Right”, You must set “0” to



Provisioning Guide



1.14 SIP PBX subscribers

1.14.1 PBXSBR with valid subscriber number (DNH)

/****************************AT SPG web portal********************************/

USE ME:MENAME=WORKFLOW;

ADD PBX: MEGROUP="ATS_VPBX", GDN="tel:+556239901193",QUL=1,SGM=0,MDF=0,PAC=0, SNDP=0 ,CHT=0;

ADD PBXSBR: MEGROUP="ATS_VPBX", IMPU="tel:+556239901193",GDN="tel:+556239901193",PSN=0;




Command Description

IMPORTANT: PBX subscribers are, first of all, SIP or H248 subscribers. So before do this procedure, the subscribers

must be created by following the procedure described on the Chapter 1.1 or 1.2.

• USE ME:MENAME=WORKFLOW;

Description: For PBX and Centrex service provisioning, the MENAME must be “WORKFLOW”, it specifies the

command will be performed in service flow mode. In service flow mode the command will be sent to both two ATS

sites in one redundancy group. Here, this parameter should be set to “WORKFLOW”, as the fixed value.

The MENAME with “WORKFLOW” value can only be used when perform on SPG as a “Batch Task”. In soap interface

between BSS and SPG, only need to specify the MEGROUP with the “ATS_VPBX” value. Only Virtual PBX

ADD/RMV/MOD/LST PBX, ADD/RMV/MOD/LST PBXSBR need to follow the following principle, for the soap format

detail, please refer <ATS9900 Service Provisioning Interface.chm>.

ADD PBX: MEGROUP="ATS_VPBX", GDN="tel:+556239901193",QUL=1,SGM=0,MDF=0,PAC=0, SNDP=0,CHT=0;

Description: This command is used to add a PBX service data record to the configuration database. To add a PBX

service data record is to configure a PBX group, so that subscribers in the group can be selected to answer calls.

MEGROUP(F): It specifies the name of an ME group. If this parameter is specified, the command is run on the specified ME group. If this parameter is not specified, the command is run on the ME or ME group determined by the user policy configuration. For this issue, there is a redundancy ME group named “ATS_VPBX”. Here, this

parameter should be set to “ATS_VPBX”, as the fixed value.

GDN (V): It specifies the access code of the PBX group for incoming calls. When an out-PBX subscriber dials the PBX

pilot number, the call processing software selects a subscriber in the PBX group based on a specific line hunting

mode, or queues the call when all PBX subscribers are busy.

A PBX pilot number can be an existing number in the subscriber data table, namely, a valid subscriber number pre-

defined by running ADD SBR. Such a PBX pilot number is not only an access code, but also has all the attributes of an

ordinary subscriber.


Provisioning Guide



A PBX pilot number can also be a number that does not exist in the subscriber data table. Such a PBX pilot number is

only an access code, and cannot be defined as an ordinary subscriber number by running ADD SBR.

QUL (V): It specifies whether the PBX group supports the queuing function. If the parameter is set to 1 (YES), it

indicates that when a call is addressed to the PBX pilot number and all the subscribers in the PBX group are busy,

then the ATS adds the call to the call queue instead of playing the busy tone to the caller. When subscribers in the

PBX group become idle, the ATS connects the calls in the queue to the idle subscribers according to the "first in, first

out" principle. If the parameter is set to 0 (NO), it indicates that when a call is addressed to the PBX pilot number

and all the subscribers in the PBX group are busy, and then the ATS releases the call directly. The recommend

configuration is set this parameter to 1 (YES) for all the cases.

SGM (V): It specifies the mode in which the ATS selects a subscriber for answering a call addressed to the PBX pilot

number. Options:

• MIN(FROM_SMALL_TO_LARGE): The ATS always selects the subscriber with the minimum equipment ID. This

mode helps to select the preferred subscribers.

• MAX(FROM_LARGE_TO_SMALL): The ATS always selects the subscriber with the maximum equipment ID. This


• CYC(CYCLIC): The ATS9900 selects PBX subscribers based on the sequence when idle PBX subscribers are added

and PBX subscribers are released, and then forms a queue. In subsequent calls, the ATS9900 selects PBX subscribers

based on the queue sequence.

• UNIFORM(UNIFORM): All the idle subscribers are queued in ascending order based on their record numbers (the

sequences that the PBX subscribers are added by running ADD PBXSBR or MOD PBXSBR). After being selected to

answer calls and then released, the subscribers are queued again in the same way. Each release subscriber is added

to the end of the queue in turn automatically. After all the subscribers in the previous queue are selected, the ATS

selects the subscribers in the current queue. The recommended value for this parameter is 0 (MIN -

FROM_SMALL_TO_LARGE), but it can be configured according to subscriber requirement.

MDF (V): It specifies whether the ATS provides the simultaneous ringing function for the PBX pilot number. The

default value is 0 (NO), which indicates that when a call is addressed to the PBX pilot number, the idle subscribers in

the PBX group are selected based on the configured line hunting mode. If the parameter is set to 1 (YES), it indicates

that when a call is addressed to the PBX pilot number, the phones of all the idle subscribers in the PBX group ring

simultaneously. The recommended value for this parameter is 0 (NO), but it can be configured according to

subscriber requirement.

PAC (V): It specifies whether the ATS displays the PBX pilot number to the callee when a PBX subscriber makes a call.

For PBX group where the associated numbers has valid number (DNH), this value must be 0 (NO).

SNDP (V): It specifies whether the ATS adds the pilot number AVP to be sent to the CCF or the OCS, for charging

issues. Note that the operation specified by the parameter is different from the operation specified by Use pilot

number as caller number. Send pilot number mode controls only the contents of the AVP to be sent to the CCF or

the OCS. Options:

DNTH(DO_NOTHING): The system performs the processing as that carried out for an ordinary subscriber.

SDPL(SEND_PILOT): The system sends the PBX pilot number during the charging.

RPLC(REPLACE_CALLER_NUM): The system records the PBX pilot number into original caller AVP during the charging.

For PBX group where the associated numbers has valid number (DNH), this value must be 0 (DO_NOTHING).


Provisioning Guide



CHT (V): It indicates whether the PBX group supports non-pilot number line hunting. If this parameter is set to 1

(Yes), the system performs line hunting in a call addressed to a non-pilot number in the PBX group, and the service

experience is the same as that provided in a call addressed to a pilot number. If this parameter is set to 0 (No), the

system does not perform line hunting in a call addressed to a non-pilot number in the PBX group, and the service

experience is the same as that provided in a call addressed to an ordinary subscriber. The recommended value for

this parameter is 0 (NO), but it can be configured according to subscriber requirement.

• ADD PBXSBR: MEGROUP="ATS_VPBX", IMPU="tel:+556239901193",GDN="tel:+556239901193",PSN=0;




Description: This command is used to add a PBX subscriber data record to the configuration database. To add a PBX

subscriber data record is to add a PBX subscriber and configure the attributes of the PBX subscriber.

MEGROUP (F): It specifies the name of an ME group. If this parameter is specified, the command is run on the

specified ME group. If this parameter is not specified, the command is run on the ME or ME group determined by

the user policy configuration. For this issue, there is a redundancy ME group named “ATS_VPBX”. Here, this


IMPU (V): It defines an IMPU for a subscriber in the ATS9900 configuration database. Its value can be in TEL URI or

SIP URI format.

GDN (V): It specifies the pilot number of the PBX group to which the subscriber belongs. The parameter must be

defined by running ADD PBX before being referenced here.

PSN (V): This is the Line hunting serial number. It specifies the serial number of the PBX subscriber used in line

hunting. The line hunting mode is configured by running ADD PBX or MOD PBX. When a call is addressed to the PBX

pilot number, the system selects a proper line hunting serial number based on the line hunting mode. Thus, the call

is connected to the corresponding subscriber.


Provisioning Guide



1.14.2 PBXSBR with virtual subscriber number (DLH)

/****************************AT SPG web portal********************************/


ADD PBX: MEGROUP="ATS_VPBX", GDN="tel:+556239901193",QUL=1,SGM=0,MDF=0,PAC=1, SNDP=2 ,CHT=0;





Command Description

IMPORTANT: PBX subscribers are, first of all, SIP or H248 subscribers. So before do this procedure, the subscribers

must be created by following the procedure described on the Chapter 1.1 or 1.2.


Description: For PBX and Centrex service provisioning, the MENAME must be “WORKFLOW”, it specifies the

command will be performed in service flow mode. In service flow mode the command will be sent to both two ATS

sites in one redundancy group. Here, this parameter should be set to “WORKFLOW”, as the fixed value.

The MENAME with “WORKFLOW” value can only be used when perform on SPG as a “Batch Task”. In soap interface

between BSS and SPG, only need to specify the MEGROUP with the “ATS_VPBX” value. Only Virtual PBX

ADD/RMV/MOD/LST PBX, ADD/RMV/MOD/LST PBXSBR need to follow the following principle, for the soap format

detail, please refer <ATS9900 Service Provisioning Interface.chm>.

• ADD PBX: MEGROUP="ATS_VPBX", GDN="tel:+556239901193",QUL=1,SGM=0,MDF=0,PAC=1,SNDP=2,CHT=0;

Description: This command is used to add a PBX service data record to the configuration database. To add a PBX

service data record is to configure a PBX group, so that subscribers in the group can be selected to answer calls.

MEGROUP(F): It specifies the name of an ME group. If this parameter is specified, the command is run on the specified ME group. If this parameter is not specified, the command is run on the ME or ME group determined by the user policy configuration. For this issue, there is a redundancy ME group named “ATS_VPBX”. Here, this


GDN (V): It specifies the access code of the PBX group for incoming calls. When an out-PBX subscriber dials the PBX

pilot number, the call processing software selects a subscriber in the PBX group based on a specific line hunting

mode, or queues the call when all PBX subscribers are busy.

A PBX pilot number can be an existing number in the subscriber data table, namely, a valid subscriber number pre-

defined by running ADD SBR. Such a PBX pilot number is not only an access code, but also has all the attributes of an

ordinary subscriber.


Provisioning Guide



A PBX pilot number can also be a number that does not exist in the subscriber data table. Such a PBX pilot number is

only an access code, and cannot be defined as an ordinary subscriber number by running ADD SBR.

QUL (V): It specifies whether the PBX group supports the queuing function. If the parameter is set to 1 (YES), it

indicates that when a call is addressed to the PBX pilot number and all the subscribers in the PBX group are busy,

then the ATS adds the call to the call queue instead of playing the busy tone to the caller. When subscribers in the

PBX group become idle, the ATS connects the calls in the queue to the idle subscribers according to the "first in, first

out" principle. If the parameter is set to 0 (NO), it indicates that when a call is addressed to the PBX pilot number

and all the subscribers in the PBX group are busy, and then the ATS releases the call directly. The recommend

configuration is set this parameter to 1 (YES) for all the cases.

SGM (V): It specifies the mode in which the ATS selects a subscriber for answering a call addressed to the PBX pilot

number. Options:

• MIN(FROM_SMALL_TO_LARGE): The ATS always selects the subscriber with the minimum equipment ID. This


• MAX(FROM_LARGE_TO_SMALL): The ATS always selects the subscriber with the maximum equipment ID. This


• CYC(CYCLIC): The ATS9900 selects PBX subscribers based on the sequence when idle PBX subscribers are added

and PBX subscribers are released, and then forms a queue. In subsequent calls, the ATS9900 selects PBX subscribers

based on the queue sequence.

• UNIFORM(UNIFORM): All the idle subscribers are queued in ascending order based on their record numbers (the

sequences that the PBX subscribers are added by running ADD PBXSBR or MOD PBXSBR). After being selected to

answer calls and then released, the subscribers are queued again in the same way. Each release subscriber is added

to the end of the queue in turn automatically. After all the subscribers in the previous queue are selected, the ATS

selects the subscribers in the current queue. The recommended value for this parameter is 0 (MIN -

FROM_SMALL_TO_LARGE), but it can be configured according to subscriber requirement.

MDF (V): It specifies whether the ATS provides the simultaneous ringing function for the PBX pilot number. The

default value is 0 (NO), which indicates that when a call is addressed to the PBX pilot number, the idle subscribers in

the PBX group are selected based on the configured line hunting mode. If the parameter is set to 1 (YES), it indicates

that when a call is addressed to the PBX pilot number, the phones of all the idle subscribers in the PBX group ring

simultaneously. The recommended value for this parameter is 0 (NO), but it can be configured according to

subscriber requirement.

PAC (V): It specifies whether the ATS displays the PBX pilot number to the callee when a PBX subscriber makes a call.

For PBX group where the associated numbers are virtual (DLH), this value must be 1 (YES).

SNDP (V): It specifies whether the ATS adds the pilot number AVP to be sent to the CCF or the OCS, for charging

issues. Note that the operation specified by the parameter is different from the operation specified by Use pilot

number as caller number. Send pilot number mode controls only the contents of the AVP to be sent to the CCF or

the OCS. Options:

DNTH(DO_NOTHING): The system performs the processing as that carried out for an ordinary subscriber.

SDPL(SEND_PILOT): The system sends the PBX pilot number during the charging.

RPLC(REPLACE_CALLER_NUM): The system records the PBX pilot number into original caller AVP during the charging.

For PBX group where the associated numbers are virtual (DLH), this value must be 2 (REPLACE_CALLER_NUM).


Provisioning Guide



CHT (V): It indicates whether the PBX group supports non-pilot number line hunting. If this parameter is set to 1

(Yes), the system performs line hunting in a call addressed to a non-pilot number in the PBX group, and the service

experience is the same as that provided in a call addressed to a pilot number. If this parameter is set to 0 (No), the

system does not perform line hunting in a call addressed to a non-pilot number in the PBX group, and the service

experience is the same as that provided in a call addressed to an ordinary subscriber. The recommended value for

this parameter is 0 (NO), but it can be configured according to subscriber requirement.

• ADD PBXSBR: MEGROUP="ATS_VPBX", IMPU="tel:+556239901193",GDN="tel:+ 556239901193",PSN=0;




Description: This command is used to add a PBX subscriber data record to the configuration database. To add a PBX

subscriber data record is to add a PBX subscriber and configure the attributes of the PBX subscriber.

NOTE: the virtual number provisioning has defined with GVT Engineering according to the follow standard:

IMPU=PilotNumber+XXX, where XXX is an extension from 100 to 199 (to do not conflict with One-number

extensions). To facilitate the operations, the first virtual number which occupies the PSN 1, will be created with the

extension 101, for PSN 2, the extension is 102 and so on.

MEGROUP(F): It specifies the name of an ME group. If this parameter is specified, the command is run on the

specified ME group. If this parameter is not specified, the command is run on the ME or ME group determined by

the user policy configuration. For this issue, there is a redundancy ME group named “ATS_VPBX”. Here, this


IMPU (V): It defines an IMPU for a subscriber in the ATS9900 configuration database. Its value can be in TEL URI or

SIP URI format.

GDN (V): It specifies the pilot number of the PBX group to which the subscriber belongs. The parameter must be

defined by running ADD PBX before being referenced here.

PSN (V): This is the Line hunting serial number. It specifies the serial number of the PBX subscriber used in line

hunting. The line hunting mode is configured by running ADD PBX or MOD PBX. When a call is addressed to the PBX

pilot number, the system selects a proper line hunting serial number based on the line hunting mode. Thus, the call

is connected to the corresponding subscriber.

1.15 H.248 PBX subscribers

The procedure is the same used for SIP subscribers, the only difference is about the access part when adding

subscriber on ATS (ADD SBR). Please refer to Chapter 1.14.


Provisioning Guide



1.16 Change Subscriber Restriction Group from 1029 to none 65535

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;

MOD SBR:IMPU="sip:[email protected]", CSC=1029, LMTGRP=65534;

Command Description




• MOD SBR:IMPU="sip:[email protected]",CSC=1029,LMTGRP=65534;



1.1 Create New SIP subscribers.


LMTGRP (V): It specifies the restriction group of this subscriber. Some call sources uses restriction group to forbid

specific calls, like LDN, International, other. You can check some examples of restriction groups used on this project

in the Chapter 2 – Configuration According to the Class of Service (NCOS).

1.17 Remove Conference Authority from Subscriber

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;

• MOD SS:IMPU="sip:[email protected]",NSNPTY=0;

Command Description




• MOD SS:IMPU="sip:[email protected]",NSNPTY=0;

Description: This command is used to remove the authority to use the feature.


Provisioning Guide





NSNPTY (V): This is the supplementary service “Conference Call Right”, You must set “0” to deactivate, “1” to


1.18 Remove Call Waiting Authority from Subscriber

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;

MOD SS:IMPU="sip:[email protected]",NSCW=0;

Command Description




• MOD SS:IMPU="sip:[email protected]",NSCW=0;




NSCW (V): This is the supplementary service “Call Waiting Right”, You must set “0” to deactivate, “1” to activate the

feature.

1.19 Remove CFU from subscriber

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;


Command Description






Provisioning Guide






NSCFU (V): This is the supplementary service “Call Forwarding Unconditional Right”, You must set “0” to deactivate,

“1” to activate the feature.

1.20 Change Subscriber Call Source

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;

MOD SBR:IMPU="sip:[email protected]",CSC=1001;

Command Description




• MOD SBR:IMPU="sip:[email protected]", CSC=1001;





1.21 Remove Outgoing Call Barring (Cadeado Eletrônico) from subscriber

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;

MOD SS:IMPU="sip:[email protected]",NSCBA=0;

Command Description



Provisioning Guide









NSCBA (V): This is the supplementary service “Outgoing Call Barring Right”, You must set “0” to deactivate, “1” to


1.22 Remove CLIP authority from subscriber

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;

MOD SS:IMPU="sip:[email protected]",NSCLIP=0;

Command Description




• MOD SS:IMPU="sip:[email protected]",NSCLIP=0;




NSCLIP (V): This is the supplementary service “Calling Line Identification Presentation Right”, You must set “0” to


1.23 Remove SIP subscriber from a PBX group

/****************************AT SPG web portal********************************/


RMV PBXSBR: MEGROUP="ATS_VPBX", IMPU="sip:[email protected]";

Command Description


Provisioning Guide




Description: For details, please refer to Chapter 1.14.

• RMV PBXSBR: MEGROUP="ATS_VPBX", IMPU="sip:[email protected]";

Description: This command is used to remove a PBX subscriber data record from the configuration database.

MEGROUP(F): It specifies the name of an ME group. If this parameter is specified, the command is run on the specified ME group. If this parameter is not specified, the command is run on the ME or ME group determined by the user policy configuration. we have created a redundancy ME group named “ATS_VPBX”. Here, this parameter

should be set to “ATS_VPBX”, as the fixed value.


chapter 1.1 Create New SIP subscribers.

1.24 Remove H.248 Subscriber from a PBX group

/****************************AT SPG web portal********************************/


RMV PBXSBR: MEGROUP="ATS_VPBX", IMPU="sip:[email protected]";

Command Description



• RMV PBXSBR: MEGROUP="ATS_VPBX", IMPU="sip:[email protected]";

Description: This command is used to remove a PBX subscriber data record from the configuration database.

MEGROUP(F): It specifies the name of an ME group. If this parameter is specified, the command is run on the specified ME group. If this parameter is not specified, the command is run on the ME or ME group determined by the user policy configuration. we have created a redundancy ME group named “ATS_VPBX”. Here, this parameter



chapter 1.1 Create New SIP subscribers.

1.25 Reset Subscriber Password to default value (Cadeado Eletrônico)

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;


Provisioning Guide



MOD SBR:IMPU="sip:[email protected]",COP="1234";

Command Description




• MOD SBR:IMPU="sip:[email protected]",COP="1234";

Description: This command is used to modify parameters on an existent subscriber. In this case, this command line

is to change the password used for the supplementary service “Outgoing Call Barring (Cadeado Eletronico)”.



COP (V): It specifies the call-out password of a subscriber. This parameter is used in the Outgoing Call Barring

service. For this project, the standard is a numeric sequence with four digits.

1.26 List Call Waiting

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;

LST SS:IMPU="sip:[email protected]";

DSP COMSS:IMPU="sip:[email protected]";

Command Description




• LST SS:IMPU="sip:[email protected]";

Description: This command is used to check if the subscriber has the authority to use the feature.



*** For information about this feature, check if the subscriber contains the “Call Waiting Right” feature.

• DSP COMSS:IMPU="sip:[email protected]";


Provisioning Guide



Description: This command is used to display all common supplementary service for a subscriber, if the SS appears

on the command result, it means that it’s activated.



*** For information about this feature, check if the subscriber contains the “Call Waiting Right” feature.

1.27 List Conference

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;


Command Description








*** For information about this feature, check if the subscriber contains the “Conference Call Right” feature.

1.28 List Voice Mail Service

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;


DSP COMSS:IMPU="sip:[email protected]";

Command Description





Provisioning Guide









*** For information about this command, look for these parameters:

• Call Forwarding Unconditional to Voice Mailbox Right: It specifies the Call Forwarding Unconditional to

Voice Mailbox (CFUVM) service right of a subscriber.

• Call Forwarding Busy to Voice Mailbox Right: It specifies the Call Forwarding Busy to Voice Mailbox (CFBVM)

service right of a subscriber.

• Call Forwarding No Reply to Voice Mailbox Right: It specifies the Call Forwarding No Reply to Voice Mailbox

(CFNRVM) service right of a subscriber.

• DSP COMSS:IMPU="sip:[email protected]";

Description: This command is used to display all common supplementary service for a subscriber, if the SS appears

on the command result, it means that it’s activated.



*** For information about this command, look for these parameters:

• Call Forwarding Unconditional to Voice Mailbox Right: It specifies the Call Forwarding Unconditional to

Voice Mailbox (CFUVM) service right of a subscriber.

• Call Forwarding Busy to Voice Mailbox Right: It specifies the Call Forwarding Busy to Voice Mailbox (CFBVM)

service right of a subscriber.

• Call Forwarding No Reply to Voice Mailbox Right: It specifies the Call Forwarding No Reply to Voice Mailbox

(CFNRVM) service right of a subscriber.

1.29 List CFU (Call Forwarding Unconditional)

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;


DSP CFU:IMPU="sip:[email protected]";

Command Description



Provisioning Guide









*** For information about this feature, check if the subscriber contains the “Call Forwarding Unconditional Right”

feature.

• DSP CFU:IMPU="sip:[email protected]";

Description: This command is used to display the configuration of the CFU service, if it’s activated or deactivated.



1.30 List Call Source

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;

LST SBR:IMPU="sip:[email protected]";

Command Description










*** For information about this command, look for the parameter “Call source code”.


Provisioning Guide



1.31 List CLIP

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;


Command Description





Description: List the supplementary services currently configured for this subscriber.

IMPU (V): It specifies the IMPU of a specific subscriber. More details refer to chapter 1.1 Create New SIP

subscriber.

*** For information about this feature, check if the subscriber contains the “Calling Line Identification

Presentation Right” feature.

1.32 List PBX subscribers

/****************************AT SPG web portal********************************/


LST PBXSBR: MEGROUP="ATS_VPBX", IMPU="sip:[email protected]";

Command Description



• LST PBXSBR: MEGROUP="ATS_VPBX", IMPU="sip:[email protected]"; or

• LST PBXSBR: MEGROUP="ATS_VPBX";

Description: This command is used to list PBX subscriber data records in the configuration database.

• To list the brief information about all PBX subscriber data records, do not specify any parameter.

• To list the detailed information about a specific PBX scriber data record, specify IMPU.

MEGROUP(F): It specifies the name of an ME group. If this parameter is specified, the command is run on the specified ME group. If this parameter is not specified, the command is run on the ME or ME group determined


Provisioning Guide



by the user policy configuration. we have created a redundancy ME group named “ATS_VPBX”. Here, this parameter




1.33 List Outgoing Call Barring (Cadeado Eletrônico)

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;


Command Description







subscriber.

*** For information about this feature, check if the subscriber contains the “Outgoing Call Barring Right”

feature.

1.34 Register CFU from IMS no subscriber intervention

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;


REG CFU:IMPU="sip:[email protected]",BSV=ALL,BSG=TS11,DIMPU="tel: 39901188",NOTIFYCALLER=NO,

PRVTOCER=NO_PRIVACY,PRVTODES=NO_PRIVACY;

Command Description






Provisioning Guide



Description: Allow the user to use the Call Forwarding Unconditional supplementary Service.


subscriber.

NSCFU (V): This is the supplementary service “Call Forwarding Unconditional” and has two conditions, “0” to

deactivate the feature, “1” to activate it.

• REG CFU:IMPU="sip:[email protected]",BSV=ALL,BSG=TS11,DIMPU="tel: 39901188",

NOTIFYCALLER=NO, PRVTOCER=NO_PRIVACY,PRVTODES=NO_PRIVACY;

Description: Register the Call Forwarding Unconditional supplementary Service on IMS system.


subscriber.

BSV (F): Means the “Basic Service” to apply the feature, it specifies the media type. Only the calls with selected

media types are forwarded. This parameter will be fixed in all the cases.

BSG (F): Means the “Basic Service Group”, and for this network it is configured for group TS11 (telephony services)

only.

DIMPU (V): This is the destination number, and the format can be SIP URI or TEL URI. For this project, we will use

TEL URI format, and the number must follow the same dialing rules as the current dialing plan. For example, if it’s

a CFU to a local number, it must contain 8 digits, if LDN, must contain 0+CSP+AC+number

NOTIFYCALLER (F): It specifies whether to notify the caller when a call is forwarded unconditionally. For this

project , it is set as NO in all the cases.

PRVTOCER (V): It specifies whether to include the Privacy parameter to the History-Info header field (containing

the forwarded-to number) of the 181 message that is sent to the caller when the AS of the service subscriber

triggers the call forwarding service. Now we will use this parameter fixed for all cases, but in the future, if GVT

decides to mark it on the bill, it can be set to other values. The list of values can be obtained on the Huawei IMS

documentation or in the SPG command help.

PRVTODES (V): It specifies whether to include the Privacy parameter to the History-Info header field (containing

the service subscriber number) of the INVITE message that is sent to the forwarded-to subscriber when the AS of

the service subscriber triggers the call forwarding service. Now we will use this parameter fixed for all cases, but in

the future, if GVT decides to mark it on the bill, it can be set to other values. The list of values can be obtained on

the Huawei IMS documentation or in the SPG command help.

1.35 Support Fax Service

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;

MOD SBR:IMPU="sip:[email protected]",NSFAX=1;

Command Description





Provisioning Guide



• MOD SBR:IMPU="sip:[email protected]",NSFAX=1;

Description: Allow the user to support FAX service.


subscriber.

NSFAX (V): This is the supplementary service “Support Fax” and has two conditions, “0” to deactivate the feature,

“1” to activate it.

1.36 Set Temporary Suspension of subscriber

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;

PRK_SBR:IMPU="sip:[email protected]",STYPE=NOALM,TREAT=PLAYTONEANDRELEASE;

Command Description




• PRK_SBR:IMPU="sip:[email protected]",STYPE=NOALM,TREAT=PLAYTONEANDRELEASE;

Description: This command is used to temporary suspend a subscriber.


subscriber.

STYPE (F): It specifies the seasonal suspend mode of a subscriber. For this project, the parameter is NOALM (NO

ALARM) and is fixed.

TREAT (F): It specifies the processing mode when a subscriber calls a seasonally suspended subscriber. For this

project, the parameter is PLAYTONEANDRELEASE and is fixed.

1.37 Remove Temporary Suspension of subscriber

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;

RES_PRKSBR:IMPU="sip:[email protected]";

Command Description





Provisioning Guide



• RES_ PRKSBR:IMPU="sip:[email protected]";

Description: This command is used to restore the temporary suspension of a subscriber.


subscriber.

1.38 List Temporary Suspension of subscriber

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;

LST_PRKSBR:IMPU="sip:[email protected]";

Command Description




• LST_ PRKSBR:IMPU="sip:[email protected]";

Description: This command is used to list the status of the subscriber with temporary suspension, if the service is

activated or deactivated.


subscriber.

1.39 MSAN Users – Change the Access Part and keep the Subscriber Number

/****************************AT SPG web portal********************************/


MOD ASBR: SOFTXIP="10.140.72.224", PUI="sip:[email protected]", REGTP=SINGLE, TEN=EID,

EID:“10.140.72.130:2944”, TID="1";

Command Description


Description: Select the Managed Element (ME) to do the provisioning. In this command, it selects the

Management Server M2000.

• MOD ASBR: SOFTXIP="10.140.72.224", PUI="sip:[email protected]", REGTP=SINGLE, TEN=EID,

EID:“10.140.72.130:2944”, TID="1";

Description: It is a configuration command, and is used to add A-CSCF subscriber data in the configuration

database. This function is used to configure functions provided by the AGCF.


Provisioning Guide




PUI(V):Public User ID,The user ID used outside the IMS Core is the public user ID that is used to communicate with

others. The value of this parameter must be the same as the user ID defined on the HSS and ATS.

REGTP (F): Register type. It will be SINGLE register in all situations. This parameter will be fixed.

TEN (V): It specifies the type of the equipment name. This parameter can be “EID” (Equipment ID) or “EDESC”

(Equipment Description). Normally the parameter EID is used for this command.

EID (V): Equipment ID. This is the identification of the Access Node inside the IMS. The notation is the IP address of

the AG(MSAN) + “:” + the signaling port. Example: 10.140.72.130:2944, where 10.140.72.130 is the IP of Keymile

MSAN and 2944 is the signaling port. We can compare it as the V5 ID of the V5 interface.

INFORMATION: IF the subscriber will keep in the same MSAN, but will just change the TID, there is no need to

inform this parameter.

TID (V): Terminal ID. It specifies the physical port number of the MG to which the ESL subscriber belongs. It’s

the identification of the subscriber port for the corresponding Equipment ID. We can compare it to the L3ADDR on

V5 interface.

1.40 MSAN Users – Change the Subscriber Number and keep Access Part

IMPORTANT: For this operation, There is no way to change the number, because the subscriber on ATS is

associated with a record on HSS that uses the subscriber number as index, so a new configuration on HSS

side is also needed. For this reason, the procedure in this case is to remove the subscriber completely and

create it again using the new number. For this operation, please refer to Chapters below:

Chapter 1.4 - Remove H.248 Subscriber

Chapter 1.4 - Create New H.248 subscriber

1.41 Calling Line Identification Restriction (CLIR)

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;

MOD SS:IMPU="sip:[email protected]",NSCLIR=1;

Command Description




• MOD SS:IMPU="sip:[email protected]",NSCLIR=1;



Provisioning Guide





NSCLIR (V): This is the supplementary service “Calling Line Identification Restriction Right”, You must set “0” to


1.42 Calling Line Identification Restriction Override (RIO)

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;

MOD SS:IMPU="sip:[email protected]",NSRIO=1;

Command Description




• MOD SS:IMPU="sip:[email protected]",NSRIO=1;




NSCLIR (V): This is the supplementary service “Calling Line Identification Restriction Override Right”, You must set

“0” to deactivate, “1” to activate the feature.

1.43 List CLIR

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;


Command Description






Provisioning Guide





subscriber.


Restriction Right” feature.

1.44 List RIO

/****************************AT SPG web portal********************************/

USE ME:MENAME=ATS;


Command Description







subscriber.


Restriction Override Right” feature.

1.45 Apply Number Change Announcement for changed number

There is an A number changed to B number, when someone make a call to the A number, this call will route to an

announcement equipment to tell the caller that A number had changed to B number. The configuration only needs

to do on the site of which the A number is located. You can modify the current record or add a new one.

1.45.1 Modify a current record for number change announcement:

MOD CNACLD: P=41, PFX=K'30166489, RSNAME="RS_259", DNCATCODE="5858";

Description: if you could find the full number analysis by the CNACLD command, you need to change its RSNAME

(route select name) to the route which leads to the CTA_02, and add the DNCATCODE to 5858.

P (V): It specifies the A number’s local DN set, this value must equal to the area code of the A number.

PFX (V): It specifies the exact A number’s analysis prefix, this value must equal to the A number.


Provisioning Guide



RSNAME (V): It specifies the route select name lead to the CTA_02 which connect to the announcement

equipment. All the RSNAME for each site you could get from the table below:

Site RSNAME

SPO RS_209

RJO RS_259

CTA RS_259

MGA RS_209

BHE RS_209

RCE RS_259

DNCATCODE (V): It specifies the A number’s number Category code, this value must equal to 5858.

1.45.2 Add a new record to apply a number change announcement:

ADD CNACLD: P=41, PFX=K'30166489, CSTP=BASE, RSNAME="RS_259", MINL=8, MAXL=8,

ISERVICECHECKNAME="INVALID", NUMNAME="INVALID", CHRGNAME="INVALID", DNCATCODE="5858";

Description: if you could not find the full number analysis by the CNACLD command, you need to add the full

number use ADD CNACLD.

P (V): It specifies the A number’s local DN set, this value must equal to the area code of the A number.

PFX (V): It specifies the exact A number’s analysis prefix, this value must equal to the A number.

RSNAME (V): It specifies the route select name lead to the CTA_02 which connect to the announcement

equipment. All the RSNAME for each site you could get from the table below:

Site RSNAME

SPO RS_209

RJO RS_259

CTA RS_259

MGA RS_209

BHE RS_209

RCE RS_259

MINL (V): This parameter specifies the minimum number length of the A number with the specific call prefix, this

value must equal to the length of the A number.

MAXL (V): This parameter specifies the maximum number length of the A number with the specific call prefix, this

value must equal to the length of the A number.

DNCATCODE (V): It specifies the A number’s number Category code, this value must equal to 5858.

The other parameter in this command you do not need to change.


Provisioning Guide



2 Configuration According to the Class of Service (NCOS)

2.1 General Rules: The configuration of the class of service (NCOS) is only done at ATS side. About HSS, ENS and UGC, the

provisioning commands keeps the same. Please refer to the ADD command in the Chapter 1.

When adding a subscriber, four parameters need special attention, as below:

Call Source code (CSC): It defines the source of the call. In IMS, we use this to identify which location this

subscriber belongs to. Subscribers with different call sources cannot do local calls to each other.

Local DN Set (LP): It defines the dialing plan and rules for each are code (AC). Call sources from different

local areas shares the same Local DN set, but the local calls to different areas are blocked by ATS through

CNL control.

Restriction (Barring) Group (LMTGRP): It defines the outgoing call barring profile. Subscribers that have this

parameter configured have restriction to make calls according to a standard defined by NCOS values. For

example Subscribers that has NCOS 2 (block LDN, LDI) must be configured with parameter LMTGRP=2.

ENUM Index (ENUMIDX): It defines the number change profile. Subscribers that have this parameter

configured can have changes in calling or called number according to a standard defined by NCOS values.

For example, subscribers that has NCOS 15 (easy call) must be configured with parameter ENUMIDX=15.

Below is the current call source information for normal subscribers (NCOS 1) for the six sites (from table GVT

IMS Location Info v1.3.xls).

IMPORTANT: This information is based on the current cities that will be implemented. New cities /

location can be implemented in the future, so in this case this table will be feed with new values.

Table 1 – Call source definition for all the cities

IMS Location City

Code CNL AC

Tariff

Area

Location

Info in HSS

Location

Index in

ATS

CallSRC LDNSET

SPO7

SAO PAULO SPO 11000 11 11 SPO_ 1101 1101 11

ARUJA AUJ 11048 11 11 AUJ_ 1101 1101 11

BARUERI BRE 11071 11 11 BRE_ 1101 1101 11

BIRITIBA-MIRIM BMM 11082 11 11 BMM_ 1101 1101 11

CAIEIRAS CER 11130 11 11 CER_ 1101 1101 11

CAJAMAR CJR 11132 11 11 CJR_ 1101 1101 11

CARAPICUIBA CIV 11151 11 11 CIV_ 1101 1101 11

COTIA COA 11176 11 11 COA_ 1101 1101 11

DIADEMA DDA 11185 11 11 DDA_ 1101 1101 11

EMBU EMB 11202 11 11 EMB_ 1101 1101 11

EMBU-GUACU EBG 11203 11 11 EBG_ 1101 1101 11

FERRAZ DE VASCONCELOS FAV 11220 11 11 FAV_ 1101 1101 11

FRANCISCO MORATO FAT 11229 11 11 FAT_ 1101 1101 11

FRANCO DA ROCHA FCR 11227 11 11 FCR_ 1101 1101 11

GUARAREMA GRM 11251 11 11 GRM_ 1101 1101 11

GUARULHOS GRS 11892 11 11 GRS_ 1101 1101 11

ITAPECERICA DA SERRA ICS 11291 11 11 ICS_ 1101 1101 11

ITAPEVI ITE 11294 11 11 ITE_ 1101 1101 11

ITAQUAQUECETUBA IAQ 11300 11 11 IAQ_ 1101 1101 11


Provisioning Guide



JANDIRA JAD 11318 11 11 JAD_ 1101 1101 11

JUQUITIBA JQB 11330 11 11 JQB_ 1101 1101 11

MAIRIPORA MAR 11358 11 11 MAR_ 1101 1101 11

MAUA MAU 11370 11 11 MAU_ 1101 1101 11

MOGI DAS CRUZES MCZ 11381 11 11 MCZ_ 1101 1101 11

OSASCO OCO 11425 11 11 OCO_ 1101 1101 11

PIRAPORA DO BOM JESUS PPJ 11480 11 11 PPJ_ 1101 1101 11

POA POA 11488 11 11 POA_ 1101 1101 11

RIBEIRAO PIRES RPS 11528 11 11 RPS_ 1101 1101 11

RIO GRANDE DA SERRA RGS 11964 11 11 RGS_ 1101 1101 11

SALESOPOLIS SEP 11582 11 11 SEP_ 1101 1101 11

SANTA ISABEL SBL 11623 11 11 SBL_ 1101 1101 11

SANTANA DE PARNAIBA SPB 11589 11 11 SPB_ 1101 1101 11

SANTO ANDRE SNE 11633 11 11 SNE_ 1101 1101 11

SAO BERNARDO DO CAMPO SBO 11548 11 11 SBO_ 1101 1101 11

SAO CAETANO DO SUL SCN 11550 11 11 SCN_ 1101 1101 11

SAO LOURENCO DA SERRA SALS 11564 11 11 SALS 1101 1101 11

SUZANO SZN 11641 11 11 SZN_ 1101 1101 11

TABOAO DA SERRA TBS 11644 11 11 TBS_ 1101 1101 11

VARGEM GRANDE PAULISTA VPA 12210 11 11 VPA_ 1101 1101 11

RJO6

RIO DE JANEIRO RJO 21000 21 21 RJO_ 2101 2101 21

NITERÓI NRI 21188 21 21 NRI_ 2101 2101 21

BELFORD ROXO BERO 21037 21 21 BERO 2101 2101 21

DUQUE DE CAXIAS DQX 21088 21 21 DQX_ 2101 2101 21

NOVA IGUAÇU NIU 21199 21 21 NIU_ 2101 2101 21

CTA7

CURITIBA CTA 41000 41 412 CTA_ 4102 4102 41

ARAUCARIA AUC 41049 41 412 AUC_ 4102 4102 41

CAMPO LARGO CLG 41119 41 412 CLG_ 4102 4102 41

PINHAIS PNIS 41486 41 412 PNIS 4102 4102 41

PIRAQUARA PQA 41495 41 412 PQA_ 4102 4102 41

SAO JOSE DOS PINHAIS SJP 41585 41 412 SJP_ 4102 4102 41

ALMIRANTE TAMANDARE ATT 41015 41 412 ATT_ 4102 4102 41

COLOMBO CBX 41161 41 412 CBX_ 4102 4102 41

FAZENDA RIO GRANDE FZR 41919 41 412 FZR_ 4102 4102 41

MGA4

CAMPO MOURAO CPM 41122 44 448 CPM_ 4408 4408 44

CIANORTE CNE 41151 44 447 CNE_ 4407 4407 44

MARIALVA MRV 41382 44 442 MRV_ 4402 4402 44

MARINGA MGA 41389 44 442 MGA_ 4402 4402 44

PAICANDU PNU 41447 44 442 PNU_ 4402 4402 44

PARANAVAI PVA 41466 44 444 PVA_ 4404 4404 44

SARANDI SWW 41628 44 442 SWW_ 4402 4402 44

UMUARAMA UMR 41711 44 446 UMR_ 4406 4406 44

RCE3

RECIFE RCE 81000 81 812 RCE_ 8102 8102 81

JABOATAO DOS GUARARAPES JBO 81083 81 812 JBO_ 8102 8102 81

OLINDA OLD 81103 81 812 OLD_ 8102 8102 81

PAULISTA PUI 81115 81 812 PUI_ 8102 8102 81

CAMARAGIBE CGB 81200 81 812 CGB_ 8102 8102 81

CABO DE SANTO AGOSTINHO CBO 81029 81 812 CBO_ 8102 8102 81

BHE4

BELO HORIZONTE BHE 31000 31 31 BHE_ 3101 3101 31

BETIM BET 31085 31 31 BET_ 3101 3101 31

CONTAGEM CEM 31856 31 31 CEM_ 3101 3101 31

2.2 List of NCOS

Below is a list with the current NCOS implemented on IMS, with description of each service function.

IMPORTANT: For NCOS used for VoIP services (Always local, Vox3G, VoxIP, 9x), there is also a new

procedure. These services will be explained in a separated document that will be provided after the

homologation phase of this solution.


Provisioning Guide



Table 2 – NCOS definition

NCOS Call

Source

Barring

Group

Enum

Index Description

1

Refer to

Table 1

65534 65535 Liberado TOTAL

2 2 65535 Bloqueio do DDD 025 e DDI 0025, para outras operadoras pode fazer

3 3 65535 Bloqueio do 0300; 0500; 0900

4 4 65535 Bloqueio do DDD 025; DDI 0025; 0300; 0500; 0900

15 65534 15 Assinante disca sem CSP para DDD (todos) e DDG, após é inserido CSP 25 (ligue fácil)

16 65534 16 Transforma CSP todas as regiões; CSP a cobrar para todos e CSP todos os paises em 025

17 17 65535 Liberado somente para 0800 e 000x (prefixo Webline local)

19 65534 19 Transforma CSP DDD todas as regiões e CSP todos os paises em CSP 25. Nos casos de

chamadas a cobrar é considerado o CSP originalmente discado pelo cliente

20 20 65535 Liberado Chamadas locais ( 2 até 6 ) e 078 – TRANSMIT

21 21 65535 Bloqueio para celular 7; 8; 91 a 99

22 22 65535 Bloqueio do DDD 025; DDI 0025 e para celular 7; 8; 91 a 99

23 23 65535 Bloqueio para celular 7; 8; 91 a 99; 0300;; 0500; 0900

24 24 65535 Bloqueio do DDD 025; DDI 0025 e para celular 7; 8; 91 a 99; 0300; 0500; 0900

25 65534 25 Liberado somente 11x; 190 e 193; 080005xxxxx; caso assinante tente ligar é transferido

para 08006001325

30 65534 30 Igual NCOS 19 xxx_POS mais acesso internacional 100% liberado (não transforma csp

pra internacional)

31 65534 31 Igual NCOS 16 xxx_POS mais acesso internacional 100% liberado (não transforma csp

pra internacional)

32 65534 32 Igual NCOS 1 xxx_POS mais acesso internacional 100% liberado (não transforma csp pra

internacional)

33 65534 33 Igual NCOS 1 – Corporativos PBXRAMAL + 100% LDI Liberado

34 65534 34 Igual NCOS 16– Corporativos PBXRAMAL + 100% LDI Liberado

41 41 65535 Bloqueio para celular 7; 8; 91 a 99 - Corporativos PBXRAMAL com TIC - CLISERV 1041

71 71 65535 Limitador Smart Credits para assinantes com NCOS 1: Bloqueio de VC1 + VC2 e VC3 com

CSP 25

72 72 72 Limitador Smart Credits para assinantes com NCOS 15: Bloqueio de VC1 + VC2 e VC3

com CSP 25

2.3 Commands for provisioning

2.3.1 NCOS 1

USE ME: MENAME=ATS;

ADD SBR:IMPU="sip:[email protected]",LP=XX,CSC=YYYY, TEMPLATEIDX=1, LMTGRP=65534,

ENUMIDX=65535;

MOD SS:IMPU="sip:+ [email protected]",NSCLIP=1,NSSCCA=1;

Where : XX is the local DN set, YYYY is the call source according the “Table 1”.

2.3.2 NCOS 2

USE ME: MENAME=ATS;

MOD SBR:IMPU="sip:[email protected]",LP=XX,CSC=YYYY, TEMPLATEIDX=1, LMTGRP=2,

ENUMIDX=65535;


Provisioning Guide





2.3.3 NCOS 3

USE ME: MENAME=ATS;


ENUMIDX=65535;



2.3.4 NCOS 4

USE ME: MENAME=ATS;


ENUMIDX=65535;


Where : XX is the local DN set, YYYY is the callsource according the “Table 1”

2.3.5 NCOS 15

USE ME: MENAME=ATS;


ENUMIDX=15;



2.3.6 NCOS 16

USE ME: MENAME=ATS;


ENUMIDX=16;




Provisioning Guide



2.3.7 NCOS 17

USE ME: MENAME=ATS;


ENUMIDX=65535;



2.3.8 NCOS 19

USE ME: MENAME=ATS;


ENUMIDX=19;



2.3.9 NCOS 20

USE ME: MENAME=ATS;


ENUMIDX=65535;



2.3.10 NCOS 21

USE ME: MENAME=ATS;


ENUMIDX=65535;



2.3.11 NCOS 22

USE ME: MENAME=ATS;


Provisioning Guide




ENUMIDX=65535;



2.3.12 NCOS 23

USE ME: MENAME=ATS;


ENUMIDX=65535;



2.3.13 NCOS 24

USE ME: MENAME=ATS;


ENUMIDX=65535;



2.3.14 NCOS 25

USE ME:MENAME=HSS;


USE ME: MENAME=ATS;


ENUMIDX=25;


Where : XX is the local DN set, YYYY is the call source according the “Table 1”

2.3.15 NCOS 30

USE ME: MENAME=ATS;


Provisioning Guide




ENUMIDX=30;



2.3.16 NCOS 31

USE ME: MENAME=ATS;


ENUMIDX=31;



2.3.17 NCOS 32

USE ME: MENAME=ATS;


ENUMIDX=32;



2.3.18 NCOS 33

USE ME: MENAME=ATS;


ENUMIDX=33;



2.3.19 NCOS 34

USE ME: MENAME=ATS;


ENUMIDX=34;



Provisioning Guide




2.3.20 NCOS 41

USE ME: MENAME=ATS;


ENUMIDX=65535;



2.3.21 NCOS 71

USE ME: MENAME=ATS;


ENUMIDX=65535;



2.3.22 NCOS 72

USE ME: MENAME=ATS;


ENUMIDX=72;



2.4 General Blocking for Retail Subscribers

2.4.1 xxxBIO

Block

/****************************AT SPG web portal********************************/

USE ME:MENAME=HSS;

ADD HSIFC: IMPU=" sip:[email protected] ", SIFCID=629;

USE ME: MENAME=ATS;


Provisioning Guide



MOD SBR:IMPU="sip:[email protected]", OUTRST=NO, INRST=YES, LMTGRP=9001;

MOD SS:IMPU="sip:[email protected]", NSSCCA=0;

Command Description










SIFCID (V): This is an index value. GVT standard is AC+P, and P can assume the follow values:




9 - For traffic terminated on ATS, used only for General Block service, ex 629

Here an IFC set with index 629 was added to the subscriber, for the purpose of triggering the call to ATS, which the

callee number is Emergency Number, and ATS analyses the callee number, decide the call will reject or not.




• MOD SBR: IMPU="sip:[email protected]", OUTRST=NO, INRST=YES, LMTGRP=9001;





OUTRST (V): It specifies the type of the carrier-determined barring service and the outgoing call restriction status of

a subscriber. If "NO" is selected, all outgoing calls of a subscriber are permitted; if "YES" selected, all outgoing calls

of a subscriber are rejected. Here this parameter should be set to “NO”, because the user can make a call to some

specifically numbers.

INRST (V): It specifies the type of the carrier-determined barring service and the incoming call restriction status of a

subscriber. If "NO" is selected, all incoming calls of a subscriber are permitted; if "YES" selected, all incoming calls of

a subscriber are rejected. Here this parameter should be set to “YES”, because the user cannot receive any call.

LMTGRP (V): It specifies the restriction group number of a specified subscriber. This parameter is used for the

Outgoing Call Barring: Fixed (OCB-F) service. According to GVT’s requirement, for General Blocking service, this

parameter should be 9001.

• MOD SS:IMPU="sip:[email protected]", NSSCCA=0;


Provisioning Guide







NSSCCA (F): It specifies the Collect Call (SCCA) service right of a subscriber. This parameter is one of the elements

Supplement Service Right. Here this parameter should be set to “0”.

Unblock

/****************************AT SPG web portal********************************/

USE ME:MENAME=HSS;

RMV HSIFC: IMPU=" sip:[email protected] ", SIFCID=629;

USE ME: MENAME=ATS;

MOD SBR:IMPU="sip:[email protected]", OUTRST=NO, INRST=NO, LMTGRP=65534;

MOD SS:IMPU="sip:[email protected]", NSSCCA=1;

Command Description




• RMV HSIFC:IMPU="sip:[email protected]", SIFCID=629;

Description (V): Remove a shared initial filter criteria (iFC) set for the specified IMPU.




SIFCID (V): This is an index value. GVT standard is AC+P, and P can assume the follow values.

1-For intra-office traffic, used for Retail and Corporate, ex: 621



9 - For traffic terminated on ATS, used only for General Block service, ex 629

Here this parameter should be the same as we added in the Block, using command ADD HSIFC.




• MOD SBR: IMPU="sip:[email protected]", OUTRST=NO, INRST=NO, LMTGRP=65534;






Provisioning Guide



OUTRST (V): It specifies the type of the carrier-determined barring service and the outgoing call restriction status of

a subscriber. If "NO" is selected, all outgoing calls of a subscriber are permitted; if "YES" selected, all outgoing calls

of a subscriber are rejected. Here this parameter should be set to “NO”.

INRST (V): It specifies the type of the carrier-determined barring service and the incoming call restriction status of a

subscriber. If "NO" is selected, all incoming calls of a subscriber are permitted; if "YES" selected, all incoming calls of

a subscriber are rejected. Here this parameter should set to “NO”.

LMTGRP (V): It specifies the restriction group number of a specified subscriber. This parameter is used for the

Outgoing Call Barring: Fixed (OCB-F) service. If the value of Restriction group is the same as the value of Restriction

group defined by running ADD CLRGRP in the MML Command - ATS9900 window, the call is restricted. Here should

be set as wildcard value “65534” since subscribe is unblocked.

• MOD SS:IMPU="sip:[email protected]", NSSCCA=1;





NSSCCA (F): It specifies the Collect Call (SCCA) service right of a subscriber. This parameter is one of the elements

Supplement Service Right. Here this parameter should be set as GVT’s default value “1”.

Documents

IMS - Provisioning Guide for Retail v3.1