Collecting Agent HiPath COL PDF

Documentation
HiPath 4000 Assistant/Manager V6

Collecting Agent/HiPath COL
Help
A31003-H3460-M104-4-76A9
Siemens Enterprise Communications

www.siemens-enterprise.com
Our Quality and Environmental Management Sys-
tems are implemented according to the requirements
of the ISO9001 and ISO14001 standard certified by
an external certification company.
Copyright © Siemens Enterprise

Communications GmbH & Co. KG July 2012
Hofmannstr. 51, D-80200 München
Siemens Enterprise Communications GmbH & Co.
KG is a Trademark Licensee of Siemens AG
Reference No.: A31003-H3460-M104-4-76A9
The information provided in this document contains
merely general descriptions or characteristics of
performance which in case of actual use do not always
apply as described or which may change as a result of
further development of the products. An obligation to
provide the respective characteristics shall only exist if
expressly agreed in the terms of contract. Availability
and technical specifications are subject to change with-
out notice.
OpenScape, OpenStage and HiPath are registered
trademarks of Siemens Enterprise
Communications GmbH & Co. KG.
Siemens Enterprise Communications All other company, brand, product and service names
www.siemens-enterprise.com are trademarks or registered trademarks of their re-
spective holders.
HiPath_COLIVZ.fm
Nur für den internen Gebrauch Collecting Agent/HiPath COL - Content
Collecting Agent/HiPath COL - Content 0
1 PM/COL Installation Instructions -- Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

1.1 Important Hints Before Starting -- Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
1.1.1 HiPath 4000 Manager – Performance Management (PM) . . . . . . . . . . . . . . . . . . 1-3
1.1.2 Performance Management (PM) - Connection Types. . . . . . . . . . . . . . . . . . . . . . 1-4
1.1.3 Call Charge Data Registration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
1.1.4 Data Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
1.1.5 Collecting Agent (COL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
1.1.6 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
1.1.7 Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
1.1.8 Collecting Agent (COL) -- Important Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
1.1.9 Security Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
1.2 Installation Hints for Performance Management (PM) . . . . . . . . . . . . . . . . . . . . . . . . 1-15
1.2.1 Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
1.2.2 HiPath 4000 System Installation - Step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
1.2.6 Installing PM on the HiPath 4000 Manager - Step 1 . . . . . . . . . . . . . . . . . . . . . . 1-21
1.2.10 Installing PM on the HiPath 4000 Manager - Step 5 . . . . . . . . . . . . . . . . . . . . . 1-25
1.2.11 Installing PM on the HiPath 4000 Manager - Step 6 . . . . . . . . . . . . . . . . . . . . . 1-26
1.2.12 AMO DAGR - Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27
1.2.12.1 Increased Security -- Automatic Copying of FT_INTERN_FILE . . . . . . . . 1-28
1.2.13 Transferring FTBL batch from HiPath 4000 Manager to Client PC . . . . . . . . . . 1-29
1.2.14 Adapting the FTBL File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-32
1.3 Trunk Group Measurement for Separating AM and PM Data in Collecting Agent V2.0 1-
33
1.3.1 Trunk Group Measurement on HiPath 4000 Systems. . . . . . . . . . . . . . . . . . . . . 1-34
1.3.2 AMO SELG -- Block Size Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-35
2 HiPath COL / Collecting Agent – Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2.1 COL Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
2.2 Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
3 Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.1 Collecting Agent / HiPath COL User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.2 Launching the Collecting Agent / HiPath COL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
3.2.1 Launching HiPath COL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
3.2.2 Launching the Collecting Agent in HiPath 4000 Assistant/Manager . . . . . . . . . . . 3-6
A31003-H3460-M104-4-76A9, July 2012

Collecting Agent / HiPath COL, Help 0-1
HiPath_COLIVZ.fm
Collecting Agent/HiPath COL - Content Nur für den internen Gebrauch
3.3 Collecting Agent / HiPath COL - Homepage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

3.3.1 Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
3.3.2 Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
3.3.3 Navigation Pane and Application Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
3.3.4 Content Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
3.3.5 Multiple Selection of Records in List View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
3.3.6 Sorting of Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
3.3.7 Switching from List View to Object View by Double Click . . . . . . . . . . . . . . . . . . 3-20
3.4 COL Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
3.5 Controlling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
3.6 Collecting Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
3.7 Output Line Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
3.8 Definition of Input Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
3.8.1 Differences in System Management of HiPath COL versus HiPath 4000 Assistant/Ma-
nager Collecting Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
3.8.2 Definition of Input Lines Using the Collecting Agent in HiPath 4000 Assistant/Manager
3-33
3.8.2.1 Object List (System Management – HiPath 4000 Administration) . . . . . . . . . 3-34
3.8.2.2 Collecting Agent tab sheet (System Management – HiPath 4000 Administration)
3-35
3.8.2.3 COL Administration sub tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36
3.8.2.4 Trunk Group/CDR sub tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39
3.8.2.5 Attendant Consoles sub tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43
3.8.2.6 Node No. Transform sub tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45
3.8.2.7 ISDN Access Codes sub tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47
3.8.3 Definition of Input Lines using HiPath COL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-49
3.8.3.1 Object List view, System Management dialog in HiPath COL . . . . . . . . . . . . 3-50
3.8.3.2 COL Administration tab sheet (System Management in HiPath COL). . . . . . 3-52
3.8.3.3 Communication Parameter tab sheet (System Management in HiPath COL) 3-54
3.8.3.4 ISDN Access Codes tab sheet (System Management in HiPath COL) . . . . . 3-56
3.9 Input Format Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58
3.10 Pre-defined Formats for Defining CDR Input and Output Formats . . . . . . . . . . . . . . 3-59
3.10.1 Pre-defined Input and Output Formats Are Reset to Default Settings During Initializa-
tion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-61
3.10.2 Default Input and Output Formats Cannot Be Modified Any More . . . . . . . . . . . 3-62
3.11 Input Format Editor - Object view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63
3.12 Input Format Editor - Object List view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66
3.13 Input Format Editor - Set Default Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-68
3.14 Input Format Editor - Configure Input Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-70
3.15 Definition of Output Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72
3.15.1 Parallel Output of CDR Data on Multiple Output Devices in HiPath 4000 V1.0 . 3-75
3.16 Output Line Definition - Object List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-76
3.17 Output Format Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78
3.18 Output Format Editor - Object List view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-82
A31003-H3460-M104-4-76A9, July 2012

0-2 Collecting Agent / HiPath COL, Help
HiPath_COLIVZ.fm
3.19 Configure Output Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-84

3.20 Filter Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-86
3.21 Filter Editor - Object List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-89
3.22 Filter Editor - Set Default Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-91
3.23 Translation Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-93
3.24 Translation Table Editor, Object List view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-95
3.25 Translation Table Editor, Object view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-97
3.26 Translation Group Editor, Object List view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-99
3.27 Translation Group Editor, Object view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-101
3.28 Incorrect Records - Send Back To Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103
3.29 Saved CDRs in Backup File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-106
3.30 Files Ready for Output Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-107
3.31 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-108
3.31.1 Options - COL Paths tab sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-109
3.31.2 Options - Settings tab sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-111
3.31.3 Options - Process Controlling tab sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-114
3.32 Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-116
3.33 COL Logging Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-118
3.34 CDR Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-120
3.35 Exporting Log Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-122
3.35.1 Run Report Dialog - Output Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-123
3.35.2 Run Report Dialog - E-mail Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-124
3.35.3 Run Report Dialog - Export Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-125
3.35.4 Run Report - Status Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-126
3.35.5 COL Logging Events Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-127
4 Field and Controls Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.1 Collecting Agent/HiPath COL Homepage, field descriptions . . . . . . . . . . . . . . . . . . . . 4-3
4.2 Fields displayed when Controlling link is active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
4.3 Collecting Status dialog, field descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
4.4 Output Line Status dialog, field descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
4.5 HiPath COL – System Management dialog, field descriptions . . . . . . . . . . . . . . . . . 4-12
4.5.1 COL Administration tab sheet - System Management dialog (HiPath COL only) 4-16
4.5.2 Communication Parameter tab sheet - System Management dialog (HiPath COL only)
4-20
4.5.3 ISDN Access Codes tab sheet - System Management dialog . . . . . . . . . . . . . . 4-22
4.5.4 System Management dialog, Object List view (HiPath COL only), field descriptions 4-
23
4.6 Input Format Editor - Object view, field descriptions . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
4.7 Input Format Editor - Object List view, field descriptions . . . . . . . . . . . . . . . . . . . . . . 4-30
4.8 Input Format Editor - Set Default Value, field descriptions . . . . . . . . . . . . . . . . . . . . 4-32
4.9 Input Format Editor - Configure Input Element, field descriptions . . . . . . . . . . . . . . . 4-33
4.10 Output Line Definition - Object view, field descriptions . . . . . . . . . . . . . . . . . . . . . . 4-35
4.11 Output Line Definition - Object List view, field descriptions . . . . . . . . . . . . . . . . . . . 4-38
4.12 Output Format Editor - Object view, field descriptions. . . . . . . . . . . . . . . . . . . . . . . 4-40
A31003-H3460-M104-4-76A9, July 2012

HiPath_COLIVZ.fm
4.13 Output Format Editor - Object List view, field descriptions . . . . . . . . . . . . . . . . . . . . 4-44
4.14 Output Format Editor - Configure Output Element, field descriptions . . . . . . . . . . . . 4-46
4.15 Filter Editor - Object view, field descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48
4.16 Filter Editor - Object List view, field descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51
4.17 Filter Editor - Set Default Value, field descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . 4-53
4.18 Translation Table Editor - Object view, field descriptions . . . . . . . . . . . . . . . . . . . . . 4-54
4.19 Translation Table Editor - Object List view, field descriptions. . . . . . . . . . . . . . . . . . 4-57
4.20 Translation Group Editor - Object view, field descriptions . . . . . . . . . . . . . . . . . . . . 4-59
4.21 Translation Group Editor - Object List view, field descriptions . . . . . . . . . . . . . . . . . 4-62
4.22 Incorrect Records dialog, field descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64
4.23 Saved CDRs in Backup File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-66
4.24 Files Ready for Output Lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-67
4.25 COL Paths tab sheet, Options dialog, field descriptions . . . . . . . . . . . . . . . . . . . . . . 4-68
4.26 Settings tab sheet, Options dialog, field descriptions . . . . . . . . . . . . . . . . . . . . . . . . 4-70
4.27 Process Controlling tab sheet, Options dialog, field descriptions . . . . . . . . . . . . . . . 4-75
4.28 Options dialog, Save button description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78
4.29 Logging dialog (log file) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-79
4.29.1 COL Logging Events dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-81
4.29.2 COL Logging Events Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82
4.30 CDR Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-84
4.31 Collecting Agent tab sheet in System Management . . . . . . . . . . . . . . . . . . . . . . . . . 4-86
4.31.1 COL Administration sub tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-87
4.31.2 Trunk Group/CDR sub tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-93
4.31.3 Attendant Consoles sub tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-101
4.31.4 Node No. Transform sub tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-102
4.32 Fields and Controls in the Run Report Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-104
5 Step-By-Step Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.1 COL Homepage and Navigation Tree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
5.2 Controlling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
5.3 Collecting Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
5.4 Output Line Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
5.5 System Management in HiPath COL versus HiPath 4000 Assistant/Manager Collecting
Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
5.5.1 Adding a System In HiPath COL System Management . . . . . . . . . . . . . . . . . . . . 5-11
5.5.2 Adding a System in HiPath 4000 Assistant/Manager System Management . . . . 5-12
5.6 COL Administration tab sheet in System Management dialog in HiPath COL . . . . . . 5-13
5.7 Communication Parameter tab sheet in System Management dialog in HiPath COL 5-17
5.8 System Management dialog, Object List view in HiPath COL . . . . . . . . . . . . . . . . . . 5-18
5.9 Input Format Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
5.10 Input Format Editor - Set Default Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
5.11 Input Format Editor - Configure Input Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
5.12 Start/Stop PM Collecting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
5.13 Format Assignment/Format Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
5.14 Output Line Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
A31003-H3460-M104-4-76A9, July 2012

HiPath_COLIVZ.fm
5.15 Output Format Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26

5.16 Output Format Editor - Configure Output Element. . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
5.17 Filter Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29
5.18 Filter Editor - Set Default Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
5.19 Translation Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
5.19.1 Translation Table Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
5.19.2 Translation Group Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35
5.20 Incorrect Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38
5.21 Saved CDRs in Backup File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39
5.22 Files Ready for Output Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
5.23 CDR Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41
5.24 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42
5.25 Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45
6 Reference Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
6.1 Field Descriptions and User Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
6.2 Elements for Defining Input and Output Formats for COL CDRs . . . . . . . . . . . . . . . 6-49
6.2.1 Fixed Values in FTBL Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-80
6.2.2 AMO Text Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-87
6.3 Pre-defined Formats for Output Format Definition . . . . . . . . . . . . . . . . . . . . . . . . . . 6-97
6.4 Pre-defined Formats for Input Format Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-138
6.5 Additional CM Elements for Defining CDR Output Formats . . . . . . . . . . . . . . . . . . 6-185
6.5.1 CM Elements Used for Generating History Output . . . . . . . . . . . . . . . . . . . . . . 6-185
6.5.2 CM Elements Used for Transforming Virtual to Physical Node Numbers . . . . . 6-188
6.5.2.1 Loading the col_port and col_switch Tables. . . . . . . . . . . . . . . . . . . . . . . . 6-190
7 Configuration Examples - Data Collection Using HiPath COL . . . . . . . . . . . . . . . . . 7-1
7.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
7.1.1 Language of the User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
7.1.2 Cancel Background Processes (COLProcM Service) . . . . . . . . . . . . . . . . . . . . . . 7-4
7.2 HiPath 4000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
7.2.1 Configuring HiPath 4000 Call Data Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
7.2.2 Configuring HiPath 4000 for File Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
7.2.3 HiPath 4000 – HiPath COL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
7.2.3.1 HiPath 4000 – Setting Up Input Lines (Systems) . . . . . . . . . . . . . . . . . . . . . 7-10
7.2.3.2 HiPath 4000 – Setting Up Output Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
7.2.4 HiPath 4000 – HiPath AM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
7.2.4.1 With HiPath 4000 Manager Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
7.2.4.2 Without HiPath 4000 Manager Exchange. . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29
7.3 HiPath 4000 Manager Collecting Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34
7.3.1 Configuring HiPath 4000 Manager Collecting Agent. . . . . . . . . . . . . . . . . . . . . . 7-35
7.3.2 HiPath 4000 Manager Collecting Agent – HiPath COL . . . . . . . . . . . . . . . . . . . . 7-37
7.3.2.1 HiPath 4000 Manager Collecting Agent – Setting Up Input Lines (Systems) 7-38
7.3.2.2 HiPath 4000 Manager Collecting Agent – Setting Up Output Lines . . . . . . . 7-41
7.3.3 HiPath 4000 Manager Collecting Agent – HiPath AM . . . . . . . . . . . . . . . . . . . . . 7-43
A31003-H3460-M104-4-76A9, July 2012

HiPath_COLIVZ.fm
7.3.4 HiPath 4000 Manager Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-48

7.3.4.1 Creating a Login in HiPath 4000 Manager for HiPath AM (Customer Data) and Hi-
Path COL (Call Data). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-49
7.3.4.2 HiPath 4000 Manager Collecting Agent – Activate Access Rights for the XIE Inter-
face . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-50
7.3.4.3 Special Items with HiPath 4000 Manager – XIE Interface . . . . . . . . . . . . . . . 7-51
7.4 HiPath 4000 Assistant Collecting Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-52
7.4.1 Configuration of HiPath 4000 Assistant Collecting Agent. . . . . . . . . . . . . . . . . . . 7-53
7.4.1.1 HiPath 4000 Assistant Collecting Agent – Setting Up Output Lines . . . . . . . 7-54
7.4.2 HiPath 4000 Assistant Collecting Agent – HiPath COL . . . . . . . . . . . . . . . . . . . . 7-56
7.4.2.1 HiPath 4000 Assistant Collecting Agent – Setting Up Input Lines (Systems) 7-57
7.4.2.2 HiPath 4000 Assistant Collecting Agent – Setting Up Output Lines . . . . . . . 7-61
7.4.3 HiPath 4000 Assistant Collecting Agent – HiPath AM . . . . . . . . . . . . . . . . . . . . . 7-63
7.4.4 HiPath 4000 Assistant Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-68
7.4.4.1 Creating a Login in HiPath 4000 Assistant for HiPath AM (Customer Data) and Hi-
Path COL (Call Data). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-69
7.4.4.2 HiPath 4000 Assistant Collecting Agent – Activate Access Rights for the XIE In-
terface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-70
7.4.4.3 Special Items with HiPath 4000 Assistant – XIE Interface. . . . . . . . . . . . . . . 7-71
7.5 HiPath 5000 (HiPath 5300, HiPath 5500) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-72
7.5.1 Configuration of HiPath 5000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-73
7.5.2 HiPath 5000 – HiPath COL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-76
7.5.2.1 HiPath 5000 – Setting Up Input Lines (Systems). . . . . . . . . . . . . . . . . . . . . . 7-77
7.5.2.2 HiPath 5000 - Setting Up Output Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-80
7.5.3 HiPath 5000 - HiPath AM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-82
7.6 HiPath OpenScape Voice with IPSec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-86
7.6.1 Administration Steps for OpenScape Voice using HiPath COL . . . . . . . . . . . . . . 7-86
7.6.1.1 OpenScape Voice Collecting Agent - Setting up Input Lines (systems) . . . . 7-87
7.6.1.2 OpenScape Voice Collecting Agent - Setting up Output Lines . . . . . . . . . . . 7-89
7.6.2 Configuration on the OpenScape Voice system. . . . . . . . . . . . . . . . . . . . . . . . . . 7-90
7.7 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-90
7.8 HiPath AllServe (HiPath AllServe 150 V1.0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-91
7.8.1 Configuration: Installation of HiPath AM/COL on a Separate System (PC) . . . . . 7-92
7.8.2 Configuration: Installation of HiPath AM/COL on the HiPath AllServe Server . . . 7-93
7.8.3 Configuring the HiPath AllServe System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-94
7.8.3.1 Setting Up the Call Charge Data Output in HiPath AllServe 150 V1.0 . . . . . 7-95
7.8.4 HiPath AllServe - HiPath COL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-97
7.8.4.1 Setting Up Input Lines (Systems) for Collecting HiPath AllServe Data via FTP 7-
98
7.8.4.2 Setting Up Input Lines (Systems) for Collecting HiPath AllServe Data via Local File
System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-101
7.8.4.3 HiPath AllServe - Setting Up Output Lines . . . . . . . . . . . . . . . . . . . . . . . . . 7-104
7.8.5 HiPath AllServe - HiPath AM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-106
7.9 Incorrect Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-111
A31003-H3460-M104-4-76A9, July 2012

HiPath_COLIVZ.fm
7.10 HiPath AM FTP Collecting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-112

7.11 Call Collecting from HiPath 4000 Manager/Assistant without HiPath COL . . . . . . 7-113
7.11.1 HiPath 4000 Manager Collecting Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-114
7.11.2 Configuring HiPath 4000 Manager Collecting Agent. . . . . . . . . . . . . . . . . . . . 7-115
7.11.3 HiPath 4000 Manager Collecting Agent - HiPath AM . . . . . . . . . . . . . . . . . . . 7-117
7.11.4 HiPath 4000 Manager Collecting Agent – HiPath 4000 Manager Exchange . 7-122
7.11.4.1 Creating a Login in HiPath 4000 Manager for HiPath AM (Customer Data) and
HiPath COL (Call Data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-123
7.11.4.2 HiPath 4000 Manager Collecting Agent - Activate Access Rights for the XIE In-
terface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-124
7.11.4.3 Special Items with HiPath 4000 Manager - XIE Interface. . . . . . . . . . . . . 7-125
7.11.5 HiPath 4000 Assistant Collecting Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-126
7.11.6 Configuration of HiPath 4000 Assistant Collecting Agent . . . . . . . . . . . . . . . . 7-127
7.11.6.1 HiPath 4000 Assistant Collecting Agent – Setting Up Output Lines . . . . . 7-128
7.11.7 HiPath 4000 Assistant Collecting Agent – HiPath AM. . . . . . . . . . . . . . . . . . . 7-130
7.11.8 HiPath 4000 Assistant Collecting Agent – HiPath 4000 Assistant Exchange . 7-130
7.11.9 HiPath 4000 Assistant Collecting Agent – Activate Access Rights for the XIE Interface
7-130
7.11.9.1 Special Items with HiPath 4000 Assistant - XIE Interface . . . . . . . . . . . . 7-131
7.12 HiPath 4000 Manager Collecting Agent - Configuration for AM/PM . . . . . . . . . . . 7-132
7.12.1 How Do I Add an Additional Output Line for PM in COL, Having One Existing AM Out-
put Line? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-133
7.12.2 HiPath 4000 Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-134
7.12.3 Generating the TieLine Reconciliation Table – Valid for HiPath 4000 Assistant/Mana-
ger V1.0 Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-136
7.12.4 Scenario 1 – Valid for HiPath 4000 Assistant/Manager V1.0 Only . . . . . . . . . 7-137
7.12.5 Scenario 2 – Valid for HiPath 4000 Assistant/Manager V1.0 Only . . . . . . . . . 7-140
7.13 Setting the LCR Attribute WCHREG – Valid for HiPath 4000 Assistant/Manager V1.0 Only
7-141
7.14 Retrieving AM Data Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-142
7.15 Deactivating the AM Input Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-143
7.16 Creating an Input Format for a specific Variant . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-144
7.17 Activating the AM and PM Input Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-146
7.18 Setting the AM Filter for the AM Output Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-147
7.19 Verifying the AM Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-148
7.20 Verifying the PM Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-149
7.21 Enhancing the AM Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-150
7.22 Activating a Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-151
7.23 AMO Text - Configuration for HiPath 4000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-152
8 Error Messages and Error Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
8.1 Input Line(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
8.2 Output Line(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
8.3 Database Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
8.4 Connection Errors (HiPath 4000 Expert Access). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
A31003-H3460-M104-4-76A9, July 2012

HiPath_COLIVZ.fm
8.5 Automatic Forwarding of Alarms to Fault Management . . . . . . . . . . . . . . . . . . . . . . . . 8-6

9 Attachments to the Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
9.1 DISPLAY-DAGR; ... DISPLAY-FBTN:TAB=TN; . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
9.2 Examples: B01 - B71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-76
9.3 Examples: S01 - S20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-114
10 Using the Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
10.1 Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
10.2 Overview of Key Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
10.3 How to Use the Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
10.3.1 Open the Help Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
10.3.2 Searching Within the Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
10.3.3 Printing Help Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
10.3.4 Key Combinations in the Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Z-1
A31003-H3460-M104-4-76A9, July 2012

Getting_Started_COL_PM.fm
Nur für den internen Gebrauch PM/COL Installation Instructions -- Getting Started
1 PM/COL Installation Instructions -- Getting Started

Important Hints Before Starting -- Overview
Installation Hints for Performance Management (PM)
A31003-H3460-M104-4-76A9, July 2012

PM/COL Installation Instructions -- Getting Started Nur für den internen Gebrauch
1.1 Important Hints Before Starting -- Overview

HiPath 4000 Manager – Performance Management (PM)
Performance Management (PM) - Connection Types
Call Charge Data Registration
Data Volume
Collecting Agent (COL)
Restrictions
Error Messages
Collecting Agent (COL) -- Important Notes
Security Notes
A31003-H3460-M104-4-76A9, July 2012

1.1.1 HiPath 4000 Manager – Performance Management (PM)

● PM is a WEB based application providing statistics on the traffic load of lines and trunk
groups (PM-N), and analysis results regarding the call activity of subscribers/stations, hunt
groups, attendant consoles and attendant console groups.
● PM-N (Network) replaces PM-Charts, and is operational on HiPath 4000 systems.
● PM-E (Enhanced) replaces CTM, and is operational on HiPath 4000 systems.
● PM in its current version is based on the evaluation of call charge data records (CDRs). To
support this feature, the Call Charge Registration (incoming, outgoing) must be configured
on all switches.
● The call charge data records are collected network-wide by the Collecting Agent (COL) and
stored separately for AM and PM.
A31003-H3460-M104-4-76A9, July 2012

1.1.2 Performance Management (PM) - Connection Types
A31003-H3460-M104-4-76A9, July 2012

1.1.3 Call Charge Data Registration
1 HiPath 4000
All types of call data (incoming, outgoing, internal) can be filtered selectively and saved in the
CGD area (30 MB) of the switch hard disk in a file (FTFILE). A combined AM+PM call data
record has a size of approximately 328 bytes. Depending on the traffic load and on the security
buffer settings, the file (FTFILE) will have to be collected by COL at correspondingly frequent
intervals.
Number of data records/day * 328 bytes -> Collecting Frequency
Example: 45,000 data records/day = 14 MB/day = 2 MB/h (calculated for an 8-hours work
day).
Basic Rules for Activating PM on a Switch

Empirical Formula (similar to CDR-E): Activating PM causes a 15% reduction of the BHCA ca-
pacity, which corresponds to a 20% increase of the CPU load on running systems
(e.g. 70%*1.2 = 84%).
Data throughput (flow rate): The output data thruput volume of the Call Charge Registration is
approximately 16,000 CDRs per hour. If the data volume exceeds this limit, CDR data loss may
occur. For calculating the threshold (limit) value, the peak load must be used.
Metering objects in PM for calculating the CDR volume: B Channels (Lines/Trunks), Subscrib-
ers/Stations, Attendant Consoles (AC), Hunt Groups, Trunk Groups (multiplied with the number
of B Channels in a trunk group), Attendant Console Groups (multiplied with the number of At-
tendant Consoles in a group), and ADP/SWU Load.
A31003-H3460-M104-4-76A9, July 2012

1.1.4 Data Volume
Factors to be Used with Metering Objects

Line/B-Channel factor = 1,4
Subscriber/station factor = 3,5
Attendant Console (AC) factor = 3,7
Hunt Group factor = (1,4 * number of stations in hunt group)
AC Group factor = (3,7 * number of ACs in a group)
Trunk Group factor = 1,4
SWU/ADP Load = 6 data records per minute (no factor)
Assumptions for Number of Calls per Metering Object (sample values)

Subscriber/station - approx. 20 calls per day
AC - approx. 200 calls per day
Hunt Group - approx. 100 calls per day
Trunk Group - approx. 3000 calls per day
These sample values need to be adapted to the existing (real) values.
For ADP/SWU, a total of 8640 call charge data records is created per switch and per day
(provided that metering is active).
A31003-H3460-M104-4-76A9, July 2012

Formula for Calculating the FTFILE Size per Day

(number of calls for metering object <X> per day *
metering objects * factor <X>* data record length per CDR) +
(number of calls for metering object <Y> per day *
metering objects * factor <Y>* data record length per CDR) +
...
(number of calls for metering object <APD/SWU Load> per day or time period *
data record length per CDR) +
...
= Size of FTFILE in Byte (/1024 = KB)
Note
> For a switch running with a load of 80% (new value would be 80% * 1.2 = 96%, i. e.
a critical value) it does not make sense to activate all trunk groups for metering.
A31003-H3460-M104-4-76A9, July 2012

1.1.5 Collecting Agent (COL)
2 Connection Types
The data transfer duration is calculated based on the size of the file to be transferred
divided by the transfer rate of the respective connection:
● LAN: 10 Mbit/s
Bsp: 15 MByte / 10 Mbit/s = 12 s
● S0: 64 kbit/s
Bsp: 15 MByte / 64 kbit/s = 1920 s = 32 min
● V.24: 9600 bit/s
Bsp: 15 MByte / 9600 bit/s = 13120 s = 3,6 h
Note: Due to initialisation, connection setup or other connection-specific delays these theoret-
ical values are not reached in practice.
3 HiPath 4000 Manager
The Server Database stores all data records from all platforms. The sum of all file sizes multi-
plied with the number of days in the observation period adds up to the hard disk space required
on the server.
Example:
15 MByte/day * 36 systems = 540 MByte/day
540 MByte/day * 30 days = 16 GByte
Attention: All CDRs are stored in the CDB. In addition to this, separate output files
> for AM and PM can be generated for further processing. Additional hard disk space
is necessary to account for these files. Therefore, you need to give special attention
to archiving/moving and deleting data, respectively.
The formula used to calculate the size of the database is a continuation of the formula used for
calculating the size of the FTFILE. If an exact calculation of the FTFILE size per switch already
exists then there is no need to add another factor for additional CDRs in the customer network.
The main difference lies in the number of bytes per CDR. In PM this is a fixed value of approx-
imately 350 Bytes/CDR in the Server Database.
A31003-H3460-M104-4-76A9, July 2012

Step 1: Determining the PM CDRs per switch

(number of calls for metering object <X> per day *
metering objects * factor <X>) +
(number of calls for metering object <Y> per day *
metering objects * factor <Y>) +
...
(number of calls for metering object <ADP/SWU load> +
...
= number of PM CDRs per switch
A31003-H3460-M104-4-76A9, July 2012

Step 2: Calculating the PM data storage requirements in the CDB

(number of PM CDRs switch <A> +
number of PM CDRs switch <B> +
... <X>) * 350 Bytes PM CDRs *
number of days of storage in PM DB (attention: work days)
= PM storage requirements in Bytes (/1024 = KB)
Please take into consideration the threshold value for the PM database size in the CommonDB
(CDB) here. Default setting = 50% of CDB size. This value can be changed in PM.
A31003-H3460-M104-4-76A9, July 2012

1.1.6 Restrictions
Due to the large data volume that can be generated when activating PM metering ob-
jects, the following restrictions have to be taken into consideration:
1. The data thruput volume on the switch is approx. 16,000 CDRs per hour
(Warning: higher thruput values may cause data loss).
Attention: The value measured at peak load times is the decisive one.
2. The size of the CDR area is limited to approx. 30 MB
(Attention: The collecting cycles need to be adjusted to the volume of data created).
3. In case of performance problems on the HiPath systems please use the empirical formula
for the CPU load calculation (old load% * 1.2 = new load%).
4. The data transfer rate depends on the communication type used (MSV1, S0). Is it possible
at all to transfer the created CDRs (collecting frequency, transfer time, security buffer)?
5. The hard disk space capacity on the Manager is limited.
6. Higher load on the Manager when processing/integrating the data records.
7. Longer evaluation period in Performance Management due to large amounts of data.
A31003-H3460-M104-4-76A9, July 2012

1.1.7 Error Messages

Error situations may occur in the Collecting Agent (COL) and Performance Management (PM)
applications, possibly causing data loss and damaging the entire system. If one of the following
error situations occurs error messages are forwarded to the Fault Management (FM)/HTS ap-
plication. If the customer does not have FM installed the error messages are also displayed in
Logging Management):
1. COL: A system cannot be reached during a collecting cycle -> in FM the respective system
is displayed in "RED" color - RETRY EXCEEDED.
Solution: Restart the Switch/Manager communication.
2. COL: If the threshold value set for the free disk space left on the /var partition has been
reached, COL will stop collecting further call charge data since there is not enough free
space available on the /var partition any more (default setting = 10% of free space must be
left on the device) -> in FM the Manager is displayed in "RED" color - NOT ENOUGH
SPACE.
Solution: Delete data on the /var partition.
3. PM: When the threshold value set for the size of the PM database is reached (default set-
ting = 50%) in the CommonDB -> in FM the Manager is displayed in "RED" color - PM-DB
FULL.
Solution: Delete/archive data from the PM CDB.
See Also
Automatic Forwarding of Alarms to Fault Management
A31003-H3460-M104-4-76A9, July 2012

1.1.8 Collecting Agent (COL) -- Important Notes
Important Notes
● Verify the estimated traffic load on every switch from time to time, and adjust the collecting
frequency, disk space requirements and archiving cycles accordingly.
● Activate PM operation sequentially, one by one, on individual switches, and keep an eye
on the traffic load.
● Explain the background reason and the necessity of regular archiving to the customer. Ar-
chiving only a few essential reports in HTML format might be sufficient in some cases, thus
making it unnecessary to save/store all CDRs.
● Especially with PM-E, be sure to make a meaningful selection of metering objects and me-
tering durations.
● The CDR data from AM and PM are stored in the /var partition of the hard disk, provided
that the default settings have not been changed.
A31003-H3460-M104-4-76A9, July 2012

1.1.9 Security Notes

● CDR backup or additional output line activated?
-> /var partition must be set to a minimum of 2 GB.
● Activate automatic forwarding of error messages from the HiPath 4000 Manager to FM, if
possible.
● HiPath alarm in case of CDR overflow activated?
● Has the size of the CGD area been verified?
● Has the number of metering objects been verified/reduced via list of metering objects?
● Load the patch that prevents the defect of the CGD area. MSC06309 + MSC06341.
A31003-H3460-M104-4-76A9, July 2012

1.2 Installation Hints for Performance Management (PM)

This document describes how to install Performance Management on HiPath 4000 systems
and the installation steps required for creating PM reports on HiPath 4000 Manager and HiPath
4000 Assistant systems, respectively.
The Important Hints Before Starting -- Overview section provides a short overview on the PM
features and basic security hints.
This document is structured as follows:
1. Flowchart for installing PM on a HiPath 4000 system
2. Flowchart for installing PM on the HiPath 4000 Assistant/Manager
3. Error detection hints
4. Cross references containing detailed information and examples referring to the flowchart
contents
Steps 1 or 2, respectively, and step 3 have to be repeated for each system on which PM is to
be activated.
Important Note:
> Before you start activating the PM metering objects on a switch you should familiar-
ize yourself with the facts in the customer network. Please read the Important Hints
Before Starting -- Overview section for this purpose.
A31003-H3460-M104-4-76A9, July 2012

1.2.1 Installation Prerequisites
Installation Prerequisites
Prerequisites for HiPath 4000/

HiPath 4000 System Installation:
● HiPath Manager is installed
● System is registered in
System Management
● System ist registered in
Configuration Management (CM)
● Upload All and LCR Upload have
been executed for the system
● The Client PC is set up as HiPath
4000 Manager Client
● A HiPath 4000 Expert Access
(ComWin) connection from the Cli-
ent PC can be established
HiPath 4000 System Installation

(1)
A31003-H3460-M104-4-76A9, July 2012

1.2.2 HiPath 4000 System Installation - Step 1
Step 1
Verify the parameters of the DMS file for Call Detail Recording
using DISPLAY-DAGR;
The file contains the following parameters: Notes (1)

● File Size = 40.000 records
● Output.Code = ASCII
● Copy Period = 1 hour
● Time of First Copy = DD-HH
● Name of Transfer File = FTFILE
Example (2)
To change the parameter values to customer-specific settings, use:
CHANGE-DAGR;
Example (3)
Step 2 (4)
A31003-H3460-M104-4-76A9, July 2012

Step 2
Verify output devices for Call Detail

Recording using DISPLAY-FEACG
Example (5)
Retrieve Selection Groups using DISPLAY-SELG

Example (6)
Deactivate CDRFAST Yes

Fast Output using CDRFAST (Charge Registra-
DELETE-FEACG tion on Fast Output Device)
activated?
Example (7)
No
Activate Immediate Out- CDRCDUMP

put using ADD-FEACG, No (Charge Registration
parameter CDRC- on Immediate Output
DUMP, otherwise no call Device) activated?
charge data records will
be generated.
Example (8) Yes
Get matching FTBP batch and AMO TEXT batch from HiPath 4000
Manager and start batch on HiPath 4000 system.
Details (9)
Step 3 (10)
A31003-H3460-M104-4-76A9, July 2012

Step 3
Retrieve Selection Groups using DISPLAY-SELG;

Example (11)
Any Selection No
Yes
Group configured
for output on FT?
Ensure that the existing Selection Group Configure a new Selection Group to
is properly configured. support FT as base device.
Use the next available Selection Group
number (1,2,3 or 4) as shown in
Example (12).
Attention: CDRFAST (Charge Regis-
tration on Fast Output Device) must be
deactivated (DISPLAY-FEACG).
Set up the line trunk number 99 using

ADD-FBTN. Yes Shall stations
Example (13) be metered?
No
Activate the selected selection group using ACTIVATE-SELS (Example 14)
Step 4 (15)
A31003-H3460-M104-4-76A9, July 2012

Step 4
As a test, place several outgoing trunk calls.
Verify whether a CDR file has been created.

Open a ComWin MML session (Example 16) and
retrieve the file (Example 17) or
Open a ComWin File Transfer session (Example 18) and
retrieve the file (Example 19).
Re-check the entire CDR

No
configuration and correct/solve
the problem. Data records
exist?
Yes
To test the Collecting Agent (COL) functionality, copy the

call data records from FT_FILE_INTERN to the transfer
file FTFILE using
COPY-DAGR; (Example 20).
Make sure that the transfer file exists
(Example 21).
The system is now ready for COLto fetch the CDR data.
Installing PM on the HiPath 4000 Manager (22)
A31003-H3460-M104-4-76A9, July 2012

1.2.6 Installing PM on the HiPath 4000 Manager - Step 1
Installing PM on the HiPath 4000 Manager
Open the Start Page (LAP=Launchpad).

(If COL is running on the ADP: Assistant,
If COL is running on the Manager: Manager).
Activate the Collecting Agent Collecting

(COL): No (9) Agent exists
Click on on Start Page
Base Administration (10). (LAP) (1)?
Click on
Application Control (11).
Check the check mark for Yes (2)
Collecting Agent (12). Click on Collecting Agent on the Start Page (LAP)
Click on Submit (13). to see the applications/features of the group.
A confirmation message (14) Click on Homepage - Collecting Agent(3).
will be displayed.
Wait for the reply (15) from the
server. Double-click on
Close the Application Control Definition of Input Lines (4)
window. (System Management opens).
Refresh (16) the display of the
Start Page (LAP) (17).
Click on Search (5) to get the
List of systems (6) displayed.
Use the Object view. For each system, activate the

Collecting Agent (7) in the Active Application
area by setting the corresponding check mark. A
new Collecting Agent tab sheet is displayed.
F (8)
A31003-H3460-M104-4-76A9, July 2012

Start a ComWin MML session and perform DISPLAY-ZAND:ALLDATA;

(18) to obtain the physical node number of the switch.
In System Management, open the Collecting Agent tab sheet on the Man-
ager or Assistant, respectively, and
enter the required values into the fields (Example 19).
Save the values.
Click on Back (20) to return to the Collecting Agent Homepage.
Click on Controlling (21) to make sure that the Input and Output Status
are both set to Active. For this purpose, click on
Start Input (22) and Start Output (23).
On the Homepage of Collecting Agent, click on

Collecting Status (24).
To test the Collecting Agent (COL) functionality, click on

Collect Now (25) in the Collecting Status dialog. Then click on
Refresh (26) several times to monitor the Transfer Status and Trans-
form Status. The status should be OK in all cases.
The CDR data is now saved on the harddisk of the Assistant/Manager, in

the /var/col/data/output folder.
Verify this in a Shell session (27)
using the commands "cd /var/col/data/output" and "find ."
G (28)
A31003-H3460-M104-4-76A9, July 2012

Activate the Performance Manage- No Performance

ment application: Management exists
Click on on Start Page (LAP)
Base Administration (36).
Click on
Application Control (37). Yes
Check the check mark for
Performance Management (38). Click on Performance Management on the Start
Click on Submit (39). Page (LAP) to see the applications/features of the
A confirmation message (40) group.
will be displayed. Click on Performance Management (30) to go to
Wait for reply (41) from server. the PM Homepage.
Close the Application Control
dialog.
Double-click on Metering Settings (31).
Refresh (42) the display of the
(System Management opens).
Start Page (LAP) (43).
Click on Search (32) to get the

List of systems (33) displayed.
Use the Object view. For each system, activate

Performance Management (34) in the Active Ap-
plication area by setting the corresponding check
mark. A new Performance Management tab sheet is
displayed.
H (35)
A31003-H3460-M104-4-76A9, July 2012

In System Management, on a Manager or Assistant system, respectively,

open the Performance Management tab sheet,
define the metering values (44) (on a HiPath 4000 system), and save the
values.
By selecting the metering values you decide which PM data will be generated
by the HiPath 4000 system, thus influencing the data volume. Especially with
larger networks this is an important factor that needs to be taken into ac-
count. As an example, 50 HiPath 4000 systems in a network will produce
about 130 MB of data per day in the Manager DB for ADS/SWU load me-
tering only.
Close the System Management dialog.
On the PM Homepage, double-click on Filter (46)

to define a filter. A filter contains all metering objects
that should be displayed in a report.
On the PM Homepage, double-click on Report (47)

to define a report (48).
Create all reports as requested by the customer.
I (49)
A31003-H3460-M104-4-76A9, July 2012

Test the newly created report (50).
Lauch the Collecting Agent and have it collect CDR data

for some time.
Create reports for the time periods indicated by the cus-

tomer.
COL to remain
Yes active for further
reports?
No
On the Collecting Agent Homepage, click on

Controlling (51) and set the Input Status and Output
Status to Not Active. To do this, click on
Stop Input (52) and
Stop Output (53).
Start a ComWin MML session and perform

DEACTIVATE-SELS:; (Example 54). Indicate the
selection group for FT when doing this.
K (55)
A31003-H3460-M104-4-76A9, July 2012

Has a service don- Yes

gle been used for
installation?
Connect the original dongle again, and

No enter the original codeword again.
Deactivate the COL and PM applications, respectively, via

the Application Control (on the Assistant) if the customer
does not intend to continue using COL and/or PM.
The CDR configuration is available for future metering.
End
A31003-H3460-M104-4-76A9, July 2012

1.2.12 AMO DAGR - Notes
AMO DAGR -- Important Notes

File Size = nnnnn data records
Maximum value: 65535
This value sets the maximum size for the FT file. If this file size limit is reached while saving the
data records, a copy process is triggered for the file (before the automatic copy process is start-
ed (see Copy Period parameter)). If the customer specific file has not been fetched yet (see
Name of Transfer File parameter, e.g. "FTFILE"), then the FT file will be appended to this file.
Required disk space evaluation: Number of call data records * 350 Bytes (approximate size of
data record, depending on FTBL, e.g. AMPM_UV1.0.GE) * 2 (data is saved both in the FT file
and in the customer-specific file. Example: 45000 * 350 Bytes * 2 = 31500000 Bytes
(i.e. approx. 30 MB).
Output.Code = ASCII
Note: If the output code is changed (from EBCDIC to ASCII) a notification message will be is-
sued. In this case you need to copy the file manually to ensure that the file can be fetched, and
also to avoid having data records with different formatting in the file:
1. Set the selection group to COLLECT (AMO SELS).
2. Start the file copy process (AMO K-DAGR).
3. Fetch the customer-specific FT file.
4. Change the file parameters (output code).
5. Activate the selection group.
Copy Period = hhh
Value given in hours; In case of high traffic set the minimum value 1. See also "Required disk
space evaluation", File Size parameter).
Time of First Copy = DD-HH
Sets the start time for the copy process from FT_FILE-INTERN to FTFILE.
Format: DD = Day in current or next month, HH = Hour. You can set the start time of the copy
process to a later time using this parameter. Recommended: current day, next clock hour).
Name of Transfer File = FTFILE
This is the pre-set default name in HiPath 4000 Manager, System Management area - Collect-
ing Agent).
A31003-H3460-M104-4-76A9, July 2012

1.2.12.1 Increased Security -- Automatic Copying of FT_INTERN_FILE

Increased security through Automatic Copying of FT_INTERN_FILE with Every Data Collection
Cycle for HiPath 4000 V1.0 (F53382)
By executing the AMO command COPY-DAGR with every data collection cycle in COL the
FT_INTERN_FILE is automatically appended to the FT file (FTFILE) to be fetched. This en-
sures that for each collecting cycle all existing call charge data will be fetched. This command
is only executed for HiPath 4000 V1.0.
A31003-H3460-M104-4-76A9, July 2012

1.2.13 Transferring FTBL batch from HiPath 4000 Manager to Client PC

To transfer the FTBL batch from the HiPath 4000 Manager to the Client PC, proceed as follows:
1. Create a directory for the FTBL files on the client PC (either using Windows Explorer
or via Start -> Execute -> md directory_name).
see Example
2. Start the FTP program on the client PC (using Start -> Execute -> FTP).
3. In the FTP tool, open the connection to the HiPath 4000 Manager by entering the following
command: open IP-Adresse.
4. Log on to the system as user engr or rsca by entering the corresponding password.
5. Change to the FTBL directory using cd /var/col/data/ftbl.
6. Enter pwd to check whether the current directory has been changed.
7. Set the target directory on the client PC to the directory name created in step 1 entering
lcd directory_name.
8. Set the transfer mode to "binary" by entering bin.
9. Copy the files from the current directory on the HiPath 4000 Manager to the client PC by
entering mget * (Confirm the following prompts for the individual files by entering y and
pressing the Enter key.
10. Quit the FTP tool by entering bye.
see also Example
11. If a value other than FORM01 is specified for FT in the selection group, then you need to
adjust the FTBL batch accordingly.
see Example
Execute the required FTBL command batch on the HiPath 4000 system.
12. Open a HiPath 4000 Expert Access (ComWin) connection to the system.
13. In the HiPath 4000 Expert Access (ComWin) toolbar, click Macro -> Start -> Open.
see Example
14. Select the required FTBL command batch from the directory created in step 1.
see Example
15. Start the FTBL command batch by clicking Start -> Start in the HiPath 4000 Expert Access
(ComWin) toolbar.
see Example
A31003-H3460-M104-4-76A9, July 2012

Execute the required TEXT command batch on the HiPath 4000 system:
16. In the HiPath 4000 Expert Access (ComWin) toolbar, click Macro -> Start -> Open.
17. Select the required TEXT command batch from the directory created in step 1.
18. Start the TEXT command batch by clicking Start -> Start in the HiPath 4000 Expert Access
(ComWin) toolbar.
Selecting the FTBL and TEXT command batch file, respectively:

The file names are selected according to the following scheme:
<PurposeOfUse_SystemversionProgramversion.LANGUAGE>:
● Purpose of Use:
“AM” FTBL file only for Accounting Management
“AMPM_” FTBL file for Accounting Management and Performance Management
“PM_” FTBL file only for Performance Management
“AMO_TEXT_AMPM_” batch file for AMO TEXT
● System Version:
“UV” HiPath 4000
● Program version: 1.0 for version 1.0, ...
● Language: GE for german, ...
The files are provided in both English (filename extension “.EN” or “.ENG”, respectively) and
German version (filename extension “.GE” or “.GER”, respectively).
Examples:
AMPM_UV1.0.GE FTBL file for Accounting Management and Performance Management in a
HiPath 4000 V1.0 system with German AMO language.
AMO_TEXT_AMPM_UV1.0.GER file for AMO TEXT in a HiPath 4000 V1.0 system with Ger-
man AMO language.
A31003-H3460-M104-4-76A9, July 2012

Element RECTYPE in the PM Input Formats
Please read before starting operation of Load CV631, CV645-646 and higher
> versions.
Starting with HiPath 4000 Assistant/Manager – Collecting Agent Load CV631 and CV645 the
RECTYPE element has been appended at the end of the pre-defined input formats PM_UV1.0
and later. Before starting the first call charge data collection cycle after implementing the VC
you need to adapt the Collecting Agent/COL.
Before implementing the VC you need to stop the data input. To do this, go to the Controlling
link on the COL Homepage and click on Stop Input to be able to perform the maintenance
work. Don´t forget to activate the data input again after finishing the maintenance work by click-
ing on Start Input.
There are two possibilities of adaptation:
1. The existing FTBL is to be used (FTBL unchanged).
You need to create a new user-defined input format (Copy -> Paste) and to remove the
RECTYPE element (last element) from the input data record description. Then you need
to allocate the user-defined input format to the corresponding systems.
2. The new feature is to be used = Use new FTBL.
To do this, you need to adapt the corresponding FTBLs. For all systems affected the FTBL
needs to be enhanced by adding a fixed text.
Please be sure to perform either instruction 1 or 2. If you omit to do this, the call charge data
records of all affected systems will be stored as "Incorrect Records".
A31003-H3460-M104-4-76A9, July 2012

1.2.14 Adapting the FTBL File
A FORM number is specified in each line of the FTBL file:

ADD-FTBL:1,S,FORM,1,N,"$#@@@#@#@@#@#@@@@@@@@@@@@@@@@@@@@@##@@#@@#@#@@@@@@@@@@@@@@@@";
ADD-FTBL:1,S,FORM,2,N,"@@@@@##@@#@@@@#@@@@@@@@#@@##@@@@@#@#@@#@@#@##@@@@@@@@@@@@@@@";
ADD-FTBL:1,S,FORM,3,N,"@@@@@@#@@@@@@@@##@#@#@#@#@#@@@##@@#@@#@#@@@@@@@#@@@@#@#@@@@@";
...
Use AB-SELG to query and retrieve the required value.

If necessary, change the FORM number in each line of the FTBL file.
A31003-H3460-M104-4-76A9, July 2012

Trunk Group Measurement for Separating AM and PM Data in Collecting Agent V2.0
1.3 Trunk Group Measurement for Separating AM and PM Data in

Collecting Agent V2.0
This feature is only supported in Collecting Agent under HiPath 4000 Assistant/Manager V2.0;
it is not supported in HiPath COL.
The aim of this feature is to separate the AM and PM data generated by a HiPath switch by
measuring of trunk groups.
The separation of AM and PM data is necessary in order to avoid calls to be recorded twice if
CDRs for PM are being generated on the switch.
This can only be achieved if the administrator has the possibility to define trunk groups relevant
for AM only, for PM only, or for both AM and PM.
Trunk Group Measurement on HiPath 4000 Systems
A31003-H3460-M104-4-76A9, July 2012

1.3.1 Trunk Group Measurement on HiPath 4000 Systems

The functionality of this feature has already been implemented in Version 1.0 as a CR for Hi-
Path 4000 systems and is now supported by a new, improved user interface since Version 2.0.
HiPath 4000 V1.0 generates an element RECTYPE for call charge data recording in the CDRs.
The value for RECTYPE specifies whether the data record is intended for HiPath AM only, for
PM only, for both AM and PM or for none of the two -- see table below.
RECTYPE/COLTYPE Value 0 1 2 3
Relevant for None AM PM AM + PM
Table 1-1 RECTYPE/COLTYPE Values
On HiPath 4000 V1.0 systems no additional recording of AM CDRs is necessary, and therefore
for these systems the loading of data described in the next sections is not necessary.
To separate AM and PM data on HiPath 4000 systems it is sufficient to use the output filter for
the RECTYPE element. The output filter can also be set for the new COLTYPE element, as
COLTYPE and RECTYPE always have the same value on HiPath 4000 V1.0 systems. COL-
TYPE is a calculated element, i.e. it never appears on the input. During the CDR evaluation
COL calculates the value of COLTYPE, and COLTYPE can be used in output files as any other
standard element.
A31003-H3460-M104-4-76A9, July 2012

1.3.2 AMO SELG -- Block Size Parameters

AMO SELG administers block size parameters for the Base Device (BLBAS) and for the Re-
serve Device (BLRES). If you enter the value 1 every record is immediately written to the output
device. Larger values cause the system to store the data records until the number of records
specified by the value is reached. Only then will the data records be written blockwise to the
output device. This increases the output rate. The best results are achieved with a value of 10.
Note: For HiPath 4000 systems only the value 1 makes sense.
>
Attention:
> Before changing the block size the status of the selection group needs to be set to
OFF using the AMO COLLECT-SELS.
Only then should you change the block size.
After this you can start the output again with ACTIVATE-SELS.
Another side-effect: Individual CDRs are not output until the specified number of CDRs is
reached. This can be confusing, especially with tests having only a small amount of calls.
A31003-H3460-M104-4-76A9, July 2012

A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Overview.fm
Nur für den internen Gebrauch HiPath COL / Collecting Agent – Overview
2 HiPath COL / Collecting Agent – Overview

In HiPath 4000 Assistant/Manager this application is named Collecting Agent. In the HiPath
environment, however, the same application is named COL. In this publication the common
short term COL is used for both variants. The Collecting Agent/HiPath COL is used to collect
accounting data in a HiPath network. Collecting Agent/HiPath COL is a basic function of Ac-
counting Management (AM).
HiPath COL V2.0 covers the following topics:
● Collecting CDRs from HiPath AllServe 150, H150-BackupPC, H150-ComboX
● Collecting CDRs from HiPath 5000 (Gatekeeper)
● Providing CDR output files for AM
● Flexible format support of CDRs in input and output files
● Support of CDR output filter according to certain call detail elements
● Administration of COL (activate/deactivate, scheduling of collecting, etc.)
● Logging of COL activities
● Client/server architecture of COL
Related Topics
COL Scenarios, page 2-2
Collecting Agent / HiPath COL User Interface, page 3-2
Launching the Collecting Agent / HiPath COL, page 3-4
Collecting Agent / HiPath COL - Homepage, page 3-7
COL Features, page 3-21
A31003-H3460-M104-4-76A9, July 2012

HiPath COL / Collecting Agent – Overview Nur für den internen Gebrauch
COL Scenarios
2.1 COL Scenarios

HiPath COL V2.0 collects all CDRs via a LAN interface.
CDR collecting is supported from:

● HDMS V3.6 (Element Manager)
● HiPath AllServ 150 V1.0 (Element Manager)
● HiPath 5000 V3.0 (Single System)
Related Topics
A31003-H3460-M104-4-76A9, July 2012

Nur für den internen Gebrauch HiPath COL / Collecting Agent – Overview
Languages
2.2 Languages
For HiPath COL V1.0 and V2.0 the supported languages are German and English.
To set or change the display language of your web browser, you need to set the corresponding
language parameter in your browser. Please refer to the Language of the User Interface section
for details on how to set the desired browser display language.
HiPath COL V1.0 and V2.0 support the following languages:
● German
● English
Related Topics
A31003-H3460-M104-4-76A9, July 2012

HiPath COL / Collecting Agent – Overview Nur für den internen Gebrauch
Languages
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Functionality.fm
Nur für den internen Gebrauch Functionality
3 Functionality
Main Functional Areas / Features of the Collecting Agent/HiPath COL
Controlling, page 3-23
Collecting Status, page 3-25
Output Line Status, page 3-28
Definition of Input Lines, page 3-31
Input Format Editor, page 3-58
Definition of Output Lines, page 3-72
Output Format Editor, page 3-78
Filter Editor, page 3-86
Translation Tables, page 3-93
Incorrect Records - Send Back To Input, page 3-103
Saved CDRs in Backup File, page 3-106
Files Ready for Output Lines, page 3-107
Options, page 3-108
Logging, page 3-116
COL Logging Events, page 3-118
CDR Viewer, page 3-120
Exporting Log Reports, page 3-122
Related Topics
A31003-H3460-M104-4-76A9, July 2012

Functionality Nur für den internen Gebrauch

Collecting Agent / HiPath COL User Interface
3.1 Collecting Agent / HiPath COL User Interface

HiPath COL / Collecting Agent provides a web-based user interface for COL administration
tasks, which can be grouped into the following functional categories:
● Administration of switch-specific COL parameters, e.g. enabling/disabling AM collecting as
well as the scheduling data for collecting
● Other administrative tasks, e.g. definition of input and output formats, definition of output
lines and filters, and monitoring of the COL status.
All administration tasks are launched by using the links on the COL Homepage. COL supports
the following features and functional areas:
Toolbar, page 3-10
Menu Bar, page 3-9
Navigation Pane and Application Tree, page 3-12
Content Pane, page 3-14
Options, page 3-108
Logging, page 3-116
Related Topics
COL Administration tab sheet (System Management in HiPath COL), page 3-52
A31003-H3460-M104-4-76A9, July 2012

Communication Parameter tab sheet (System Management in HiPath COL), page 3-54
Object List view, System Management dialog in HiPath COL, page 3-50
Important Hints Before Starting -- Overview, page 1-2
Installation Hints for Performance Management (PM), page 1-15
PM/COL Installation Instructions -- Getting Started, page 1-1
Exporting Log Reports, page 3-122
A31003-H3460-M104-4-76A9, July 2012


Launching the Collecting Agent / HiPath COL
3.2 Launching the Collecting Agent / HiPath COL

Launching HiPath COL
Launching the Collecting Agent in HiPath 4000 Assistant/Manager
A31003-H3460-M104-4-76A9, July 2012

3.2.1 Launching HiPath COL

The HiPath COL Homepage is started in a Web browser via a URL (IP address); it can not be
launched via the Homepage of HiPath 4000 Assistant/Manager or via the Desktop.
● To start the HiPath COL Homepage
– Enter the COL URL followed by the name of the Homepage (HiPathCOL.asp) in a web
browser or by using a bookmark containing the HiPath COL URL, e. g.
http://servername/COL/HiPathCOL.asp
– You can also create an icon on your desktop containing the COL URL link.
Related Topics
Launching the Collecting Agent in HiPath 4000 Assistant/Manager, page 3-6
Toolbar, page 3-10
Menu Bar, page 3-9
A31003-H3460-M104-4-76A9, July 2012


3.2.2 Launching the Collecting Agent in HiPath 4000 Assistant/

Manager
● To launch the Homepage of the Collecting Agent in HiPath 4000 Assistant/Manager:
– Enter the URL for the HiPath 4000 Assistant/Manager Homepage in a web browser,
e. g. https://servername/LAP/
To access the HiPath 4000 Assistant/Manager Start Page you must be a licensed
user, and you have to log in by entering your valid username and password.
– Select the desired application, in this case Collecting Agent, by clicking the applica-
tion link on the HiPath 4000 Assistant/Manager Start Page.
The following links will be displayed:
– Collecting Agent
Double-clicking this link will open the Collecting Agent Homepage, showing all
available COL features in an application tree. To launch one of these features and
get its user interface displayed, just double-click it.
– Collecting Status
Double-clicking this link will open the COL Collecting Status dialog where all con-
figured input lines will be displayed.
– Output Line Status
Double-clicking this link will open the COL Output Line Status dialog where all
configured output lines will be displayed.
– On the COL Homepage in the application tree, double-click the link of the COL feature
you want to use, e.g. Collecting Status or Output Format Editor.
The user interface of the selected COL feature will be displayed in your browser.
Related Topics
Launching HiPath COL, page 3-5
Toolbar, page 3-10
Menu Bar, page 3-9
A31003-H3460-M104-4-76A9, July 2012

Collecting Agent / HiPath COL - Homepage
3.3 Collecting Agent / HiPath COL - Homepage

The HiPath COL Homepage is started from a bookmark (URL) or by entering the IP address
in a browser window; it can not be launched via the HiPath 4000 Assistant/Manager Start Page
or via the Desktop - see Launching HiPath COL.
For HiPath 4000 Assistant/Manager, the Collecting Agent Homepage is started via the Hi-
Path 4000 Assistant/Manager Start Page or via the Desktop - see Launching the Collecting
Agent in HiPath 4000 Assistant/Manager.
The Collecting Agent / HiPath COL Homepage contains the Menu Bar, the Toolbar, the Nav-
igation Pane and Application Tree with links to the various COL features and dialogs used to
display and set COL parameters (on the left-hand side of the dialog), and the Content Pane (on
the right-hand side of the dialog) showing a short description of the currently selected item from
the application tree. An overview of the COL functionality can be found in HiPath COL / Col-
lecting Agent – Overview, page 2-1 and in COL Features, page 3-21.
For HiPath COL the Logging component is also part of HiPath COL V1.0 because HiPath 4000
Assistant/Manager Logging is not available. A basic functionality is reimplemented and can be
executed in HiPath COL. Due to this reason the user interface has been enhanced to display
the logging messages.
A31003-H3460-M104-4-76A9, July 2012


Field and Controls Descriptions

Application tree
Description of the selected tree item
Related Topics
Menu Bar, page 3-9
Multiple Selection of Records in List View, page 3-15
Sorting of Records, page 3-18
Switching from List View to Object View by Double Click, page 3-20
COL Homepage - Field Descriptions and User Actions, page 6-9
Menu Bar - Description of the Menu Options, page 6-4
Step-By-Step Instructions
COL Homepage and Navigation Tree
A31003-H3460-M104-4-76A9, July 2012

3.3.1 Menu Bar

The Menu Bar in HiPath COL / Collecting Agent contains the following menus:
● View,
● Action,
● Help,
● Object (not displayed on the COL Homepage).
The Object menu is not displayed on the COL Homepage; it is available only with those
COL features which support the display, selection and editing of a network object or of a
format, respectively.
Depending on the functionality of the COL feature selected, different and specific menu options
may be displayed in the menus.
For a detailed description of the individual menu options please refer to the
Menu Bar - Description of the Menu Options
Related Topics
Toolbar, page 3-10
A31003-H3460-M104-4-76A9, July 2012


3.3.2 Toolbar
The toolbar on the COL Homepage contains the following icons:
Toolbar in HiPath COL
Toolbar of Collecting Agent in HiPath 4000 Assistant/Manager
Print * Printing is only supported by the Collecting Agent in HiPath 4000

Assistant/Manager. The Print icon is not displayed on the Homep-
age of the Collecting Agent; the icon is only displayed in some dia-
logs supporting the Print feature, e.g. Collecting Status and Output
Line Status.
The current screen content is written to an HTML file and displayed in
a separate browser window. This separate browser window contains
a Print icon of its own. If you click on this icon, the currently displayed
content of the separate browser window is sent to the configured print-
er.
Same function as the Print Report option in the Object menu.
* Printing is only supported using the Print button from the separate
browser window.
* Activating the Definition of Input Lines feature will launch the Sys-
tem Management application (in the Collecting Agent) or the System
Management tab sheet (in HiPath COL), respectively. Clicking the
Print icon in the System Management toolbar activates the Report
Generator.
Help Activates the Context Help. The mouse pointer is displayed as an ar-
row with an adjacent question mark. When you click on an element in
your browser window with this pointer, the corresponding context-spe-
cific Help topic will be displayed in a separate Help browser window.
You can also activate the Context Help by pointing and clicking on a
specific location in the user interface and pressing CTRL+F1.
Same functionality as the Context Help option in Help menu.
Homepage Goes back to the Homepage of HiPath COL/Collecting Agent.
Same function as the Home option in the View menu.
A31003-H3460-M104-4-76A9, July 2012

Start(*) Jumps back to the HiPath 4000 Assistant/Manager Start Page.

Opens a new browser window and displays the HiPath 4000 Assistant/
Manager Start Page.
Same function as the Start option in the View menu.
* This feature is only supported in HiPath 4000 Assistant/Manager.
Logoff When you click the Logoff icon in the toolbar, a message dialog is dis-
played, warning you that all unsaved data will be lost, prompting you
to save all unsaved data from the current session and to confirm with
OK that you want to log off.
After logging off the program returns to the Logon screen.
Same function as the Logoff option in the Action menu.
Pin (Sticky Pa- Clicking on the Pin pushbutton switches the sticky page mode ON or
ge) OFF.
● OFF (default): a new applet will be launched in the currently
opened browser window.
● ON: a new applet will be launched in a new browser window.
Same function as the Sticky Page option in the View menu.
Related Topics
Menu Bar, page 3-9
A31003-H3460-M104-4-76A9, July 2012


3.3.3 Navigation Pane and Application Tree

The Navigation Pane on the left-hand side of the COL Homepage shows the Application Tree.
The application tree is similar to a menu folder structure, displaying all COL features in the form
of links the user can activate.
When a link in the navigation pane is selected with a single mouse click, a short description of
the selected feature will be displayed in the right-hand pane of the Homepage, called Content
Pane. If Controlling has been selected in the tree, the description will not be visible. See also
Controlling.
If Logging is selected, the Content pane will display the 3 different types of logs, and a View
and Delete button near each type, thus allowing the user to view or delete the desired log. See
also Logging.
COL features are launched by double-clicking on the corresponding link in the application tree.
Related Topics
Toolbar, page 3-10
Menu Bar, page 3-9
A31003-H3460-M104-4-76A9, July 2012


A31003-H3460-M104-4-76A9, July 2012


3.3.4 Content Pane

When a link in the navigation pane (on the left-hand side of the COL Homepage) is selected
with a single click, a short description of the selected link will be displayed in the right-hand
pane, called Content Pane.
If Logging is selected (this feature is only supported in HiPath COL), the Content Pane will
display the 3 different types of logs, and a View and Delete button near each type, thus allow-
ing the user to view or delete the desired log. See also Logging.
Related Topics
Toolbar, page 3-10
Menu Bar, page 3-9
A31003-H3460-M104-4-76A9, July 2012

3.3.5 Multiple Selection of Records in List View

Multiple selection of records in list view is possible in the following pages:
● Input Format Editor - Object List view, page 3-66
● Output Line Definition - Object List, page 3-76
● Output Format Editor - Object List view, page 3-82
● Filter Editor - Object List, page 3-89
● Translation Table Editor, Object List view, page 3-95
● Translation Group Editor, Object List view, page 3-99
● Incorrect Records - Send Back To Input, page 3-103
● Saved CDRs in Backup File, page 3-106
● Files Ready for Output Lines, page 3-107
After having selected more than one line, it is possible to delete the complete selection by
clicking the Delete button on the bottom of the page.
A dialog box is displayed showing the selection and prompting to confirm the deletion of all the
entries.
In case of an error in deleting one of the entries in the selection (e.g. the entry is locked etc.),
an error message is displayed, and the deletion procedure will stop. All remaining entries of the
selection will not be deleted.
The functionalities that have no meaning in a multi selection context will be disabled. Thus, for
example the Copy button will become disabled.
Selection of multiple entries in a table is done by using the mouse together with the shift or the
Ctr-key.
A31003-H3460-M104-4-76A9, July 2012


Multiple selection of a range of lines

By keeping the Shift key pressed you can select a range of values with the mouse.
When the Shift key is released selection reverts back to normal mode.
Multiple selection of a seperate lines

By keeping the Ctr-key pressed you can select multiple separate entries with the mouse.
When the Ctr-key is released selection reverts back to normal mode.
A31003-H3460-M104-4-76A9, July 2012

Related Topics
Menu Bar, page 3-9
A31003-H3460-M104-4-76A9, July 2012


3.3.6 Sorting of Records

Sorting of records in a table is possible in the following pages:
● Collecting Status, page 3-25
● Output Line Status, page 3-28
● Input Format Editor - Object view, page 3-63
● Output Format Editor, page 3-78
● Filter Editor, page 3-86
● Translation Table Editor, Object view, page 3-97
● Translation Group Editor, Object view, page 3-101
● Incorrect Records - Send Back To Input, page 3-103
● Saved CDRs in Backup File, page 3-106
● Files Ready for Output Lines, page 3-107
Sorting in ascending and descending order

Clicking the header of any of the table columns will sort the records in ascending order of the
contents of this column first.
Clicking the same header again, will sort in descending order.
A31003-H3460-M104-4-76A9, July 2012

Related Topics
Menu Bar, page 3-9
A31003-H3460-M104-4-76A9, July 2012


3.3.7 Switching from List View to Object View by Double Click

Double clicking a record in a line of the table will display the details of the correspunding record
in object view.
This feature is available in the following pages:
● Collecting Status, page 3-25
● Output Line Status, page 3-28
Related Topics
Menu Bar, page 3-9
A31003-H3460-M104-4-76A9, July 2012

COL Features
3.4 COL Features

COL supports the following features:
Options, page 3-108
Logging, page 3-116
A31003-H3460-M104-4-76A9, July 2012


COL Features
Related Topics
Lists of all pre-defined elements and formats available for defining the CDR input and output
formats for COL can be found in:
Pre-defined Formats for Defining CDR Input and Output Formats
Attention:
> Default Input and Output Formats Cannot Be Modified Any More.
A31003-H3460-M104-4-76A9, July 2012

Controlling
3.5 Controlling
When Controlling is selected, the status displays Input Status: Active and Output Status:
Active and the buttons Start/Stop Input and Start/Stop Output will be displayed in the Con-
tent pane on the right hand side area of the COL Homepage.

Input Active
Output Active
Start/Stop Input
Start/Stop Output
Controlling
A31003-H3460-M104-4-76A9, July 2012


Controlling
Related Topics
COL Features
PM/COL Installation Instructions -- Getting Started
A31003-H3460-M104-4-76A9, July 2012

Collecting Status
3.6 Collecting Status

The Collecting Status feature allows the administrator to get information about the collecting
status of switches for which collecting is configured in SysM.
This dialog can be started either from the COL Homepage or from the HiPath 4000 Assistant/
Manager Start Page.
To navigate to a different object in the list, you can either select the object by clicking on the list
row, or use the arrow keys at the bottom of the screen, or select View -> Go To and choose
one of the navigation options First Object, Previous Object, Next Object or Last Object.
Description
The list of configured input lines is displayed in a table. Only switches for which the collecting
has been configured in SysM are displayed. When the dialog is displayed, table rows are sorted
by start time of the next transfer in ascending order.
Displayed data is not refreshed automatically. In order to view the latest data the
> user should restart the window or refresh the data display by pressing the Refresh
button.
A31003-H3460-M104-4-76A9, July 2012


Collecting Status
When the user starts immediate collecting with Collect now, the operation is carried out asyn-
chronously. So, the user is not informed directly about the status of collecting due to the possi-
bly long duration of the collecting.
The fields “Input format” and “Transform completed” are not applicable to Backup PC, because
a Backup PC can hold files in different formats from different systems. These files are trans-
ferred together, and the whole operation is shown in a table as a single transfer. The error code
of the multiple transfer is OK only if all files have been transferred correctly and at least one file
is not empty. Error code is No data only if all files are empty or non-existent.
Note: Even if a particular input format does not appear in the table, some input files from a
Backup-PC in that format could still be processed by COL. Transform action errors can occur
and the input files can be rejected if the user changes a format that is already being processed.
The table allows multiple selection of rows for the action Collect Now. For the Configure ac-
tion only selection of the single row is allowed.

Number Of Configured Input Lines
Collecting Active (Check box for status display, read-only)
Timecontrolled switch ON for CDR transformation / output in COL
Collecting Status, table columns
Collect Now (button)
Configure (button)
Refresh (button)
Related Topics
Collecting Status - Field Descriptions and User Actions, page 6-12
COL Features
A31003-H3460-M104-4-76A9, July 2012

Collecting Status
Collecting Status
A31003-H3460-M104-4-76A9, July 2012


Output Line Status
3.7 Output Line Status

The Output Line Status function allows the administrator to get information about the output
lines created by COL.
This dialog can be started either from the COL Homepage or from the HiPath 4000 Assistant/
Manager Start Page.
Description
This dialog shows the output status of CDR output lines. Both active and inactive lines are
shown.
If PM is enabled for some switch, PM data is collected and handled by a predefined PM output
line that is also shown in this window.
A31003-H3460-M104-4-76A9, July 2012

Output Line Status
The system does not generate any message informing you whether the CDR file
> has been successfully transformed or not. If the transformation was successful, the
file will be deleted, otherwise the file will stay in the list. Displayed data is not re-
freshed automatically. In order to view the latest (current) data, you have to click the
Refresh button or restart the window.

Number Of Output Lines
Output Active (Read-only check box)
Output Line Status, table columns
Configure (button)
Refresh (button)
Deliver Now (button)
Deliver all Lines Now (button)
Related Topics
Output Line Status - Field Descriptions and User Actions, page 6-14
COL Features
Definition of Output Lines
Attention:
A31003-H3460-M104-4-76A9, July 2012


Output Line Status
Output Line Status
A31003-H3460-M104-4-76A9, July 2012

Definition of Input Lines
3.8 Definition of Input Lines

Differences in System Management of HiPath COL versus HiPath 4000 Assistant/Manager
Collecting Agent
Definition of Input Lines Using the Collecting Agent in HiPath 4000 Assistant/Manager
Definition of Input Lines using HiPath COL
A31003-H3460-M104-4-76A9, July 2012


3.8.1 Differences in System Management of HiPath COL versus HiPath

4000 Assistant/Manager Collecting Agent
In HiPath 4000 Assistant/Manager COL the additional PM check box in the COL System Man-
agement tab sheet allows the user to activate the PM input line. The PM output line is also au-
tomatically activated if the PM check box is checked. Thus, it is not necessary to set up a sep-
arate specific output line for PM.
Related Topics
Object List (System Management – HiPath 4000 Administration)
Collecting Agent tab sheet (System Management – HiPath 4000 Administration)
● COL Administration sub tab
● Trunk Group/CDR sub tab
● Attendant Consoles sub tab
● Node No. Transform sub tab
● ISDN Access Codes sub tab
Object List view, System Management dialog in HiPath COL
COL Administration tab sheet (System Management in HiPath COL)
Communication Parameter tab sheet (System Management in HiPath COL)
ISDN Access Codes tab sheet (System Management in HiPath COL)
A31003-H3460-M104-4-76A9, July 2012

3.8.2 Definition of Input Lines Using the Collecting Agent in HiPath

4000 Assistant/Manager
The Definition of Input Lines using the Collecting Agent in HiPath 4000 Assistant/Manager
is done directly in the System Management application. System Management is started auto-
matically when you click on Definition of Input Lines on the Collecting Agent Homepage.
The functionality of the COL System Management (HiPath 4000 Administration) are de-
scribed in the following sections:
COL Administration sub tab
● Trunk Group/CDR sub tab
● Attendant Consoles sub tab
● Node No. Transform sub tab
● ISDN Access Codes sub tab
For more information regarding the System Management application please refer to the rele-
vant documentation and online help, respectively.
Attention:
Related Topics
Collecting Agent
A31003-H3460-M104-4-76A9, July 2012


3.8.2.1 Object List (System Management – HiPath 4000 Administration)

The Object List view in System Management – HiPath 4000 Administration displays a list
of network objects and their System Management related data in the content area. The col-
umns of the table can be moved forward or backward - the user can determine the ordering of
the columns.
Double-clicking on a certain line of the table starts the Object View of the selected object. Within
the object list view the user cannot modify the parameters but he/she can select a line and in-
voke the Delete button for removing the network element for the system. Multiple selections
are not possible.
For more information regarding the System Management application please refer to the rele-
vant documentation and online help, respectively.
See also
Trunk Group/CDR sub tab
Attendant Consoles sub tab
Node No. Transform sub tab
ISDN Access Codes sub tab
A31003-H3460-M104-4-76A9, July 2012

3.8.2.2 Collecting Agent tab sheet (System Management – HiPath 4000

Administration)
COL provides a separate Collecting Agent (COL) tab sheet in System Management – Hi-
Path 4000 Administration for administering COL specific data regarding a network object.
Switch-specific COL parameters (e.g. Activate/Deactivate AM and PM call recording functions
as well as scheduling data) are managed by the System Management application.
The Collecting Agent tab sheet in in System Management – HiPath 4000 Administration
comprises the following tab sheets:
A31003-H3460-M104-4-76A9, July 2012


3.8.2.3 COL Administration sub tab

The Collecting Agent -> COL Administration tab sheet is used for entering COL administra-
tion and scheduling parameters for call charge data collection.
In order to make the COL Administration sub tab available, under Active Appli-
> cation the Collecting Agent checkbox must be checked!
When pressing the Save button, a check is carried out whether or not the input format is con-
sistent with PM settings. Mandatory fields for PM are checked and in the case of an error an
appropriate message is displayed. The retry time multiplied by the number of retries must be
less than the cycle time. If cycle time is less than 1 hour, the retry time is set to 0.
Data is only collected if the call charge data collection is activated, i.e. either Collect AM Data
or Collect PM Data must be checked. The scheduling data for the selected switch is used for
both AM and PM. A different scheduling for PM collecting is not supported.
A31003-H3460-M104-4-76A9, July 2012

The PM Input Format field has been introduced in Version 2.0 of HiPath 4000 Assistant/Man-
ager. The purpose of this feature is to provide a short PM input format in order to reduce the
length of the PM-N CDR records and thereby reduce the data volume when PM is active.
When the Collect PM Data check box is marked (active), the format displayed in the Input For-
mat field will also be displayed in the PM Input Format field (default setting).
There is a separate Performance Management tab sheet in System Management – HiPath
4000 Administration for PM administration tasks. See Performance Management (PM) Tab
Sheet in System Management.
Field Descriptions
Input Format
PM Input Format
Translation Group
Collect AM Data
Generating Node Number
Collect PM Data (*Only supported for HiPath 4000 COL)
CDR Source: File/Directory
File/Directory Name
CDR from Local File System
Activate Copy CDR from RMX to Unix area
Number Of Retries
Retry Time
Start Date
Start Time
Cycle
Hours
Minutes
See Also
A31003-H3460-M104-4-76A9, July 2012



A31003-H3460-M104-4-76A9, July 2012

3.8.2.4 Trunk Group/CDR sub tab

The Collecting Agent -> Trunk Group/CDR tab sheet in System Management – HiPath
4000 Administration displays the trunk groups and their attributes. By activating the Cyclic
Check of Trunk Groups feature you can perform a cyclic check which queries the usage of all
available resources (B channels) assigned to a trunk group. To activate the Cyclic Check of
Trunk Groups feature, check the Cyclic Check of Trunk Groups Active check box and set
the Start Date, Start Time and Cycle parameters for the switch.
To enable the Cyclic Check for selected trunk groups only, activate the check box of the trunk
group in the PM/TG Check table column. This reduces communication with the switch and the
amount of data.
The Cyclic Check of Trunk Groups feature cyclically queries the status of all available re-
sources (B channels) assigned to a trunk group and stores the resulting trunk usage data in the
COL database. The Collecting Agent queries the switches, collects the trunk usage data, and
stores the data in the COL database. Performance Management (PM) then uses these data
to provide an analysis report of the trunk group resource usage.
A31003-H3460-M104-4-76A9, July 2012


The Cyclic Check of Trunk Groups feature is only supported on HiPath 4000 As-
> sistant/Manager and not in HiPath COL.
The metering is only performed for the selected switch if the following conditions are met:
● The Cyclic Check of Trunk Groups Active check box must be checked (enabled) for
the particular switch. The check box is located on the right hand side in the Collecting
Agent -> Trunk Groups/CDR tab sheet.
● The check box in the PM/TG Check table column must be checked for at least one of
the trunk groups displayed in the table, because the metering is performed only for the
trunk groups selected for metering.
Cyclically, in defined time intervals, COL queries the usage of all available resources (B chan-
nels) assigned to a trunk group (AMO DIS-BUEND), obtaining the list of trunk groups, the as-
sociated trunk cards, and the number of assigned channels. The status of each assigned chan-
nel is also determined (AMO DIS-SDSU). Finally, the Collecting Agent calculates the number
of available channels for each trunk group. The data obtained through the cyclic check is then
stored in the COL database and can be used by PM for further analysis and reporting.
The cyclic check is only performed for trunk groups with enabled check box in the PM/TG
Check table column. After performing the cyclic check you can upload the data of the metered
trunk groups back to the switch by clicking the Activate button. The PM data generated on the
switch will then contain only the selected trunk groups. This reduces the communication with
the switch and the amount of PM data.
Data should be collected only for relevant trunk groups in order to minimize commu-
> nication with the switch and to reduce the amount of PM data.
You can edit the displayed data and save them in the COL database by clicking the Save but-
ton.
Click the Download button to download the trunk group data from the system. The download
process is performed asynchronously, i. e. you need to click the Refresh button in order to get
the current data displayed in the table.
Click the Activate button to send changed trunk group data back to the system. The Activate
button is only activated after you have clicked the Save button to confirm and apply your chang-
es. The download process is also performed asynchronously.
In addition, you can use the Activate feature to upload information about metered trunk groups
back to the switch. After that, PM data generated on the switch will contain only the selected
trunk groups. In this way, the communication with the switch and the amount of PM data is re-
duced.
A31003-H3460-M104-4-76A9, July 2012

Field Descriptions
Download (button)
Activate (button)
Download Status
Last download passed on (date/time)
Activation Status
Last activation passed on (date/time)
Trunk (table column)
Name (table column)
AM (table column)
PM (table column)
PM/TG Check (table column with check box)
Cyclic Check of Trunk Groups Active (check box)
Start Date
Start Time
Cycle (radio button)
Hours
Minutes
Refresh (button)
Save (button)
Discard (button)
New (button)
Delete (button)
A31003-H3460-M104-4-76A9, July 2012


See Also
A31003-H3460-M104-4-76A9, July 2012

3.8.2.5 Attendant Consoles sub tab

The Collecting Agent/Attendant Consoles tab sheet of the System Management – HiPath
4000 Administration application under HiPath 4000 Assistant/Manager supports downloading
attendant consoles data from the system and and retrieving their virtual node numbers.
The transformation from virtual to physical node numbers is generally done based on the data
in the col_port database table.
The data of all systems configured using the Configuration Management (CM) application are
stored in col_port database tables.
Attendant consoles are not configured using CM, and therefore their data are not included in
the col_port database tables, so for attendant consoles it is not possible to perform a trans-
formation from virtual to physical node numbers.
A31003-H3460-M104-4-76A9, July 2012


Field Descriptions
Download
Refresh
Generating Node No. (table)
See Also
A31003-H3460-M104-4-76A9, July 2012

3.8.2.6 Node No. Transform sub tab

In the Node No. Transform tab sheet you may assign virtual node numbers to physical node
numbers for extensions, which are not managed by CM, in order to make them available for
Account Management.
Collecting Agent is responsible for correct transformations of the CDR data in order to hand
them over to Performance Management. The transformations are necessary in order for PM to
make calculations with switch names and physical node numbers rather than virtual node num-
bers. This is achieved by mechanisms which query the Informix database, identify the switch
name for the coordination of extension/virtual node number from col_port and then use the
switch name for finding the physical node number from col_switch. The transformed node
number will be delivered to PM.
Do not add any Attendant Console extension in this tab sheet – their virtual node
7 numbers must be downloaded in the Attendant Console tab sheet!
Also do not add any extension in this tab sheet which is handled by CM!
A31003-H3460-M104-4-76A9, July 2012


Field Descriptions
Virtual Node Number
Extension / Extension Range
Add (button )
Remove (button)
Remove All (button)
Virtual Node Number (table column)
Extension (lower value) (table column)
Extension (upper value) (table column)
See Also
A31003-H3460-M104-4-76A9, July 2012

3.8.2.7 ISDN Access Codes sub tab

In order to support mixed networks with HiPath 4000 and OpenScape Voice in a consistent way,
CDRs which are collected from HiPath 4000 switches, can be calculated to the E.164 number
format. With the ISDN Access Code sub tab there is a possibility to recalculate country code,
area code and local code (ISDN Access Codes) of a selected switch from the internal number
format. If the values from the database can be evaluated and calculated correctly, checking the
Enable E.164 Format check box displays in the table read-only data from the selected switch:
● Virtual Node Number,
● Country Code,
● Area Code,
● Local Code.
If there is a calculation problem, a warning message is displayed, denoting to check the follow-
ing criteria:
● Status of CM upload operation
● Configuration of AMO KNDEF
● Validity of Generating Node ID in input line definition screen.
In this error case recalculation will not be completed.
A31003-H3460-M104-4-76A9, July 2012


See also
A31003-H3460-M104-4-76A9, July 2012

3.8.3 Definition of Input Lines using HiPath COL

HiPath COL uses its own System Management dialog as a user interface for editing and sav-
ing the COL-specific administration and communication parameters to the database.
The data can be displayed in three different views:
● Object view,
● New Object view,
● Object List view.
In object view, the System Management dialog in HiPath COL contains the following tab
sheets:
– COL Administration tab sheet (System Management in HiPath COL)
– Communication Parameter tab sheet (System Management in HiPath COL)
– ISDN Access Codes tab sheet (System Management in HiPath COL)
formats for COL can be found in: Pre-defined Formats for Defining CDR Input and Output For-
mats
Attention:
Related Topics
Collecting Agent
A31003-H3460-M104-4-76A9, July 2012


3.8.3.1 Object List view, System Management dialog in HiPath COL

The Object List view of the COL- System Management / Input Lines dialog can not be edit-
ed. Each row contains information about one input line. The table allows only selection of one
single row.
For details regarding the COL- System Management / Input Lines dialog UI and the field de-
scriptions please refer to the link below.
Object List view, System Management dialog in HiPath COL - Field Descriptions, page
6-20

System ID
Description
System Type
System Version
A31003-H3460-M104-4-76A9, July 2012

IP Address
Save (Button)
New (Button)
Delete (Button)
Related Topics
A31003-H3460-M104-4-76A9, July 2012


3.8.3.2 COL Administration tab sheet (System Management in HiPath COL)

The COL Administration tab sheet in the System Management dialog in HiPath COL con-
tains the administration parameter for COL.
For details regarding the System Management features in HiPath COL please refer to the links
below.
COL Administration tab sheet, System Management dialog in HiPath COL - Field Des-
criptions, page 6-19
mats
Attention:

System ID
Description
A31003-H3460-M104-4-76A9, July 2012

System Type
System Version
IP Address
Communication Parameter (tab sheet)
ISDN Access Codes (tab sheet)
Input Format
Collect AM Data
Collect PM Data (*)
File/Directory (Radio buttons for CDR Source:)
File/Directory Name
Number of Retries
Retry Time (min)
Start Date
Start Time
Cycle
Hours
Minutes
Save (Button)
New (Button)
Delete (Button)
Related Topics
A31003-H3460-M104-4-76A9, July 2012


3.8.3.3 Communication Parameter tab sheet (System Management in HiPath COL)

The Communication Parameter tab sheet in the System Management dialog in HiPath COL
contains the communication parameter for COL.
The retry time multiplied by the number of retries must be less than the cycle time. If cycle time
is less than 1 hour, the retry time is set to 0.
The hook-in mechanism like in HiPath 4000 Assistant/Manager for System Management is not
supported.
For details regarding the COL- System Management / Input Lines dialog UI and the field de-
scriptions please refer to the link below.
Communication Parameter tab sheet, System Management dialog in HiPath COL - Field
Descriptions and User Actions, page 6-19
mats
Attention:
A31003-H3460-M104-4-76A9, July 2012


System ID
Description
System Type
System Version
IP Address
COL Administration (tab sheet in System Management dialog, HiPath COL only)
User Name (Group Famos)
Password (Group Famos)
TSAP SRC (Group Famos)
TSAP DST (Group Famos)
User Name (Group FTP/OpenFT)
Password (Group FTP/OpenFT)
TSAP SRC (Group FTP/OpenFT)
TSAP DST (Group FTP/OpenFT)
Save (Button)
New (Button)
Delete (Button)
Related Topics
A31003-H3460-M104-4-76A9, July 2012


3.8.3.4 ISDN Access Codes tab sheet (System Management in HiPath COL)
In order to support mixed networks with HiPath 4000 and OpenScape Voice in a consistent
way, CDRs which are collected from the switches, can be calculated to the E.164 number for-
mat.
With the ISDN Access Code tab there is a possibility to recalculate country code, area code
and local code (ISDN Access Codes) of a selected switch from the internal number format.
Checking the Enable E.164 Format check box enables the Read E.164 Fields button.
Clicking the Read E.164 Fields button, in the table (read-only) data from the selected switch
are displayed, if the values from the CDR database can be evaluated and calculated correctly:
● Country Code,
● Area Code,
● Local Code.
When the Enable E.164 Format check box is activated and the user tries to save the data in
object view without pressing the Read E.164 Fields button, a reminder message for this is dis-
played.
A31003-H3460-M104-4-76A9, July 2012


System ID
Description
System Type
System Version
IP Address
Enable E.164 Format
Read E.164 Fields
Table
Save (Button)
New (Button)
Delete (Button)
Related Topics
A31003-H3460-M104-4-76A9, July 2012


Input Format Editor
3.9 Input Format Editor

The Input Format Editor allows the administrator to define and edit input formats. An input for-
mat describes the structure of the received call charge data records (CDRs). The elements to
be used depend on the system version. For each input format an FTBL file is generated. This
file contains AMO commands which are copied to the HiPath system and executed there. After
the execution of the FTBL file the HiPath system creates CDR data that match the defined input
format.
The input format editor is started from the COL Homepage.
There are pre-defined elements and formats available for defining the CDR input and output
formats for COL. Lists of all pre-defined elements and formats for defining the CDR input
and output formats for COL can be found in:
Attention:
Input formats can be displayed, ein three different views: Object view, New Object view, and
Object List view.
For details, please refer to the respective sections:
Input Format Editor - Object view
Input Format Editor - Object List view
Input Format Editor - Set Default Value
Input Format Editor - Configure Input Element
Output Line Definition - Object List
Output Format Editor
Output Format Editor - Object List view
Configure Output Element
Filter Editor
A31003-H3460-M104-4-76A9, July 2012

3.10 Pre-defined Formats for Defining CDR Input and Output Formats
Important Information
> versions.
● Pre-defined Input and Output Formats Are Reset to Default Settings During Initialization
● Default Input and Output Formats Cannot Be Modified Any More
● CM Elements Used for Transforming Virtual to Physical Node Numbers
The following tables contain the elements and pre-defined formats that can be selected for de-
fining input and output formats.
● Elements for Defining Input and Output Formats for COL CDRs
● Pre-defined Formats for Output Format Definition (likewise for H3000 and H2000 systems)
– AM-WIN 1.0 – Format for AM-WIN 1.0
– H4000_HP_AM – Output format from HiPath 4000 for HiPath AM
– HiPath 4000 Manager/Assistant PM – Output format for HiPath 4000 Manager/As-
sistant PM V1.0
– H4000_HPAM_E164 – Output format from HiPath 4000 for HiPath AM
– H8000_AM – OpenScape Voice Output Format V1.0
– H8000_AM_V22 – OpenScape Voice Output Format V2.2 (Single System)
– OSV_AM – Open Scape Voice Output Format
– HP4M_AMPM_UV3.0 – Output format from HiPath 4000 V3 for HiPath 4000 V6
– HP4M_AMPM_UV4 – Output format from HiPath 4000 V4 for HiPath 4000 V6
– HP4M_AMPM_UV6 – Output format from HiPath 4000 V6
– HP4M_PM_UV6 – Output format from HiPath 4000 V6
● Pre-defined Formats for Input Format Definition (likewise for H3000 and H2000 systems)
– AMPM_UV1.0 - Input format for AM / PM HiPath 4000
– AllServe - Input format for HiPath AllServe 150 V1.0 (Element Manager)
A31003-H3460-M104-4-76A9, July 2012


– H5000_V30 - Input format for HiPath 5000 V3.0 (Single System)

– H8000_V22 – OpenScape Voice Input Format V2.2 (single PABX)
– AMPM_UV6 - Input format for AM/PM HiPath 4000
– PM_UV6 - Input format for HiPath 4000
● Additional CM Elements for Defining CDR Output Formats
– CM Elements Used for Generating History Output
– CM Elements Used for Transforming Virtual to Physical Node Numbers
– Loading the col_port and col_switch Tables
Related Topics
Input Format Editor - Field Descriptions and User Actions, page 6-20
COL Features
Input Format Editor
A31003-H3460-M104-4-76A9, July 2012

3.10.1 Pre-defined Input and Output Formats Are Reset to Default

Settings During Initialization
> versions.
The installation/update of CV631 and CV645-646 as well as all following higher versions re-
initializes all input/output formats and filters and resets them to the default settings. Conse-
quently, all changes made to pre-defined formats and filters are reset to the default settings.
Therefore, you need to apply the changes made to pre-defined formats and filters to new user-
defined input/output formats and filters. You can create user-defined input/output formats and
filters using the Object -> Copy -> Paste menu. Next, you need to assign the new names to
the corresponding input and output lines.
This step has become necessary in order to allow for lost pre-defined input/output formats and
filters to be re-created during an update installation. PM filters should basically not be deleted.
Please don´t forget to also copy enhanced AM filters (e.g. +CONNTYPE) to user-defined filters
and to assign them to the output line. If this is omitted and PM is activated, PM CDRs might be
written to the AM output line.
Related Topics
A31003-H3460-M104-4-76A9, July 2012


3.10.2 Default Input and Output Formats Cannot Be Modified Any More
> versions.
Starting with CV631/CV645 the pre-defined input and output formats cannot be modified any
more. The pre-defined input and output formats contain all necessary obligatory elements for
AM and PM. By removing elements, certain HiPath AM or PM features may not be executed
any more. Moreover, during an update installation the pre-defined formats are re-initialized.
If a different input or output format is to be set you need to copy and modify an existing format.
This can be done via the menu using Object -> Copy -> Paste. See Input Format Editor - Ob-
ject view.
Attention:
> If a previous pre-defined input or output format has been modified, this mod-
ified format needs to be copied as user-defined format. Please follow the re-
spective instructions.
See Also
A31003-H3460-M104-4-76A9, July 2012

3.11 Input Format Editor - Object view

The Input Format Editor - Object View is used to define and edit input format descriptions
and store them in the database.
An input format describes the structure of a received CDR. The elements to be used depend
on the system version. For each input format an FTBL file is generated. This file contains AMO
commands which are copied to the HiPath system and executed there. After execution of the
FTBL file, the HiPath system will create CDR data that will match the defined input format.
The Input Format Editor is started from the COL Homepage.
Pre-defined Formats for Defining CDR Input and Output Formats.
Attention:
Input formats can be displayed in three different views: Object view, New Object view, and
Object List view.
A31003-H3460-M104-4-76A9, July 2012


Two tables are shown on the Object view page:

● Default element table (left-hand side table)
and
● Input element table (right-hand side table).
Elements in the default element table do not appear in the input file. A default value should be
defined for each element in this table. The input element table contains selected elements and
their properties. All elements from that table appear in the input file. Element properties for both
tables cannot be edited directly in the tables but in separate windows that are started by double-
clicking on the selected row.
An additional special element containing fixed text can be added to the input as well. This ele-
ment is used to represent those parts of the input that are ignored in further processing and do
not match any standard element.
The same element cannot appear more than once among input elements in the input table. The
only exception is a fixed text element that is allowed to appear several times in input.
The End-of-Line sequence is defined separately and does not have to be listed as the last el-
ement in the input table.
System version determines the choice of elements in the default table and the input element
table. The user can define formats that have no system version assigned by choosing “none”
as the system version. Such format is referred to as a ’free format’. If this format is used, all
possible elements are allowed and both tables can be modified as desired.
When a new object is created, the default table contents are shown according to the system
version. If the system version of an existing object is changed, the table contents are automat-
ically synchronized with the selected system version, and the previous contents are lost.
Predefined input formats cannot be modified. If the user tries to save the changed predefined
input format, an appropriate warning message is displayed and the changes are not saved.
Name uniquely identifies the format. If the user changes the name and presses the Save but-
ton, a dialog box appears if the current object is assigned to some input line.
Both tables only allow the selection of a single row.
If the user wants to change an existing format that is in use, the user will be warned of possible
errors, because files in old formats could already have been generated by the system (a warn-
ing box appears).
Each format (except free format) has an associated FTBL file. This file contains AMO com-
mands that should be sent to the system. These commands are used to configure the system
so that it produces CDRs in a defined format. AMO commands depend on the system type.
Therefore each format should have a system type defined. The only exception is the free for-
mat.
A31003-H3460-M104-4-76A9, July 2012

It is not possible to print changed data that has not been saved.

Format Name
System Version
Description
Predefined
End Of Line
Default element table (on left-hand side of dialog)
Input element table
Number Of Elements
Format Length
Save (Button)
New (Button)
Delete (Button)
Related Topics
Attention:
Input Format Editor
A31003-H3460-M104-4-76A9, July 2012


3.12 Input Format Editor - Object List view

Input Format Editor - Object List is the default view that is shown when the dialog is dis-
played. The Object List view is read-only. It shows the list of all defined input formats, but dis-
plays only basic information about the formats. The Object view shows the complete set of in-
formation for the selected object and can be used to add, modify or delete the selected input
format. The New Object view is used to define new objects. This view looks similar to the Ob-
ject view.
A search function is not supported.
The Object List can not be edited. Each row contains information about one format. The table
allows only selection of a single row.

Input Format Editor, Table columns
Save (Button)
New (Button)
Delete (Button)
Related Topics
Input Format Editor - Object List - Field Descriptions, page 6-24
A31003-H3460-M104-4-76A9, July 2012

Attention:
Input Format Editor
A31003-H3460-M104-4-76A9, July 2012


3.13 Input Format Editor - Set Default Value

The Input Format Editor - Set Default Value dialog allows the administrator to set the default
value of a specific CDR element. This value is used as output value, if the element is part of
the output data and does not appear in the input data.
Start
The dialog is started from the Input Format Editor - Object View dialog by double-clicking on
the row in the default element table.
Description
This is a modal dialog with the title “COL - Set Default Value”. It is used to set the default value
of the selected input element. Other fields in the dialog are read-only.
Lists of all pre-defined elements and formats that can be selected by the user for defining the
CDR input and output formats for COL can be found in:
Attention:

Element Description
Type
Length
Alignment
Default
A31003-H3460-M104-4-76A9, July 2012

Related Topics
Input Format Editor - Set Default Value - Field Descriptions and User Actions, page 6-24
A31003-H3460-M104-4-76A9, July 2012


3.14 Input Format Editor - Configure Input Element

Configure Input Element allows the administrator to set the properties of a specific CDR input
element.
This dialog is started from the Input Format Editor dialog by double-clicking on the input ele-
ment table row.
Menu
This dialog does not have a menu.
Description
This is a modal dialog used to modify properties of the selected input element. It is opened by
double-clicking on one of the records listed in the Input element table.
Attention:

No.
Element Description
Type
Length
A31003-H3460-M104-4-76A9, July 2012

Alignment
Filler
Related Topics
Input Format Editor - Configure Input Element - Field Descriptions and User Actions,
page 6-25
A31003-H3460-M104-4-76A9, July 2012


3.15 Definition of Output Lines

To open the Output Line Definition dialog, click the Definition of Output Lines link on the
COL Homepage. The Object List view is the default view displayed after starting this feature.
Definition of Output Lines allows the administrator to define output lines for the Account Man-
agement. Each output line is defined by an output CDR file, its specific output format (see Out-
put Format Editor) and its output filter (see Filter Editor). The output CDR file is supplied cycli-
cally.
The Output Line Definition dialog is started from the COL Homepage.
Attention:
Definition of Output Lines - "New Object" view
A31003-H3460-M104-4-76A9, July 2012

Description
Output lines apply to AM data only. Output of PM data is not shown with other output lines. Out-
put of PM-specific files cannot be stopped if the input is active.
Output lines can be displayed in three different views:
● Object View,
● Object List.
Object List is the default view that is shown when the dialog is displayed. Object List is read-
only and displays only basic information about lines. The Object view, on the other hand,
shows complete information about the object and can be used to add, modify or delete the se-
lected line. The New Object view is used to define new objects and looks similar to the Object
view.
To navigate to a different object in the list, choose one of the following actions:
● select the object by clicking on the object in the list row,
or
● use the arrow keys at the bottom of the screen,
or
● select View -> Go To and choose one of the navigation options First Object, Previous
Object, Next Object or Last Object.
Object view
Changes in the output line definition require COL restart to become active. The same applies
to adding or deleting an output line.

Output Line Name
Description
Active
Output Format
Translation Group
Filter
A31003-H3460-M104-4-76A9, July 2012


File Name
Start Date/Time
Cycle
Save (Button)
New (Button)
Delete (Button)
Related Topics
Output Line Definition - Object View - Field Descriptions and User Actions, page 6-25
Output Line Definition
A31003-H3460-M104-4-76A9, July 2012

3.15.1 Parallel Output of CDR Data on Multiple Output Devices in HiPath

4000 V1.0
Parallel output of CDR data onto multiple output devices (e.g. V24 and FT file) is only supported
if the CDRFAST parameter in the AMO FEACG is deactivated.
If CDRFAST is activated, only one selection group (SELG1) and thus only one output device is
activated; the other selection groups (2 through 4) are deactivated.
Parallel output of CDR data on multiple output devices (e.g. V24 and FT file) is only
> supported if the CDRFAST parameter in the AMO FEACG is deactivated.
In case of high load on the switch, deactivating the CDRFAST parameter can cause
performance problems.
CDRFAST optimizes the CDR data output and increases the output performance on the ADP.
This is achieved by deactivating the selection groups 2 through 4, thus reducing the output to
one selection group, i.e. one output device.
As a general rule, you should only deactivate CDRFAST if you need parallel output of CDR data
on multiple output devices.
If you only need the FT file as the target format for CDR data output (i.e. only one output device)
you should always activate CDRFAST in order to increase the output performance on the
switch.
Related Topics
A31003-H3460-M104-4-76A9, July 2012


3.16 Output Line Definition - Object List

To open the Output Line Definition dialog, click the Definition of Output Lines link on the
COL Homepage.
The Output Line Definition - Object List can not be edited. Each row contains information
about one output line.
To navigate to a different object in the list, choose one of the following actions:
● select the object by clicking on the object in the list row,
or
● use the arrow keys at the bottom of the screen,
or
● select View -> Go To and choose one of the navigation options First Object, Previous
Object, Next Object or Last Object.

Output Line Definition, table columns
Save (Button)
A31003-H3460-M104-4-76A9, July 2012

New (Button)
Delete (Button)
Related Topics
Output Line Definition - Object List - Field Descriptions, page 6-27
Attention:
A31003-H3460-M104-4-76A9, July 2012


3.17 Output Format Editor

The Output Format Editor feature allows the administrator to define and modify output for-
mats. An output format describes the structure of the provided output CDRs. Used HiPath ele-
ments which are not received within the input line are set to the default value. The Output For-
mat Editor is used to edit output format descriptions and store them in the database.
An output CDR can also contain CM elements (e.g. personal data / (elements are only shown
if package “with CM-elements” is installed). At least the structure of the output CDR must be
defined in accordance with the used accounting system (e.g. AM).
The output format editor is started from the COL Homepage.
Attention:
Description
The output format editor is used to edit output format descriptions and store them in the data-
base.
Output formats can be displayed in three different views:
● Object view,
● Object List.
Object view
The user can choose standard elements and fields from the database (e.g. personal data) and
add them to the Output elements table. Properties of the elements in the Output elements ta-
ble can be modified in the Configure Output Element modal window which is opened by dou-
ble-clicking on an element (a row).
A31003-H3460-M104-4-76A9, July 2012

Element types are:

● Standard elements,
● CM elements
Note: On a HiPath Manager the CM Elements are only displayed if the COL software is
installed with the necessary user license rights. No licence is needed for a HiPath Assis-
tant.
● Fixed text.
For each CM element there is a defined criterion according to which data from the database
are selected. This criterion is fixed and cannot be defined by the user.
Fixed text elements have an additional property - Text.
If the user wants to change an existing format that is in use, a warning box is displayed which
informs the user that output files might already exist on the server in old format.
The End-of-Line sequence is defined separately and does not have to be listed as the last el-
ement in the input table.
Additional special elements containing fixed text can be added to the output as well.
The same element can appear more than once among the elements of the output table.
A31003-H3460-M104-4-76A9, July 2012


Special characters can be entered using a backslash as an escape character (\n, \r etc.).
When a new object is created, the output table is empty.
“Format name’ uniquely identifies the format. If the name has been changed before, changes
are saved to the database, a dialog box appears and the user can decide whether to save the
format as a new object or change the name of the current object. If the current object is in use,
i.e. assigned to some output line, the name cannot be changed.
Both tables only allow selection of a single line.
If the user wants to change an existing format that is in use, the user is warned of possible er-
rors because files could exist in the system in old format (a warning box appears).
It is not possible to print changed data that has not been saved.

Format Name
Description
End of Line
Element group list
Element table (on left-hand side of dialog)
Output elements table (on right-hand side of dialog)
Number Of Elements
Format Length
Save (Button)
New (Button)
Delete (Button)
A31003-H3460-M104-4-76A9, July 2012

Related Topics
Output Format Editor - Object View - Field Descriptions and User Actions, page 6-28
Attention:
A31003-H3460-M104-4-76A9, July 2012


3.18 Output Format Editor - Object List view

Object List is the default view that is shown when the dialog is displayed. The Object List view
is read-only. It shows the list of all defined input formats, but displays only basic information
about the formats. The Object view shows the complete set of information for the selected ob-
ject and can be used to add, modify or delete the selected input format. The New Object view
is used to define new objects. This view looks similar to the Object view.
Object List
The object list can not be edited. Each row contains information about one output format. The
table only allows the selection of a single row.
A31003-H3460-M104-4-76A9, July 2012


Output Format Editor, table columns
Save (Button)
New (Button)
Delete (Button)
Related Topics
Output Format Editor - Object List - Field Descriptions, page 6-31
Attention:
A31003-H3460-M104-4-76A9, July 2012


3.19 Configure Output Element

The Configure Output Element dialog allows the administrator to set the properties of a spe-
cific CDR output element.
This dialog is started from the Output Format Editor dialog, Object view, by double-clicking
on a record (row) in the Elements in Output Format table.
Attention:

No.
Element Description
Type
Length
Alignment
Filler
Text
A31003-H3460-M104-4-76A9, July 2012

Related Topics
Output Format Editor - Configure Output Element - Field Descriptions and User Actions,
page 6-31
Output Format Editor - Configure Output Element
A31003-H3460-M104-4-76A9, July 2012


Filter Editor
3.20 Filter Editor

The Filter Editor function allows the administrator to define filters for output CDRs. Each sys-
tem element and each CM element (only if package “with CM-Elements” is installed) supported
by COL can be used as a filter criterion (e.g. filtering of CDRs based on “department”, as de-
fined in personal data).
The Filter Editor is used to edit filter descriptions and store them in the database. The defined
filter is used to select the output. Only CDRs which fulfill the defined filter criteria are sent to the
output. Other CDRs are ignored.
The Filter Editor dialog is started from the COL Homepage.
Filters can be displayed in three different views:
● Object view,
● Object List.
Object view
Two tables are displayed in the object view:
● Element table on the left-hand side of the dialog,
A31003-H3460-M104-4-76A9, July 2012

Filter Editor
● Filter Clause table on the right-hand side of the dialog.
The Element table contains elements divided into several types. Element types are:
● Standard elements
● CM elements
Note: On a HiPath Manager the CM Elements are only displayed if the COL software is
installed with the necessary user license rights. No licence is needed for a HiPath Assis-
tant.
● Complex elements
The list of CM elements is the same as for the output editor.

The Filter Clause table is used to define selection clauses. Selection clause consists of several
subclauses. Each subclause has the form: <element><operator><value>. A CDR is included
in the output only if it fulfills all subclauses from the filter (AND operation).
Operators IN and NOT IN allow a list of values to be specified as parameters. The delimiter for
this list is a semicolon (“;”). It is also possible to specify a range of values, but only for numeric
values. Example: “1-9” has the same meaning as “1;2;3;4;5;6;7;8;9”.
Complex elements are special elements that consist of several standard elements. If the filter
clause contains such an element, then several values in brackets must be specified (f.e. [1-1-
21-4711]). Such elements can appear in lists, f.e. [1-1-20-4711], [1-1-21-4711],[1-1-22-4711]).
Complex elements are defined for the most frequent combination of elements. The list of com-
plex elements is predefined and cannot be modified by user. This is necessary because an ex-
tension can only be identified in a network with “DOMAIN”-”SUBDOMAIN”-”KNODENR”-”EX-
TENSION”.
A31003-H3460-M104-4-76A9, July 2012


Filter Editor

Filter Name
Description
Element group list (combo box with dropdown list)t
Filter Editor, table columns (left-hand side)
Filter Editor, table columns (right-hand side)
Number Of Elements
Save (Button)
New (Button)
Delete (Button)
Related Topics
Filter Editor - Object View - Field Descriptions and User Actions, page 6-32
Attention:
Filter Editor
A31003-H3460-M104-4-76A9, July 2012

Filter Editor - Object List
3.21 Filter Editor - Object List

Object List is the default view that is shown when the dialog is displayed. The Object List view
is read-only. It shows the list of all defined filters, but displays only basic information. The Ob-
ject view shows the complete set of information for the selected object and can be used to add,
modify or delete the selected object. The New Object view is used to define new objects. This
view looks similar to the Object view.
Object list
The object can not be edited. Each line contains information about one filter.
A31003-H3460-M104-4-76A9, July 2012


Filter Editor - Object List

Filter Editor, table columns
Save (Button)
New (Button)
Delete (Button)
Related Topics
Filter Editor - Object List - Field Descriptions, page 6-34
Attention:
Filter Editor
A31003-H3460-M104-4-76A9, July 2012

Filter Editor - Set Default Value
3.22 Filter Editor - Set Default Value

The Filter Editor - Set Default Value dialog allows the administrator to set the filter criteria for
an element.
The dialog is started from the Filter Editor dialog, Object view, by double-clicking on a row in
the Filter Clause table.

Element Name
Element Description
Operator
Value
Related Topics
Filter Editor - Set Default Value - Field Descriptions and User Actions, page 6-34
A31003-H3460-M104-4-76A9, July 2012


Attention:
A31003-H3460-M104-4-76A9, July 2012

Translation Tables
3.23 Translation Tables

In order to provide all HiPath system CDRs (H150, H5000, H300) in a consistent, "normalized"
format, the different values from the CDR elements need to be transformed (i.e. "translated")
to the same value in the COL standard elements.
This goal has been achieved in Version 2.0 of Collecting Agent (in HiPath 4000 Assistant/Man-
ager) and in HiPath COL by introducing translation tables for both input and output lines.
Translation tables consist of value pairs which define how an element value is translated on
input or output. Each translation table is defined for one specific standard element.
Translation tables can be created and edited by the administrator/user, and saved to the data-
base under a unique name.
A translation group consists of several translation tables and can be associated with more than
one input or output line. In the same way, a single table can appear in more than one group.
A31003-H3460-M104-4-76A9, July 2012


Translation Tables
The Translation Tables link on the Homepage of Collecting Agent or HiPath COL, respec-
tively, contains the following links:
● Translation Table Editor
The Translation Table Editor allows you to define, modify, save and delete translation ta-
bles. Translation tables are used to define value pairs for the transformation of input and
output values for specific elements. Translation tables can be used for both input and out-
put.
– Double-click the link to open the Translation Table Editor.
See Also
Translation Table Editor, Object List view
Translation Table Editor, Object view
● Translation Group Editor

The Translation Group Editor allows you to define, modify, save and delete translation
groups. A translation group consists of several translation tables and can be associated
with more than one input or output line.
– Double-click the link to open the Translation Group Editor.
See Also
Translation Group Editor, Object List view
Translation Group Editor, Object view
A31003-H3460-M104-4-76A9, July 2012

3.24 Translation Table Editor, Object List view

To start the Translation Table Editor, double-click the link on the Homepage of Collecting
Agent or HiPath COL, respectively.
Translation Tables are used to define value pairs for the transformation of input and output val-
ues for specific elements. Translation tables can be used for both input and output.
You can choose between three different views of this editor:
● Object,
● New Object,
● Object List (default view).
The Object List view is the default view displayed when starting the Translation Table Editor.
The Object List is write-protected (read-only) and contains only the most important data from
a translation table.
Each row in the object list contains the data of one translation table. Only one row at a time can
be selected in the list.
The Object view -- see Translation Table Editor, Object view - displays the complete set of in-
formation from a translation table. This view allows you to add, modify, delete and save trans-
lation tables to the database.
The New Object view is used to define new translation tables. This view contains the same
elements as the Object view.
The menu items in the Translation Table Editor are identical with the elements in the Input For-
mat Editor and in the Output Format Editor. For descriptions of the menu items please refer to
Menu Bar - Description of the Menu Options.
A31003-H3460-M104-4-76A9, July 2012



Translation Table Editor, table columns
Save (Button)
New (Button)
Delete (Button)
A31003-H3460-M104-4-76A9, July 2012

3.25 Translation Table Editor, Object view

To start the Translation Table Editor, double-click the link on the Homepage of Collecting
The Object view displays the complete set of information from a translation table. This view
allows you to add, modify, delete and save translation tables to the database.
● Object,
● New Object,
Predefined translation tables are write-protected (read-only) and can not be modified.
mat Editor and in the Output Format Editor.
For descriptions of the menu items please refer to Menu Bar - Description of the Menu Op-
tions.
A31003-H3460-M104-4-76A9, July 2012


The Object List view -- see Translation Table Editor, Object List view - is the default view dis-
played when starting the Translation Table Editor. The Object List is write-protected (read-
only) and contains only the most important data from a translation table.
The New Object view is used to define new translation tables. This view contains the same

Translation Table Name
Description
Element
Predefined (check box)
Add New Row (button)
Delete Row (button)
New (button)
Copy (button)
Insert (button)
Save (button)
Delete (button)
A31003-H3460-M104-4-76A9, July 2012

3.26 Translation Group Editor, Object List view

To start the Translation Group Editor, double-click the link on the Homepage of Collecting
● Object,
● New Object,
The Object List view is the default view displayed when starting the Translation Table Editor.
The Object List is write-protected (read-only) and contains only the most important data of a
translation group.
Each row in the object list contains the data of one translation group. Only one row at a time
can be selected in the list.
The Object view -- see Translation Group Editor, Object view - displays the data of one trans-
lation group. This view allows you to add, modify, delete and save translation groups to the da-
tabase.
The New Object view is used to define new translation groups. This view contains the same
A31003-H3460-M104-4-76A9, July 2012



Translation Group Editor, table columns
Save (button)
New (button)
Delete (button)
A31003-H3460-M104-4-76A9, July 2012

3.27 Translation Group Editor, Object view

To start the Translation Group Editor, double-click the link on the Homepage of Collecting
● Object,
● New Object,
The Object view displays the data of one translation group. This view allows you to add, modify,
delete and save translation groups to the database.
The New Object view is used to define new translation groups. This view contains the same
The Object List view -- see Translation Group Editor, Object List view -- is the default view dis-
played when starting the Translation Table Editor. The Object List is write-protected (read-
only) and contains only the most important data of a translation group.
Adding Translation Tables To A Translation Group

The Available Tables area (on the left hand side of the dialog) displays the list of available
translation tables.
● Select a table in the Available Tables list and add it to the Translation Group by clicking
the ">" button.
A translation table (left hand side table) that is added to a translation group (right hand side
table) is not displayed in the left hand side table any more, because a translation table can-
not be added to the same translation group twice.
Similarly, translation tables that have been removed from a translation group will be dis-
played in the Available tables list on the left hand side again.
Predefined translation tables are write-protected (read-only) and can not be modified.
Changes made to a translation group are only applied after you have clicked the Save button.
A31003-H3460-M104-4-76A9, July 2012


Group Name
Description
Translation Group Editor, table columns (left-hand side)
Translation Group Editor, table columns (right-hand side)
Number of Tables
Save (button)
New (button)
Delete (button)
A31003-H3460-M104-4-76A9, July 2012

Incorrect Records - Send Back To Input
3.28 Incorrect Records - Send Back To Input

If a call charge data records file (FTFILE) contains an incorrect record, the HiPath COL stores
the entire file in the ..\HiPathCOL\data\error\[input_line] (input line = 1, 2, 3 etc.) directory under
the filename cdr_yyyymmdd_hhnnss.err. You can edit or correct this file, respectively, using a
text editor (e.g. Notepad), and then send the file back to the input to have it processed again
using the Incorrect Records feature (Send Back To Input button) on the HiPath COL Home-
page. If the file still contains incorrect records after re-processing, it is stored in the error direc-
tory again, but this time under a different file name, containing the current date and time.
Received CDRs that do not match the input format and therefore could not be processed by
the col_transform process can be edited and returned to the input. Faulty CDR files are auto-
matically stored in a predefined folder (e.g. ../data/error/[PBX]) and are listed in the Incorrect
Records dialog. The Incorrect Records feature allows the administrator to edit and send files
with rejected CDRs back to the input line, and allows COL to process that file again.
There is no message issued by the system whether the CDR file has been success-
> fully transformed or not. If the transformation was successful, the file will be deleted
from the list of incorrect records, otherwise the file will stay in the list. Displayed data
is not refreshed automatically. In order to view the latest (current) data, you have to
click the Refresh button or restart the window.
The Incorrect Records dialog is started from the COL Homepage.
A31003-H3460-M104-4-76A9, July 2012


Description
Upon starting the Incorrect Records window, a list of all CDR error files is displayed. CDR er-
ror files generated by COL are stored in a predefined folder (e.g. ../data/error/[PBX]) and are
listed in the Incorrect Records dialog, as defined in Definition of Output Lines. If there are oth-
er files in the mentioned directories, they are also displayed in this list. So the user can generate
a new file, store it in an error directory and use this form to send it back to the input processing.
If the user chooses to send the selected file back, the file is sent back and added to the trans-
form queue. After that, the CDR error file is deleted and the added file is processed asynchro-
nously by COL.

Incorrect Records dialog, table columns
Send Back To Input (button)
Refresh (button)
Delete (button)
View CDRs
A31003-H3460-M104-4-76A9, July 2012

Related Topics
Incorrect Records - Send Back To Input - Field Descriptions and User Actions, page 6-44
CDR Viewer
Attention:
Incorrect Records
A31003-H3460-M104-4-76A9, July 2012


Saved CDRs in Backup File
3.29 Saved CDRs in Backup File

In this page all saved CDR files in the backup directory are displayed.
The backup feature for CDR files can be activated, deactivated and customized in the COL Op-
tions (see Section 3.31.2, “Options - Settings tab sheet”).
The table is sortable by clicking on the column headers. Also multiple selection is supported for
the Send Back To Input and Delete buttons.

Saved CDRs in Backup File dialog, table columns
Send Back To Input
Refresh
Delete
View CDR Files
Related Topics
CDR Viewer
Step-By-Step Instruction
A31003-H3460-M104-4-76A9, July 2012

Files Ready for Output Lines
3.30 Files Ready for Output Lines

This page is opened after double clicking Files Ready for Output Lines on the COL Home-
page. It displays a list of available CDR files for output, which are stored in the manager’s de-
livery directories.
The columns can be sorted by clicking on the column header and several lines in the table can
be selected (also multiple selection is possible). A multiple selection applies only for the func-
tion of the Delete button, but not for the View CDRs button.

Files Ready for Output Lines dialog, table columns
Refresh
Delete
View CDRs
Related Topics
CDR Viewer
Step-By-Step Instruction
A31003-H3460-M104-4-76A9, July 2012


Options
3.31 Options
The Options feature allows the administrator to view or to set COL options.
Only authorised users having “rsca” access rights are allowed to change and save
> values in the Options dialog.
The Options dialog is started from the COL Homepage; it contains the following three tab
sheets:
Options - COL Paths tab sheet
Options - Settings tab sheet
Options - Process Controlling tab sheet
A31003-H3460-M104-4-76A9, July 2012

Options
3.31.1 Options - COL Paths tab sheet

This tab sheet is used to set the paths for the folders where Collecting Agent administers and
stores the different types of information.
After pressing the Save button, the parameters are stored in the database. However, a restart
of the whole system (COL) is needed for the parameter changes to take effect.
Only authorised users having “rsca” access rights are allowed to change and save values.
The COL Paths tab sheet allows you to set the paths for folders and types of information.
A31003-H3460-M104-4-76A9, July 2012


Options

Input Path
Transform Path
Output Path (internal)
AM Deliver Path
PM Deliver Path
Path of Incorrect Records
FTBL Path
Trunk Group Metering Path
Save (button)
Related Topics
Options
A31003-H3460-M104-4-76A9, July 2012

Options
3.31.2 Options - Settings tab sheet

This tab sheet allows you to set the system parameters used by Collecting Agent for data col-
lection, processing, administration and archiving, for example the number of receive threads,
transform threads and line threads, the size of the required free (disk) space, the retention pe-
riod for CM history data, for logging entries, and for the cyclic check of trunk group data.
Only authorised users having “rsca” access rights are allowed to change and save values.
A31003-H3460-M104-4-76A9, July 2012


Options
The Settings tab sheet allows you to set the following parameters or values.

Required Free Space
Retention Period for CM History Data ... Day(s)
Activate fast mode for transformation of virtual to physical node number only for the PM
output line (check box)
Activate/Deactivate Automatic Delecte of Logging Entries in COL (check box)
Retention Period for Logging Entries ... Day(s)
Retention Period for Trunk Group Data from the Cyclic Check of the B Channels ... Day(s)
Save Input Files (CDRs)
Retention Period for AC Configuration Data ... Day(s)
Send email notification if free space/collection thresholds exceeds
Select email recipients
Activate/Deactivate automatic Cleanup
Retention Period for the Back Up CDR files ... Day(s)
Activate/Deactivate Define Backup and check of BackUp Directory
Retention Period for "File Transfer" (receive) Process Monitor
Retrieve CDRs alive time
Save (button)
Related Topics
Options - Field Descriptions and User Actions, page 6-45
A31003-H3460-M104-4-76A9, July 2012

Options
Attention:
Related Topics
Options
A31003-H3460-M104-4-76A9, July 2012


Options
3.31.3 Options - Process Controlling tab sheet
The Process Controlling tab sheet allows you to set the following parameters or values.
A31003-H3460-M104-4-76A9, July 2012

Options

Number of Receive (CDR collecting) Processes
Number of Transform (CDR standardisation) Processes
Number of Line (CDR output) Processes
Number of Metering Processes
Number of TG-Check (Cyclic check of Trunk Groups) Processes
Schedule Incorporation of CDR Processing Active
Start Time
Stop Time
Save (button)
Related Topics
Options
A31003-H3460-M104-4-76A9, July 2012


Logging
3.32 Logging
Click on Logging on the Homepage of Collecting Agent or HiPath COL to display and/or de-
lete different types of message logs listed in the upper right pane.

Log Type:
System ID
From: (Date: / Time:)
To: (Date: / Time:)
View (button)
Delete (button)
A31003-H3460-M104-4-76A9, July 2012

Logging
Related Topics
COL Logging Events
COL Logging Events Report
Logging Report - Field Descriptions
Logging
A31003-H3460-M104-4-76A9, July 2012


COL Logging Events
3.33 COL Logging Events

The following example screen for Call Logging Events is based on the Receive Log selection.
For each log message the following information is displayed:
Some of the columns may be left blank without values. The completeness of the presented data
is limited by the information which is recorded during the logging of each event. This is depen-
dent from the settings in each COL section, whether loggings are to be recorded or not.
The columns of the table grid are sortable by clickin in the column headers.
A31003-H3460-M104-4-76A9, July 2012

COL Logging Events

Columns in the Log Table:
● Logging Type
● Logging Period
● Date (column)
● Category (column)
● Error (column)
● System ID (column)
● Short message (column)
● Long message (column)
● Severity (column)
Print/Export (Button)
Related Topics
Logging
COL Logging Events Report
Exporting Log Reports
Logging
A31003-H3460-M104-4-76A9, July 2012


CDR Viewer
3.34 CDR Viewer

The CDR Viewer dialog opens by clicking the View CDRs button from pages Incorrect
Records, Saved CDR files in Backup or Files Ready for Output Lines.
This dialog has two different formats:
● If the selected Input/Output format is unknown, unassigned or the length of the CDR
doesn't fit to the selected format, the dialog is displayed in the ’Undefined Format’ layout.
The column header in this case is a scale which represents the length of the CDR.
● In all other cases, with defined and valid record formats, the dialog displayes a scrollable
table with rows of CDRs, showing the content of a single CDRs column by column.

Define Format
Display all CDRs
Columns in the CDR table
Print
Number of Records in the CDR File
A31003-H3460-M104-4-76A9, July 2012

CDR Viewer
Related Topics
A31003-H3460-M104-4-76A9, July 2012


3.35 Exporting Log Reports

After clicking the Export/Print button in the Call Logging Events page the Run Report Dialog
window is displayed. In this dialog the following options for the export of the log file can be
configured:
● Output Format
● Email Recipients
● Export File Locations
Related Topics
Run Report Dialog - Output Tab, page 3-123
Run Report Dialog - E-mail Tab, page 3-124
Run Report Dialog - Export Tab, page 3-125
Run Report - Status Window, page 3-126
COL Logging Events Report, page 3-127
A31003-H3460-M104-4-76A9, July 2012

3.35.1 Run Report Dialog - Output Tab

The Output tab of the Run Report dialog allows you to select the template and different output
media and output file formats for the log file.
Multiple selection for display and/or export options is possible in general.
Figure 3-1 Run Report Dialog - Output Tab

Report Object:
Choose template
Display Report on Screen
Send File to Printer
Send Report as Email
Export Report to the follwoing formats
Run
Related Topics
A31003-H3460-M104-4-76A9, July 2012


3.35.2 Run Report Dialog - E-mail Tab

The E-mail tab of the Run Report dialog allows you to send the report to selectable e-mail
recipients.
Figure 3-2 Run Report Dialog - Email Tab

To
CCs
Subject
Body
Run
Related Topics
A31003-H3460-M104-4-76A9, July 2012

3.35.3 Run Report Dialog - Export Tab

The Export tab of the Run Report dialog allows you to define file locations for each output
format for saving the report.
Figure 3-3 Run Report Dialog - Exports Tab

Exports (HTML , PDF , CSV , XML)
Automatic overwrite of existing export files
Run
Related Topics
A31003-H3460-M104-4-76A9, July 2012


3.35.4 Run Report - Status Window

After clicking the Run button in the Run Report Dialog the generation of the report according
to the selected settings is started and the status window is displayed, showing information
about the current progress of the report export/generation.
Figure 3-4 Run Report - Status Window

Export Format
Status
Refresh
Abort
Save As...
Related Topics
A31003-H3460-M104-4-76A9, July 2012

3.35.5 COL Logging Events Report

The following example for a Call Logging Events Report is based on the Receive Log selection.
Depending on the selection after clicking the Print/Export button in the COL Loggin Events
dialog, the report will be displayed in HTML, XML or PDF export format
Related Topics
Logging
COL Logging Events
Logging
A31003-H3460-M104-4-76A9, July 2012


A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Fields.fm
Nur für den internen Gebrauch Field and Controls Descriptions
4 Field and Controls Descriptions

The following links contain the fields and controls descriptions of the Collecting Agent / HiPath
COL, sorted by topics.
Collecting Agent/HiPath COL Homepage, field descriptions, page 4-3
Fields displayed when Controlling link is active, page 4-4
Collecting Status dialog, field descriptions, page 4-6
Output Line Status dialog, field descriptions, page 4-9
HiPath COL – System Management dialog, field descriptions, page 4-12
Communication Parameter tab sheet - System Management dialog (HiPath COL only), page
4-20
System Management dialog, Object List view (HiPath COL only), field descriptions, page 4-23
Input Format Editor - Object view, field descriptions, page 4-25
Input Format Editor - Object List view, field descriptions, page 4-30
Input Format Editor - Set Default Value, field descriptions, page 4-32
Input Format Editor - Configure Input Element, field descriptions, page 4-33
Output Line Definition - Object view, field descriptions, page 4-35
Output Line Definition - Object List view, field descriptions, page 4-38
Output Format Editor - Object view, field descriptions, page 4-40
Output Format Editor - Object List view, field descriptions, page 4-44
Output Format Editor - Configure Output Element, field descriptions, page 4-46
Filter Editor - Object view, field descriptions, page 4-48
Filter Editor - Object List view, field descriptions, page 4-51
Filter Editor - Set Default Value, field descriptions, page 4-53
Translation Table Editor - Object view, field descriptions, page 4-54
Translation Table Editor - Object List view, field descriptions, page 4-57
Translation Group Editor - Object view, field descriptions, page 4-59
Translation Group Editor - Object List view, field descriptions, page 4-62
Incorrect Records dialog, field descriptions, page 4-64
A31003-H3460-M104-4-76A9, July 2012

Field and Controls Descriptions Nur für den internen Gebrauch

COL Paths tab sheet, Options dialog, field descriptions, page 4-68
Settings tab sheet, Options dialog, field descriptions, page 4-70
Process Controlling tab sheet, Options dialog, field descriptions, page 4-75
Options dialog, Save button description, page 4-78
Logging dialog (log file), page 4-79
Collecting Agent tab sheet in System Management, page 4-86
Trunk Group/CDR sub tab, page 4-93
Node No. Transform sub tab, page 4-102
A31003-H3460-M104-4-76A9, July 2012

Collecting Agent/HiPath COL Homepage, field descriptions
4.1 Collecting Agent/HiPath COL Homepage, field descriptions

Application tree
Application tree
The application tree is similar to a menu folder structure, displaying all COL features in the form
of links the user can activate from the COL Homepage. The Application Tree is displayed on
the left-hand side of the COL Homepage in the Navigation Pane.
Read-only.

A short description of the currently selected feature/link from the application tree is displayed
in the Content Pane on the right-hand side of the Homepage. If Controlling is selected in the
tree, the description will not be visible, and the Content pane will show the status displays Input
Status: Active and Output Status: Active and the buttons Start/Stop Input and Start/Stop
Output.
Read-only.
A31003-H3460-M104-4-76A9, July 2012


Fields displayed when Controlling link is active
4.2 Fields displayed when Controlling link is active

Input Active
Output Active
Start/Stop Input
Start/Stop Output
Input Active
Shows status of collecting files from system (applies to both AM and PM files). Visible only if
Controlling is selected in tree.
Use the Start/Stop Input button to activate or deactivate the input of CDR data, respectively.
The status display changes accordingly, showing the current status of the system, i. e. either
Input: Active or Input: Not active.
Active/Not active.
Read-only.
Output Active
Shows status of producing output files (applies only to CDR files). Visible only if Controlling is
selected in tree.
Use the Start/Stop Output button to activate or deactivate the output of CDR data, respective-
ly. The status display changes accordingly, showing the current status of the system, i. e. either
Input: Active or Input: Not active.
Active/Not active.
Read-only.
Start/Stop Input
Toggle button to start/stop collecting files from system (applies to both AM and PM files). Visible
only if Controlling is selected in tree.
Use this button to activate or deactivate the input of CDR data, respectively. The status display
changes accordingly, showing the current status of the system, i. e. either Input: Active or In-
put: Not active.
Warning Box.
A31003-H3460-M104-4-76A9, July 2012

Fields displayed when Controlling link is active
Start/Stop Output
Toggle button to start/stop producing output files (applies only to CDR files). Visible only if Con-
tolling is selected in tree.
Use this button to activate or deactivate the output of CDR data, respectively. The status dis-
play changes accordingly, showing the current status of the system, i. e. either Input: Active
or Input: Not active.
Warning Box.
A31003-H3460-M104-4-76A9, July 2012


Collecting Status dialog, field descriptions
4.3 Collecting Status dialog, field descriptions

Configure (button)
Refresh (button)

Number of switches for which the collecting is configured in SysM
Integer
Read-only

Check-box shows whether collecting has been activated for all switches
Checked/unchecked
Read-only

The status ’Timecontrolled switch ON for CDR transformation / output in COL’ is displayed only
if you have checked the Schedule Incorporation of CDR Processing Active check box in the
Options - Process Controlling tab sheet, otherwise nothing is displayed. Next to this label is dis-
played the Start and Stop time, which is also defined in the Options - Process Controlling tab
sheet.

The table displays the following columns:
System ID
System ID
String
Read-only
A31003-H3460-M104-4-76A9, July 2012

System Type
System type
String
Read-only
Input Format
Input format
String
Read-only.
Active Collecting
Shows whether collecting has been activated for the switch.
AM, PM, AM/PM, empty
Read-only
Next Transfer
Start time of the next transfer
String in format “hh:mm dd.mm.yyyy”
Read-only. Empty if collecting for that switch is not active.
Last Transfer
Start time of the last transfer
String in format “hh:mm dd.mm.yyyy”
Read-only
Transfer Status
Status of the last transfer
Values:
RMX:OK, RMX:Waiting, RMX:Running, RMX:Retrying, RMX:Error, RMX:N/A, RMX:No Data,
RMX:No Space
Next to each value an extra field will be displayed only if you have checked the Activate Copy
CDR from RMX to UNIX area check Box in SysM -> Collecting Agent (Tab-sheet) -> COL Ad-
ministration (Tab-sheet); the possible values of this extra field are the following:
A31003-H3460-M104-4-76A9, July 2012


ADP:OK, ADP:Waiting, ADP:Running, ADP:Retrying, ADP:Error, ADP:No Data, ADP:No

Space
Read-only. “No Data” means that the input file was empty or non-existing.
Transform Status
Shows whether transfer files have been transferred into standard format.
Values:
Yes, No, N/A, Waiting, Error, Started, Line Started, Line Error, Processing, Stopped
Read-only. N/A for Backup PC.
Possible values will be either Processing or Stopped when the Schedule Incorporation of
CDR Processing Active checkbox is checked. Otherwise, the possible values for these col-
umns will not be affected.
Line Status
Values:
Waiting, Error, N/A, Started, Line Started, Line Error, Processing, Stopped
Possible values will be either Processing or Stopped when the Schedule Incorporation of
CDR Processing Active checkbox is checked. Otherwise, the possible values for these col-
umns will not be affected.

Immediately starts the recording of CDRs.
The operation is carried out in asynchronous mode. Processing of several lines (data records)
at a time is supported
Configure (button)
Configure input line. In the Collecting Agent under HiPath 4000 Assistant/Manager, clicking
this button will launch the System Management application. In HiPath COL, clicking this but-
ton will launch the COL-specific tab sheet System Management.
Only one line at a time can be selected and configured.
Refresh (button)
Refreshes the contents of the configured input lines and displays the current contents.
A31003-H3460-M104-4-76A9, July 2012

Output Line Status dialog, field descriptions
4.4 Output Line Status dialog, field descriptions

Configure (button)
Refresh (button)
The table allows selection of a single row only.

Number of defined output lines
Integer
Read-only

If the check-box is unchecked, output has been deactivated for all lines
Checked/unchecked.
Read-only

Name (table column)

Output line name
String
Read-only
Active (read-only check box)

Is output line activated?
Yes/No
Read-only
A31003-H3460-M104-4-76A9, July 2012


Output Format
Output format
String
Read-only
Filter
Filter
String
Read-only. N/A for Backup PC
Last Output
Start time of the last output
hh:mm dd.mm.yyyy; N/A for PM output line
Read-only
Status
Status of the last output
OK/Error/No data
Read-only. “No data” means that the output file was empty or non-existing.
Next Output
Start time of the next output
hh:mm dd.mm.yyyy; N/A for PM output
Read-only
The table allows selection of a single row only.
Configure (button)
Launches the Output Line Definition dialog used for configuring and displaying configured
output lines.
Only one line at a time can be selected and configured. See also Definition of Output Lines.
A31003-H3460-M104-4-76A9, July 2012

Refresh (button)
Refreshes the contents of the dialog, showing the current contents of the configured output
lines.
Deliver Now (button)

The files in the selected output lines will be delivered immediately to the delivery directory.
Normally /var/col/data/output/<output_id> on server side for each output line:
/var/col/data/output/1
/var/col/data/output/3 ....
In the table the Last Output and Status fields are updated.
All files gathered within these directories will be moved to /var/col/data/deliver and
appended in one file for each output line under the name specified for each output line. The
HiPath Application Management (AM) is able to retrieve the data.
Deliver all Lines Now (button)

Files of all output lines will be delivered to the delivery directory.
Normally /var/col/data/output/<output_id> on server side for each output line:
/var/col/data/output/3 ....
In the table the Last Output and Status fields are updated.
All files gathered within these directories will be moved to /var/col/data/deliver and
appended in one file for each output line under the name specified for each output line. The
HiPath Application Management (AM) is able to retrieve the data.
A31003-H3460-M104-4-76A9, July 2012


HiPath COL – System Management dialog, field descriptions
4.5 HiPath COL – System Management dialog, field descriptions

System ID
Description
System Type
System Version
IP Address
Save (Button)
New (Button)
Delete (Button)
System ID
System name / retrieved system.
String (char 4).
Description
Description of system-ID.
String (char 40).
System Type
Combo box with the list of all supported systems
H300
HDMS
H150-LAN
H150-BAC
H150-ALL
H150-COM
H5000
H300 (OpenFT)
HDMS (FTP)
H150-Lan (passiv/TFTP)
H150-BackupPC (FTP)
A31003-H3460-M104-4-76A9, July 2012

H150-AllServe (FTP)
H150-ComboX (FTP)
H5000 (FTP)
System Version
The software release is defined by its version that corresponds to the System Release which
is determined by the SWU APS (S-APS, ABFRAGEN-APS). The 8th and 9th position (after “B”)
of the Part Number indicates the System Release number, also called "variant".
Each Part Number is based on the following rule:
Part Number: P30252-Bxx00-S001-pp
xx ... System Release (also called Variant, uniquely corresponds to a version)
S001 ... Revision Level, 4 digits
pp ... Patch information, 2 digits “00”, “01”, ...
The version number of a system is made up the following 3 adjacent fields (described below):
Version, Part Number, Patch Number.
● Version (1st field)
The Product Release Version , e.g. UV 1.0 for HiPath 4000.
Values: See table below.
● Part Number (German: "Sachnummer") (2nd field)
The part number ("Long Number") of the system can be retrieved with the AMO S-APS,
ABFR-APS.
In the part number P30252-Bxx00-S001-00 the letters xx are standing for the System Re-
lease number, which is mapped to a certain Version number.
Values: The table below shows the mapping of the Version to the System Release number
wich is part of the Part Number (German "Sachnummer").
● Patch Number (3rd field)
A 2-digit number indicating the number of the software patch.
Mapping of Version to System Release and Network Object Type
Version (1st field) System Release in Part Number, Network Object Type
2nd field
(xx in P30252-Bxx00-S001-00)
UV 1.0 (HiPath 4000) 43 Hipath 4000
A31003-H3460-M104-4-76A9, July 2012


Version (1st field) System Release in Part Number, Network Object Type
2nd field
(xx in P30252-Bxx00-S001-00)
UV 4 (HiPath 4000) 46 HiPath 4000
UV 5 (HiPath 4000) 47 HiPath 4000
UV 6 (HiPath 4000) 48 HiPath 4000/
HiPath 4000
6.1 PM
6.2 PM
6.3 PM
6.3.3 PM
6.4.3 PM
V 1.0 NM
IP Address
IP Adress of the retrieved system.
String (char 32).
(Mask ___.___.___.___ ?)
IP Address is also needed from H150-Lan because of the mapping from H150-BackupPC.
Tab sheet for setting up and administering system data in HiPath COL.
HiPath COL has its own System Management dialog for setting up and administering system
data.
On the other hand, the Collecting Agent in HiPath 4000 Assistant/Manager directly starts
the System Management application when you click on Definition of Input Lines.

In this tab sheet COL communication parameter can be set.

Tab sheet for recalculating internal CDR number format to E.164 format.
A31003-H3460-M104-4-76A9, July 2012

Save (Button)
Saves changes to the database.
An error message will be issued for wrong values.
New (Button)
Creates a new object and switches to the New Object view.
None
Delete (Button)
Deletes the selected object(s) (only available in Object List view)
A warning box will be displayed before deletion is carried out.
A31003-H3460-M104-4-76A9, July 2012


4.5.1 COL Administration tab sheet - System Management dialog

(HiPath COL only)
The COL Administration tab sheet in the System Management dialog is used to administer
and maintain COL administration and scheduling parameters.
Input Format
Collect AM Data
Collect PM Data (*)
File/Directory Name
Number of Retries
Retry Time (min)
Start Date
Start Time
Cycle
Hours
Minutes
Save (Button)
New (Button)
Delete (Button)
Input Format
Combo box with the list of all input formats.
List of all input formats.
Collect AM Data
Check-box to activate AM collecting.
Checked/not checked.

3 numeric entry fields for the node number
A31003-H3460-M104-4-76A9, July 2012

Values: 1 to 9
Field lengths: 3,3,2; Mask: 111-111-11
Collect PM Data (*)

(*) This feature is only supported in the Collecting Agent under HiPath 4000 Assistant/Man-
ager.
Check box for activating PM collecting.
Checked/Not checked.

Radio buttons to choose input from file or directory.
File or Directory – depending on System Type.
H300 = File.
HDMS = File.
H150-Lan = Directory.
H150-BackupPC = Directory.
H150-AllServe = File.
H150-ComboX = File.
H5000 = Directory.
File/Directory Name
Name of the file/directory where data is collected from.
String
Default:
H300 = FTFILE
HDMS = GCDATA
H150-Lan = Input-Dir
H150-BackupPC = ../<FTP-Collect-Dir>
H150-AllServe = ../GCALLSERV
H150-ComboX = FTFILE
A31003-H3460-M104-4-76A9, July 2012


H5000 = <inst_path>/H5000/cfg/cdr/CDRReport_<date>_<time>.txt or
CDRReport_<date>_<time>_seq_number>
<date> = YYYYMMDD
<time> = HHMMSS
<seq_number> = {1,2,...}
Number of Retries
Number of retries for data transfer
Integer
Default: 3.
Retry Time (min)

Retry time in minutes for data transfer
Integer
Default: 15 min.
Start Date
Start date for collecting
Date
Default: today
Start Time
Start time for collecting
Time in format “hh:mm”
Default: current time
Cycle
Radio-buttons to choose hours or minutes
Hours or Minutes
Default: hours
Hours
Combo-box with hours
A31003-H3460-M104-4-76A9, July 2012
1,2,3,4,6,8,12,24
Enabled only if Cycle = Hours, not mandatory. Default: 1
Minutes
Combo-box with minutes
1,2,3,4,5,6,10,12,15,30
Enabled only if Cycle = Minutes, not mandatory. Default: 15.
Save (Button)
Saves changes to the database.
New (Button)
None
Delete (Button)
A31003-H3460-M104-4-76A9, July 2012


4.5.2 Communication Parameter tab sheet - System Management

dialog (HiPath COL only)
Save (Button)
New (Button)
Delete (Button)

User name for famos session
String (char 8)
Only for H300

Password for User name (famos session)
String (char 8)
Only for H300

Transport name for source
String (char 8)
Only for H300

Transport name for destination
A31003-H3460-M104-4-76A9, July 2012

String (char 8)
Only for H300

User name for FTP/OpenFT session
String (char 8)

Password for User name (FTP/OpenFT session)
String (char 8)

Transport name for source
String (char 8)
Only for H300

Transport name for destination
String (char 8)
Only for H300
Save (Button)
Saves changes to the database
New (Button)
None
Delete (Button)
A31003-H3460-M104-4-76A9, July 2012


4.5.3 ISDN Access Codes tab sheet - System Management dialog

Enable E.164 Format
Read E.164 Fields
Table
Save (Button)
New (Button)
Delete (Button)
Enable E.164 Format

Checking the Enable E.164 Format check box enables the Read E.164 Fields button.
Read E.164 Fields

Clicking the Read E.164 Fields button, in the table (read-only) data from the selected switch
are displayed, if the values from the CDR database can be evaluated and calculated correctly.
Table
Shows the number correlation of the selected switch regarding:
● Country Code,
● Area Code,
● Local Code.
Save (Button)
When the Enable E.164 Format check box is activated and the user tries to save the data in
object view without pressing the Read E.164 Fields button, a reminder message for this is dis-
played.
New (Button)
Delete (Button)
Deletes the selected object(s) (only available in Object List view).
A31003-H3460-M104-4-76A9, July 2012

4.5.4 System Management dialog, Object List view (HiPath COL only),
field descriptions
System ID
Description
System Type
System Version
IP Address
Save (Button)
New (Button)
Delete (Button)
System ID
System name / retrieved system
String (char 4)
Read-only
Description
Description of system-ID
String (char 32)
Read-only
System Type
Type of the systems which are supported
H300
HDMS
H150-LAN
H150-BAC
H150-ALL
H150-COM
H5000
Read-only
System Version
Version of the system
H300 = UV1.0
HDMS = V3.6
A31003-H3460-M104-4-76A9, July 2012


H150-LAN = V1.0. V1.2

H150-BackupPC = V1.x
H150-AllServe = V1.0
H150-ComboX = V1.0, V1.2
H5000 = V3.0
Read-only
IP Address
IP-Adress of the retrieved system
String
Read-only
Save (Button)
New (Button)
None
Delete (Button)
A31003-H3460-M104-4-76A9, July 2012

Input Format Editor - Object view, field descriptions
4.6 Input Format Editor - Object view, field descriptions

Format Name
System Version
Description
Predefined
End Of Line
Input element table
Number Of Elements
Format Length
Save (Button)
New (Button)
Delete (Button)
Format Name
Name of the selected format
String (max. length 30)
Required, unique
System Version
Combo-box with the system version to which the format applies
Required. When changed, a warning box is displayed. If the user accepts the action, default
values for default and input table are displayed. The value “none” defines “free format”.
Description
Short format description
Optional
Predefined
Check-box is checked for predefined elements
A31003-H3460-M104-4-76A9, July 2012


Checked, unchecked
Read-only
End Of Line
Combo-box to choose End of Line sequence
List of values: LF, CR, CR/LF, none)

Combo-box to select or edit a default element for CDR input format
Values: List of default input formats, stored in the form of database records. The input format
describes the structure of a received CDR. The elements to be used depend on the system ver-
sion. For each input format an FTBL file is generated. This file contains AMO commands which
are copied to the HiPath system and executed there. After execution of the FTBL file, the Hi-
Path system will create CDR data that will match the defined input format.
Two tables are shown on the Input Editor - Object View page:
and
Elements in the Default element table do not appear in the input file. A default value should be
defined for each element in this table. Element properties for both tables cannot be edited di-
rectly in the tables but in separate windows that are started by double-clicking on the selected
row.
Name
Element name, e.g. ACCTCODE for "Account code used during a call"
Value: String; Length: 12 characters
Read-only
A31003-H3460-M104-4-76A9, July 2012

Element Description
Element description, e.g. "Account code used during a call" for ACCTCODE
String, Numeric
Read-only
Allowed
Value to be assigned to the element if it is a permitted field.
check box - Permitted fields are checked, not permitted fields are unchecked.
Read-only
Input element table

Combo-box containing the selected input format elements for configuring the structure of re-
ceived CDR data.
Values: List of selected input formats stored in the form of database records. The input format
describes the structure of a received CDR. The elements to be used depend on the system ver-
sion. For each input format an FTBL file is generated. This file contains AMO commands which
are copied to the HiPath system and executed there. After execution of the FTBL file, the Hi-
Path system will create CDR data that will match the defined input format.
Two tables are shown on the Input Editor - Object View page:
and
Only the elements from the Input element table will appear in the input file. A default value
should be defined for each element in this table. Element properties for both tables cannot be
edited directly in the tables but in separate windows that are started by double-clicking on the
selected row.
A31003-H3460-M104-4-76A9, July 2012


# (Number)
Position number of input element
Integer
Read-only; Automatically generated by program
Name
Element name, e.g. ACCTCODE for "Account code used during a call"
Value: String; Length: 12 characters
Read-only
Element Description
Element description, e.g. "Account code used during a call" for ACCTCODE
String, Numeric
Read-only
Length
Length in bytes of the element.
Integer
Read-only
Alignment
Alignment
Left, Right
Read-only
Number Of Elements
Number of elements in the Input element table
Integer
Format Length
Total length in bytes of an input row
A31003-H3460-M104-4-76A9, July 2012

Integer
Save (Button)
New (Button)
None
Delete (Button)
A31003-H3460-M104-4-76A9, July 2012


Input Format Editor - Object List view, field descriptions
4.7 Input Format Editor - Object List view, field descriptions

Save (Button)
New (Button)
Delete (Button)
The object list can not be edited. Each row contains information about one format. The table

Format Name
Read-only, unique.
System Version
System version to which the format applies
Read-only
Description
Read-only
Element Count
Number of elements in the element table.
Integer
Read-only
Format Length
Total length in bytes of an input row.
A31003-H3460-M104-4-76A9, July 2012

Input Format Editor - Object List view, field descriptions
Integer
Read-only
Save (Button)
New (Button)
None
Delete (Button)
A31003-H3460-M104-4-76A9, July 2012


Input Format Editor - Set Default Value, field descriptions
4.8 Input Format Editor - Set Default Value, field descriptions

Element Description
Type
Length
Alignment
Default
This is a modal dialog with the title COL - Set Default Value. It is used to set the default value
Element Description
Element name
String
Read-only
Type
Combo-box with the type of the element.
String, Numeric
Read-only
Length
Integer
Read-only
Alignment
Alignment
Left, Right
Read-only
Default
Value to be assigned to the element if it does not appear in input.
String
Required.
A31003-H3460-M104-4-76A9, July 2012

Input Format Editor - Configure Input Element, field descriptions
4.9 Input Format Editor - Configure Input Element, field descriptions

No.
Element Description
Type
Length
Alignment
Filler
This is a modal dialog with the title “COL - Configure Input Element”. It is used to modify prop-
erties of the selected input element.
No.
Row position
Integer
Read-only
Element Description
Element name
String
Read-only
Type
String, Numeric
Required
Length
Integer
Required only if Type is String.
Alignment
Combo-box to define alignment
Left, Right
A31003-H3460-M104-4-76A9, July 2012


Input Format Editor - Configure Input Element, field descriptions
Filler
Character used for padding (filling empty text spaces)
Char
Default: space
A31003-H3460-M104-4-76A9, July 2012

Output Line Definition - Object view, field descriptions
4.10 Output Line Definition - Object view, field descriptions

Output Line Name
Description
Active
File Name
Output Format
Translation Group
Filter
Start Date/Time
Cycle
Save (Button)
New (Button)
Delete (Button)
Output Line Name

Output line name
String, max. length 32
Mandatory. Unique.
Description
Short description of the output line
Optional
Active
Check-box shows whether the line has been activated
Checked/unchecked
Output Format
Assigned output format
List of defined output formats
A31003-H3460-M104-4-76A9, July 2012


Mandatory
Translation Group
This field displays the available translation groups in a selection list. You can either select one
of the defined translation groups or -- if NO transformation is necessary -- take over the pre-
defined Default Translation Group.
Changed data that have not been saved yet cannot be printed.
A translation group consists of one or more translation tables -- - see Translation Table Editor,
Object List view und Translation Table Editor, Object view. A single translation group can be
assigned to more than one input or output lines.
To define new translation groups, use the Translation Group Editor.
To define new translation tables, use the Translation Table Editor.
Not editable (read-only).
Filter
Assigned filter or empty
List of defined filters
Optional
File Name
File destination
String
Mandatory. If the file name does not start with “/” the file name is relative to $COL_DELIVER.
If the file name is complete, $COL_DELIVER is ignored. Directory should already exist. Name
must be unique.
Start Date/Time
hh:mm dd.mm.yyyy
Mandatory. Default: current time and date.
Cycle
Choice of cycle format
Hours or Minutes
Mandatory
A31003-H3460-M104-4-76A9, July 2012

Hours:
● Combo-box with cycle-time in hours
● 1,2,3,4,6,8,12,24
● Enabled only if Cycle=Hours, not mandatory. Default: 1
Minutes
● Combo-box with cycle-time in minutes
● 1,2,3,4,5,6,10,12,15,30
● Enabled only if Cycle=Minutes, not mandatory. Default 15.
Save (Button)
New (Button)
None
Delete (Button)
A31003-H3460-M104-4-76A9, July 2012


Output Line Definition - Object List view, field descriptions
4.11 Output Line Definition - Object List view, field descriptions

Save (Button)
New (Button)
Delete (Button)
The object can not be edited. Each row contains information about one output line.

Name
Output line name
Read-only
Description
Short description of the output line
Read-only
Output format
Assigned output format
List of defined output formats
Read-only
Filter
Assigned filter or empty
List of defined filters
Read-only
Active
Status check: Is line activated?
A31003-H3460-M104-4-76A9, July 2012

Output Line Definition - Object List view, field descriptions
Yes/No
Read-only
Filename
File destination
String
Read-only
Start Date/Time
hh:mm dd.mm.yyyy
Read-only
Cycle
Cycle time in hours or minutes. Possible values for minutes are: 1,2,3,4,5,6,10,12,15,30. Pos-
sible values for hours are: 1,2,3,4,6,8,12,24.
Hours or Minutes
Read-only
Save (Button)
New (Button)
None
Delete (Button)
A31003-H3460-M104-4-76A9, July 2012


Output Format Editor - Object view, field descriptions
4.12 Output Format Editor - Object view, field descriptions

Format Name
Description
End of Line
Element group list
Number Of Elements
Format Length
Save (Button)
New (Button)
Delete (Button)
Format Name
Name of the selected format.
Required, unique
Description
End of Line
Combo-box to choose End of Line sequence
List of values: LF, CR, CR/LF, none)
Element group list

Selection of the element group. Combo-box with the list of element groups.
Values: Standard Elements, CM Elements, Text Elements
Read-only
A31003-H3460-M104-4-76A9, July 2012

Note: On a HiPath Manager the CM Elements are only displayed if the COL software is installed
with the necessary user license rights. No licence is needed for a HiPath Assistant.
Predefined
This box is checked (activated) with predefined, non-editable tables.
Possible values: Activated, Not activated.
Read-only.

List of elements available in the database. Allows selection of the element to be added to the
Output table.
Values: String
Read-only
Name
Element name, e.g. "BCHLCNT" for "Number of used B channels"
Value: String
Read-only
Description
Element description, e.g. "Number of used B channels" for "BCHLCNT"
Value: String
Read-only

List of output elements added by the user to the Output elements table. Output elements can
be edited by double-clicking on a record (row) in the Output elements table. The modal window
Configure Output Element is then opened and allows editing of the selected output element.
Values: String
# (Count number)
Position number
A31003-H3460-M104-4-76A9, July 2012


Integer
Read-only. Position number is automatically generated by program.
Name
Element name, e.g. "BCHLCNT" for "Number of used B channels"
Value: String
Read-only
Description
Element description, e.g. "Number of used B channels" for "BCHLCNT"
String
Read-only
Length
Integer
Read-only
Alignment
Alignment
Left, Right
Read-only
Filler
Character for padding.
Char
Read-only
Text
Text is defined only for fixed text elements
String
Read-only
A31003-H3460-M104-4-76A9, July 2012

Number Of Elements
Number of elements in the Output table
Integer
Read-only
Format Length
Total length in bytes of an output row.
Integer
Read-only
Save (Button)
New (Button)
None
Delete (Button)
A31003-H3460-M104-4-76A9, July 2012


Output Format Editor - Object List view, field descriptions
4.13 Output Format Editor - Object List view, field descriptions

Save (Button)
New (Button)
Delete (Button)

Format Name
Read-only, unique.
Description
Read-only
Element Count
Number of elements in the output element table.
Integer
Read-only
Format Length
Total length in bytes of an output row.
Integer
Read-only
A31003-H3460-M104-4-76A9, July 2012

Output Format Editor - Object List view, field descriptions
Save (Button)
New (Button)
None
Delete (Button)
A31003-H3460-M104-4-76A9, July 2012


Output Format Editor - Configure Output Element, field descriptions
4.14 Output Format Editor - Configure Output Element, field

descriptions
No.
Element Description
Type
Length
Alignment
Filler
Text
No.
Position number
Integer
Read-only
Element Description
Element name
String
Read-only
Type
String, Numeric
Required
Length
Integer
Required only if Type is String.
Alignment
Combo-box to define alignment
A31003-H3460-M104-4-76A9, July 2012

Output Format Editor - Configure Output Element, field descriptions
Left, Right
Filler
Character used for padding
Char
Text
Text property for fixed text elements
String
Enabled and required only for fixed text elements.
A31003-H3460-M104-4-76A9, July 2012


Filter Editor - Object view, field descriptions
4.15 Filter Editor - Object view, field descriptions

Filter Name
Description
Number Of Elements
Save (Button)
New (Button)
Delete (Button)
Filter Name
Mandatory
Description
Optional

Selection of the element group. Combo-box with dropdown list of element groups.
Values: Standard Elements, CM Elements, Complex Elements
Read-only

List of elements available in selected element group. Allows selection of an element. The table
displays the following columns:
Name
Table column with element names
A31003-H3460-M104-4-76A9, July 2012

Values: String, e.g. "ACCOUNT" for "Account Number"

Read-only
Element Description
Table column with element descriptions
Values: String, e.g. "Account Number" for "ACCOUNT"
Read-only

List of elements added by the user to the Filter Clause table. Filter Clause elements can be
edited by double-clicking on a record (row) in the Filter Clause elements table. The modal win-
dow Configure Filter Element is then opened and allows editing of the selected output ele-
ment.
#
Position number
Integer
Read-only. Position number is generated automatically by program.
Name
Table column with element names
String
Read-only
Operator
Table column with operators
=, <>, <, > <=, >=, IN, NOT IN
Required
Value
Table column with values. In case of multiple values, comma is used as the delimiter.
String; eg [1-1-20-4711]
Required
A31003-H3460-M104-4-76A9, July 2012


Number Of Elements
Number of rows in the selection clause
Integer
Read-only
Save (Button)
New (Button)
None
Delete (Button)
A31003-H3460-M104-4-76A9, July 2012

Filter Editor - Object List view, field descriptions
4.16 Filter Editor - Object List view, field descriptions

Save (Button)
New (Button)
Delete (Button)
The object can not be edited. Each line contains information about one filter. To edit one of the
records from this table, double click on it to open the modal dialog Set Default Value.

Filter Name
Name of the filter
Read-only, unique.
Description
Read-only
Element Count
Number of elements in the filter table.
Integer
Read-only
Save (Button)
New (Button)
A31003-H3460-M104-4-76A9, July 2012


Filter Editor - Object List view, field descriptions
None
Delete (Button)
A31003-H3460-M104-4-76A9, July 2012

Filter Editor - Set Default Value, field descriptions
4.17 Filter Editor - Set Default Value, field descriptions

Element Name
Element Description
Operator
Value
Element Name
Name of element selected in the Filter Clause table.
String
Read-only
Element Description
Description of the element selected in the Filter Clause table.
String
Read-only
Operator
Combo-box with operators
=, <>, <, > <=, >=, IN, NOT IN
Required
Value
Value
String, range for numeric values and values in brackets []
Required
A31003-H3460-M104-4-76A9, July 2012


Translation Table Editor - Object view, field descriptions
4.18 Translation Table Editor - Object view, field descriptions

Description
Element
Delete Row (button)
Save (button)
New (button)
Delete (button)

Name of selected translation table.
String (max. 30 characters).
Unique.
Mandatory.
Description
Short description of translation table.
Optional.
Element
This combo box contains the list of Standard Elements and CM Elements.
The list of Standard Elements also contains generated elements which do not appear in the in-
put (e.g. SYSTYPE).
The CM Elements are only displayed if the COL software is installed with the necessary user
license rights.
Mandatory.
A31003-H3460-M104-4-76A9, July 2012


This table is used to define or change the input and output values for the translation table. The
table displays the following columns:
Position
Displays the sequential number of each table row.
The sequential numbers of all table rows are automatically assigned or updated, respectively,
upon creation or deletion of a row. If a row is added or deleted between already existing rows
at a later time, the sequential numbers of all following rows will be updated automatically.
Read-only.
In Value
Enter the input value for the translation (transformation) here.
String, max. 100 characters.
Value must be unique within one table.
Out Value
Enter the output value for the translation (transformation) here.
Value must be unique within one table.
Optional.
Comment
Optional.
Number of Values (xx)

The total number of rows in the table is displayed here.
Integer.
Read-only.

A31003-H3460-M104-4-76A9, July 2012



Read-only.

Click this button to add a new row to the table.
A new, empty row is inserted into the table below the currently selected row. The cursor is po-
sitioned in the In Value column in the new row.
The sequential numbers of all rows following the newly inserted row are updated automatically.
Delete Row (button)

Click this button to delete the selected row from the translation table.
The sequential numbers of all rows following the deleted row are updated automatically.
New (button)
Click this button to create a new object and to switch to the new object.
Copy (button)
Copy the current object to the clipboard.
This button is only enabled in the Object view.
Insert (button)
Insert the previously copied object from the clipboard into the current view.
Save (button)
Save changes to the database.
An error message is issued if wrong or illegal values are entered.
Delete (button)
Delete the selected object.
A warning message is issued before irreversible deletion.
This button is only enabled in the Object List view.
A31003-H3460-M104-4-76A9, July 2012

Translation Table Editor - Object List view, field descriptions
4.19 Translation Table Editor - Object List view, field descriptions

Save (Button)
New (Button)
Delete (Button)

The table shows the following values:
Table Name
Name of the selected translation table.
Unique, mandatory.
Read-only.
Element
This combo box contains the list of Standard Elements and CM Elements - see Translation Ta-
ble Editor - Object view, field descriptions.
The list of Standard Elements also contains generated elements which do not appear in the in-
put (e.g. SYSTYPE).
The CM Elements are only displayed if the COL software is installed with the necessary user
license rights.
Read-only.
Description
String (max. 255 characters)
Optional.
Read-only.
A31003-H3460-M104-4-76A9, July 2012


Translation Table Editor - Object List view, field descriptions
Number of Values
Number of elements in the translation table.
Integer.
Read-only.
Mandatory.
Save (Button)
New (Button)
Create a new object and switch to this new object.
Delete (Button)
Delete selected object.
A31003-H3460-M104-4-76A9, July 2012

Translation Group Editor - Object view, field descriptions
4.20 Translation Group Editor - Object view, field descriptions

Group Name
Description
Number of Tables
Save (button)
New (button)
Delete (button)
Group Name
Unique name of translation group.
Unique,
Mandatory.
Description
Short description of translation group.
Optional.

Read-only.

The table located in left hand side area of Translation Group Editor dialog, Object. view dis-
plays the available translation tables that can be added to a translation group.
A31003-H3460-M104-4-76A9, July 2012


Table Name (table column)

Table column in Available tables list located in left hand side area of Translation Group Ed-
itor dialog, Object. view.
Displays the name of the translation table.
Read-only.
Element (table column)

Table column in Available tables list located in left hand side area of Translation Group Ed-
itor dialog, Object. view.
Displays the element for which a value transformation (translation) is defined in the table.
Read-only.
Description (table column)

Read-only.
Optional.

Titel of table located in right hand side area of Translation Group Editor dialog, Object. view.
This table displays the translation tables that have been added to a translation group.
Table Name
Name of selected translation table.
Read-only.
Element
Table column in the Translation Tables in the Group table located in right hand side area of
Translation Group Editor dialog, Object. view.
Displays the element for which a value transformation (translation) is defined in the table.
A31003-H3460-M104-4-76A9, July 2012


Read-only.
Description
Read-only.
Optional.
Number of Values
Number of values in the translation table.
Integer.
Read-only.
Number of Tables
Number of tables in the group.
Integer.
Read-only.
Save (button)
New (button)
Delete (button)
A31003-H3460-M104-4-76A9, July 2012


Translation Group Editor - Object List view, field descriptions
4.21 Translation Group Editor - Object List view, field descriptions

Save (button)
New (button)
Delete (button)

The table displays the following values:
Translation Group Name

Name of the translation group.
Read-only.
Mandatory.
Description
Short description of translation group.
Read-only.
Optional.
Number of Tables
Number of tables in the group.
Integer.
Read-only.
Save (button)
New (button)
A31003-H3460-M104-4-76A9, July 2012

Translation Group Editor - Object List view, field descriptions
Delete (button)
A31003-H3460-M104-4-76A9, July 2012


Incorrect Records dialog, field descriptions
4.22 Incorrect Records dialog, field descriptions

Refresh (button)
Delete (button)
View CDRs

System ID
System ID
String
Read-only. System ID is extracted from the directory name. If the file is stored in the wrong di-
rectory, the System ID is wrong as well.
File Name
File name (without directory name)
String
Read-only
File Size
File size in kilobytes
Integer
Read-only
Input Format
Input format for the switch
String
Read-only. Current format for the switch is fetched from the database. It is not necessarily the
original format of the file.
A31003-H3460-M104-4-76A9, July 2012

Incorrect Records dialog, field descriptions

Sends the incorrect data back to the input.
Refresh (button)
Updates the display of the incorrect data sets.
The system does not issue any message informing you whether the processing of the CDR
data was successful or not. If the processing was successful, the CDR file will automatically be
deleted from the list. If processing was not successful, the CDR file will continue to be displayed
in the list of incorrect data sets. The display is not updated automatically. To make sure that you
have the current data displayed, we recommend to re-open the dialog and to click on Refresh.
Delete (button)
Deletes the data sets from the displayed list.
View CDRs
Displays the content of the selected CDR in the CDR Viewer (see CDR Viewer, page 3-120).
A31003-H3460-M104-4-76A9, July 2012



Send Back To Input
Refresh
Delete
Send All Back To Input
View CDR Files

The existing CDR files in the backup directory will be displayed in a table, showing file informa-
tion about:
● System ID
● File Name
● File Size
● Input Format
The columns of the table are sortable by clicking on the column header.
Also multiple selection is available for the functions of the Send Back To Input and Delete but-
tons.
Send Back To Input

All selected files are transformed from the input format to the standard format.
Refresh
Updates the list.
Delete
Deletes the selected entries from the backup directory.
Send All Back To Input

All files from the table are transformed from the input format to the standard format.
View CDR Files

A31003-H3460-M104-4-76A9, July 2012


Refresh
Delete
View CDRs

● Output Line Name
Name of the output line which produced the CDR
● Output Line Description
Description/switch of the output line which produced the CDR
● File Name
CDR file name.
● File Size
Size of the CDR file (in kilobytes)
● Output Format
Output format of the CDR file, if recognized.
Refresh
Re-reads the manager’s delivery directories and updates the list.
Delete
Deletes the selected CDR file(s).
View CDRs
A31003-H3460-M104-4-76A9, July 2012


COL Paths tab sheet, Options dialog, field descriptions
4.25 COL Paths tab sheet, Options dialog, field descriptions

Input Path
Transform Path
AM Deliver Path
PM Deliver Path
FTBL Path
Save (button)
Input Path
Directory where to store input files.
String.
Also referred to as $COL_INPUT.
Transform Path
Directory where to store transformed files.
String.
Also referred to as $COL_TRANSFORM.

Directory where to store output files.
String.
Also referred to as $COL_OUTPUT.
AM Deliver Path
Directory where to deliver files for AM.
String.
Also referred to as $COL_DELIVER.
A31003-H3460-M104-4-76A9, July 2012

COL Paths tab sheet, Options dialog, field descriptions
PM Deliver Path
Directory where to deliver files for PM.
String.

Directory where to store rejected CDRs.
String.
Also referred to as $COL_ERROR.
FTBL Path
Directory where FTBL files are stored.
String.
Also referred to as $COL_FTBL.

Path where the traffic metering files will be saved.
String
A31003-H3460-M104-4-76A9, July 2012


Settings tab sheet, Options dialog, field descriptions
4.26 Settings tab sheet, Options dialog, field descriptions

Required Free Space
Retrieve CDRs alive time
Save (button)
Required Free Space

Required free space on disk in % for input files.
Integer (0-100).

Use this field to enter the duration (in number of days) for the retention period of CM history
data.
Integer.
Default vaule: 20 days.
A31003-H3460-M104-4-76A9, July 2012

When this check box is marked, the fast mode for transformation of virtual to physical node
numbers is activated for the PM output line only.

Using this check box you can specify whether the logging entries in COL should be automati-
cally deleted or saved and retained for a certain period.
When this check box is marked, the logging entries will automatically be deleted.

Use this field to enter the duration (in number of days) for the retention period of the logging
entries.
The value entered here will only become active and can only be administered if you activated
the Activate/Deactivate Automatic Delete of Logging Entries in COL option by marking the
check box.
Integer, 1-3 digits
Possible values: 1 - 366 day(s)
Use this field to enter the period - defined in days - for the retention period of the trunk usage
data obtained by the Cyclic Check of Trunk Groups feature and stored in the COL database.
Data older than the retention period defined in this field will be deleted.
Integer.
Default value: 100 days.
Max. value: 366 days.

Use this check box to enable/disable the backing up of input files (CDRs). If this check box is
enabled, the input files containing the call data record sets (CDRs) will be saved to a backup
directory under the path ..\var\COL\data.
Important: If this feature is enabled you need to make sure that the data stored in
7 the backup directory is archived/deleted regularly, otherwise the disk storage capac-
ity will be exceeded.
A31003-H3460-M104-4-76A9, July 2012


When activating this feature, all collected input data is saved in the /var/col/data/backup/<Sys-
tem-ID>/<cdr_filename> directory. At present the Collecting Agent / HiPath COL does not sup-
port a feature for deleting the data in the /var/col/data/backup directory. Therefore, the user who
activated this feature is responsible for the administration/deletion of the backup data. This fea-
ture is used to read in and thus recover from the backup directory CDR data that has been lost
in the recording and evaluation system.
In order to read in the CDR records, the required CDR files can be copied to the /var/col/data/
error/<System-ID> directory. The data records are then read in via the Incorrect Records di-
alog by selecting the file and pressing the Send Back to Input button.
If this feature is enabled the /var partition may be completely filled with data (depend-
7 ing on the value set for Required Free Space in the Options dialog). This may re-
sult in a complete stop of the data collection process by the Collecting Agent / HiPath
COL. The stopping of the CDR collection process may result in a loss of CDR data.
Therefore, you should regularly delete this data in order to avoid exceeding the storage capac-
ity of the /var partition.

Check this checkbox to set the period of days in the Day(s) spinner box for the retention period
of the Attendant Console usage data, which are obtained by the Download of Attendant Con-
soles feature and stored in the COL database (System Management).
Data older than the retention period defined in this field will be deleted.
Integer.
Default value: 366 days.
Possible values: 366 - 999 days.

If this option is enabeled, you can select e-mail recipients from a list of subscribers defined in
the CM application (Configuration Management –> Personal Data –> Subscriber).
For details setting up the e-mail server, please refer to Email Settings in the RepGen Admin-
istration Page in:
● Report Generator Manual; V6 (English)
● Report Generator Manual; V6 (German)
A31003-H3460-M104-4-76A9, July 2012


By clicking the Lookup button (...) button on the right of the text input field, you can select e-
mail recipients from a list of subscribers defined in the CM application (Configuration Manage-
ment –> Personal Data –> Subscriber).
istration Page in:

When the checkbox Save Input Files (CDRs) in this tab is checked, the CDR files are stored
in a directory per system. After this, you can activate and deactivate an automatic cleanup of
stored CDR files by checking/unchecking the Activate/Deactivate automatic Cleanup check-
box and set parameters for time and size of the cleanup:

Set the retention time for the saved CDR files in the Day(s) spinner box.
Data older than the retention period defined in this field will be cleaned.
The default time for the cleanup is 40 days.
● Day(s)
If the checkbox is checked, the Day(s) spinner box will be enabled, otherwise this will be
disabled.

Activate this checkbox, if you want to limit the size of the backup directory.
If the checkbox is checked, then the edit field Size of backup Directory will be enabled, oth-
erwise this will be disabled.
● Size of backup Directory
The size of CDR files which can be saved in the backup directory will set in MB. The default
size will be 512 MBs.

By setting a number of minutes in the spin field Retrieve CDRs alive time you can define the
interval how often the size of the CDR file being retrieved will be checked in order to ensure
that the col_receive process is still active and has not been blocked.
● Retrieve CDRs alive time
A31003-H3460-M104-4-76A9, July 2012


The range of values for the retention period.

The spin field can be scrolled from 10 to 60 minutes.
Default value: 20 minutes.
A31003-H3460-M104-4-76A9, July 2012

Process Controlling tab sheet, Options dialog, field descriptions
4.27 Process Controlling tab sheet, Options dialog, field descriptions

Start Time
Stop Time
Save (button)

Number of receive processes.
Integer.
Default value: 1

Number of transform processes. The number of Transform processes must always be equal to
the number of Line processes.
Integer.
Default value: 1
Maximum value: 10

Number of line processes. The number of Transform processes must always be equal to the
number of Line processes.
Integer.
Default value: 1
Maximum value: 10
A31003-H3460-M104-4-76A9, July 2012



Number of metering processes.
Integer.
Default value: 1

Number of TG-Check processes.
Integer.
Default value: 1

With this feature it is possible to configure time-controlled transformation and output of CDR
data in COL. However, this does not apply to performance extensive transformation and col-
lecting of call charge data, which will be done during times of lower system load.
Schedule incorporation is supported for both Manager and Assistant.
Multiple Processes are not supported for Assistant.
>
Activation and Deactivation
The feature can be activated by the the Schedule Incorporation of CDR Processing Active
checkbox.
If the checkbox is checked, the feature is be enabled. If the checkbox is unchecked, the feature
is deactivated.
Default value: unchecked
Start Time
Define a start time.
Start Time selector will be enabled only if the Schedule Incorporation of CDR Processing
Active checkbox is checked.
The difference between the Stop and Start times must be more than or equals to 1 hour and
less than or equals to 18 hours.
A31003-H3460-M104-4-76A9, July 2012

Stop Time
Define a stop time.
Stop Time selector will be enabled only if the Schedule Incorporation of CDR Processing
Active checkbox is checked.
The difference between the Stop and Start times must be more than or equals to 1 hour and
less than or equals to 18 hours.
A31003-H3460-M104-4-76A9, July 2012


Options dialog, Save button description
4.28 Options dialog, Save button description

Save (button)
Save (button)
This button applies to all of the tab sheets in the Options dialog.
The parameter values entered are saved in the database. The changed settings are applied
after COL system restart only. You must be an authorized user with "rsca" access rights to be
allowed to make changes and save values.
An error message is issued if wrong values are entered.
A31003-H3460-M104-4-76A9, July 2012

Logging dialog (log file)
4.29 Logging dialog (log file)

Log Type:
● Receive Log
● Output Log
● Cyclic Check Log
● Error and Activity Log
System ID
To: (Date: / Time:)
View (button)
Delete (button)
Log Type:
● All Log
Selects as logging type all logging categories in the list.
● Receive Log
Contains the error log for the receive lines.
● Output Log
Contains the error log for the output lines.
Contains the error log that informs you whether the Cyclic Check has started, finished or if
an error has occurred for a specific system ID. The Error and Activity Log is also updated
if necessary, i.e. if an error occurs for a specific system ID, then the Error and Activity Log
will display additional information regarding to this error.
Selects as logging type only the Receive Loggings. Selecting this radio button activates the
sub-checkboxes Activity Log and Error Log (default: both checked, both log types will be
included in the result).
– Activity Log
Option checked/unchecked: Includes/excludes Activity Loggings in the results.
– Error Log
A31003-H3460-M104-4-76A9, July 2012


Option checked/unchecked: Includes/excludes Error Loggings in the results.
System ID
The System ID list box is activated only if the corresponding System ID checkbox to the left is
enabled. If the checkbox is unchecked, all the available system IDs are taken into account after
the View button is clicked. The system ID is selectable from the list box (multiple selection is
possible), where all existing system IDs in SysM are displayed. For events, which are created
by Manager the System ID is Local which is the default value of the list box.

Define the beginning for the period of time for which the selected log should be generated. You
can either select the date from the Calendar view and the time from the spinner box or enter
both manually.
To: (Date: / Time:)

Define the end for the period of time for which the selected log should be generated. You can
either select the date from the Calendar view and the time from the spinner box or enter both
manually.
View (button)
To view the selected message logs, click the View button.
Delete (button)
To delete a message log, click the Delete button next to the selected log type for the entered
period of time.
A31003-H3460-M104-4-76A9, July 2012

4.29.1 COL Logging Events dialog

● Logging Type
● Logging Period
● Date (column)
● Error (column)
Button
Print/Export
Columns in the Log Table

Indicates the amount of log entries for the selected logging events within the selected period
and shows in the bottom of the page on the right the total of Number of events found.
The read only columns indicate:
● Logging Type
Displays the log type selected in the Logging Dialog.
● Logging Period
Displays the logging period for the log type selected in the Logging Dialog.
● Date
Displays the date and time when the log message was issued.
● Category
Indicates the category of the logged activity, e.g. "start application" or "exit application".
● Error
List of possible errors in error codes
● System ID
A31003-H3460-M104-4-76A9, July 2012


The ID of the network node (switch) that is being logged and issued the log message.
● Short message
Displays a short description of the logged activity or error, e.g.
"COL process dbproxy started."
● Long message
Displays a short description of the logged activity or error, e.g. "COL process dbproxy start-
ed."
● Severity
Indicates the severity of the log message.
Values: 0 indicates lowest severity.
Print/Export
Prints or exports the displayed loggings. After clicking this button the Run Report dialog is dis-
played to select the output format (for export: HTML, XML, PDF) for the file, output options
(screen, printer) and to send the log file as e-mail.
4.29.2 COL Logging Events Report

Logging Type
Logging Period
Date
Category
Error
System ID
Short message
Long message
Severity
Logging Type
Displays the log type selected in the Logging Dialog.
Logging Period
Displays the logging period for the log type selected in the Logging Dialog.
A31003-H3460-M104-4-76A9, July 2012

Date
Displays the date and time when the log message was issued.
Column
Category
Indicates the category of the logged activity, e.g. "start application" or "exit application".
Column
Read only
Error
List of possible errors
Error code
System ID
The ID of the network node (switch) that is being logged and issued the log message.
Column
Short message
Displays a short description of the logged activity or error, e.g. "COL process dbproxy started."
Long message
Displays a short description of the logged activity or error, e.g. "COL process dbproxy started."
Severity
Indicates the severity of the log message.
Values: 0 indicates lowest severity.
A31003-H3460-M104-4-76A9, July 2012


CDR Viewer
4.30 CDR Viewer

Define Format
Display all CDRs
Print
Define Format
DropDown list for defining the format of the displayed CDR.
For the record format descriptions refer to the tables in the Reference Material, e.g. Pre-defi-
ned Formats for Output Format Definition, page 6-97.
When you change the type of Input/Output Format and the length of the CDR still fits to this
choice, the CDR Viewer dialog will retain its layout.
If the CDR’s length does not fit to the selected Input/Output format, the CDR Viewer dialog au-
tomatically switches to the alternative ’Undefined’ layout.
Display all CDRs

If this checkbox is selected, all CDRs will be displayed in the table.
if the total number of Records in the CDR file is grater than 500 and you check this checkbox
a message window is displayed, informing that it might take a while to display all records. You
can confirm or abort the action in this message window.
If this checkbox is not selected, only the first 20 CDRs will be displayed, if the format is known
valid. Related to the loaded files the format description will be displayed as column header.
If the checkbox is not selected and the format is undefined, only the first CDR is displayed in
’undefined’ layout.

Depending on the selected and displayed file format (not for ’undefined’), the fields of the CDR
and the column headers of the table columns vary. For the field descriptions refer to the tables
in the Reference Material, e.g. Pre-defined Formats for Output Format Definition, page 6-
97.
Print
Pressing this button, the CDR record is exported in to the defined standard printer.
A31003-H3460-M104-4-76A9, July 2012

CDR Viewer

Read only field, gives information, how many CDRs are listed in the CDR file.
A31003-H3460-M104-4-76A9, July 2012


Collecting Agent tab sheet in System Management
4.31 Collecting Agent tab sheet in System Management

The Collecting Agent tab sheet in System Management comrises five sub tabs:
A31003-H3460-M104-4-76A9, July 2012

4.31.1 COL Administration sub tab

Input Format
PM Input Format
Translation Group
Number Of Retries
Retry Time
Collect AM Data
Collect PM Data (*)
File/Directory Name
Start Date
Start Time
Cycle
Hours
Minutes
Input Format
Combo box with the list of all supported input formats. The drop down list of all supported input
formats is shown in this box.
PM Input Format
Combo box with the list of supported PM input formats.
The PM Input Format field provides a a combo box of short PM input formats in order to reduce
the length of the PM-N CDR records and thereby reduce the data volume when PM is active.
The PM Input Format field is only active, when the Collect PM Data checkbox is checked.
When the Collect PM Data checkbox is checked, the PM Input Format field displays the same
format as the Input Format field (default).
The PM input formats is available for the following switch versions:
A31003-H3460-M104-4-76A9, July 2012

● UV6
● UV5
● UV4
● UV2.0 (Version 2.0 only),
● UV1.0,
All formats contain RECTYPE as leading element. The names of the new PM input formats are:
● PM-N_UV6
● PM-N_UV5
● PM-N_UV4
● PM-N_UV2.0 (Version 2.0 only),
● PM-N_UV1.0,
The PM-N_xxx formats contain the following elements:
No Element Type Length

1 FIXTEXT $ 1
1 RECTYPE number 1
2 CALLILV0 number 3
3 CALLILV1 number 3
4 CALLILV2 number 2
5 CALLIPTY string 22
6 CONNTYPE string 1
7 CONTOT number 6
8 DESTLV0 number 3
9 DESTLV1 number 3
10 DESTLV2 number 2
11 DESTPTY string 22
12 END10 number 1
13 ENDDAY number 2
14 ENDHOUR number 2
15 ENDMIN number 2
Table 4-1 PM-N input formats
A31003-H3460-M104-4-76A9, July 2012

No Element Type Length

16 ENDMONTH number 2
17 ENDSEC number 2
18 ENDYEAR number 4
19 QUEUEDUR number 5
20 RINGDUR number 3
21 SUPLSERV string 2
22 THRESEQ number 8
23 TKNOREAL number 5
24 TKNOTRGR number 3
SUM: 109
Table 4-1 PM-N input formats
The output format to PM remains unchanged and is not affected.
The RECTYPE element can have 4 different values. The value of the RECTYPE element de-
fines whether a CDR record is relevant for AM only, PM only, AM + PM or for none of the two
(see following table).
To separate AM data from PM data it is therefore sufficient to check the value of the RECTYPE
element for each CDR record.
RECTYPE/COLTYPE value 0 1 2 3
Relevant for None AM PM AM and PM
Table 4-2 RECTYPE/COLTYPE - possible values
Translation Group
This combo box displays a selection list of available translation groups. You can either select
one of the defined translations groups, or - if NO translation group is required - you can use the
Default Translation Group.
Changed data that has not been saved yet can not be printed.
In order to provide all CDRs for HiPath systems in a consistent, "normalized" format, the differ-
ent values of the CDR elements need to be transformed or "translated" in such a way that they
all have the same value in the COL standard elements. This is reached by translation tables for
the input and output lines.
A translation group consists of several translation tables and can be assigned to several input
or output lines. Likewise, a translation table can be used in several translation groups.
A31003-H3460-M104-4-76A9, July 2012


Translation tables consist of value pairs that define how the value of an element is being "trans-
lated" in the input or output process.
Every translation table is defined for a specific standard element.
Translation tables and translation groups can be created and edited by the user, and they can
be saved in the database under a unique name.
This field is not editable (read-only).
Collect AM Data
Check box to activate AM collecting.
Checked/not checked.

3 numeric entry fields for the node number.
Values: 1 to 9
Field lengths: 3,3,2; Mask: 111-111-11
Collect PM Data (*Only supported for HiPath 4000 COL)

Check-box for activating PM collecting.
Checked/Not Checked.
Enabled only if PM installed.

Select the CDR data source in CDR Source field. File or Directory can be specified as source.
File: Click this radio button if a file is to be specified as CDR data source.
Directory: Click this radio button if a directory is to be specified as CDR data source.
Radio buttons to choose input from file or directory.
File/Directory Name
The name of the file or directory as CDR data source can be specified on this field.
String
Default: FTFILE
A31003-H3460-M104-4-76A9, July 2012


If this check box is enabled, the input files containing the call data record sets (CDRs) will be
saved to a backup directory under the path ..\var\COL\data.
When activating this feature, all collected input data is saved in the /var/col/data/backup/<Sys-
tem-ID>/<cdr_filename> directory. At present the Collecting Agent / HiPath COL does not sup-
port a feature for deleting the data in the /var/col/data/backup directory. Therefore, the user who
activated this feature is responsible for the administration/deletion of the backup data. This fea-
ture is used to read in and thus recover from the backup directory CDR data that has been lost
In order to read in the CDR records, the required CDR files can be copied to the /var/col/data/
error/<System-ID> directory. The data records are then read in via the Incorrect Records di-
alog by selecting the file and clicking the Send Back to Input button.
Therefore, you should regularly delete this data in order to avoid exceeding the storage capac-
ity of the /var partition.

If this check box is enabled, the input files containing the call data record sets (CDRs) will be
copied from the RMX to the Unix area.
Number Of Retries
The number of retries for data transfer is entered in this field.
Integer.
Default: 3.
Retry Time
The time interval (in minutes) until the next retry for data transfer is entered in this field.
Integer.
Default: 15 min.
Start Date
The date to begin the collecting process is entered on this field.
Date.
Default: today.
A31003-H3460-M104-4-76A9, July 2012


Start Time
The time to begin the collecting process is entered on this field.
Time in format “hh:mm”.
Default: current time.
Cycle
The time length of a collecting cycle is entered on this field.
The duration can be specified in hours or minutes.
Default: hours.
Hours
Combo box with hours. Select this field if the duration for one cycle is to be in hours. The de-
sired numerical values can be chosen from the selection list below the field.
1, 2, 3, 4, 6, 8, 12, 24
Enabled only if Cycle = Hours, not mandatory. Default: 1
Minutes
Combo box with minutes. Select this field if the duration for one cycle is to be in minutes. The
desired numericl values can be chosen from the selection list below the field.
1, 2, 3, 4, 5, 6, 10, 12, 15 ,30
Enabled only if Cycle = Minutes, not mandatory. Default: 15.
A31003-H3460-M104-4-76A9, July 2012

4.31.2 Trunk Group/CDR sub tab

Download (button)
Activate (button)
Download Status
Activation Status
Name (table column)
AM (table column)
PM (table column)
Start Date
Start Time
Hours
Minutes
Refresh (button)
Save (button)
Discard (button)
Download (button)
Click the Download button to download the trunk group data from the system. The download
process is performed asynchronously, i. e. you need to click the Refresh button in order to get
the current download status displayed in the table. Click the Save button to same changed at-
tributes and new data to a COL database.
When you start a data transfer by clicking the Activate or Download button, the status is set
to "Running".
During a running upload or download process (Status: "Running" is displayed) you can click the
Refresh button to get the current status displayed.
A31003-H3460-M104-4-76A9, July 2012


Activate (button)
Click the Activate button to send changed trunk group data back to the system. The Activate
button is deactivated as long as you are editing and/or changing data; the Activate button is
only activated after you have clicked the Save button to confirm and apply your changes. The
upload process is also performed asynchronously, i.e. you need to click the Refresh button in
order to get the current data displayed in the table.
to "Running".
After having performed the Cyclic Check for selected trunk groups, the user can upload infor-
mation about metered trunk groups back to the switch by pressing the Activate button. The PM
data generated on the switch will then contain only the selected trunk groups. This reduces the
communication with the switch and the amount of PM data.
Download Status
The status of the last download is displayed here. When you click the Download button, the
displayed value changes, and a new download process starts. When the page is opened in the
browser, the status of the last download is shown.
Possible values: OK; Error; Running; N/A if undefined.
Read-only
Start value: N/A
to "Running".

The date/time of the last download is displayed. When you click the Download button, the dis-
played value changes, and a new download process starts. When the page is opened in brows-
er, the date/time of the last download is shown.
Display format: “dd:MM:yyyy hh:mm”; N/A if undefined.
Read-only.
Start value: N/A.
A31003-H3460-M104-4-76A9, July 2012

Activation Status
The status of the last upload is displayed here. When you click the Activate button, the dis-
played value changes, and a new upload process starts. When the page is opened in the
browser, the status of the last upload is shown.
Possible values: OK; Error; Running; N/A if undefined.
Read-only.
Not displayed on HiPath 4000 systems.
Start value: N/A
to "Running".

The date/time of the last upload is displayed here. When you click the Activate button, the dis-
played value changes, and a new upload process starts. When the page is opened in the
browser, the date/time of the last upload is shown.
Display format: “dd:MM:yyyy hh:mm”; N/A if undefined.
Read-only.
Start value: N/A
Table of Trunk Group Data

This table serves the following purposes:
● Displays the trunk group data
and
● Allows you to select individual trunk groups to be metered and to be sent back to the sys-
tem.
A31003-H3460-M104-4-76A9, July 2012


The Start Date, Start Time and Cycle Time parameters for the cyclic check have to be defined
individually for each switch.
The table contains the following columns:
Name (table column)
AM (table column)
PM (table column)

ID number of the trunk group.
Integer.
Read-only;
Unique for selected switch.
Name (table column)

Trunk group name.
String (max. length 30 characters).
Read-only;
Unique for selected switch.
AM (table column)
Check box is checked if trunk group is relevant for AM.
Possible values: Checked, unchecked.
Default value: unchecked.
A31003-H3460-M104-4-76A9, July 2012

PM (table column)
Check box is checked if trunk group is relevant for PM.

The check box in this table column allows you to enable or disable the Cyclic Check of Trunk
Groups feature for selected trunk groups only. Activating the Cyclic Check only for selected
trunk groups reduces communication with the switch and the amount of data.
By activating the Cyclic Check of Trunk Groups feature you can perform a cyclic check which
queries the usage of all available resources (B channels) assigned to a trunk group in defined
time intervals (cyclically). This feature makes sure that only the actually available resources
(status READY) assigned to a trunk group are collected and counted in a report. The Collect-
ing Agent stores the resulting trunk group usage data in the COL database, and Performance
Management (PM) can then create correct trunk usage reports based on these data.
A31003-H3460-M104-4-76A9, July 2012



Use this check box to activate or deactivate the Cyclic Check of Trunk Groups feature for the
selected switch. By activating the Cyclic Check of Trunk Groups feature you can perform a
cyclic check which queries the usage of all available resources (B channels) assigned to a trunk
group. This feature makes sure that only the actually available resources (status READY) as-
signed to a trunk group are collected and counted in a report. The Collecting Agent stores the
resulting trunk group usage data in the COL database, and Performance Management (PM)
can then create correct trunk usage reports based on these data.
In order to reduce communication with the switch and the amount of data, the user can enable
or disable the cyclic check individually for selected trunk groups by checking or unchecking the
check box in the PM/TG Check column. In this way, the user can select trunk groups for which
the cyclic check is performed.
Cyclically, in defined time intervals, COL queries the usage of all available resources (B chan-
nels) assigned to a trunk group (AMO DIS-BUEND), obtaining the list of trunk groups, the as-
sociated trunk cards, and the number of assigned channels. The status of each assigned chan-
nel is also determined (AMO DIS-SDSU). Finally, the Collecting Agent calculates the number
of available channels for each trunk group. The data obtained through the Cyclic Check is then
stored in the COL database and can be used by PM for further analysis and reporting.
Additionally, the user can upload information about metered trunk groups back to the switch by
pressing the Activate button. The PM data generated on the switch will then contain only the
selected trunk groups. This reduces the communication with the switch and the amount of PM
data.
A31003-H3460-M104-4-76A9, July 2012

Start Date
The date to begin the cyclic check of trunk group resources is entered into this field.
individually for each switch. The user can activate or deactivate the Cyclic Check of Trunk
Groups feature for the selected switch by checking/unchecking the Cyclic Check of Trunk
Groups Active check box.
Format: Date.
Default: today.
Start Time
The time to begin the cyclic check of trunk group resources is entered into this field.
Time format: “hh:mm”.
Default: current time.

Enter the time interval for one metering cycle into this field.
The time interval can be specified either in hours or in minutes. Check the Hours or Minutes
radio button to specify the time unit for the cycle time period. The cycle time can be specified
either in hours or in minutes.
Default: hours.
Hours
Combo box with hours. Select this field if the duration for one cycle is to be in hours. The de-
sired numerical values can be chosen from the selection list below the field.
1, 2, 3, 4, 6, 8, 12, 24
Enabled only if Cycle = Hours
Default: 1
A31003-H3460-M104-4-76A9, July 2012


Not mandatory.
Minutes
Combo box with minutes. Select this field if the duration for one cycle is to be in minutes. The
desired numericl values can be chosen from the selection list below the field.
Values:
5, 6, 10, 12, 15, 30 for HiPath 4000
and
15, 30 for H300
Enabled only if Cycle = Minutes
Default: 15
Not mandatory.
Refresh (button)
Click Refresh to load the data from the database again and to display the current data.
to "Running". During a running upload or download process (Status: "Running" is displayed)
you can click the Refresh button to get the current status displayed.
Save (button)
Saves the changed data to the database.
The Activate button is deactivated as long as you are editing and/or changing trunk group data;
the Activate button is only activated after you have clicked the Save button to confirm and save
your changes to the database.
Discard (button)
Changes that have not been saved yet are ignored and will be lost.
New (button)
Creates a new item/entry.
Delete (button)
Deletes the selected item/entry.
A31003-H3460-M104-4-76A9, July 2012

4.31.3 Attendant Consoles sub tab
Download
Click the Download button to download available Attendant Consoles data from the system.
When you start a data transfer by clicking Download button, the status is set to "Running" and
displayed on the right side of the Download button and downloaded data are displayed in the
table below.
The download process is performed asynchronously, i. e. you need to click the Refresh button
in order to get the current download status displayed in the table.
Refresh
Since the download process is performed asynchronously, you need to click the Refresh but-
ton in order to get the current download status displayed.
Generating Node No. (table)

The currently downloaded and generated data of Attendant Consoles are displayed in the ta-
ble:
● Attendant Group: Assigned Group of the Attendant Console
● Extension: Assigned Extension of the Attendant Console
● Attendant Group Type: Group Type of the Attendant Console
● Virtual Node Number : Assigned virtual node number of the Attendant Console
A31003-H3460-M104-4-76A9, July 2012


4.31.4 Node No. Transform sub tab

Virtual Node Number
Add (button )
Remove (button)
Remove All (button)
Virtual Node Number

Enter the address of the extension into this field.
The Virtual Node Number is the three-level node number of the system to which the extension
belongs to (or of the system on which the extension is to be installed, respectively).
Virtual node numbers are composed of the following parts:
aa = node number/area number in subnetwork level 2 (0 - 29)
bbb = node number/area number in subnetwork level 1 (0 - 253)
ccc = node number/area number in subnetwork level 0 (0 - 999)
The Collecting Agent/Attendant Consoles tab sheet of the System Management applica-
tion under HiPath 4000 Assistant/Manager supports adding and setting up of extensions.

Consists of 2 entry fields.
If only one extension number has been allocated then this is to be entered in the first (left hand
side) field which holds the "lower value". The second (right hand side) field remains empty in
this case.
If an extension range comprises several extension numbers, then the lower value is to be en-
tered in the first (left hand side) field, and the upper value in the second (right hand side) field.
Add (button )
Use this button to add the data listed from the left hand side of the dialog to the extension table
on the right hand side of the dialog.
A31003-H3460-M104-4-76A9, July 2012

Remove (button)
Removes the selected entry (the selected line) from the extensions table.
Remove All (button)

Deletes all entries (all lines) from the extensions table.

Displays the virtual three-level node number in the following format:
"aa-bbb-ccc".
Not editable.

Displays the extension number, if only one extension number has been allocated.
If an extension range comprises several extension numbers, the lower value of the extension
range is displayed in this field.
Not editable.

If only one extension number has been assigned to the extension, this field remains empty.
If an extension range comprises several extension numbers , the upper value of the extension
range is displayed in this field.
Not editable.
A31003-H3460-M104-4-76A9, July 2012


Fields and Controls in the Run Report Dialog
4.32 Fields and Controls in the Run Report Dialog

The Run Report output dialog consists of the following items:
Items in the Output Tab

Report Object:
Choose template
Items in the E-mail Tab

To
CCs
Subject
Body
Items in the Exports Tab

Exports (HTML , PDF , CSV , XML)
Button
Run
Items in the Status Window

Export Format
Status
Refresh
Abort
Save As...
A31003-H3460-M104-4-76A9, July 2012

Report Object:
Indicates the selected report type to be generated (read only).
Choose template
You may select the report template from a drop down list of the available report templates for
the selected report.
By default the report template file previously specified in the RepGen Report Designing Page
is displayed.
The report template name has the following structure:
template filename {(Predefined)}
The notation "predefined" is indicated in parentheses at the end of template name only if the
template is a predefined one.

The report will be displayed in a browser window.

The report will be sent to your configured printer.

Activating the e-mail option activates the E-mail tab to select e-mail recipients for the report and
to enter the subject and a comment.

It is possible to export from the server and save the report in the following formats on your local
computer; multiple selection is possible:
● html
● pdf
● csv
● xml (MS Excel)
A31003-H3460-M104-4-76A9, July 2012


Note:
> If you have chosen a template which generates a report in chart form, xml and
csv options are disabled, because chart form is not supported for these for-
mats. This is due to limitations of Microsoft Excel application itself and its xml
document format.
To
By default the field is automatically filled with the default main address previously specified in
the RepGen Administration Page.
By clicking the Lookup button (...) button on the right of the To input field, you can select e-mail
recipients from a list of subscribers defined in the CM application (Configuration Management
–> Personal Data –> Subscriber).
istration Page in:
CCs
By default the field is automatically filled with the CC address previously specified in the Rep-
Gen Administration Page.
By clicking the Lookup button (...) button on the right of the CC input field, you can select e-mail
recipients from a list of subscribers defined in the CM application (Configuration Management
–> Personal Data –> Subscriber).
istration Page in:
Subject
Subject field of the e-mail - default: name of the report.
Body
E-mail body for entering the e-mail text.
A31003-H3460-M104-4-76A9, July 2012

Exports
Displays the export directory for each output file format. You may select for each desired output
format a different file location by clicking the Lookup button (...) on the right of the path name for
● HTML
● PDF
● CSV
● XML

Option activated:
Existing files in the selected export directories will be overwritten automatically.
Option deactivated:
If a report is to be downloaded in a directory in which a report with the same filename exists,
the download process is aborted. The report files to be downloaded remain on the server and
will not be lost.
Run
Clicking this button finally confirms your selections and settings of the Flexible Report Output
dialog and initiates the generation and export of the report. The Status window is displayed,
informing about the status of the export.
Export Format
Displays the output formats from the selection in the Output tab to be generated/exported.
Status
Information about the status of the export of each selected output format separately. The
possible status values are:
● Not started:
The exporting of this format has been enqueued but not yet started.
● Error:
An error has occurred while exporting to this format.
● Running:
The exporting has been started, but is not yet completed.
● Complete - Saved:
The exporting has been completed and the result has been downloaded to the export path
indicated in the export tabsheet of the Run Report dialog.
A31003-H3460-M104-4-76A9, July 2012


● Complete - Not Saved:

The exporting has been completed, but the result has not been downloaded. The cause is
that the checkbox "overwrite existing export files" has not been checked, and a file with the
intended name already exists in the specified local export path.
Refresh
Clicking the Refresh button displays the current status of the running export/generation
immediately instead of waiting for the automatic cyclic refresh.
Abort
In case an export file has not been produced due to some error, clicking the Abort button closes
this window.
Save As...
Copy the downloaded report(s) to a another directory (e.g. to a flash card) than defined before
in the Exports tab of the Run Report dialog. Select a directory in which the file(s) will be copied.
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm
Nur für den internen Gebrauch Step-By-Step Instructions
5 Step-By-Step Instructions
This section contains step-by-step instructions for executing COL operations.
COL Homepage and Navigation Tree, page 5-2
COL Administration tab sheet in System Management dialog in HiPath COL, page 5-13
Communication Parameter tab sheet in System Management dialog in HiPath COL, page 5-17
System Management dialog, Object List view in HiPath COL, page 5-18
Input Format Editor - Set Default Value, page 5-22
Input Format Editor - Configure Input Element, page 5-22
Start/Stop PM Collecting, page 5-22
Format Assignment/Format Change, page 5-23
Output Line Definition, page 5-24
Output Format Editor - Configure Output Element, page 5-28
Filter Editor - Set Default Value, page 5-30
Incorrect Records, page 5-38
Options, page 5-42
Logging, page 5-45
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm
Step-By-Step Instructions Nur für den internen Gebrauch

5.1 COL Homepage and Navigation Tree
Launching HiPath COL

The HiPath COL Homepage is launched in a browser by entering the IP address followed by
the COL alias, e.g. http://<IP-ADR>/COL or https://<IP-ADR>/COL. It can not be launched via
the HiPath 4000 Start Page/Desktop. The HiPath COL Homepage (.html) can be reached by
entering the COL URL in a web browser or by using a bookmark containing the HiPath COL
URL. Users can also create an icon on their desktop containing the COL URL link.
Launching HiPath 4000 Assistant/Manager Collecting Agent

The HiPath 4000 Assistant/Manager Collecting Agent Homepage can be launched via the Hi-
Path 4000 Start Page/Desktop.
COL Homepage
The COL Homepage contains:
● the Menu Bar containing the View, Action and Help options,
● the Toolbar,
● the COL Features and dialogs used to display and set COL parameters.
The Navigation Pane on the left-hand side of the COL Homepage shows the Application Tree.
The application tree is similar to a menu folder structure, displaying all COL functions in the
form of links the user can activate.
When a link in the navigation pane is selected with a single click, a short description of the se-
lected link will be displayed in the right-hand pane, called Content pane.
If Logging is selected, the Content pane will display the 3 different types of logs, and a View
and Delete button near each type, thus allowing the user to view or delete the desired log.
Double clicking on a link in the navigation pane launches the dialog of the corresponding COL
feature.
Launching COL Features via the COL Homepage

The individual COL features like setting up the input and output line format, and displaying the
collecting status or the output line status, can be started via the COL Homepage. As detailed
above, the COL Homepage itself is launched in a browser by entering the IP address followed
by the COL alias, e.g. http://<IP-ADR>/COL or https://<IP-ADR>/COL.
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm
Related Topics
Toolbar, page 3-10
Menu Bar, page 3-9
COL Features
An overview of the COL functionality can be found in HiPath COL / Collecting Agent – Over-
view, page 2-1 and in COL Features, page 3-21.
The Logging component is also part of HiPath COL because in HiPath 4000 Assistant/Man-
ager Logging is not available. A basic functionality is implemented and can be executed in Hi-
Path COL. Due to this reason the user interface is enhanced to display the logging messages.
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm

Description of User Actions

.
Action Description Next Form

Click on link/ Shows a short description of the currently selected item None.
feature in ap- from the application tree. If Controlling is selected, the
plication tree status displays Input Status: Active and Output Sta-
tus: Active and the toggle buttons Start/Stop Input
and Start/Stop Output are displayed in the content
pane on the right-hand side of the window.
Start/Stop In- Toggle button to start/stop collecting files from system Warning Box
put (applies to both AM and PM files). Visible only if Con-
trolling is selected in tree.
Start/Stop Out- Toggle button to start/stop producing output files (ap- Warning Box
put plies only to CDR files). Visible only if Controlling is se-
lected in tree.
Double-click Link to the dialog that shows collecting status for all Collecting status
on Collecting switches.
Status
Double-click Link to the dialog that shows status of output lines. Output Line Status
on Output
Line Status
Double-click Link to SysM System Manage-
on Definition ment
of Input Lines
Double-click Link to the dialog for administration of output lines. Output Line Defini-
on Definition tion
of Output
Lines
Double-click Link to the dialog for definition of input formats. Input Format Editor
on Input For-
mat Editor
Double-click Link to the dialog for definition of output formats. Output Format Edi-
on Output tor
Format Editor
Double-click Link to the dialog for definition of filters Filter Editor
on Filter Edi-
tor
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm

Double-click Opens the Translation Table Editor used to create, Translation Table
on Transla- add, modify and delete translation tables. Editor
tion Table Ed-
itor
Double-click Opens the Translation Group Editor used to create, Translation Group
on Transla- add, modify and delete translation group. Editor
tion Group
Editor
Double-click Link to the dialog to send the rejected CDRs back to the Incorrect Records
on Incorrect input.
Records
Double-click Link to Options dialog Options
on Options
Click on See Toolbar - Icon Descriptions and User Actions.
"?" (Help),
Home Page,
Start, Logoff
or Pin (Sticky
Page) icon in
Toolbar
Table 5-1 Description of actions performed on the COL Homepage
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm

Controlling
5.2 Controlling
Field Description Values Notes

Application The application tree is similar to a menu Read-only.
tree folder structure, displaying all COL fea-
tures in the form of links the user can
activate from the COL Homepage. The
Application Tree is displayed on the
left-hand side of the COL Homepage in
the Navigation Pane.
Description of A short description of the currently se- Strings are listed in Read-only.
the selected lected feature/link from the application Action table.
tree item. tree is displayed in the Content Pane on
the right-hand side of the Homepage. If
Controlling is selected in the tree, the
description will not be visible, and the
Content pane will show the status dis-
plays Input Status: Active and Output
Status: Active and the buttons Start/
Stop Input and Start/Stop Output.
Input Active Shows status of collecting files from Active/Not active Read-only
system (applies to both AM and PM
files). Visible only if Controlling is se-
lected in tree.
Output Active Shows status of producing output files Active/Not active Read-only
(applies only to CDR files). Visible only
if Controlling is selected in tree.
Table 5-2 Description of fields on the COL Homepage

.

plication tree status displays Input Status: Active and Output Status:
Active and the toggle buttons Start/Stop Input and
Start/Stop Output are displayed in the content pane on
the right-hand side of the window.
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm
Controlling

put (applies to both AM and PM files). Visible only if Control-
ling is selected in tree. Button caption is
Start/Stop Toggle button to start/stop producing output files (applies Warning Box
Output only to CDR files). Visible only if Controlling is selected
in tree.
Table 5-3 Description of actions on the COL Homepage
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm

Collecting Status
5.3 Collecting Status

Collect now Start immediate collecting for selected switches (multi- Warning-Box
ple selection possible).
Configure Configure collecting parameters for the selected switch SysM (COL tab
in SysM. sheet)
Refresh Refresh displayed data. None
First record Select first row None
Previous Select previous row None
record
Next record Select next row None
Last record Select last row None
Click on Print, See Toolbar - Icon Descriptions and User Actions.
"?" (Help),
Home Page,
Start, Logoff
or Pin (Sticky
Page) icon in
Toolbar
Table 5-4 Description of actions in the Collecting Status dialog.
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm
Output Line Status
5.4 Output Line Status

Configure Configure output line. Output Line Defini-
tion
Deliver Now Files in the selected output lines will be delivered imme- None
diately to the delivery directory.
Deliver all Files of all output lines will be delivered to the delivery None
Lines Now directory.
record
"?" (Help),
Home Page,
Start, Logoff
or Pin (Sticky
Page) icon in
Toolbar
Table 5-5 Description of actions in the Output Line Status dialog
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm

System Management in HiPath COL versus HiPath 4000 Assistant/Manager Collecting Agent
5.5 System Management in HiPath COL versus HiPath 4000

Assistant/Manager Collecting Agent
There are differences between setting up a system in HiPath COL on the one hand, and in
HiPath 4000 Assistant/Manager Collecting Agent on the other hand.
Double click the Definition of Input Lines link on the COL Homepage to launch
● the System Management application in HiPath 4000 Assistant/Manager
or
● the specific System Management tab sheet in HiPath COL.
Related Topics
Adding a System In HiPath COL System Management
Adding a System in HiPath 4000 Assistant/Manager System Management
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm
5.5.1 Adding a System In HiPath COL System Management

Double-click the Definition of Input Lines link on the HiPath COL Homepage to launch the
System Management tab sheet in HiPath COL. This tab sheet is specific to HiPath COL only.
While configuring a system it is important that the output format is mapped to an FTBL that has
been set up in the system. If a wrong format is chosen and mapped here, the input of charge
collecting data will fail. See also Output Line Definition and Output Format EditorIn HiPath COL
the communication parameters are maintained using the Communication Parameter tab
sheet. Please enter the required parameters for FAMOS and FTFTP into the corresponding
fields in this tab sheet. See also Definition of Input Lines.
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm

5.5.2 Adding a System in HiPath 4000 Assistant/Manager System

Management
As described in System Management in HiPath COL versus HiPath 4000 Assistant/Manager
Collecting Agent on page 5-10 and in Output Line Definition on page 5-24 the System Man-
agement application used for setting up a system is launched by double clicking the Definition
of Input Lines feature link on the COL Homepage. The Collecting Agent check box in Sys-
tem Management has to be enabled to get the required dialog displayed. In this configuration
example the charge collecting data for AM and PM is collected in CDR_UV1.0. The communi-
cation parameters will be set up directly in System Management.
Please refer to the System Management Online Help for more information and for detailed
field descriptions.
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm
COL Administration tab sheet in System Management dialog in HiPath COL
5.6 COL Administration tab sheet in System Management dialog in

HiPath COL
The following table describes the COL Administration tab sheet in the System Management
dialog in HiPath COL. This tab sheet includes the COL administration and scheduling param-
eters.

System ID System name / retrieved system String (char 4)
Description Description of system ID String (char 40)
System Type Types of supported systems String (char 8) H300 (OpenFT)
H300 HDMS (FTP)
HDMS H150-Lan (passiv/
H150-LAN TFTP)
H150-BAC H150-BackupPC
H150-ALL (FTP)
H150-COM H150-AllServe (FTP)
H5000 H150-ComboX
(FTP)
H5000 (FTP)
System Ver- Version of the system String (char 5) Version depends on
sion H300 = V3.4, EV1.0, system type
EV2.0,
EV3.0, (+UV1.0)
HDMS = V3.6
H150-LAN = V1.0.
V1.2
H150-BackupPC =
V1.x
H150-ComboX =
V1.0, V1.2
H5000 = V3.0
IP Address IP Adress of the retrieved sys- String (char 32) IP Address is also
tem (Mask needed from H150-
___.___.___.___ ?) Lan because of the
mapping from H150-
BackupPC.
Tab Sheet COL Administration
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm


Input Format Combo box with the list of all in- List of all input for- Disabled for H150-
put formats mats BackupPC
Format of H150-
BakkupPC:
the mapping to sys-
tem ID is done by IP
Address
Collect AM Check-box to activate AM col- Checked/not
Data lecting checked
Generating 3 numeric entry fields for the Values: 1 to 9 Field lengths: 3,3,2;
Node Number node number Mask: 111-111-11
Collect PM Da- Check-box to activate PM col- (*) Only supported in
ta(*) lecting HiPath 4000 Collect-
ing Agent
File/Directory Radio buttons to choose input of File or Directory Depending on Sys-
CDR Source from file or directo- tem Type
ry H300 = File
HDMS = File
H150-Lan = Directo-
ry
H150-BackupPC =
Directory
H150-AllServe = File
H150-ComboX = File
H5000 = Directory
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm

File/Directory Name of the file/directory where String Default:
Name data is collected from H300 = FTFILE
HDMS = GCDATA
H150-BackupPC = ../
<FTP-Collect-Dir>
H150-AllServe = ../
GCALLSERV
H150-ComboX = FT-
FILE
H5000 =
<inst_path>/H5000/
cfg/cdr/
CDRReport_<date>
_<time>.txt or
CDRReport_<date>
_<time>_seq_numb
er>
<date> = YYYYM-
MDD
<time> = HHMMSS
<seq_number> =
{1,2,...}
Number of Re- Number of retries for data trans- Integer Default: 3.
tries fer
Retry Time Retry time in minutes for data Integer Default: 15 min.
transfer
Start Date Start date for collecting Date Default: today
Start Time Start time for collecting Time in format Default: current time
“hh:mm”
Cycle Radio-buttons to choose hours Hours or Minutes Default: hours
or minutes
Hours Combo-box with hours 1,2,3,4,6,8,12,24 Enabled only if Cycle
= Hours, not manda-
tory. Default: 1
Minutes Combo-box with minutes 1,2,3,4,5,6,10,12,15, Enabled only if Cycle
30 = Minutes, not man-
datory. Default: 15.
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm


Communica- Tab Sheet Disabled for H150-
tion Parameter Lan
Tab Sheet
see below see below
Table 5-6 COL Administration tab sheet in System Management dialog in HiPath
COL, field descriptions
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm
Communication Parameter tab sheet in System Management dialog in HiPath COL
5.7 Communication Parameter tab sheet in System Management

dialog in HiPath COL
.

(new) (size un-
changed)
User Name User name for famos session String (char 8) Only for H300
(Group Famos)
Password Password for User name (famos String (char 8) Only for H300
(Group Famos) session)
TSAP SRC Transport name for source String (char 8) Only for H300
(Group Famos)
TSAP DST Transport name for destination String (char 8) Only for H300
(Group Famos)
User Name User name for FTP/OpenFT ses- String (char 8)
(Group FTP/ sion
OpenFT)
Password Password for User name (FTP/ String (char 8)
(Group FTP/ OpenFT session)
OpenFT)
(Group FTP/
OpenFT)
(Group FTP/
OpenFT)
Table 5-7 Communication Parameter tab sheet in System Management dialog in Hi-
Path COL, field descriptions
Buttons:
Field Description Values

Save Save changes to the database Error message for
wrong values
New Create a new object and switch to New Object None
Delete Delete selected object (only in list view) Warning box
Table 5-8 System Management dialog in HiPath COL, button descriptions
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm

System Management dialog, Object List view in HiPath COL
5.8 System Management dialog, Object List view in HiPath COL

System ID System name / retrieved system String (char 4) Read-only
Description Description of system-ID String (char 32) Read-only
IP Address IP-Adress of the retrieved system String Read-only
Table 5-9 System Management dialog, Object List view in HiPath COL, field descrip-
tions
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm
Input Format Editor
5.9 Input Format Editor
Setting Up Input Formats

Use the Input Format Editor link on the COL Homepage to set up the COL input format. On
the right-hand side of the dialog, beneath the Input label, you will see the list of charge collect-
ing elements used in the input format (FTBL). The names of the charge collecting elements are
not system version-dependent. The element names (see Name column) are the identifiers for
the charge collecting elements used again in the output format. The names are chosen in de-
pendence on HiPath 4000 (or HiPath 4000 respectively). The mapping of a format to a specific
system is done using COL System Management.
For AM/PM (AM...) pre-defined formats have been set up. Moreover, one format (CDR...) cov-
ering all charge elements has been set up for each system version.
The newly created or pre-defined input format will then be used to automatically create the cor-
responding FTBL of the selected system version during the storage process. The FTBL AMO
batches are created in both English and German. The files are stored at the location indicated
in the FTBL path under Options (reachable via the COL Homepage), e.g. AM_UV2.0_S.GE
(German) or AM_UV2.0_S.EN (English).
You can use an existing format as a template for creating a new format by copying
> the existing format to the clipboard using the Copy feature in the Object menu.
The basic prerequisite is that all elements needed in the output format are specified
> in the input format creation process. It is also possible to create more than one out-
put format from one input.
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm

Input Format Editor

Double click in Edit default value for the selected element Set Default Value
the Default el- dialog.
ement table
Double click in Edit properties for the selected element Configure Input El-
the Input ele- ement dialog.
ment table
< Move selected element from the default table to the ele- None.
ment table. Position numbers are automatically adjust-
ed. Button is enabled according to system type.
> Move selected element from the element table to default None.
table. Position numbers are automatically adjusted. But-
ton is enabled according to system versions.
Up Move up selected element in the element table. Position None.
numbers are automatically adjusted.
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm
Input Format Editor

Down Move down selected element in the element table. Posi- None.
tion numbers are automatically adjusted.
Save Save changes to the database. Before saving the format Error message for
is tested (mandatory elements) and FTPL file is gener- wrong format
ated. Enabled only in object view.
New Create a new object and switch to New Object. None.
Delete Delete selected object. Enabled only in list view. Warning box
Add fixed text Add fixed text to input. None.
First record Show first format from the database None
Previous Show previous format from the database None
record
Next record Show next format from the database None
Last record Show last format from the database None
"?" (Help),
Home Page,
Start, Logoff
or Pin (Sticky
Page) icon in
Toolbar
Object Change to object view Same form in object
view
New Object Open new format in object view Same form in object
view
Object List Change to list view. Same form in list
view
Table 5-10 Input Format Editor dialog, action descriptions
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm

5.10 Input Format Editor - Set Default Value

OK Accept values and close dialog Input Format Editor
Cancel Close without accepting values Input Format Editor
Table 5-11 Set Default Value dialog, action descriptions
5.11 Input Format Editor - Configure Input Element

Table 5-12 Configure Input Element dialog, action descriptions
5.12 Start/Stop PM Collecting

When PM collecting from some switch is started/stopped, it is necessary to ensure that the ap-
propriate format has already been assigned to the switch. Therefore, starting/stopping PM col-
lecting should be carried out with great care and attention. When PM collecting is started, the
assigned input format is checked and, if mandatory PM fields are not included in the format, an
error message is displayed.
Necessary steps for assigning/changing a format are described in Format Assignment/Format
Change.
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm
Format Assignment/Format Change
5.13 Format Assignment/Format Change

Before a different format is assigned to an input line (switch) or the current format is modified,
it is necessary to ensure that no data in old format exists in the COL system. Therefore, chang-
ing/assigning formats should be carried out with great care and attention.
When an existing format is modified, the following step should be carried out:
● Input format - change old format and save changes. When the changes are saved, the
FTBL file for the new format will be automatically generated.
When a different format is assigned to a switch, the following steps should be carried out:
● HiPath 4000 Expert Access - Stop CDR creation on HiPath, if possible
● Input status - Execute “Collect Now”
● SysM - deactivate collecting for the switch
● Input status - wait until all data is processed into standard format
● SysM - Assign new format to the switch
● HiPath 4000 Expert Access - Send FTBL to system
● SysM - Start collecting for system
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm

5.14 Output Line Definition

For each output file an output line has to be set up. The COL feature for the definition of output
lines is launched by double-clicking the Definition of Output Lines link on the COL Homep-
age. Each output line must have a specific output format assigned to it. You can create and edit
output formats using the Output Format Editor. If you want all charge collecting data to be writ-
ten to the output line, you have to select the Default Filter setting in the Filter dropdown list.
In HiPath COL, however, it is necessary to create one separate output line for each system
type, i.e. for H300, H150 (AllServe, H150 LAN), and H5000. For these lines, pre-defined for-
mats and filters are provided. In case of standard configurations with HiPath AM these formats
and filters should not be modified.

New Add new output line None.
Delete Delete selected output line (enabled only in object list) Warning Box.
New Create a new object and switch to new object. None.
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm

Save Save values (enabled only in Object view). None.
Active Activate/deactivate selected input line Warning Box
First record Show first filter from the database None
Previous Show previous filter from the database None
record
Next record Show next filter from the database None
Last record Show last filter from the database None
view
New Object Open new filter in object view Same form in object
view
Object List Change to list view. Same form in list
view
"?" (Help),
Home Page,
Start, Logoff
or Pin (Sticky
Page) icon in
Toolbar
Table 5-13 Output Line Definition dialog, action descriptions
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm

5.15 Output Format Editor
Setting Up Output Formats

The Output Format Editor is launched by double-clicking on the the Output Format Editor link
on the COL Homepage. The Output Format Editor is used to set up the output formats. The
Output table on the right-hand side of the screen displays the charge collecting elements used
in the output format. The names are identical to the ones of the charge collecting elements used
in the input (see System Management in HiPath COL versus HiPath 4000 Assistant/Manager
Collecting Agent on page 5-10). Multiple instances of one charge collecting element can be
written into the output file. It is also possible to insert text and CM elements into the output file.
The format mapping is done in the output line.
For H150, H300 and H5000 pre-defined formats have been set up.
You can use an existing format as a template for creating a new format by copying
> the existing format to the clipboard using the Copy feature in the Object menu.
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm

> Copy selected element from the standard element None
list to the output table. Selected element is not delet-
ed from the original table. Position numbers are au-
tomatically adjusted.
< Delete selected element from the output element ta- None
ble. Position numbers are automatically adjusted.
Double click in Edit properties for the selected element Configure Output Ele-
Output table ment dialog.
Up Move up selected element in the output element ta- None
Down Move down selected element in the output element None
table. Position numbers are automatically adjusted.
Save Save changes to the database. Enabled only in ob- None
ject view.
Delete Delete selected object. Enabled only in list view. Warning Box
record
Click on Print, See Toolbar - Icon Descriptions and User Ac-
"?" (Help), tions.
Home Page,
Start, Logoff
or Pin (Sticky
Page) icon in
Toolbar
view
New Object Open new format in object view Same form in object
view
Object List Change to list view. Same form in list view
Table 5-14 Output Format Editor dialog, description of actions
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm

Output Format Editor - Configure Output Element
5.16 Output Format Editor - Configure Output Element

OK Accept values and close dialog Output Format Edi-
tor
Cancel Close without accepting values Output Format Edi-
tor
Table 5-15 Configure Output Element dialog, description of actions
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm
Filter Editor
5.17 Filter Editor

Double-click in Modify selected row from the filter table. Set Default Value
the Filter dialog.
Clause table
> Copy selected element from the element table to the fil- None
ter table. Position numbers are adjusted automatically.
< Delete selected element from the filter table. Position None
numbers are adjusted automatically.
Save Save changes to the database. Enabled only in object None
view.
record
"?" (Help),
Home Page,
Start, Logoff
or Pin (Sticky
Page) icon in
Toolbar
Object Change to object view. Same form in Ob-
ject view.
New Object Open new filter in object view. Same form in Ob-
ject view.
Object List Change to list view. Same form in Ob-
ject List view.
Table 5-16 Filter Editor dialog, description of actions
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm

5.18 Filter Editor - Set Default Value

OK Accept values and close dialog Filter Editor
Cancel Close without accepting values Filter Editor
Table 5-17 Set Default Value dialog, description of actions
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm
Translation Tables
5.19 Translation Tables

Click on Short description of selected element is displayed. None.
Translation Description: “Double-click on link to open page for ad-
Table Editor ministration of translation tables”.
link.
Click on Short description of selected element is displayed. None.
Translation Description: “Double-click on link to open page for ad-
Group Edi- ministration of translation groups”.
tor link.
Double-click Link to Translation Table Editor used for adding, edit- Translation Table Edi-
on Transla- ing and deleting translation tables. tor
tion Table Ed-
itor link.
Double-click Link to Translation Group Editor used for adding, edit- Translation Group
on Transla- ing and deleting translation groups. Editor
tion Group
Editor link.
Table 5-18 Translation Tables link on Homepage of Collecting Agent/HiPath COL, de-
scription of actions
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm

Translation Tables
5.19.1 Translation Table Editor

Add new row Add new row to the translation table. New empty row None.
(icon) is inserted below the currently selected row. Cursor is
positioned to the In Value field in the new row. The se-
quential number of the new row is automatically gen-
erated. Sequential numbers are updated for all rows
below the new row. Changes are not saved to the da-
tabase. Only in Object and New Object view.
Delete row Delete selected row from the translation table. The se- None.
(icon) quential number of the new row is automatically gen-
tabase. Only in Object and New Object view.
New Create new object and switch to this object. None.
Copy Copy the current object to the clipboard. None.
Insert Insert the previously copied object from the clipboard None.
into the current view.
Save Save changes to the database. An error message is is-
This button is only enabled in the Object view. sued if wrong or illegal
values are entered.
Delete Delete the selected object. A warning message is
This button is only enabled in the Object List view. issued before irrevers-
ible deletion.
Homepage Goes back to the Homepage of HiPath COL or Col- Homepage of HiPath
lecting Agent, respectively. Same function as the COL or Collecting
Homepage icon in the Toolbar. Agent, respectively.
Start Jumps back to the HiPath 4000 Assistant/Manager Start Page of HiPath
Start Page. 4000 Assistant/Man-
Opens a new browser window and displays the HiPath ager.
4000 Assistant/Manager Start Page.
Same function as the Start(*) option in the Toolbar.*
This feature is only supported in HiPath 4000 Assis-
tant/Manager.
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm
Translation Tables

Object Change to Object view. Same form in Object
view.
New Objekt Open new form in Object view. Same form in Object
view.
Object List Change to Object List view. Same form in Object
List view.
First Record Show first record from database. Not displayed in None.
New Object view.
Previous Show previous record from database. Not displayed in None.
Record New Object view.
Next Record Show next record from database. Not displayed in None.
New Object view.
Last Record Show last record from database. Not displayed in New None.
Object view.
Refresh Reload data from database and refresh the display. None.
Pin Check box for turning on and off the Sticky Page None.
mode. Defines whether a new browser page is
opened in the same window or in a new window.
● OFF (default): a new applet will be launched in the
currently opened browser window.
● ON: a new applet will be launched in a new brows-
er window.
Same function as the Sticky Page option in the View
menu.
Logoff When you click the Logoff icon in the toolbar, a mes- Warning message,
sage dialog is displayed, warning you that all unsaved then logon screen.
data will be lost, prompting you to save all unsaved
data from the current session and to confirm with OK
that you want to log off.
After logging off the program returns to the Logon
screen.
Same function as the Logoff option in the Action
menu.
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm

Translation Tables

Context Help Activates the Context Help. The mouse pointer is dis- None.
played as an arrow with an adjacent question mark.
When you click on an element in your browser window
with this pointer, the corresponding context-specific
Help topic will be displayed in a separate Help browser
window. You can also activate the Context Help by
pointing and clicking on a specific location in the user
interface and pressing CTRL+F1.
Same functionality as the Context Help option in Help
menu.
Help Topics Show the Help topics. Help topics are dis-
played in new window.
Info Shows the software version and the copyright data of Info box is displayed in
the application. new dialog.
Table 5-19 Translation Table Editor, description of actions
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm
Translation Tables
5.19.2 Translation Group Editor

> Add selected table from list of available tables to trans- None.
lation group. The selected table is removed from the
list of available tables. The changes are not saved to
the database.
< Delete selected row (translation table) from translation None.
group and move translation table to list of available ta-
bles. The changes are not saved to the database.
values are entered.
ible deletion.
tant/Manager.
view.
New Object Open new form in Object view. Same form in Object
view.
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm

Translation Tables

List view.
New Object view.
New Object view.
Object view.
er window.
menu.
screen.
menu.
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm
Translation Tables

menu.
Table 5-20 Translation Group Editor, description of actions
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm

Incorrect Records
5.20 Incorrect Records

In general, CDRs are rejected if a mismatch is detected between the received CDRs and the
assigned input format. A list of all rejected CDRs is displayed using the Incorrect Records di-
alog (see Incorrect Records - Send Back To Input).
The following error situations are possible:
● The assigned format is wrong.
● The format setup in system is wrong.
Before a CDR can be processed again, the associated error file and the input format must
match. In order to achieve this, either the error file must be corrected on the server using a stan-
dard ASCII editor or the input format must be changed. Afterwards the rejected CDR can be
sent back to the input using the Send Back To Input button in this dialog (see Incorrect
Records - Send Back To Input). Single CDR files can be selected and transferred to the CDR
Viewer to be viewed in detail, printed or exported.

Send Back to Send selected file back to input. If the input format is None
Input correct and the file can be processed, it will automatical-
ly be deleted afterwards. In order to view the latest data,
press the Refresh button or restart the window.
Delete Delete selected file None
Refresh Refresh displayed data. None.
View CDR files Display details of a selected CDR file. CDR Viewer
record
"?" (Help),
Home Page,
Start, Logoff
or Pin (Sticky
Page) icon in
Toolbar
Table 5-21 Description of actions in the Incorrect Records dialog
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm

Using the Saved CDR files in BackUp dialog, a list of all available saved CDRs from the serv-
er’s backup directory is displayed (see Saved CDRs in Backup File).
Selected CDR files can be deleted or sent back to the input.
Single CDR files can be selected and transferred to the CDR Viewer to be viewed in detail,
printed or exported.

Send Back to Send selected file back to input - multiple selection is None
Input possible.
If the input format is correct and the file can be pro-
cessed. In order to view the latest data, press the Re-
fresh button or restart the window.
Delete Delete selected file - multiple selection is possible. None
record
"?" (Help),
Home Page,
Start, Logoff
or Pin (Sticky
Page) icon in
Toolbar
Table 5-22 Description of actions in the Saved CDR files in BackUp dialog
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm


Using the Files Ready for Output Lines dialog, a list of all available CDRs from the manager’s
delivery directories is displayed (see Files Ready for Output Lines).
Selected CDR files can be deleted.
Single CDR files can be selected and transferred to the CDR Viewer to be viewed in detail,
printed or exported.

Delete Delete selected file - multiple selection is possible. None
record
"?" (Help),
Home Page,
Start, Logoff
or Pin (Sticky
Page) icon in
Toolbar
Table 5-23 Description of actions in the Files Ready for Output Lines dialog
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm
CDR Viewer
5.23 CDR Viewer

The CDR Viewer dialog opens by clicking the View CDRs button from pages Incorrect
Records, Saved CDR files in Backup or Files Ready for Output Lines.
The CDR file is displayed either in a valid or in an undifined format.

Define Format Select format for displayed file - Refresh displayed data. None.
Export/Print Export the displayed file in standard MS Excel format. None.
Display all Refresh displayed data - toggle all CDRs/first 20 CDRs CDR Viewer
DCRs
"?" (Help),
Home Page,
Start, Logoff
or Pin (Sticky
Page) icon in
Toolbar
Table 5-24 Description of actions in the Files Ready for Output Lines dialog
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm

Options
5.24 Options
Only authorised users having “rsca” access rights are allowed to change and save values in
the Options dialog.

Select tab sheet Activate/deactivate functions and enter values. Select tab sheet
Save Save values. Enabled only for “rsca” user. Warning box.
"?" (Help),
Home Page,
Start, Logoff or
Pin (Sticky
Page) icon in
Toolbar
Table 5-25 Description of actions in the Options dialog.
Path tab
● Input Path
● Transform Path
● Output Path (internal)
● AM Deliver Path
● PM Deliver Path
● Path of Incorrect Records
● FTBL Path
● Trunk Group Metering Path
Settings tab
● Required Free Space
● Retention Period for CM History Data ... Day(s)
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm
Options
● Activate fast mode for transformation of virtual to physical node number only for the
PM output line (check box)
● Activate/Deactivate Automatic Delecte of Logging Entries in COL (check box)
● Retention Period for Logging Entries ... Day(s)
● Retention Period for Trunk Group Data from the Cyclic Check of the B Channels ...
Day(s)
● Save Input Files (CDRs)
● Retention Period for AC Configuration Data ... Day(s)
● Send email notification if free space/collection thresholds exceeds
● Select email recipients
● Activate/Deactivate automatic Cleanup
● Retention Period for "File Transfer" (receive) Process Monitor
Process Controlling tab

● Number of Receive (CDR collecting) Processes
● Number of Transform (CDR standardisation) Processes
● Number of Line (CDR output) Processes
● Number of Metering Processes
● Number of TG-Check (Cyclic check of Trunk Groups) Processes
● Schedule Incorporation of CDR Processing Active
● Start Time
● Stop Time
● Retention Period for "File Transfer" (receive) Process Monitor
● Send email notification if free space/collection thresholds exceeds
● Select email recipients
Button
Save (button)
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm

Options
Related Topics
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm
Logging
5.25 Logging
Field and Controls Descriptions in the Logging Page

Log Type:
● Receive Log
● Output Log
System ID
To: (Date: / Time:)
View (button)
Delete (button)
Field and Controls Descriptions in the Logging Events Table

Date Displays the date and time when the log Column;
message was issued. Read-only
Category Indicates the category of the logged ac- Column;
tivity, e.g. "start application" or "exit ap- Read-only
plication".
System ID The ID of the network node (switch) that String Also referred
is being logged and issued the log mes- as
sage. $COL_TRANS
FORM
Error Error code Also referred
as
$COL_INPUT
Short mes- Displays a short description of the Column;
sage logged activity or error, e.g. "COL pro- Read-only
cess dbproxy started."
Long message Displays a more detailled description of Column;
the logged activity or error, e.g. "COL Read-only
process dbproxy started."
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_Steps.fm

Logging

Severity Indicates the severity of the log mes- 0 indicates lowest Column;
sage. severity. Read-only
Print/Export Opens Run Report dialog to define var- Button
ious log output formats for Exporting
Log Reports and send log files as e-mail
attachment.
Table 5-26 Description of fields in the Logging dialog

● Logging Type
● Logging Period
● Date (column)
● Error (column)
Print/Export (Button)
Related Topics
Logging Report - Field Descriptions, page 6-47
A31003-H3460-M104-4-76A9, July 2012

HiPath_COL_References.fm
Nur für den internen Gebrauch Reference Material
6 Reference Material
Toolbar - Icon Descriptions and User Actions
Field Descriptions and User Actions
Elements for Defining Input and Output Formats for COL CDRs
Pre-defined Formats for Output Format Definition (likewise for H3000 and H2000 systems):
– H4000_HP_AM – Output format from HiPath 4000 for HiPath AM
– HiPath 4000 Manager/Assistant PM – Output format for HiPath 4000 Manager/As-
sistant PM V1.0
– H4000_HPAM_E164 – Output format from HiPath 4000 for HiPath AM
– H8000_AM – OpenScape Voice Output Format V1.0
– H8000_AM_V22 – OpenScape Voice Output Format V2.2 (Single System)
– OSV_AM – Open Scape Voice Output Format
– HP4M_AMPM_UV3.0 – Output format from HiPath 4000 V3 for HiPath 4000 V6
– HP4M_AMPM_UV6 – Output format from HiPath 4000 V6
– HP4M_PM_UV6 – Output format from HiPath 4000 V6
A31003-H3460-M104-4-76A9, July 2012

Reference Material Nur für den internen Gebrauch
● Pre-defined Formats for Input Format Definition (likewise for H3000 and H2000 systems)
– AMPM_UV1.0 - Input format for AM / PM HiPath 4000
– AllServe - Input format for HiPath AllServe 150 V1.0 (Element Manager)
– H5000_V30 - Input format for HiPath 5000 V3.0 (Single System)
– H8000_V22 – OpenScape Voice Input Format V2.2 (single PABX)
– AMPM_UV6 - Input format for AM/PM HiPath 4000
– PM_UV6 - Input format for HiPath 4000
● Additional CM Elements for Defining CDR Output Formats
– CM Elements Used for Generating History Output
– CM Elements Used for Transforming Virtual to Physical Node Numbers
– Loading the col_port and col_switch Tables
A31003-H3460-M104-4-76A9, July 2012

6.1 Field Descriptions and User Actions

Menu Bar - Description of the Menu Options, page 6-4
Toolbar - Icon Descriptions and User Actions, page 6-7
COL Homepage - Field Descriptions and User Actions, page 6-9
Collecting Status - Field Descriptions and User Actions, page 6-12
Output Line Status - Field Descriptions and User Actions, page 6-14
COL Administration tab sheet, System Management dialog in HiPath COL - Field Des-
criptions, page 6-15
Descriptions and User Actions, page 6-19
Object List view, System Management dialog in HiPath COL - Field Descriptions, page 6-
20
Input Format Editor - Object List - Field Descriptions, page 6-24
Input Format Editor - Set Default Value - Field Descriptions and User Actions, page 6-24
Input Format Editor - Configure Input Element - Field Descriptions and User Actions,
page 6-25
Output Line Definition - Object View - Field Descriptions and User Actions, page 6-25
Output Line Definition - Object List - Field Descriptions, page 6-27
Output Format Editor - Object View - Field Descriptions and User Actions, page 6-28
Output Format Editor - Object List - Field Descriptions, page 6-31
Output Format Editor - Configure Output Element - Field Descriptions and User Actions,
page 6-31
Filter Editor - Object View - Field Descriptions and User Actions, page 6-32
Filter Editor - Object List - Field Descriptions, page 6-34
Filter Editor - Set Default Value - Field Descriptions and User Actions, page 6-34
Translation Table Editor -- Field Descriptions and User Actions, page 6-36
Translation Group Editor -- Field Descriptions and User Actions, page 6-40
Incorrect Records - Send Back To Input - Field Descriptions and User Actions, page 6-44
A31003-H3460-M104-4-76A9, July 2012


Logging Report - Field Descriptions, page 6-47

Depending on the functionality of the COL feature selected, different or only specific menu op-
tions may be displayed in the menus.
Top Level Second Level Description

Menu Menu
Object The Object menu contains the options for creating and edit-
ing network objects, e.g. New, Copy, Insert, Save, Delete
and Print Report.
Object Start/Stop In- Toggle button used to start/stop the call charge data input.
put Same function as Start/Stop Input button. Only available in
Controlling dialog.
Object Start/Stop Toggle button used to start/stop the creation of output files
Output (only CDR files). Same function as Start/Stop Output button.
Only available in Controlling dialog.
Object Collect Now Immediately starts the recording of CDRs. The operation is
carried out in asynchronous mode. Processing of several
lines (data records) at a time is supported.
Same function as Collect Now (button).
Object Configure Configure input line. In the Collecting Agent under HiPath
4000 Assistant/Manager, clicking this button will launch the
System Management application. In HiPath COL, clicking
this button will launch the COL-specific tab sheet System
Management. Only one line at a time can be selected and
configured. Same function as Configure (button).
Table 6-1 Menu Bar - Description of Menu Options
A31003-H3460-M104-4-76A9, July 2012


Menu Menu
Object Print Report The current screen content is written to an HTML file and dis-
played in a separate browser window. This separate browser
window contains a Print icon of its own. If you click on this
icon, the currently displayed content of the separate browser
window is sent to the configured printer.
Same function as the Print icon in the toolbar.
* Printing is only supported by the Collecting Agent in Hi-
Path 4000 Assistant/Manager. The Print icon is not dis-
played on the Homepage of the Collecting Agent; the icon
is only displayed in some dialogs supporting the Print fea-
ture, e.g. Collecting Status and Output Line Status.
* Printing is only supported using the Print button from the
separate browser window.
* Activating the Definition of Input Lines feature will launch
the System Management application (in the Collecting
Agent) or the System Management tab sheet (in HiPath
COL), respectively. Clicking the Print icon in the System
Management toolbar activates the Report Generator.
Object New Use this option to create a new object. The view switches to
New Object. After entering the required parameters you
need to save the new object in order to store its configura-
tions settings.
Same function as New (Button).
Object Copy Use this option to copy existing input and output formats to
the clipboard and to paste the existing format parameters into
new formats using Insert, thus creating new formats.
Object Insert Use this option to paste the formats or settings previously
copied (using Copy) to the clipboard into the new formats.
Object Save Use this option to store changed or new configuration set-
tings of objects and formats to the database.
Object Delete Use this option to delete the selected format or object, re-
spectively, from the displayed list. The selected format/object
is only deleted from the list view, not from the database. For
most COL features, this option is only available in the Object
List view in order to avoid accidental deletion of formats or
objects.
Table 6-1 Menu Bar - Description of Menu Options (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012



Menu Menu
Object Save Input Use this check box to enable/disable the saving of input files.
Files (CDRs) This option is only available in the Options dialog.
See detailed description in Save Input Files (CDRs).
View
View Home Goes back to the Homepage of HiPath COL/Collecting
Agent..
Same function as the Homepage icon in the Toolbar.
View Start Jumps back to the HiPath 4000 Assistant/Manager Start
Page.
Opens a new browser window and displays the HiPath 4000
Assistant/Manager Start Page.
Same function as the Start(*) icon in the Toolbar.
* This feature is only supported in HiPath 4000 Assistant/
Manager.
View Object Use the Object menu option to change to the Object view
used to display the configuration settings of a single selected
object. With most of the COL features you can switch be-
tween the Object List, Object and New Object view by ei-
ther selecting the respective option in the View menu or by
clicking the corresponding radio button beneath the menu
bar.
Same function as the Object radio button beneath the menu
bar.
View Object List Use the Object List menu option to change to the Object
List view. This is the default view with most COL features. It
displays the list of all configured network objects. The Object
List cannot be edited and contains only general information
about the displayed objects. With most of the COL features
you can switch between the Object List, Object and New
Object view by either selecting the respective option in the
View menu or by clicking the corresponding radio button be-
neath the menu bar.
Same function as the Object List radio button beneath the
menu bar.
View Go To Use the First Object, Previous Object, Next Object and
Last Object menu options in the Go To menu to navigate to
the respective object in the line of configured network objects.
A31003-H3460-M104-4-76A9, July 2012


Menu Menu
View Refresh Use this option to upload the current data from the database
and to refresh the contents of the screen.
Same function as Refresh (button).
View Sticky Page The Sticky Page (Pin) option in the View menu switches the
sticky page mode ON or OFF.
● OFF (default): a new applet will be launched in the cur-
rently opened browser window.
● ON: a new applet will be launched in a new browser win-
dow.
Same function as the Pin (Sticky Page) icon in the Toolbar.
Action
Action Logoff When you click the Logoff option in the Action menu, a mes-
sage dialog is displayed, warning you that all unsaved data
will be lost, prompting you to save all unsaved data from the
current session, and to confirm with OK that you want to log
off.
After logging off the program returns to the Logon screen.
Same function as the Logoff icon in the Toolbar.
Help
Help Context Help Use this menu option to activate the Context Help. The
mouse pointer is displayed as an arrow with an adjacent
question mark. When you click on an element in your browser
window with this pointer, the corresponding context-specific
Help topic will be displayed in a separate Help browser win-
dow. You can also activate the Context Help by pointing and
clicking on a specific location in the user interface and press-
ing CTRL+F1.
Same functionality as the ? (Help) icon in the Toolbar.
Help Help Topics Use the Help Topics option to open the Online Help Table of
Contents. You can also invoke the Online Help Table of Con-
tents by pressing the F1 key.
Help About Use the About option to display information about the pro-
gram software version, the release date, and the copyright
provisions.
Toolbar - Icon Descriptions and User Actions

A31003-H3460-M104-4-76A9, July 2012

Print(*) * Printing is only supported using the Print button from None (or modal print
the separate browser window. dialog)
The current screen content is written to an HTML file
Click on Print and displayed in a separate browser window. This sep-
toolbar icon(*) arate browser window contains a Print icon of its own.
If you click on this icon, the currently displayed content
of the separate browser window is sent to the config-
ured printer.
Same function as the Print Report option in the Object
menu.
* Printing is only supported by the Collecting Agent in
HiPath 4000 Assistant/Manager. The Print icon is not
displayed on the Homepage of the Collecting Agent;
the icon is only displayed in some dialogs supporting
the Print feature, e.g. Collecting Status and Output
Line Status.
* Printing is only supported using the Print button from
the separate browser window.
* Activating the Definition of Input Lines feature will
launch the System Management application (in the
Collecting Agent) or the System Management tab
sheet (in HiPath COL), respectively. Clicking the Print
icon in the System Management toolbar activates the
Report Generator.
Help Activates the Context Help. The mouse pointer is dis- Online Help browser
Click on ? with this pointer, the corresponding context-specific
(Help) tool- Help topic will be displayed in a separate Help browser
bar icon window. You can also activate the Context Help by
pointing and clicking on a specific location in the user in-
terface and pressing CTRL+F1.
menu.
Home Goes back to the Homepage of HiPath COL/Collect- Homepage of Hi-
Page ing Agent. Path COL / Collect-
Same function as the Home option in the View menu. ing Agent
Click on
Home Page
toolbar icon
Table 6-2 Toolbar - Icon descriptions and user actions
A31003-H3460-M104-4-76A9, July 2012

(*) Start Page. 4000 Assistant/Man-
Opens a new browser window and displays the HiPath ager
Click on Start Same function as the Start option in the View menu.
toolbar icon(*) * This feature is only supported in HiPath 4000 Assis-
tant/Manager.
Logoff When you click the Logoff icon in the toolbar, a mes- Logon screen of Hi-
sage dialog is displayed, warning you that all unsaved Path 4000 Assistant/
data will be lost, prompting you to save all unsaved data Manager
from the current session and to confirm with OK that
Click on you want to log off.
Logoff After logging off the program returns to the Logon
toolbar icon screen.
menu.
Pin Clicking on the Pin pushbutton switches the sticky page None
(Sticky mode ON or OFF.
Page)
Click on Pin ● OFF (default): a new applet will be launched in the
toolbar icon currently opened browser window.
● ON: a new applet will be launched in a new browser
window.
menu.
Table 6-2 Toolbar - Icon descriptions and user actions (Fortsetzung)
COL Homepage - Field Descriptions and User Actions

Application The application tree is similar to a Read-only.
tree menu folder structure, displaying all
COL features in the form of links the
user can activate from the COL
Homepage. The Application Tree is
displayed on the left-hand side of the
COL Homepage in the Navigation
Pane.
Table 6-3 Description of fields on the COL Homepage
A31003-H3460-M104-4-76A9, July 2012



Description of A short description of the currently se- Read-only.
the selected lected feature/link from the applica-
tree item. tion tree is displayed in the Content
Pane on the right-hand side of the
Homepage. If Controlling is selected
in the tree, the description will not be
visible, and the Content pane will
show the status displays Input Sta-
tus: Active and Output Status: Ac-
tive and the buttons Start/Stop Input
and Start/Stop Output.
Input Status: Shows status of collecting files from Active/Not active Read-only
Active system (applies to both AM and PM
files). Visible only if Controlling is se-
lected in tree.
Output Status: Shows status of producing output files Active/Not active Read-only
Active (applies only to CDR files). Visible
only if Controlling is selected in tree.
Table 6-3 Description of fields on the COL Homepage (Fortsetzung)

plication tree status displays Input Status: Active and Output Sta-
tus: Active and the toggle buttons Start/Stop Input
and Start/Stop Output are displayed in the content
pane on the right-hand side of the window.
put (applies to both AM and PM files). Visible only if Con-
trolling is selected in tree. Button caption is
Start/Stop Toggle button to start/stop producing output files (ap- Warning Box
Output plies only to CDR files). Visible only if Controlling is se-
lected in tree.
Double-click Link to the dialog that shows collecting status for all Collecting status
on Collecting switches.
Status
Table 6-4 Description of actions on the Collecting Agent/HiPath COL Homepage
A31003-H3460-M104-4-76A9, July 2012


Double-click Link to the dialog that shows status of output lines. Output Line Status
on Output
Line Status
Double-click Link to System Management. System Manage-
on Definition ment
of Input
Lines
Double-click Link to the dialog for administration of output lines. Output Line Defini-
on Definition tion
of Output
Lines
Double-click Link to the dialog for definition of input formats. Input Format Editor
on Input For-
mat Editor
Double-click Link to the dialog for definition of output formats. Output Format Editor
on Output
Format Edi-
tor
Double-click Link to the dialog for definition of filters Filter Editor
on Filter Edi-
tor
Double-click Opens the Translation Table Editor used to create, Translation Table
on Transla- add, modify and delete translation tables. Editor
tion Table
Editor
Double-click Opens the Translation Group Editor used to create, Translation Group
on Transla- add, modify and delete translation group. Editor
tion Group
Editor
Double-click Link to the dialog to send the rejected CDRs back to the Incorrect Records
on Incorrect input.
Records
Double-click Link to Options dialog Options
on Options
Table 6-4 Description of actions on the Collecting Agent/HiPath COL Homepage (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012



Click on See Toolbar - Icon Descriptions and User Actions.
"?" (Help),
Home Page,
Start, Logoff
or Pin (Sticky
Page) icon in
Toolbar
Table 6-4 Description of actions on the Collecting Agent/HiPath COL Homepage (Fortsetzung)
Collecting Status - Field Descriptions and User Actions

Number Of Number of switches for which collect- Integer Read-only.
Configured In- ing is configured in SysM
put Lines
Collecting Ac- Check-box shows whether collecting Checked/unchecked Read-only.
tive has been activated for all switches
Table column: System ID String Read-only.
System ID
Table column: System type String Read-only.
System Type
Table column: Input format String Read-only.
Input Format
Table column: Shows whether collecting has been AM, PM, AM/PM, Read-only.
Active Collect- activated for the switch. empty
ing
Table column: Start time of the next transfer String in format Read-only.
Next Transfer “hh:mm Empty if col-
dd.mm.yyyy” lecting for that
switch is not
active.
Table column: Start time of the last transfer String in format Read-only.
Last Transfer “hh:mm
dd.mm.yyyy”
Table 6-5 Description of fields in the Collecting Status dialog
A31003-H3460-M104-4-76A9, July 2012


Table column: Status of the last transfer OK/Error/No data/ Read-only. “No
Transfer Status Running data” means
that the input
file was empty
or non-existing.
Table column: Shows whether transfer files have Yes, No, N/A Read-only. .
Transform been transferred into standard format.
Completed
Table 6-5 Description of fields in the Collecting Status dialog (Fortsetzung)

Collect now Start immediate collecting for selected switches (multi- Warning-Box
ple selection possible).
Configure Configure collecting parameters for the selected switch SysM (COL tab-
in SysM. COL tabsheet in SysM is opened. sheet)
record
"?" (Help),
Home Page,
Start, Logoff
or Pin (Sticky
Page) icon in
Toolbar
Table 6-6 Description of actions in the Collecting Status dialog
A31003-H3460-M104-4-76A9, July 2012


Output Line Status - Field Descriptions and User Actions

Number Of Number of defined output lines Integer Read-only.
Output Lines
Output Active If the check-box is unchecked, output Checked/un- Read-only.
has been deactivated for all lines checked.
Table column: Output line name String Read-only.
Name
Table column - Is output line activated? Yes/No Read-only.
Active
Table column: Output format String Read-only.
Output Format
Table column: Filter String Read-only. N/A
Filter for Backup PC
Table column: Start time of the last output hh:mm dd.mm.yyyy Read-only.
Last Output N/A for PM output
line
Table column: Status of the last output OK/Error/No data Read-only. “No
Status data” means
that the output
file was empty
or non-existing.
Table column: Start time of the next output hh:mm dd.mm.yyyy Read-only.
Next Output N/A for PM output
Table 6-7 Description of fields in the Output Line Status dialog

Configure Configure output line. Output Line Defini-
tion
Deliver Deliver selected output line(s) to the delivery directory None
Deliver all Deliver all output line(s) to the delivery directory None
Lines Now
Table 6-8 Description of actions in the Output Line Status dialog
A31003-H3460-M104-4-76A9, July 2012


record
"?" (Help),
Home Page,
Start, Logoff
or Pin (Sticky
Page) icon in
Toolbar
Table 6-8 Description of actions in the Output Line Status dialog (Fortsetzung)
The table allows selection of a single row at a time only.
COL Administration tab sheet, System Management dialog in HiPath COL - Field De-
scriptions
The following table describes the COL Administration tab sheet in HiPath COL. This tab sheet
includes COL administration and scheduling parameters.

System ID System name / retrieved sys- String (char 4)
(new) tem
Description Description of system ID String (char 40)
(new)
System Type Types of supported systems String (char 8) H300 (OpenFT)
(new) H300 HDMS (FTP)
HDMS H150-Lan (passiv/
H150-LAN TFTP)
H150-BAC H150-BackupPC
H150-ALL (FTP)
H150-COM H150-AllServe (FTP)
H5000 H150-ComboX (FTP)
H5000 (FTP)
Table 6-9 Description of fields in the HiPath COL System Management dialog
A31003-H3460-M104-4-76A9, July 2012



System Ver- Version of the system String (char 5) Version depends on
sion (new) H300 = V3.4, EV1.0, system type
EV2.0,
EV3.0, (+UV1.0)
HDMS = V3.6
H150-LAN = V1.0.
V1.2
H150-BackupPC =
V1.x
H150-ComboX =
V1.0, V1.2
H5000 = V3.0
IP Address IP Adress of the retrieved sys- String (char 32) IP Address is also
(new) tem (Mask needed from H150-
___.___.___.___ ?) Lan because of the
mapping from H150-
BackupPC.
Tab Sheet COL Administration
Input Format Combo box with the list of all List of all input for- Disabled for H150-
input formats mats BackupPC
Format of H150-
BackupPC:
the mapping to sys-
tem ID is done by IP
Address
Collect AM Check-box to activate AM col- Checked/not checked
Data lecting
Generating 3 numeric entry fields for the Values: 1 to 9 Field lengths: 3,3,2;
Node Number node number Mask: 111-111-11
Collect PM Da- Check-box to activate PM col- (*) Only supported for
ta(*) lecting HiPath 4000 COL
Table 6-9 Description of fields in the HiPath COL System Management dialog (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012


File/Directory Radio buttons to choose input File or Directory Depending on Sys-
from file or directory tem Type
H300 = File
HDMS = File
H150-Lan = Directory
H150-BackupPC =
Directory
H150-AllServe = File
H150-ComboX = File
H5000 = Directory
File/Directory Name of the file/directory String Default:
Name where data is collected from H300 = FTFILE
HDMS = GCDATA
H150-BackupPC = ../
<FTP-Collect-Dir>
H150-AllServe = ../
GCALLSERV
H150-ComboX = FT-
FILE
H5000 = <inst_path>/
H5000/cfg/cdr/
CDRReport_<date>_
<time>.txt or
CDRReport_<date>_
<time>_seq_number
>
<date> = YYYYM-
MDD
<time> = HHMMSS
<seq_number> =
{1,2,...}
Number of Re- Number of retries for data Integer Default: 3. Disabled
tries transfer for Hicom 150E
(unchanged)
Retry Time Retry time in minutes for data Integer Default: 15 min. Dis-
(unchanged) transfer abled for Hicom 150E
Start Date Start date for collecting Date Default: today
(unchanged)
A31003-H3460-M104-4-76A9, July 2012



Start Time Start time for collecting Time in format Default: current time
(unchanged) “hh:mm”
Cycle Radio-buttons to choose hours Hours or Minutes Default: hours
(unchanged) or minutes
Hours Combo-box with hours 1,2,3,4,6,8,12,24 Enabled only if Cycle
(unchanged) = Hours, not manda-
tory. Default: 1
Minutes Combo-box with minutes 1,2,3,4,5,6,10,12,15, Enabled only if Cycle
(unchanged) 30 = Minutes, not man-
datory. Default: 15.
Communica- Tab Sheet Disabled for H150-
tion Parame- Lan
ter Tab Sheet
see below see below
A31003-H3460-M104-4-76A9, July 2012

Descriptions and User Actions
.

(new) (size unchanged)
User Name User name for famos session String (char 8) Only for H300
(Group Famos)
Password Password for User name (famos String (char 8) Only for H300
(Group Famos) session)
(Group Famos)
(Group Famos)
User Name User name for FTP/OpenFT String (char 8)
(Group FTP/ session
OpenFT)
Password Password for User name (FTP/ String (char 8)
(Group FTP/ OpenFT session)
OpenFT)
(Group FTP/
OpenFT)
(Group FTP/
OpenFT)
Table 6-10 Description of fields in the HiPath COL Administration tab sheet
Buttons:
Field Description Values

Save Save changes to the database Error message for wrong
values
New Create a new object and switch to New Object None
Delete Delete selected object (only in list view) Warning box
Table 6-11 Description of buttons in the HiPath COL System Management dialog
A31003-H3460-M104-4-76A9, July 2012


Object List view, System Management dialog in HiPath COL - Field Descriptions

System ID System name / retrieved system String (char 4) Read-only
Description Description of system-ID String (char 32) Read-only
System Type Type of the systems which are sup- H300 Read-only
ported HDMS
H150-LAN
H150-BAC
H150-ALL
H150-COM
H5000
System Ver- Version of the system H300 = V3.4, EV1.0, Read-only
sion EV2.0,
EV3.0, (+UV1.0)
HDMS = V3.6
H150-LAN = V1.0.
V1.2
H150-BackupPC =
V1.x
H150-AllServe =
V1.0
H150-ComboX =
V1.0, V1.2
H5000 = V3.0
IP Address IP Adress of the retrieved system String Read-only
Table 6-12 Description of fields in the HiPath COL System Management dialog - Object List view
Input Format Editor - Field Descriptions and User Actions

Format Name Name of the selected format String (max. length Required,
30) unique
Description Short format description String (max. length Optional
255)
Predefined Check-box is checked for predefined Checked, un- Read-only
elements checked
Table 6-13 Description of fields in the Input Format Editor dialog - Object view
A31003-H3460-M104-4-76A9, July 2012


End of Line Combo-box to choose End of Line se- List of values: LF,
quence CR, CR/LF, none)
Default ele- Combo-box to select or edit a default
ment table (on element for CDR input format
left-hand side
of dialog)
Name (Default Element name, e.g. ACCTCODE for String; Length: 12 Read-only
element table) "Account code used during a call" characters
Element De- Element description, e.g. "Account String, Numeric Read-only
scription (De- code used during a call" for ACCT-
fault element CODE
table)
Allowed (De- Value to be assigned to the element if check box Read-only
fault element it is a mandatory field
table)
Input element Combo-box containing the selected
table (on right- input format elements for configuring
hand side of di- the structure of received CDR data.
alog)
# (Input ele- Position number of input element Integer Read-only. Au-
ment table) tomatically
generated by
program.
Name (Input el- Element name, e.g. ACCTCODE for String; Length: 12 Read-only
ement table) "Account code used during a call" characters
Element De- Element description, e.g. "Account String, Numeric Read-only
scription (Input code used during a call" for ACCT-
element table) CODE.
Length (Input Length in bytes of the element. Integer Read-only
element table)
Alignment (In- Alignment Left, Right Read-only
put element ta-
ble)
Number Of El- Number of elements in the Input ele- Integer Read-only; Au-
ements ment table. tomatically
generated by
program
Table 6-13 Description of fields in the Input Format Editor dialog - Object view (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012



Format Length Total length in bytes of an input row. Integer Read-only; Au-
tomatically
generated by
program
Table 6-13 Description of fields in the Input Format Editor dialog - Object view (Fortsetzung)

Double click Edit default value for the selected element Set Default Value
in the Default dialog.
element table
Double click Edit properties for the selected element Configure Input El-
in the Input ement dialog.
element table
> Move selected element from the element table to de- None.
fault table. Position numbers are automatically adjust-
ed. Button is enabled according to the system versions.
< Move selected element from the default table to the el- None.
ement table. Position numbers are automatically adjust-
ed. Button is enabled according to the System type.
Up Move up selected element in the element table. Position None.
numbers are automatically adjusted.
Down Move down selected element in the element table. Po- None.
sition numbers are automatically adjusted.
Save Save changes to the database. Before saving the for- Error message for
mat is tested (mandatory elements) and FTBL file is wrong format
generated. Enabled only in .
Add fixed text Add fixed text to input. None.
record
Table 6-14 Description of actions in the Input Format Editor dialog
A31003-H3460-M104-4-76A9, July 2012


"?" (Help),
Home Page,
Start, Logoff
or Pin (Sticky
Page) icon in
Toolbar
view.
New Object Open new format in Object view. Same form in Object
view.
List view.
Table 6-14 Description of actions in the Input Format Editor dialog (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012


Input Format Editor - Object List - Field Descriptions

The object list can not be edited. Each row contains information about one format. The table

Format Name Name of the selected format String (max. length Read-only,
30) unique.
System Ver- System version to which format ap- Free format, HiPath Read-only.
sion plies 4000
Description Short format description String (max. length Read-only.
255)
Element Count Number of elements in the element Integer Read-only
table.
Format Length Total length in bytes of an input row. Integer Read-only
Table 6-15 Description of fields in the Input Format Editor dialog - Object List view
Input Format Editor - Set Default Value - Field Descriptions and User Actions
This is a modal dialog with the title “COL - Set Default Value”. It is used to set the default value
.

Name Element name String Read-only
Type Combo-box with the type of the ele- String, Numeric Read-only
ment.
Length Length in bytes of the element. Integer Read-only
Alignment Alignment Left, Right Read-only
Default Value to be assigned to the element if String Required.
it does not appear in input.
Table 6-16 Description of fields in the Input Format Editor/Set Default Value dialog

Table 6-17 Description of actions in the Input Format Editor/Set Default Value dialog
A31003-H3460-M104-4-76A9, July 2012

Input Format Editor - Configure Input Element - Field Descriptions and User Actions
This is a modal dialog with the title “COL - Configure Input Element”. It is used to modify prop-
erties of the selected input element.

No. Row position Integer Read-only
Element De- Element name String Read-only
scription
Type Combo-box with the type of the ele- String, Numeric Required
ment.
Length Length in bytes of the element. Integer Required only
if Type is
String.
Alignment Combo-box to define alignment Left, Right
Filler Character used for padding. Char Default: space
Table 6-18 Description of fields in the Input Format Editor/Configure Input Element dialog

Table 6-19 Description of actions in the Input Format Editor/Configure Input Element dialog
Output Line Definition - Object View - Field Descriptions and User Actions

Output Line Output line name String, max. length Mandatory.
Name 32 Unique.
Description Short description of the output line String, max. length Optional
256
Active Check-box shows whether the line Checked/unchecked
has been activated
Table 6-20 Description of fields in the Output Line Definition dialog - Object view
A31003-H3460-M104-4-76A9, July 2012



File Name File destination String Mandatory. If
the file name
does not start
with “/” the file
name is rela-
tive to
$COL_DELIVE
R. If the file
name is com-
plete,
$COL_DELIVE
R is ignored.
Directory
should already
exist. Name
must be
unique.
Output Format Assigned output format List of defined output Mandatory
formats
Filter Assigned filter or empty List of defined filters Optional
Start Date/ hh:mm dd.mm.yyyy Mandatory. De-
Time fault: current
time and date.
Cycle Choice of cycle format Hours or Minutes Mandatory
Hours Combo-box with cycle-time in hours 1,2,3,4,6,8,12,24 Enabled only if
Cycle=Hours,
not mandatory.
Default: 1
Minutes Combo-box with cycle-time in min- 1,2,3,4,5,6,10,12,15, Enabled only if
utes 30 Cycle=Min-
utes, not man-
datory. Default
15.
Table 6-20 Description of fields in the Output Line Definition dialog - Object view (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012


Delete Delete selected output line (enabled only in Object List Warning Box.
view)
Save Save values (enabled only in Object view) None.
Active Activate/deactivate selected input line Warning Box
record
"?" (Help),
Home Page,
Start, Logoff
or Pin (Sticky
Page) icon in
Toolbar
view.
view.
List view.
Table 6-21 Description of actions in the Output Line Definition dialog
Output Line Definition - Object List - Field Descriptions

The object can not be edited. Each row contains information about one output line.

Name Output line name String, max. length Read-only
32
Description Short description of the output line String, max. length Read-only
256
Table 6-22 Description of fields in the Output Line Definition dialog - Object List view
A31003-H3460-M104-4-76A9, July 2012



Output Format Assigned output format List of defined output Read-only
formats
Filter Assigned filter or empty List of defined filters Read-only
Active Is line activated? Yes/No Read-only
Filename File destination String Read-only
Start Date/ hh:mm dd.mm.yyyy Read-only
Time
Cycle Cycle time in hours or minutes. Possi- Hours or Minutes Read-only
ble values for minutes are:
1,2,3,4,5,6,10,12,15,30. Possible val-
ues for hours are: 1,2,3,4,6,8,12,24.
Table 6-22 Description of fields in the Output Line Definition dialog - Object List view (Fortsetzung)
Output Format Editor - Object View - Field Descriptions and User Actions

Format Name Name of the selected format. String (max. length Required, unique
30)
Description Short format description String (max. length
255)
End of Line Combo-box to choose End of List of values: LF,
Line sequence CR, CR/LF, none)
Element group list Selection of the element group. Standard Elements, Read-only
Combo-box with the list of ele- CM Elements, Text
ment groups. Elements
Element table (on List of elements available in the String Read-only
left-hand side of di- database. Allows selection of
alog) the element to be added to the
Output table.
Name - Element ta- Element name, e.g. "BCHL- String Read-only
ble CNT" for "Number of used B
channels"
Description - Ele- Element description, e.g. String Read-only
ment table "Number of used B channels"
for "BCHLCNT"
Table 6-23 Description of fields in the Output Format Editor dialog - Object view
A31003-H3460-M104-4-76A9, July 2012


Output elements List of output elements added
table (on right- by the user to the Output ele-
hand side of dia- ments table.
log)
# - Output ele- Position number Integer Read-only. Posi-
ments table tion number is au-
tomatically gener-
ated by program.
Name - Output ele- Element name, e.g. "BCHL- String Read-only
ments table CNT" for "Number of used B
channels"
Description - Out- Element description, e.g. String Read-only
put elements table "Number of used B channels"
for "BCHLCNT"
Length - Output el- Length in bytes of the element. Integer Read-only
ements table
Alignment - Output Alignment Left, Right Read-only
elements table
Filler - Output ele- Character for padding. Char Read-only.
ments table
Text - Output ele- Text is defined only for fixed text String. Read-only.
ments table elements
Number Of Ele- Number of elements in the out- Integer Read-only.
ments put table
Format Length Total length in bytes of an out- Integer Read-only.
put row.
Table 6-23 Description of fields in the Output Format Editor dialog - Object view (Fortsetzung)

> Copy selected element from the standard element None
list to the output table. Selected element is not delet-
ed from the original table. Position numbers are au-
tomatically adjusted.
< Delete selected element from the output element ta- None
Table 6-24 Description of actions in the Output Format Editor dialog
A31003-H3460-M104-4-76A9, July 2012



Double click in Edit properties for the selected element Configure Output Ele-
the Output ta- ment dialog.
ble
Up Move up selected element in the output element ta- None
Down Move down selected element in the output element None
table. Position numbers are automatically adjusted.
Save Save changes to the database. Enabled only in Ob- None
ject view.
Delete Delete selected object. Enabled only in Object List Warning Box
view.
record
Click on Print, See Toolbar - Icon Descriptions and User Ac-
"?" (Help), tions.
Home Page,
Start, Logoff
or Pin (Sticky
Page) icon in
Toolbar
view.
view.
List view.
Table 6-24 Description of actions in the Output Format Editor dialog (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012

Output Format Editor - Object List - Field Descriptions


Format Name Name of the selected format String (max. length Read-only,
30) unique.
255)
Element Count Number of elements in the output ele- Integer Read-only
ment table.
Output format Total length in bytes of an output row. Integer Read-only
length
Table 6-25 Description of fields in the Output Format Editor dialog - Object List view
Output Format Editor - Configure Output Element - Field Descriptions and User Actions

No Position number Integer Read-only
Name Element name String Read-only
Type Combo-box with the type of the ele- String, Numeric Required
ment.
Length Length in bytes of the element. Integer Required only
if Type is
String.
Alignment Combo-box to define alignment Left, Right
Filler Character used for padding Char
Text Text property for fixed text elements String Enabled and
required only
for fixed text el-
ements.
Table 6-26 Description of fields in the Configure Output Element dialog
A31003-H3460-M104-4-76A9, July 2012



OK Accept values and close dialog Output Format Editor
Cancel Close without accepting values Output Format Editor
Table 6-27 Description of actions in the Output Format Editor/Configure Output Element dialog
Filter Editor - Object View - Field Descriptions and User Actions

Filter name String, max. length Mandatory
32
Description String, max. length Optional
256
Element group Selection of the element group. Com- Standard Elements, Read-only
list bo-box with the list of element groups CM Elements, Com-
plex Elements
Element table List of elements available in selected
element group. Allows selection of an
element.
Name - Ele- Table column with element names String, e.g. "AC- Read-only
ment table COUNT" for "Ac-
count Number"
Name - Ele- Table column with element descrip- String, e.g. "Account Read-only
ment table tions Number" for "AC-
COUNT"
Filter Clause List of elements added by the user to
table the Filter Clause table. Filter Clause
elements can be edited by double-
clicking on a record (row) in the Filter
Clause elements table.
# - Filter Position number Integer Read-only. Po-
Clause table sition number
is generated
automatically
by program.
Name - Filter Table column with element names String Read-only.
Clause table
Table 6-28 Description of fields in the Filter Editor dialog - Object view
A31003-H3460-M104-4-76A9, July 2012


Operator - Fil- Table column with operators =, <>, <, > <=, >=, IN, Required
ter Clause ta- NOT IN
ble
Value - Filter Table column with values. In case of String Required
Clause table multiple values, comma is used as the eg [1-1-20-4711]
delimiter.
Element count Number of rows in the selection Integer Read-only
clause
Table 6-28 Description of fields in the Filter Editor dialog - Object view (Fortsetzung)

Double-click Modify selected row from the filter table. Configure Filter Ele-
in the filter ta- ment dialog.
ble
> Copy selected element from the element table to the fil- None
ter table. Position numbers are adjusted automatically.
< Delete selected element from the filter table. Position None
numbers are adjusted automatically.
Save Save changes to the database. Enabled only in Object None
view.
record
"?" (Help),
Home Page,
Start, Logoff
or Pin (Sticky
Page) icon in
Toolbar
Table 6-29 Description of actions in the Filter Editor dialog
A31003-H3460-M104-4-76A9, July 2012



view.
view.
List view.
Table 6-29 Description of actions in the Filter Editor dialog (Fortsetzung)
Filter Editor - Object List - Field Descriptions

The object can not be edited. Each line contains information about one filter.

Filter Name Name of the filter String (max. length Read-only,
30) unique.
255)
Element Count Number of elements in the filter table. Integer Read-only
Table 6-30 Description of fields in the Filter Editor dialog - Object List view
Filter Editor - Set Default Value - Field Descriptions and User Actions

Element Name Name of element selected in the Fil- String Read-only
ter Clause table.
Element De- Description of the element selected in String Read-only
scription the Filter Clause table.
Operator Combo-box with operators =, <>, <, > <=, >=, IN, Required
NOT IN
Value Value String, range for nu- Required
meric values and
values in brackets []
Table 6-31 Description of fields in the Configure Filter Element dialog
A31003-H3460-M104-4-76A9, July 2012


OK Accept values and close dialog Filter Editor
Cancel Close without accepting values Filter Editor
Table 6-32 Description of actions in the Configure Filter Element dialog
A31003-H3460-M104-4-76A9, July 2012


Translation Table Editor -- Field Descriptions and User Actions
Field Description Value(s) Comment

Translation Ta- Name of selected translation table. String (max. 30 Unique.
ble Name characters). Mandatory.
Element This combo box contains the list of The list of Standard Mandatory.
Standard Elements and CM Ele- Elements also con-
ments. tains generated ele-
The CM Elements are only displayed ments which do not
if the COL software is installed with appear in the input
the necessary user license rights. (e.g. SYSTYPE).
Description Short description of translation table. String (max. 255 Optional.
characters).
Predefined This box is checked (activated) with Activated, Not acti- Read-only.
predefined, non-editable tables. vated.
Translation Ta- Displays the sequential number of 1,2,3,... Read-only.
ble Values -- each table row.
Position The sequential numbers of all table
rows are automatically assigned or
updated, respectively, upon creation
or deletion of a row. If a row is added
or deleted between already existing
rows at a later time, the sequential
numbers of all following rows will be
updated automatically.
Translation Ta- Enter the input value for the transla- String, max. 100 Value must be
ble Values -- tion (transformation) here. characters. unique within one
In Value table.
Translation Ta- Enter the output value for the trans- String, max. 100 Value must be
ble Values -- lation (transformation) here. characters. unique within one
Out Value tabl.
Optional.
Translation Ta- Comment. String, max. 255 Optional.
ble Values -- characters.
Comment
Number of Val- The total number of rows in the table Integer. Read-only.
ues is displayed here.
Table 6-33 Translation Table Editor, Object view, field descriptions
A31003-H3460-M104-4-76A9, July 2012


Add new row Add new row to the translation table. New empty row None.
(icon) is inserted below the currently selected row. Cursor is
positioned to the In Value table column field in the new
row. The sequential number of the new row is auto-
matically generated. Sequential numbers are updated
for all rows below the new row. Changes are not saved
to the database. Available only in Object and New
Object view.
Delete row Delete selected row from the translation table. The se- None.
(icon) quential number of the new row is automatically gen-
tabase. Available only in Object and New Object
view.
values are entered.
ible deletion.
tant/Manager.
Table 6-34 Translation Table Editor, description of user actions
A31003-H3460-M104-4-76A9, July 2012



view.
view.
List view.
New Object view.
New Object view.
Object view.
er window.
menu.
screen.
menu.
Table 6-34 Translation Table Editor, description of user actions (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012


menu.
Table 6-34 Translation Table Editor, description of user actions (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012


Translation Group Editor -- Field Descriptions and User Actions

Group Name Unique name of translation group. String (max. 30 Unique,
characters). Mandatory.
Description Short description of translation String (max. 255 Optional.
group. characters).
Predefined This box is checked (activated) with Activated, Not acti- Read-only.
predefined, non-editable tables. vated.
Available Ta- Table column in Available tables list String, max. 30 Read-only.
bles -- Table located in left hand side area of characters.
Name Translation Group Editor dialog,
Object. view.
Displays the name of the translation
table.
Available Ta- Table column in Available tables list String, max. 30 Read-only.
bles -- located in left hand side area of characters.
Element Translation Group Editor dialog,
Object. view.
Displays the element for which a val-
ue transformation (translation) is de-
fined in the table.
Available Ta- Short description of translation table. String (max. 255 Read-only.
bles -- characters). Optional.
Description
Translation Ta- Name of selected translation table. String (max. 30 Read-only.
bles in the characters).
Group -- Table
Name
Translation Ta- Table column in the Translation Ta- String (max. 30 Read-only.
bles in the bles in the Group table located in characters).
Group -- Ele- right hand side area of Translation
ment Group Editor dialog, Object. view.
Displays the element for which a val-
ue transformation (translation) is de-
fined in the table.
Table 6-35 Translation Group Editor, Object view, field descriptions
A31003-H3460-M104-4-76A9, July 2012


Translation Ta- Short description of translation table. String (max. 255 Read-only.
bles in the characters). Optional.
Group -- De-
scription
Translation Ta- Number of values in the translation Integer. Read-only.
bles in the table.
Group -- Num-
ber of Values
Number of Ta- Number of tables in the group. Integer Read-only.
bles
Table 6-35 Translation Group Editor, Object view, field descriptions (Fortsetzung)

> Add selected table from list of available tables to trans- None.
lation group. The selected table is removed from the
list of available tables. The changes are not saved to
the database.
< Delete selected row (translation table) from translation None.
group and move translation table to list of available ta-
bles. The changes are not saved to the database.
values are entered.
ible deletion.
Table 6-36 Translation Group Editor, description of user actions
A31003-H3460-M104-4-76A9, July 2012



tant/Manager.
view.
view.
List view.
New Object view.
New Object view.
Object view.
er window.
menu.
Table 6-36 Translation Group Editor, description of user actions (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012


screen.
menu.
menu.
Table 6-36 Translation Group Editor, description of user actions (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012


Incorrect Records - Send Back To Input - Field Descriptions and User Actions

System ID System ID String Read-only.
System ID is
extracted from
the directory
name. If the file
is stored in the
wrong directo-
ry, the System
ID is wrong as
well.
File Name File name (without directory name) String Read-only
File Size File size in kilobytes Integer Read-only
Input Format Input format for the switch String Read-only.
Current format
for the switch is
fetched from
the database. It
is not neces-
sarily the origi-
nal format of
the file.
Table 6-37 Description of fields in the Incorrect Records dialog

Incorrect Send selected file back to input. If the input format is Warning box
Records / correct and the file can be processed, it will automatical-
Send Back to ly be deleted afterwards. In order to view the latest data,
Input press the Refresh button or restart the window.
Delete Delete selected file Warning box
record
Table 6-38 Description of actions in the Incorrect Records dialog
A31003-H3460-M104-4-76A9, July 2012


"?" (Help),
Home Page,
Start, Logoff
or Pin (Sticky
Page) icon in
Toolbar
Table 6-38 Description of actions in the Incorrect Records dialog (Fortsetzung)
Options - Field Descriptions and User Actions

Input Path Directory where to store input files String Also referred as
$COL_INPUT
Transform Path Directory where to store transformed String Also referred as
files $COL_TRANSFORM
Output Path Directory where to store output files String Also referred as
$COL_OUTPUT
AM Deliver Directory where to deliver files for AM String Also referred as
path $COL_DELIVER
PM Deliver Directory where to deliver files for PM String
path
Path of Incor- Directory where to store rejected CDRs String Also referred as
rect Records $COL_ERROR
FTBL path Directory where FTBL files are stored. String Also referred as
$COL_FTBL
TFTP path Directory where TFTP files are stored. String Also referred as
$COL_TFTP
Trunk Group Path where the traffic metering files will String
Metering Path be saved.
Number of Re- Number of receive processes Integer
ceive Threads
Table 6-39 Description of fields in the Options dialog
A31003-H3460-M104-4-76A9, July 2012



Number of Number of transform processes Integer
Transform
Threads
Number of Line Number of line processes Integer
Threads
Required Free Required free space on disk in % for in- Integer
Space put files (0-100)
Retention Peri- Use this field to enter the duration (in Integer.
od for CM His- number of days) for the retention period Default vaule:
tory Data ... of CM history data. 20 days.
Day(s)
Activate fast When this check box is marked, the fast
mode for trans- mode for transformation of virtual to
formation of vir- physical node numbers is activated for
tual to physical the PM output line only.
node number
only for the PM
output line
Activate/Deac- Using this check box you can specify When this check box
tivate automatic whether the logging entries in COL is marked, the logging
delete of Log- should be automatically deleted or entries will automati-
ging Entries in saved and retained for a certain period. cally be deleted.
COL
Retention Peri- Use this field to enter the duration (in Integer, 1-3
od for Logging number of days) for the retention period digits
Entries ... of the logging entries. Possible val-
Day(s) ues:
1 - 366 day(s)
Save Input Use this check box to enable/disable If this check box is en-
Files (CDRs) the backing up of input files (CDRs). If abled, the input files
this check box is enabled, the input files containing the call
containing the call data record sets data record sets
(CDRs) will be saved to a backup direc- (CDRs) will be saved
tory under the path ..\var\COL\data. to a backup directory
For more information and important under the path
notes please refer to ..\var\COL\data.
Save Input Files (CDRs).
Table 6-39 Description of fields in the Options dialog (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012


Retention Peri- Use this field to enter the period - de- Integer
od for Trunk fined in days - over which the cyclic Default value:
Group Data check data will be kept in the database. 100 days.
from the Cyclic Max. value:
Check of the B 366 days.
Channels ...
Day(s)
Table 6-39 Description of fields in the Options dialog (Fortsetzung)

Save Save values. Enabled only for “rsca” user. Warning box.
"?" (Help),
Home Page,
Start, Logoff
or Pin (Sticky
Page) icon in
Toolbar
Table 6-40 Description of actions in the Options dialog

Date Displays the date and time when Column; Read-only
the log message was issued.
Category Indicates the category of the Column; Read-only
logged activity, e.g. "start applica-
tion" or "exit application".
System ID The ID of the network node String Also referred as
(switch) that is being logged and $COL_TRANSFORM
issued the log message.
Error Error code Also referred as
$COL_INPUT
Short message Displays a short description of the Column; Read-only
logged activity or error, e.g. "COL
process dbproxy started."
Table 6-41 Description of fields in the Logging report
A31003-H3460-M104-4-76A9, July 2012



Long message Displays a more detailled descrip- Column; Read-only
tion of the logged activity or error,
e.g. "COL process dbproxy start-
ed."
Severity Indicates the severity of the log 0 indicates lowest Column; Read-only
message. severity.
Print/Export Opens Run Report dialog to de- Button
fine various log output formats for
Exporting Log Reports and send
log files as e-mail attachment.
Table 6-41 Description of fields in the Logging report (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012

6.2 Elements for Defining Input and Output Formats for COL CDRs
Important:
> Starting with CV631/CV645-646 the pre-defined input and output formats cannot be
modified any more. For more information please refer to Default Input and Output
Formats Cannot Be Modified Any More.
Elements for Defining Input and Output Formats, page 6-50
A31003-H3460-M104-4-76A9, July 2012


Elements for Defining Input and Output Formats

The following table describes the elements which can be assigned to the input and output for-
mat of COL:
Short name Long name (eng) Type (Len) / Range Man- Element desciption De-
Default of datory fault
Length values field value
ACCTCODE account code int(12) num. no >= H300 UNITY ger/eng: blank
H8:int(15) H8:text ACCT CODE
(new US) Account code used
(+H8000) be fore / during a R6.5/6.6: ACCTCODE
call
Account code associated with a call.
The account code is entered by the
user either before or during the call.
In AMO FEASU, the sys tem feature
“CDRACC” must be activated for this
to work.
>= H300 UNITY ger/eng:

ACCTCODE
R6.5/6.6: ACCTCODE
H8000 Element No 8
ACCTCODEBG BG account code H8:int(15) H8:text no only for (no H300 field): blank
H8000 Element No 90
(+H8000)
ACDAGTID ACD agent ID, the int(6) num no >= HiPath 4000 V1.0 0
ID of the ACD agent ger/eng: ACDAGTID
in volved in an in-
coming of outgoing, The ID of the ACD agent involved in
(new H4000) answered call. an incoming or outgoing, answered
call.
ACDGID ACD Group Number Int(3) Num. no Standard Element 0
(new H4000) (ID) >= HiPath 4000 V3.0
ger/eng: ACDGID
ACDINFO ACD / Non-ACD char(1) text no only for (no H300 field): H5000 -
(new H5000)
Table 6-42 Elements for Defining Input and Output Formats
A31003-H3460-M104-4-76A9, July 2012

ADPLOAD ACD / Non-ACD char(1) text no only for (no H300 field): H5000 -
0-1000 promille (ev-
ery 10 sec onds) >= H300 UNITY ger/eng: ADP LOAD
(new H5000)
Processor load of the ADP in parts
per thousand. It is an aver age load
over 10 seconds. The time stamp,
when the load was taken, is available
in the end_of_connection field:
ENDDAY (2 digits),
ENDMONTH (2 digits),
ENDHOUR (2 digits),
ENDMIN (2 digits),
ENDSEC (2 digits),
END10 (1 digits). END10 is tenth of a
second.
AOCTYPE advice of charge char(10) text no >= H300 E3.0 ger/eng: AOC TYPE 0
/ def: 1 (0-3) Not used in the US.
(AMO-TEXT)
ARSPATTGRP BG ARS Pattern int(1) num. no only for (no H300 field): 0
Group H8000 Element No 97
(new H8000)
ATTCALLP attendant call priori- int(2) num. no >= H4000 V2.0 0
ty, priority of the call (1-48) ger/eng: ATTCALLP
(new H4000) to the attendant
This field contains a number repre-
senting the priority of a call to the at-
tendant.
ATTCALLR attendant intercept int(2) num. no >= H4000 V2.0 0
reason, reason for (0-26) ger/eng: ATTCALLR
(new H4000) the intercept When a call is intercepted to the at-
tendant console, the field will contain
a number representing the intercept
reason.
Table 6-42 Elements for Defining Input and Output Formats (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012


ATTCALLT attendant call type int(2) num. no >= H4000 V2.0 0
(0-23) ger/eng: ATTCALLT
(new H4000) Contains a number representing the
type of a call to the attendant.
0: EMERGENCY_CALL
1: HOTLINE_CALL
2: LOCAL_FIRST_CALL
3: LOCAL_RECALL
4: LOCAL_PRIO_CALL
5: CO_RECALL
6: CO_SERIAL_CALL
7: CO_IN_CONSULTATION
8: CO_ON_HOOK_IN_CONS
9: TIE_RECALL
10: TIE_SERIAL_CALL
11: TIE_IN_CONSULTATION
12: TIE_ON_HOOK_IN_CONS
13: OVFL_LOC_FIRST_CALL
14: OVFL_LOC_PRIO_CALL
15: OVFL_CO_FIRST_CALL
16: OVFL_TIE_FIRST_CALL
17: PERSONAL_CALL
18: ATND_LOOP_TRANSFER
19: CO_FIRST_CALL
20: MLPP_FLASH_OV
21: MLPP_FLASH
22: MLPP_IMMED
23: MLPP_PRTY
ATTGRNO attendant console int(2) num. no H300 ger: ATTGRNR 0
group (0-16) H300 eng:ATNDGRNO
R6.5/6.6: ATNDGRNO
ATTQUEID attendant queue id int(2) num. no >= H4000 V2.0 0
for AC-Win Multipe (0-14) ger/eng: ATTQUEID
Queue (MQ)
(new H4000) For calls to an AC Win MQ this field
will hold the Queue ID as signed to
the call.
AUTH autorisation code char(22) text no No H300 element blank
H8:char(15) H8000 Element No 89
(+new H8000)
A31003-H3460-M104-4-76A9, July 2012

BAUD transmission speed char(10) num. no H300 ger: SPEED 0
/ def: 3 0-255 H300 eng: BAUD
(AMO-TEXT) or R6.5/6.6: BAUD
value
Output of the transmission speed as
a text string
(10 digits, administr. by AMO- Text, if

the speed is not defined by AMO-
text-table, the speed will be a num-
ber with 3 digits)
BCHLCNT number of used B- int(2) num. no >= H300 E1.0 ger/eng: BCHLCNT 0
channels (0-30) R6.5/6.6: BANDWDTH
BEARCAP Bearer Capability int(1) num. no only for (no H300 field): 0
Request H8000 Element No 20
(new H8000)
BLENBYT block length in bytes int(5) num. no H300 ger/eng: BLENBYT 0
(old) R6.5/6.6: BLENBYT
BLENREC No. of Records per int(5) num. no H300 ger/eng: BLENREC 0
(old) Block R6.5/6.6: BLENREC
CAELNPNO Local Number Porta char(10) text no only for (no H300 field): blank
biltily (LNP) Ad- H8000 Element No 15
(new H8000) dress Parameter
CALCTYPE applied type of bill- char(10) text no >= H300 E3.0 ger/eng: 0
(AMO-TEXT) ing / def: 1 0-3 CALCTYPE
A31003-H3460-M104-4-76A9, July 2012


CALLEPTY called party, number char(22) text no >= H300 E3.0 ger/eng: CALLEP TY blank
which was dialed by 0-9,*,# Common for all parties: If the party is
the calling party - an attendant console, AMO-TLZO
e.g. hunting group can be used to create a virtual sub-
scriber number; an entry in AMO-
TLZO must be cre ated for a main
PBX tie trunk set (HAS). If the length
of the output field is shorter than the
length of the party number to output,
the party number is cut off. For this
reason the parameter FLDALIGN
(more details see AMO-FTBL) will be
used.
Example right justified: Party:
96252125 Data record: 2125
Example left justified: Party:
96252125 Data record: 9625
If the length of the party to output is
shorter than the field size in the data
record, the field will be filled with the
specified filler (left or right).
Example right justified with longer
field:
A-Paypart: 2125 Data record:
____2125
Example left justified with long er
field:
A-Paypart: 2125 Data record:
2125____
CALLFUSE Per Call Feature us- int(1) num no only for (no H300 field): 0
age H8000 Element No 106
(new H8000)
CALLIID identification of call- char(10) text no >= H300 UNITY ger/eng: 4
ing party number / def: 1 (0-8) CALLIID H8:0
(AMO-TEXT ST- (uses value from el- H8:int(3) H8:num H8000 Element No 40
NID) ement STNID)
(new) The ID output is the same as the
(+H8000) AMO TEXT field STNID.
CALLILV0 node number of int(3) num. no >= H300 E3.0 ger/eng: CALLILV0 0
calling party (0-999) >= H300 E1.0 ger/eng: LEVEL0
>= H300 V3.4 ger/eng: NODENR
CALLILV1 subdomain number int(3) num. no >= H300 E3.0 ger/eng: CALLIV1 0
of calling party (0-255)
CALLILV2 domain number of int(2) num. no >= H300 E3.0 ger/eng: CALLILV2 0
call ing party (0-31) >= H300 E1.0 ger/eng: LEVEL2
A31003-H3460-M104-4-76A9, July 2012

CALLIONI originating network int(2) num. no >= H300 UNITY ger/eng: CAL LIONI 0
ID of the calling par- (0- 27) H4000 V1.0:
(new H4000) ty (pri vate / public) 0 = private network
1 = public network
H4000 V2.0:
0 + (>4) 5-27 = private network
1,2,3,4 = public network
CALLIPTY calling party, party char(22) text no >= H300 E3.0 ger/eng CALLIPTY blank
that initiated the cur- H8:char(2 0) 0-9,*,# >=H300 V3.4 ger: PAYPART
(+H8000) rent connection/ >=H300 V3.4 eng: CHRGEE
section R6.5/6.6: SRCNO
H8000 Element No 12
CALLISTAT Calling Party Query int(2) num. no only for (no H300 field): 9
Status H8000 Element No 46
(new H8000)
CALLTPYE Call Type / Attempt int(3) num. no only for (no H300 field): Blank
H8000 Element No 16
(new H8000)
CARRIER carrier, char(10) text no >= H300 V3.4 ger/eng: CARRIER 1
output of the com- / def: 1 (0-9)
(AM0-TEXT) muni cation network H8:char(6 ) Output of the Identifier of the com
(+H8000) as a text string munication network, such as AT & T,
or MCI.
H8000 Element No 10
CAUSE cause of connection int(3) num no >= H300 V3.4 ger/eng: 0
in terrupt / clearing CAUSE
(enhanced) the call
(+H8000) A code used to indicate the rea son
for clearing a call (connection inter-
rupt), consult AMO-FTBL for a com-
plete listing. Not used when
CONNTYPE = INTERNAL
H8000 Element No 19
CDRRECINFO Additional CDR int(1) num no only for (no H300 field): 0
(AIN Call Involve- H8000 Element No 100
(new H8000) ment)
CFANUUMID BG Orignating Sta- char(7) num no only for (no H300 field): blank
tion Facility ID H8000 Element No 93
(new H8000)
CFATYPE BG Orignating Fa- int(1) num no only for (no H300 field): 0
cility Type H8000 Element No 91
(new H8000)
A31003-H3460-M104-4-76A9, July 2012


CFW indicates forwarded char(10) / text no only for (no H300 field) 1
calls def: 1 (0-1) R6.5/6.6: CFW
(new R6.5/6.6 H8:int(1) H8:num H8000 Element No 23
(AMO-MFORM)
(+H8000)
CHOFCON type of connection char(10) text no H300 ger/eng: CHOFCON 0
(old) / def: 1 (0-6) 1 = Local
2 = Long distance
(AMO-TEXT) 3 = Local with limit value exceed ed
4 = Long distance with limit value ex-
ceeded
5 = No entry
6 = Route optimization
CHRGUNIT call charge units int(5) num. no H300 ger/eng: CHRGUNIT 0
(0- Not used in the US.
65535)
CHRGVALU call charge units or int(11) num. no only for (no H300 field): 0
amount H150-LAN and H150-ALL
(new H150)
CJITTER Originating Side In- int(10) num no only for (no H300 field): 0
ter arrival JITTER H8000 Element No 75
(new H8000) Lost
CLINEUSED Originating Side Co- int(7) num no only for (no H300 field): 0
dec Used H8000 Element No 67
(new H8000)
CMDRID BG Originating. char(10) text no only for (no H300 field): blank
MDR Customer ID H8000 Element No 87
(new H8000)
CMSWVERS Switch version Char(5) text no CM Element blank
COCTRCVD Originating Side Oc- int(10) num no only for (no H300 field): 0
tets Received H8000 Element No 73
(new H8000)
COCTSEND Originating Side Oc- int(10) num no only for (no H300 field): 0
tets Send H8000 Element No 71
(new H8000)
COLTYPE COL Record Type Char(1) text no Standard Element 0
(sign AM and/or
PM)
CON10 connecton duration int(1) num. no H300 ger/eng: CON10 0
part of 1/10 second R6.5/6.6: CON10
CONCHRG costs calulated on float num., no H300 ger/eng: CONCHRG 0
out put with include char(13) with
value- added tax / def: 9 comma Not used in the US.
A31003-H3460-M104-4-76A9, July 2012

CONCHRN nettocosts calculat- float num., no >= H300 E3.0 ger/eng: CON CHRN 0
ed on output (with- char(13) with
out val ue added / def: 9 comma Not used in the US.
tax)
CONDAY connection duration int(3) num. no only for (no H300 field): 0
of part day H5000
(new H5000)
CONF indicates confer- char(10) / text no only for (no H300 field) 1
ence call def: 1 (0-1) R6.5/6.6: CONF
(new R6.5/6.6
(AMO-MFORM)
CONHOUR connection duration int(2) num. no H300 ger/eng: CONHOUR 0
of part hour R6.5/6.6: CONHOUR
CONMIN connection duration int(2) num. no H300 ger/eng: CONMIN 0
of part minute R6.5/6.6: CONMIN
CONNSTEP connection se- int(3) num. no >= H300 E3.0 ger/eng: 1
quence, (1-255) CONNSTEP
all CDB records of a (start with content 1)
connection will be
numbered sequen-
tially
CONNTYPE connection type char(10) text no >= H300 V3.4 ger/eng: CONNTYPE 0
/ def: 1 (0-5) 2 additional values
(enhanced) Connection type:
(AMO-TEXT) INTERN = internal connection
INCO = incoming connection
OUTGO = outgoing connection
ACACT = activity of attendant
LOAD = load of processors
CONSEC connection duration int(2) num. no H300 ger/eng: CONSEC 0
of part second R6.5/6.6: CONSEC
CONTOT connection duration int(6) num. no H300 ger: CONTSEC 0
to tal in 1/10 second H8:int(10) H300 eng: CONSECT
(+H8000) R6.5/6.6: CONSECT
H8000 Element No 4
A31003-H3460-M104-4-76A9, July 2012


COPIN class of pin char(10) text no >= H300 V3.4 ger/eng: COPIN 0
/ def: 2 (0-10) R6.5/6.6: DISAIND
(enhanced) 0 = No valid class of PIN
(AMO-TEXT) 1 = Manual PIN for mobile user
2 = Business PIN for long service
3 = Business PIN used for the call
4 = Private PIN used for the call
5 = Project code used for the call
6 = ID card for mobile user
7 = Switchover code
8 = PIN for service ID
9 = CDR account code
10 = PIN for dialing pattern check
CPACKLOST Originating Side int(10) num no only for (no H300 field): 0
Pack ets Lost H8000 Element No 74
(new H8000)
CPACKRCVD Originating Side int(10) num no only for (no H300 field): 0
Pack ets Received H8000 Element No 72
(new H8000)
CPACKSENT Originating Side int(10) num no only for (no H300 field): 0
Pack ets Send H8000 Element No 70
(new H8000)
CRESINFO Originating Side int(1) num no only for (no H300 field): 0
Res ervation Used H8000 Element No 69
(new H8000)
CSIGCOMP BG Origination Call int(1) num no only for (no H300 field): 0
Completion Code H8000 Element No 95
(new H8000)
CSUPLINFO BG Origination - int(1) num no only for (no H300 field): 0
Busi ness Feature H8000 Element No 96
(new H8000) Code
CTOSUSED Originating Side int(3) num no only for (no H300 field): 0
TOS Used H8000 Element No 68
(new H8000)
CTRDIFF call charge sum for int(5) num. no H300 ger/eng: CTRDIFF 0
(old) sta tion difference
only GET functionality (charge data
recording per station) with format
No.>=97
CTRNSDELY Originating Side int(10) num no only for (no H300 field): 0
Aver age Transmis- H8000 Element No 76
(new H8000) sion De lay
A31003-H3460-M104-4-76A9, July 2012

CTRTOT call charge sum for int(5) num. no H300 ger/eng: CTRTOT 0
(old) sta tion total
only GET functionality (charge data
recording per station) with format
No.>=97
CUSTNAME Customer Name / char(16) text no only for (no H300 field): blank
Number H8000 Element No 7
(new H8000)
DAILID Dailing and Presub int(1) text no only for (no H300 field): 0
scription Indicator H8000 Element No 54
(new H8000)
DAILINFOBG BG Access Code / char(5) text no only for (no H300 field): blank
Dai ling Information H8000 Element No 99
(new H8000)
DEPARTNAME BG Department char(20) text no only for (no H300 field): blank
Name H8000 Element No 102
(new H8000)
DESTIP destination gateway char(15) text no only for (no H300 field): H5000 blank
(new H5000)
DESTLV0 node number of int(3) num. no >= H300 E3.0 ger/eng: DESTLV0 0
desti nation number (0-999)
(new/ connect par-
ty)
DESTLV1 subdomain number int(3) num. no >= H300 E3.0 ger/eng: DESTLV1 0
of destination num- (0-255)
ber (new/connect
party)
DESTLV2 domain number of int(2) num. no >= H300 E3.0 ger/eng: DESTLV2 0
des tination number (0-31)
(new/ connect par-
ty)
A31003-H3460-M104-4-76A9, July 2012


DESTPID identification num- char(10) text no >= H300 UNITY ger/eng: 0
ber of destination / def: 1 (0-8) DESTPID
(AMO-TEXT number (new/con- R6.5/6.6: DESTID (see AMO- TEXT)
STNID) nect party) (uses H8:int(3) H8:num For dialed numbers it is not al ways
(new) value from ele ment possible to determine the ID of the
STNID) destination party. In these cases “un-
known” is output. For connected par-
ties (and new desti nation parties
that might occur) the ID is the same
as that STNID in AMO TEXT listed
here:
1 = VF =Operator console
2 = HAS= PBX set
3 = NST= Night server
4 = TLN = Subscriber
5 = SM= Service module (for field
paying party ID only)
6 = SPC= Special charging (for field
paying party ID only)
7 = MEQ= Maintenance equip ment
(for field paying party ID only)
8 = PUP= Public phone via SL MAR
to HiPath (for field paying party ID
only)
9 = MOB = Mobile user
10 = KEY = Number of the other line
(keyset)
DESTPSTAT Destination Party int(2) num. no only for (no H300 field): 9
Que ry Status H8000 Element No 47
(new H8000)
DESTPTY destination number char(22) text no >= H300 E3.0 ger/eng: blank
(new/connected max. range 0-9,*,# DESTPTY
(enhanced for party) called party char(25) H300 ger: VDESTNR
H150) H8:char(3 0) H300 eng: VDESTNO
(+H8000) R6.5/6.6: DESTNO
only filled if connected

H8000 Element No 11
DFANUUMID BG Terminating Sta- char(7) num no only for (no H300 field): blank
tion Facility ID H8000 Element No 94
(new H8000)
DFATYPE BG Terminating Fa- int(1) num no only for (no H300 field): 0
cility Type H8000 Element No 92
(new H8000)
A31003-H3460-M104-4-76A9, July 2012

DISPCHRG display charge, float num., no >= H300 V3.4 ger/eng: 0
charge of the con- char(13) with DIS PCHRG
nection shown on / def: 9 comma
display with include calculated during the connection
value-added tax
Not used in the US.
DISPCHRN netto display float num., no >= H300 E3.0 ger/eng: DIS PCHRN 0
charge, charge of char(13) with
the connec tion / def: 9 comma calculated during the connection
shown on display
without value-add- Not used in the US.
ed tax
DISPCHRN netto display float num., no >= H300 E3.0 ger/eng: 0
charge, charge of char(13) with DISPCHRN
the connec tion / def: 9 comma
shown on display calculated during the connection
without value-add-
ed tax
DJITTER Terminating Side In- int(10) num no only for (no H300 field): 0
ter arrival JITTER H8000 Element No 85
(new H8000) Lost
DLINEUSED Terminating Side Co int(7) num no only for (no H300 field): 0
dec Used H8000 Element No 77
(new H8000)
DMDRID BG Terminating char(10) text no only for (no H300 field): blank
MDR Customer ID H8000 Element No 88
(new H8000)
DNBASESTA Forwarded Base char(20) text no only for (no H300 field): Blank
Sta tion H8000 Element No 65
(new H8000)
DNIS contains text strings char(22) text no >= H300 UNITY ger/eng: DNIS blank
re lated to the called R6.5/6.6: DNIS
(new US) party (dialed num-
ber) The DNIS number is provided by the
PSTN and is related to the called
party.
DOCTRCVD Terminating Side Oc int(10) num no only for (no H300 field): 0
tets Received H8000 Element No 83
(new H8000)
DOCTSEND Terminating Side Oc int(10) num no only for (no H300 field): 0
tets Send H8000 Element No 81
(new H8000)
DPACKLOST Terminating Side int(10) num no only for (no H300 field): 0
Pack ets Lost H8000 Element No 84
(new H8000)
A31003-H3460-M104-4-76A9, July 2012


DPACKRCVD Terminating Side int(10) num no only for (no H300 field): 0
Pack ets Received H8000 Element No 82
(new H8000)
DPACKSENT Terminating Side int(10) num no only for (no H300 field): 0
Pack ets Send H8000 Element No 80
(new H8000)
DRESINFO Terminating Side int(1) num no only for (no H300 field): 0
Res ervation Used H8000 Element No 79
(new H8000)
DTOSUSED Terminating Side int(3) num no only for (no H300 field): 0
TOS Used H8000 Element No 78
(new H8000)
DTRNSDELY Terminating Side int(10) num no only for (no H300 field): 0
Aver age Transmis- H8000 Element No 86
(new H8000) sion De lay
EGCARRIER Egress Carrier Iden- char(6) text no only for (no H300 field): Blank
tifi cation H8000 Element No 22
(new H8000)
END10 end-of-connection int(1) num. yes H300 ger/eng: END10 0
1/10 of a second R6.5/6.6: END10
ENDDAY end-of-connection int(2) num. yes H300 ger/eng: ENDDAY 0
day R6.5/6.6: ENDDAY
ENDHOUR end-of-connection int(2) num. yes H300 ger/eng: ENDHOUR 0
hour R6.5/6.6: ENDHOUR
ENDMIN end-of-connection int(2) num. yes H300 ger/eng: ENDMIN 0
minute R6.5/6.6: ENDMIN
ENDMONTH end-of-connection int(2) num. yes H300 ger/eng: ENDMONTH 0
month R6.5/6.6: ENDMONTH
ENDSEC end-of-connection int(2) num. yes H300 ger/eng: ENDSEC 0
sec ond R6.5/6.6: ENDSEC
ENDYDAY end-of-connection int(3) num. no H300 ger/eng: ENDYDAY 0
day of the year R6.5/6.6: ENDYDAY
ENDYEAR end-of-connection int(4) num. yes H300 ger/eng: ENDYEAR 0
year R6.5/6.6: ENDYEAR
EVENTID Indentification of int(1) num. no only for (no H300 field): Blank
Event H8000 Element No 107
(new H8000)
A31003-H3460-M104-4-76A9, July 2012

EXPENS expensive connec- char(10) text no >= H300 V3.4 ger/eng: EXPENS 0
tion / def: 1 (0-3) R6.5/6.6: LCRXPATH
(AMO-TEXT) Values:
0 = BILLIG = Inexpensive connec
tions
1 = TEUER= Expensive connec tions
2 = GRATIS_A = Free of charge A-
party
3 = GRATIS_B = Free of charge B-
party
FACA facility number/ char(5) text no >= H300 UNITY ger/eng: FACA blank
param eter for FAX/ R6.5/6.6: FACA
(new US) TTA access - This parameter is provided as part of
BREAKIN NI2 PRI support
FACB facility number/ char(5) text no >= H300 UNITY ger/eng: FACB blank
param eter for FAX/ R6.5/6.6: FACB
(new US) TTA access - This parameter is provided as part of
BREAKOUT NI2 PRI support
FAXPAGES Number of Fax Pag- int(10) num. no only for (no H300 field): 0
es Sent / Received H8000 Element No 102
(new H8000)
FIXTEXT Fixed Text Standard Element 0
FLAG1 generation of flag char(2) text no H300 ger/eng: FLAG1 blank
byte 1 (only using data processing sys tem
(old) / only using DVA)
The generation of flag byte one, only
if using a data processing system be-
hind PBX.
FLAG2 generation of flag char(2) text no H300 ger/eng: FLAG2 blank
byte 2 (only using data processing sys tem
(old) / only using DVA)
The generation of flag byte two, only

if using a data processing system be-
hind PBX.
FRL BG Facility Restric- int(1) num. no only for (no H300 field): 0
tion Level H8000 Element No 98
(new H8000)
GENID ID of generating char(15) text no only for (no H300 field): H5000 blank
gate keeper
(new H5000)
GENLV0 node number of ge- int(3) num. no No H300 element 0
ner ating node
(only COL)
A31003-H3460-M104-4-76A9, July 2012


GENLV1 subdomain number int(3) num. no No H300 element 0
of generating node
(only COL)
GENLV2 domain number of int(2) num. no No H300 element 0
gen erating node
(only COL)
GLOBLLV0 node number of leg int(3) num. no >= H300 UNITY ger/eng: GLOBLLV0 0
id - global for node (0-999) on H300 E3.0 ger/eng: LEGLV0
on H300 E1.0/2.0 ger/eng: CALLEV0
on H300 V3.4 ger/eng: CALLN ODE
identical with LEGLV0
GLOBLLV1 subdomain number int(3) num. no >= H300 UNITY ger/eng: GLOBLLV1 0
of local global (leg) (0-255) on H300 E3.0 ger/eng: LEGLV1
id - global for node on H300 E1.0/2.0 ger/eng: CALLEV1
GLOBLLV2 domain number of int(2) num. no >= H300 UNITY ger/eng: GLOBLLV2 0
lo cal global (leg) id (0-31) on H300 E3.0 ger/eng: LEGLV2
- glo bal for node on H300 E1.0/2.0 ger/eng: CALLEV2
GLOBLNODE Local Global Node char(10) text no only for (no H300 field): Blank
ID / Leg ID H8000 Element No 121
(new H8000)
GLOBLSEQ local global (leg) id, int(32) num. no >= H300 UNITYger/eng: 0
if a target user may GLOBLLSEQ
be changed with an on H300 E3.0 ger/eng: LEGSEQ
exist ing connec- >= H300 V3.4 ger/eng: CALLSEQU
tion, a new local glo-
bal (leg)_id will be identical with LEGSEQ
generated, the tread
(global) call_id it self H8000 Element No 122
wouldn’t be
changed - global for
node
GWCODE gateway access char(5) text no only for (no H300 field): H5000 blank
code
(new H5000)
H150INFO Type of call (e.g. char(2) text no only for (no H300 field): 2
outg., inc. ...) H150-LAN and H150-ALL
(new H150)
H5CALLINFO Call Forwarding / Di char(1) text no only for (no H300 field): H5000 C
verting
(new H5000)
A31003-H3460-M104-4-76A9, July 2012

HOLDDUR hold duration in 1/10 int(5) num. no >= H300 UNITY ger/eng: 0
seconds (0- HOLDDUR
(new)(US) 65535)
(IM Pakage)
ICNINRID Incoming IC/ICN int(1) num. no only for (no H300 field): 0
Rout ing Indicator H8000 Element No 60
(new H8000)
ICNOUTRID Outgoing IC/ICN int(1) num. no only for (no H300 field): 0
Rout ing Indicator H8000 Element No 62
(new H8000)
ICNRSTAT IC/ICN Call Event int(2) num. no only for (no H300 field): 0
Sta tus H8000 Element No 61
(new H8000)
IDPP station CDR char- char(10) text no H300 ger/eng: IDPP 0
(old) gees, GET function- / def: 1 only GET functionality (charge data
(AMO-TEXT) ality recording per station) with format
No.>=97
The output of the station ID as a text
string (administered through AMO-
TEXT), only GET-function ality
(charge data recording per station)
INCACONDUR Incoming Carrier int(26) num. no only for (no H300 field): Blank
Con nect Time H8000 Element No 50
(new H8000)
INCARELDUR Outgoing Carrier Re int(26) num. no only for (no H300 field): Blank
lease Time H8000 Element No 53
(new H8000)
INFOTYPE type of information char(10) text no >= H300 E3.0 ger/eng: INFO TYPE 0
/ def: 1 (0-2)
(AMO-TEXT) If charging information from carri er,
then units or amounts. Not used in
the US.
INGCARRIER Ingress Carrier char(6) text no only for (no H300 field): Blank
Identifi cation H8000 Element No 21
(new H8000)
INPHCONT Incoming phone- int(10) text no only for (no H300 field): Blank
con text H8000 Element No 105
(new H8000)
INTNBCHA B-channel of the int(2) num. no >= H300 E2.0 ger/eng: 0
real trunk number of H8:int(10) INTNBCHA
(+H8000) the non-record point H8000 Element No 33
INTNLIST imaginary trunk int(30) num. no >= H300 E1.0 ger/eng: INTNLIST 0
num ber created of
INT NREAL H8000 Element No 126
A31003-H3460-M104-4-76A9, July 2012


INTNREAL real trunk number of int(5) num. no >= H300 E1.0 ger/eng: INT NREAL 0
the non-recording R6.5/6.6: DTRUNKID
point (see TKNO- H8000 Element No 126
REAL)
The real trunk number of non-re
cording point (see also TKNO RE-
AL). This field represents the “real”
trunk number of the non- record-ing
point. But again, forget the word
“trunk”, as this field actu ally means
“line” number. This field is taken from
the internal “line” number of a chan-
nel. For analog trunks, each analog
trunk channel has its own unique
“line” number. For digital trunks,
each of the channels on a digital
trunk span share a common “line”
num ber, so you cannot tell which “B-
channel” is being used. If a sta tion-
to-station (internal) call pro duces a
CDR record, INTNREAL will display
the “line” number of the called sta-
tion.
Example #1:
If station 2001 dials 9-972-355-
4321, then the CDR record will show
“2001” in Field 15 (CALLIP TY), “9” in
field 18 (ROUTCN), “9723554321” in
field 16 (DESTP TY), the trunk line
number in field 19 (TKNOREAL),
and the station (2001) line number in
field 20 (INTNREAL). So for station
calls, the data in this field is not need-
ed, as we already know the station
number. We really do not need the
“line” number in this example.
Example #2:
If a trunk call enters the HP4K, then
exits the HP4K on another trunk (tan-
dem call), the CDR fields TKNORE-
AL and INT NREAL show the “line”
numbers for both trunks that were
used. This example is the only prac-
tical use for the field INTNREAL.
A31003-H3460-M104-4-76A9, July 2012

INTNTGRID Incoming Trunk int(1) num. no only for (no H300 field): 0
Group Signaling H8000 Element No 38
(new H8000) Type
INTNTRGR real trunk group int(3) num. no >= H300 UNITY ger/eng: INT NTR- 0
num ber of the non- (0-512) GR
(new) record ing point H8:int(16) When the nonrecording point is a line
(+H8000) (see INT NREAL) (station) instead of a trunk, zero
(000) is output here.
H8000 Element No 32
JIPINFO Jurisdiction Informa int(10) num. no only for (no H300 field): 0
tion Parameter (JIP) H8000 Element No 44
(new H8000)
JIPSOURCE JIP Source Indicator int(1) num. no only for (no H300 field): 5
H8000 Element No 42
(new H8000)
KEYLV0 node number of key int(3) num. no >= H300 E3.0 ger/eng: KEYLV0 0
line used party
KEYLV1 subdomain number int(3) num. no >= H300 E3.0 ger/eng: KEYLV1 0
of key line used par-
ty
KEYLV2 subdomain number int(2) num. no >= H300 E3.0 ger/eng: KEYLV2 0
of key line used par-
ty
KEYPTY key line used party, char(22) text no >= H300 E3.0 ger/eng: KEYPTY blank
the selected line
(number) on a key For information about the right or left
phone provid ing justified output field, see CAL LEPTY
multiple lines description of item
LAYHIGINFO High-Layer Com- int(1) num. no only for (no H300 field): 0
(new H8000) patibil iy Information H8000 Element No 58
Delivery
LAYLOWINFO Low-Layer Compat- int(1) num. no only for (no H300 field): 0
(new H8000) ibil iy Information H8000 Element No 57
Delivery
LCALLENO length of the called int(2) num. no >= H300 E3.0 0
par ty (0-22) ger: LCALLENR
eng: LCALLENO
LCALLENO length of the called int(2) num. no >= H300 E3.0 0
(LCALLENR) par ty (0-22) ger: LCALLENR
eng: LCALLENO
LCRROUT LCR route char(2) text no only for (no H300 field): blank
H150-LAN and H150-ALL
(new H150)
A31003-H3460-M104-4-76A9, July 2012


LCRROUT LCR route char(2) text no only for (no H300 field): blank
H150-LAN and
(new H150) H150-ALL
LDESTNO length of the destina int(2) num. no >= H300 E3.0 0
(LDESTNR) tion number (0-22) ger: LDESTNR
eng: LDESTNO
R6.5/6.6: LDESTNO
LISTTYPE Type of station, char(16) text no >= H300 ger/eng: LISTTYPE blank
CDR list type as a only GET functionality (charge data
(old) text string, only GET recording per station) with format
(AMO-TEXT) functionality No.>=97
Values:
IND = Individual call charge calcu
lation
SUM = Sum call charge calcula tion
(partial calculation.)
TOTAL = Total call charge calcu
lation
LRNNO Location Routing int(10) num. no only for (no H300 field): 0
(new H8000) Num ber (LRN) H8000 Element No 45
LRNSOURCE LRN Source Indica- int(1) num. no only for (no H300 field): 5
(new H8000) tor H8000 Element No 43
MEDIATYPE Media Type int(1) num. no only for (no H300 field): 0
H8000 Element No 104
(new H8000)
MOBUCLV0 node number of mo- int(3) num. no >= H300 E3.0 ger/eng: MOBUCLV0 0
bile user calling par-
(not netwide) ty
MOBUCLV1 subdomain number int(3) num. no >= H300 E3.0 ger/eng: MOBUCLV1 0
of mobile user call-
(not netwide) ing par ty
MOBUCLV2 domain number of int(2) num. no >= H300 E3.0 ger/eng: MOBUCLV2 0
mo bile user calling
(not netwide) party
MOBUCPTY mobile user calling char(22) text no >= H300 E3.0 ger/eng: MOBUCP TY blank
par ty, user identi-
(not netwide) fies at calling station For information about the right or left
with PIN justified output field, see CAL LEPTY
description.
MODEM modem pool num- char(2) text no only for (no H300 field) blank
ber R6.5/6.6: MODEM
(new R6.5/
R6.6)
A31003-H3460-M104-4-76A9, July 2012

MODEM modem pool num- char(2) text no only for (no H300 field) blank
ber R6.5/6.6: MODEM
(new R6.5/
R6.6)
MSGNO consecutive num- int(4) num. no H300 ger: MSGNR 0
ber of message by H8:int(6) H300 eng: MSGNO
S&F (Store a. For- H8000 Element No 1
(+H8000) ward) con nection
MSN MSN used char(11) text no only for (no H300 field): blank
H150-LAN and H150-ALL (no val ue)
(new H150)
NCT indicate calls in char(1) “-” or no >= H300 UNITY ger/eng: NCT “-”
which network call- “N” R6.5/6.6: NCT
(new US) transfer (NCT) was
successful “-” dash = empty
N = true
A flag, indicating that a network call

transfer (NCT) was suc cessfully per-
formed. In a network call transfer, the
transfer is per formed in the public
network and all connections via the
HiPath 4000 are released. CDR of
HiPath 4000 is not able to monitor
charg ing of the remaining call any
more (1 char)
NETCARA access code of the int(4) num. no >= H300 UNITY ger/eng: NET CARA 0
net work carrier of R6.5/6.6: NETCARA
(new US) the BREAKIN trunk
NETCARB access code of the int(4) num. no >= H300 UNITY ger/eng: NET CARB 0
net work carrier of R6.5/6.6: NETCARB
(new US) the BREAKOUT
trunk
NETPULS pulses, charge info int(5) num. no >= H300 E3.0 ger/eng: 0
from net (0- NETPULS
65535)
NETSVCA type of service for int(2) num. no >= H300 UNITY ger/eng: 0
long distance carrier NETSVCA
(new US) for BREAKIN R6.5/6.6: NETSVCA
NETSVCB type of service for int(2) num. no >= H300 UNITY ger/eng: 0
long distance carrier NETSVCB
(new US) for BREAKOUT R6.5/6.6: NETSVCB
A31003-H3460-M104-4-76A9, July 2012


NETTYPE network description char(10) text no >= H300 V3.4 ger/eng: NETTYPE 0
/ def: 1 (0-3) Values are:
(AMO-TEXT) ANA = Analog network
IDN = Integrated Data Network
ISDN = Integrated Services Digi tal
Network
NODETXT node indentification char(17) text no only for (no H300 field) blank
(text) R6.5/6.6: NODEID
(new R6.5/
R6.6)
NODETXT node indentification char(17) text no only for (no H300 field) blank
(text) R6.5/6.6: NODEID
(new R6.5/
R6.6)
ORGNATADR Orig. Nature of Ad int(3) num. no only for (no H300 field): 0
dress H8000 Element No26
(new H8000)
ORGNATADR Orig. Nature of Ad int(3) num. no only for (no H300 field): 0
dress H8000 Element No26
(new H8000)
OSAA operator service ac int(1) num. no >= H300 UNITY ger/eng: 0
cess for BREAKIN OSAA
(new US) R6.5/6.6: BEARERA
OSAB operator service ac int(1) num. no >= H300 UNITY ger/eng: 0
cess for BREAK- OSAB
(new US) OUT R6.5/6.6: BEARERB
OTCACON Outgoing Carrier int(26) num. no only for (no H300 field): Blank
DUR Con nect Time H8000 Element No 52
(new H8000)
OUTDAY current date of the int(3) num. no H300 ger/eng: OUTDAY 0
out put day of the only on H300 V3.4 ger:
year OUTDAYN
R6.5/6.6: OUTYDAY
OUTDAYC current date of the char(10) text no H300 ger/eng: OUTDAYC 0
out put name of the / def: 1 R6.5/6.6: OUTDAYC
(AMO-TEXT) day
OUTDAYN current date of the int(2) num. no H300 ger/eng: OUTDAYN 0
out put day R6.5/6.6: OUTDAYN
OUTHOUR current date of the int(2) num. no H300 ger/eng: OUTHOUR 0
out put hour R6.5/6.6: OUTHOUR
OUTMIN current date of the int(2) num. no H300 ger/eng: OUTMIN 0
out put minute R6.5/6.6: OUTMIN
A31003-H3460-M104-4-76A9, July 2012

OUTMONC current date of the char(10) text no H300 ger/eng: OUTMONC 0
out put name of the / def: 2 R6.5/6.6: OUTMONC
(AMO-TEXT) month
OUTMONN current date of the int(2) num. no H300 ger/eng: OUTMONN
out put month R6.5/6.6: OUTMONN
OUTSEC current date of the int(2) num. no H300 ger/eng: OUTSEC 0
out put second R6.5/6.6: OUTSEC
OUTYEAR current date of the int(4) num. no H300 ger/eng: OUTYEAR 0
out put year R6.5/6.6: OUTYEAR
PARTYINFO User-to-User Infor- int(1) num. no only for (no H300 field): 0
ma tion / Fast Select H8000 Element No 59
(new H8000)
PAYPART paying party, char- char(22) text no H300 ger: PAYPART blank
gee of a connection H8:char(2 0) 0-9,*,# H300 eng: CHRGEE
(+H8000) R6.5/6.6: SRCNO
(DEFPP = define PAYPART)

H8000 Element No 13
PIN personal ID char(12) text no H300 ger: VIDCARD blank
H300 eng: PIN
R6.5/6.6: DISAPIN
PINLEN length of the per- int(2) num. no H300 ger: LIDCARD 0
sonal ID (0-12) H300 eng: PINLEN
PPLV0 node number of int(3) num. no >= H300 E3.0 ger/eng: 0
paying party (0-999) PPLV0
>= H300 E1.0 ger/eng:
LEVEL0
>= H300 V3.4 ger/eng:
NODENR
PPLV1 subdomain number int(3) num. no >= H300 E3.0 ger/eng: 0
of paying party (0-255) PPLV1
PPLV2 domain number of int(2) num. no >= H300 E3.0 ger/eng: 0

paying party (0-31) PPLV2
>= H300 E1.0 ger/eng:
LEVEL2
PRICIC PRI CIC char(4) text no only for (no H300 field): blank
H150-LAN
(new H150)
PRINODAL PRI Nodal Service char(2) text no only for (no H300 field): blank
H150-LAN
(new H150)
PRIWATS PRI WATS-Band char(1) text no only for (no H300 field): blank
H150-LAN
(new H150)
A31003-H3460-M104-4-76A9, July 2012


QUEUEDUR queuing duration, int(5) num. no >= H300 E3.0 ger/eng: 0
total queuing dura- QUEUEDUR
tion (call queue of
attendent) in 1/10
seconds
RECEIVID ID of receiving gate char(15) text no only for (no H300 field): blank
keeper H5000
(new H5000)
RECID unique Record ID char(59) text no only for (no H300 field): blank
H8000 Element No 6
(new H8000)
RECIDENT Record Type / Iden- int(8) num no only for (no H300 field): 00000
tifi cation for used H8000 Element No 2 000
(new H8000) format
RECNO consecutive num- int(32) num. no H300 ger: RECNR 0
ber of the record to (1- H300 eng: RECNO
(old) be output for each 9999) R6.5/6.6: RECNO
selection group
RECPT record point int(1) num. no >= H300 E1.0 ger/eng: 0
0=transit between (0-4) RECPT
sys tems
1=breakout to cen-
tral office
2=Recording direct
at origin
3=Recording direct
at origin and break-
out to central office
4=Incoming
RECTYPE record type int(1) num. no >= H300 UNITY ger/eng: 3
0=Empty (0-3) (yes if RECTYPE
(new) 1=only Accounting UNITY)
2=only Traffic
3=Accounting and
traf fic
RELDUR Call Release Time int(26) num. no only for (no H300 field): Blank
H8000 Element No 49
(new H8000)
RING10 ring duration of part int(1) num. no >= H300 E3.0 ger/eng: 0
1/ 10 seconds with RING10
format minute:sec-
ond:1/ 10second
RINGDUR ring duration, total int(3) num. no >= H300 V3.4 ger/eng: 0
ring duration in for- H8:int(26) RINGDUR H8:Bla
(+H8000) mat 1/10 seconds H8000 Element No 48 nk
A31003-H3460-M104-4-76A9, July 2012

RINGMIN ring duration of part int(2) num. no >= H300 E3.0 ger/eng: 0
minutes with format RINGMIN
minute:second:1/
10second
RINGSEC ring duration of part int(2) num. no >= H300 E3.0 ger/eng: 0
seconds with format RINGSEC
minute:second:1/
10second
ROUTCC route code as a text char(10) text no H300 ger/eng: 0
string / def: 6 (0- ROUTCC
(AKZ2) 999’999
)
(AMO-TEXT)
ROUTCN route code int(6) num. no >= H300 V3.4 ger/eng: 0
ROUTCN
(AKZ1) R6.5/6.6: ACCESSC
ROUTESEL Route Selection int(1) num. no only for (no H300 field): 0
H8000 Element No29
(new H8000)
RTINGLV0 node number of redi int(3) num. no >= H300 E3.0 ger/eng: 0
recting party RTINGLV0
RTINGLV1 subdomain number int(3) num. no >= H300 E3.0 ger/eng: 0
of redirecting party RTINGLV1
RTINGLV2 domain number of int(2) num. no >= H300 E3.0 ger/eng: 0
redi recting party RTINGLV2
RTINGPTY redirecting party, char(22) text no >= H300 E3.0 ger/eng: blank
party that redirects RTINGPTY
a call
party who forwarded this call (A- par-
ty - in record of B-party)
RTIONLV0 node number of redi int(3) num. no >= H300 E3.0 ger/eng: 0
rection party RTIONLV0
RTIONLV1 subdomain number int(3) num. no >= H300 E3.0 ger/eng: 0
of redirection party RTIONLV1
RTIONLV2 domain number of int(2) num. no >= H300 E3.0 ger/eng: 0
redi rection party RTIONLV2
RTIONPTY redirection party, char(22) text no >= H300 E3.0 ger/eng: 0
party where a call is RTIONPTY
redirect ed to R6.5/6.6: DIVERTNO
RTPID indication secure int(1) num. no only for (no H300 field): Blank
RTP used H8000 Element No 108
(new H8000)
A31003-H3460-M104-4-76A9, July 2012


RURAL flag if rural call char(10) num. no >= H300 E3.0 ger/eng: 0
/ def: 1 (0-1) RURAL
(AM-TEXT)
SCPINFO SCP / Service Fea- int(3) num. no only for (no H300 field): 27
ture Codes H8000 Element No 63
(new H8000)
SECDUR Call Segment Dura- int(10) num. no only for (no H300 field): 0
tion H8000 Element No 9
(new H8000)
SELGRNO selection group num int(1) num. no H300 ger: SELGRUNU 0
ber (1-4) H300 eng: SELGRNO
>= H300 E3.0 eng:
SELGRUNO
R6.5/6.6: SELGRNO
SERVICE service code char(10) text no H300 ger/eng: SERVICE 0
/ def: 1 (0-6) R6.5/6.6: SERVICE
(AMO-TEXT) H8:char(1 7) H8000 Element No 64
(+H8000)
SHFININDS Ingress DS0 ID (In int(10) num. no only for (no H300 field): 0
gress Shelf) H8000 Element No24
(new H8000)
SHFINOUTDS Egress DS0 ID (In int(10) num. no only for (no H300 field): 0
gress Shelf) H8000 Element No25
(new H8000)
SHFOUINDS Ingress DS0 ID int(10) num. no only for (no H300 field): 0
(Egress Shelf) H8000 Element No36
(new H8000)
SHFOUOUTDS Egress DS0 ID int(10) num. no only for (no H300 field): 0
(Egress Shelf) H8000 Element No37
(new H8000)
SIDANI contain text strings char(25) text no >= H300 UNITY ger/eng: blank
re leated to the call- SIDANI
(new US) ing party
(Displayname des Anrufers)
SIGDATA indicates whether char(10) text no H300 ger/eng: SIGDATA 0
the output data / def: 1 (0-1) R6.5/6.6: ERRDATA
(AMO-TEXT) record is correct / in- H8000 Element No 66
(+H8000) correct or double
SIGTYPINCO Ingress Signaling int(2) num. no only for (no H300 field): 0
Type - IN H8000 Element No30
(new H8000)
SIGTYPOUTC Egress Signaling int(2) num. no only for (no H300 field): 0
Type - OUT H8000 Element No31
(new H8000)
A31003-H3460-M104-4-76A9, July 2012

SOURCEIP source gateway char(15) text no only for (no H300 field): blank
H5000
(new H5000)
ST10 start-of-connection int(1) num. no H300 ger/eng: ST10 0
1/ 10 of a second R6.5/6.6: ST10
STDATETIME Start Time (date / char(26) da no only for (no H300 field): 1970-
time stamp to 1/10) tetime H8000 Element No 3 01-01
(new H8000) frac 01:01:
tion(1) 000
STDAY start-of-connection int(2) num. no H300 ger/eng: STDAY 0
day R6.5/6.6: STDAY
STHOUR start-of-connection int(2) num. no H300 ger/eng: STHOUR 0
hour R6.5/6.6: STHOUR
STMIN start-of-connection int(2) num. no H300 ger/eng: STMIN 0
minute R6.5/6.6: STMIN
STMONTH start-of-connection int(2) num. no H300 ger/eng: STMONTH 0
month R6.5/6.6: STMONTH
STNID station ID char(10) text no H300 ger: SUBSID 0
/ def: 1 (0-8) H300 eng: STNID
(AMO-TEXT) H8:int(3) H8:num (PAYPART)
(+H8000) R6.5/6.6: SOURCEID
H8000 Element No 40
STNSTAT Paying Party Query int(2) num. no only for (no H300 field): 9
Status H8000 Element No 46
(new H8000)
STSEC start-of-connection int(2) num. no H300 ger/eng: STSEC 0
second R6.5/6.6: STSEC
STYDAY start-of-connection int(3) num. no H300 ger/eng: STYDAY 0
day of the year R6.5/6.6: STYDAY
STYEAR start-of-connection int(4) num. no H300 ger/eng: STYEAR 0
year R6.5/6.6: STYEAR
SUBADCALLE Called Party Subad int(1) num. no only for (no H300 field): 0
dress Delivery H8000 Element No 56
(new H8000)
SUBADCALLI Calling Party Subad int(1) num. no only for (no H300 field): 0
dress Delivery H8000 Element No 55
(new H8000)
SUPLSERV supplement service char(10) text no >= H300 V3.4 ger/eng: 0
/ def: 2 (0-58) SUPLSERV
(change) H8:int(1) H8:num H8000 Element No 18
(+ chg. US)
(AMO-TEXT)
(+H8000)
A31003-H3460-M104-4-76A9, July 2012


SWITCHID Switch ID char(16) text no only for (no H300 field): blank
H8000 Element No 5
(new H8000)
SWP call phases char(10) text no >= H300 V3.4 ger/eng: 0
/ def: 2 (0-10) SWP
(change US)
(AMO-TEXT)
SWULOAD switching unit load, int(4) num. no >= H300 UNITY ger/eng: 0
1- 1000 promille SWULOAD
(new)
SYNCH indicates synchro- char(10) / text no only for (no H300 field) 0
nous call def: 1 (0-1) R6.5/6.6: SYNCH
(new R6.5/6.6
(AMO-MFORM)
SYSID system ID (system char(12) text no No H300 element blank
name)
(new COL)
SYSTYPE system typ char(12) text no No H300 element H300
H300
(new COL)
SYSVERS system verison char(12) text no No H300 element value
values: UV1.0?
(new COL)
TEXT01 Text Field 01 char(50) text no only for (no H300 field): Blank
H8000 Element No 27
(new H8000)
H8000 Element No 28
(new H8000)
(new H8000)
(new H8000)
(new H8000)
(new H8000)
(new H8000)
A31003-H3460-M104-4-76A9, July 2012

(new H8000)
(new H8000)
(new H8000)
(new H8000)
(new H8000)
(new H8000)
(new H8000)
(new H8000)
(new H8000)
(new H8000)
THRELV0 node number of int(3) num. no >= H300 UNITY ger/eng: 0
tread (global) call id, (0-999) THRELV0
(change) a new call id may be on H300 E3.0 ger/eng:
generat ed only in GLOBLV0
case af a new con-
nection. - glo blal for
network
THRELV1 subdomain number int(3) num. no >= H300 UNITY ger/eng: 0
of tread (global) call (0-255) THRELV1
(change) id - globlal for net- on H300 E3.0 ger/eng:
work GLOBLV1
THRELV2 domain number of int(2) num. no >= H300 UNITY ger/eng: 0
tread (global) call id (0-31) THRELV2
(change) - globlal for network on H300 E3.0 ger/eng:
GLOBLV2
A31003-H3460-M104-4-76A9, July 2012


THRENODE Thread Call Node char(10) text no only for (no H300 field): Blank
ID - Orig. Node (glo- H8000 Element No 124
(new H8000) bal for the network)
THRESEQ tread (global) call id int(10) num. no >= H300 UNITY ger/eng: 0
- globlal for network THRESEQ
(change) on H300 E3.0 ger/eng:
GLOBSEQ

TKNOBCHA B-channel of the int(2) num. no >= H300 E2.0 ger/eng 0
real trunk number of H8:int(10) TKNOBCHA
(+H8000) the non record point H8000 Element No 35
TKNOLIST imaginary trunk int(30) num. no H300 ger: TNLIST 0
num ber created of H300 eng: TKNOLIST
TKNO REAL (see
AMO- FBTN) H8000 Element No 127
TKNOREAL real trunk number of int(30) num. yes H300 ger: TNREAL 0
re cording point (0- H300 eng: TKNOREAL
65535) R6.5/6.6: STRUNKID

TKNOTRGR real trunk group int(3) num. yes >= H300 UNITY ger/eng: 0
num ber of record- H8:int(16) (0-512) TKNOTRGR
(new) ing point H8000 Element No 34
(+H8000)
TKNOTRGRID Outgoing Trunk int(1) num. no only for (no H300 field): 0
Group Signaling H8000 Element No 39
(new H8000) Type
TOLLNO Toll-Free Dialed char(10) text no only for (no H300 field): Blank
Num ber H8000 Element No 14
(new H8000)
TRANSCNT number of passed int(2) num. no >= H300 E1.0 ger/eng: 0
through transit (0-99) TRANSCNT
nodes
TRANSDN Transferred from Di int(20) num no only for (no H300 field): Blank
rectory Number H8000 Element No 123
(new H8000)
TRANSFER indicates station char(10) / text no only for (no H300 field) 0
trans fers def: 1 (0-1) R6.5/6.6: TRANSFER
(new R6.5/6.6
(AMO-MFORM)
TRANSRATE Transfer Rate int(10) num. no only for (no H300 field): blank
H8000 Element No 17
(new H8000)
A31003-H3460-M104-4-76A9, July 2012

TRNSFLV0 node number of int(3) num. no >= H300 E3.0 ger/eng: 0
trans fering party - TRNSFLV0
(attendent console) >= H300 E2.0 ger/eng:
ATTLEV0
TRNSFLV1 subdomain number int(3) num. no >= H300 E3.0 ger/eng: 0
of transfering party - TRNSFLV1
(at tendent console) >= H300 E2.0 ger/eng:
ATTLEV1
TRNSFLV2 domain number of int(2) num. no >= H300 E3.0 ger/eng: 0
transfering party - TRNSFLV2
(at tendent console) >= H300 E2.0 ger/eng:
ATTLEV2
TRNSFPTY transfering party - char(22) text., no >= H300 E3.0 ger/eng: blank
(at tendent con- 0-9,*,# TRNSFPTY
sole), party that H300 ger: ATTNR
transferred a call H300 eng: ATNDNO
UNANS through connect / char(10) text no >= H300 E2.0 ger/eng: Y (lang
no through connect / def: 1 (0-1) UNANS indep)
(AMO-TEXT)
on H300 V3.4/E1.0 ger/eng:
UNITERAS (see b.)
UNITERAS deletion of the sta- char(22) text no H300 ger/eng: UNITERAS Y
tion CDR resettable / def: 1 (0-1) (lang.
(AMO-TEXT) counter after output, (charge data recording per sta tion) indep)
only GET function-
ality
ZONE distance zone char(10) text no >= H300 V3.4 ger/eng: 0
/ def: 3 0-209 ZONE
(AMO-TEXT)
ZONEBIT bit information dis- char(12) num no only for (no H300 field): 00000
tance zone H5000 00000
(new H5000) 00
A31003-H3460-M104-4-76A9, July 2012


6.2.1 Fixed Values in FTBL Elements

The following table contains a list and a short description of the pre-defined (fixed) values that
can be assigned to the individual elements.
Short name Long name Value description (engl.) Element description

(ger.)
ATTCALLR attendant intercept 0, internal busy
reason, reason for 1, external busy
(new H4000) the intercept 2, undetermined call busy
3, no answer
4, not authorized
5, DID restriction
6, do not disturb,
7, not possible
8, not available
9, no pathway
10, insufficient data
11, after check
13, busy verification
14, busy verification with busy partner
15, busy verification with locked partner
16, held call no answer
17, recall hold
18, recall
19, msg wait cb
20, recall trunk
21, bes_o_btln
22, frei_o_btln
23, recall after SR
24, call after SR
25, direct call after SR
26, diverted call after SR
Table 6-43 Fixed Values in FTBL Elements
A31003-H3460-M104-4-76A9, July 2012


(ger.)
ATTCALLT attendant call type 0, EMERGENCY_CALL
1, HOTLINE_CALL
(new H4000) 2, LOCAL_FIRST_CALL,
3, LOCAL_RECALL
4, LOCAL_PRIO_CALL
5, CO_RECALL
6, CO_SERIAL_CALL
7, CO_IN_CONSULTATION
8, CO_ON_HOOK_IN_CONS
9, TIE_RECALL
10, TIE_SERIAL_CALL
11, TIE_IN_CONSULTATION
12, TIE_ON_HOOK_IN_CONS
13, OVFL_LOC_FIRST_CALL
14, OVFL_LOC_PRIO_CALL
15, OVFL_CO_FIRST_CALL
16, OVFL_TIE_FIRST_CALL
17, PERSONAL_CALL
18, ATND_LOOP_TRANSFER
19, CO_FIRST_CALL
20, MLPP_FLASH_OV
21, MLPP_FLASH
22, MLPP_IMMED
23, MLPP_PRTY
Table 6-43 Fixed Values in FTBL Elements (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012



(ger.)
BAUD transmission 000 = 0 Baud 10 digits, administr. by AMO-
speed 005 = 600 Baud Text, if the speed is not de-
006 = 2400 Baud fined by AMO-text-table, the
007 = 4800 Baud speed will be a number with 3
008 = 9600 Baud digits.
009 = 48000 Baud
010 = 64000 Baud
011 = variable
012 = X25 2400 Baud
013 = X25 4800 Baud
014 = X25 9600 Baud
015 = X25 48000 Baud
016 = X25 64000 Baud
017 = X25 variable
024 = 300 Baud
025 = 3600 Baud
026 = 12000 Baud
032 = 3510 Service
033 = Displaycopy
034 = BTX 1200 75 Modem
035 = BTX 1200 1200 Modem
036 = BTX 64k
037 = 3510 kind 1
038 = 3510 kind 2
039 = 3510 kind 3
040 = 3510 kind 4
041 = 3510 kind 5
042 = 3510 kind 6
043 = 3510 kind 7
044 = 3510 kind 8
045 = 3510 kind 9
046 = 3510 kind 10
047 = 3510 kind 11
049 = 900 Baud
050 = 1200 Baud
051 = 1800 Baud
052 = 7200 Baud
053 = 14400 Baud
054 = 16800 Baud
055 = 19200 Baud
056 = 56000 Baud
069 = 600 Baud asynchronous
075 = variable Baud asynchronous
A31003-H3460-M104-4-76A9, July 2012


(ger.)
BAUD 084 = 110 Baud asynchronous
(continued) 085 = 134,5 Baud asynchronous
CAUSE cause of connec- 000 = no cause
tion interrupt / 001 =unallocated (unassigned) number
clearing the call 002 = no route to specified transit network
003 = no route to destination
006 = channel unacceptable
016 = normal call clearing
017 = user busy
018= no user responding
019 = no answer from user (user alerted)
021 = call rejected
022 = number changed
026 = non-selected user clearing
027 = destination out of order
028 = invalid number format (address in-
complete)
029 = facility rejected
030 = response to STATUS ENQUIRY
031 = normal, unspecified
033 = circuit out of order
034 = no circuit/channel available
038 = network out of order
041 = temporary failure
A31003-H3460-M104-4-76A9, July 2012



(ger.)
CAUSE 042 = switching equipment congestion
(continued) 043 = access information discarded
044 = requested circuit/channel not avail-
able
047 = resource unavailable, unspecified
049 = Quality of Service not available
050 = requested facility not subscribed
052 = outgoing call barred
053 = outgoing call barred with CUG
054 = incoming call barred
055 = incoming call barred with CUG
057 = bearer capability not authorized
058 = bearer capability not presently avail-
able
063 = service or option not available, un-
specified
065 = bearer capability not implemented
066 = channel type not implemented
069 = requested facility not implemented
CAUSE 070 = only restricted digital information
(continued) bearer capability is available
079 =service or option not implemented,
unspecified
081 = invalid call reference value
082 = identified channel does not exist
083 = a suspended call exists, but this call
identity does not
084 = call identity in use
085 = no call suspended
086 = call having the requested call identity
has been cleared
088 = incompatible destination
091 = invalid transit network destination
095 = invalid message, unspecified
096 = mandatory information element is
missing
097 = message type non-existent or not
implemented
098 = message not compatible with call
state or message type non-existent or not
implemented
A31003-H3460-M104-4-76A9, July 2012


(ger.)
CAUSE 099 = information element non-existent or
(continued) not implemented
100 = invalid information element contents
101 = message not compatible with call
state
102 = recovery on timer expiry
111 = protocol error, unspecified
127 = interworking, unspecified
128 = HOP counter exceeded
129 = ACD PBK agent available
130 = ACD PBK divert
131 = ACD PBK end of shift
132 = circuit operational
133 = changeover
134 = user access busy
135 = not allowed SPV
136 = REV change n ALD at OAD
137 = REV change n ALD at DAD
138 = destination not optainalble
139 = out of order
CAUSE 140 = netw congestion
(continued) 141 = remote user intiated
142 = local proc error
143 = remote proc error
144 = remote user susp
145 = remote user resumed
146 = vacant code
147 = pre 0 dial err
148 = pre 1 dial err
149 = pre 1 not dial
150 = exc DGT rec
151 = miss routed call
152 = bc incomp src req
153 = src op violated
154 = NI2 protocol err
155 = not defined
CAUSE carrier, 0 = Unknown Reason 0 = unbekannter Grund
output of the com- 1 = Normal call hang-up 1 = normales Gesprächsende
(H5000) munication net- 2 = destination reject 2 = destination reject
work as a text 3 = lines busy 3 = Leistung besetzt
string 4 = out of service 4 = außer Betrieb
5 = destination busy 5 = Ziel besetzt
6 = no answer/abandoned 6 = keine Antwort/abandoned
Default : 1 Default : 1
A31003-H3460-M104-4-76A9, July 2012



(ger.)
CALLIONI originating Net- H4000 V1.0 H4000 V1.0
work ID of the call- 0 = private network 0 = internes Netwerk
(new H4000) ing party (privat / 1 = public network 1 = öffentliches Netwerk
public)
H4000 V2.0 H4000 V2.0
0 = private (no indication) 0 = intern /eigenes Netzwerk
(keine Identifikation)
1 = public tel 1 = öffentlich tel
2 = public data 2 = öffentlich data
3 = public isdn 3 = öffentlich isdn
4 = public foreign network 4 = öffentlich foreign network
5 = own network 1 5 = eigenes Netzwerk 1
... ...
29 = onn network 25 29 = eigenes Netzwerk 25
A31003-H3460-M104-4-76A9, July 2012

6.2.2 AMO Text Elements

The following table contains the list of AMO text elements. The individual values that can be
assigned to the elements are listed and explained.
Short name Long name Value description Element description

AOCTYPE advice of charge 0 = Advice of charges - during (“1 ..”) 0 = Gebühreninformation
the call (D_AOC) während des Gesprächs (D_AOC)
1 = Advice of charges - at end of (“2 ..”) 1 = Gebühreninformation bei Ge-
call (E_AOC) sprächsende (E_AOC)
2 = Advice of charges - during (“3 ..”) 2 = Gebühreninformation bei
call setup (S_AOC) Verbindungsaufbau (S_AOC)
BAUD transmission 0 = no speed specified (“000”) 0 = Keine Geschwindigkeits ang-
speed 2400 = 2400 Baud abe (“000”)
(AM) (10 digits, adminis- 4800 = 4800 Baud (“001”) 2400 = 2400 Baud
tr. by AMO-Text, if 9600 = 9600 Baud (“002”) 4800 = 4800 Baud
the speed is not 48000 = 48000 Baud (“003”) 9600 = 9600 Baud
defined by AMO- 64000 = 64000 Baud (“004”) 48000 = 48000 Baud
text-table, the (“005”) 64000 = 64000 Baud
speed will be a
number with 3 dig-
its)
CALCTYPE applied type of bill- CLOCK = charge pulse meter- (“1 ..”) CLOCK = Münztelefon (RURAL)
ing ing and sending, coinbox (RU- (“2 ..”) PULSES = Impulse / Beträge
RAL) vom AMT
PULSES = Units / amounts from (“3 ..”) WOUT = Vergebührung nach Zeit
carrier (CENTRAL OFFICE)
WOUT = Costs per time unit
CARRIER carrier, 0 = CARRIER_0 (intern) (“0 ..”) 0 = CARRIER_0 (intern)
output of the com- 1 = CARRIER_1 (“1 ..”) 1 = CARRIER_1
(AM) munication net- 2 = CARRIER_2 (“2 ..”) 2 = CARRIER_2
work as a text 3 = CARRIER_3 (“3 ..”) 3 = CARRIER_3
string 4 = CARRIER_4 (“4 ..”) 4 = CARRIER_4
5 = CARRIER_5 (“5 ..”) 5 = CARRIER_5
6 = CARRIER_6 (“6 ..”) 6 = CARRIER_6
7 = CARRIER_7 (“7 ..”) 7 = CARRIER_7
8 = CARRIER_8 (“8 ..”) 8 = CARRIER_8
9 = CARRIER_9 (“9 ..”) 9 = CARRIER_9
CFW indicates forward- 0 = Call forwarded 0 = Gespräch weitergeleitet
ed calls 1 = Call not forwarded 1 = Gespräch nicht weitergeleitet
(new R6.5/6.6
(AMO-MFORM)
Table 6-44 AMO Text Elements
A31003-H3460-M104-4-76A9, July 2012



CHOFCON type of connection 1 = Local (“1 ..”) 1 = Ortsverbindung
2 = Long distance (“2 ..”) 2 = Fernverbindung
(old) 3 = Local with limit value ex- (“3 ..”) 3 = Ortsverbindung mit Grenzw-
ceeded ertüberschreitung
4 = Long distance with limit val- (“4 ..”) 4 = Fernverbindung mit Grenzw-
ue exceeded ertüberschreitung
5 = No entry (“5 ..”) 5 = Kein Eintrag
6 = Rerouting (“6 ..”) 6 = Rerouting
CONF indicates confer- 0 = Conference 0 = Konferenze
ence call 1 = Normal 1 = Normal
(new R6.5/6.6
(AMO-MFORM)
CONNTYPE connection type OUTGO = Outgoing connec- (“0 ..”) GEHEND = Abgehende Verbind-
tions ungen
(AM) INCO = Incoming connections (“1 ..”) KOMMEND = Ankommende
(enhanced INTERN = Internal connections Verbindungen
2 values) ACACT = activity of attendant (“3 ..”) INTERN = Interne Verbindungen
LOAD = load of processor (“4 ..”) ACACT = Vermittlungsplatzaktiv-
(ADP / SWU) ität
(“5 ..”) LOAD = Systemlast (ADP / SWU)
CONNTYPE connection type 1 = Incoming connections (ext./ 1 = Ankommende Verbindungen (ext./
int.) int.)
(H5000) 2 = Outgoing connections (int./ 2 = Abgehende Verbindungen (int./ext.)
ext.) 3 = Interne Verbindungen (int./int.)
3 = Internal connections (int./ 4 = Transit (ext./ext.)
int.)
4 = Transit (ext./ext.)
COPIN class of pin 0 = No valid class of pin (“0 ..”) 0 = Keine PIN vorhanden
1 = Pin manual (“P ..”) 1 = PIN-Klasse_1
(AM) 2 = Pin long service (“P ..”) 2 = PIN-Klasse_2
3 = Pin 1 call service (“P ..”) 3 = PIN-Klasse_3
4 = Pin 1 private service (“P ..”) 4 = PIN-Klasse_4
5 = Project code for 1 call (“P ..”) 5 = PIN-Klasse_5
6 = ID card user (“P ..”) 6 = PIN-Klasse_6
7 = Class of service switchover (“P ..”) 7 = PIN-Klasse_7
8 = PIN -Class_8 (“P ..”) 8 = PIN-Klasse_8
COPIN class of pin (“0 ..”) 0 = Disa number (“0 ..”) 0 = Disa Nummber
(“P ..”) 1 = PIN (“P ..”) 1 = PIN
(only R6.5/6.6 - (“P ..”) 2 = Normal - Neither (“P ..”) 2 = Normal - keine DISA or PIN
MFORM ele- DISA or PIN
ment -
DISAIND)
Table 6-44 AMO Text Elements (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012


DESTPID / ST- identification num- 1 = Operator console (“1 ..”) 1 = Vermittlungsfernsprecher
NID ber of destination 2 = Main PABX set (“2 ..”) 2 = Hauptanlagensatz
number (new/con- 3 = Night server (“3 ..”) 3 = Nachtnebenstelle
(AMO-TEXT nect party) (uses 4 = Subscriber (“4 ..”) 4 = Teilnehmer
STNID) value from element 5 = Service module (“5 ..”) 5 = Service-Modul
(new) STNID) 6 = Special charging (“6 ..”) 6 = Spezielle Vergebührung
7 = Maintenance equipment (“7 ..”) 7 = Wartungseinrichtung
8 = Public phone (“8 ..”) 8 = Öffentlicher Fernsprechappa-
9 = Mobile user rat
10 = Number of the other line (“9 ..”) 9 = Mobiler Teilnehmer
(keyset) (“10 ..”) 10 = Fremde Leitungsnummer
(Keyset)
DESTPID identification num- 1 = Gateway 1 = Gateway
ber of destination 2 = Subscriber 2 = Teilnehmer
(new H5000) number
EXPENS expensive connec- 0 = Inexpensive connections (“0 ..”) 0 = Billig
tion 1 = Expensive connections (“1 ..”) 1 = Teuer
(AM) 2 = Free of charge A-party (“2 ..”) 2 = Gratis A-Tlnr
3 = Free of charge B-party (“3 ..”) 3 = Gratis B-Tlnr
EXPENS expensive connec- (“0 ..”) 0 = Inexpensive connec- (“0 ..”) 0 = Billig
tion tions (“1 ..”) 1 = Teuer
(only R6.5/6.6 - (“1 ..”) 1 = Expensive connec-
MFORM ele- tions
ment - LCR-
EXP)
IDPP station CDR char- ATND = Attendant console (“1 ..”) VF = Vermittlungsfernsprecher
gees, GET func- MTLC = Main PABX tie-line cir- (“2 ..”) HAS = Main PABX tie-line circuit
tionality cuit (“3 ..”) TLN = Teilnehmer
STN = Station (“4 ..”) AS = Amtssatz (Trunk)
TC = CDR per trunk
INFOTYPE type of information AMOUNT = Amounts from carri- (“1 ..”) AMOUNT = Beträge vom AMT
er (CENTRAL OFFICE) (“2 ..”) UNITS = Einheiten vom AMT
UNITS = Units from carrier
(CENTRAL OFFICE)
LISTTYPE Type of station, IND = Individual call charge cal- (“1 ..”) EINZEL = Einzelabrechnung
CDR list type as a culation (“3 ..”) TEIL = Teilabrechnung
text string, only SUM = Sum call charge calcula- (“2 ..”) TOTAL = Totalabrechnung
GET functionality tion (part calc.)
TOTAL = Total call charge cal-
culation
NETTYPE network descrip- ANA = Analog network (“0 ..”) ANA = Analog-Netz
tion IDN = Integrated Data Network (“1 ..”) IDN = Integriertes-Daten-Netz
(used but not ISDN = Integrated Services Dig- (“2 ..”) ISDN = Integriertes-Service- Dat-
def. in AM) ital Network en-Netz
A31003-H3460-M104-4-76A9, July 2012



OUTDAYC current date of the 1 = “Monday ..” 1 = “Montag ..”
output name of the 2 = “Tuesday ..” 2 = “Dienstag ..”
(R6.5/R6.6 - day 3 = “Wednesday ..” 3 = “Mittwoch ..”
MFORM ele- 4 = “Thursday ..” 4 = “Donnerstag ..”
ment - 5 = “Friday ..” 5 = “Freitag ..”
DAY) 6 = “Saturday ..” 6 = “Samstag ..”
7 = “Sunday ..” 7 = “Sonntag ..”
OUTMONC current date of the 1 = “January ..” 1 = “Januar ..”
output name of the 2 = “February ..” 2 = “Februar ..”
(R6.5/R6.6 - month 3 = “March ..” 3 = “März ..”
MFORM ele- 4 = “April ..” 4 = “April ..”
ment - 5 = “May ..” 5 = “Mai ..”
MONTH) 6 = “June ..” 6 = “Juni ..”
7 = “July ..” 7 = “Juli ..”
8 = “August ..” 8 = “August ..”
9 = “September ..” 9 = “September ..”
10 = “October ..” 10 = “Oktober ..”
11 = “November ..” 11 = “November ..”
12 = “December ..” 12 = “Dezember ..”
ROUTCC route code as a 0 = “00 ..” 0 = “00 ..”
text string 1 = “01 ..” 1 = “01 ..”
(AKZ2) 2 = “02 ..” 2 = “02 ..”
from 0 to 999999 3 = “03 ..” 3 = “03 ..”
(AM) 4 = “04 ..” 4 = “04 ..”
5 = “05 ..” 5 = “05 ..”
6 = “06 ..” 6 = “06 ..”
7 = “07 ..” 7 = “07 ..”
8 = “08 ..” 8 = “08 ..”
9 = “09 ..” 9 = “09 ..”
10 = 10 ..” 10 = 10 ..”
11 = “11 ..” 11 = “11 ..”
12 = “12 ..” 12 = “12 ..”
13 = “13 ..” 13 = “13 ..”
14 = “14 ..” 14 = “14 ..”
15 = “15 ..” 15 = “15 ..”
16 = “16 ..” 16 = “16 ..”
RURAL flag if rural call 0=rural (“0 ..”) 0=Münzfernsprecher
1=other terminal device (“1 ..”) 1=andere Endgeräte
SERVICE service VOICE = Voice connection (“0 ..”) VOICE = Sprachverbindung

TTX = Teletex (“1 ..”) TTX = Teletex
VTX = Interactive videotex (“2 ..”) BTX = Bildschirmtext
FAX = Facsimile (“3 ..”) FAX = Faksimile
DTE = data terminal (“4 ..”) DEE = Datenendeinrichtung
TTC = Teletex-telex converter (“5 ..”) TTC = Teletex-Telex-Umsetzer
A31003-H3460-M104-4-76A9, July 2012


SERVICE service (“0 ..) VCE = Voice connection (“0 ..”) VCE = Sprachverbindung
(“1 ..) DATA = data terminal (“1 ..”) DATA = Datenendeinrichtung
(only R6.5/R6.6 (“2 ..) FAX = Facsimile (“2 ..”) FAX = Faksimile
- MFORM)
SERVICE service 0 = Voice 0 = Sprache
1 = Data 1 = Daten
(new H5000)
SIGDATA indicates whether 0 = incorrect or double data set (“1 ..”) 0 = ungenauer oder doppelter
the output data 1 = correct data set Datensatz
(R6.5/R6.6 - record is correct / (“0 ..”) 1 = korrekter Datensatz
MFORM ele- incorrect or double
ment -
ERRDATA)
STNID station ID 1 = Operator console (“1 ..”) 1 = Vermittlungsfernsprecher
2 = Main PABX set (“2 ..”) 2 = Hauptanlagensatz
(AM) 3 = Night server (“3 ..”) 3 = Nachtnebenstelle
4 = Subscriber (“4 ..”) 4 = Teilnehmer
5 = Service module (“5 ..”) 5 = Service-Modul
6 = Special charging (“6 ..”) 6 = Spezielle Vergebührung
7 = Maintenance equipment (“7 ..”) 7 = Wartungseinrichtung
8 = Public phone (“8 ..”) 8 = Öffentlicher Fernsprechappa-
9 = Mobile user rat
10 = Number of the other line (“9 ..”) 9 = Mobiler Teilnehmer
(keyset) (“10 ..”) 10 = Fremde Leitungsnummer
(Keyset)
STNID station ID (“1 ..”) 1 = Attendant (“1 ..”) 1 = Vermittlungsfernsprecher
(“2 ..”) 2 = Subscriber (“2 ..”) 2 = Teilnehmer
(only R6.5/6.6 - (“3 ..”) 3 = Main PABX set (“3 ..”) 3 = Hauptanlagensatz
MFORM ele- (“4 ..”) 4 = Night server (“4 ..”) 4 = Nachtnebenstelle
ment - PARTY- (“5 ..”) 5 = CO amd PRI rate (“5 ..”) 5 = CO amd PRI rate trunk
ID) trunk (“6 ..”) 6 = Recorded and Music An-
(“6 ..”) 6 = Recorded and Music nouncement
Announcement (“7 ..”) 7 = NI voice device for initiating a
(“7 ..”) 7 = NI voice device for ini- call to a telecomputer
tiating a call to a telecomputer (“8 ..”) 8 = Relocated telecomputer office
(“8 ..”) 8 = Relocated telecom- station
puter office station
STNID station ID 1 = Gateway 1 = Gateway
2 = Subscriber 2 = Teilnehmer
(new H5000)
A31003-H3460-M104-4-76A9, July 2012



SUPLSERV supplement ser- 0 = Not defined (“0 ..”) 0 = Nicht definiert
vice 1 = Normal call (“1 ..”) 1 = Normalgespräch
(AM) 2 = Consultation call (“2 ..”) 2 = Rückfrageverbindung
3 = Call transfer (“3 ..”) 3 = Anrufübergabe
(change +9) 4 = Call back (“4 ..”) 4 = Rückruf
(+ chg. US + 14) 5 = Call fwd busy (“5 ..”) 5 = Anrufumleitung auf besetzten
6 = Call fwd unconditional Teilnehmer
7 = Call fwd noreply (“6 ..”) 6 = Unbedingte Anrufumleitung
8 = Call pickup (“7 ..”) 7 = Rufweiterschaltung / Umlei-
9 = Conference tung bei keiner Annahme
10 = Override (“8 ..”) 8 = Anrufübernahme
11 = Hunting group (“9 ..”) 9 = Konferenz
12 = Mail box (“10 ..”) 10 = Aufschalten
13 = Paging (“11 ..”) 11 = Sammelanschluß
14 = Dictation (“12 ..”) 12 = Briefkasten / Sprachspeich-
15 = Credit card charge er
16 = Reverse charging (“13 ..”) 13 = Personensuche (Blättern)
17 = Call defection (“14 ..”) 14 = Diktat
18 = Door opening (“15 ..”) 15 = Kreditkartenvergebührung
19 = Ring back (“16 ..”) 16 = Gebührenübernahme
20 = Hang up on hold (“17 ..”) 17 = Rufablenkung
21 = Hang up on queueing (“18 ..”) 18 = Türöffnung
(“19 ..”) 19 = Rufzustand / Freiton
(“20 ..”) 20 = Auflegen im Haltezustand
(“21 ..”) 21 = Auflegen in einer Warte-
schlange
A31003-H3460-M104-4-76A9, July 2012


SUPLSERV 22 = End of queueing (“22 ..”) 22= Ausgliedern aus der Warte-
(continued) 23 = Begin of queueing schlange
24 = Master transfer (“23 ..”) 23= Einhängen in die Warte-
25 = Recall schlange
26 = Intercept (“24 ..”) 24= Konferenz wird übergeben
27 = Central attendant (“25 ..”) 25= Wiederanruf
28 = No CDR with end of select (“26 ..”) 26 = Abwurf
29 = Busy (“27 ..”) 27= Umleitung zum zentralen
30 = CDR lost buffer Vermittlungsplatz
31 = AC activates night service (“28 ..”) 28= Keine Vergebührung ab
32 = AC deactivates night ser- Wahlende
vice (“29 ..”) 29= Besetzt
33 = AC pulls the jack (“30 ..”) 30= Hängengebliebenes Ge-
34 = AC reconnects the jack bührenticket
35 = AC out of service (“31 ..”) 31= Aktivierung Nachschaltung
36 = AC restart (“32 ..”) 32= Deaktivierung Nachtschal-
37 = Hang up in a hunting group tung
queue (“33 ..”) 33= Klinke ziehen
38 = hunting group busy (“34 ..”) 34= Klinke einstecken
39 = SWU and ADP load (“35 ..”) 35= VF außer Betrieb
40 = Transit (“36 ..”) 36= VF restart
41 = Rerouting (“37 ..”) 37= Auslegen in einer Sam-
42 = incoming call barred melanschluß - Warteschlange
(“38 ..”) 38= Sammelanschluß ist besetzt
(“39 ..”) 39= Prozessorauslastung
(“40 ..”) 40= Transit
(“41 ..”) 41= Wegoptimierung
(“42 ..”) 42= Kommender Ruf blockiert
A31003-H3460-M104-4-76A9, July 2012



SUPLSERV 43 = Destination out of service (“43 ..”) 43= Zielteilnehmer nicht im
(continued) 44 = Resource unavailable Betrieb
45 = Call rejected (“44 ..”) 44= Resource nicht verfügbar
46 = Unassigned number (“45 ..”) 45= Verbindung abgelehnt
47 = Account code (“46 ..”) 46= Nummer nicht vorhanden
48 = Conference activ (“47 ..”) 47= Zuordnungsnummer
49 = Conference passiv (“48 ..”) 48= Einberufer der Konferenz-
50 = Begin of HOLD “A” verbindung ist noch aktiv
51 = Begin of HOLD “B” (“49 ..”) 49= Einberufer der Konferenz-
52 = End of HOLD “A” verbindung ist ausgeschieden
53 = End of HOLD “B” (“50 ..”) 50= A Teilnehmer wird gehalten
54 = Hang up on HOLD “A” (“51 ..”) 51= B Teilnehmer wird gehalten
55 = Hang up on HOLD “B” (“52 ..”) 52= A Teilnehmer verlässt den
56 = Ringing after connect Haltezustand
(“53 ..”) 53= B Teilnehmer verlässt den
Haltezustand
(“54 ..”) 54= A Teilnehmer legt im Halte-
zustand auf
(“55 ..”) 55= B Teilnehmer legt im Halte-
zustand auf
(“56 ..”) 56= Klingeln nach Verbunden
SWP call phases (“0 ..”) SPACE = No call pro- (“0 ..”) LEER = Kein Vermittlungsvor-
cessing process gang
(AM) (“1 ..”) ENDS = End of call after (“1 ..”) ENDNB = Gesprächsende nach
seizure Belegung
(change US+ 1 (“2 ..”) ENDSEC = End of call af- (“2 ..”) ENDNA = Gesprächsende nach
value) ter transfer point Abschnitt
(“3 ..”) ENDL = End of call after (“3 ..”) ENDNG = Gesprächsende nach
limit value Grenzwert
(“4 ..”) SECS = Transfer point (“4 ..”) ABSNB = Abschnitt nach Bele-
after seizure gung
(“5 ..”) NEXTSEC = Transfer (“5 ..”) ABSNA = Abschnitt nach Ab-
point after transfer point schnitt
(“6 ..”) SECL = Transfer point af- (“6 ..”) ABSNG = Abschnitt nach Gren-
ter limit value zwert
(“7 ..”) LAS = Limit value after (“7 ..”) GRWNB = Grenzwert nach Bele-
seizure gung
(“8 ..”) LASEC = Limit value af- (“8 ..”) GRWNA = Grenzwert nach Ab-
ter transfer point schnitt
(“9 ..”) LAL = Limit value after (“9 ..”) GRWNG = Grenzwert nach Gren-
limit value zwert
(“10 ..”) SECACC = Transfer af- (“10 ..”) ABSNACC = Abschnitt nach Ac-
ter account code count Code
SYNCH indicates synchro- 0 = Synchronous 0 = Synchron
nour call 1 = Asynchronous 1 = Asynchron
(new R6.5/6.6
(AMO-MFORM)
A31003-H3460-M104-4-76A9, July 2012


TRANSFER indicates station (“0 ..”) SPACE = Call not in-
transfers volved in a transfer
(new R6.5/6.6 (“1 ..”) ATTND = Call involved in
(AMO-MFORM) a attendent transfer
(“2 ..”) XFER = Call involved in a
transfer
(“3 ..”) TIME = Call was > 18 hr
time limit and record was split
(this portion closed out and new
record started)
UNANS through connect / NTHRCONN = No through con- (“Y ..”) (language independent)
no through connect nect DURCHV = Durchgeschaltene Verbind-
(AM) THRCONN = Through connect ung
(“N ..”) NDURCHV = Nicht durchge-
schaltene Verbindung
UNITERAS deletion of the sta- Y = Resettable counter deleted (“Y ..”) Y (language independent) = Dif-
tion CDR resetta- or through connected ferenzzähler gelöscht oder durchver-
(AM) ble counter after N = Resettable counter not de- bunden
output, only GET leted or not through connected (“N ..”) N = Differenzzähler nicht gelöscht
functionality oder nicht durchverbunden
Attention: AMO-
TEXT for EV1.0
and V3.4
ZONE distance zone SPACE = Space LEER (0) = Leereintrag
INT01 = Internal01 - INT01 (1) = 1. Internzone -
INTnn = Internalnn INTnn = nn. Internzone
INT09 = Internal09 INT09 (9) = 9. Internzone
INC0 = Incoming01 ANK01 (11)= 1. ankommende Zone
INCnn = Incomingnn ANKnn = nn. ankommende Zone
INC09 = Incoming09 ANK09 (19) = 9. ankommende Zone
LOC = Local ORT (21) = Lokal Zone
NEAR = Nearby NAH 31)= Nahezone
CHRGFREE = Charge free GEBFREI = Gebührenfrei
CHRGINFO = Charge info from GEBINFO = Gebühreninformation vom
carrier Carrier
DIST01 = Distance01 FERN0 (51) = 1. Fernzone
DISTnn = Distancenn FERNnn = nn. Fernzone
DIST50 = Distance50 FERN50 (100) = 50. Fernzone
ABR01 = Abroad01 AUSL01 (101) = 1. Auslandszone
ABRnn = Abroadnn AUSLnn = nn. Auslandszone
ABR99 = Abroad99 AUSL99 (199) = 99. Aus
TIE01 = Tie01 QUER01 (201) = 1. Zone für Quer-
TIEnn = Tienn verbindungen
TIE09 = Tie09 QUERnn = nn. Zone für Querverbindun-
gen
QUER09 (209) = 9. Zone für Quer-
verbindungen
A31003-H3460-M104-4-76A9, July 2012



ZONE distance zone see element ZONEBIT see Element ZONEBIT
Default = 0 Default = 0
(only H5000)
ZONEBIT bit information The column ’Value’ is displayed in ZONE for H5000
distance zone
(new H5000)
A31003-H3460-M104-4-76A9, July 2012

Pre-defined Formats for Output Format Definition
6.3 Pre-defined Formats for Output Format Definition
Important:
The following pre-defined formats for defining the output format are available, and they apply
likewise to the output formats of H3000 and H2000 systems:
● Elements for Defining Input and Output Formats
● AM-WIN 1.0 – Format for AM-WIN 1.0
● AM-WIN 2.0 – Format for AM-WIN 2.0
● H4000_HP_AM – Output format from HiPath 4000 for HiPath AM
● HiPath 4000 Manager/Assistant PM – Output format for HiPath 4000 Manager/Assi-
stant PM V1.0
● H4000_HPAM_E164 – Output format from HiPath 4000 for HiPath AM
● H8000_AM – OpenScape Voice Output Format V1.0
● H8000_AM_V22 – OpenScape Voice Output Format V2.2 (Single System)
● OSV_AM – Open Scape Voice Output Format
● HP4M_AMPM_UV3.0 – Output format from HiPath 4000 V3 for HiPath 4000 V6
● HP4M_AMPM_UV4 – Output format from HiPath 4000 V4 for HiPath 4000 V6
● HP4M_AMPM_UV5 – Output format from HiPath 4000 V5 for HiPath 4000 V6
● HP4M_AMPM_UV6 – Output format from HiPath 4000 V6
● HP4M_PM_UV6 – Output format from HiPath 4000 V6
A31003-H3460-M104-4-76A9, July 2012


AM-WIN 1.0 – Format for AM-WIN 1.0

Legend:
No. = sequential element number; ET = element type: F = fixed text, V = variable element;
E = ending element; FTBL Name = FTBL element name; EIndex = element index;
L = element length; A = alignment; FI = pad character: Empty = space
NO ET Element Long name (eng) Position Lenght Align- filler

ment
1 F $ sign for record begin 1 1
2 V TKNOLIST trunk number 2-6 5 r
3 V PPLV2 domain of paying party 7-8 2 r 0
4 V PPLV1 subdomain of paying party 9-11 3 r 0
5 V PPLV0 node number of paying party 12-14 3 r 0
6 V PAYPARTY paying party 15-24 10 r
7 V STNID source id 25 1
8 V PIN PIN 26-37 12 l
9 V DESTPTY destination number 38-59 22 l
10 V CONTOT call duration in 1/10 seconds 60-65 6 r 0
11 V ENDYEAR end of call - year 66-67 2 r 0
12 V ENDMONTH end of call - month 68-69 2 r 0
13 V ENDDAY end of call - day 70-71 2 r 0
14 V ENDHOUR end of call - hour 72-73 2 r 0
15 V ENDMIN end of call - minute 74-75 2 r 0
16 V ENDSEC end of call - second 76-77 2 r 0
17 V CHRGUNIT call charge units 78-81 4 r 0
18 V SERVICE service code 82 1
19 V ZONE call zone 83-85 3 r 0
20 V CARRIER carrier 86 1
21 V ROUTCC route code 87-92 6 l
22 V CONNTYPE call type 93 1
23 V EXPENS flag for “expensive facility” 94 1
24 V GENLV2 domain of node generating the 95-96 2 r 0
call record
Table 6-45 AM-WIN 1.0 - Output format for AM-WIN 1.0
A31003-H3460-M104-4-76A9, July 2012


ment
25 V GENLV1 subdomain of node generating 97-99 3 r 0
the call record
26 V GENLV0 node number of node generat- 100-102 3 r 0
ing the call record
27 V COPIN PIN category 103 1
28 V DISPCHRG display costs 104-112 9 r 0
29 V RINGDUR ring duration in 1/10 seconds 113-115 3 r 0
30 V SUPLSERV supplementary services 116-117 2 r 0
31 V GLOBLV2 domain of node generation the 118-119 2 r 0
call id (old leg) - global for
node
32 V GLOBLV1 subdomain of node generation 120-122 3 r 0
the call id (old leg) - global for
node
33 V GLOBLV0 node number of node genera- 123-125 3 r 0
tion the call id (old leg) - global
for node
34 V GLOBSEQ sequence number of generat- 126-133 8 r 0
ing node (old leg) - global for
node
35 V CONCHRG evaluated cost 134-142 9 r 0
36 V CAUSE reason for release of a call 143-145 3 r 0
37 V UNANS answered / not answered flag 146 1
38 V RECPT record point of CDR 147 1
39 V TRANSCNT number of transit nodes 148-149 2 r 0
40 V TRNSFPTY Transfering party - party that 150-159 10 r
transferred a call
41 V BAUD transmission speed 160-162 3 r 0
42 V SIGDATA data record “correct/incorrect” 163 1
43 F CRLF CR / LF flag for end of data 164-165 2
record
Table 6-45 AM-WIN 1.0 - Output format for AM-WIN 1.0 (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012


AM-WIN 2.0 – Format for AM-WIN 2.0

Legend:

ment
6 V PAYPARTY paying party 15-24 10 r
8 V PIN PIN 26-37 12 l
24 V GENLV2 domain of node generating 95-96 2 r 0
the call record
Table 6-46 AM-WIN 2.0 - Output format for AM-WIN 2.0
A31003-H3460-M104-4-76A9, July 2012


ment
25 V GENLV1 subdomain of node generat- 97-99 3 r 0
ing the call record
26 V GENLV0 node number of node gener- 100-102 3 r 0
ating the call record
29 F FixText FFF 113-115 3 FFF
31 V GLOBLV2 domain of node generation 118-119 2 r 0
node
32 V GLOBLV1 subdomain of node genera- 120-122 3 r 0
for node
33 V GLOBLV0 node number of node gener- 123-125 3 r 0
ation the call id (old leg) - glo-
bal for node
node
transferred a call
43 V TRNSFLV2 domain number of transfering 164-165 2 r 0
party
44 V TRNSFLV1 subdomain number of trans- 166-168 3 r 0
fering party
A31003-H3460-M104-4-76A9, July 2012



ment
45 V TRNSFLV0 node number number of 169-171 3 r 0
transfering party
46 V DESTLV2 domain number of connected 172-173 2 r 0
party
47 V DESTLV1 subdomain number of con- 174-176 3 r 0
nected party
48 V DESTLV0 node number of connected 177-179 3 r 0
party
49 V THRELV2 domain number of global call 180-181 2 r 0
id - global for network
50 V THRELV1 subdomain number of global 182-184 3 r 0
call id - global for network
51 V THRELV0 node number of global call id, 185-187 3 r 0
a new call id may be generat-
ed only in case af a new con-
nection. - global for network
52 V THRESEQ global call id - global for net- 188-195 8 r 0
work
53 V NETTYPE network description 196 1
54 V INTNLIST trunk number of the non-re- 197-201 5 l
cording point
56 V QUEUEDUR queuing duration in 1/10 sec- 208-213 6 l
onds
57 F CRLF CR / LF flag for end of data 214-215 2
record
A31003-H3460-M104-4-76A9, July 2012

H4000_HP_AM – Output format from HiPath 4000 for HiPath AM

Legend:
No. ET Element Long name (eng) Position Length Align- filler

ment
1 F FIXTEXT sign for record begin - fixed text 1-1 1 $
6 V PAYPART paying party 15-26 12 r
7 V STNID source id 27-27 1
8 V PIN PIN 28-39 12 l
18 V SERVICE service code 84-84 1
20 V CARRIER carrier 88-88 1
22 V CONNTYPE call type 95-95 1
23 V EXPENS flag for "expensive facility" 96-96 1
call record
Table 6-47 H4000_HP_AM - Output format from HiPath 4000 for
HiPath AM
A31003-H3460-M104-4-76A9, July 2012



ment
25 V GENLV1 subdomain of node generating the 99-101 3 r 0
call record
26 V GENLV0 node number of node generating 102-104 3 r 0
the call record
27 V COPIN PIN category 105-105 1
29 F FIXTEXT FFF - fixed text 115-117 3 FFF
31 V GLOBLV2 domain of node generation the call 120-121 2 r 0
id (old leg) - global for node
32 V GLOBLV1 subdomain of node generation the 122-124 3 r 0
call id (old leg) - global for node
33 V GLOBLV0 node number of node generation 125-127 3 r 0
the call id (old leg) - global for node
34 V GLOBSEQ sequence number of generating 128-135 8 r 0
node (old leg) - global for node
37 V UNANS answered / not answered flag 148-148 1
38 V RECPT record point of CDR 149-149 1
transferred a call
42 V SIGDATA data record "correct/incorrect" 167-167 1
43 V TRNSFLV2 domain number of transfering party 168-169 2 r 0
44 V TRNSFLV1 subdomain number of transfering 170-172 3 r 0
party
45 V TRNSFLV0 node number number of transfer- 173-175 3 r 0
ing party
46 V DESTLV2 domain number of connected party 176-177 2 r 0
HiPath AM (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012


ment
47 V DESTLV1 subdomain number of connected 178-180 3 r 0
party
48 V DESTLV0 node number of connected party 181-183 3 r 0
49 V THRELV2 domain number of global call id - 184-185 2 r 0
global for network
50 V THRELV1 subdomain number of global call id 186-188 3 r 0
- global for network
51 V THRELV0 node number of global call id, a 189-191 3 r 0
new call id may be generated only
in case af a new connection. - glo-
bal for network
52 V THRESEQ global call id - global for network 192-199 8 r 0
53 V NETTYPE network description 200-200 1
54 V INTNLIST trunk number of the non-recording 201-205 5 l
point
56 V QUEUEDUR queuing duration in 1/10 seconds 212-217 6 l
F CRLF CR / LF flag for end of data record 218-219 2
HiPath AM (Fortsetzung)
HiPath 4000 Manager/Assistant PM – Output format for HiPath 4000 Manager/Assistant

PM V1.0
Short name Long name (eng) Type Range Manda- Element desciption De-
(Len) / of tory fault
Default values field val-
Length ue
ATTCALLP attendant call prior- int(2) num. no >= H4000 V2.0 0
ity, priority of the (1-48) ger/eng: ATTCALLP
(new H4000) call to the atten-
dant
Table 6-48 HiPath 4000 Manager / Assistant PM - Output format for
HiPath 4000 Manager / Assistant PM V1.0
A31003-H3460-M104-4-76A9, July 2012


ATTCALLR attendant intercept int(2) num. no >= H4000 V2.0 0

reason, reason for (0-26) ger/eng: ATTCALLR
(new H4000) the intercept
ATTCALLT attendant call type int(2) num. no >= H4000 V2.0 0
(0-23) ger/eng: ATTCALLT
(new H4000)
ATTQUEID attendant queue id int(2) num. no >= H4000 V2.0 0
for AC-Win Multipe (0-14) ger/eng: ATTQUEID
Queue (MQ)
(new H4000)
Table 6-48 HiPath 4000 Manager / Assistant PM - Output format for
HiPath 4000 Manager / Assistant PM V1.0 (Fortsetzung)
Element Description Position Lenght Align- filler

ment
ADPLOAD ADP load 1-4 4 l
ATTGRNO attendant console group 5-6 2 l
ATTCALLP attendant call priority 7-8 2 l
ATTCALLR attendant intercept reason 9-10 2 l
ATTCALLT attendant call type 11-12 2 l
ATTQUEID attendant queue id for AC-Win MQ 13-14 2 l
BCHLCNT number of used B-channels 7-8 2 l
CALLEPTY called party, number which was dialed by 9-30 22 l
the calling party - e.g. hunting group
CALLILV2 domain number of calling party 31-32 2 l
CALLILV1 subdomain number of calling party 33-35 3 l
CALLILV0 node number of calling party 36-38 3 l
CALLIONI originating network id of the calling party 39-40 2 l
CALLIPTY calling party, party that initated the cur- 41-62 22 l
rent connection/section
CARRIER output of the communication network as 63 1 l
a text string
CAUSE cause of connection interrupt / clearing 64-66 3 l
the call
Table 6-49 HiPath 4000 Manager/Assistant PM - Output format for HiPath 4000 Manager/Assistant PM
V1.0
A31003-H3460-M104-4-76A9, July 2012


ment
CONNSTEP connection sequenz, 67-69 3 l
all CDB records of a connection will be
numbered sequentially
CONNTYPE connection typ 70 1 l
CONTOT connection duration total in 1/10 seconds 71-76 6 l
DESTLV2 domain number of destination number 77-78 2 l
(new/connect party)
DESTLV1 subdomain number of destination num- 79-81 3 l
ber (new/connect party)
DESTLV0 node number of destination number 82-84 3 l
(new/connect party)
DESTPTY destination number (new/conneted par- 85-106 22 l
ty)
ENDYEAR end-of-connection year 107-110 4 l
ENDMONTH end-of-connection month 111-112 2 l
ENDDAY end-of-connection day 113-114 2 l
ENDHOUR end-of-connection hour 115-116 2 l
ENDMIN end-of-connection minute 117-118 2 l
ENDSEC end-of-connection second 119-120 2 l
END10 end-of-connection 1/10 of a second 121 1 l
GENLV2 domain number of generating node 122-123 2 l
GENLV1 subdomain number of generating node 124-126 3 l
GENLV0 node number of generating node 127-129 3 l
GLOBLV2 domain number of leg id - global for node 130-131 2 l
GLOBLV1 subdomain number of leg id - global for 132-134 3 l
node
GLOBLV0 node number of leg id - global for node 135-137 3 l
GLOBSEQ leg id, if a targetuser may be changed 138-145 8 l
with an existing connection, a new leg_id
will be generated, the global call_id itself
wouldn’t be changed - global for node
V1.0 (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012



ment
HOLDDUR hold duration in 1/10 seconds 146-150 5 l
INTNBCHA B-channel of the real trunk number of the 151-152 2 l
non-record point
INTNTRGR real trunk group number of the non-re- 153-154 2 l
cording point
INTNREAL real trunk number of the non-recording 155-159 5 l
point (see TKNOREAL)
PPLV2 domain number of paying party 160-161 2 l
PPLV1 subdomain number of paying party 162-164 3 l
PPLV0 Knotennumber der paying party 165-167 3 l
PAYPART paying party, chargee of a connection 168-189 22 l
QUEUEDUR queuing duration, total queuing duration 190-194 5 l
(call queue of attendent) in 1/10 seconds
RINGDUR ring duration, total ring duration in format 195-197 3 l
1/10 seconds
SUPLSERV supplement service 198-199 2 l
SWP call phases 200-201 2 l
SWULOAD switching unit load 202-205 4 l
THRELV2 domain number of global call id - global 206-207 2 l
for network
THRELV1 subdomain number of global call id - glo- 208-210 3 l
bal for network
THRELV0 node number of global call id, a new call 211-213 3 l
id may be generated only in case af a
new connection. - global for network
THRESEQ global call id - global for network 214-221 8 l
TKNOBCHA B-channel of the real trunk number of the 222-223 2 l
non record point
TKNOTRGR real trunk group number of recording 224-225 2 l
point
TKNOREAL real trunk number of recoring point 226-230 5 l
V1.0 (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012


ment
TRNSFLV2 domain number of transering party - (at- 231-232 2 l
tendent console)
TRNSFLV1 subdomain number of transering party - 233-235 3 l
(attendent console)
TRNSFLV0 node number of transering party - (atten- 236-238 3 l
dent console)
TRNSFPTY transering party - (attendent console), 239-260 22 l
party that transferred a call
TRANSCNT number of passed through transit nodes 261-262 2 l
UNANS through connect / no through connect 263 1 l
CRLF CR / LF flag for end of data record 264-265 2 l
V1.0 (Fortsetzung)
H4000_HPAM_E164 – Output format from HiPath 4000 for HiPath AM

Legend:

ment
6x V EPAYPARTY Paying party; chargee of a 15-36 22 r
connection - in E.164 Number-
ing Format
8 V PIN PIN 38-49 12 l
Table 6-50 H4000_HPAM_E164 - Output format from HiPath 4000
for HiPath AM
A31003-H3460-M104-4-76A9, July 2012



ment
9x V EDESTPTY Destination number (new/con- 50-74 25 l
nected party) - in E.164 Num-
bering Format
call record
25 V GENLV1 subdomain of node generating 112-114 3 r 0
the call record
26 V GENLV0 node number of node generat- 115-117 3 r 0
ing the call record
29 F FixText FFF 128-130 3 FFF
31 V GLOBLV2 domain of node generation the 133-134 2 r 0
call id (old leg) - global for
node
for HiPath AM (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012


ment
32 V GLOBLV1 subdomain of node generation 135-137 3 r 0
node
33 V GLOBLV0 node number of node genera- 138-140 3 r 0
for node
node
40 V ETRNSFPTY Transferring party (attendant 165-186 22 r
console) - in E.164 Numbering
Format
43 V TRNSFLV2 domain number of transferring 191-192 2 r 0
party
44 V TRNSFLV1 subdomain number of trans- 193-195 3 r 0
ferring party
45 V TRNSFLV0 node number of transferring 196-198 3 r 0
party
46 V DESTLV2 domain number of connected 199-200 2 r 0
party
47 V DESTLV1 subdomain number of con- 201-203 3 r 0
nected party
48 V DESTLV0 node number of connected 204-206 3 r 0
party
49 V THRELV2 domain number of global call 207-208 2 r 0
id - global for network
A31003-H3460-M104-4-76A9, July 2012



ment
50 V THRELV1 subdomain number of global 209-211 3 r 0
call id - global for network
51 V THRELV0 node number of global call id - 212-214 3 r 0
global for network
52 V THRESEQ global call id - global for net- 215-222 8 r 0
work
53 V NETTYPE network description 223 1
54 V INTNLIST trunk number of the non-re- 224-228 5 l
cording point
56 V QUEUEDUR queuing duration in 1/10 sec- 235-240 6 l
onds
F CRLF CR / LF flag for end of data 241-242 2
record
A31003-H3460-M104-4-76A9, July 2012

H8000_AM – OpenScape Voice Output Format V1.0

Legend:

ment
1 V RECIDENT Record Type 1-8 8 L
2 V STDATETIME Start Time 9-34 26 L
3 V CONTOT Duration of call 35-44 10 L
4 V SWITCHID Switch ID 45-60 16 L
5 V RECID Record ID (Leg-ID ?) (not used) 61-119 59 L
6 V CUSTNAME Customer Name/Number 120-135 16 L
7 V CARRIER Carrier ID Parameter 136-139 4 L
8 V DESTPTY Terminating Number/Called Par- 140-159 20 L
ty
9 V CALLIPTY Originating Number/Calling Par- 160-179 20 L
ty
10 V PAYPART ANI - responsible for paying for 180-199 20 L
the call
11 V CALLTYPE Call Type 200-202 3 L
12 V SUPLSERV Attempt Indicator 203-203 1 L
13 V CAUSE Release Cause/Completion Indi- 204-206 3 L
cator
(not used)
14 V CFW Indicates forwarded calls 207-207 1 L
15 V ORGNATADR Orig Nature of Address 208-210 3 L
16 V INTNTGR Incoming PRI Name/Trunk 211-226 16 L
Group
17 V INTNBCHA Incoming PRI/Trunk Group 227-236 10 L
Member ID
18 V TKNOTRGR Outgoing PRI Name/Trunk 237-252 16 L
Group ID
19 V TKNOBCHA Outgoing PRI/Trunk Member ID 253-262 10 L
Table 6-51 H8000_AM - OpenScape Voice Output Format V1.00
A31003-H3460-M104-4-76A9, July 2012



ment
20 V STNID Originating Party Identifier 263-265 3 L
21 V DESTPID Terminating Party Identifier 266-268 3 L
22 V RINGDUR Call Answer Time 269-294 26 L
23 V RELDUR Call Release Time 295-320 26 L
24 V SERVICE Per Call Feature (not used) 321-337 17 L
25 V DNBASESTA Forwarded from DN 338-357 20 L
26 V SIGDATA Intermediate Indicator 358-358 1 L
27 V AUTH BG Authorization Code 359-373 15 L
28 V ACCTCODE- BG Account Code 374-388 15 L
BG
29 V CFATYPE BG Originating Facility Type 389-389 1 L
30 V DFATYPE BG Terminating Facility Type 390-390 1 L
F CRLF Flag for end of data record 391-392 2
Table 6-51 H8000_AM - OpenScape Voice Output Format V1.00 (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012

H8000_AM_V22 – OpenScape Voice Output Format V2.2 (Single System)

Legend:
L = element length; A = alignment; FI = pad character: Empty = space.
No. ET HiPath COL Position L A FI DEF. H8 Definition
Element Name No
1 V RECIDENT 1-8 8 L 0 00000000 2 Record Type
2 V STDATETIME 9-34 26 L 3 Start Time
3 V CONTOT 35-44 10 L 0 4 Duration of call
4 V SWITCHID 45-60 16 L 5 Switch ID
5 V RECID 61-119 59 L 6 Record ID (Leg-ID ?) (not used)
6 V CUSTNAME 120-135 16 L 7 Customer Name/Number
7 V ACCTCODE 136-150 15 L 8 At the moment not filled by H8000
8 V CARRIER 151-154 4 L 10 Carrier ID Parameter
9 V DESTPTY 155-174 20 L 11 Terminating Number/Called Party
10 V CALLIPTY 175-194 20 L 12 Originating Number/Calling Party
11 V PAYPART 195-214 20 L 13 ANI - responsible for paying for
the call
12 V CALLTYPE 215-217 3 L 16 Call Type
13 V SUPLSERV 218 1 L 18 Attempt Indicator
14 V CAUSE 219-221 3 L 19 Release Cause/Completion Indi-
cator (not used)
15 V INGCARRIER 222-227 6 L 21 Ingress Carrier Identification
16 V EGCARRIER 228-233 6 L 22 Egress Carrier Identification
17 V CWF 234 1 L 23 Operator Indicator (not used)
18 V ORGNATADR 235-237 3 L 26 Orig Nature of Address
19 V INTNTGR 238-253 16 L 32 Incoming PRI Name/Trunk Group
20 V INTNBCHA 254-263 10 L 33 Incoming PRI/Trunk Group Mem-
ber ID
21 V TKNOTRGR 264-279 16 L 34 Outgoing PRI Name/Trunk Group
ID
22 V TKNOBCHA 280-289 10 L 35 Outgoing PRI/Trunk Member ID
23 V INTNTGRID 290 1 L 38 Incoming Trunk Group Signaling
Type (not used)
24 V TKNOTRGRID 291 1 L 39 Outgoing Trunk Group Signaling
Type (not used)
25 V STNID 292-294 3 L 40 Originating Party Identifier
26 V DESTPID 295-297 3 L 41 Terminating Party Identifier
27 V RINGDUR 298-323 26 L 48 Call Answer Time
28 V RELDUR 324-349 26 L 49 Call Release Time
29 V INCACONDUR 350-375 26 L 50 Incoming Carrier Connect Time
Table 6-52 H8000_AM_V22 – OpenScape Voice Output Format V2.2
A31003-H3460-M104-4-76A9, July 2012


No. ET HiPath COL Position L A FI DEF. H8 Definition

Element Name No
30 V OTCACONDUR 376-401 26 L 52 Outgoing Carrier Connect Time
(not used)
31 V ICNRSTAT 402-403 2 L 61 IC/ICN Call Event Status (not used)
32 V ICNOUTRID 404 1 L 62 Outgoing IC/ICN Routing Indica-
tor (not used)
33 V SCPINFO 405-407 3 L 63 Service Feature Codes (not used)
34 V SERVICE 408-424 17 L 64 Per Call Feature (not used)
35 V DNBASESTA 425-444 20 L 65 Forwarded from DN
36 V SIGDATA 445 1 L 66 Intermediate Indicator
37 V CLINEUSED 446-452 7 L 67 Originating Side: Codec Used (not
used)
38 V CMDRID 453-462 10 L 87 BG Orig. MDR Customer ID
39 V DMDRID 463-472 10 L 88 BG Terminating MDR Customer
ID
40 V AUTH 473-487 15 L 89 BG Authorization Code
41 V ACCTCODEBG 488-502 15 L 90 BG Account Code
42 V CFATYPE 503 1 L 91 BG Originating Facility Type
43 V DFATYPE 504 1 L 92 BG Terminating Facility Type
44 V MSGNO 505-510 6 L 1 Sequential Record Number
45 V CFANUMID 511-517 7 L 93 BG Orig. Station Facility ID
46 V DFANUMID 518-524 7 L 94 BG Term. Station Facility ID
47 V CSIGCOMP 525 1 L 95 BG Call Completion Code
48 V CDRRECINFO 526 1 L 0 100
49 V GLOBLNODE 527-536 10 L 121 Global Node ID / leg-id (not used)
50 V GLOBLSEQ 537-546 10 L 122 Global Call Sequence number /
leg-id
51 V TRANSDN 547-566 20 L 123 Transferred from DN
52 V THRENODE 567-576 10 L 124 Thread Node ID (network wide)
(not used)
53 V THRESEQ 577-586 10 L 125 Thread Sequence number (net-
work wide)
54 V INTNLIST 587-616 30 L 126 Ingress SIP endpoint (incoming
trunk)
55 V TKNOLIST 617-646 30 L 127 Egress SIP endpoint (outgoing
trunk)
F CRLF 647-648 2 Flag for end of data record
Table 6-52 H8000_AM_V22 – OpenScape Voice Output Format V2.2 (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012

OSV_AM – Open Scape Voice Output Format

Legend:
No. ET Element Long name (eng) Position Length Align- filler OSV
ment CDR No.
1 V RECIDENT Record Type 1-8 8 L 0 2
2 V STDATETIME Start Time 9-34 26 L 3
3 V CONTOT Duration of call 35-44 10 L 4
4 V SWITCHID Switch ID 45-60 16 L 5
5 V RECID Record ID (Leg-ID ?) (not used) 61-119 59 L 6
6 V CUSTNAME Customer Name/Number 120-135 16 L 7
7 V ACCTCODE At the moment not filled by H8000 136-150 15 L 8
8 V CARRIER Carrier ID Parameter 151-154 4 L 10
9 V DESTPTY Terminating Number/Called Party 155-174 20 L 11
10 V CALLIPTY Originating Number/Calling Party 175-194 20 L 12
11 V PAYPART ANI - responsible for paying for the call 195-214 20 L 13
12 V CALLTYPE Call Type 215-217 3 L 16
13 V SUPLSERV Attempt Indicator 218-218 1 L 18
14 V CAUSE Release Cause/Completion Indicator (not 219-221 3 L 19
used)
15 V INGCARRIER Ingress Carrier Identification 222-227 6 L 21
16 V EGCARRIER Egress Carrier Identification 228-233 6 L 22
17 V CWF Operator Indicator (not used) 234-234 1 L 23
18 V ORGNATADR Orig Nature of Address 235-237 3 L 26
19 V INTNTGR Incoming PRI Name/Trunk Group 238-253 16 L 32
20 V INTNBCHA Incoming PRI/Trunk Group Member ID 254-263 10 L 33
21 V TKNOTRGR Outgoing PRI Name/Trunk Group ID 264-279 16 L 34
22 V TKNOBCHA Outgoing PRI/Trunk Member ID 280-289 10 L 35
23 V INTNTGRID Incoming Trunk Group Signaling Type (not 290-290 1 L 38
used)
24 V TKNOTRGRID Outgoing Trunk Group Signaling Type (not 291-291 1 L 39
used)
25 V STNID Originating Party Identifier 292-294 3 L 40
26 V DESTPID Terminating Party Identifier 295-297 3 L 41
27 V RINGDUR Call Answer Time 298-323 26 L 48
28 V RELDUR Call Release Time 324-349 26 L 49
Table 6-53 OSV_AM - Open Scape Voice Output Format
A31003-H3460-M104-4-76A9, July 2012


No. ET Element Long name (eng) Position Length Align- filler OSV
ment CDR No.
29 V INCACONDUR Incoming Carrier Connect Time 350-375 26 L 50
30 V OTCACONDUR Outgoing Carrier Connect Time (not used) 376-401 26 L 52
31 V ICNRSTAT IC/ICN Call Event Status (not used) 402-403 2 L 61
32 V ICNOUTRID Outgoing IC/ICN Routing Indicator (not 404-404 1 L 62
used)
33 V SCPINFO Service Feature Codes (not used) 405-407 3 L 63
34 V SERVICE Per Call Feature (not used) 408-424 17 L 64
35 V DNBASESTA Forwarded from DN 425-444 20 L 65
36 V SIGDATA Intermediate Indicator 445-445 1 L 66
37 V CLINEUSED Originating Side: Codec Used (not used) 446-452 7 L 67
38 V CMDRID BG Orig. MDR Customer ID 453-462 10 L 87
39 V DMDRID BG Terminating MDR Customer ID 463-472 10 L 88
40 V AUTH BG Authorization Code 473-487 15 L 89
41 V ACCTCODEBG BG Account Code 488-502 15 L 90
42 V CFATYPE BG Originating Facility Type 503-503 1 L 91
43 V DFATYPE BG Terminating Facility Type 504-504 1 L 92
44 V MSGNO Sequential Record Number 505-510 6 L 1
45 V CFANUMID BG Orig. Station Facility ID 511-517 7 L 93
46 V DFANUMID BG Term. Station Facility ID 518-524 7 L 94
47 V CSIGCOMP BG Call Completion Code 525-525 1 L 95
48 V CDRRECINFO 526-526 1 L 100
49 V GLOBLNODE Global Node ID / leg-id (not used) 527-536 10 L 121
50 V GLOBLSEQ Global Call Sequence number / leg-id 537-546 10 L 122
51 V TRANSDN Transferred from DN 547-566 20 L 123
52 V THRENODE Thread Node ID (network wide) (not used) 567-576 10 L 124
53 V THRESEQ Thread Sequence number (network wide) 577-586 10 L 125
54 V INTNLIST Ingress SIP endpoint (incoming trunk) 587-616 30 L 126
55 V TKNOLIST Egress SIP endpoint (outgoing trunk) 617-646 30 L 127
56 V EVENTID Identification of Event 647-656 10 L 107
F CRLF Flag for end of data record 657-658 2
Table 6-53 OSV_AM - Open Scape Voice Output Format (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012

HP4M_AMPM_UV3.0 – Output format from HiPath 4000 V3 for HiPath 4000 V6

Legend:
No ET Element Long name (eng) Position Length Align- filler

ment
1 F FIXTEXT Fixed text 1 1 L $
2 V ACDGID ACD Group Number 2-4 3 L
3 V ADPLOAD ADP load 5-8 4 R 0
4 V ATTGRNO Attendant console group 9-10 2 R 0
5 V BAUD Transmission speed 11-13 3 L
6 V BCHLCNT Number of used B-channels 14-15 2 R 0
7 V CALLEPTY Called party; dialed number 16-37 22 L
8 V CALLIID Identification of calling party 38-38 1 L
number
9 V CALLILV0 Node number of calling party 39-41 3 R 0
10 V CALLILV1 Subdomain number of calling 42-44 3 R 0
party
11 V CALLILV2 Domain number of calling party 45-46 2 R 0
12 V CALLIPTY Calling party; party that initated 47-68 22 L
connection
13 V CARRIER Carrier; communication network 69-69 1 L
14 V CAUSE Cause - of connection interrupt / 70-72 3 R 0
clear down
15 V CHRGUNIT Call charge units 73-77 5 R 0
16 V CONCHRG Costs calculated on output within 78-86 9 R 0
VAT
17 V CONNSTEP Connection sequence; number 87-89 3 R 0
18 V CONNTYPE Connection type 90-90 1 L
19 V CONTOT Connection duration total in 1/10 91-96 6 R 0
seconds
20 V COPIN Class of PIN 97-98 2 L
21 V DESTLV0 Node number of destination num- 99-101 3 R 0
ber
Table 6-54 HP4M_AMPM_UV3.0 - Output format
A31003-H3460-M104-4-76A9, July 2012



ment
22 V DESTLV1 Subdomain number of destina- 102-104 3 R 0
tion number
23 V DESTLV2 Domain number of destination 105-106 2 R 0
number
24 V DESTPID Identification number of destina- 107-107 1 L
tion number
25 V DESTPTY Destination number (new/con- 108-129 22 L
nected party)
26 V DISPCHRG Display of connection charge 130-138 9 R 0
with VAT
27 V END10 End-of-connection 1/10 of a sec- 139-139 1 R 0
ond
28 V ENDDAY End-of-connection day 140-141 2 R 0
29 V ENDHOUR End-of-connection hour 142-143 2 R 0
30 V ENDMIN End-of-connection minute 144-145 2 R 0
31 V ENDMONTH End-of-connection month 146-147 2 R 0
32 V ENDSEC End-of-connection second 148-149 2 R 0
33 V ENDYEAR End-of-connection year 150-153 4 R 0
34 V EXPENS Expensive connection 154-154 1 L
35 V GLOBLLV0 Node number of global call ID 155-157 3 R 0
only local
36 V GLOBLLV1 Subdomain number of global call 158-160 3 R 0
ID (local)
37 V GLOBLLV2 Domain number of global call ID 161-162 2 R 0
(local)
38 V GLOBLSEQ Global call ID (local/leg) 163-179 8 R 0
39 V HOLDDUR Hold duration in 1/10 seconds 171-175 5 R 0
40 V INTNBCHA B-channel for real trunk no. of the 176-177 2 R 0
recording point
41 V INTNLIST Imaginary trunk number created 178-183 6 R 0
from INTNREAL
42 V INTNREAL Real trunk no. of the non-record- 184-188 5 L
ing point (see TKNOREAL)
43 V INTNTRGR Real trunk group number of the 189-191 3 R 0
non-recording point
44 V NETTYPE Network description 192-192 1 L
Table 6-54 HP4M_AMPM_UV3.0 - Output format (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012


ment
45 V PAYPART Paying party; chargee of a con- 193-214 22 L
nection
46 V PIN Personal identification number 215-226 12 L
47 V PPLV0 Node number of paying party 227-229 3 R 0
48 V PPLV1 Subdomain number of paying 230-232 3 R 0
party
49 V PPLV2 Domain number of paying party 233-234 2 R 0
50 V QUEUEDUR Queueing duration in 1/10 sec- 235-239 5 R 0
onds
51 V RECPT Record point 240-240 1 R 0
52 V RECTYPE Record type 241-241 1 R 0
53 V RINGDUR Ring duration; total in 1/10 sec- 242-244 3 R 0
onds
54 V ROUTCC Route code as a text string 245-250 6 R
55 V SERVICE Service 251-251 1 L
56 V SIGDATA Indicates whether the output data 252-252 1 L
record is correct / incorrect or
double
57 V STNID Station identification number 253-253 1 L
58 V SUPLSERV Supplementary service 254-255 2 L
59 V SWP Call processing phases 256-257 2 L
60 V SWULOAD Switching unit load 258-261 4 R 0
61 V THRELV0 Node number of thread (global) 262-264 3 R 0
call ID
62 V THRELV1 Subdomain number of thread 265-267 3 R 0
(global) call ID
63 V THRELV2 Domain number of thread (glo- 268-269 2 R 0
bal) call ID
64 V THRESEQ Thread (global) call ID in network 270-277 8 R 0
65 V TKNOBCHA B-channel for real trunk no. of the 278-279 2 R 0
non-recording point
66 V TKNOLIST Imaginary trunk number created 280-285 6 L
of TKNOREAL (see AMO-FBTN)
67 V TKNOREAL Real trunk number of recording 286-290 5 R 0
point
A31003-H3460-M104-4-76A9, July 2012



ment
68 V TKNOTRGR Real trunk group number of re- 291-293 3 R 0
cording point
69 V TRANSCNT Number of passed through transit 294-295 2 R 0
nodes
70 V TRNSFLV0 Node number of transferring par- 296-298 3 R 0
ty (AC)
71 V TRNSFLV1 Subdomain number of transfer- 299-301 3 R 0
ring party (AC)
72 V TRNSFLV2 Domain number of transferring 302-303 2 R 0
party (AC)
73 V TRNSFPTY Transferring party (attendant 304-325 22 L
console)
74 V UNANS Through connect / no through 326-326 1 L
connect
75 V ZONE Distance zone 327-329 3 L
A31003-H3460-M104-4-76A9, July 2012

HP4M_AMPM_UV4 – Output format from HiPath 4000 V4 for HiPath 4000 V6

Legend:

ment
8 V CALLIID Identification of calling party num- 38-38 1 L
ber
10 V CALLILV1 Subdomain number of calling par- 42-44 3 R 0
ty
connection
clear down
VAT
17 V CONNSTE Connection sequence; number 87-89 3 R 0
P
18 V CONNTYP Connection type 90-90 1 L
E
seconds
Table 6-55 HP4M_AMPM_UV4 - Output format
A31003-H3460-M104-4-76A9, July 2012



ment
ber
22 V DESTLV1 Subdomain number of destination 102-104 3 R 0
number
number
tion number
nected party)
26 V DISPCHRG Display of connection charge with 130-138 9 R 0
VAT
ond
31 V END- End-of-connection month 146-147 2 R 0
MONTH
35 V GLOBLLV0 Node number of global call ID only 155-157 3 R 0
local
ID (local)
(local)
recording point
from INTNREAL
Table 6-55 HP4M_AMPM_UV4 - Output format (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012


ment
non-recording point
nection
48 V PPLV1 Subdomain number of paying par- 230-232 3 R 0
ty
50 V QUEUE- Queueing duration in 1/10 sec- 235-239 5 R 0
DUR onds
onds
record is correct / incorrect or dou-
ble
call ID
62 V THRELV1 Subdomain number of thread (glo- 265-267 3 R 0
bal) call ID
63 V THRELV2 Domain number of thread (global) 268-269 2 R 0
call ID
65 V TKNOB- B-channel for real trunk no. of the 278-279 2 R 0
CHA non-recording point
A31003-H3460-M104-4-76A9, July 2012



ment
point
68 V TKNOTR- Real trunk group number of re- 291-293 3 R 0
GR cording point
nodes
70 V TRNSFLV0 Node number of transferring party 296-298 3 R 0
(AC)
71 V TRNSFLV1 Subdomain number of transferring 299-301 3 R 0
party (AC)
party (AC)
73 V TRNSFPTY Transferring party (attendant con- 304-325 22 L
sole)
connect
A31003-H3460-M104-4-76A9, July 2012

HP4M_AMPM_UV5 – Output format from HiPath 4000 V5 for HiPath 4000 V6

Legend:
No ET Element Long name (eng) Position Length Align filler

ment
ber
10 V CALLILV1 Subdomain number of calling party 42-44 3 R 0
connection
clear down
VAT
seconds
ber
number
A31003-H3460-M104-4-76A9, July 2012



ment
number
24 V DESTPID Identification number of destination 107-107 1 L
number
25 V DESTPTY Destination number (new/connect- 108-129 22 L
ed party)
VAT
27 V END10 End-of-connection 1/10 of a second 139-139 1 R 0
local
36 V GLOBLLV1 Subdomain number of global call ID 158-160 3 R 0
(local)
37 V GLOBLLV2 Domain number of global call ID (lo- 161-162 2 R 0
cal)
recording point
from INTNREAL
42 V INTNREAL Real trunk no. of the non-recording 184-188 5 L
non-recording point
45 V PAYPART Paying party; chargee of a connec- 193-214 22 L
tion
A31003-H3460-M104-4-76A9, July 2012


ment
48 V PPLV1 Subdomain number of paying party 230-232 3 R 0
50 V QUEUEDUR Queueing duration in 1/10 seconds 235-239 5 R 0
53 V RINGDUR Ring duration; total in 1/10 seconds 242-244 3 R 0
ble
61 V THRELV0 Node number of thread (global) call 262-264 3 R 0
ID
bal) call ID
call ID
non-recording point
66 V TKNOLIST Imaginary trunk number created of 280-285 6 L
TKNOREAL (see AMO-FBTN)
point
68 V TKNOTRGR Real trunk group number of record- 291-293 3 R 0
ing point
nodes
(AC)
A31003-H3460-M104-4-76A9, July 2012



ment
party (AC)
72 V TRNSFLV2 Domain number of transferring par- 302-303 2 R 0
ty (AC)
sole)
74 V UNANS Through connect / no through con- 326-326 1 L
nect
A31003-H3460-M104-4-76A9, July 2012

HP4M_AMPM_UV6 – Output format from HiPath 4000 V6

Legend:

ment
ber
10 V CALLILV1 Subdomain number of calling par- 42-44 3 R 0
ty
connection
clear down
VAT
seconds
ber
A31003-H3460-M104-4-76A9, July 2012



ment
number
number
tion number
nected party)
VAT
ond
local
ID (local)
(local)
recording point
from INTNREAL
non-recording point
A31003-H3460-M104-4-76A9, July 2012


ment
nection
48 V PPLV1 Subdomain number of paying par- 230-232 3 R 0
ty
onds
onds
ble
call ID
(global) call ID
call ID
non-recording point
point
A31003-H3460-M104-4-76A9, July 2012



ment
cording point
nodes
(AC)
ring party (AC)
party (AC)
sole)
connect
A31003-H3460-M104-4-76A9, July 2012

HP4M_PM_UV6 – Output format from HiPath 4000 V6

Legend:

ment
ber
9 V CALLILV1 Subdomain number of calling party 39-41 3 R 0
connection
clear down
seconds
ber
number
number
20 V DESTPID Identification number of destination 88-88 1 L
number
Table 6-58 HP4M_PM_UV6 - Output format
A31003-H3460-M104-4-76A9, July 2012



ment
21 V DESTPTY Destination number (new/connect- 89-110 22 L
ed party)
22 V END10 End-of-connection 1/10 of a second 111-111 1 R 0
local
30 V GLOBLLV1 Subdomain number of global call ID 129-131 3 R 0
(local)
31 V GLOBLLV2 Domain number of global call ID (lo- 132-133 2 R 0
cal)
recording point
35 V INTNREAL Real trunk no. of the non-recording 149-153 5 L
non-recording point
37 V PAYPART Paying party; chargee of a connec- 157-178 22 L
tion
39 V PPLV1 Subdomain number of paying party 182-184 3 R 0
41 V QUEUEDUR Queueing duration in 1/10 seconds 187-191 5 R 0
42 V RINGDUR Ring duration; total in 1/10 seconds 192-194 3 R 0
46 V SWULOAD Switching unit load 200203 4 R 0
Table 6-58 HP4M_PM_UV6 - Output format (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012


ment
47 V THRELV0 Node number of thread (global) call 204-206 3 R 0
ID
bal) call ID
call ID
non-recording point
point
53 V TKNOTRGR Real trunk group number of record- 227-229 3 R 0
ing point
nodes
(AC)
party (AC)
57 V TRNSFLV2 Domain number of transferring par- 238-239 2 R 0
ty (AC)
sole)
59 V UNANS Through connect / no through con- 262-262 1 L
nect
Table 6-58 HP4M_PM_UV6 - Output format (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012


Pre-defined Formats for Input Format Definition
6.4 Pre-defined Formats for Input Format Definition
Important:
The following pre-defined formats for defining the input format are available, and they apply
likewise to the input formats of H3000 and H2000 systems:
● Elements for Defining Input and Output Formats
● AMPM_UV1.0 - Input format for AM / PM HiPath 4000
● AllServe - Input format for HiPath AllServe 150 V1.0 (Element Manager)
● H5000_V30 - Input format for HiPath 5000 V3.0 (Single System)
● H8000_V22 – OpenScape Voice Input Format V2.2 (single PABX)
● AMPM_UV6 - Input format for AM/PM HiPath 4000
● PM_UV6 - Input format for HiPath 4000
● CM Elements Used for Generating History Output
A31003-H3460-M104-4-76A9, July 2012

AMPM_UV1.0 - Input format for AM / PM HiPath 4000
No Element Description Position Lenght Align- filler

ment
1 $ sign for record begin 1 1
2 ADPLOAD APD load 2-5 4 r 0
3 ATTGRNO attendant console group 6-7 2 r 0
4 BAUD transmission speed 8-10 3 l
5 BCHLCNT number of used B-channels 11-12 2 r 0
6 CALLEPTY called party, number which was di- 13-34 22 l
aled by the calling party - e.g. hunt-
ing group
7 CALLIID identification of calling party 35 1 l
8 CALLILV0 node number of calling party 36-38 3 r 0
9 CALLILV1 subdomain number of calling party 38-41 3 r 0
10 CALLILV2 domain number of calling party 42-43 2 r 0
11 CALLIPTY calling party, party that initated the 44-65 22 l
current connection/section
12 CARRIER output of the communication net- 66 1 l
work as a text string
13 CAUSE cause of connection interrupt / 68-69 3 r 0
clearing the call
14 CHRGUNIT call charge units 70-74 5 r 0
15 CONCHRG evaluated cost 75-83 9 r 0
16 CONNSTEP connection sequenz, 84-86 3 r 0
all CDB records of a connection will
be numbered sequentially
17 CONNTYPE connection type 87 1 l
18 CONTOT connection duration total in 1/10 88-93 6 r 0
seconds
19 COPIN PIN category 94-95 2 l
20 DESTLV0 node number of destination num- 96-97 3 r 0
ber (new/connect party)
21 DESTLV1 subdomain number of destination 98-100 3 r 0
number (new/connect party)
Table 6-59 AMPM_UV1.0 - Input format for AM/PM HiPath 4000
A31003-H3460-M104-4-76A9, July 2012



ment
22 DESTLV2 domain number of destination 101-102 2 r 0
number (new/connect party)
23 DESTPID Identification number of destination 103 1 l
24 DESTPTY destination number (new/conneted 105-126 22 l
party)
25 DISPCHRG display costs 127-135 9 r 0
26 END10 end-of-connection 1/10 of a second 136 1 r 0
27 ENDDAY end-of-connection day 137-138 2 r 0
28 ENDHOUR end-of-connection hour 139-140 2 r 0
29 ENDMIN end-of-connection minute 141-142 2 r 0
30 ENDMONTH end-of-connection month 143-144 2 r 0
31 ENDSEC end-of-connection second 145-146 2 r 0
32 ENDYEAR end-of-connection year 147-150 4 r 0
33 EXPENS flag for “expensive facility” 151 1 l
34 GLOBLLV0 node number of leg id 152-154 3 r 0
35 GLOBLLV1 subdomain number of leg id 155-157 3 r 0
36 GLOBLLV2 domain number of leg id 158-159 2 r 0
37 GLOBLSEQ leg id, if a targetuser may be 156-167 8 r 0
changed with an existing connec-
tion, a new leg_id will be generat-
ed, the global call_id itself wouldn’t
be changed
38 HOLDDUR hold duration in 1/10 seconds 168-172 5 r 0

39 INTNBCHA B-channel of the real trunk number 173-174 2 r 0
of the non-record point
40 INTNLIST trunk number of the non-recording 175-180 6 r 0
point
41 INTNREAL real trunk number of the non-re- 181-185 5 l
cording point (see TKNOREAL)
42 INTNTRGR real trunk group number of the non- 186-188 3 r 0
recording point
43 NETTYPE network description 189 1 l
Table 6-59 AMPM_UV1.0 - Input format for AM/PM HiPath 4000 (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012


ment
44 PAYPART paying party, chargee of a connec- 190-211 22 l
tion
45 PIN PIN 212-223 12 l
46 PPLV0 Knotennumber der paying party 224-226 3 r 0
47 PPLV1 subdomain number of paying party 227-229 3 r 0
48 PPLV2 domain number of paying party 230-231 2 r 0
49 QUEUEDUR queuing duration, total queuing du- 232-236 5 r 0
ration (call queue of attendent) in
1/10 seconds
50 RECPT record point of CDR 237 1 r 0
51 RECTYPE record type 238 1 r 0
52 RINGDUR ring duration, total ring duration in 239-241 3 r 0
format 1/10 seconds
53 ROUTCC route code 242-247 6 l
54 SERVICE service code 248 1 l
55 SIGDATA data record “correct/incorrect” 249 1 l
56 STNID source id 250 1 l
57 SUPLSERV supplement service 251-252 2 l
58 SWP call phases 253-254 2 l
59 SWULOAD switching unit load 255-258 4 r 0
60 THRELV0 node number of global call id, a 259-261 3 r 0
new call id may be generated only
in case af a new connection.
61 THRELV1 subdomain number of global call id 262-264 3 r 0
62 THRELV2 domain number of global call id 265-266 2 r 0
63 THRESEQ global call id 267-274 8 r 0
64 TKNOBCHA B-channel of the real trunk number 275-276 2 r 0
of the non record point
65 TKNOLIST trunk number 277-282 6 l
66 TKNOREAL real trunk number of recoring point 283-287 5 r 0
67 TKNOTRGR real trunk group number of record- 288-290 3 r 0
ing point
A31003-H3460-M104-4-76A9, July 2012



ment
68 TRANSCNT number of passed through transit 291-292 2 r 0
nodes
69 TRNSFLV0 node number of transering party - 293-295 3 r 0
(attendent console)
70 TRNSFLV1 subdomain number of transering 296-298 3 r 0
party - (attendent console)
71 TRNSFLV2 domain number of transering party 299-300 2 r 0
- (attendent console)
72 TRNSFPTY transering party - (attendent con- 301-322 22 l
sole), party that transferred a call
73 UNANS through connect / no through con- 323 1 l
nect
74 ZONE call zone 324-326 3 l
75 CRLF CR / LF flag for end of data record 327-328 2
AllServe - Input format for HiPath AllServe 150 V1.0 (Element Manager)
The CDR transfer is done using Standard FTP. HiPath AllServe 150 V1.0 supports only the
Windows 2000 operating system. In Windows 2000 an FTP server is also available. The FTP
server package is part of the HiPath AllServe 150 V1.0 installation package (image). The FTP
server package is installed automatically and launched at system startup. The configuration is
described in the HiPath AM/COL documentation.
HiPath AllServe 150 provides one file for max. 4 - H150 switches. The directory is “C:\COLDIR”
and the filename is “GCALLSERV”. The format is position oriented.
The CDR file is only open when records are written to the “GCALLSERV” file. If the file
“GCALLSERV” is collected by HiPath COL V1.0/V2.0 using FTP, the file is first moved to “COL-
FILE” and then transferred. After a successful transfer the file is deleted. If after deletion of the
file the CDR output procedure tries to add a new record to “GCALLSERV”, the file will be cre-
ated again.
The HiPath AllServe record format is not the same as for HICOM 150 - Standalone. The “GEZ-
Ausgabe.doc” does not describe the HiPath AllServe record format. HiPath AllServe has the
following format (the format is position oriented):
A31003-H3460-M104-4-76A9, July 2012

Legend:
NO ET Name Name AllServe Pos. L A FI Definition Element in

H150 Struct HiPath COL
1 V End date tConnection Start 1-8 8 End of call ENDDAY
+ Iconnection du- (date), e.g. ENDMONTH
ration = ENDDATE “13.09.00” ENDYEAR
2 V End Time tConnection Start 9-16 8 End of call ENDHOUR
+ Iconnection du- (time), e.g. ENDMIN
ration = ENDTIME “14:14:00” ENDSEC
3 V Line szAssociatedCall- 17-19 3 R Line number , TKNOREAL
ingDevice e.g. “ 1”
4 V Node vNodeID 20-22 3 R Node number PPLV0
5 V Station szCallingDevice 23-28 6 R Internal exten- PAYPART
sion number
6 V Ring du- No value in 29-33 5 BLANK, no RINGMIN
ration AllServe for this value in this RINGSEC
field in this version AllServe ver-
- BLANK sion
7 V Call dura- Iconnection dura- 34-41 8 Call duration in CONHOUR
tion tion format CONMIN
hh:mm:ss, e.g. CONSEC
“00:04:34”
8 V Phone SzNetworkCalled- 42-66 25 L Dialed or in- DESTPTY
number Device coming exter-
nal phone
number
9 V Charge LcurrencyAmount 67-77 11 R Units (CHR- CHRGVALU
call pulse / lTariffTable GUNIT) (new H150)
Default =
‘BLANK’
10 V Connec- SupplServiceInfo 78 1 R Type of Call H150INFO
tion type / Incoming = 1 (new H150)
SupplSer- Outgoing =2
vice Default = 2
Table 6-60 AllServe - Input format for HiPath AllServe 150 V1.0 (Element Manager)
A31003-H3460-M104-4-76A9, July 2012


NO ET Name Name AllServe Pos. L A FI Definition Element in

H150 Struct HiPath COL
11 V Project szAccountInfo 79-89 11 L Account code PIN
code PKZ
12 V MSN No value in 90-100 11 R BLANK, no MSN (new
used AllServe - BLANK value H150)
13 V Access szAccessCode 101- 5 R Access code ROUTCC
code 105
14 V LCR route ISelectedRoute 106- 4 R LCR route LCRROUT
109 (new H150)
15 E CR 110 1 Carriage Re-
turn
16 E LF 111 1 Line Feed
Table 6-60 AllServe - Input format for HiPath AllServe 150 V1.0 (Element Manager) (Fortsetzung)
H5000_V30 - Input format for HiPath 5000 V3.0 (Single System)

HiPath 5000 V3.0 is a single system.
The CDR transfer is done uses Standard FTP. This method uses an FTP server process run-
ning on the HiPath 5000 V3.0.
HiPath 5000 V3.0 provides several files with a time stamp format. The directory can be config-
ured. Default Path: <installion path>/H5000/cfg/cdr and the filename is fix = CDRRe-
port<…>.txt.
HiPath 5000 will create the files according to user configurable dynamic periodicity. Periodicity
can be - no report, hourly, daily, n number of days or on a paricular day of the week.
Filename format: CDRReport_<data>_<time>.txt or
CDRReport_<date>_<time>_<seq_number>).
<date> = YYYYMMDD, <time> = HHMMSS, <seq_number> = {1 , 2, 3 …}
If the output date/time or limit (both configurable) is reached, the internal CDR file is moved to
the CDR output directory. During populating the CDR file with data records from the Informix
database the filename is not ‘CDRReport…txt’. When population the CDR file has finished, a
final move/rename operation (no copy) to filename ‘CDRReport…txt’ will be executed. The
move/rename is the last operation. If the file exists with the same name, a <seq_number> will
be added to the filename.
Example daily file:
CDRReport_20010125_020000.txt
A31003-H3460-M104-4-76A9, July 2012

CDRReport_20010126_020000_1.txt
CDRReport_20010126_020000_2.txt
The file format is position oriented and contains the following fields:
For all fields in the format:
– Alignment = Left
– Filler = Blank for all fields
Legend:
NO ET Name H150 Pos. L A FI Definition Element in Hi-

Path COL
1 V Service In- 1 1 0 0 = Voice, 1 = Data SERVICE
dicator
2 V Source De- 2 1 2 1 = Gateway, 2 = Sub- STNID
vice Type scriber
3 F Delimiter 3 1 Blank
4 V Start Date 4-13 10 L Start of call (date), STMONTH
Format: “mm/dd/yyyy” STDAY
STYEAR
6 V Start Time 15-22 8 L Start of call (time), STHOUR
Format: “hh:mm:ss” STMIN
STSEC
8 V Duration 24-35 12 L Call duration in format CONDAY
ddd:hh:mm:ss, e.g. (new H5000)
“001:00:04:34” CONHOUR
CONMIN
CONSEC
Table 6-61 H5000_V30 -Input format for HiPath 5000 V3.0 (Single System)
A31003-H3460-M104-4-76A9, July 2012



Path COL
10 V Call For- 37 1 C F = ongoing, C = last H5CALLINFO
warding / record (new H5000)
Diverting
11 V Destination 38 1 2 1 = Gateway, 2 = subscrib- DESTPID
answering er
type
12 F Blank 39 1 - - (do not understand – re-
ally)
13 V ACD / Non- 40 1 - A = ACD call, “-“ = Non- ACDINFO (new
ACD ACD H5000)
14 V Call Type 41 1 3 1 = incoming (ext./int.) CONNTYPE
2 = outgoing (int./ext.)
3 = internal (int./int.)
4 = transit (ext./ext.)
16 V Calling Par- 43-57 15 L (Name) / Number PAYPART
ty
18 V Destination 59-80 22 L (Name) / Number DESTPTY
/ Answering
number
20 V Originally 82-96 15 L (Name) / Number CALLEPTY
dialled / di-
verting
number
22 V Dialled Ac- 98-102 5 L Gateway access code GWCODE
cess Code (new H5000)
24 V Source 104-118 15 L IP address SOURCEIP
gateway (new H5000)
Table 6-61 H5000_V30 -Input format for HiPath 5000 V3.0 (Single System) (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012


Path COL
26 V Destination 120-134 15 L IP address DESTIP (new
gateway H5000)
28 V Unique ID 136-167 32 L Unique ID RECNO
30 V Leg ID 169-200 32 L ID for relating multiple GLOBSEQ
legs of a call.
- Local global (leg) id – no
network functionality
32 V Call Discon- 202 1 1 Disconnect reasons CAUSE
nect Rea- 0 = Unknown Reason
son 1= Normal call hang-up
2= destination reject
3=lines busy
4=out of service
5=destination busy
6=no answer/abandoned
34 V Detailed 204 1 0 Type of connection CHOFCON
Call Type 0=none
1=call type EMERGENCY
2=call type LOCAL
3=call type NATIONAL
4=call type INTERNA-
TIONAL
5=call type EXTERNAL
6=call type SERVICE
7=call type TOLL_FREE
8=call type PREMIUM
9=call type DUMMY
36 V Last For- 206-220 15 L Redirecting party, party RTINGPTY
warding who forwarded this call (A-
Party party – in record of B-par-
ty)
A31003-H3460-M104-4-76A9, July 2012



Path COL
38 V Last Trans- 222-236 15 L Transferring party (e.g. at- TRNSFPTY
ferring Party tendant console), party
that transferred a call
40 V Local Gate- 238-252 15 L ID of generating gate- GENID (new
keeper ID keeper H5000)
42 V Remote 254-268 15 L ID of receiving gatekeeper RECEIVID
Gatekeeper (new H5000)
ID
E CR 269 1 Carriage Return
E LF 270 1 Line Feed
A31003-H3460-M104-4-76A9, July 2012

H8000_V22 – OpenScape Voice Input Format V2.2 (single PABX)

Legend:
No. = sequential element number;
ET = element type: F = fixed text, V = variable element;
L = element length; A = alignment; FI = pad character: Empty = space.
No. ET OpenScape Type Min Max Definition Element in Hi-
Voice Name Len Len Path COL
1 V Sequential INT 1 6 This field provides the sequential number of MSGNO
Record Num- the call record within the file.
ber
2 V Record Type ENUM 8 8 00000000=Standard Call Record RECIDENT
Def: 00000001=Intermediate Call Record (new)
00000 00000002=AIN Trigger Record
000 00000003=INAP Trigger Record
00000004=Queue Record
00000005=Call Forwarding Record
00000006=FMC Record
10000000=Change of Time Audit Record
10000001=Long Call Audit Record
10000010=Change of Software Audit Record
10000100=Feature Activation/Deactivation
Record
3 V Start Time DATE 26 26 This field provides the call setup start date/ STDATETIME
time stamp to the nearest 1/10 of a second. (new)
4 V Duration of call INT 1 10 This field provides subscriber call connect CONTOT
Def:0 time in tenths of seconds. For Long Call Dura-
tion Records, this field provides total subscrib-
er call connect time upon record generation.
(An INT value supports call duration in excess
of 13.6 years). This field is zero if the call was
not completed (i.e. attempts other than an-
swer).
5 V Switch ID CHAR 1 16 A 16-character string which identifies the HIQ SWITCHID
Def: 8000 system by Host Name. Default value is (new)
Blank no character (NULL).
6 V Record ID CHAR 59 59 DATE plus an incrementing 32 character nu- RECID
merical sequence which uniquely identifies (new)
each record and, in combination with Switch
ID, allows troubleshooting even after CDR(s)
are normalized and combined with data from
other devices.
7 V Customer CHAR 0 16 An up to 16-character string that associates CUSTNAME
Name/Number Def: the initiator of a call with the provisioned (as- (new)
Blank signed) customer number or name. Default
value for HIQ 8000 is NULL.
Table 6-62 H8000_V22 – OpenScape Voice Input Format V2.2
A31003-H3460-M104-4-76A9, July 2012



8 V Account Code CHAR 0 15 At the moment not filled ACCTCODE
Def:
Blank
9 V Call Segment INT: 1 10 This field provides the time elapsed, in tenths SEGDUR
Duration Def:0 of seconds, since the last record generated (new)
for this particular call (e.g., for Long Call Dura-
tion Records and other calls with multiple
records). For conventional CDR(s), the value
of this field will be identical to that delivered in
Duration of Call Field 4. For Long Call Dura-
tion Records, the value will be the time
elapsed since the Long Call Duration Record
immediately prior. This field is zero if the call
was not completed (i.e. attempts other than
answer).
10 V Carrier ID Pa- CHAR 0 6 An up to 6-character string, this field identifies CARRIER
rameter Def: the Originating Carrier ID provided by the IAM
Blank message. Default value is no character
(NULL).
11 V Terminating CHAR 0 30 An up to 30-character string, which associ- DESTPTY
Number/Called Def: ates the recipient of a call with the provisioned
Party Blank (assigned) customer number. This field repre-
sents the number of the user to whom the call
is directed.
For a Toll-Free 800 call, this field will contain
the translated 800 number returned from the
Service Control Point(SCP). Default value is
no character (NULL).
12 V Originating CHAR 0 20 An up to 20-character string, which associ- CALLIPTY
Number/Call- Def: ates the initiator of a call with the provisioned
ing Party Blank (assigned) customer number or name. This
field provides the number of the party initiating
the call. Default value is no character (NULL).
13 V ANI CHAR 0 20 Automatic Number Identification This is a PAYPART
Def: packed BCD field and allows up to 20 numeric
Blank only digits. This ISUP field often provides the
number of a third party responsible for paying
for the call. Default value is no character
(NULL).
14 V Toll-Free Origi- DIGIT 0 10 This field will contain the original 800 dialed TOLLNO
nal 800 Dialed Def: number. This is a packed BCD field and al- (new)
Number / BG Blank lows up to 20 numeric only digits. Default val-
Dialed Digits ue is no character (NULL).
Table 6-62 H8000_V22 – OpenScape Voice Input Format V2.2 (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012


15 F LNP Generic CHAR 0 10 For a recipient switch in a Local Number Port- CAELNPNO
Address Pa- Def: ability scenario, this field provides the actual (new)
rameter Blank 10-character Called Party number after the
numbers in the Called Party field have been
replaced by the Local Routing Number. This is
a packed BCD field and allows up to 20 nu-
meric only digits. Default value is no character
(NULL).
16 V Call Type ENUM 0 3 Specifies the type of call attempt: CALLTPYE
Def: 0=Voice call (new)
Blank 1=Data call
5=International Call
102=T102 Test Call
108=T108 Test Call
109 = Network Loopback
110 = Network Continuity
Default value is no character (NULL).
17 V Information INT 0 10 Specifies the amount of bandwidth reserved TRANSRATE
Transfer Rate Def: through the gateway to carry the call. The (new)
Blank number provided is in bits per second. Default
value is no character (NULL).
18 V Attempt Indica- ENUM 0 1 Specifies the result of the call attempt: SUPLSERV
tor Def: 0=Call was completed.
Blank 1=Call was not completed due to called party
busy.
2=Call was not completed due to invalid di-
aled number.
3=Call was not completed due to lack of avail-
able lines/trunks to complete the call.
4=Call was not completed due to calling party
aborting the call prior to answer.
5=Call was not completed due to called party
not answering the call.
6=Call was not completed due to a network
problem.
7=Call was not completed due to unknown
reasons.
8=Call was not completed due to no subscrib-
er account.
9=Call was not completed due to unautho-
rized subscriber.
10=LNP Query on Response
A31003-H3460-M104-4-76A9, July 2012



19 V Release ENUM 0 3 Specifies the cause for call completion. Enu- CAUSE
Cause/Com- Def: merated values taken directly from signaling
pletion Indica- Blank message field.
tor PRI Release Cause Codes (CCITT list from
Q.931, unless otherwise indicated):
001=unassigned (unallocated) number
002=no route to specified transit network
003=no route to destination
004=send special information tone (TR-NWT-
1268 lists alternate national-specific cause
“vacant code”)
005=misdialed trunk prefix (no procedure
specified for U.S. networks)
006=channel unacceptable
007=call awarded and being delivered in an
established channel
008=preemption (TR-NWT-1268 lists alter-
nate national-specific cause “prefix 0 dialed in
error”)
009=preemption – circuit reserved for reuse
(TR-NWT-1268 lists alternate national-specif-
ic cause “prefix 1 dialed in error”)
010=prefix 1 not dialed (National-specific val-
ue, per TR-NWT-1268)
011=excessive digits received, call is pro-
ceeding (National-specific value, per TR-
NWT-1268)
014=Ported Out Subscriber
016=normal call clearing
017=user busy
018=no user responding
019=user alerting, no answer
020=subscriber absent
021=call rejected
022=number changed
023=redirect to new destination (GR-246-
CORE lists alternate ANSI cause “unallocated
destination number”)
024=unknown business group (ANSI cause,
per GR-246-CORE)
025=exchange routing error (ANSI cause, per
GR-246-CORE)
026=misrouted call to a ported number (ANSI
cause, per GR-246-CORE)
027=destination out of order (GR-246-CORE
lists alternate ANSI cause “number portability
(NP) query on release (QoR) – number not
found”; no procedure specified for U.S. net-
works)
A31003-H3460-M104-4-76A9, July 2012

028=invalid number format (incomplete num-
ber)
029=facility rejected
030=response to status inquiry
031=normal, unspecified
034=no circuit/channel available
038=network/channel out of order
041=temporary failure
042=switching equipment congestion
043=access information discarded
044=requested circuit/channel not available
045=preemption (ANSI cause, per GR-246-
CORE)
046=precedence call blocked
047=resource unavailable, unspecified
050=requested facility unsubscribed
051=call type incompatible with service re-
quest (ANSI cause, per GR-246-CORE)
053=outgoing calls barred within CUG (no
procedure specified for U.S. networks)
054=call blocked due to group restrictions
(ANSI cause, per GR-246-CORE)
055=incoming calls barred within CUG (no
procedure specified for U.S. networks)
057=bearer capability not authorized
058=bearer capability not presently available
062=inconsistency in designated outgoing ac-
cess information and subscriber class
063=service or option not available, unspeci-
fied
065=bearer capability not implemented
066=channel type not implemented
069=requested facility not implemented
070=only restricted digital information bearer
capability is available
079=service or option not implemented, un-
specified
081=invalid call reference value
082=identified channel does not exist
083=a suspended call exists, but this call
identity does not
084=call identity in use
085=no call suspended
086=call having the requested call identity
has been cleared
087=user not member of CUG (no procedure
specified for U.S. networks)
A31003-H3460-M104-4-76A9, July 2012



088=incompatible destination
090=non-existent CUG (no procedure speci-
fied for U.S. networks)
091=invalid transit network selection
095=invalid message, unspecified
096=mandatory information element is miss-
ing
097=message type non-existent or not imple-
mented
098=message not compatible with call state
or message type non-existent or not imple-
mented
099=information element non-existent or not
implemented
100=invalid information element contents
101=protocol error, threshold exceeded (TR-
NWT-1268 lists alternate network-specific
cause “protocol error, threshold exceeded”)
102=recovery on time expiry
103=parameter nonexistent or not implement-
ed – passed on
110=message with unrecognized parameter
111=protocol error, unspecified
127=interworking, unspecified
20 V Bearer Capa- ENUM 0 1 Specifies the requested bearer capability: BEARCAP
bility Request Def: 0=Circuit mode speech. (new)
Blank 1=Circuit mode 3.1 kHz audio.
2=Circuit mode / unrestricted digital informa-
tion at 56 Kbps.
tion at 64 Kbps.
tion at Nx64 Kbps.
5=Not Recorded
6=Unrestricted digital information with an-
nouncement
7=Restricted digital information
8=Video
21 V Ingress Carrier String 0 6 An up to 6-character string, this field identifies INGCARRIER
Identification Def: the interconnected carrier on the ingress side (new)
Blank of the call leg. Default value is no character
(NULL).
A31003-H3460-M104-4-76A9, July 2012


22 V Egress Carrier String 0 6 An up to 6-character string, this field identifies EGCARRIER
Identification Def: the interconnected carrier on the egress side (new)
Blank of the call leg. Default value is no character
(NULL).
23 V Operator Indi- ENUM 1 1 0=Direct Dialed (default) CWF
cator Def:0 1=Operator Involved
2=Unknown
3=Collect Call
24 V Ingress DS0 ID INT 0 10 Identifies the incoming DS0 used to carry the SHFININDS
(Ingress Shelf) Def: call by internal DS0 numerical ID. (For clus- (new)
Blank tered media gateways, incoming DS0 ID for
Ingress Shelf.) Default value is no character
(NULL).
25 V Egress DS0 ID INT 0 10 Identifies the outgoing DS0 used to carry the SHFINOUTDS
(Ingress Shelf) Def: call by internal DS0 numerical ID. (For clus- (new)
Blank tered media gateways, outgoing DS0 ID for
Ingress Shelf.) Default value is no character
(NULL).
26 V Orig Nature of ENUM 0 3 Specifies the NOA from an incoming call as ORGNATADR
Address Def: populated in the IAM: (new)
Blank 0=Voice call
1=Data call
5=International Call
102=T102 Test Call
108=T108 Test Call
109 = Network Loopback
110 = Network Continuity
27 V Empty Field 0 0 Not Used, default value is no character TEXT01
(NULL). (new)
28 V Empty Field 0 0 Not Used, default value is no character TEXT02
(NULL). (new)
29 V Route Selec- ENUM 1 1 Indicates the basis on which Route Selection ROUTESEL
tion Def:0 is made. Current default value for HIQ 8000 is (new)
“0”.
0=Standard (FCS)
1=Least-Cost
2=Overflow Routing
3=TBD
A31003-H3460-M104-4-76A9, July 2012



30 V Ingress Signal- ENUM 0 2 Indicates the type of signaling used on the line SIGTYPINCO
ing Type Def: for the incoming side. (new)
Blank 0=ISDN PRI – Network Side NI-2
1=ISDN PRI – Network Side 5ESS
2=ISDN PRI – Network Side DMS100
4=SS7 – ANSI
5=SS7 – ITU
6=ATM Forum UNI 3.0
7=ATM Forum UNI 3.1
8=ATM Forum UNI 4.0
9=CAS – (variety of protocols TBD)
10=IPDC
11=MGCP
12=H.323
13=CAS Loop Start
14=CAS Ground Start
15=CAS E&M
16=CAS Wink
17=SIP
18=SIP T
19=ISDN PRI – 5ESS Custom
31 V Egress Signal- ENUM 0 2 Indicates the type of signaling used on the line SIGTYPOUTC
ing Type Def: for the outgoing side. (new))
Blank 0=ISDN PRI – Network Side NI-2
2=ISDN PRI – Network Side DMS100
4=SS7 – ANSI
5=SS7 – ITU
6=ATM Forum UNI 3.0
7 =ATM Forum UNI 3.1
8=ATM Forum UNI 4.0
9=CAS – (variety of protocols TBD)
10=IPDC
11=MGCP
12=H.323
13=CAS Loop Start
14=CAS Ground Start
15=CAS E&M
16=CAS Wink
17=SIP
18=SIP T
19=ISDN PRI – 5ESS Custom
A31003-H3460-M104-4-76A9, July 2012


32 V Incoming PRI CHAR 0 16 Identifies the incoming PRI or Trunk Group INTNTGR
Name/Trunk Def: used to carry the call by Group name (provid-
Group Blank ed by provisioned data). For trunk groups, the
field is populated with the trunk group num-
ber; for PRIs, the field is populated with the
PRI name. Default value is no character
(NULL).
33 V Incoming PRI/ INT 0 10 Identifies the incoming DS0 used to carry the INTNBCHA
Trunk Group Def: call by internal DS0 numerical ID. For trunk
Member ID Blank groups, the field is populated with the TCIC;
for PRIs, the field is populated with the B
channel index. Default value is no character
(NULL).
34 V Outgoing PRI CHAR 0 16 Identifies the outgoing PRI or Trunk Group TKNOTRGR
Name/Trunk Def: used to carry the call by Group name (provid-
Group ID Blank ed by provisioned data). For trunk groups, the
field is populated with the trunk group num-
ber; for PRIs, the field is populated with the
PRI name. Default value is no character
(NULL).
35 V Outgoing PRI/ INT 0 10 Identifies the outgoing DS0 used to carry the TKNOBCHA
Trunk Member Def: call by internal DS0 numerical ID. For trunk
ID Blank groups, the field is populated with the TCIC;
for PRIs, the field is populated with the B
channel index. Default value is no character
(NULL).
36 F Ingress DS0 ID INT 0 10 Identifies the incoming DS0 used to carry the SHFOUINDS
(Egress Shelf) Def: call by internal DS0 numerical ID. (For clus- (new))
Blank tered media gateways, incoming DS0 ID for
Egress Shelf.) Default value is no character
(NULL), especially where a single shelf was
used to switch call.
37 F Egress DS0 ID INT 0 10 Identifies the outgoing DS0 used to carry the SHFOUOUTDS
(Egress Shelf) Def: call by internal DS0 numerical ID. (For clus- (new))
Blank tered media gateways, outgoing DS0 ID for
Egress Shelf.) Default value is no character
(NULL), especially where a single shelf was
used to switch call.
38 V Incoming Trunk ENUM 1 1 0=Tandem or Access Tandem Exchange INTNTGRID
Group Signal- Def:0 1=Access Exchange (new)
ing Type 2=Remote Access Server
3=Integrated Access Device
4=PBX/KTS
5=Not Provisioned
A31003-H3460-M104-4-76A9, July 2012



39 V Outgoing Trunk ENUM 1 1 0=Tandem or Access Tandem Exchange TKNOTRGRID
Group Signal- Def:0 1=Access Exchange (new)
ing Type 2=Remote Access Server
3=Integrated Access Device
4=PBX/KTS
5=Not Provisioned
40 V Originating ENUM 1 3 001=Originating party directory number data CALLIID
Party Identifier Def:99 002=Terminating party directory number data STNID
9 003=Billing party directory number data
004=Aggregate/feature record directory num-
ber(s) data
005=Detailed/feature record directory num-
ber(s) data
006=Third party verification
007=Busy line verification
008=Redirecting
009=Directory Assistance - Requested party
directory number data
010=Incoming Trunk Group
011=Outgoing Trunk Group
012=Reserved
013=Operator Services Switch
101=Originating party directory number data -
native
102=Terminating party directory number data
- native
110=Incoming Trunk Group - native
111=Outgoing Trunk Group - native
201=Originating Party directory number data -
unbundled
- unbundled
210=Incoming Trunk Group - unbundled
resold
- resold
310=Incoming Trunk Group - resold
900=Originating Side Endpoint on the
hiQ(Originating)
901=Originating Side Endpoint not on the
hiQ(Incoming)
902=Terminating Side Endpoint on the
hiQ(Terminating)----Note 1
903=Terminating Side Endpoint not on the
hiQ(Outgoing)----Note 1
999=Unknown
Note 1: Not applicable for this field
A31003-H3460-M104-4-76A9, July 2012


41 V Terminating ENUM 1 3 001=Originating party directory number data DESTPID
Party Identifier Def:99 002=Terminating party directory number data
9 003=Billing party directory number data
004=Aggregate/feature record directory num-
ber(s) data
005=Detailed/feature record directory num-
ber(s) data
006=Third party verification
007=Busy line verification
008=Redirecting
009=Directory Assistance - Requested party
directory number data
010=Incoming Trunk Group
011=Outgoing Trunk Group
012=Reserved
013=Operator Services Switch
native
- native
110=Incoming Trunk Group - native
111=Outgoing Trunk Group - native
201=Originating Party directory number data -
unbundled
- unbundled
210=Incoming Trunk Group - unbundled
resold
- resold
310=Incoming Trunk Group – resold
900=Originating Side Endpoint on the
hiQ(Originating)----Note 1
901=Originating Side Endpoint not on the
hiQ(Incoming)----Note 1
902=Terminating Side Endpoint on the
hiQ(Terminating)
903=Terminating Side Endpoint not on the
hiQ(Outgoing)
999=Unknown
Note 1: Not applicable for this field
42 F JIP Source In- ENUM 1 1 1=LNP Database Dip JIPSOURCE
dicator Def:5 2=Switching System Data (new)
3=Incoming Signaling
4=Switch LRN/GUBB LNP Database
5=Unknown (Default)
A31003-H3460-M104-4-76A9, July 2012



43 F LRN Source In- ENUM 1 1 1=LNP Database Dip LRNSOURCE
dicator Def:5 2=Switching System Data (new)
3=Incoming Signaling
4=Switch LRN/GUBB LNP Database
5=Unknown (Default)
44 F Jurisdiction In- DIGIT 0 10 This field identifies the switching entity that JIPINFO
formation Pa- Def: provides service to the originating party. The (new)
rameter (JIP) Blank identity is a Location Routing Number (LRN).
Required for Table 731 in LNP Module 720.
Data provided by ISUP message.
45 F Location Rout- DIGIT 0 10 This field identifies the switching entity that LRNNO
ing Number Def: provides service to the portable party. The (new)
(LRN) Blank identity is a Location Routing Number (LRN).
Data provided by SS7 message.
46 V Originating ENUM 1 2 01=Successful Query CALLISTAT
Party Query Def:9 02=No query response message received as STNSTAT
Status Indicator response (new)
03=AIN CONTINUE message received as re-
sponse
04=Protocol error in received response mes-
sage
05=Error detected in response data
06=Query rejected
07=Last Resort routing
09=No query done (Default)
11=Successful QoR (Obsolete; unused.)
12=QoR initiated (Obsolete; unused.)
13=QoR received (Obsolete; unused.)
14=Portability Outside the Rate Center
(PORC) Last Resort - Donor
15=PORC Last Resort - Surrogate Donor
99=Query unsuccessful, reason unknown
A31003-H3460-M104-4-76A9, July 2012


47 V Terminating ENUM 1 2 01=Successful Query DESTPSTAT
Party Query Def:9 02=No query response message received as (new)
Status Indicator response
03=AIN CONTINUE message received as re-
sponse
04=Protocol error in received response mes-
sage
05=Error detected in response data
06=Query rejected
07=Last Resort routing
09=No query done (Default)
11=Successful QoR (Obsolete; unused.)
12=QoR initiated (Obsolete; unused.)
13=QoR received (Obsolete; unused.)
14=Portability Outside the Rate Center
(PORC) Last Resort - Donor
15=PORC Last Resort - Surrogate Donor
99=Query unsuccessful, reason unknown
48 V Call Answer DATE 0 26 Call Answer Time to nearest 1/10th second. RINGDUR
Time Def: Default value is no character (NULL).
Blank
49 V Call Release DATE 0 26 Call Release Time to nearest 1/10th second. RELDUR
Time Def: Default value is no character (NULL). (new)
Blank
50 V Incoming Carri- DATE 0 26 Incoming Carrier Connect Time to nearest 1/ INCACONDUR
er Connect Def: 10th second. Default value is no character (new)
Time Blank (NULL).
51 V Incoming Carri- DATE 0 26 Incoming Carrier Release Time to nearest 1/ INCARELDUR
er Release Def: 10th second. Default value is no character (new)
Time Blank (NULL).
52 V Outgoing Carri- DATE 0 26 Outgoing Carrier Connect Time to nearest 1/ OTCACON-
er Connect Def: 10th second. Default value is no character DUR
Time Blank (NULL). (new)
53 V Outgoing Carri- DATE 0 26 Outgoing Carrier Release Time to nearest 1/ OTCARELDUR
er Release Def: 10th second. Default value is no character (new)
Time Blank (NULL).
A31003-H3460-M104-4-76A9, July 2012



54 F Dialing and ENUM 1 1 0=No IC/INC involved in call (default) DAILID
Presubscrip- Def:0 1=Carrier Access Code (CAC) not dialed, (new)
tion Indicator customer presubscribed, no presubscription
indication arrangement with IC/INC
2=CAC dialed, customer not presubscribed,
no presubscription indication arrangement
with IC/INC
3=950-XXXX dialed
4=CAC not dialed, customer presubscribed,
presubscription arrangement with IC/INC (not
currently supported)
5=CAC dialed, customer not presubscribed,
presubscription indication arrangement with
IC/INC. (Customer “not presubscribed” indi-
cation provided to IC/INC.) (not currently sup-
ported)
6=CAC dialed, customer presubscribed, pre-
subscription indication arrangement with IC/
INC. (not currently supported)
7=CAC dialed, customer presubscribed, no
presubscription indication arrangement with
IC/INC.
8=CAC not dialed, customer not presub-
scribed, no presubscription indication ar-
rangement with IC/INC.
9=CAC not dialed, customer presubscribed,
presubscription indication arrangement for-
warded to the IC/INC (not currently support-
ed).
55 F Calling Party ENUM 1 1 1=Feature not used or not recorded SUBADCALLI
Subaddress Def:1 2=Feature used (new)
Delivery
56 F Called Party ENUM 1 1 1=Feature not used or not recorded SUBADCALLE
Subaddress Def:1 2=Feature used (new)
Delivery
57 F Low-Layer ENUM 1 1 1=Feature not used or not recorded LAYLOWINFO
Compatibility Def:1 2=Feature used (new)
Information De-
livery
58 F High-Layer ENUM 1 1 1=Feature not used or not recorded LAYHIGINFO
Compatibility Def:1 2=Feature used (new)
Information De-
livery
59 F User-to-User ENUM 1 1 1=Feature not used or not recorded PARTYINFO
Information/ Def:1 2=Feature used, presumed delivered (new)
Fast Select 3=Feature used, but not delivered
A31003-H3460-M104-4-76A9, July 2012


60 F Incoming IC/ ENUM 0 1 0=Direct ICNINRID
INC Routing In- Def: 1=Tandem (new)
dicator Blank 2=CAP direct from end office
3=CAP direct from AP tandem
4=Tandem signaling to TSP - CAP trunks
5=Tandem from another LEC’s end office
(LEC to LEC Interconnection)
61 F IC/INC Call ENUM 0 2 00=call is abandoned or released before the ICNRSTAT
Event Status Def: IAM is sent by the originating EC’s EO or be- (new)
Blank fore the EXM is received by the originating
EC’s EO from the EC’s AT.
01=call is abandoned or released after the
EXM is received by the originating EC’s EO
from the EC’s AT.
04=timeout occurs after the EXM is received
by the originating EC’s EO from the EC’s AT.
06=(terminating access only) call disconnects
in the terminating network due to a network
management procedure. This occurs before
called party off-hook but after the IAM is re-
ceived.
ACM is received by the originating EC’s EO.
08=(terminating access only) terminating end
of the call either did not recognize the called
NXX or that the NXX received is not valid in
the terminating network. Since the called
number has been transmitted to the terminat-
ing end at this point, the digits should be in-
serted into the proper terminating number
field of the AMA record, if one is generated for
the call, and the correct value set in the Study
Indicator field (Table 8) as defined earlier in
this Division of BAF Tables.
09=(terminating access only) call cannot be
set up to the terminating office in the terminat-
ing network. An example of the type of failure
that could occur is a link failure between the
AT and the terminating EO. This value is used
to cover all failures at the terminating end ex-
cept those failures indicated by values "06"
and "08".
ANM is received by the originating EC’s EO.
A31003-H3460-M104-4-76A9, July 2012



62 F Outgoing IC/ ENUM 0 1 0=Direct ICNOUTRID
INC Routing In- Def: 1=Tandem (new)
dicator Blank 2=CAP direct to end office
3=CAP direct to AP tandem
4=Tandem signaling to TSP - CAP trunks
5=Tandem from another LEC’s end office
(LEC to LEC Interconnection)
63 V Service Fea- ENUM 1 3 Used to record SCP information in the CDR. SCPINFO
ture Codes Def:27 Information taken directly from Service Fea- (new)
ture Identification in the Billing Indicators pa-
rameter of the SCP response, and simply
translated into ASCII text format. Populates
BAF Table 12.
000=None of the following values apply
001=LEC-owned standard interface public
line
006=Centrex attendant
008=INWATS
010=Three-Way Calling
012=Call Forwarding
014=Call Forwarding Busy Line or Call For-
warding Don’t Answer
015=Public Switched Digital Service (PSDS)
with Toll-Free Service
017=Remote Call Forwarding
018=Usage-Sensitive Three-Way Calling
023=Cellular Mobile Carrier – Type-2A
026=Private Virtual Network – Remote ac-
cess indicator
027=AIN – Default
049=Usage-Sensitive Call Forwarding
154=Last Call Return + 3 Way Calling
301=Last Call Return
A31003-H3460-M104-4-76A9, July 2012


64 V Per Call Fea- BIT 1 17 This field describes the ‘per call feature’ acti- SERVICE
ture ENUM vation and the feature(s) usage in a normal
Def:0 call setup. In cases where a different feature
? name is commonly used in other markets, the
alternate feature name is also shown.
0=no feature
1=Anonymous Call Rejection Treatment
2=Call Forward Busy Line / Call Forward on
Busy
4=Call Forward Don’t Answer / Call Forward
on No Answer
8=Call Forward Variable / Call Forward Un-
conditional
16=Calling Number Delivery Blocking / Call-
ing Line Identity Restriction
32=Calling Name Delivery Blocking
64=Calling ID Delivery and Suppression
128=Calling Number Delivery to Called / Call-
ing Line Identity Presentation
256=Calling Name Delivery to Called
512=Private/OOA Delivery to CND
1,024= Private/OOA Delivery to CNAM
2,048=Both Name and Number Delivered
4,096=Both Name and Number not Delivered
8,192=Calling Number but not Name Deliv-
ered
16,384=Calling Name but not Number Deliv-
ered
32,768=Enhanced Call Forwarding / Selec-
tive Call Forwarding (Note 1)
65,536=Remote Activation Call Forwarding
131,072=Remote Call Forwarding / Perma-
nent Call Forwarding
262,144=Selective Call Forwarding (Node 2)
524,288=Distinctive Ringing / Call Waiting
1,048,576=Malicious Call Trace / Malicious
Caller ID
2,097,152=Selective Call Rejection
4,194,304=Selective Call Acceptance
8,388,608=Usage Sensitive 3Way Calling
(Call Hold)
16,777,216=Usage Sensitive 3Way Calling
(Conference)
33,554,432=Automatic Recall
67,108,864=Automatic Recall (Level 2)
134,217,728=Automatic Call Return
268,435,456=Enhanced Anonymous Call Re-
jection
A31003-H3460-M104-4-76A9, July 2012



536,870,912=Local Call Park
1,073,741,824=Directed Call Park
2,147,483,648=Call Park Retrieval
4,294,967,296=Usage Sensitive Anonymous
Call Rejection
8,589,934,592=Usage Sensitive Call For-
warding Variable
17,179,869,184=Usage Sensitive Calling
Number Delivery
34,359,738,368=Usage Sensitive Calling
Name Delivery
68,719,476,736=Usage Sensitive Distinctive
Ringing Call Waiting
137,438,953,472=Usage Sensitive Enhanced
Anonymous Call Rejection
274,877,906,944=Usage Sensitive Malicious
Call Trace
549,755,813,888=Usage Sensitive Selective
Call Acceptance
1,099,511,627,776=US Selective Call Rejec-
tion
2,199,023,255,552=Usage Sensitive Calling
Num and Name Delivery
4,398,046,511,104=Cancel Call Waiting
8,796,093,022,208=Caller ID on Call Waiting
17,592,186,044,416=Call Transfer
35,184,372,088,832=Call Waiting Terminat-
ing / Call Waiting
70,368,744,177,664=Speed Calling
140,737,488,355,328=Teen Line
281,474,976,710,656=Toll Restriction
562,949,953,421,312=3Way Calling (Confer-
ence)
1,125,899,906,842,624=Usage Sensitive
Caller ID Delivery and Suppression
2,251,799,813,685,248=Caller Voiceback
4,503,599,627,370,496=Busy Line Verify
9,007,199,254,740,992=Usage Sensitive
Calling Name Delivery Blocking
18,014,398,509,481,984=Usage Sensitive
Calling Number Delivery Blocking
36,028,797,018,963,968=Completion of Calls
on Busy Subscriber
72,057,594,037,927,936=Completion of Calls
on No Reply
144,115,188,075,855,872=Last Outgoing
Number Redial
A31003-H3460-M104-4-76A9, July 2012


288,230,376,151,711,744=Last Incoming
Number Redial
576,460,752,303,423,488=Hot Line
1,152,921,504,606,846,976=Warm Line
2,305,843,009,213,693,952=Do Not Disturb
4,611,686,018,427,387,904=Outgoing Call
Barring
9,223,372,036,854,775,808=Override Call
Barring
Note 1: Enhanced Call Forwarding provides
CF on a time-of-day basis. In some markets,
the name Selective Call Forwarding is used
for time-of-day CF.
Note 2: This Selective Call Forwarding feature
is the CLASS feature used in the North Amer-
ican market.
65 V Forwarded CHAR 0 20 This 20-digit field specifies the forwarded DNBASESTA
from DN Def: Base Station DN. Default value is no charac- (new)
Blank ter (NULL).
66 V Intermediate CHAR 0 1 1=Intermediate CDR SIGDATA
Indicator Def: Only set if CDR is a ‘Intermediate Call Record’
Blank CDR.
(default is NULL)
67 V Originating BIT 0 7 This field identifies the Codec(s) negotiated in CLINEUSED
Side: Codec ENUM a call. The Audio Codec(s) are added in as- (new)
Negotiated Def: cending order and Video Codec(s) are added
Blank in a descending order.
1=G.711 64k PCM a-law compression
4=G.711 64k PCM u-law compression
16=G.722 compression to 64kbps
128=G.723 voice coding with compression
256=G.728
512=G.729
1,024=G.729 Annex A
2,048=is11172 capability
8,192=G.729 Annex B
16,384= G.729 Annex A & B
32,768=G.723.1 Annex capability
65,536=GSM full rate
131,072=GSM half rate
262,144=GSM enhanced full rate
524,288=G.726 40kbps
A31003-H3460-M104-4-76A9, July 2012



1,048,576=G.726 32kbps
2,097,152=G.726 24kbps
4,194,304=G.726 16kbps
8,388,608=G.729E
16,777,216=T.38_Loose/T.38_Fax
33,554,432=ILBC
67,108,864=BV16
134,217,728=T.38_Image
268,435,456=Telephone_Event
536,870,912= Clearmode 64K Unrestricted
*
Spare Codec Values
*
9,007,199,254,740,992=H263_2000 (video)
18,014,398,509,481,984=H263_1998 (video)
36,028,797,018,963,968=MP2T (video)
72,057,594,037,927,936=MPV (video)
144,115,188,075,855,872=H261 (video)
288,230,376,151,711,744=NV (video)
576,460,752,303,423,488=JPEG (video)
1,152,921,504,606,846,976=CE1B (video)
2,305,843,009,213,693,952=MPEG4 (video)
4,611,686,018,427,387,904=H264 (video)
9,223,372,036,854,775,808=H263 (video)
68 V Originating INT 0 3 Value of TOS in IP header. CTOSUSED
Side: TOS Def: (new)
Used Blank
69 V Originating ENUM 1 1 0=Default CRESINFO
Side: Reserva- Def:0 1=Guaranteed service (new)
tion Used 2=Controlled load
3=Best Effort
70 V Originating: INT 1 10 Received from MG at end of call. CPACKSENT
Packets Sent Def:0 (new)
71 V Originating: INT 1 10 Received from MG at end of call. COCTSENT
Octets Sent Def:0 (new)
72 V Originating: INT 1 10 Received from MG at end of call. CPACKRCVD
Packets Rcvd Def:0 (new)
73 V Originating: INT 1 10 Received from MG at end of call. COCTRCVD
Octets Rcvd Def:0 (new)
74 V Originating: INT 1 10 Received from MG at end of call. CPACKLOST
Packets Lost Def:0 (new)
75 V Originating: In- INT 1 10 Received from MG at end of call (millisec- CJITTER
terarrival Jitter Def:0 onds). (new)
A31003-H3460-M104-4-76A9, July 2012


76 V Originating: Av- INT 1 10 Received from MG at end of call (millisec- CTRNSDELY
erage Trans- Def:0 onds). (new)
mission Delay
77 E Terminating BIT 0 7 This field identifies the Codec(s) negotiated in DLINEUSED
Side: Codec ENUM a call. The Audio Codec(s) are added in as- (new)
Negotiated Def: cending order and Video Codec(s) are added
Blank in a descending order.
128=G.723 voice coding with compression
256=G.728
512=G.729
1,024=G.729 Annex A
8,192=G.729 Annex B
16,384= G.729 Annex A & B
32,768=G.723.1 Annex capability
65,536=GSM full rate
131,072=GSM half rate
262,144=GSM enhanced full rate
524,288=G.726 40kbps
1,048,576=G.726 32kbps
2,097,152=G.726 24kbps
4,194,304=G.726 16kbps
8,388,608=G.729E
16,777,216=T.38_Loose/T.38_Fax
33,554,432=ILBC
67,108,864=BV16
134,217,728=T.38_Image
268,435,456=Telephone_Event
536,870,912= Clearmode 64K Unrestricted
*
Spare Codec Values
*
9,007,199,254,740,992=H263_2000 (video)
18,014,398,509,481,984=H263_1998 (video)
36,028,797,018,963,968=MP2T (video)
72,057,594,037,927,936=MPV (video)
144,115,188,075,855,872=H261 (video)
288,230,376,151,711,744=NV (video)
576,460,752,303,423,488=JPEG (video)
A31003-H3460-M104-4-76A9, July 2012



1,152,921,504,606,846,976=CE1B (video)
2,305,843,009,213,693,952=MPEG4 (video)
4,611,686,018,427,387,904=H264 (video)
9,223,372,036,854,775,808=H263 (video)
78 V Terminating INT 0 3 Value of TOS in IP header. DTOSUSED
Side: TOS Def: (new)
Used Blank
79 V Terminating ENUM 1 1 0=Default DRESINFO
Side: Reserva- Def:0 1=Guaranteed service (new)
tion Used 2=Controlled load
3=Best Effort
80 V Terminating: INT 1 10 Received from MG at end of call. DPACKSENT
Packets Sent Def:0 (new)
81 V Terminating: INT 1 10 Received from MG at end of call. DOCTSENT
Octets Sent Def:0 (new)
82 V Terminating: INT 1 10 Received from MG at end of call. DPACKRCVD
Packets Rcvd Def:0 (new)
83 V Terminating: INT 1 10 Received from MG at end of call. DOCTRCVD
Octets Rcvd Def:0 (new)
84 V Terminating: INT 1 10 Received from MG at end of call. DPACKLOST
Packets Lost Def:0 (new)
85 V Terminating: In- INT 1 10 Received from MG at end of call (millisec- DJITTER
terarrival Jitter Def:0 onds). (new)
86 V Terminating: INT 1 10 Received from MG at end of call (millisec- DTRNSDELY
Average Trans- Def:0 onds). (new)
mission Delay
87 V BG Orig. MDR CHAR 0 10 General note for this Business Group field CMDRID
Customer ID Def: and all other BG related data fields that follow: (new)
Blank Some or all of current release supported BG
related data fields get populated when either
or both endpoint sides of the call is a BG facil-
ity and the BG MDR Capability is turned on.
Identifies the originating Business Group
MDR Customer ID. Default value is no char-
acter (NULL).
88 V BG Term. MDR CHAR 0 10 Identifies the terminating Business Group DMDRID
Customer ID Def: MDR Customer ID. Default value is no char- (new)
Blank acter (NULL).
89 V BG Authoriza- CHAR 0 15 Identifies the Authorization code digits em- AUTH
tion Code Def: ployed in the originating Business Group call.
Blank Default value is no character (NULL).
90 V BG Account CHAR 0 15 Identifies the Account code digits employed in ACCTCODEBG
Code Def: the originating Business Group call. Default (new)
Blank value is no character (NULL).
A31003-H3460-M104-4-76A9, July 2012


91 V BG Orig. Facili- ENUM 0 1 Identifies the originating Business Group Fa- CFATYPE
ty Type Def: cility type. (new)
Blank 0=Default None
1=BG Collocated Line
2=BG Collocated Attendant
3=BG Trunk Physical Private Facility
4=BG Trunk Virtual Private Facility
5=Non-BG Collocated Line
6=Non-BG Trunk Public Network Facility
7=BG FX
8=Other BG Facility
9=Other Non-BG Facility
Note: values 3, 4, 7, 8 and 9 are not supported
and are not populated in current release
92 V BG Term. Facil- ENUM 0 1 Identifies the terminating Business Group Fa- DFATYPE
ity Type Def: cility type. (new)
1=BG Collocated Line
2=BG Collocated Attendant
3=BG Trunk Physical Private Facility
4=BG Trunk Virtual Private Facility
5=Non-BG Collocated Line
6=Non-BG Trunk Public Network Facility
7=BG FX
8=Other BG Facility
9=Other Non-BG Facility
Note1: values 3, 4, 7, 8 and 9 are not support-
ed and are not populated in current release
Note2: This field will have a value of ‘5’ if the
originating BG facility (originating BG has
MDR Capability turned on) call terminates to
a non-BG residential line or to a different BG
line whose MDR Capability is turned off.
93 V BG Orig. Sta- CHAR 0 7 Identifies the seven digit (NXX-XXXX) DN for CFANUMID
tion Facility ID Def: an originating Business Group Subscriber. (new)
Blank Default value is no character (NULL).
94 V BG Term. Sta- CHAR 0 7 Identifies the seven digit (NXX-XXXX) DN for DFANUMID
tion Facility ID Def: a terminating Business Group Subscriber. De- (new)
Blank fault value is no character (NULL).
A31003-H3460-M104-4-76A9, July 2012



95 V BG Call Com- ENUM 0 1 Identifies the call completion code for an orig- CSIGCOMP
pletion Code Def: inating Business Group call. (new)
Blank 0=Completed: Call Connected without having
been queued at this switch (normal case)
1=Completed: Call Connected after having
been queued at this switch
2=Not Completed: Invalid Office or Area Code
3=Not Completed: Invalid Auth Code
4=Not Completed: Insufficient FRL
5=Not Completed: All facility busy or call fail-
ure at this switch
6=Not Completed: Call abandoned from
queue or abandoned before being put in
queue
7=Not Completed: Call timed out of queue
8=Not Completed/Unconnected: Non-queued
call abandoned after a trunk or line is seized
(normal case)
9=Not Completed/Unconnected: Queued call
abandoned after a trunk or line is seized
Note: values 1, 4, 6, 7 and 9 are not supported
and are not populated in current release
96 V BG Business ENUM 0 1 Identifies the originating Business Group call CSUPLINFO
Feature Code Def: feature code. (new)
1=Attendant Handled
2=Call Forward
3=Toll Diverted (not supported in current re-
lease)
97 F BG ARS Pat- Char 0 1 Identifies the Automatic Route Selection pat- ARSPATTGRP
tern Group Def: tern group employed in the originating Busi- (new)
Blank ness Group call (not implemented in current
release). Default value is no character
(NULL).
98 F BG FRL Char 0 1 Identifies the Facility Restriction Level em- FRL
Def: ployed in the originating Business Group call (new)
Blank (not implemented in current release). Default
value is no character (NULL).
A31003-H3460-M104-4-76A9, July 2012


99 F BG Access Char 0 5 Identifies the Business Group dialing prefix DAILINFOBG
Code Def: access code dialed by the originating Busi- (new)
Blank ness Group facility. This field is populated
only when the dialed prefix access code is an
on-net or off-net prefix access code type (i.e.
this field does not get populated for BG exten-
tion dialing, vertical service code dialing or ob-
viously if the Orig. BG MDR capability is
turned off). Default value is no character
(NULL).
100 Additional CDR BIT 1 1 Indicates the additional Record(s) that are CDRRECINFO
(AIN Call In- ENUM generated besides the Standard Call Record. (new)
volvement) Def:0 0=Default, Default value is no character
(NULL).
1=IN Record; For this value, there will be ad-
ditional AIN or INAP CDR(s) generated
Note: Either INAL(AIN) Services or INAP Ser-
vices software is started in the hiQ 8000 de-
pending whether the target is a World or US
market. Both Services cannot be active at the
same time.
2=Queue Record; One or more Queue
records are generated
4= FMC Record; One or more FMC records
are generated.
8=Call Forward Record: One or more Call
Forward records are generated.
101 V Original Dialed DIGIT 0 20 An up to 20-character string, this field identi- CALLEPTY
Digits Def: fies the original digits dialed by the originating
Blank endpoint.
For a BG endpoint and if the BG MDR Control
flag is turned on, the BG prefix on-net or off-
net access code (if dialed) is stripped and the
field is populated with the remaining original
dialed digits. Otherwise, the field is populated
with the original dialed digits.
Note: In some cases, the pattern will be the
same as the Terminating Number/Called Par-
ty (field #11) for the following cases:
The final translated terminating number is the
number dialed.
Calls involving Service Vertical Code dialed
for feature activation.
A31003-H3460-M104-4-76A9, July 2012



102 V BG Department CHAR 0 20 An up to 20-character string, this field identi- DEPARTNAME
Name Def: fies the BG Department Name that the BG (new)
Blank endpoint belongs to. This field is output re-
gardless of whether the BG MDR Control is
turned on or not.
103 V Number of Fax INT 1 10 This field is valid when the Media Type is Im- FAXPAGES
Pages Sent/ Def:0 age. This field represents the sum number of (new)
Received Fax pages sent and Fax pages received for a
Fax setup.
Note: The field’s population is dependent on

the gateway devices supporting the T.38 Fax
capability; otherwise it will default to NULL or
0 (i.e. if media type is Image).
104 V Media Type BIT 1 1 The field identifies the media type(s) used MEDIATYPE
ENUM during a call. (new)
Def:0 1=Audio
2=Video
4=IM (Instant Messaging)
8=Image (e.g. Fax)
105 V Incoming CHAR 0 4 Alphanumeric string representing incoming INPHCONT
phone-context Def: phone-context e.g. country code (new)
Blank
106 V Per Call Fea- BIT 1 1 This field describes the ‘per call feature’ fea- CALLFUSE
ture Extention ENUM ture(s) usage in a normal call setup. In cases (new)
Def:0 where a different feature name is commonly
used in other markets, the alternate feature
name is also shown. This field shows usage
of features beyond those covered by the field
"Per Call Feature".
0=Default None
1=reserved for R10.2
2=reserved for R10.2
4=Set Top Box Caller ID
107 V Indentification ENUM 0 10 Large Conference EVENTID
of Event Def: (new)
Blank
108 V RTP Indicator ENUM 0 1 Indicates when secure RTP is used RTPID
Def: (new)
Blank
109 V Spare CHAR 0 30 Not Used TEXT07
Def: (new)
Blank
Def: (new)
Blank
A31003-H3460-M104-4-76A9, July 2012


Def: (new)
Blank
Def: (new)
Blank
Def: (new)
Blank
Def: (new)
Blank
Def: (new)
Blank
Def: (new)
Blank
Def: (new)
Blank
Def: (new)
Blank
Def: (new)
Blank
Def: (new)
Blank
121 V Global Node ID CHAR 0 10 Global Node ID – Generating Node e.g. 10- GLOBLNODE
Def: 100-300 – unique only for one connection (new)
Blank (leg-id)
122 V Global Se- INT 0 10 Global Node Sequence number e.g. 1- GLOBLSEQ
quence number Def: 2147483647 – unique only for one connection
Blank (leg-ID)
123 V Transferred INT 0 20 Transferred from DN (DN = Directory Num- TRANSDN
from DN Def: ber) (new)
Blank e.g. 302106247123
124 V Thread Call CHAR 0 10 Thread Node ID-Generating Node e.g. 10- THRENODE
Node ID Def: 100-300 – keep the same for the whole call (new)
Blank scenario – network wide
125 V Thread Call INT 0 10 Thread Node Sequence number e.g. 1- THRESEQ
Node Se- Def: 2147483647 – keep the same for the whole
quence number Blank call scenario – network wide
A31003-H3460-M104-4-76A9, July 2012



126 V Ingress SIP CHAR 0 30 Ingress SIP endpoint / incoming trunk ad-
endpoint ad- Def: dress e.g. 152.25.10.256 INTNLIST
dress Blank INTNREAL
127 V Egress SIP CHAR 0 30 Egress SIP endpoint / outgoing trunk address
endpoint ad- Def: e.g. 152.25.10.256 TKNOLIST
dress Blank TKNOREAL
Def: (new)
Blank
Def: (new)
Blank
Def: (new)
Blank
A31003-H3460-M104-4-76A9, July 2012

AMPM_UV6 - Input format for AM/PM HiPath 4000

Legend:

ment
4 V ATTCALLP Attendant call priority 9-10 2 R
5 V ATTCALLR Attendant intercept reason 11-12 2 R
6 V ATTCALLT Attendant call type 13-14 2 R
8 V ATTQUEID Attendant queue id for AC-Win 17-18 2 R
Multipe Queue (MQ)
number
14 V CALLILV1 Subdomain number of calling 50-52 3 R 0
party
16 V CALLIONI Originating Network ID of the 55-56 2 R
calling party (privat/public)
connection
clear down
20 V CHOFCON Type of connection 83-83 1 L
VAT
Table 6-63 AMPM_UV6 - Input format for AM/PM HiPath 4000
A31003-H3460-M104-4-76A9, July 2012



ment
seconds
27 V DESTLV0 Node number of destination 110-112 3 R 0
number
28 V DESTLV1 Subdomain number of destina- 113-115 3 R 0
tion number
number
tion number
nected party)
32 V DISPCHRG Display of connection charge 141-149 9 R 0
with VAT
ond
41 V GLOBLLV0 Node number of global call ID 166-168 3 R 0
only local
ID (local)
(local)
recording point
Table 6-63 AMPM_UV6 - Input format for AM/PM HiPath 4000 (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012


ment
from INTNREAL
non-recording point
nection
54 V PPLV1 Subdomain number of paying 241-243 3 R 0
party
onds
onds
record is correct / incorrect or
double
call ID
(global) call ID
69 V THRELV2 Domain number of thread (glo- 279-280 2 R 0
bal) call ID
A31003-H3460-M104-4-76A9, July 2012



ment
non-recording point
point
cording point
nodes
76 V TRNSFLV0 Node number of transferring par- 307-309 3 R 0
ty (AC)
ring party (AC)
party (AC)
console)
connect
A31003-H3460-M104-4-76A9, July 2012

PM_UV6 - Input format for HiPath 4000

Legend:

ment
4 V ATTCALLP Attendant call priority 9-10 2 R
5 V ATTCALLR Attendant intercept reason 11-12 2 R
6 V ATTCALLT Attendant call type 13-14 2 R
8 V ATTQUEID Attendant queue id for AC- 17-18 2 R
Win Multipe Queue (MQ)
number
13 V CALLILV1 Subdomain number of call- 47-49 3 R 0
ing party
14 V CALLILV2 Domain number of calling 50-51 2 R 0
party
15 V CALLIONI Originating Network ID of the 52-53 2 R
calling party (privat/public)
16 V CALLIPTY Calling party; party that initat- 54-75 22 L
ed connection
17 V CARRIER Carrier; communication net- 76-76 1 L
work
18 V CAUSE Cause - of connection inter- 77-79 3 R 0
rupt / clear down
19 V CHOFCON Type of connection 80-80 1 L
20 V CONNSTEP Connection sequence; num- 81-83 3 R 0
ber
Table 6-64 PM_UV6 - Input format for HiPath 4000
A31003-H3460-M104-4-76A9, July 2012



ment
22 V CONTOT Connection duration total in 85-90 6 R 0
1/10 seconds
23 V DESTLV0 Node number of destination 91-93 3 R 0
number
24 V DESTLV1 Subdomain number of desti- 94-96 3 R 0
nation number
25 V DESTLV2 Domain number of destina- 97-98 2 R 0
tion number
26 V DESTPID Identification number of des- 99-99 1 L
tination number
27 V DESTPTY Destination number (new/ 100-121 22 L
connected party)
28 V END10 End-of-connection 1/10 of a 122-122 1 R 0
second
35 V GLOBLLV0 Node number of global call 137-139 3 R 0
ID only local
36 V GLOBLLV1 Subdomain number of global 140-142 3 R 0
call ID (local)
37 V GLOBLLV2 Domain number of global call 143-144 2 R 0
ID (local)
39 V HOLDDUR Hold duration in 1/10 sec- 153-157 5 R 0
onds
40 V INTNBCHA B-channel for real trunk no. 158-159 2 R 0
of the recording point
41 V INTNREAL Real trunk no. of the non-re- 160-164 5 L
cording point (see TKNORE-
AL)
Table 6-64 PM_UV6 - Input format for HiPath 4000 (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012


ment
42 V INTNTRGR Real trunk group number of 165-167 3 R 0
the non-recording point
43 V PAYPART Paying party; chargee of a 168-189 22 L
connection
45 V PPLV1 Subdomain number of pay- 193-195 3 R 0
ing party
46 V PPLV2 Domain number of paying 196-197 2 R 0
party
47 V QUEUEDUR Queueing duration in 1/10 198-202 5 R 0
seconds
48 V RECTYPE Record type 203-203 1 Right
49 V RINGDUR Ring duration; total in 1/10 204-206 3 R 0
seconds
54 V THRELV0 Node number of thread (glo- 216-218 3 R 0
bal) call ID
55 V THRELV1 Subdomain number of 219-221 3 R 0
thread (global) call ID
56 V THRELV2 Domain number of thread 222-223 2 R 0
(global) call ID
57 V THRESEQ Thread (global) call ID in net- 224-231 8 R 0
work
58 V TKNOBCHA B-channel for real trunk no. 232-233 2 R 0
of the non-recording point
59 V TKNOREAL Real trunk number of record- 234-238 5 R 0
ing point
60 V TKNOTRGR Real trunk group number of 239-241 3 R 0
recording point
61 V TRANSCNT Number of passed through 242-243 2 R 0
transit nodes
62 V TRNSFLV0 Node number of transferring 244-246 3 R 0
party (AC)
A31003-H3460-M104-4-76A9, July 2012



ment
63 V TRNSFLV1 Subdomain number of trans- 247-249 3 R 0
ferring party (AC)
64 V TRNSFLV2 Domain number of transfer- 250-251 2 R 0
ring party (AC)
console)
66 V UNANS Through connect / no 274-274 1 L
through connect
A31003-H3460-M104-4-76A9, July 2012

Additional CM Elements for Defining CDR Output Formats
6.5 Additional CM Elements for Defining CDR Output Formats

CM Elements Used for Generating History Output, page 6-185
CM Elements Used for Transforming Virtual to Physical Node Numbers, page 6-188
Loading the col_port and col_switch Tables, page 6-190
6.5.1 CM Elements Used for Generating History Output

COL uses CM data from the database in order to show it as part of the CDR output data or as
additional criteria in the filter.
Since personal data may change, COL must always get CM data that has been valid at the mo-
ment when COL data (CDRs) has been generated on the switch, and not the current CM data.
Therefore CM provides data which shows the history of adding/modifying/deleting for specific
objects.
CM provides additional data records in separate tables, showing the history of the changed ob-
ject.
The history records are stored by CM into the following tables:
● col_switch: history records for the switch object
● col_domain: history records for the domain object
● col_persdat: history records for the persdat object
● col_pin: history records for the pin object
These tables have the same structure as the original CM tables.The history records are gen-
erated when something has been changed in the original CM tables. They are created in online
mode, not in batch mode.
In general, history data will only be created if the flags admin.col_install and admin.col_sync
are set to “001”. This is done at installation time depending on the current licence information.
COL components always have to use date and time when CDR data has been generated to
select appropriate historical CM data.
COL is also maintaining the deletion of history records.
The following table specifies the CM elements used as part of the CDR output file or as addi-
tional criteria in the filter.
A31003-H3460-M104-4-76A9, July 2012


Short name Long name (eng) Usage Type Reference to

(M = Manager (Length) CM tables
A = Assistant)
persdat
ACCOUNT account number M char(15) persdat.accountnum
(own tabsheet AM)
BANKCODE bankcode M char(15) persdat.bankcode
(own tabsheet AM)
BUILDING building M char(30) persdat.building
CHARGEID chargeid M char(12) persdat.chargeid
(own tabsheet AM)
COMPANY company M char(30) persdat.company
COSTBEAR cost bearer M char(32) persdat.costbear
(own tabsheet AM)
COUNTRY country M char (2) persdat.country
EXTAREACOD ext. area code M char(6) persdat.ext_areacode
EXTCOUCODE ext. country code M char(2) persdat.ext_countrycode
EXTNETCODE ext. netcode M char(16) persdat.ext_netcode
EXTTIENUM tienum M char(6) persdat.tienum
FAXNUMBER fax number M char(22) persdat.faxnumber
FIRSTNAME christian name M char(30) persdat.christianname
LOCATION location M char(15) persdat.location
NAME name M char (50) persdat.name
ORG1 organisation 1 M char(40) persdat.org1
PAYPART extension M char ( 6) persdat.extension
PERSNUM personal number M char(32) persdat.persnum
(own tabsheet AM)
POSITION position M integer persdat.sequ_num
ROOM room M char(10) persdat.longname
SALUTATION salutation M char(15) persdat.salutation
SORTNAME sort name M char (60) persdat.sortname
SWITCHNAME switch name M char ( 4) persdat.switch_name
TITLE title M char(15) persdat.title
TRUNKACC trunk M char(1) persdat.direct_trunk_acc
USEGROUP user group M char(30) persdat.owner_group
switch M
AREACODE switch areacode M char(16) switch.areacode
CMVERSION switch version M char(5) switch.version
Table 6-65 CM Tables used for generating CDR output files
A31003-H3460-M104-4-76A9, July 2012


A = Assistant)
DOMAIN switch domain M char(8) switch.domain
NETCODE switch netcode M char(16) switch.netcode
NODENUM node number M char(10) switch.nodenum
SWCOUNTRY switch country M char(2) switch.country
SWITCHNAME switch name M char(4) switch.switch_name
or from chdmain
SYSNAME system name chdmain.mnemonic
SWITCHTYP switch typ M char(10) switch.switch_typ
domain M
(POSITION) position M integer pin.position
DOMAIN domain M char(8) switch.domain
PAYPART extension M char(6) pin.extension
pin M
PIN pin number M char(12) pin.pin_num
SWITCHNAME switch name M char(4) pin.switch_name
TIENUM tienum M char(6) domain.tienum
port M
CALLIPTY calling party (initiated M char(6) port.extension
connection) (If no match with this key VIRTLV0-
VIRTLV2 = 0 (default = 0))
SWITCHNAME switch name M char(4) port.switch_name
VIRTLV0 virtual node number of M, A int(3) port.node_id
calling party (char(10)) (there are two formats possible
three-stage or single stage or empty/
blank)
three <x>-<x>-<VIRTLV0>
single-stage <VIRTLV0>)
(If field is blank/empty VIRTLV0-
VIRTLV2 = 0 (default =0))
(If format is single-stage VIRTLV1 +
VIRTLV2 = 0)
VIRTLV1 virtual subdomain M, A int(3) port.node_id
number of calling party (char(10)) (three <x>-<VIRTLV1>-<x>)
VIRTLV2 virtual domain number M, A int(2) port.node_id
of calling party (char(10)) (part <VIRTLV2>-<x>-<x>)
admin M
Col-install flag M char(3) admin.col_install
000 = COL no
001 = COL yes
written during COL-inst
Table 6-65 CM Tables used for generating CDR output files (Fortsetzung)
A31003-H3460-M104-4-76A9, July 2012



A = Assistant)
Col-sync flag for cre- M char(3) admin.col_sync
ation of history records 000 = COL sync no
in CM 001 = COL sync yes
Package depenent
only with Package COL-C
Delete Delete M char(3) admin.gcu_install
char(3) admin.gcu_sync
Table 6-65 CM Tables used for generating CDR output files (Fortsetzung)
6.5.2 CM Elements Used for Transforming Virtual to Physical Node

Numbers
Basically, only the virtual node numbers are sent in the call charge data records (CDRs), as
only these are known network-wide. On the other hand, users can allocate a station/subscriber
only via the physical node number of the system. But since physical and the virtual node num-
ber must be different, an allocation of virtual node numbers from CDR data to a physical station/
subscriber is needed.
So, when a system is upgraded to HiPath 4000, this implies switching between virtual and phys-
ical node numbers. In order to provide HiPath Assistant/Manager or other evaluation applica-
tions with the possibility to continue using the physical node number, COL-CM output elements
have been introduced in HiPath 4000 Manager. The purpose of these output elements is to out-
put the physical node number in the output data records.
These COL-CM elements are automatically collected during run time from data of HiPath 4000
Manager Configuration Management (CM) (tables col_port and col_switch). The elements can
be found in the Output Format Editor under "CM Elements".
The CM elements for the virtual node number output are:
YCALLILV0-YCALLILV2 Physical node number of calling party

YPDESTLV0-YDESTLV2 Physical node number of destination number
YPPLV0-YPPLV2 Physical node number of cost bearer
YRTINGLV0-YRTINGLV2 Physical node number of transferring subscriber/station
YRTIONLV0-YRTIONLV2 Physical node number of forward destination
YTRNSFLV0-YTRNSFLV2 Physical node number of transferring subscriber/station (AC)
Table 6-66 CM Output Elements for physical node number transformation
Please use format PHYS_HP-COL_V1.0 if you want to transform the virtual node number to
the physical node number for the Hi-Path Assistant/Manager output line.
A31003-H3460-M104-4-76A9, July 2012

Attention:
> The usage of the CM elements slows down the data thruput in the col_line process
considerably due to the fact that for each element a SELECT query has to be exe-
cuted in the col_port and col_switch tables in order to ermitteln the physical node
number. This transformation also needs to be performed with the CDRs since the
call initiation may have occurred in a HiPath 4000 system with a virtual node number.
Please take this into consideration when using these elements in the output record.
A performance improvement is already being worked at for one of the next loads to
come.
See also
Loading the col_port and col_switch Tables
A31003-H3460-M104-4-76A9, July 2012


6.5.2.1 Loading the col_port and col_switch Tables

You can initialize/load the col_port table for every system individually by using the UPLOAD-
ALL command. For many systems this mechanism is not the optimum solution. A simpler so-
lution would be to load the col_port and col_switch tables from the port and switch
tables. You need to execute the following SQL sequence to perform this operation.
● Establish the connection with the HiPath 4000 Assistant/Manager.
● Enter .<blank>/opt/informix/ids_env_var (loading the Informix environment vari-
ables). <blank> is a placeholder representing a blank character.
● Start the SQL Command Interface with dbaccess cdb
● Select Query Language and confirm by pressing the Enter key.
● Select New and confirm.
● Updating the col_port table
Enter the following command:
insert into col_port
select * from port
where active="A"
and extension not in
( select extension from col_port where
switch_name=port.switch_name );
update col_port set issue="H",active="H",b_active="H" where ac-
tive="A";
● Updating the col_switch table
insert into col_switch
select * from switch
where active="A"
and switch_name not in
( select switch_name from col_switch where nodenum=switch.node-
num );
update col_switch set issue="H",active="H",b_active="H" where
active="A";
● The col_port and the col_switch tables are now populated with data.
Quit dbaccess by pressing the ESC key twice.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Nur für den internen Gebrauch Configuration Examples - Data Collection Using HiPath COL
7 Configuration Examples - Data Collection Using

HiPath COL
HiPath COL in the HiPath AM software package is the successor of the AM COL application
in AM Win 2.0. The main differences/improvements to AM COL are the web-based user inter-
face and the extended palette of supported system types:
● HiPath 4000,
● HiPath 4000 Assistant/Manager,
● HiPath 5000,
● OpenScape Voice,
● HiPath AllServe.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Configuration Examples - Data Collection Using HiPath COL Nur für den internen Gebrauch
Requirements
7.1 Requirements
The following software-components have to be installed for HiPath COL to operate:
● Operating systems: Windows 2003 server, Windows 2000 and Windows XP environment.
● Browser software: Microsoft Internet Explorer 5.5 SP2 or later.
● Microsoft Internet Information Services (IIS).
● HiPath 4000 Expert Access V5.0.79 or later.
● Java Runtime Environment JRE: 1.3.1_01.
● HiPath AM V1.0, V2.0
A detailed description of the installation and configuration of HiPath COL can be found in the
documents HiPathCOL-InstEng.pdf and Installation Overview.pdf in the directory \Manuals
on the HiPath AM Installation CD.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Requirements
7.1.1 Language of the User Interface

The HiPath COL user interface is available in German and English. To set or change the display
language of your web browser, select the corresponding settings in your browser - as described
below:
● Internet Explorer
Open the browser settings (Tools -> Internet Options). Open the Language Preferences
window by clicking the Languages button on the General page. The following languages
will be detected by HiPath COL:
– German (Germany) [de]
– English [en]
The language listed at the top position will be the display language of the HiPath COL user in-
terface.
The automatic detection of the language via the browser settings does only work if
> HiPath COL is started from the URL http://[PC address]/COL (and not with
http://[PC address]/COL/HomePage.html or .../HomePage_de.html). Take this
into account when creating a bookmark or a favorite link in the web browser.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Requirements
7.1.2 Cancel Background Processes (COLProcM Service)

Before you stop the background processes of HiPath COL by using the Control Panel (stop of
COLProcM service) or by shutting down the PC you need to make sure that no call data transfer
is in progress at that moment. If a transfer is active, this might result in losing call data.
You have to stop all input lines by using the Controlling function on the HiPath COL Home-
page (Stop Input button). Afterwards you need to check that no call data transfer is in progress
by using the Collecting Status feature (columns Transfer Status and Transform Status).
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000
7.2 HiPath 4000
Basic Scenario
● Each HiPath 4000 switch saves call detail records to its FT file.
● HiPath COL collects the call data from HiPath 4000 systems via File Transfer.
● The actual data transfer is performed by the HiPath 4000 Expert Access component.
● HiPath COL controls the process and time flow and decides which switches will be polled.
For the polling of the call charge data, the following steps are required:
Procedure
1. Configuration of call data output in HiPath 4000 systems, see Configuring HiPath 4000 Call
Data Output on page 7-6,
2. Configuration of HiPath 4000 for file transfer, see Configuring HiPath 4000 for File Transfer
on page 7-8,
3. Configuration of retrieved switches in HiPath COL, see HiPath 4000 – HiPath COL on page
7-9,
4. Configuration of retrieved switches in HiPath AM, see HiPath 4000 – HiPath AM on page
7-16.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000
7.2.1 Configuring HiPath 4000 Call Data Output
Configuring the selection tables for saving the call data into the FT file
Create the individual selection tables in the usual manner. With regard to the output format you
must specify an FTBL-defined format FORM01 - FORM16 rather than HDFORM as for CDRC
files:
Selection table batch file for HiPath 4000 V1.0:
ADD-SELG:SELG,1,N,FT,NODEV,1,0;
CHANGE-SELG:SELT,1,1,FORM04,NOFORM,TARGR01,A22;
CHANGE-SELG:SELT,1,1,,,,,0&&999999;
CHANGE-SELG:SELT,1,1,,,,,,VOICE&FAX&DTE;
CHANGE-SELG:SELT,1,1,,,,,,,0&&15;
CHANGE-SELG:SELT,1,1,,,,,,,,ALL,ALL,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N;
CHANGE-SELG:SELT,1,1,,,,,,,,,,,,,,,,,,,,,,,,,,,0,000000;
CHANGE-SELG:SELT,1,1,,,,,,,,,,,,,,,,,,,,,,,,,,,,,0&&999,0&&127,0&&15;
CHANGE-SELG:SELT,1,1,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,N,N,INTERN&IN-
CO&OUTG,0&&7,0&&9,ALL;
Activating call detail recording
ACT-SELS:1;
Configuring the device (FT)

Example:
ADD-DAGR:FT,65535,ASC,17-9,1,"FTFILE";
The call data is collected in a separate temporary file (:CGD:FT_INTERN_FILE) on the HDD
until the time configured in AMO DAGR. At this time the call data from this file is added to the
output file (e.g.:CGD:FTFILE).
To get the most current call data into HiPath COL/AM the time and period of gener-
> ating the FT file should be synchronized with the time and period of the transfer from
HiPath COL. It is recommended not to set the time of transfer in HiPath COL to a
value of less then 10 minutes after the time of generating the FT file.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000
By using the AMO command
K-DAGR;
you can force the system to generate the FT file manually.
Parallel Output of CDR Data on Multiple Output Devices in HiPath 4000 V1.0
Parallel output of CDR data onto multiple output devices (e.g. V24 and FT file) is only supported
if the CDRFAST parameter in the AMO FEACG is deactivated.
If CDRFAST is activated, only one selection group (SELG1) and thus only one output device is
activated; the other selection groups (2 through 4) are deactivated.
Parallel output of CDR data on multiple output devices (e.g. V24 and FT file) is only
> supported if the CDRFAST parameter in the AMO FEACG is deactivated.
In case of high load on the switch, deactivating the CDRFAST parameter may cause
performance problems.
CDRFAST optimizes the CDR data output and increases the output performance on the ADP.
This is achieved by deactivating the selection groups 2 through 4, thus reducing the output to
one selection group, i.e. one output device.
As a general rule, you should only deactivate CDRFAST if you need parallel output of CDR data
on multiple output devices.
If you only need the FT file as the target format for CDR data output (i.e. only one output device)
you should always activate CDRFAST in order to increase the output performance on the
switch.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000
7.2.2 Configuring HiPath 4000 for File Transfer

You'll find a detailed description on how to configure the file transfer parameters for HiPath
4000 switch in the HiPath 4000 Expert Access (ComWin 300) Online Help
(e.g. [ComWin installation directory]\Help\en\comwin_ft.htm).
Example:
ADD-CPTP:DPCON,1,"DVANCC01","139.1.20.43";
ADD-CPTP:APPL,1,"FAMOS","DVANCC01","DIPAS",YES,102,102,"DT-HIC","DT-DMS";
ADD-CPTP:APPL,2,"FILETRAN","DVANCC01","FT0",YES,102,102,"FT-HIC","$FJAM";
ADD-FTCSM:A1,NCF,1,"MXFCENT","DVANCC01","FT0","SINIX1",OTHER;
ADD-FTCSM:A1,FTTF,1,":DBD:FTA1",1,1,1;
ADD-FTCSM:A1,STATE,RUN;
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000
7.2.3 HiPath 4000 – HiPath COL

● HiPath 4000 – Setting Up Input Lines (Systems) (see page 7-10),
● HiPath 4000 – Setting Up Output Lines (see page 7-14).
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000
7.2.3.1 HiPath 4000 – Setting Up Input Lines (Systems)

In HiPath COL you need to set up an input line for each system you want to collect data from.
● To set up an input line, select the Definition of Input Lines feature on the HiPath COL
Homepage.
● To set up a new input line, select the New Object radio button or the Object -> New menu
item.
In the dialog displayed, enter the following data:
Communication Parameter tab sheet
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000
System ID This is the name of the HiPath 4000 system that is being polled by this
input line.
● The name length is limited to 4 characters. It is possible to type in
more characters into the field but only the first 4 characters are
stored to the database.
● For consistency reasons, the name of the input line should be the
same as in HiPath AM.
System Type For HiPath 4000 systems, select H300 here .
System Version Select the version of your system software here. The following version
is supported :
Software Version (System Version) see page 7-12
IP Address The IP address of the system.
Format : nnn.nnn.nnn.nnn (nnn : 0-255)
COL Administration tab sheet
Input Format Choose one of the predefined or one of your user-defined data record
formats. Please note that the format to be used depends on the ver-
sions of the connected HiPath 4000 systems (System Version). The
following format is predefined and should be used for HiPath 4000
systems:
Pre-defined Format (Input Format) see page 7-13
Activate Input Line This button is specifically used to start/stop the collecting of data for
this input line.
Generating Node In all predefined record formats the node number entered here (incl.
Number domain-subdomain-number) will be exported as Generating Node
Number in the fields GENLV0-GENLV2.
CDR Source For HiPath 4000 systems the File option is preselected here and must
never be changed.
File / Directory Name Type in the filename you have configured with the AMO DAGR as FT
output file. Preceding the filename, you have to add the partition name
of the HDD (:CGD:). As shown in the sample configuration in the pre-
ceding section, the filename is :CGD:FTFILE.
Number of Retries The default value is 3. This means that after a failed transfer HiPath
COL starts three further transfer retries to collect the call data from the
system. If all 3 retries fail a corresponding error message is added to
the "Receive Log" and the next transfer starts at the configured time.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000
Retry Time [min] 10 is the default value. This means that the waiting interval between
2 retries has a duration of 10 minutes.
Start Date / Start The current date and time is automatically entered here. Adjust the
Time values to your needs. To retrieve and load the current records from
the system, the date/time should be set to a value immediately after
the date/time value configured with the AMO DAGR in the HiPath
4000 system for copying of the output file. To be able to also obtain
the data under ADP load, the interval between the time values should
not be less than 10 minutes.
Cycle Use this field to enter the value for the input cycle. Possible values:
Min. 1 minute, max. 24 hours. Adjust the input cycle to match the copy
cycle of the system (see AMO DAGR).
Communication Parameter - Famos
User Name / Pass- Enter the user name and password of a FAMOS user ID that has has
word been granted the necessary access rights for renaming and deleting
files on the hard disk.
TSAP SRC/TSAP Enter here the TSAP specifications configured with the AMO CPTP
DST (TYPE= "FAMOS").
Communication Parameter - FTP / Open FT
User Name / Pass- Enter the corresponding data here (user name and password, AMO
word FTCSM).
TSAP SRC/TSAP Enter here the TSAP specifications configured with the AMO CPTP
DST (TYPE= "FILETRAN").
And... Don´t forget to save your data!
Software Version (System Version)
Value HiPath Version

UV1.0 HiPath 4000 V1.0
UV4 HiPath 4000 V4
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000

UV5 HiPath 4000 V5
UV6 HiPath 4000 V6
Pre-defined Format (Input Format)
HiPath 4000 Version Format

V1.0 AM_UV1.0_L
V2.0 AM_UV2.0_L
V3.0 AM_UV3.0_L
V4 AM_UV4_L
V5 AM_UV5_L
V6 AM_UV6_L
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000
7.2.3.2 HiPath 4000 – Setting Up Output Lines

To set up the output of records, you need to set up one output line (output file) per record for-
mat.
● To set up output lines, use the Definition of Output Lines feature from the HiPath COL
Homepage.
● To set up a new output line, select the New Object radio button or the Object Æ New menu
item.
In the dialog displayed you have to enter the following data:
Output Line Name Name of output line, e.g. H300GDS, max. 32 characters.
Description Arbitrary text. Max. 256 characters.
Active This toggle switch is specifically used to start/stop the output for this
output line. Please take into consideration that if the output is turned
off no records will be buffered (temporarily saved). Therefore, if you
intend to temporarily turn off the output without losing records, use
the Stop Output button of the Controlling feature on the HiPath
COL Homepage.
Output Format Choose one of the pre-defined or user defined record formats. The
chosen output format should match the input record format:
Pre-defined Format (Output Format), page 7-15
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000
Filter Choose the H300 filter here. This filter selects all data records col-
lected by input lines having the system type HDMS.
File Name Enter the output file name here (without specifying the path and/or
the drive), e.g. h4000gds. This output file will by default be created
in the [installation_directory]\data\deliver directory.
Time output time values to your needs. The output date/time should be set
to a value of at least 10 minutes before the collecting time of the Hi-
Path AM.
Cycle Use this field to enter the value for the output cycle. Possible values:
Min. 1 minute, max. 24 hours. Adjust the output cycle to match the
collecting cycle of the HiPath AM.
Pre-defined Format (Output Format)
Input Format Output Format

AM_UV1.0_L H300_HP-AM_1.0
AM_UV4_L H300_HP-AM_1.0
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000
7.2.4 HiPath 4000 – HiPath AM

When configuring the HiPath AM, two different scenarios have to be taken into consideration,
depending on whether data exchange with HiPath 4000 Manager is existing/planned or not.
● With HiPath 4000 Manager Exchange (see page 7-17),
● Without HiPath 4000 Manager Exchange (see page 7-29).
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000
7.2.4.1 With HiPath 4000 Manager Exchange

To establish a connection between HiPath AM and HiPath 4000 Manager the first step is to con-
figure a user for the AM in the HiPath 4000 Manager.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000
1. Assign access rights for the HiPath 4000 Manager user (hpam) to the API interface (XIE).
2. Configure a daily or monthly data exchange in the HiPath AM.
To configure a data exchange in the HiPath AM please go to

Maintenance --> Task Manager --> Import/Export.
Under Name you configure the name of the job (for example: ImportManagerMonthly).
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000
In the User Name field please enter the name of the configured user from the HiPath 4000
Manager (for example: hpam) and the corresponding Password.
In the Log File Path field you can create a folder for the log file by entering the path including
the folder name and the file name.
In the Address field you need to enter the IP Address of the HiPath 4000 Manager.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000
The Exchange Type parameter can be configured for Daily or Monthly synchronisation.
● Monthly = complete synchronisation;
● Daily = delta update of the Organisation and Personal Data.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000
Please continue by clicking the Next button, and then click on Save to store the configuration
changes.
For the initial Synchronization of the HiPath 4000 Manager and the HiPath AM you have to start
the new job once over by clicking on the Start Job Now icon. After the initial synchronization
the job can be started over via the Job Scheduler as scheduled job.
The next step is to configure a job for daily synchronization in the same way as before. The
Exchange Type is Daily.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000
This is done by using the Job Scheduler.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000
Defining a Task for CDR Data Collection Over FTP
To configure a CDR data collection over FTP please choose the Maintenance module. Go to
Task Manager and Data Collector. Under Data Source please choose a HiPath 4000 Man-
ager system.
Under Type & Parameters please choose DC FTP for data collection over FTP.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000
In the Path to Input File on FTP field please enter the path from the HiPath 4000 Manager
including the file name.
For the INI File Path field please select the Config.ini entry.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000
In the PD9 File Path field please select the defined output format for the data output from the
Collecting Agent (HiPath 4000 Manager).
Click the Next button.
Click the Save button.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000
Now you can start the new job manually by clicking on the Start Job Now icon or via the Job
Scheduler as scheduled job.
Click on the Job Scheduler icon.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000
7.2.4.2 Without HiPath 4000 Manager Exchange
Defining a Task for CDR Data collection over FTP
To configure a CDR data collection over FTP please choose the Maintenance module.
Go to Task Manager and Data Collector. Under Data Source please choose a HiPath 4000/
HiPath 4000 Manager system.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000
Under Type & Parameters please choose DC FTP for data collection over FTP.
In the Path to Input File on FTP field please enter the path from the HiPath 4000/HiPath 4000
Manager including the file name.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000
In the PD9 File Path field please select the defined output format for the data output from the
Collecting Agent (HiPath 4000 Manager).
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000 Manager Collecting Agent
7.3 HiPath 4000 Manager Collecting Agent
Basic Scenario
● Each HiPath 4000 switch stores calls detail records to its FT file.
● HiPath 4000 Manager Collecting Agent polls the call tickets from HiPath 4000 switches via
File Transfer and separates the call tickets to one file for AM (Accounting Management)
and another file for PM (Performance Management). A prerequisite for this data separation
is that HiPath PM-N or HiPath PM-E has to be installed on the network.
● HiPath COL transfers all call tickets as one compiled file collected by HiPath 4000 Manager
Collecting Agent from all single HiPath 4000 switches.
● HiPath AM takes over the subscriber (customer) data (exchange = external transfer) from
HiPath 4000 Manager.
In order to perform the polling of the calls tickets and to configure of the exchange interface for
the subscriber (customer) data, the following steps are required:
Procedure
1. Configuration of HiPath 4000 Manager Collecting Agent - Ausgabelinie (see Configuring
HiPath 4000 Manager Collecting Agent on page 7-35),
2. Setting up the systems (switches) to be polled in HiPath COL (see HiPath 4000 Manager
Collecting Agent – HiPath COL on page 7-37),
3. Setting up the systems (switches) to be polled in HiPath AM (see HiPath 4000 Manager
Collecting Agent – HiPath AM on page 7-43),
4. Setting up HiPath 4000 Manager Exchange for the subscriber data (see HiPath 4000 Man-
ager Exchange on page 7-48).
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.3.1 Configuring HiPath 4000 Manager Collecting Agent

HiPath 4000 Manager Collecting Agent stores the CDRs gathered from the switches in the net-
work into one single file. This file is periodically made available to HiPath COL in an output di-
rectory.
The procedure of setting up the input line side of HiPath 4000 Manager Collecting Agent is de-
scribed in the Definition of Input Lines section and is therefore not explained here.
Setting Up the Output Line

mat.
● To set up output lines, use the Definition of Output Lines feature from the Start Page of
HiPath 4000 Manager Collecting Agent.
item.
Output Line Name Name of output line, e.g. HPAM4000, max. 32 characters.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
intend to temporarily turn off the output without losing records, use the
Stop Output button of the Controlling feature on the HiPath COL
Homepage.
Pre-defined Format (Output Format) page 7-36
Filter Select the DefaultFilter setting here.
File Name Enter the filename GCDATA for the output file. The output file will by
default be created in the /var/col/data/deliver/ directory.
Path AM.
Min. 1 minute, max. 24 hours. Adjust the output cycle to match the col-
lecting cycle of the HiPath AM.

AM_V3.0_L HP-COL_V1.0
AM_UV1.0_L HP-COL_V1.0
AM_UV4_L HP-COL_V1.0
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.3.2 HiPath 4000 Manager Collecting Agent – HiPath COL

● HiPath 4000 Manager Collecting Agent – Setting Up Input Lines (Systems) (see page 7-
38),
● HiPath 4000 Manager Collecting Agent – Setting Up Output Lines (see page 7-41).
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.3.2.1 HiPath 4000 Manager Collecting Agent – Setting Up Input Lines (Systems)
In HiPath COL you need to set up an input line for the HiPath 4000 Manager Collecting Agent
that you want to collect data from.
● To set up an input line, select the Definition of Input Lines feature on the HiPath 4000
Manager Collecting Homepage.
item.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
System ID This is the name of the HiPath 4000 Manager Collecting Agents re-
trieved via this input line. The name length is limited to 4 characters.
It is possible to type in more characters into the field but only the first
4 characters are stored to the database.
System Type For HiPath 4000 Manager Collecting Agent select H4000M here.
System Version Select the version of your system software. The following versions are
supported:
Software Version (HiPath Version) page 7-40
IP Adresse The IP address of the HiPath 4000 Manager Collecting Agent.
Format: nnn.nnn.nnn.nnn (nnn : 0-255)
Input Format Choose one of the predefined or user-defined data record formats.
Please note that the format to be used depends on the versions of the
connected HiPath 4000 systems (System Version). The following for-
mat is predefined and can be used as default value for HiPath 4000
Manager Collecting Agent:
Pre-defined Format (Input Format) page 7-40
this input line.
Number domain-subdomain-number) will generally be exported as generating
node number in the fields GENLV0-GENLV2.
If collecting is done from HiPath 4000 Manager Collecting Agent the
Generating Node Number is irrelevant since it is already included per
CDR in the format from HiPath 4000 Collecting Agent.
Enter for instance
00-000-000 as a dummy value here.
CDR Source For HiPath 4000 Manager Collecting Agent the File option is prese-
lected and must never be changed.
File/Directory Name Enter the filename that is already pre-defined or set with the output
line in HiPath 4000 Manager Collecting Agent. By default this is
/var/col/data/deliver/GCDATA.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Time values to your needs. The time should be set to a point when the GC-
DATA collection file has already been created by the HiPath 4000
Manager Collecting Agent and is ready to be retrieved. The time inter-
val should be of at least 10 minutes after the creation of the GCDATA
file.
Min. 1 minute, max. 24 hours. Adjust the input cycle to match the cre-
ation (output) cycle of the GCDATA file in HiPath 4000 Manager Col-
lecting Agent.
User Name/Pass- Enter the user name and password for accessing the XIE API
word ID here (e.g. hpam/hpam).
Before you can enter this user name and password here, you
need to create the account in HiPath 4000 Manager and grant
it the necessary access rights for XIE API functionality.
Software Version (HiPath Version)

MV1.0 HiPath 4000 Manager Collecting Agent V1.0
MV2.0 HiPath 4000 Manager Collecting Agent V2.0

V1.0 H4000_V1.0_L
V2.0 H4000_V2.0_L
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.3.2.2 HiPath 4000 Manager Collecting Agent – Setting Up Output Lines

mat.
● To set up output lines, use the Definition of Output Lines feature from the HiPath 4000
Manager Collecting Agent Homepage.
item.
Homepage.
Filter Choose the H300 filter here. This filter selects all data records collect-
ed by input lines having the system type HDMS.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
File Name Enter the output file name here (without specifying the path and/or the
drive), e.g. h4000gds. This output file will by default be created in the
[installation_directory]\data\deliver directory.
Path AM.

AM_V3.0_L H300_HP-AM_1.0
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.3.3 HiPath 4000 Manager Collecting Agent – HiPath AM

This configuration is always based on the assumption that HiPath 4000 Manager Collecting
Agent collects the call tickets of all HiPath 4000 switches in the network and makes them avail-
able to HiPath COL/HiPath AM.
The external exchange of HiPath AM to the subscriber data in HiPath 4000 Manager is always
enabled.
Procedure
In order to transfer the collected calls data from HiPath COL to HiPath AM 2.0, you have to con-
vert - per output line – one (and only one – not several, not all) switch imported from HiPath
4000 Manager to a HiPathAM task.
To configure a CDR data collection from file, please choose the Maintenance module. Go to
Task Manager and Data Collector. Under Data Source please choose a switch, a system
which is responsible for the file.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Under Type & Parameters please choose DC File for CDR data collection from file.
In the Input File field please enter the path including the CDR file name.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
PD9 File Path: Select the file path for the defined “Output format” from the HiPath system (FT-
BL).
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.3.4 HiPath 4000 Manager Exchange

The Import/Export Interface - Import/Export API (XIE) - is used to take over the customer data
(organizational structure, personal data, PIN and switch-specific data) from HiPath 4000 Man-
ager - Configuration Management.
In addition, HiPath COL also needs the XIE privilege to retrieve connection data (see Special
Items with HiPath 4000 Manager – XIE Interface on page 7-51).
To be able to operate this interface appropriately, an account having the necessary privileges
for the required data needs to be set up.
● Creating a Login in HiPath 4000 Manager for HiPath AM (Customer Data) and HiPath COL
(Call Data) (see page 7-49),
● HiPath 4000 Manager Collecting Agent – Activate Access Rights for the XIE Interface (see
page 7-50),
● Special Items with HiPath 4000 Manager – XIE Interface (see page 7-51).
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath COL (Call Data)
Create a new user account using the Access Management application:
● Menu item: Account Management - User Account Administration
● Select the User - Add menu to create the hpam user account. In the Actions area, enter
hpam as the new password into the New Password field.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.3.4.2 HiPath 4000 Manager Collecting Agent – Activate Access Rights for the XIE
Interface
In order to add the XIE rights for the user account created, you need to select All access rights
of "Import/Export API (XIE)" in the Access Right Configuration and allocate these access
rights to user hpam.
This allocation creates a new direcory /home/hpam/iefiles. The external exchange with HiPath
AM for customer data (XIE data) is managed via this directory.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.3.4.3 Special Items with HiPath 4000 Manager – XIE Interface

● File Transfer (FTP) Access for HiPath COL Call Data Exchange
The XIE user account is required for HiPath AM to receive the call data file from HiPath
4000 Manager Collecting Agent. You can use the same login as for the external exchange
for customer data.
● Automatic Creation of Response Files
Like in the previous version of XIE, the request files (xxx.req), that are located in the ex-
change directory <iefiles>, are read by the system after a configurable amount of time. The
corresponding response files (xxx.rsp) are generated by the system and copied to the
same directory, e.g. here for HiPath AM retrieval.
This period is set by default to 15 minutes in HiPath 4000 Manager due to performance
reasons. You can change this value, but this would lead to a significant performance loss
within the HiPath 4000 Manager system.
● Supported Hierarchy Levels
HiPath 4000 Assistant/Manager supports 6 hierarchy levels: org1 through org6.
HiPath AM is configured for the hierarchy levels "Country", "Company", "org1-org3". This
implies that only the hierarchy levels org1-org3 are exchanged via the XIE interface.
Consequence:
In HiPath 4000 Manager – Configuration Management - please fill in only the levels
> org1-org3 for HiPath AM.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000 Assistant Collecting Agent
7.4 HiPath 4000 Assistant Collecting Agent
Basic Scenario
● HiPath 4000 stores the call detail records to its FT file.

● HiPath 4000 Assistant COL polls the call tickets from HiPath 4000 system and separates
the call tickets to one file for AM (Accounting Management) and another file for PM (Per-
formance Management).
● HiPath COL then retrieves only the AM file from Assistant COL.
In order to perform the polling of the call tickets (call charge data), the following steps are re-
quired:
Procedure
1. Configuration of HiPath 4000 Assistant Collecting Agent - Output Line (see Configuration
of HiPath 4000 Assistant Collecting Agent on page 7-53),
2. Configuration of the switches to be retrieved in HiPath COL (see HiPath 4000 Assistant
Collecting Agent – HiPath COL on page 7-56),
3. Configuration of the switches to be retrieved in HiPath AM (see HiPath 4000 Assistant Col-
lecting Agent – HiPath AM on page 7-63),
4. Configuration of HiPath 4000 Assistant Exchange for Customer Data (see HiPath 4000 As-
sistant Exchange on page 7-68).
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.4.1 Configuration of HiPath 4000 Assistant Collecting Agent

HiPath 4000 Assistant Collecting Agent stores the CDRs gathered from the HiPath 4000 sys-
tem into one single file. This file is periodically made available to HiPath COL in an output di-
rectory.
The procedure of setting up the input line side of HiPath 4000 Assistant Collecting
> Agent is described in the Collecting Agent documentation, and is therefore not ex-
plained here.
HiPath 4000 Assistant Collecting Agent – Setting Up Output Lines on page 7-54
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.4.1.1 HiPath 4000 Assistant Collecting Agent – Setting Up Output Lines

mat.
Assistant Collecting Agent -> Homepage.
item.
Homepage.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Filter Select DefaultFilter here.

Path AM.

AM_U3.0_L HP-COL_V1.0
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.4.2 HiPath 4000 Assistant Collecting Agent – HiPath COL

● HiPath 4000 Assistant Collecting Agent – Setting Up Input Lines (Systems) (see page 7-
57),
● HiPath 4000 Assistant Collecting Agent – Setting Up Output Lines (see page 7-61).
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.4.2.1 HiPath 4000 Assistant Collecting Agent – Setting Up Input Lines (Systems)
In HiPath COL you need to set up an input line for the system that you want to collect data from.
Homepage.
item.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
System ID This is the name of the HiPath 4000 system that is collected by this
input line.
System Type For HiPath 4000 Assistant systems, enter H300 here .
System Version Select the version of your system software here.
The following version is supported:
Software Version (System Version) page 7-59
IP Address This is the IP Address of the system. Format: nnn.nnn.nnn.nnn
(nnn: 0-255)
Input Format Choose one of the predefined or one of your user-defined record for-
mats. Note that the used format depends on the version of the HiPath
system (System Version). The following format is predefined and
should be used for HiPath 4000 systems:
Pre-defined Format (Input Format) page 7-60
Activate Input Line With this check box you can specifically activate or deactivate the call
data collection for this input line.
Generating Node In all predefined output formats this node number (incl. domain-sub-
Number domain-number) will generally be exported as Generating Node
Number in the fields GENLV0-GENLV2.
If collecting is done from HiPath 4000 Assistant Collecting Agent, the
Generating Node Number is irrelevant since it is already included per
CDR in the format provided from HiPath 4000 Assistant Collecting
Agent. Enter for instance 00-000-000 as a dummy value here.
CDR Source For HiPath 4000 Assistant Collecting Agent the File option is prese-
lected and must never be changed.
File / Directory Name Enter the filename preselected or preset at the output line in HiPath
4000 Assistant Collecting Agent. The preset path/filename is /var/col/
data/deliver/GCDATA, see page 7-54.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Time values to your needs. The time should be set to a point when the GC-
DATA collection file has already been created by the HiPath 4000
Manager Collecting Agent and is ready to be retrieved. The time inter-
val should be of at least 10 minutes after the creation of the GCDATA
file.
ation (output) cycle of the GCDATA file in HiPath 4000 Manager Col-
lecting Agent.
Communication Parameter – FTP / Open FT
User Name / Pass- Enter the appropriate account data (user name and password) for ac-
word cessing the XIE API account (e.g. hpam/hpam) here.
This is the user account name and password you previously created
in HiPath 4000 Assistant and activated for the XIE API features (see
page 7-68).
Software Version (System Version)
Value System Version

UV4 HiPath 4000 V4
UV5 HiPath 4000 V5
UV6 HiPath 4000 V6
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000 Version Format

V1.0 AM_UM1.0_L
V2.0 AM_UM2.0_L
V3.0 AM_UM3.0_L
V4 AM_UM4_L
V5 AM_UM5_L
V6 AM_UM6_L
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm

mat.
Assistant -> Collecting Agent -> Homepage.
● To set up a new output line, select the New Object radio button or the Object -> New menu
item.
Homepage.
Filter Choose the H300 filter here. This filter selects all data records collect-
ed by input lines having the system type HDMS.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
drive), e.g. h4000gds. This output file will by default be created in the
Path AM.

AM_V3.0_L H300_HP-AM_1.0
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.4.3 HiPath 4000 Assistant Collecting Agent – HiPath AM
Procedure
Step by Step: Configuring Polled Switch(es)

Per output line of HiPath COL, a so-called "polled switch“ has to be configured. The call tickets
of this output line are imported by this switch. For this reason, the call record format and the
retrieval time are adjusted to match the output line.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
BL).
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.4.4 HiPath 4000 Assistant Exchange

(organizational structure, personal data, PIN and switch-specific data) from HiPath 4000 Assis-
tant - Configuration Management.
In addition, HiPath COL also needs the XIE privilege in order to retrieve connection data (see
Special Items with HiPath 4000 Assistant – XIE Interface on page 7-71).
● Creating a Login in HiPath 4000 Assistant for HiPath AM (Customer Data) and HiPath COL
● HiPath 4000 Assistant Collecting Agent – Activate Access Rights for the XIE Interface (see
page 7-70),
● Special Items with HiPath 4000 Assistant – XIE Interface (see page 7-71).
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.4.4.1 Creating a Login in HiPath 4000 Assistant for HiPath AM (Customer Data)
and HiPath COL (Call Data)
Menu item: Account Management - User Account Administration
Select the User -> Add menu to create the hpam user account. In the Actions area, enter
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.4.4.2 HiPath 4000 Assistant Collecting Agent – Activate Access Rights for the XIE
Interface
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.4.4.3 Special Items with HiPath 4000 Assistant – XIE Interface

4000 Assistant Collecting Agent. You can use the same login as for the external exchange
for customer data.
This period is set by default to 15 minutes in HiPath 4000 Assistant due to performance
within the HiPath 4000 Assistant system.
Consequence:
In HiPath 4000 Assistant – Configuration Management - please fill in only the levels
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 5000 (HiPath 5300, HiPath 5500)
7.5 HiPath 5000 (HiPath 5300, HiPath 5500)
Basic Scenario
● HiPath 5000 stores the call detail records to a file.

● Call detail records are actively retrieved by HiPath COL, connected to the HiPath 5000 sys-
tems. This is achieved via an FTP connection to the HiPath 5000 server on which you in-
stalled an FTP server (HiPath COL working as FTP client).
● HiPath COL fetches the provided call files and deletes them on the HiPath 5000 server af-
ter processing.
The HiPath AM configuration requires an FTP server to be already installed on

> the HiPath 5000 system. This FTP server is not provided by HiPath AM.
As an alternative, you can use the "SlimFTP“ server located on the HiPath AM CD
in the ../Addons directory.
Procedure
1. Configuring the call charge data output on the HiPath AllServe system - see Configuration
of HiPath 5000 on page 7-73.
2. Setting up the systems to be retrieved in HiPath COL - see HiPath 5000 – HiPath COL on
page 7-76.
3. Setting up the systems to be retrieved in HiPath AM - see HiPath 5000 - HiPath AM on
page 7-82.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.5.1 Configuration of HiPath 5000
Setting Up the Call Data Output in HiPath 5300/5500 Management

The Central Call Charge Registration (CDRC) in HiPath 5000 needs to be activated, and the
path for supplying the file has to be set. To configure these settings, select Feature Server
Configuration – Services – CDR in the HiPath 5300/5500 Management menu tree.
The following images show the correct parameter settings.
Setting Up the Filter

● Select CDR Report Filtering Option in the menu tree.
● Activate all check boxes (Outbound, Inbound, Internal, and Abandoned).
Setting Up the Output Path

● Select the CDR Configuration feature in the menu tree.
● Click on the OUTPUT-LOCATION entry in the list to configure the path for supplying the
files for HiPath COL. This path needs to be addressed in COL as well, in order to guarran-
tee the CDR transfer to HiPath AM.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
● Set the path to the desired value in the Modifying CDR Config dialog. In the example be-
low the path is set to D:\cdrdata\output. HiPath COL will fetch the output file(s) from this
location and read in the CDR data from the filel(s).
Setting Up the Output Schedule

● Select the CDR Scheduler in the menu tree.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
● In the Output Mode field, select the <Periodicity> entry.

● Set the output type to Day= <Daily>
● Set the output time Output Time to a time value of your choice, e.g.
– Hour = 03,
– Minute = 30,
– Second = 00.
This output time is the reference base for the time value that needs to be set in HiPath COL for
fetching the CDR file. In this example, a time value of 04:00 makes sense, since this is half an
hour after the schedule output in the HiPath 5000 system.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.5.2 HiPath 5000 – HiPath COL

● HiPath 5000 – Setting Up Input Lines (Systems) (see page 7-77).
● HiPath 5000 - Setting Up Output Lines (see page 7-80).
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.5.2.1 HiPath 5000 – Setting Up Input Lines (Systems)
Setting Up the Input Line

● Open the Definition Of Input Lines feature from the HiPath COL Homepage.
● To add a new input line select the New Object radio button or the Object Æ New menu
item.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
System ID This is the name of the system collected by this input line.
System Type Select H5000 for the configuration here.
System Version You can only select HV3.0 here.
IP Address Enter the IP address of the HiPath 5000 server PC here.
Format : nnn.nnn.nnn.nnn (nnn : 0-255)
Input Format Select the H5000_V3.0 format here.

this input line.
Number domain-subdomain-number) will be exported as generating node
number in the fields GENLV0-GENLV2 and added to every record.
This node number is needed by HiPath AM to allocate the call num-
bers from the data records to the correct subscribers in the HiPath AM
database or to correctly create the subscriber data, respectively.
Since HiPath 5000 systems do not recognize node numbers, an arbi-
trary node number can be selected here. However, this node number
has to be unique in HiPath AM.
CDR Source For H5000 lines, directory is preselected by default here.
File / Directory Name Enter a slash here (/), followed by a directory of your choice.
Time values to your needs. To provide the current records of the system,
the output time should be adjusted to match the output period of the
HiPath 5000 system.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
ation (output) cycle of the HiPath 5000 system.
User Name / Pass- Enter the user name and password that you set up on the FTP server
word of the HiPath 5000 system.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.5.2.2 HiPath 5000 - Setting Up Output Lines

In order to output the call charge data imported via the H5000 line, you need to set up an output
line (output file).
Output Line Name Name of the output line, e.g. H5000GDS, max. 32 characters.
Homepage.
Output Format Select the H5000_HP-AM_1.0 output format here.
Filter Select the pre-defined H5000 filter here.
drive), e.g. h5000gds.txt. This output file will by default be created in
the [installation_directory]\data\deliver directory.
Path AM.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
● Close the dialog by clicking the OK button.
● And... Don´t forget to save your data!
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.5.3 HiPath 5000 - HiPath AM
Procedure
Configure the HiPath server that is to be polled via HiPath COL as a task for "Collect from File"
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
BL).
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath OpenScape Voice with IPSec
7.6 HiPath OpenScape Voice with IPSec

This section contains a description for the feature "Collect CDR from OpenScape Voice with
IPSec".
According to this feature an interconnection between HiPath COL and OpenScape Voice has
to be established. By creating an appropriate input line for OpenScape Voice switch, the CDR
collection is achieved from the OpenScape Voice systems. The CDR file is an ASCII file where
elements are separated by commas. Delimiter is a configurable file that contains all available
CDR elements.
7.6.1 Administration Steps for OpenScape Voice using HiPath COL

For the collection of data records (CDR) from a OpenScape Voice system, special configuration
is neccesary in the HiPath COL application. The next two sections describe the required ad-
ministration steps for CDR collection.
● OpenScape Voice Collecting Agent - Setting up Input Lines (systems)
● OpenScape Voice Collecting Agent - Setting up Output Lines
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.6.1.1 OpenScape Voice Collecting Agent - Setting up Input Lines (systems)

To set up an Input Line in HiPath COL, select Definition of Input Lines feature on OpenScape
Voice home page. Then select New Object radio button and enter the following data in the dis-
played dialog.
The table below describes the required fields for the Input Line Definition:
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
System ID This is the name of the OpenScape Voice Manager Col-

lecting Agents retrieved via this input line. The name
length is limited to 4 characters. It is possible to type in
more characters into the field but only the first 4 charac-
ters are stored to the database
System Type For OpenScape Voice Collecting Agent select H8000
here
System Version Select the version of your system software. The follow-
ing version is supported for OpenScape Voice: H8_01
IP Address The IP address of the OpenScape Voice Collecting
Agent
COL Administration tab sheet:
Input Format Choose one of the predefined or user defined data

record formats. Please note that the format to be used
depends on the versions of the connected OpenScape
Voice systems (System Version). The following format
can be used: H8000_V01
CDR Source: File/Directory Name Enter the filename that is already pre-defined or set with
the output line in OpenScape Voice. By default this is: /
cdr
Communication Parameter – FTP / Open FT:
Secure FTP: User Name / Pass- Enter the user name and password for accessing the
word OpenScape Voice system
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.6.1.2 OpenScape Voice Collecting Agent - Setting up Output Lines

To set up an output line in HiPath COL, select Definition of Ouput Lines feature on Open-
Scape Voice home page. Then select New Object radio button and enter the following data in
the displayed dialig:
The table below describes the required fields for the Output Line Definition:
Active This toggle switch is specifically used to start/stop the output for this output line.
If the output is turned off no records will be buffered (temporarily saved). There-
fore, to temporarily turn off the output without losing records, use the Stop Out-
put button of the Controlling feature on the HiPath COL Homepage
Output Choose one of the pre-defined or user defined record formats. The chosen out-
Format put format should match the input record format: H8000_AM
Filter Choose the H8000 filter here. This filter selects all data records collected by in-
put lines having the system type H8000
File Name Enter the output file name here (without specifying the path and/or the drive),
e.g. h8000gds. This output file will by default be created in the
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Restrictions
7.6.2 Configuration on the OpenScape Voice system

It is important to configure the shell commands that are given to the OpenScape Voice in order
to permit the application server of HiPath COL to make a connection with OpenScape Voice
and retrieve the CDRs.
Moreover a user is needed that have root privileges in order to be able not only to retrieve the
files but also to remove them after retrieval. The following lines describe the configuration com-
mands given to the OpenScape Voice system:
Configuration Example:
10.0.250.186
SSH Secure Shell 3.2.9 (Build 283)

Copyright (c) 2000-2003 SSH Communications Security Corp - http://www.ssh.com/
This copy of SSH Secure Shell is a non-commercial version.

This version does not include PKI and PKCS #11 functionality.
Last login: Fri Apr 22 11:39:39 2005 from inmc_smc_11.h8k.dip

SISDev:~ # ssh 10.0.32.10
root@10.0.32.10's password:
Last login: Mon Mar 1 11:04:58 1993
HI
grd03a:~ # cd /usr/local/bin
grd03a:/usr/local/bin # ls
. dbiproxy gdbserver ora_explain perl5 removeTrustedHost
.. gdb gdbtui perl permitTrustedHost showTrustedHost
grd03a:/usr/local/bin # ./permitTrustedHost 141.29.39.221
grd03a:/usr/local/bin #
7.7 Restrictions
● HiPath AM V2.0 / V1.0 and HiPath COL V2.0 must be installed on the same PC.
● Secure FTP connection for OpenScape Voice system is necessary, in order to collect CDR
files after the interconnection with the HiPath COL application.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath AllServe (HiPath AllServe 150 V1.0)
7.8 HiPath AllServe (HiPath AllServe 150 V1.0)

Configuration: Installation of HiPath AM/COL on a Separate System (PC)
Configuration: Installation of HiPath AM/COL on the HiPath AllServe Server
Configuring the HiPath AllServe System
HiPath AllServe - HiPath COL
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.8.1 Configuration: Installation of HiPath AM/COL on a Separate

System (PC)
The HiPath AllServe system saves the call data to a file.

Connecting to HiPath AllServe systems, the call data is actively collected by HiPath COL. This
is done using an FTP connection to the HiPath AllServe server on which an FTP server has
been installed (where HiPath COL is the FTP client). HiPath COL collects the call charge data
provided and deletes the data after processing it on the HiPath AllServe server.
The HiPath AM configuration is based on the assumption that an FTP server has already
been installed on the HiPath AllServe system. The FTP server is not provided by HiPath
AM.
As an alternative, you can use the "SlimFTP“ server from the HiPath AM CD, "Addons“ direc-
tory.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.8.2 Configuration: Installation of HiPath AM/COL on the HiPath

AllServe Server
In this configuration, HiPath AM/COL is installed on the HiPath AllServe server.

The HiPath AllServe system saves the call data to a file.
Connecting to HiPath AllServe systems, the call data is actively collected by HiPath COL. Hi-
Path COL collects the call charge data provided from the local file system and deletes the data
after processing it.
No FTP server is needed when using this configuration.
Procedure
1. Configuring the call charge data output on the HiPath AllServe system - see Configuring
the HiPath AllServe System on page 7-94
2. Setting up the systems to be retrieved in HiPath COL - see HiPath AllServe - HiPath COL
on page 7-97
3. Setting up the systems to be retrieved in HiPath AM - see HiPath AllServe - HiPath AM on
page 7-106
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.8.3 Configuring the HiPath AllServe System

Setting Up the Call Charge Data Output in HiPath AllServe 150 V1.0 on page 7-95
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.8.3.1 Setting Up the Call Charge Data Output in HiPath AllServe 150 V1.0
You need to activate the Charge Collection Central (Gebührenerfassung-Zentral) in the HiPath
AllServe 150 V1.0, and to set the path for providing the file. To configure these settings in Hi-
Path AllServe 150 V1.0, go to the Start menu and select HiPath AllServe 150 Administration
- Call Charge Evaluation (Gesprächskostenauswertung) - Properties from the menu tree.
The images below show the required parameter settings.
Starting the Application
Configuring the Call Charge Data Output

Select the properties of the Call Charge Evaluation (Gesprächskostenauswertung) using
the Right Mouse Key.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Use the External Call Data Transfer (Externe Gesprächsdatenweitergabe) tab sheet to
configure the call charge data output.
This tab sheet is used to configure the Mode (Modus), the Transfer File Name (Transfer-
datei-Name), and the Transfer File Folder (Ordner der Transferdatei). The Transfer File
Folder is selected via the Browse button.
Data is written to the call charge data file immediately when generating call charge data. There-
fore, it is not necessary to set and administer a time value for the output.
For further details about the configuration settings, please refer to the HiPath AllServe 150 V1.0
documentation.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.8.4 HiPath AllServe - HiPath COL

Setting Up Input Lines (Systems) for Collecting HiPath AllServe Data via FTP on page 7-98
Setting Up Input Lines (Systems) for Collecting HiPath AllServe Data via Local File System on
page 7-101
HiPath AllServe - Setting Up Output Lines on page 7-104
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.8.4.1 Setting Up Input Lines (Systems) for Collecting HiPath AllServe Data via FTP
Homepage.
item.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
System Type Select ALLSERVE for the configuration here.
The following versions are supported:
System Version page 7-100
IP Address Since the data is retrieved from the local system, it is not necessary
to enter an IP address here.
Input Format Select the AllServe format here.

this input line.
Since HiPath AllServe systems do not recognize node numbers, an
arbitrary node number can be selected here. However, this node num-
ber has to be unique in HiPath AM.
CDR Source For HiPath AllServe lines, File is preselected by default here.
File / Directory Name Enter a filename of your choice here. The default filename is
GCALLSERV.
Time values to your needs.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Min. 1 minute, max. 24 hours.
User Name / Pass- Enter the user name and password that you set up on the FTP server
word of the HiPath AllServe system (see page 7-95).
System Version

AV1.0 HiPath AllServe 150 V1.0
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.8.4.2 Setting Up Input Lines (Systems) for Collecting HiPath AllServe Data via
Local File System
Homepage.
item.
System Type Select ALLSERVE for the configuration here.
The following versions are supported:
System Version page 7-103
IP Address Since the data is collected from the local file system, no IP address
has to be entered here.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Input Format Select the AllServe format here.

this input line.
Since HiPath AllServe systems do not recognize node numbers, an
arbitrary node number can be selected here. However, this node num-
ber has to be unique in HiPath AM.
CDR Source For HiPath AllServe lines, File is preselected by default here.
File / Directory Name Enter a filename of your choice here. The default filename is
GCALLSERV.
CDR From Local File The ALLSERVE system type can also be used for collecting call
System charge data from the local file system. If this check box is enabled, the
input files containing the call data record sets (CDRs) will be saved to
a backup directory under the path ..\var\COL\data.
When activating this feature, all collected input data is saved in the /
var/col/data/backup/<System-ID>/<cdr_filename> directory. At
present the Collecting Agent / HiPath COL does not support a feature
for deleting the data in the /var/col/data/backup directory. Therefore,
the user who activated this feature is responsible for the administra-
tion/deletion of the backup data. This feature is used to read in and
thus recover from the backup directory CDR data that has been lost
In order to read in the CDR records, the required CDR files can be
copied to the /var/col/data/error/<System-ID> directory. The data
records are then read in via the Incorrect Records dialog by select-
ing the file and pressing the Send Back to Input button.
Therefore, you should regularly delete this data in order to avoid ex-
ceeding the storage capacity of the /var partition.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Time values to your needs.
Min. 1 minute, max. 24 hours.
User Name / Pass- No entry is necessary in these fields for this configuration.
word
System Version

AV1.0 HiPath AllServe 150 V1.0
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.8.4.3 HiPath AllServe - Setting Up Output Lines

In order to output the call charge data imported via the ALLSERVE line you need to set up an
output line (output file).
Output Line Name Name of the output line, e.g. H150GDS, max. 32 characters.
Homepage.
Output Format Select the H150_HP-AM_1.0 output format here.
Filter Select the pre-defined H150 filter here.
drive), e.g. allserve.txt. This output file will by default be created in
the [installation_directory]\data\deliver directory.
Path AM.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
● Close the dialog by clicking the OK button.
● And... Don´t forget to save your data!
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.8.5 HiPath AllServe - HiPath AM
Procedure
Configure the HiPath AllServe server that is to be polled via HiPath COL as file transfer switch.
> Collection
HiPath AllServe needs to be configured as Voice type in the
Type dialog, like all other systems described here.
Step by Step
Per output line of HiPath COL, a task has to be configured in HiPath AM. The call data records
(call tickets) of this output line are imported by this switch. The call record format and the re-
trieval time are adjusted to the output line for this purpose.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Under Type & Parameters please choose DC File for data collection from file.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
BL).
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Incorrect Records
7.9 Incorrect Records

If a call detail records file (FTFILE) contains an incorrect record, then HiPath COL stores the
complete file as follows:
● Directory:
...\HiPathCOL\data\error\[Input_Line] (Input_Line = 1,2,3 ...)
● Filename:
cdr_yyyymmdd_hhnnss.err
You can edit/correct the incorrect record(s) in this file using a text editor (e.g. Notepad). After-
wards the rejected file can be sent back to the input using the Send Back To Input button on
the Incorrect Records dialog (HiPath COL Homepage) (see Incorrect Records - Send Back
To Input).
If the file content is still incorrect the file will be stored in the error directory again, but this time
with a different file name containing the current date and time.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath AM FTP Collecting
7.10 HiPath AM FTP Collecting

Call Collecting from HiPath 4000 Manager/Assistant without HiPath COL
Configuring HiPath 4000 Manager Collecting Agent
HiPath 4000 Manager Collecting Agent - HiPath AM
HiPath 4000 Manager Collecting Agent – HiPath 4000 Manager Exchange
Configuration of HiPath 4000 Assistant Collecting Agent
HiPath 4000 Assistant Collecting Agent – HiPath AM
HiPath 4000 Assistant Collecting Agent – HiPath 4000 Assistant Exchange
HiPath 4000 Assistant Collecting Agent – Activate Access Rights for the XIE Interface
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.11 Call Collecting from HiPath 4000 Manager/Assistant without

HiPath COL
This description completes the HiPath AM V1.0 configuration for call collecting and personal
data exchange with HiPath 4000 Manager/Assistant by FTP direct access (without HiPath
COL).
Two separate scenarios are shown:
● Connecting HiPath AM to HiPath 4000 Manager (network)
and, respectively,
● HiPath 4000 Assistant (single site), where installation of HiPath COL is dropped.
This leads to shortened installation figures and increases the data transfer security (one com-
ponent less). You should vote for these scenarios if you attach HiPath 4000 single switches or
homogeneous HiPath 4000 network domains to HiPath AM. Please refer to the service manual
of HiPath AM for detailed settings.
Configuring HiPath 4000 Manager Collecting Agent
HiPath 4000 Manager Collecting Agent - HiPath AM
HiPath 4000 Manager Collecting Agent – HiPath 4000 Manager Exchange
Configuration of HiPath 4000 Assistant Collecting Agent
HiPath 4000 Assistant Collecting Agent – HiPath AM
HiPath 4000 Assistant Collecting Agent – HiPath 4000 Assistant Exchange
HiPath 4000 Assistant Collecting Agent – Activate Access Rights for the XIE Interface
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.11.1 HiPath 4000 Manager Collecting Agent
Scenario
● Each HiPath 4000 switch stores calls detail records to its FT file.
● HiPath 4000 Manager Collecting Agent polls the call tickets from HiPath 4000 switches via
File Transfer and separates the call tickets to one file for AM (Accounting Management)
and another file for PM (Performance Management). A prerequisite for this data separation
is that HiPath PM-N or HiPath PM-E has to be installed on the network.
● HiPath AM transfers all call tickets as one compiled file collected by HiPath 4000 Manager
Collecting Agent from all single HiPath 4000 switches.
● HiPath AM takes over the subscriber (customer) data (exchange = external transfer) from
HiPath 4000 Manager.
In order to perform the polling of the calls tickets and to configure the exchange interface for
the subscriber (customer) data, the following steps are required:
Procedure
1. Configuration of HiPath 4000 Manager Collecting Agent - Output (see Section Configuring
HiPath 4000 Manager Collecting Agent).
2. Setting up the systems (switches) to be polled in HiPath AM (see Section HiPath 4000
Manager Collecting Agent - HiPath AM).
3. Setting up HiPath 4000 Manager Exchange for the subscriber data. (see Section HiPath
4000 Manager Collecting Agent – HiPath 4000 Manager Exchange).
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.11.2 Configuring HiPath 4000 Manager Collecting Agent

HiPath 4000 Manager Collecting Agent stores the CDRs gathered from the switches in the net-
work into one single file. This file is periodically made available to HiPath COL in an output di-
rectory.
The procedure of setting up the input line side of HiPath 4000 Manager Collecting Agent is de-
scribed in the Definition of Input Lines section and is therefore not explained here.
Setting Up the Output Line

mat.
● To set up output lines, use the Definition of Output Lines feature from the Start Page of
HiPath 4000 Manager Collecting Agent.
item.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Homepage.
Filter Select the DefaultFilter setting here.
Path AM.

A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.11.3 HiPath 4000 Manager Collecting Agent - HiPath AM

This configuration is always based on the assumption that HiPath 4000 Manager Collecting
Agent collects the call tickets of all HiPath 4000 switches in the network and makes them avail-
able to HiPath COL/AM.
The external exchange of HiPath AM to the subscriber data in HiPath 4000 Manager is always
enabled.
Procedure
In order to transfer the collected calls data from HiPath COL to HiPath AM 2.0, you have to con-
vert - per output line – one (and only one – not several, not all) switch imported from HiPath
4000 Manager to a HiPathAM task.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
BL).
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.11.4 HiPath 4000 Manager Collecting Agent – HiPath 4000 Manager

Exchange
(organizational structure, personal data, PIN and switch-specific data) from HiPath 4000 Man-
ager - Configuration Management.
In addition, HiPath COL also needs the XIE privilege to retrieve connection data (see Special
Items with HiPath 4000 Manager - XIE Interface on page 7-51).
● Creating a Login in HiPath 4000 Manager for HiPath AM (Customer Data) and HiPath COL
● HiPath 4000 Manager Collecting Agent - Activate Access Rights for the XIE Interface (see
page 7-124) ,
● Special Items with HiPath 4000 Manager - XIE Interface (see page 7-125).
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath COL (Call Data)
● Menu item: Account Management - User Account Administration
● Select the User - Add menu to create the hpam user account. In the Actions area, enter
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.11.4.2 HiPath 4000 Manager Collecting Agent - Activate Access Rights for the XIE
Interface
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.11.4.3 Special Items with HiPath 4000 Manager - XIE Interface

4000 Manager Collecting Agent. You can use the same login as for the external exchange
for customer data.
This period is set by default to 15 minutes in HiPath 4000 Manager due to performance
within the HiPath 4000 Manager system.
Consequence:
In HiPath 4000 Manager – Configuration Management - please fill in only the levels
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.11.5 HiPath 4000 Assistant Collecting Agent
Basic Scenario
● HiPath 4000 stores the call detail records to its FT file.

● HiPath 4000 Assistant COL polls the call tickets from HiPath 4000 system and separates
the call tickets to one file for AM (Accounting Management) and another file for PM (Per-
formance Management).
● HiPath AM then retrieves only the AM file from Assistant COL.
In order to perform the polling of the call tickets (call charge data), the following steps are re-
quired:
Procedure
1. Configuration of HiPath 4000 Assistant Collecting Agent - Output Line (see Configuration
of HiPath 4000 Assistant Collecting Agent on page 7-127),
2. Configuration of the switches to be retrieved in HiPath AM (see HiPath 4000 Assistant Col-
lecting Agent – HiPath AM on page 7-63),
3. Configuration of HiPath 4000 Assistant Exchange for Customer Data (see HiPath 4000 As-
sistant Exchange on page 7-68).
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.11.6 Configuration of HiPath 4000 Assistant Collecting Agent

HiPath 4000 Assistant Collecting Agent stores the CDRs gathered from the HiPath 4000 sys-
tem into one single file. This file is periodically made available to HiPath COL in an output di-
rectory.
The procedure of setting up the input line side of HiPath 4000 Assistant Collecting
> Agent is described in the Collecting Agent documentation, and is therefore not ex-
plained here.
HiPath 4000 Assistant Collecting Agent – Setting Up Output Lines on page 7-128
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm

mat.
Assistant Collecting Agent -> Homepage.
item.
Output Line Name Name of output line, e.g. "HPCOL", max. 32 characters.
Homepage.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Filter Select DefaultFilter here.

Path AM.

A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.11.7 HiPath 4000 Assistant Collecting Agent – HiPath AM

See description in section HiPath 4000 Manager Collecting Agent - HiPath AM.
7.11.8 HiPath 4000 Assistant Collecting Agent – HiPath 4000 Assistant

Exchange
See description in section HiPath 4000 Manager Collecting Agent – HiPath 4000 Manager Ex-
change.
7.11.9 HiPath 4000 Assistant Collecting Agent – Activate Access Rights

for the XIE Interface
See description in section HiPath 4000 Manager Collecting Agent - Activate Access Rights for
the XIE Interface.
Special Items with HiPath 4000 Assistant - XIE Interface
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.11.9.1 Special Items with HiPath 4000 Assistant - XIE Interface

● File Transfer (FTP) Access for HiPath AM Call Data Exchange
4000 Assistant Collecting Agent. You can use the same login as for the external exchange
for customer data.
Like in the previous version of XIE, the request files (xxx.req) which are located in the ex-
change directory <iefiles> are read by the system after a configurable amount of time. The
This period is set by default to 15 minutes in HiPath 4000 Assistant due to performance
within the HiPath 4000 Assistant system.
Consequence:
In HiPath 4000 Assistant – Configuration Management - please fill in only the levels
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
HiPath 4000 Manager Collecting Agent - Configuration for AM/PM
7.12 HiPath 4000 Manager Collecting Agent - Configuration for AM/PM

How Do I Add an Additional Output Line for PM in COL, Having One Existing AM Output Line?
HiPath 4000 Node
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.12.1 How Do I Add an Additional Output Line for PM in COL, Having

One Existing AM Output Line?
Procedure
In order to avoid losing call charge data, the following procedure is recommended:
● Retrieve AM Data
● Deactivate AM Input Line
● Perform Enhancement (Add PM Output Line)
● Activate AM and PM Input Line
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.12.2 HiPath 4000 Node
Retrieving AM Data
Please refer to Retrieving AM Data Manually on page 7-142.
Deactivating the AM Input Line

Please refer to Deactivating the AM Input Line on page 7-143.
Enhancing the Input Format With the Fields Required for PM

a) Analyze the already configured CDR data elements for AM.
b) If the CDR data elements required for AM are included in the AMPM_UV1.0 default
input format, then you should use this format as the new input format.
c) Based on the new input format, COL will generate an FTBL batch for the configuration
of the CDR output format.
Path and name of the FTBL batch:
/var/col/data/ftbl/AMPM_UV1.0.GE (German)
/var/col/data/ftbl/AMPM_UV1.0.EN (English)
AM Output Format
The output format for AM must not be changed.
In this way you make sure that the AM data remain unchanged.
AM Output Line
The AM Filter needs to be activated for the AM Output Line.
For details, please refer to Setting the AM Filter for the AM Output Line on page 7-147.
The AM Filter contains the following elements: COLTYPE=0;1;3
For details, please refer to Verifying the AM Filter on page 7-148.
PM Output Line
The PM Output Line is preset to a default value. The PM filter is used as a filter here.
The PM Filter contains the following elements: COLTYPE=0;2;3
For details, please refer to Verifying the PM Filter on page 7-149.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Configuring the Node

a) Transfer the FTBL batch generated by COL to the client using FTP.
b) The TEXT configuration required for PM needs to be compared to the current TEXT
configuration. If elements already configured are modified by the new TEXT configu-
ration, you need to clarify which applications are using these elements.
Hint:
At present there is no solution available for the case when different text configurations are
required for one element.
Since at present there is no TEXT configuration batch available on the Manager, the AMO
TEXT commands listed in the Pre-defined Formats for Output Format Definition and
Pre-defined Formats for Input Format Definition sections have to be used.
See also AMO Text - Configuration for HiPath 4000, on page 7-152:
c) Execute the FTBL batch on the node.
d) Execute the TEXT batch on the node.
e) Configure the virtual tie trunk and CO trunk number (Quer- und Amtssatznummer) us-
ing the AMO FBTN.
Example:
ADD-FBTN:TBL=TN,LTG=99,LTU=1,SLOT=1,CCT=1,
BCHAN=1,VTRKNO=111111;
This dummy entry is only necessary if subscribers have to be measured.
Activating the AM and PM Input Line

Please refer to Activating the AM and PM Input Lines on page 7-146.
Activating the Measurement for Trunks and Subscribers

Please refer to Activating a Measurement on page 7-151.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.12.3 Generating the TieLine Reconciliation Table – Valid for HiPath

4000 Assistant/Manager V1.0 Only
Attention:
> This section is valid for HiPath 4000 Assistant/Manager V1.0 only!
General Requirements for the Client

● HiPath 4000 Expert Access 5.0.42,
● MS Excel 2000; Macro Security Level set to Medium.
There are two possible scenarios for generating the XIE LoadFile for nodes with versions older
than HiPath 4000 V1.0:
1. Scenario 1 – Valid for HiPath 4000 Assistant/Manager V1.0 Only - For all nodes with ver-
sions older than UV1.0 connected to the HiPath 4000 Manager.
2. Scenario 2 – Valid for HiPath 4000 Assistant/Manager V1.0 Only - For a specific node.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.12.4 Scenario 1 – Valid for HiPath 4000 Assistant/Manager V1.0 Only
Attention:
1. Copy the XIE_TOOL.ZIP file to a directory of your choice on the PC´s hard disk, and unzip
the file. The following files will be created: TrunksToExcel.cbl, UpdateGebakt.cbl, uptCon-
nectLib.cbl, XIEGer.cnt, Odf.xls, and Xietool V7.2.xls.
2. Terminate all Excel processes.
3. Start the TrunksToExcel.cbl program by double clicking on the file.
4. An entry dialog opens, and you will be prompted to enter the IP address, the user account
and the user password for the HiPath 4000 Manager, and to confirm by pressing the Start
button.
5. The HiPath 4000 Expert Access (ComWin) opens and connects - in sequential order - to
each of the systems configured in the HiPath Manager, in order to retrieve the data.
The process flow is as follows: Connection to system is established and system opens;
Macro is executed; When macro execution has finished this connection is closed, and new
connection to next system is established. This procedure will be repeated for all systems
configured in the HiPath Manager (indipendent of their version). If during connection es-
tablishment you are asked for the password, then please enter the password and confirm.
When sequential macro execution has finished for all systems, all HiPath 4000 Expert Ac-
cess dialogs will close and the message "Application finished." will be displayed. The CON-
NECT HiPath 4000 Expert Access dialog will remain open and needs to be closed manu-
ally, if necessary.
Note
> If the execution of the CBL macro stops at a certain system during this process, then
the HiPath 4000 Expert Access (formerly ComWin), CBLRun and EXCEL processes
have to be terminated manually using the Task Manager.
If due to problems with a certain system the CBL macro execution cannot be continued, then
you need to edit the INI file TrunksToExcelStatus.ini. This file is located in the same directory
as the CBL macro.
In the INI file you need to change the status of the system that causes the CBL execution to
stop from progress to ok .
After the next start of TrunksToExcel.cbl this system will not be processed any more.
6. The directory where the CBL is located should now contain a file named AM_PM_lines.xls.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7. Open this file by double-clicking it. For each of the systems configured in the HiPath Man-
ager, the CBL macro creates one separate table in the Excel sheet.
Now you only have to fill in the columns H (AM) and I (PM) for each system (EV3.0), thus
determining for which trunk groups (TRK GROUPS) you want to activate AM or PM. This
is done by simply entering an "X“ (either in capital or small letters, both are accepted) into
the respective column. If you want to leave a certain TRK GROUP unassigned, just leave
the column empty. Save the file and close it.
Converting the AM_PM_Lines.xls File to the Database Import Format

8. Start the Xietool V7.2.xls program by double-clicking it, and activate the macros.
(Before doing this, please make sure that no xls file is open!!!)
9. Open the AM_PM_lines.xls file. The active dialog (dialog header highlighted in blue color)
should now display the AM_PM_lines.xls file.
10. Choose Create Tables (Tabellen erzeugen) in the menu bar, then select the XIE tab
sheet, and click on COL Load File. The Excel macro will then create a new table called
LOAD_FILE.
11. Once again, select the XIE tab sheet and click Apply ODF Parameter (ODF-Parameter
zuweisen). A dialog will open. Simply click the OK button to close this dialog.
12. To complete this process, you need to click on XIE -> Export Data (Daten exportieren).
A small dialog opens, allowing you to choose the file you want to export. In this case
LOAD_FILE is the only file that should be displayed as a choice here. Select LOAD_FILE
by clicking on it. The filename should then be highlighted with a blue background. On the
right hand side, next to the filename, enter the path where the file should be copied to on
the PC. Finally, click OK to confirm your entries. The LOAD_FILE.XIE should now be lo-
cated in the folder previously indicated.
13. Close MS Excel, and answer No twice when prompted to save the changes.
Transferring the LOAD_FILE.XIE File to the HiPath-Manager

14. The LOAD_FILE.XIE file must now be copied to a directory of your choice (preferrably
/home) via File Transfer, e.g. (/home/LOAD_FILE.XIE).
Loading the LOAD_FILE.XIE To the Database
ATTENTION!
7 For experienced DBACCESS users only!
15. Establish the connection with the HiPath Manager (preferrably using Telnet or a similar pro-
gram).
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
16. Enter cd /opt/informix to change to the /opt/informix directory.

17. Enter .<Blank>./ids_env_var in order to point to the database.
<Blank> is a placeholder in this context, meaning that you have enter a blank character
between the two periods.
18. Enter dbaccess; dbaccess is launched.
19. Select Query Language and confirm your selection.
Select cdbonline and confirm by pressing the Enter key.
Select New and confirm your selection.
load from “/home/LOAD_FILE.XIE“ insert into col_trunk
Press the Esc button.
Enter Run and confirm by pressing the Enter key.
20. The col_trunk table is now populated with data.
Close dbaccess by pressing the Esc key twice.
21. Terminate the Telnet session by pressing the Esc key.
22. The configuration of the HiPath 4000 Manager is now complete.
Next, you also have to customize the system values in the LDAT AMO accordingly. You
can make the LCR changes either using the CM menu of the HiPath Manager, or manually
using HiPath 4000 Expert Access, or using the UpdateGebakt.cbl macro, which is located
in the same directory as the AM_PM_lines.xls file. The individual steps for using the Up-
dateGebakt.cbl macro are described in Setting the LCR Attribute WCHREG – Valid for Hi-
Path 4000 Assistant/Manager V1.0 Only on page 7-141.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
7.12.5 Scenario 2 – Valid for HiPath 4000 Assistant/Manager V1.0 Only
Attention:
1. The main difference of this (indirect) method is that as a first step you need to establish a
HiPath 4000 Expert Access connection (preferrably via the Direct Access feature of the Hi-
Path Manager) to the system on which you intend to start the TrunksToExcel.cbl.
2. Having established the connection to the selected system, start the
TrunksToExcel.cbl by clicking Makro -> Start CBL. Select the directory where the Trunks-
ToExcel.cbl is located, and start the program by selecting Open.
3. When the CBL process has finished, you can continue with step 5 of Scenario 1. The re-
maining procedure steps are identical.
You can also generate the TieLine Reconciliation Table manually.

> The following description should therefore only be regarded as background informa-
tion for the procedure described above.
1. Analyzing the trunks: Determine whether the trunks are
CO trunks (CDR record for AM and PM)
or Tie trunks (CDR record for PM only).
Attention:
> An incorrect analysis will lead to errors in call charge data recording.
2. Displaying the data records in the trunks:

Example: DISPLAY-BUEND:1&&512;
3. Displaying the Line of these B-channels
Example: DISPLAY-SDSU:ALL,,PEN,PER3,1,1,25,0;
4. Entering the data;
Data format of the import file:
LINE|BUENDEL|RECTYPE|SYSTEMID
Example: 1682|510|2|80E21
Values for RECTYPE:

0 NONE
1 AM Data
2 PM Data
3 AM/PM Data
5. Importing the data into the database using dbaccess.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Setting the LCR Attribute WCHREG – Valid for HiPath 4000 Assistant/Manager V1.0 Only
7.13 Setting the LCR Attribute WCHREG – Valid for HiPath 4000
Assistant/Manager V1.0 Only
Attention:
Requirements
The TrunksToExcel.cbl macro must already have been executed for the respective system.
For details please refer to Generating the TieLine Reconciliation Table – Valid for HiPath 4000
Assistant/Manager V1.0 Only on page 7-136.
1. Use HiPath 4000 Expert Access (ComWin) via the Direct Access feature of the HiPath
Manager to connect to the system on which you intend to make the LDAT changes.
2. To start the CBL, click the Start CBL macro and select the UpdateGebakt.cbl file.
3. The macro will now perform the following steps:
– Search for the System ID in the tables within the AM_PM_lines.xls file;
– Set up a CHANGE-LDAT:............ batch for all TRK GROUPS where the PM column
has been checked, and
– Feed the CHANGE-LDAT:............ batch back into the system.
Result
The data records required for Performance Management will now be output on the tie trunk
lines.
4. This procedure has to be repeated for all systems having versions older than UV1.0.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Retrieving AM Data Manually
7.14 Retrieving AM Data Manually

1. Start: Start Page -> Collecting Agent-> Collecting Status
a) Select the node (system) for which you want to perform the data collection,
b) Click the Collect Now button to start retrieving the AM data.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Deactivating the AM Input Line
7.15 Deactivating the AM Input Line

1. Start: Start Page -> System Management -> HiPath 4000 Administration
a) Select the node for which you want to activate the AM input line,
b) Make sure the Collecting Agent in the Active Applications area is checked.
Click the Collecting Agent tab sheet to bring it to the front on your display,
c) Deactivate the Collect AM Data feature by unchecking the check box,
d) Save your changes.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Creating an Input Format for a specific Variant
7.16 Creating an Input Format for a specific Variant

1. Start: Start Page -> Collecting Agent -> Collecting Agent Homepage -> Input Format
Editor
a) Highlight the AMPM_UV1.0 format,
b) Switch from the Object List view to the Object view.
c) Object -> Copy.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Creating an Input Format for a specific Variant
d) Object -> New;

The empty table of the Input Format Editor is displayed,
e) Object -> Insert;
You created a copy of the AMPM_UV1.0 input format,
f) Format Name field: Enter the name of the new format,
g) Description field: Enter a description of the new format,
h) System Version field: Select the system version;
A message dialog is displayed, notifying you that the format will be edited automatical-
ly. As soon as you confirm this message, all fields that do not exist in this system vari-
ant will be deleted.
i) Save your new input format.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Activating the AM and PM Input Lines
7.17 Activating the AM and PM Input Lines

a) Select the node for which you want to activate the AM and PM input lines,
b) Make sure the Collecting Agent in the Active Applications area is checked.
c) Click the Collecting Agent tab sheet to bring it to the front on your display,
d) Activate the Collect AM Data feature by checking the corresponding check box,
e) Activate the Collect PM Data feature by checking the corresponding check box,
f) Input Format field: Enter the AM/PM input format,
depending on the system version (e.g. AM/PM_UV1.0, ...),
g) PM Input Format field: Enter the AM/PM input format,
depending on the system version (e.g. AM/PM_UV1.0, ...),
h) Save your configuration.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Setting the AM Filter for the AM Output Line
7.18 Setting the AM Filter for the AM Output Line

1. Start: Start Page -> Collecting Agent -> Homepage Collecting Agent -> Definition of
Output Lines
a) Output Line Name field: Select the AM output line,
b) Translation Group field: Select the translation group,
c) Filter field: Select AM Filter,
d) Save your configuration.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Verifying the AM Filter
7.19 Verifying the AM Filter

1. Start: Start Page -> Collecting Agent -> Homepage Collecting Agent -> Filter Editor
a) Filter Name field: Select AM Filter, then switch to Object view.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Verifying the PM Filter
7.20 Verifying the PM Filter

a) Filter Name field: Select PM Filter, then switch to Object view.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Enhancing the AM Filter
7.21 Enhancing the AM Filter

a) Filter Name field: Select AM Filter,
b) Add CONNTYPE = 0 as Filter Clause,
c) Save.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
Activating a Measurement
7.22 Activating a Measurement

a) Select the node, then switch to the Object view,
b) Make sure Performance Management in the Active Applications area is checked,
c) Click the Performance Management tab sheet to bring it to the front on your display,
d) Select the objects to be measured (specific trunks, subscribers) or click the All Items
radio button in the Metered Items area if you want all items to be measured,
e) Click the Save button to activate the measurement.
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
AMO Text - Configuration for HiPath 4000
7.23 AMO Text - Configuration for HiPath 4000

AMO-TEXT - Configuration for HiPath 4000
AMO-TEXT - Configuration for HiPath 4000
ADD-TEXT:SERVICE,VOICE,"0 ";
ADD-TEXT:SERVICE,FAX,"3 ";
ADD-TEXT:SERVICE,DTE,"4 ";
ADD-TEXT:SPEED,0,"000 ";
ADD-TEXT:NETTYPE,ANA,"0 ";
ADD-TEXT:NETTYPE,IDN,"1 ";
ADD-TEXT:NETTYPE,ISDN,"2 ";
ADD-TEXT:SWP,SPACE,"0 ";
ADD-TEXT:SWP,ENDS,"1 ";
ADD-TEXT:SWP,ENDSEC,"2 ";
ADD-TEXT:SWP,ENDL,"3 ";
ADD-TEXT:SWP,SECS,"4 ";
ADD-TEXT:SWP,NEXTSEC,"5 ";
ADD-TEXT:SWP,SECL,"6 ";
ADD-TEXT:SWP,LAS,"7 ";
ADD-TEXT:SWP,LASEC,"8 ";
ADD-TEXT:SWP,LAL,"9 ";
ADD-TEXT:SWP,SECACC,"10 ";
ADD-TEXT:SUBSID,1,"1 ";
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
ADD-TEXT:SIGDATA,0,"1 ";
ADD-TEXT:SIGDATA,1,"0 ";
ADD-TEXT:ROUTCC,0,"00 ";
ADD-TEXT:EXPENS,0,"0 ";
ADD-TEXT:CONNTYPE,INTERN,"3 ";
ADD-TEXT:CONNTYPE,INCO,"1 ";
ADD-TEXT:CONNTYPE,OUTGO,"0 ";
ADD-TEXT:CONNTYPE,ACACT,"4 ";
ADD-TEXT:CONNTYPE,LOAD,"5 ";
ADD-TEXT:SUPLSERV,0,"00 ";
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
ADD-TEXT:ZONE,SPACE,"000 ";
ADD-TEXT:ZONE,INT01,"001 ";
ADD-TEXT:ZONE,INC01,"011 ";
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
ADD-TEXT:ZONE,LOC,"021 ";
ADD-TEXT:ZONE,CHRGFREE,"IN FREE CH";
ADD-TEXT:ZONE,CHRGINFO,"IN INFO CH";
ADD-TEXT:ZONE,NEAR,"031 ";
ADD-TEXT:ZONE,DIST01,"051 ";
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
ADD-TEXT:ZONE,ABR01,"101 ";
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
ADD-TEXT:ZONE,TIE01,"201 ";
ADD-TEXT:CARRIER,0,"0 ";
ADD-TEXT:COPIN,0,"0 ";
ADD-TEXT:COPIN,1,"P ";
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
ADD-TEXT:UNANS,THRCONN,"Y ";
ADD-TEXT:UNANS,NTHRCONN,"N ";
A31003-H3460-M104-4-76A9, July 2012

Config_Examples.fm
A31003-H3460-M104-4-76A9, July 2012

Error_Messages.fm
Nur für den internen Gebrauch Error Messages and Error Numbers
8 Error Messages and Error Numbers

The description of error messages and error codes in HiPath COL Logging does not cover this
subject with enough detail. Therefore, this section contains the lists of the possible error mes-
sages and explanations of the meanings of the error codes.
● Input Line(s) (see page 8-2).
● Output Line(s) (see page 8-3).
● Database Errors (see page 8-4).
● Connection Errors (HiPath 4000 Expert Access) (see page 8-5).
A31003-H3460-M104-4-76A9, July 2012

Error_Messages.fm
Error Messages and Error Numbers Nur für den internen Gebrauch
Input Line(s)
8.1 Input Line(s)
Date Category Short message Servrity Error SwitchID

yyyy.dd.mm receive File 'FFFF' is not re- 0
hh:nn:ss log ceived
File 'FFFF' is not received from line 'XXXX' (error: x)
'FFFF' represents the file name e.g. ':CGD:FTFILE'

'XXXX' is the name of the input line.
Possible Error Codes (code: x):
1 General Receive Error. Possible Cause: "System type is not supported" - The commu-
nication with the chosen system type is not supported.
A31003-H3460-M104-4-76A9, July 2012

Error_Messages.fm
Output Line(s)
8.2 Output Line(s)

yyyy.dd.mm output Output for line 'XXXX' 0
hh:nn:ss log is not provided
Output for line XXXXs' is not provided (error: x)

yyyy.dd.mm output Output for line 'XXXX' 11 Error
hh:nn:ss log is not provided
Output for line XXXXs' is not provided (error: x)
'XXXX' is the name of the output line.
1 Error:
Possible reason for this error: The paths for the Perl directories have not been entered
into the PATH environment variable. Please verify the configuration based on the infor-
mation in chapter 3.2.2 of the HiPath COL Installation Manual (\Manuals\HiPathCOL-
InstEng.pdf on the HiPath AM CD).
2 Target file is locked (possibly locked by another running application).
3 No Data (Data missing, all output files are empty).
A31003-H3460-M104-4-76A9, July 2012

Error_Messages.fm
Database Errors
8.3 Database Errors

yyyy.dd.mm miscella- Database error (code: 3) 11 Error
hh:nn:ss neous
Database error (code: )
1 Data not found

2 Duplicate key in database
3 Database error
4 Referential constraint violation
A31003-H3460-M104-4-76A9, July 2012

Error_Messages.fm
Connection Errors (HiPath 4000 Expert Access)
8.4 Connection Errors (HiPath 4000 Expert Access)

yyyy.dd.mm miscellaneous Transfer error for 0
hh:nn:ss switch 'XXXX
HiPath 4000 Expert Access error during transfer from switch 'XXXX' (code: x)
'XXXX' is the name of the input line.
1 Operation aborted by user

2 Operation aborted
3 An error occurred while reading or creating the local file
4 An error occurred while reading or creating the remote file
5 SAM - ASCII Text - Conversion Error
6 Incorrect Logon
7 Transfer Error
8 Not connected
9 Undefined error
11 Operation not supported
This list is based on HiPath 4000 Expert Access Version 5.0.10 and has been extracted from
the OLE Interface Documentation of HiPath 4000 Expert Access FT; file:
<ComWin-Inst-path>\help\<language>\cbl-phb.pdf, chapter "3.3.5 ole_class ComWinFT", top-
ic "Establishing the connection".
A31003-H3460-M104-4-76A9, July 2012

Error_Messages.fm
Automatic Forwarding of Alarms to Fault Management
8.5 Automatic Forwarding of Alarms to Fault Management

If one of the following error situations occurs error messages are forwarded to the Fault Man-
agement (FM)/HTS application. If FM is not installed the error messages are also displayed in
the Logging Management of HiPath 4000 Assistant/Manager:
1. A system cannot be reached during a collecting cycle -> in FM the respective system is
displayed in "RED" color - RETRY EXCEEDED.
Solution: Restart the Switch/Manager communication.
2. If the threshold value set for the free disk space left on the /var or /var/col partition has
been reached, COL will stop collecting further call charge data since there is not enough
free space available on the /var or /var/col partition any more. The value Required
Free Space is set in the Options dialog (default setting = 10% of free space must be left
on the device).
In FM the Manager is displayed in "RED" color - NOT ENOUGH SPACE.
Solution: Delete data on the /var or /var/col partition.
Example of a filter configuration used in Logging Management to output the COL alarms/error
messages.
For protocol type(s): Error events (select)
Further search criteria:
● Application = COL
● Priority/Severity = CAUTION
● Category = RECEIVE_LOG
Administration in Logging Management:

To activate the forwarding of error messages to the Fault Management you need to activate the
Remote Alarms to Local FM check box in the Admin dialog in Logging Management.
Administration in Fault Management:

In Fault Management, in the /opt/bin/ncc/options ini file, you need to activate the read-
ing in of alarms from the Manager. For more information please refer to the Fault Management
documentation.
A31003-H3460-M104-4-76A9, July 2012

Attachments_COL_PM.fm
Nur für den internen Gebrauch Attachments to the Installation Steps
9 Attachments to the Installation Steps

DISPLAY-DAGR; ... DISPLAY-FBTN:TAB=TN; -- page 9-2
Examples: B01 - B71 -- page 9-76
Examples: S01 - S20 -- page 9-114
A31003-H3460-M104-4-76A9, July 2012

Attachments to the Installation Steps Nur für den internen Gebrauch

DISPLAY-DAGR; ... DISPLAY-FBTN:TAB=TN;
9.1 DISPLAY-DAGR; ... DISPLAY-FBTN:TAB=TN;

DISPLAY-DAGR;
CHANGE-DAGR:FT,40000,ASC,12-10,001,FTFILE;
DISPLAY-FEACG;
DELETE-FEACG:CDRFAST;
ADD-FEACG:CDRCDUMP;
DISPLAY-SELG;
ACTIVATE-SELS:1;
STA-INFO:":CGD:FT_FILE_INTERN",L;
COPY-DAGR;
DISPLAY-SELG:;
Setting Up Selection Group 1 in Two Steps
DISPLAY-SELG;
CHANGE-SELG:SELT,1,1,,,,,,VOICE;
CHANGE-SELG:SELT,1,1,,,,,,,,ALL,ALL,N,N,J,N,N,N,N,N,N,N,N,N,N,N,N,N,N;
CHANGE-SELG:SELT,1,1,,,,,,,,,,,,,,,,,,,,,,,,,,,0,000000;
CHANGE-SELG:SELT,1,1,,,,,,,,,,,,,,,,,,,,,,,,,,,,,0&&999,0&&254,0&&30;
AE-SELG:SELT,1,1,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,N,N,INTERN&KOMMEND&GE-
HEND&ACACT&LOAD,0&&15,0&&9,ALL;
DISPLAY-COSSU;
DISPLAY-COT;
DISPLAY-FEASU;
ACTIVATE-SELS:1;
DISPLAY-SELS;
DISPLAY-ZAND:ALLDATA;
DISPLAY-SELS:;
DEACTIVATE-SELS:1;
DISPLAY-SELS:;
A31003-H3460-M104-4-76A9, July 2012
ADD-FEACG:BITL=CDRFAST&CDRCDUMP;
DISPLAY-SELG
CHANGE-DAGR:FILE=FT,NO=40000,CODE=ASC,TIME=20-11,PERIOD=001,NAME=FT-
FILE;
DISPLAY-DAGR;
DISPLAY-FEACG;
DISPLAY-SELG;
ADD-FEACG:CM=CDRFAST;
DELETE-FEACG:CM=CDRCDIS&CDRATND&CDRSPR;
DISPLAY-FEACG;
ADD-FEACG:CDRFAST;
DISPLAY-FEACG;
ADD-FEACG:CM=CDRCDUMP;
DISPLAY-SELG;
ADD-SELG:TBL=SELG,SELGNO=1,RESOP=Y,BASDEV=FT,RESDEV=FT,BLBAS=1,BL-
RES=1;
DISPLAY-SELG;
DISPLAY-COT:;
DISPLAY-TDCSU:1-1-103-0;
CHANGE-COT:COTNO=22,COTTYPE=COTADD,PAR=ICZL;
CHANGE-LDAT:LROUTE=231,LSVC=VCE,LRTEL=1,LATTR=WCHREG;
DISPLAY-FEASU;
DISPLAY-FEASU;
DISPLAY-SELS;
Connecting via FTP (1)
Connecting via Telnet (1)
A31003-H3460-M104-4-76A9, July 2012


ADD-FBTN:TBL=TRKNO,LTG=99,LTU=1,SLOT=1,CCT=1,BCHAN=1,VTRKNO=111111;
DISPLAY-FBTN:TAB=TN;
A31003-H3460-M104-4-76A9, July 2012

DISPLAY-DAGR;
DISPLAY-DAGR;
DISPLAY-DAGR;
H500: AMO DAGR STARTED
FILE-PARAMETERS OF DMS-FILES OF CALL CHARGE REGISTRATION
FILE NAME NUMBER OF RECORDS IN THE FILE
CDRC1 65000
CDRC2 0
FT 65000
PARAMETERS FOR THE FILE FOR FILE-TRANSFER:
OUTPUT-CODE : ASC
COPY TIME (DD-HH) : 05-10
COPY PERIOD (HOURS) : 001
NAME OF THE TRANSFER FILE : FTFILE
AMO-DAGR -111 SMDR/DMDR FILE SIZES
DISPLAY COMPLETED;
A31003-H3460-M104-4-76A9, July 2012


CHANGE-DAGR:FT,40000,ASC,12-10,001,FTFILE;
CHANGE-DAGR:FILE=FT,NO=40000,CODE=ASC,TIME=05-10,PERIOD=001,NAME="FTFILE";
CHANGE COMPLETED;
A31003-H3460-M104-4-76A9, July 2012

DISPLAY-FEACG;
DISPLAY-FEACG;
DISPLAY-FEACG;
H500: AMO FEACG STARTED
CALL DATA REGISTRATION AT ATTENDANT CONSOLE : DEACTIVATED;
CALL DATA REGISTRATION ON ADD. DEVICE, IMMEDIATE OUTPUT : ACTIVATED; CDRCDUMP
CALL DATA REGISTRATION ON ADDITIONAL DEVICE, CALL UP : ACTIVATED; CDRFAST
CALL DATA REGISTRATION PER STATION, PRINTER OUTPUT : DEACTIVATED;
CALL DATA REGISTRATION ON FAST OUTPUT DEVICE : DEACTIVATED;
AMO-FEACG-111 SMDR/DMDR FEATURE LIST
DISPLAY COMPLETED;
A31003-H3460-M104-4-76A9, July 2012


DISPLAY-FEACG;
AB-FEACG;
H500: AMO FEACG GESTARTET
GEBUEHRENERFASSUNG AM VERMITTLUNGSPLATZ : AUSGESCHALTET;
GEBUEHRENERFASSUNG AUF ZUSATZGERAET, SOFORTAUSGABE : EINGESCHALTET; CDRCDUMP

GEBUEHRENERFASSUNG AUF ZUSATZGERAET, ABRUF : AUSGESCHALTET; CDRFAST
GEBUEHRENERFASSUNG PRO TEILNEHMER, DRUCKERAUSGABE : AUSGESCHALTET;
GEBUEHRENERFASSUNG AUF SCHNELLES AUSGABEGERAET : EINGESCHALTET;
AMO-FEACG-111 BITLEISTE DER GEBUEHRENERFASSUNG

ABFRAGEN DURCHGEFUEHRT;
A31003-H3460-M104-4-76A9, July 2012

DELETE-FEACG:CDRFAST;
DELETE-FEACG:CM=CDRFAST;
DELETE-FEACG:CM=CDRFAST;
DELETE COMPLETED;
A31003-H3460-M104-4-76A9, July 2012


ADD-FEACG:CDRCDUMP;
ADD-FEACG:CM=CDRDUMP;
ADD-FEACG:CM=CDRDUMP;
ADD COMPLETED;
A31003-H3460-M104-4-76A9, July 2012

DISPLAY-SELG;
DISPLAY-SELG:;
H500: AMO SELG STARTED
+==============================================================================+ Selection group 1 can

| SELECTION GROUP : 1 | be used for FT output,
+------------------------------------------------------------------------------+
| | as it is already config-
| OPERATING STATE : ON | ured and activated
| |
| RESOP : N |
(FORM01 is used).
| BASDEV : FT BLBAS : 1 |
| RESDEV : NODEV BLRES : 0 |
| |
+==============================================================================+
| |
| SELECTION GROUP : 1 SELECTION TABLE : 1 |
| |
| FORMBAS : FORM01 TARIFF : NOCALC |
| FORMRES : NOFORM DESTCNT : A22 |
| |
|
+==============================================================================+
| SELECTION GROUP : 2 |
+------------------------------------------------------------------------------+
| |
| OPERATING STATE : OFF |
|+==============================================================================+
+------------------------------------------------------------------------------+
| |
| |
|+==============================================================================+
+------------------------------------------------------------------------------+
| |
| |
|+==============================================================================+
AMO-SELG -111 ADMINISTRATION OF SELECTION GROUPS AND TABLES
DISPLAY COMPLETED;
A31003-H3460-M104-4-76A9, July 2012


ACTIVATE-SELS:1;
ACTIVATE-SELS:SELGRNO=1;
H500: AMO SELS STARTED
AMO-SELS -111 SMDR/DMDR SELECTION GROUP SWITCHES
ACTIVATE COMPLETED;
A31003-H3460-M104-4-76A9, July 2012

sta-info:":CGD:FT_FILE_INTERN",L;
H500: AMO INFO GESTARTET
< :CGD:FT_FILE_INTERN >
FILETYPE : DATA
FILESIZE : H'00000132
FILEGRANULARITY : H'0001
FILECONECTIONS : H'0002
READCONECTIONS : H'0001
WRITECONECTIONS : H'0001
OPEN SHARE : H'0000
OWNER : H'FFFF
FILE BLOCKS : H'00000001
VOLUMENAME : A1H1G
VOLUME SIZE : H'02300000
ACCESS : H'000F
FSTAT BEENDET
STATUS = H'0000
AMO-INFO -111 FILESTATUS AUSGEBEN
START DURCHGEFUEHRT;
A31003-H3460-M104-4-76A9, July 2012


COPY-DAGR;
COPY-DAGR;
COPY-DAGR;
COPY COMPLETED;
A31003-H3460-M104-4-76A9, July 2012

DISPLAY-SELG:;
DISPLAY-SELG:;
DISPLAY-SELG:;
+==============================================================================+
+------------------------------------------------------------------------------+
| |
| |
| RESOP : |
| BASDEV : BLBAS : |
| RESDEV : BLRES : |
| |
+==============================================================================+
+==============================================================================+
+------------------------------------------------------------------------------+
| |
| |
| RESOP : N |
| |
+==============================================================================+
| |
| |
| FORMBAS : FORM04 TARIFF : NOCALC |
| |
| LEVEL0 : 0&&999 |
| LEVEL1 : 0&&254 |
| LEVEL2 : 0&&30 |
| CDRCD : 0&&999999 |
| |
| ATNDGR : 0&&15 |
| SERVICE : VOICE &FAX &DTE |
| |
| CDRULT : 0 CONNTL : 00 : 00 : 00 |
| COPIN : 0&&8 CARRIER : 0&&9 |
| |
| SELECTION FEATURES 1 : |
| |
| CTYPE : ALL PAYPARTY : ALL NSTAT : N |
| CDRAC : N SFSETUP : N CDBAD : N |
| CDRC : N CDRSTA : N THRGCON : N |
| SECTION : N TIE-LINE : N EXPENS : N |
| CONNTYP : INTERN &INCO &OUTG |
| RECTYP : ALL |
| |
| |
| CDCHU : N CDRULTE : N CONNT : N |
| PCODE : N PPCF : N STATAB1 : N |
| STATAB2 : N DNOTBL1 : N DNOTBL2 : N |
| |
+==============================================================================+
A31003-H3460-M104-4-76A9, July 2012


+==============================================================================+
+------------------------------------------------------------------------------+
| |
| |
| RESOP : N |
| BASDEV : CDRC1 BLBAS : 1 |
| |
+==============================================================================+
| |
| |
| FORMBAS : HDFORM TARIFF : NOCALC |
| |
| LEVEL0 : 0&&999 |
| LEVEL1 : 0&&254 |
| LEVEL2 : 0&&30 |
| CDRCD : 0&&999999 |
| |
| ATNDGR : 0&&15 |
| SERVICE : VOICE &FAX &DTE |
| |
| CDRULT : 0 CONNTL : 00 : 00 : 00 |
| COPIN : 0&&8 CARRIER : 0&&9 |
| |
| |
| CTYPE : ALL PAYPARTY : ALL NSTAT : N |
| CDRAC : N SFSETUP : N CDBAD : N |
| CDRC : N CDRSTA : N THRGCON : N |
| SECTION : N TIE-LINE : N EXPENS : N |
| CONNTYP : INTERN &INCO &OUTG |
| RECTYP : ALL |
| |
| |
| CDCHU : N CDRULTE : N CONNT : N |
| PCODE : N PPCF : N STATAB1 : N |
| STATAB2 : N DNOTBL1 : N DNOTBL2 : N |
| |
+==============================================================================+
+==============================================================================+
+------------------------------------------------------------------------------+
| |
| |
| RESOP : N |
| |
+==============================================================================+
DISPLAY COMPLETED;
A31003-H3460-M104-4-76A9, July 2012


How to set up selection group 1 in two steps:
ADD-SELG:TBL=SELG,SELGNO=1,RESOP=Y,BASDEV=FT,RESDEV=FT,BLBAS=1,BLRES=1;
ADD COMPLETED;
CHANGE-SELG:TBL=SELT,SELGNO=1,SELTABNO=1,FORMBAS=FORM01,FORMRES=NOFORM,
TARIF=NOCALC,DESTCNT="A22",CDRCD=0&&999999,SERVICE=DTE&FAX&VOICE,ATNDGR=0&&15,
CTYPE=ALL,PAYPARTY=ALL,CDRC=N,CDRSTA=N,THRGCON=N,NSTAT=N,SECTION=N,CDCHU=N,
CDRAC=N,SFSETUP=N,CDBAD=N,CDRULTE=N,CONNT=N,PCODE=N,PPCF=N,STATAB1=N,
STATAB2=N,DNOTBL1=N,DNOTBL2=N,CDRULT=0,CONNTL=000000,LEVEL0=0&&99,
LEVEL1=0&&254,LEVEL2=0&&30,TIELINE=N,EXPENS=N,
CONNTYP=INTERN&INCO&OUTG&ACACT&LOAD,COPIN=0&&8,CARRIER=0&&9,RECTYP=ALL;
CHANGE COMPLETED;
A31003-H3460-M104-4-76A9, July 2012


DISPLAY-SELG;
ab-selg;
AB-SELG;
H500: AMO SELG GESTARTET
+==============================================================================+
| SELEKTIONSGRUPPE : 1 |
+------------------------------------------------------------------------------+
| |
| BETRIEBSZUSTAND : OFF |
| |
| RESBET : J |
| BASGER : FT BLBAS : 1 |
| RESGER : FT BLRES : 1 |
| |
+==============================================================================+
+==============================================================================+
+------------------------------------------------------------------------------+
| |
| |
| RESBET : N |
| BASGER : FT BLBAS : 1 |
| RESGER : NODEV BLRES : 0 |
| |
+==============================================================================+
| |
| SELEKTIONSGRUPPE : 2 SELEKTIONSTABELLE : 1 |
| |
| FORMBAS : FORM04 TARIF : NOCALC |
| FORMRES : NOFORM ZLNUZ : A22 |
| |
...
+==============================================================================+
+------------------------------------------------------------------------------+
| |
...
+==============================================================================+
+------------------------------------------------------------------------------+
| |
| BETRIEBSZUSTAND : OFF_WITHOUT_QUEUEING |
...
<
A31003-H3460-M104-4-76A9, July 2012

<ae-selg:selt,1,1,,,,,0&&999999;
AE-SELG:SELT,1,1,,,,,0&&999999;
H19: DIE TABELLENEINRICHTUNG ERFOLGT NUR DANN,
WENN DER PARAMETER KOMDIE EINGEGEBEN WIRD.
AMO-SELG -111 SELEKTIONSGRUPPEN
AENDERN DURCHGEFUEHRT;
A31003-H3460-M104-4-76A9, July 2012


CHANGE-SELG:SELT,1,1,,,,,,VOICE;
ae-selg:selt,1,1,,,,,,voice;
AE-SELG:SELT,1,1,,,,,,VOICE;
A31003-H3460-M104-4-76A9, July 2012

CHANGE-SELG:SELT,1,1,,,,,,,,ALL,ALL,N,N,J,N,N,N,N,N,N,N,N,N,N,N,N,N,N;
ae-selg:selt,1,1,,,,,,,,all,all,n,n,j,n,n,n,n,n,n,n,n,n,n,n,n,n,n;
AE-SELG:SELT,1,1,,,,,,,,ALL,ALL,N,N,J,N,N,N,N,N,N,N,N,N,N,N,N,N,N;
A31003-H3460-M104-4-76A9, July 2012


CHANGE-SELG:SELT,1,1,,,,,,,,,,,,,,,,,,,,,,,,,,,0,000000;
ae-selg:selt,1,1,,,,,,,,,,,,,,,,,,,,,,,,,,,0,000000;
AE-SELG:SELT,1,1,,,,,,,,,,,,,,,,,,,,,,,,,,,0,000000;
A31003-H3460-M104-4-76A9, July 2012

CHANGE-SELG:SELT,1,1,,,,,,,,,,,,,,,,,,,,,,,,,,,,,0&&999,0&&254,0&&30;
ae-selg:selt,1,1,,,,,,,,,,,,,,,,,,,,,,,,,,,,,0&&999,0&&254,0&&30;
AE-SELG:SELT,1,1,,,,,,,,,,,,,,,,,,,,,,,,,,,,,0&&999,0&&254,0&&30;
H500: AMO SELG GESTARTET <ae-selg:selt,1,1,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,n,n,intern&kommend&gehend&acact&
load,0&&15,0&&9,all;
AE-SELG:SELT,1,1,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,N,N,
INTERN&KOMMEND&GEHEND&ACACT&LOAD,0&&15,0&&9,ALL;
<
A31003-H3460-M104-4-76A9, July 2012


AE-SELG:SELT,1,1,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,N,N,INTERN&KOMMEND&GE-
HEND&ACACT&LOAD,0&&15,0&&9,ALL;
ae-selg:selt,1,1,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,n,n,intern&kommend&gehend&acact&
load,0&&15,0&&9,all;
AE-SELG:SELT,1,1,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,N,N,
INTERN&KOMMEND&GEHEND&ACACT&LOAD,0&&15,0&&9,ALL;
A31003-H3460-M104-4-76A9, July 2012

DISPLAY-COSSU;
ab-cossu;
AB-COSSU;
H500: AMO COSSU GESTARTET
+------+-----------------+---------------+-----------------+
| COS | SPRACHE | FAX | DEE |
+------+-----------------+---------------+-----------------+
| 1 |>ANALOGES EG HALBAMT |
| | HAB | HAB | HAB |
| | QVKW | QVKW | QVKW |
| | DUAS | FSM | GRUBE |
| | PRTLN | GRUBE | DSM |
| | GESP | | MULTRA |
| | GEZ | | |
| | BUC | | |
| | SSM | | |
| | ZURL | | |
| | UENW | | |
| 2 |>ANALOGES EG AMT OHNE AULEXT |
| | FBKW | FBKW | FBKW |
| | GESP | FSM | GRUBE |
| | GEBINT | GRUBE | DSM |
| | GEZ | UENW | MULTRA |
| | BUC | | UENW |
| | SSM | | |
| | UENW | | |
| 3 |>ANALOGES EG AMT MIT AULEXT |
| | GEZ | UENW | MULTRA |
| | BUC | | UENW |
| | SSM | | |
| | AULEXT | | |
| | AULERU | | |
| | UENW | | |
| 11 |>DIGITALES EG HALBAMT OHNE AULEXT MIT BRIEFKASTEN |
| | HAB | HAB | HAB |
| | BRK | UENW | MULTRA |
| | BUC | | UENW |
| | DATLN | | |
| | AULRTG | | |
| | UENW | | |
| 12 |>DIGITALES EG AMT OHNE AULEXT MIT BRIFKASTEN |
| | BUC | | UENW |
| | DATLN | | |
| | AULRTG | | |
| | UENW | | |
| 13 |>DIGITALES EG AMT MIT AULEXT MIT BRIFKASTEN |
A31003-H3460-M104-4-76A9, July 2012



| | BUC | | UENW |
| | DATLN | | |
| | AULEXT | | |
| | AULERU | | |
| | AULFAT | | |
| | AULRTG | | |
| | AULUMF | | |
| | UENW | | |
| 20 |>SPEZIAL FUER TELEWORKER VERLAENGERUNG GERKON TCVLV|
| | FBKW | NIB | FBKW |
| | QVKW | NQVB | QVKW |
| | GEBINT | UENW | GRUBE |
| | BRK | | DSM |
| | BUC | | MULTRA |
| | DATLN | | UENW |
| | SPECAR | | |
| | UENW | | |
| 22 |> |
| | FBKW | NIB | FBKW |
| | QVKW | NQVB | QVKW |
| | DATLN | UENW | GRUBE |
| | MSN | | DSM |
| | MULTRA | | MSN |
| | CCBS | | MULTRA |
| | COLR | | UENW |
| | UENW | | |
| 23 |>SPEZIAL FUER EDSS1 TLN UND TELEWORKING CLIENT S0PP|
| | BUC | | UENW |
| | DATLN | | |
| | MULTRA | | |
| | UENW | | |
| 90 |>BERECHTIGUNGSKLASSE FUER SAETZE |
| | FBKW | NIB | NIB |
| | QVKW | NQVB | NQVB |
| | GESP | | |
| | UENW | | |
| 99 |>BERECHTIGUNGSKLASSE FUER ATTENDANT |
| | FBKW | NIB | NIB |
| | QVKW | NQVB | NQVB |
| | UENW | | |
| 122 |>EDSS1 EG |
| | DATLN | GRUBE | GRUBE |
| | MSN | MSN | MSN |
| | MULTRA | MULTRA | MULTRA |
| | CCBS | | |
| | CW | | |
| | | | |
+------+-----------------+---------------+-----------------+
+------+-----+
| COEX | COS |
...
AMO-COSSU-111 BERECHTIGUNGSKLASSEN
A31003-H3460-M104-4-76A9, July 2012

DISPLAY-COT;
ab-cot;
AB-COT;
H500: AMO COT GESTARTET
COT: 0 INFO: QUER SO CORNET NQ E/V3 BEIDE

GERAET: S0VERB QUELLE: DB
PARAMETER:
LEITUNG MIT MELDEKRITERIUM MVLT
AUFSCHALTEN BZW. ANKLOPFEN MOEGLICH AMGL
UEBERGABE IM BESETZT-, RUF- ODER GESPRAECHSZUSTAND UELM
NETZWEITER RUECKRUF IM BESETZTFALL RRBN
NETZWEITER RUECKRUF IM FREIFALL RRFN
ANRUFUMLEITUNG NETZWEIT ERLAUBT AULN
RUFWEITERSCHALTUNG NETZWEIT ERLAUBT RWSN
UEBERTRAGUNG DER VBZ-GRUPPE DES TLN UEBER S0/S2-LEITUNG VBZN
ANRUFE ZU EINEM BESETZTEN SA WERDEN NICHT AUSGELOEST SAAO
"SENDING_COMPLETE" WIRD GESETZT BLOC
LEITUNG FUEHRT ZU KNOTEN MIT ROUTE OPTIMIERUNG ROPT
TSC-SIGNAL. F. UEBERGR. LM BEI DIGITALEN NETZ (ERFORDERLICH) TSCS
LEITUNG SENDET BETRAEGE AN URSPRUNGSKNOTEN LTMB
ERREICHBARKEITSPRUEFUNG DES UMLEITUNGSZIELES MOEGLICH PRZL
UUS SERVICE CLASS 1 (VERBINDUNGSAUFBAU BASIC CALL) UUS1
UUS SERVICE CLASS 3 (VERBINDUNGSABBAU BASIC CALL) UUS3
PIN REMOTE MOEGLICH (GEHENDER UND KOMMENDER VERKEHR) PINR
B-KANAL-VERHANDLUNG (PREFERRED-PREFERRED COLLISION VERH.) BKVE
KEIN TON KTON
COT: 2 INFO: QUER S2 CORNET NQ E/V3 BEIDE

PARAMETER:
PROGRAMMIERUNG ANRUFUMLEITUNG FUER ANDERE TLN MGL. AUAT
KEIN TON KTON
COT: 3 INFO: WAML OHNE LCR DATEN / V3.0 CORNV33

GERAET: LAN QUELLE: DB
PARAMETER:
WIEDERANRUFE ZU VF WERDEN UNTERDRUECKT KWDA
KOMMENDE LEITUNG VON ANLAGE OHNE LCR OLCR
VOREINGESTELLE KNOTENNUMMER DER LEITUNG VERWENDEN VKNN
KOMMENDE LEITUNG VON ANLAGE OHNE LCR (DATEN) OLRD
KEIN ABWURF BEI TRANSIT GEHEND KATG
A31003-H3460-M104-4-76A9, July 2012


SPRACHKOMPRIMIERUNG NICHT ERLAUBT SPKN

KEIN TON KTON
COT: 5 INFO: QUER VCM CORNET NQ E/V3 BEIDE

GERAET: SKVERB QUELLE: DB
PARAMETER:
SPRACHKANAL KOMPRIMIERT SPRK
KEIN TON KTON
COT: 10 INFO: 10: AMT IKZ O. ABWURF

GERAET: IKZ QUELLE: DB
PARAMETER:
LEITUNG MIT VORAB-WAHLENDEAUSSENDUNG LTVW
KEINE KNOTENNUMMER ZUM PARTNER SENDEN LOKN
KEIN TON KTON
COT: 11 INFO: 11: AMT IKZ M. ABWURF

GERAET: IKZ QUELLE: DB
PARAMETER:
ABWURF ZUM VF WENN WAHL UNVOLLSTAENDIG AWWU
ABWURF ZUM VF WENN NICHT VORHANDEN AWNV
ABWURF ZUM VF IM BESETZTFALL AWBF
ABWURF ZUM VF WENN NICHT BERECHTIGT AWNB
ABWURF ZUM VF BEI GASSENBESETZT AWGB
ABWURF ZUM VF BEI ANRUFSCHUTZ AWAS
ABWURF ZUM VF BEI FREI (NACH ZEIT) AWFR
KEIN TON KTON
COT: 12 INFO: 12: AMT HKZ

GERAET: HKZ QUELLE: DB
PARAMETER:
A31003-H3460-M104-4-76A9, July 2012


KEIN TON KTON
COT: 20 INFO: 20: S0/2 AMT EDSBRD O. ABWURF

GERAET: S2AMT QUELLE: DB
PARAMETER:
ANRUF BEI EINHAENGEN IN RUECKFRAGE AERF
SATZ GESPERRT FUER FLAG-TRACE NOFT
KEIN TON KTON
COT: 21 INFO: 21: S0/2 AMT EDSBRD M. ABWURF

PARAMETER:
ABWURF BEI NICHT ERLAUBTER WAHL AWNE
ABWURF WENN KEINE WAHL ERFOLGT AWKW
KEIN TON KTON
COT: 22 INFO: 22: S0/2 AMT 1TR6 O. ABWURF

PARAMETER:
KEIN TON KTON
COT: 23 INFO: 23: S0/2 AMT 1TR6 M. ABWURF

A31003-H3460-M104-4-76A9, July 2012


PARAMETER:
ABWURF BEI NICHT ERLAUBTER WAHL AWNE
ABWURF WENN KEINE WAHL ERFOLGT AWKW
KEIN TON KTON
COT: 30 INFO: 30: S0/2 QUER CORNV33

PARAMETER:
PRIORITAET FUER VF WIRD AUS MELDUNG ERMITTELT PRIO
TRANSIT-COUNTER-VERWALTUNG FUER S0/S2-LEITUNG AKTIVIEREN TRCA
GEBUEHRENELEMENTE NICHT SENDEN GBNS
GEBUEHREN KOMMEND IGNORIEREN GBKI
CORNET-NQ PICKUP-INFO NICHT UNTERSTUETZT NQPI
UNTERDRUECKEN SIGNALISIERUNG VON CDR-E SPEZ. MELDUNGEN NCDR
CORNET-NQ NETZWEITE UEBERNAHME NICHT UNTERSTUETZT NQNP
KEIN TON KTON
COT: 31 INFO: 31: S0/2 QUER LOKN

PARAMETER:
A31003-H3460-M104-4-76A9, July 2012


KEIN TON KTON
COT: 32 INFO: 32: S0/2 QUER ECMA1 AB V2.0

PARAMETER:
GEBUEHRENUEBERTRAGUNG PRO VERBINDUNG (ERFORDERL. CORNET-NQ) GBUE
KEIN TON KTON
COT: 33 INFO: 33: S0/2 QUER ECMA2 < V3.0

PARAMETER:
KEIN TON KTON
COT: 34 INFO: 34: S0/2 QUER CORNV33 < V3.5

PARAMETER:
A31003-H3460-M104-4-76A9, July 2012



LEITUNG MIT IMPLIZITEN RUFNUMMERN LIRU
KEIN TON KTON
COT: 35 INFO: 35: S0/2 QUER ECMA1 < V2.0

PARAMETER:
KEIN TON KTON
COT: 36 INFO: 36: S0/2 QUER ECMA2 AB V3.0

PARAMETER:
KEIN TON KTON
COT: 40 INFO: 40: KOMPRIMIERT ZU VCM

PARAMETER:
A31003-H3460-M104-4-76A9, July 2012


KEIN LOKALER HALTETON, HALTETON VON GEGENANLAGE KLHT
KEIN TON KTON
COT: 50 INFO: 50: PSE - MFV

GERAET: PSE QUELLE: DB
PARAMETER:
KEIN TON KTON
COT: 51 INFO: 51: PSE - IWV

GERAET: PSE QUELLE: DB
PARAMETER:
KEIN TON KTON
COT: 70 INFO: 70: VMS

GERAET: UNAB QUELLE: DB
PARAMETER:
SPRACHINFO-SERVER VM
COT: 71 INFO: 71: PHONEMAIL

PARAMETER:
AMTSWAEHLTONEINSPEISUNG BEI GEHENDEN AMTSBELEGUNGEN AWTE
LEITUNG MIT IMPLIZITEN RUFNUMMERN LIRU
DURCHSCHALTEN BEI UEBERGABE IM RUFZUSTAND BEI TRANSIT DUET
KEIN TON KTON
COT: 80 INFO: 80: WAML

PARAMETER:
A31003-H3460-M104-4-76A9, July 2012


KEIN TON KTON
COT: 90 INFO: 90: EDSS1-NET

PARAMETER:
NACHWAHL UNBEGRENZT MOEGLICH PDUR
QUERLEITUNG QUER
KEIN TON KTON
COT: 100 INFO: QUER SO CORNET NQ E/V3 BEIDE

PARAMETER:
NPI ISDN, ABGEHENDER VERKEHR NPIS
KEIN TON KTON
COT: 101 INFO:

PARAMETER:
KEIN TON KTON
COT: 102 INFO: QUER S2 CORNET NQ E/V3 BEIDE

PARAMETER:
A31003-H3460-M104-4-76A9, July 2012


KEIN TON KTON
COT: 103 INFO: WAML OHNE LCR DATEN / V3.0 CORNV33

PARAMETER:
KEIN TON KTON
COT: 105 INFO: QUER VCM CORNET NQ E/V3 BEIDE

PARAMETER:
KEIN TON KTON
COT: 110 INFO:

PARAMETER:
UEBERGABE NUR IM GESPRAECHSZUSTAND UEGM
KEIN TON KTON
COT: 112 INFO:

A31003-H3460-M104-4-76A9, July 2012


PARAMETER:
KEIN TON KTON
COT: 120 INFO:

PARAMETER:
KOMMENDE GEBUEHRENERFASSUNG UEBER ZONE ODER LEITUNG KGZL
KEIN TON KTON
COT: 121 INFO:

PARAMETER:
KEIN TON KTON
COT: 124 INFO:

PARAMETER:
KEIN TON KTON
COT: 150 INFO:

PARAMETER:
A31003-H3460-M104-4-76A9, July 2012


KEIN LOKALER HALTETON, HALTETON VON GEGENANLAGE KLHT
KEIN TON KTON
VARNU: 1 GERMANY
...
AMO-LDAT -111 LCR-RICHTUNGEN
<
A31003-H3460-M104-4-76A9, July 2012


DISPLAY-FEASU;
ab-feasu;
AB-FEASU;
H500: AMO FEASU GESTARTET
FREIGEGEBENE LEISTUNGSMERKMALE
RNGZ RNGI SAS SAF SAD AUFS FRAD NACHTZU

BERUMC BERUMS BERUMA BERUMV BERUMZ BERUMD HOTROE ANRS
VARKONF FANGEN WW ANKS RR DRS MAK UML
AUN KET DRD ESI RUF NOTAUF NOTTR SYNCANN
GEBGNW GEBGAMT GESPINT GESPNW GESPAMT LCRET POSTBUSY POSTFREE
RELOCATE VOICO SANW PINNW TERMIN VFVE EAUL GIS
ERHPRIO TRVAWAHL ANRLSOPT CDRE DIRAUN
GESPERRTE LEISTUNGSMERKMALE
GEFM BELM ABDUWA RES GEBFREI WARTVF AMTFANG LEDSIGN

VMSIWV RELCON RERING AUTOV RRB RRF GEBINT GEBK
PININT TRVARUF DCPA NCT RCCB MLPP CDRACC CLIP
H02: DIE GESAMTE ERWEITERTE GEBUEHRENERFASSUNG (CDRE) IST AKTIV.
AMO-FEASU-111 LEISTUNGSMERKMALE, BITLEISTE SWU SETZEN

A31003-H3460-M104-4-76A9, July 2012

ACTIVATE-SELS:1;
eins-sels:1;
EINS-SELS:1;
H500: AMO SELS GESTARTET
AMO-SELS -111 SELEKTIONSGRUPPEN SCHALTEN
EINSCHALTEN DURCHGEFUEHRT;
A31003-H3460-M104-4-76A9, July 2012


DISPLAY-SELS;
ab-sels;
AB-SELS;
BETRIEBSZUSTAENDE DER SELEKTIONSGRUPPEN
SELGRUNU BETRIEBSZUSTAND
1 EIN
2 AUS
3 AUS
4 STOP
A31003-H3460-M104-4-76A9, July 2012

DISPLAY-ZAND:ALLDATA;
DISPLAY-ZAND:TYPE=ALLDATA;
H500: AMO ZAND STARTED
GENERAL SYSTEM DATA:

====================
TRANSFER = PICKUP , ALERTN = NO ,

AUTHUP = TA ,
RNGBKTN = YES , TRANSINH = NO ,
NIGHT = TA ,
ITRFWD = NO , HOLDTN = MUSIC , ANATESIG = TONE ,
DSSLT = 5 , CODTN = YES , CONFSUB = YES ,
DATEDIS = DDMM, CNTRYCD = 0 , RCLLT = NO ,
MELODY = 1, TRCD = , CPBLOWL = 10 ,
CPBUPPL = 20 , CUTHRU1A = NO , PREDIA = NO ,
SIUANN = 1, CO = NO , COEXN = 0 ,
CBKNO = 5 , SEVDIG = NO , PNNO = 1 -85 -200,
DISPMODE = MODE1, PNODECD = 808520, ROUTOPTP = YES ,
ROUTOPTD = NO , CALLOFF = NO , PARARING = YES ,
DSSDEST = NO , ONEPARTY = YES , MSGDELAY = NO ,
EXCOCO = NO , TRDGTPR = NO , COANN = NO ,
HOTDIAL = NO , TRANSTOG = NO , NOCFW = NO ,
HOLDHUNT = NO , POSTDDLY = NO , EXBUSYOV = NO ,
OVRMST = NO , OVRHUNT = NO , CONITPRO = YES ,
RECHUNT = NO , CALLACMP = NO ;
AMO-ZAND -111 SYSTEM DATA

DISPLAY COMPLETED;
A31003-H3460-M104-4-76A9, July 2012


DISPLAY-SELS:;
ab-sels:;
AB-SELS:;
1 EIN
2 AUS
3 AUS
4 STOP
A31003-H3460-M104-4-76A9, July 2012

DEACTIVATE-SELS:1;
DEACTIVATE-SELS:SELGRNO=1;
DEACTIVATE-SELS:SELGRNO=1;
DEACTIVATE COMPLETED;
A31003-H3460-M104-4-76A9, July 2012


DISPLAY-SELS:;
AB-SELS:;
1 AUS
2 AUS
3 AUS
4 STOP
A31003-H3460-M104-4-76A9, July 2012

ADD-FEACG:BITL=CDRFAST&CDRCDUMP;
EINRICHTEN-FEACG:BITL=FAST&GEZSO;
EINRICHTEN-FEACG:BITL=FAST&GEZSO;
H500: AMO FEACG GESTARTET
H05: ELEMENT FAST WURDE GESETZT. ALLE SELEKTIONSGRUPPEN, BIS AUF DIE ERSTE,
WURDEN AUSGESCHALTET
AMO-FEACG-111 BITLEISTE DER GEBUEHRENERFASSUNG
EINRICHTEN DURCHGEFUEHRT;
A31003-H3460-M104-4-76A9, July 2012


DISPLAY-SELG
DIS-SELG;
+==============================================================================+
+------------------------------------------------------------------------------+
| |
| |
| RESOP : |
| |
+==============================================================================+
+==============================================================================+
+------------------------------------------------------------------------------+
| |
| |
| RESOP : |
| |
+==============================================================================+
+==============================================================================+
+------------------------------------------------------------------------------+
| |
| |
| RESOP : |
| |
+==============================================================================+
+==============================================================================+
+------------------------------------------------------------------------------+
| |
| OPERATING STATE : OFF_WITHOUT_QUEUEING |
| |
| RESOP : |
| |
+==============================================================================+
DISPLAY COMPLETED;
A31003-H3460-M104-4-76A9, July 2012

CHANGE-DAGR:FILE=FT,NO=40000,CODE=ASC,TIME=20-11,PERIOD=001,NAME=FT-
FILE;
CHANGE COMPLETED;
A31003-H3460-M104-4-76A9, July 2012


DISPLAY-DAGR;
DIS-DAGR;
FILE-PARAMETERS OF DMS-FILES OF CALL CHARGE REGISTRATION
FILE NAME NUMBER OF RECORDS IN THE FILE
CDRC1 65000
CDRC2 0
FT 40000
PARAMETERS FOR THE FILE FOR FILE-TRANSFER:
OUTPUT-CODE : ASC
COPY TIME (DD-HH) : 20-11
COPY PERIOD (HOURS) : 001
NAME OF THE TRANSFER FILE : FTFILE

DISPLAY COMPLETED;
A31003-H3460-M104-4-76A9, July 2012

DISPLAY-FEACG;
DIS-FEACG;
CALL DATA REGISTRATION AT ATTENDANT CONSOLE : ACTIVATED;

CDRCDUMP
CALL DATA REGISTRATION ON ADD. DEVICE, IMMEDIATE OUTPUT : ACTIVATED;
CDRFAST
CALL DATA REGISTRATION ON ADDITIONAL DEVICE, CALL UP : DEACTIVATED;
CALL DATA REGISTRATION PER STATION, PRINTER OUTPUT : ACTIVATED;

DISPLAY COMPLETED;
A31003-H3460-M104-4-76A9, July 2012


DISPLAY-SELG;
DIS-SELG;
+==============================================================================+
+------------------------------------------------------------------------------+
| |
| |
| RESOP : |
| |
+==============================================================================+
+==============================================================================+
+------------------------------------------------------------------------------+
| |
| |
| RESOP : |
| |
+==============================================================================+
+==============================================================================+
+------------------------------------------------------------------------------+
| |
| |
| RESOP : |
| |
+==============================================================================+
+==============================================================================+
+------------------------------------------------------------------------------+
| |
| OPERATING STATE : OFF_WITHOUT_QUEUEING |
| |
| RESOP : |
| |
+==============================================================================+
DISPLAY COMPLETED;
A31003-H3460-M104-4-76A9, July 2012

H04: ELEMENT CDRFAST IS ONLY SET IF ELEMENTS CDRCDIS, CDRATND AND CDRSPR
ARE NOT SET
ADD NOT COMPLETED;
A31003-H3460-M104-4-76A9, July 2012


DELETE COMPLETED;
A31003-H3460-M104-4-76A9, July 2012

DISPLAY-FEACG;
DIS-FEACG;
CALL DATA REGISTRATION ON ADD. DEVICE, IMMEDIATE OUTPUT : ACTIVATED; CDRCDUMP

CDRFAST

DISPLAY COMPLETED;
A31003-H3460-M104-4-76A9, July 2012


ADD-FEACG:CDRFAST;
H05: FAST MODE IN PROGRESS. ALL SELECTION GROUPS, EXCEPT THE FIRST ONE,
ARE SWITCHED OFF
ADD COMPLETED;
A31003-H3460-M104-4-76A9, July 2012

DISPLAY-FEACG;
DIS-FEACG;
CALL DATA REGISTRATION ON ADD. DEVICE, IMMEDIATE OUTPUT : ACTIVATED;

CDRCDUMP
CDRFAST
CALL DATA REGISTRATION ON FAST OUTPUT DEVICE : ACTIVATED;

DISPLAY COMPLETED;
A31003-H3460-M104-4-76A9, July 2012


H05: FAST MODE IN PROGRESS. ALL SELECTION GROUPS, EXCEPT THE FIRST ONE,
ARE SWITCHED OFF
ADD COMPLETED;
A31003-H3460-M104-4-76A9, July 2012

DISPLAY-SELG;
DIS-SELG;
+==============================================================================+
+------------------------------------------------------------------------------+
| |
| |
| RESOP : |
| |
+==============================================================================+
DISPLAY COMPLETED;
A31003-H3460-M104-4-76A9, July 2012


ADD-SELG:TBL=SELG,SELGNO=1,RESOP=Y,BASDEV=FT,RESDEV=FT,BLBAS=1,BL-
RES=1;
ADD COMPLETED;
A31003-H3460-M104-4-76A9, July 2012

DISPLAY-SELG;
DIS-SELG;
+==============================================================================+
+------------------------------------------------------------------------------+
| |
| |
| RESOP : Y |
| RESDEV : FT BLRES : 1 |
| |
+==============================================================================+
DISPLAY COMPLETED;
A31003-H3460-M104-4-76A9, July 2012


DISPLAY-COT:;
DISPLAY-COT:;
H500: AMO COT STARTED
COT: 0 INFO:
...
COT: 22 INFO:
DEVICE: INDEP SOURCE: DB
PARAMETER:
TRUNK SIGNALING ANSWER ANS
KNOCKING OVERRIDE POSSIBLE KNOR
CALL EXTEND FOR BUSY, RING OR CALL STATE CEBC
NETWORKWIDE AUTOMATIC CALLBACK ON FREE CBFN
NETWORKWIDE CALL FORWARDING PERMITTED FWDN
NETWORKWIDE FORWARDING NO-ANSWER FNAN
REGENERATED CO DIALTONE ON OUTGOING SEIZURE COTN
REGISTRATION OF IMPLAUSIBLE EVENTS IEVT
DON'T RELEASE CALL TO BUSY HUNT GROUP BSHT
SEND NO NODE NUMBER TO PARTNER LWNC
NO TONE NTON
COT: 23 INFO:
...
...
AMO-COT -111 CLASS OF TRUNK FOR CALL PROCESSING
DISPLAY COMPLETED;
A31003-H3460-M104-4-76A9, July 2012

DISPLAY-TDCSU:1-1-103-0;
You need to activate the ICZL parameter for all trunk groups to be metered. (Interrogate via
DISPLAY-COT). Provided that the PEN is known you can interrogate the COT number using
DISPLAY-TDCSU:
DISPLAY-TDCSU:PEN1=1-1-103-0;
H500: AMO TDCSU STARTED
+------------------------ DIGITAL TRUNK (FORMAT=L) -------------------------+
| DEV = S2CONN PEN = 1-01-103-0 |
|---------------------------------------------------------------------------|
| COTNO = 22 COPNO = 0 DPLN = 0 |
| ITR = 0 COS = 23 LCOSV = 1 |
| LCOSD = 1 CCT = DESTNO = 0 |
| PROTVAR = ECMAV2 SEGMENT = 8 TCHARG = N |
| SUPPRESS = 0 DGTPR = CHIMAP = N |
| ISDNCC = ISDNAC = ISDNLC = |
| ISDNIP = ISDNNP = |
| PNPL2C = PNPL1C = PNPLC = |
| PNPL2P = PNPL1P = PNPAC = |
| TRACOUNT = 31 SATCOUNT = MANY NNO = 1 -1 -201 |
| ALARMNO = 0 FIDX = 1 CARRIER = 1 |
| ZONE = EMPTY COTX = 22 FWDX = 1 |
| DOMTYPE = DOMAINNO = TPROFNO = |
| INIGHT = |
| CCHDL = UUSCCX = 16 UUSCCY = 8 |
|---------------------------------------------------------------------------|
| TGRP = 231 SRCHMODE = DSC BCNEG = N |
| BCGR = 1 INS = Y LWPAR = 3 |
| LWPP = 0 LWLT = 0 LWPS = 0 |
| LWR1 = 0 LWR2 = 0 |
| BCHAN 1 && 30 |
| |
+---------------------------------------------------------------------------+
AMOUNT OF B-CHANNELS IN THIS DISPLAY-OUTPUT: 30
AMO-TDCSU-111 DIGITAL TRUNKS
DISPLAY COMPLETED;
Use DISPLAY-COT to check whether the relevant ICZL parameter is set:

DISPLAY-COT:COTNO=22;
COT: 22 INFO:
DEVICE: INDEP SOURCE: DB
PARAMETER:
TRUNK SIGNALING ANSWER ANS
KNOCKING OVERRIDE POSSIBLE KNOR
CALL EXTEND FOR BUSY, RING OR CALL STATE CEBC
NETWORKWIDE AUTOMATIC CALLBACK ON FREE CBFN
NETWORKWIDE CALL FORWARDING PERMITTED FWDN
NETWORKWIDE FORWARDING NO-ANSWER FNAN
REGENERATED CO DIALTONE ON OUTGOING SEIZURE COTN
REGISTRATION OF IMPLAUSIBLE EVENTS IEVT
DON'T RELEASE CALL TO BUSY HUNT GROUP BSHT
SEND NO NODE NUMBER TO PARTNER LWNC
NO TONE NTON
DISPLAY COMPLETED;
next
A31003-H3460-M104-4-76A9, July 2012


Use CHANGE-COT to set the ICZL parameter:
H07: CHANGED COT STILL LINKED WITH FOLLOWING TRUNKS:
COT TRUNK BCGR DEVICE
-----------------------------------
22 1- 1-103- 0 1 S2CONN
1- 1-103- 1 1 S2CONN
1- 1-103- 2 1 S2CONN
1- 1-103- 2 2 S2CONN
1- 1-103- 2 3 S2CONN
1- 4- 25- 0 1 S2CONN
1- 4- 55- 0 1 S2CONN
1- 4- 25- 0 2 S2CONN
1- 4- 55- 0 2 S2CONN
-----------------------------------
H06: COT 22 CHANGED
CHANGE COMPLETED;
A31003-H3460-M104-4-76A9, July 2012

Use CHANGE-LDAT to set the WCHREG attribute for the "Voice" service:
(Use DISPLAY-TDCSU to interrogate the trunk group number.)
H500: AMO LDAT STARTED
H03: LRTEL 1 FOR LROUTE 231 WAS CHANGED
AMO-LDAT -111 LCR-DIRECTIONS
CHANGE COMPLETED;
A31003-H3460-M104-4-76A9, July 2012


DISPLAY-FEASU;
Use DISPLAY-FEASU to interrogate the CDRIC, CDROGNW, CDROGTR and CDRINH fea-
tures:
DIS-FEASU;
H500: AMO FEASU STARTED
ACTIVATED FEATURES
LDME SPDC SPDI HTVCE HTTTX HTFAX HTVTX HTDTE

FWDVCE FWDTTX FWDF FWDVTX FWDDTE OVR FRKN NIGHT
COSXCD COSXKEY DCOSX COSXATND ICPTDID HOTRCL DND TCR
CONF3 VARCONF PRESCONF BROAD TRACE SNR RKNOVR CBK
DSS SPLIT ONHKTRNS PU RSVCO SER CDRATND CQPRI
ISTR RNG LEDSIGN RELOCATE PININT NX64 TIMEDREM CLIP
DEACTIVATED FEATURES
CRITM SUPV ATNDCOSX COSXT COSXDP RPTAL CDRSAT DDTES

DVTXS NCDTE NCVTX NOCHRG DOA STAT TELM WTATND
TRACCO VMSDP RELCON RERING AUTOV EMOVR EMRLS DCBB
DCBNOA SYNCANN CDRINH CDRIC CDROGNW CDROGTR DISCHINH DISCHNW
DISCHTR LCRET POSTBUSY POSTFREE VOICO HTNW PINNW ATTR
ECFW CPS INCPRIO XFBACALL XFBADIAL CALOGOPT CDRE DIRCPCKP
AMO-FEASU-111 CUSTOMER FEATURE LIST
DISPLAY COMPLETED;
Use CHANGE-FEASU to activate the CDRIC, CDROGNW, CDROGTR and CDRINH features:
CHANGE-FEASU:TYPE=A,CM=CDRIC&CDRINH&CDROGNW&CDROGTR;
CHANGE COMPLETED;
next
A31003-H3460-M104-4-76A9, July 2012

DISPLAY-FEASU;
To double-check, you can interrogate the features once again:

DIS-FEASU;
ACTIVATED FEATURES
LDME SPDC SPDI HTVCE HTTTX HTFAX HTVTX HTDTE

FWDVCE FWDTTX FWDF FWDVTX FWDDTE OVR FRKN NIGHT
COSXCD COSXKEY DCOSX COSXATND ICPTDID HOTRCL DND TCR
CONF3 VARCONF PRESCONF BROAD CDRSAT TRACE SNR RKNOVR
CBK DSS SPLIT ONHKTRNS PU RSVCO SER CDRATND
CQPRI ISTR RNG LEDSIGN CDRINH CDRIC CDROGNW CDROGTR
RELOCATE PININT NX64 TIMEDREM CLIP
DEACTIVATED FEATURES
CRITM SUPV ATNDCOSX COSXT COSXDP RPTAL DDTES DVTXS

NCDTE NCVTX NOCHRG DOA STAT TELM WTATND TRACCO
VMSDP RELCON RERING AUTOV EMOVR EMRLS DCBB DCBNOA
SYNCANN DISCHINH DISCHNW DISCHTR LCRET POSTBUSY POSTFREE VOICO
HTNW PINNW ATTR ECFW CPS INCPRIO XFBACALL XFBADIAL
CALOGOPT CDRE DIRCPCKP
DISPLAY COMPLETED;
A31003-H3460-M104-4-76A9, July 2012



How to set up selection group 1 in two steps:
ADD COMPLETED;
CHANGE-SELG:TBL=SELT,SELGNO=1,SELTABNO=1,FORMBAS=FORM01,FORMRES=FORM01,
TARIF=TARGR00,DESTCNT="A22",CDRCD=0&&99999,SERVICE=VOICE&DTE&FAX,ATNDGR=0&&15,
CTYPE=ALL,PAYPARTY=ALL,CDRC=N,CDRSTA=N,THRGCON=N,NSTAT=N,SECTION=N,CDCHU=N,
CDRAC=N,SFSETUP=N,CDBAD=N,CDRULTE=N,CONNT=N,PCODE=N,PPCF=N,STATAB1=N,
STATAB2=N,DNOTBL1=N,DNOTBL2=N,CDRULT=0,CONNTL=000000,LEVEL0=0&&999,
LEVEL1=0&&254,LEVEL2=0&&30,TIELINE=N,EXPENS=N,CONNTYP=ALL,COPIN=0&&8,
CARRIER=0&&9;
CHANGE COMPLETED;
A31003-H3460-M104-4-76A9, July 2012

DISPLAY-SELS;
Use DISPLAY-SELS to interrogate the status of the selection group:
DIS-SELS;
OPERATING CONDITIONS OF THE SELECTION GROUPS
SELGRNO OPERATING CONDITION
1 OFF
2 OFF
3 OFF
4 OFF
DISPLAY COMPLETED;
Use ACTIVATE-SELS to activate the selection group:

ACTIVATE COMPLETED;
A31003-H3460-M104-4-76A9, July 2012



ftp> open 1.85.31.2
Verbindung mit 1.85.31.2 wurde hergestellt.
220- This system is monitored and evidence of criminal activity may be

220- reported to law enforcement officials.
220-
220-
220 HiPath FTP server ready
Benutzer (1.85.31.2:(none)): engr
331 Password required for engr.
Kennwort:
230 User engr logged in.
ftp> cd /var/col/data/ftbl
250 CWD command successful.
ftp> pwd
257 "/var/col/data/ftbl" is current directory.
ftp> lcd c:\ftbl
Lokales Verzeichnis jetzt C:\ftbl
ftp> bin
200 Type set to I.
ftp> mget *
200 Type set to I.
mget AM1.5_R6.5+6.6.EN? y
200 PORT command successful.
150 Opening BINARY mode data connection for AM1.5_R6.5+6.6.EN (923 bytes).
226 Transfer complete.
FTP: 923 Bytes empfangen in 0,01Sekunden 92,30KB/s
...
mget AMO_TEXT_AMPM_EV3.0.GER? y
150 Opening BINARY mode data connection for AMO_TEXT_AMPM_EV3.0.GER (12804 bytes).
mget AMO_TEXT_AMPM_UV1.0.ENG? y
150 Opening BINARY mode data connection for AMO_TEXT_AMPM_UV1.0.ENG (11791 bytes).
mget AMO_TEXT_AMPM_UV1.0.GER? y
150 Opening BINARY mode data connection for AMO_TEXT_AMPM_UV1.0.GER (14191 bytes).
...
mget AMPM_EV3.0.GE? y
150 Opening BINARY mode data connection for AMPM_EV3.0.GE (3881 bytes).
A31003-H3460-M104-4-76A9, July 2012

...
mget AMPM_UV1.0.EN? y
150 Opening BINARY mode data connection for AMPM_UV1.0.EN (3589 bytes).
mget AMPM_UV1.0.GE? y
150 Opening BINARY mode data connection for AMPM_UV1.0.GE (3599 bytes).
...
mget PM_UV1.0.GE? y
150 Opening BINARY mode data connection for PM_UV1.0.GE (2836 bytes).
ftp> bye
221-You have transferred 240352 bytes in 50 files.
221-Total traffic for this session was 250060 bytes in 51 transfers.
221-Thank you for using the FTP service on D7C001.
221 Goodbye.
A31003-H3460-M104-4-76A9, July 2012



ftp> open 139.21.137.39

220-
220-
Kennwort:
ftp> cd /opt/bin/tools
ftp> lcd c:\ftbl
Lokales Verzeichnis jetzt C:\ftbl
ftp> bin
200 Type set to I.
ftp> get TG_usage.zip
150 Opening BINARY mode data connection for TG_usage.zip (342407 bytes).
ftp> bye
221-Thank you for using the FTP service on server.
221 Goodbye.
A31003-H3460-M104-4-76A9, July 2012


ftp> open 139.21.137.39

220-
220-
Kennwort:
ftp> cd /home/engr
ftp> lcd C:\ftbl\TG_usage
Lokales Verzeichnis jetzt C:\ftbl\TG_usage
ftp> put LOAD_FILE.XIE

150 Opening ASCII mode data connection for LOAD_FILE.XIE.
FTP: 462 Bytes gesendet in 0,00Sekunden 462000,00KB/s
ftp> bye
221-Thank you for using the FTP service on server.
221 Goodbye.
A31003-H3460-M104-4-76A9, July 2012


Connecting via Telnet (1)

login: engr
Password:
Open UNIX 8.0.0
server
Copyright (c) 1976-2001 Caldera International, Inc. and its suppliers.
All Rights Reserved.
RESTRICTED RIGHTS LEGEND:
When licensed to a U.S., State, or Local Government, all Software

produced by Caldera International is commercial computer software as
defined in FAR 12.212, and has been developed exclusively at private
expense. All technical data, or Caldera International commercial
computer software/documentation is subject to the provisions of
FAR 12.211 - "Technical Data", and FAR 12.212 - "Computer Software"
respectively, or clauses providing Caldera International equivalent
protections in DFARS or other agency specific regulations.
Manufacturer: Caldera International, Inc.,
240 West Center Street, Orem, UT 84057.
Last login: Thu Feb 20 12:53:38 2003 on pts004
You have mail

# cd /opt/informix
# . ./ids_env_var
# dbaccess
DBACCESS: Query-language Connection Database Table Session Exit

Use SQL query language.
------------------------------------------------ Press CTRL-W for Help --------
SELECT DATABASE >>

Select a database with the Arrow Keys, or enter a name, then press Return.
------------------------------------------------ Press CTRL-W for Help --------
cdb@online
logmdb@online
sysmaster@online
sysutils@online
SQL: New Run Modify Use-editor Output Choose Save Info Drop Exit
Enter new SQL statements using SQL editor.
----------------------- cdb@online ------------- Press CTRL-W for Help --------
NEW: ESC = Done editing CTRL-A = Typeover/Insert CTRL-R = Redraw

CTRL-X = Delete character CTRL-D = Delete rest of line
A31003-H3460-M104-4-76A9, July 2012

load from "/home/engr/LOAD_FILE.XIE" insert into col_trunk
28 row(s) loaded.
SQL: New Run Modify Use-editor Output Choose Save Info Drop Exit
Run the current SQL statements.
DBACCESS: Query-language Connection Database Table Session Exit

Use SQL query language.
Database closed
A31003-H3460-M104-4-76A9, July 2012


Example for setting up line trunk group 99 in the trunk group table:
H500: AMO FBTN STARTED
AMO-FBTN -111 ADMINISTRATION OF THE FLAG BYTE AND TRUNK NUMBER TABLES
ADD COMPLETED;
Click here to see an example of the corresponding query.
A31003-H3460-M104-4-76A9, July 2012

DISPLAY-FBTN:TAB=TN;
Example for interrogating the trunk number table:
DISPLAY-FBTN:TBL=TRKNO;
DISPLAY-FBTN:TBL=TRKNO;
H500: AMO FBTN STARTED
TRUNK-NUMBER-TABLE
ENTRY LTG LTU SLOT CCT ISDN-B-CHANNEL VIRT.TRUNK CIRC. NO
1 1 2 55 0 1 -2 01025500
2 1 2 55 1 1 -2 01025501
3 1 2 55 2 1 -2 01025502
4 1 2 55 3 1 -2 01025503
5 1 2 55 4 1 -2 01025504
6 1 2 55 5 1 -2 01025505
7 1 2 55 6 1 -2 01025506
8 1 2 55 7 1 -2 01025507
9 99 1 1 1 0 99999
10 99 1 1 1 1 111111
AMO-FBTN -111 ADMINISTRATION OF THE FLAG BYTE AND TRUNK NUMBER TABLES
DISPLAY COMPLETED;
A31003-H3460-M104-4-76A9, July 2012


Examples: B01 - B71
9.2 Examples: B01 - B71

Example: B01
Example: B02
Example: B03
Example: B04
Example: B05
Example: B06
Example: B07
Example: B08
Example: B09
Example: B10
Example: B11
Example: B12
Example: B13
Example: B14
Example: B15
Example: B16
Example: B17
Example: B18
Example: B19
Example: B20
Example: B21
Example: B22
Example: B23
Example: B24
Example: B25
Example: B26
Example: B27
A31003-H3460-M104-4-76A9, July 2012

Examples: B01 - B71
Example: B28
Example: B29
Example: B30
Example: B31
Example: B32
Example: B33
Example: B34
Example: B35
Example: B36
Example: B37
Example: B38
Example: B39
Example: B40
Example: B41
Example: B42
Example: B43
Example: B44
Example: B45
Example: B46
Example: B47
Example: B48
Example: B49
Example: B50
Example: B51
Example: B52
Example: B53
Example: B54
Example: B55
A31003-H3460-M104-4-76A9, July 2012


Examples: B01 - B71
Example: B56
Example: B57
Example: B58
Example: B59
Example: B60
Example: B61
Example: B62
Example: B63
Example: B64
Example: B65
Example: B66
Example: B67
Example: B68
Example: B69
Example: B70
Example: B71
A31003-H3460-M104-4-76A9, July 2012

Examples: B01 - B71
Example: B01
Example: B02
A31003-H3460-M104-4-76A9, July 2012


Examples: B01 - B71
Example: B03
Example: B04
A31003-H3460-M104-4-76A9, July 2012

Examples: B01 - B71
Example: B05
Example: B06
A31003-H3460-M104-4-76A9, July 2012


Examples: B01 - B71
Example: B07
Example: B08
A31003-H3460-M104-4-76A9, July 2012

Examples: B01 - B71
Example: B09
Example: B10
A31003-H3460-M104-4-76A9, July 2012


Examples: B01 - B71
Example: B11
Example: B12
A31003-H3460-M104-4-76A9, July 2012

Examples: B01 - B71
Example: B13
zurück
Example: B14
Example: B15
A31003-H3460-M104-4-76A9, July 2012


Examples: B01 - B71
Example: B16
Example: B17
A31003-H3460-M104-4-76A9, July 2012

Examples: B01 - B71
Example: B18
Click here to start an MML

session.
Click here to start a

HiPath 4000 Expert Access
(ComWin) File Transfer
session.
Example: B19
A31003-H3460-M104-4-76A9, July 2012


Examples: B01 - B71
Example: B20
A31003-H3460-M104-4-76A9, July 2012

Examples: B01 - B71
Example: B21
Using COPY-DAGR; the

FT_FILE_INTERN is cop-
ied to the file FTFILE.
Example: B22
A31003-H3460-M104-4-76A9, July 2012


Examples: B01 - B71
Example: B23
Example: B24
Collecting Agent is auto-

matically installed on the
HiPath 4000 Manager
but not on the Assistant.
A31003-H3460-M104-4-76A9, July 2012

Examples: B01 - B71
Example: B25
Example: B26
A31003-H3460-M104-4-76A9, July 2012


Examples: B01 - B71
Example: B27
Example: B28
A31003-H3460-M104-4-76A9, July 2012

Examples: B01 - B71
Example: B29
Example: B30
Example: B31
A31003-H3460-M104-4-76A9, July 2012


Examples: B01 - B71
Example: B32
Example: B33
Example: B34
A31003-H3460-M104-4-76A9, July 2012

Examples: B01 - B71
Example: B35
Example: B36
A31003-H3460-M104-4-76A9, July 2012


Examples: B01 - B71
Example: B37
Example: B38
A31003-H3460-M104-4-76A9, July 2012

Examples: B01 - B71
Example: B39
Select the input

format that you
defined with the
AMO FTBL for
this system.
Activate this field
in order that COL
enters the perfor-
mance data into
the database.
Enter the phys-

ical node num-
ber retrieved
using the AMO
ZAND and
modify the oth-
er values if
needed.
A31003-H3460-M104-4-76A9, July 2012


Examples: B01 - B71
Example: B40
Example: B41
Example: B42
A31003-H3460-M104-4-76A9, July 2012

Examples: B01 - B71
Example: B43
Example: B44
A31003-H3460-M104-4-76A9, July 2012


Examples: B01 - B71
Example: B45
If the status in the Transfer Status column is set to

"Error" this means that a transfer problem has oc-
curred.
If the status in the Transform Status column is set to
"Error" this means that the COL input format and the
FORM table of the selection group (see FTBL file)
are not identical. The data will then be stored as "in-
correct records" and can be re-sent to the input or
deleted after the COL input format has been correct-
Example: B46
A31003-H3460-M104-4-76A9, July 2012

Examples: B01 - B71
Example: B47
Example: B48
A31003-H3460-M104-4-76A9, July 2012


Examples: B01 - B71
Example: B49
Example: B50
A31003-H3460-M104-4-76A9, July 2012

Examples: B01 - B71
Example: B51
Example: B52
Select the objects to be metered (extensions, external lines, trunk groups etc.) in the left hand
side pane and move the selected objects to the right hand side pane by clicking the ">" button.
next
A31003-H3460-M104-4-76A9, July 2012


Examples: B01 - B71
Example: B53
Example: B54
next
A31003-H3460-M104-4-76A9, July 2012

Examples: B01 - B71
Example: B55
next
Example: B56
next
A31003-H3460-M104-4-76A9, July 2012


Examples: B01 - B71
Example: B57
next
Example: B58
next
A31003-H3460-M104-4-76A9, July 2012

Examples: B01 - B71
Example: B59
next
Example: B60
A31003-H3460-M104-4-76A9, July 2012


Examples: B01 - B71
Example: B61
Example: B62
A31003-H3460-M104-4-76A9, July 2012

Examples: B01 - B71
Example: B63
Example: B64
A31003-H3460-M104-4-76A9, July 2012


Examples: B01 - B71
Example: B65
Example: B66
A31003-H3460-M104-4-76A9, July 2012

Examples: B01 - B71
Example: B67
Example: B68
A31003-H3460-M104-4-76A9, July 2012


Examples: B01 - B71
Example: B69
Example: B70
A31003-H3460-M104-4-76A9, July 2012

Examples: B01 - B71
Example: B71
A31003-H3460-M104-4-76A9, July 2012


Examples: S01 - S20
9.3 Examples: S01 - S20

Example: S01
Example: S02
Example: S03
Example: S04
Example: S05
Example: S06
Example: S07
Example: S08
Example: S09
Example: S10
Example: S11
Example: S12
Example: S13
Example: S14
Example: S15
Example: S16
Example: S17
Example: S18
Example: S19
Example: S20
A31003-H3460-M104-4-76A9, July 2012

Examples: S01 - S20
Example: S01
Example: S02
A31003-H3460-M104-4-76A9, July 2012


Examples: S01 - S20
Example: S03
Example: S04
Example: S05
A31003-H3460-M104-4-76A9, July 2012

Examples: S01 - S20
Example: S06
Example: S07
Example: S08
A31003-H3460-M104-4-76A9, July 2012


Examples: S01 - S20
Example: S09
Example: S10
Example: S11
A31003-H3460-M104-4-76A9, July 2012

Examples: S01 - S20
Example: S12
Example: S13
A31003-H3460-M104-4-76A9, July 2012


Examples: S01 - S20
Example: S14
Example: S15
A31003-H3460-M104-4-76A9, July 2012

Examples: S01 - S20
Example: S16
Example: S17
A31003-H3460-M104-4-76A9, July 2012


Examples: S01 - S20
Example: S18
next
Example: S19
A31003-H3460-M104-4-76A9, July 2012

Examples: S01 - S20
Example: S20
A31003-H3460-M104-4-76A9, July 2012


Examples: S01 - S20
A31003-H3460-M104-4-76A9, July 2012

h2h_en.fm
Nur für den internen Gebrauch Using the Help
Layout
10 Using the Help
10.1 Layout
The Help is displayed in a Web browser and is split into the three areas shown below:
Navigation Toolbar Topic
Navigation
The navigation area is displayed at the left of the browser window and contains the following
tabs:
A31003-H3460-M104-4-76A9, July 2012

h2h_en.fm
Using the Help Nur für den internen Gebrauch

Layout
● Contents tab
The Contents tab displays all topics relevant to the Help. Click the “+” or “-” icon, respec-
tively, to expand or collapse the subtopics. Click any entry to display the relevant topic in
the Topic area.
● Index tab
Click the Index tab to view all index entries. An alphabetical list of keywords for each topic
is displayed. Click any index entry to display the relevant topic.
● Search tab
Click the Search tab to search for a word or phrase. Enter the search term and click Go.
If you do not know the exact word or phrase, you can enter a star "*" before or after the
term. Click any search result entry to display the relevant topic. (For details see "Searching
Within the Help").
Contents
The Contents include entries from the FrameMaker TOC (English) or IVZ (German) file. The
individual topics can be expanded or collapsed. If no H2 title follows, a page icon appears in-
stead of the “+” or “-” icon.
Index
The Index contains entries from the FrameMaker IX (English) or SIX (German) file. The index
entries are either shown collectively or appear under individual letters of the alphabet in cases
where there are several index entries associated with an alphabet.
Search
One or more search terms can be specified. The section titles of the corresponding search re-
sults are displayed. Clicking / double-clicking on a topic opens that topic and shows the search
results with the search terms highlighted. The ranking entries for the individual search results
reflect the frequency of hits as a percentage. When searching a multi-volume, the book title ap-
pears in addition to the section titles.
Favorites (only with Java)

The user can add links to frequently visited pages to his or her Favorites (only possible with
Java)
Toolbar
The toolbar is displayed at the top of the browser window and contains the following buttons:
A31003-H3460-M104-4-76A9, July 2012

h2h_en.fm
Layout
● Display in Contents
Click this button to synchronize the contents currently displayed in the Topic area with the
list of contents. If you navigate through the Topic area with the "Previous Topic" or "Next
Topic" buttons, you can use the "Display in Contents" button to display the relevant topic
entry in the list of contents.
● Previous Topic
Click this button to revert to the previous related topic. By contrast, click the "Back" button
of the browser to revert to the last topic viewed.
● Next Topic
Click this button to jump to the next related topic.
● Print
Click this button to print the topic currently displayed in the Topic area. (For details see
"Printing Help Topics").
Topic
The Topic area is at the right of the browser window and displays the information on the select-
ed topics.
The browser’s caption displays the title of the current Help page.
A31003-H3460-M104-4-76A9, July 2012

h2h_en.fm

Overview of Key Functions
10.2 Overview of Key Functions

● Key combination h + .
You can use this key combination to switch between the Help and the application.
● Text highlighted in blue (links )
Within a Help topic, you can click a link (text highlighted in blue) to obtain further informa-
tion about the topic. This information is displayed in the Topic area as well.
● Popup windows
Within a Help topic, you can click a link (text highlighted in blue - bold) to obtain further or
more detailed information in an additional window (popup). These popup windows are dis-
played in the lower left corner by default.
If you click another popup link while a popup window is open, the contents of the popup
window will be changed accordingly.
A popup remains displayed until it is closed or the entire Help is closed.
● Drop down text
If you click on text identified with the icon within a Help topic, a drop down text box con-
taining additional information will open under the text. Click the icon again to collapse this
text box.
To collapse all drop down text boxes in a Help topic, click the browser’s Refresh button.
● Start page
Click the first entry in the table of contents to open the start page for the Help. The start
page may contain the following information about the open Help:
– Title of the Help
– Help ID number
– Link to HTML download
– Link to PDF download
– Link to Feedback
– Version number and release date of the Help
A31003-H3460-M104-4-76A9, July 2012

h2h_en.fm
How to Use the Help
10.3 How to Use the Help

You can use the following functions to navigate the Help system:
● Open the Help Window
● Searching Within the Help
● Printing Help Topics
● Key Combinations in the Help
10.3.1 Open the Help Window

There are different ways of opening the Help depending on the application.
Display the Help topics

● Open the contents of the integrated Help by using the Help menu in the application.
Or
● Left-click the Help icon in the application toolbar to open the content of the Help.
Or (if implemented)
● Left-click the Help icon or the Help button in the application window.
Context-sensitive help for a window (if implemented)

● Press key A if you require information about a window.
Context-sensitive help for an element (if implemented)

● Select an element (field, button, tab, etc.) in the user interface and press the $ + A
keys to open the context-sensitive help.
Or
● Open the context-sensitive help by using the Help menu in the application.
Or
● Left-click the Help icon in the application toolbar.
The cursor will become a question mark .
Now click an element (field, button, tab, etc.) in the user interface to view the relevant Help
text.
A31003-H3460-M104-4-76A9, July 2012

h2h_en.fm

How to Use the Help
10.3.2 Searching Within the Help

The Help has an integrated full-text search function which makes it easy for you to find the in-
formation you need.
1. To search for a word or phrase, click the Search tab in the Navigation area on the left.
2. Enter the search term in the input field. To optimize the search, you can search for several
words at the same time. If you do not know the exact word or phrase, you can insert an
asterisk "*" before or after the term.
Spaces between words are interpreted as AND operators (see examples).
The search is not case-sensitive.
Examples
Te*
This will display all topics containing a phrase beginning with the letters Te... or te..., such
as text, teleworking, telephone, telephone connection, Telephone Connection, etc.
Find text
This will display all topics containing the word find or text or both.
3. If the Help consists of several books, you can optionally select a specific book.
In this case a drop down list showing the names of all books will be displayed. The prese-
lected option in this drop down list is All available books. If you select this entry, the
search is run in all available books. The search result displayed indicates the source
(book).
4. Click the Start button to initiate the search.
5. Click an entry in the list of search results (in the Title column) to display the required topic.
The more often the search term occurs on the page, the higher its priority will be. Results
also have priority if the search term occurs in the heading.
The title shows the heading of the chapter in which the term occurs.
The book in which the term occurs is displayed last.
You can also use your browser’s (Ì + F) search function to run a search
> within a Help topic.
A31003-H3460-M104-4-76A9, July 2012

h2h_en.fm
How to Use the Help
10.3.3 Printing Help Topics

● Right-click the topic you want to print and click the Print button.
Or
● Click the Print icon in the toolbar.
Or
● Press the Ì + P keys.
Popup windows:
>
●
To print the contents of a popup Help topic, right-click anywhere in the popup
window and click Print topic.
● Drop down list:
If you wish to print the information displayed in dropdown text, it must be visible.
Be sure to open the desired drop down text boxes prior to printing the topic.
10.3.4 Key Combinations in the Help
Key combinations Action

ALT+TAB Switch between the Help and other open windows.
TAB Jump to the next link within a Help topic.
SHIFT+TAB Revert to the previous link within a Help topic.
F5 Refresh the display.
CTRL+POS1 Go to the top of the page.
CTRL+END Go to the end of the page.
CTRL+A Select all the text in a window.
CTRL+F Search within a Help topic.
CTRL+P Print a topic.
ALT+left arrow Revert to the previously displayed topic.
ALT+right arrow Go to the next (previously displayed) topic.
ALT+F4 Close the Help.
A31003-H3460-M104-4-76A9, July 2012

h2h_en.fm

How to Use the Help
A31003-H3460-M104-4-76A9, July 2012

HiPath_COLSIX.fm
Nur für den internen Gebrauch Index
Index Z SELG 1-35

BUILDING 6-186
C
Call Data Collection (COL) Tab Sheet in Sy-
A stem Management 3-35
ACCOUNT 6-186 CALLIPTY 6-187
ACCTCODE 4-26, 4-27 CDR collecting
Adapting Supported system types 2-2
FTBL 1-32 CDR output fields 4-84
Adding a System in HiPath 4000 Manager/ CDR output files for AM 2-1
Assistant System Management 5-12 CDR output filter 2-1
Adding a System in HiPath COL System Ma- CHARGEID 6-186
nagement chart form
Output format mapping 5-11 xml and csv restrictions 4-106
Adding a system in HiPath COL System Ma- CM elements
nagement 5-11 Additional 6-185
Additional CM elements Description 6-185
For defining CDR output formats 6-185 In CDR output files 6-185
Additional CM records In output file 5-26
For CDR output formats 6-185 Reference to CM tables 6-185
AllServe Used as filter criteria 6-185
Input format 6-142 CM history records
AMO DAGR 1-27 For output files 6-185
AMPM_UV1.0 CM records
Input format 6-139 Used in output formats 6-185
AM-WIN 1.0 CM tables
Output format 6-98 For CDR output files 6-185
AM-WIN 2.0 CMVERSION 6-186
Element table 6-100 COL
Output format 6-100 Languages 2-3
Output format from system 300 for AM- Main functional areas 3-1
WIN 2.0 6-100 Supported system types 2-2
Application Tree 3-12, 4-3, 5-6, 6-9 COL Administration
AREACODE 6-186 COL System Management 3-52
Assigning formats to an input line 5-23 tab sheet in System Management 3-36
Attendant Consoles COL Features 3-21
tab sheet in System Management 3-43 COL features
Automatic copying Links on COL Home Page 3-7
FT_INTERN_FILE 1-28 COL Home Page 5-2
B Home Page 3-7
COL home page
Backup PC 3-26
Icons 3-10
BANKCODE 6-186
Toolbar 3-10
Block size
A31003-H3460-M104-4-76A9, July 2012

Collecting Agent / HiPath COL, Help Z-1
HiPath_COLSIX.fm
Index Nur für den internen Gebrauch
COL Home Page icon 3-10, 6-8 Configuration Examples 7-1

COL Paths, tab sheet Default Filter
Options 3-109 Output format 5-24
COL Scenarios 2-2 Defining input and output formats
COL System Management Elements 6-49
COL Administration 3-52 Pre-defined formats 6-97
Communication Parameter 3-54 Defining input formats 6-138
ISDN Access Codes 3-56 Definition of Input Lines
Object List 3-34, 3-50 Adding a System 5-12
COL System Management dialog COL System Management dialog 3-31
Definitino of Input Lines 3-31 DOMAIN 6-187
COL-Funktionen 5-3 drop down text 10-4
Collect now 3-26
Collecting CDRs (HiPath COL) 2-1 E
Collecting Status 3-25 E.164 number format 3-47, 3-56
Collecting status Elements
Description 3-25 For defining input and output formats 6-49
Input lines 3-25 For input format definition 6-138
Refresh 3-25 Output format 5-26
Communication Parameter Error messages
COL System Management 3-54 PM/COL 1-12
communication parameters 5-11 Exporting log reports 3-122
COMPANY 6-186 EXTAREACOD 6-186
Configuration Examples EXTCOUCODE 6-186
HiPath COL, HiPath AM, HiPath 4000 Col- EXTNETCODE 6-186
lecting Agent 7-1 EXTTIENUM 6-186
Configure Input Element
Input Format Editor 3-70 F
Configure Output Element FAXNUMBER 6-186
Output Format Editor 3-84 Features
Connection Types COL 3-21
PM/COL 1-4 feedback 10-4
Content pane 3-14, 3-23 Field Descriptions 4-1
contents 10-3 Filter Editor 3-86
Controlling 3-23 Object List 3-89
COSTBEAR 6-186 Object view 3-86
COUNTRY 6-186 Set Default Value 3-91
csv FIRSTNAME 6-186
chart restriction 4-106 Flexible format support of CDRs 2-1
Flexible report output
D Email recipients 3-124
DAGR file locations 3-125
Notes 1-27 output format 3-123
Data Collection Flowchart
PM installation prerequisites 1-16
A31003-H3460-M104-4-76A9, July 2012
Z-2 Collecting Agent / HiPath COL, Help
HiPath_COLSIX.fm
Format assignment HiPath 4000 Manager / Assistant PM V1.0

Format change 5-23 Output format 6-105
FT_INTERN_FILE HiPath 4000 Manager/Assistant PM V1.0
Automatic copying 1-28 Output format 6-105
FTBL 5-11 HiPath 4000 Manager/Assistant Start Page
Adapting 1-32 Icon 3-11, 6-9
Output format mapping 5-11 HiPath 4000 system
FTBL AMO batches Installation 1-17
AMO batches HiPath COL
FTBL 5-19 Home Page 3-7
En_US and DE 5-19 History records
FTBL batch col_domain 6-185
Transferring 1-29 col_persdat 6-185
FTBL path col_pin 6-185
File storage location 5-19 col_switch 6-185
FTFILE 1-27 In CDR output files 6-185
FTP 1-29 Home Page 5-2
COL for HiPath 4000 3-7
G HiPath 4000 Manager/Assistant 3-11, 6-9
Getting Started HiPath COL 3-7
PM/COL Installation 1-1 Links 3-7
Home page
H Toolbar 3-10
H2000 how to use help 10-5
intput formats 6-138 HTML download 10-4
output formats 6-97
H3000 I
input formats 6-138 Icons
output formats 6-97 COL home page 3-10
H4000_HP-AM Incorrect Records
Output format 6-103 CDRs 5-38
H4000_HPAM_E164 Format mismatch 5-38
Output format 6-109 Send Back To Input 3-104
H5000_V30 Send Back to Input 3-103
Input format 6-144 Incorrect records
H8000_AM - OpenScape Voice Output For- Refresh 4-65
mat V1.0 Send back to Input 4-65
Output format 6-113 Input format
H8000_AM_V22 – OpenScape Voice Output Definition 6-138
Format V2.2 (Single System) Input format AllServe
Output format 6-115 Element table 6-142
Help icon 3-10, 6-8 For HiPath AllServe 150 V1.0 (Element
Hints Before Starting 1-2 Manager) 6-142
HiPath 4000 COL Input format AMPM_UV1.0
Home Page 3-7
A31003-H3460-M104-4-76A9, July 2012
HiPath_COLSIX.fm
Element table 6-139 key functions 10-4

For AM/PM HiPath 4000 6-139
Input format definition L
Pre-defined formats 6-138 Languages
Input Format Editor COL 2-3
Configure Input Element 3-70 Launching
Description 3-64, 4-26, 4-27 COL 3-5, 5-2
Object List 3-66 COL URL 3-5, 5-2
Object View 3-63 Launching via URL or bookmark 3-5, 5-2
Set Default Value 3-68 layout 10-1
Input format editor 3-58 links 10-4
Setting up input formats 5-19 Links on COL Home Page 3-7
Input format H5000_V30 List of network objects
Element table 6-144 System Management HiPath 4000 3-34
For HiPath 5000 V3.0 (Single System) 6- list view
144 switch to object view 3-20
Input formats LOCATION 6-186
Defining 6-97 Logging 2-1, 3-12, 3-116
Element names 5-19 Columns in error logs 5-45
Elements 6-49 Fields description 5-45
FTBL 5-19 HiPath COL 3-7
H2000 6-138
H3000 6-138 M
Mapping 5-19 mixed networks 3-47, 3-56
Modifying 5-23 Multiple selection
Pre-defined 5-19 in tables 3-15
Pre-defined formats 6-97
N
Setting up 5-19
NAME 6-186
Input lines
navigation 10-1
Collecting status 3-25
Navigation Pane 3-12, 4-3, 5-6, 6-9
Input Status 3-23
NETCODE 6-187
Installation
NODENUM 6-187
HiPath 4000 Collecting Agent 7-1
HiPath 4000 system 1-17 O
HiPath AM 7-1 Object List
HiPath COL 7-1 System Management HiPath 4000 3-34
PM 1-15 object view
Installing PM on the HiPath 4000 Manager 1- switch from list view 3-20
21 open 10-5
ISDN Access Codes 3-47, 3-56 OpenScape Voice with IPSec 7-86
COL System Management 3-56 Options 3-108
K COL Paths 3-109
Dialog 5-42
key combinations 10-7
Settings 3-111
A31003-H3460-M104-4-76A9, July 2012

HiPath_COLSIX.fm
Options - Process Controlling 3-114 Element table 6-105

ORG1-3 6-186 for HiPath 4000/HiPath 4000 Manager/As-
OSV_AM - Open Scape Voice Output Format sistant PM V1.0 6-105
Output format 6-117 Output format OSV_AM - Open Scape Voice
Output fields Output Format
CDR 4-84 Element table 6-117
Output file Output Formats
CM elements 5-26 Setting up 5-26
Text elements 5-26 Output formats
Output format Additional CM elements used in output
AM-WIN 2.0 6-100 formats 6-185
Default filter 5-24 Additional CM records 6-185
Elements 5-26 Assigning 5-24
Mapping 5-26 Elements 6-49
Mapping to an FTBL 5-11 H2000 6-97
Output line 5-24 H3000 6-97
Output format AM-WIN 1.0 from system for Pre-defined 5-26, 6-97
AM-WIN 1.0 Using CM history records 6-185
Element table 6-98 Output line
Output Format Editor 3-78 For each system type 5-24
Configure Output Element 3-84 Format mapping 5-26
Description 3-78 Output format 5-24
Object List 3-82 Output Line Definition 3-72
Object view 3-78 Description 3-73
Output format editor Object List 3-76
Output table 5-26 Output line definition
Output format from HiPath 4000 for HiPath Output filter 5-24
AM 6-103 Output formats 5-24
Output format H4000_HP-AM Output line status 3-28
Element table 6-103 Description 3-28
Output format H4000_HPAM_E164 from sy- Refresh 3-29
stem for HiPath AM Output Status 3-23
Element table 6-109 Overview 2-1
Output format H8000_AM – OpenScape
Voice Output Format V1.0 P
Element table 6-113 PAYPART 6-186, 6-187
Output format H8000_AM_V22 – OpenScape PDF download 10-4
Voice Output Format V2.2 (Single System) PERSNUM 6-186
Element table 6-115 PIN 6-187
Output format HiPath 4000 Manager / Assi- Pin 3-11, 6-9
stant PM V1.0 6-105 Sticky Page 6-7
Element table 6-105 Pin icon
Output format HiPath 4000 Manager/Assi- Sticky page 3-11, 6-9
stant PM V1.0 PM
A31003-H3460-M104-4-76A9, July 2012

HiPath_COLSIX.fm
Installation 1-15 Settings, tab sheet

PM installation prerequisites Options 3-111
Flowchart 1-16 sorting
PM restrictions 1-11 records in tables 3-18
PM/COL SORTNAME 6-186
Error messages 1-12 Start HiPath 4000 Manager/Assistant 6-9
PM/COL Connection Types 1-4 Start Page
PM/COL Installation HiPath 4000 Manager/Assistant 3-11
Getting Started 1-1 start page 10-4
Security aspects 1-14 Start/Stop Input 3-23
popup windows 10-4, 10-7 Start/Stop Output 3-23
POSITION 6-186, 6-187 Start/stop PM collecting 5-22
Pre-defined formats Starting
Assigning to output formats 6-97 COL 3-5, 5-2
Pre-defined formats for input format definition COL URL 3-5, 5-2
6-138 Step-by-step instructions 5-1
Pre-defined output formats sticky mode 3-11, 5-33, 5-36, 6-7, 6-9, 6-38,
For H150, H300 and H5000 5-26 6-42
printing 10-7 Sticky Page
Process Controlling 3-114 Pin 6-7
Sticky page
R Pin icon 3-11, 6-9
RECTYPE 1-31 Supported system types
Refresh CDR collecting 2-2
Incorrect records 4-65 SWCOUNTRY 6-187
Rejected CDRs SWITCHNAME 6-186, 6-187
Incorrect Records 5-38 SWITCHTYP 6-187
List 5-38 SYSNAME 6-187
ROOM 6-186 System Management 3-35
Run Report Dialog 3-122 Adding a system 5-12
Email 3-124 System Management HiPath 4000
Export 3-125 object ist 3-34
Output 3-123 System types supported
COL CDR collecting 2-2
S
SALUTATION 6-186 T
search 10-6 tab
Security aspects contents 10-2
PM/COL Installation 1-14 index 10-2
SELG search 10-2
Block size 1-35 Tab Sheets
Send Back to Input Call Data Collection (COL) in System Ma-
Incorrect Records 3-103, 3-104, 5-38 nagement 3-35
Set Default Value tables
Filter Editor 3-91
A31003-H3460-M104-4-76A9, July 2012
HiPath_COLSIX.fm
multiple selection 3-15

TIENUM 6-187
TITLE 6-186
Toolbar
COL home page 3-10
toolbar 10-2
topic 10-3
trables
sort records 3-18
Transferring FTBL batch from HiPath 4000
Manager to Client PC 1-29
Trunk Group/CDR
tab sheet in System Management 3-39
TRUNKACC 6-186
U
USEGROUP 6-186
User Interface 3-2
V
VIRTLV0 6-187
VIRTLV0-2 6-187
VIRTLV1 6-187
VIRTLV2 6-187
X
xml
chart restriction 4-106
Y
YCALLILV0-2 6-188
YPDESTLV0-2 6-188
YPPLV0-2 6-188
YRTINGLV0-2 6-188
YRTIONLV0-2 6-188
YTRNSFLV0-2 6-188
A31003-H3460-M104-4-76A9, July 2012

HiPath_COLSIX.fm
A31003-H3460-M104-4-76A9, July 2012


Collecting Agent HiPath COL PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Collecting Agent HiPath COL PDF

Încărcat de

Drepturi de autor:

Formate disponibile

Documentation

HiPath 4000 Assistant/Manager V6

Siemens Enterprise Communications

Copyright © Siemens Enterprise

Collecting Agent/HiPath COL - Content 0

1 PM/COL Installation Instructions -- Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

A31003-H3460-M104-4-76A9, July 2012

Collecting Agent/HiPath COL - Content Nur für den internen Gebrauch

3.3 Collecting Agent / HiPath COL - Homepage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

A31003-H3460-M104-4-76A9, July 2012

3.19 Configure Output Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-84

A31003-H3460-M104-4-76A9, July 2012

Collecting Agent/HiPath COL - Content Nur für den internen Gebrauch

A31003-H3460-M104-4-76A9, July 2012

5.15 Output Format Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26

A31003-H3460-M104-4-76A9, July 2012

Collecting Agent/HiPath COL - Content Nur für den internen Gebrauch

7.3.4 HiPath 4000 Manager Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-48

A31003-H3460-M104-4-76A9, July 2012

7.10 HiPath AM FTP Collecting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-112

A31003-H3460-M104-4-76A9, July 2012

Collecting Agent/HiPath COL - Content Nur für den internen Gebrauch

8.5 Automatic Forwarding of Alarms to Fault Management . . . . . . . . . . . . . . . . . . . . . . . . 8-6

A31003-H3460-M104-4-76A9, July 2012

1 PM/COL Installation Instructions -- Getting Started

A31003-H3460-M104-4-76A9, July 2012

1.1 Important Hints Before Starting -- Overview

A31003-H3460-M104-4-76A9, July 2012

1.1.1 HiPath 4000 Manager – Performance Management (PM)

A31003-H3460-M104-4-76A9, July 2012

1.1.2 Performance Management (PM) - Connection Types

A31003-H3460-M104-4-76A9, July 2012

1.1.3 Call Charge Data Registration

Basic Rules for Activating PM on a Switch

A31003-H3460-M104-4-76A9, July 2012

1.1.4 Data Volume

Factors to be Used with Metering Objects

Assumptions for Number of Calls per Metering Object (sample values)

A31003-H3460-M104-4-76A9, July 2012

Formula for Calculating the FTFILE Size per Day

A31003-H3460-M104-4-76A9, July 2012

1.1.5 Collecting Agent (COL)

3 HiPath 4000 Manager

A31003-H3460-M104-4-76A9, July 2012

Step 1: Determining the PM CDRs per switch

A31003-H3460-M104-4-76A9, July 2012

Step 2: Calculating the PM data storage requirements in the CDB

A31003-H3460-M104-4-76A9, July 2012

A31003-H3460-M104-4-76A9, July 2012

1.1.7 Error Messages

A31003-H3460-M104-4-76A9, July 2012

1.1.8 Collecting Agent (COL) -- Important Notes

A31003-H3460-M104-4-76A9, July 2012

1.1.9 Security Notes

A31003-H3460-M104-4-76A9, July 2012

1.2 Installation Hints for Performance Management (PM)

A31003-H3460-M104-4-76A9, July 2012

1.2.1 Installation Prerequisites

Prerequisites for HiPath 4000/

HiPath 4000 System Installation

A31003-H3460-M104-4-76A9, July 2012

1.2.2 HiPath 4000 System Installation - Step 1

The file contains the following parameters: Notes (1)