PoC Billing Guide

68P09278A31-A
2006 Motorola, Inc.

FEB 2007
All Rights Reserved

Notice
While reasonable efforts have been made to assure the accuracy of this document, Motorola,
Inc. assumes no liability resulting from any inaccuracies or omissions in this document, or
from use of the information obtained herein. The information in this document has been
carefully checked and is believed to be entirely reliable. However, no responsibility is assumed for inaccuracies or omissions. Motorola, Inc. reserves the right to make changes to
any products described herein and reserves the right to revise this document and to make
changes from time to time in content hereof with no obligation to notify any person of revisions or changes. Motorola, Inc. does not assume any liability arising out of the application
or use of any product, software, or circuit described herein; neither does it convey license
under its patent rights or the rights of others.
It is possible that this publication may contain references to, or information about Motorola
products (machines and programs), programming, or services that are not announced in
your country. Such references or information must not be construed to mean that Motorola
intends to announce such Motorola products, programming, or services in your country.
Copyrights
This instruction manual, and the Motorola products described in this instruction manual may
be, include or describe copyrighted Motorola material, such as computer programs stored
in semiconductor memories or other media. Laws in the United States and other countries
preserve for Motorola and its licensors certain exclusive rights for copyrighted material, including the exclusive right to copy, reproduce in any form, distribute and make derivative
works of the copyrighted material. Accordingly, any copyrighted material of Motorola and its
licensors contained herein or in the Motorola products described in this instruction manual
may not be copied, reproduced, distributed, merged or modied in any manner without the
express written permission of Motorola. Furthermore, the purchase of Motorola products
shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any
license under the copyrights, patents or patent applications of Motorola, as arises by operation of law in the sale of a product.
Usage and Disclosure Restrictions
License Agreements
The software described in this document is the property of Motorola, Inc and its licensors.
It is furnished by express license agreement only and may be used only in accordance with
the terms of such an agreement.
Copyrighted Materials
Software and documentation are copyrighted materials. Making unauthorized copies is prohibited by law. No part of the software or documentation may be reproduced, transmitted,
transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, without prior written permission of Motorola, Inc.
High Risk Materials
Components, units, or third-party products used in the product described herein are NOT
fault-tolerant and are NOT designed, manufactured, or intended for use as on-line control
equipment in the following hazardous environments requiring fail-safe controls: the operation of Nuclear Facilities, Aircraft Navigation or Aircraft Communication Systems, Air Trafc
Control, Life Support, or Weapons Systems (High Risk Activities). Motorola and its supplier(s) specically disclaim any expressed or implied warranty of tness for such High Risk
Activities.
Trademarks

Motorola and the Stylized M Logo are registered in the US Patent & Trademark Ofce. All
other product or service names are the property of their respective owners.

FEB 2007

Table
of
Contents

Contents

PoC Billing Guide

Revision history . . . . . . . . . . . . . . . . . . . . . . . . . .
Version information . . . . . . . . . . . . . . . . . . . . . .
General information . . . . . . . . . . . . . . . . . . . . . . . .
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cross references . . . . . . . . . . . . . . . . . . . . . . . .
Text conventions . . . . . . . . . . . . . . . . . . . . . . . .
Contacting Motorola . . . . . . . . . . . . . . . . . . . . . . . .
Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Questions and comments . . . . . . . . . . . . . . . . . . .
24 hour support . . . . . . . . . . . . . . . . . . . . . . . .
Security Advice . . . . . . . . . . . . . . . . . . . . . . . . . .
Warnings and cautions . . . . . . . . . . . . . . . . . . . . . . .
Failure to comply with warnings . . . . . . . . . . . . . . . .
Warnings. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General Safety . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ground the equipment . . . . . . . . . . . . . . . . . . . . .
Do not operate in an explosive atmosphere . . . . . . . . . .
Keep away from live circuits . . . . . . . . . . . . . . . . . .
Do not service or adjust alone . . . . . . . . . . . . . . . . .
Use caution when exposing or handling the CRT. . . . . . . .
Do not substitute parts or modify equipment . . . . . . . . .
Potentially hazardous procedure warnings. . . . . . . . . . .
Devices sensitive to static . . . . . . . . . . . . . . . . . . . . .
Special handling techniques . . . . . . . . . . . . . . . . . .
Caring for the environment . . . . . . . . . . . . . . . . . . . .
Disposal of Motorola Networks equipment in EU countries . .
Disposal of Motorola Networks equipment in non-EU countries
Motorola document set . . . . . . . . . . . . . . . . . . . . . .
Ordering documents and CD-ROMs . . . . . . . . . . . . . .
Document banner denitions . . . . . . . . . . . . . . . . .
Third Party Computer Software and Trademarks . . . . . . . . .
Computer Software . . . . . . . . . . . . . . . . . . . . . .
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

2
2
3
3
3
3
5
5
5
5
6
7
7
7
7
8
9
9
9
9
9
10
10
10
11
11
12
12
12
13
13
13
14
14
15

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

1-2
1-2
1-2
1-2

Chapter 1: Introduction
MSSPoC billing interface . .
Comma Separated Value .
Veritas NetBackup . . . .
Billing interface . . . . .
68P09278A31-A
FEB 2007

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

.
.
.
.

Contents

Acronyms and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-3

Chapter 2: User Data Records

. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
and a group call
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

2-2
2-2
2-3
2-3
2-3
2-4
2-4
2-4
2-5
2-5
2-5
2-5
2-6
2-7
2-7
2-15
2-15
2-17
2-18
2-18
2-26
2-26
2-26
2-27
2-27
2-29
2-29
2-30
2-31
2-31
2-32
2-34
2-34
2-34
2-34

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

4-2
4-3
4-4
4-5
4-6

Provisioning the Billing Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-2
5-2

Billing interface . . . . . . . . . . . . . . . . . . . . . . .
Special characters . . . . . . . . . . . . . . . . . . . .
Versions . . . . . . . . . . . . . . . . . . . . . . . . . . .
Version number . . . . . . . . . . . . . . . . . . . . .
Enabling UDR elds . . . . . . . . . . . . . . . . . . .
UDR Files . . . . . . . . . . . . . . . . . . . . . . . . . .
File naming . . . . . . . . . . . . . . . . . . . . . . .
Archive . . . . . . . . . . . . . . . . . . . . . . . . .
Time interval. . . . . . . . . . . . . . . . . . . . . . .
File transfer . . . . . . . . . . . . . . . . . . . . . . .
Checksum . . . . . . . . . . . . . . . . . . . . . . . .
Tracking transferred les . . . . . . . . . . . . . . . .
Status le names. . . . . . . . . . . . . . . . . . . . .
Schema for Call Records . . . . . . . . . . . . . . . . . . .
UDR schema for Call Records . . . . . . . . . . . . . .
How the Call_Id is generated? . . . . . . . . . . . . . .
What Call_Id represents for calls and activity records? .
Differentiating between barge calls and between a barge
Schema for Activity Records . . . . . . . . . . . . . . . . .
UDR schema for Activity Records . . . . . . . . . . . .
UDR examples . . . . . . . . . . . . . . . . . . . . . . . .
Pointtopoint call . . . . . . . . . . . . . . . . . . . .
Group call . . . . . . . . . . . . . . . . . . . . . . . .
Adhoc call . . . . . . . . . . . . . . . . . . . . . . . .
Activity record . . . . . . . . . . . . . . . . . . . . . .
Corrupted or missing SID . . . . . . . . . . . . . . . . . .
Scenarios . . . . . . . . . . . . . . . . . . . . . . . .
Alert Call or Alert Message . . . . . . . . . . . . . . . . .
Disconnect reasons . . . . . . . . . . . . . . . . . . . . .
Release indicators . . . . . . . . . . . . . . . . . . . .
Scenarios . . . . . . . . . . . . . . . . . . . . . . . .
Time measurement. . . . . . . . . . . . . . . . . . . . . .
Timestamps . . . . . . . . . . . . . . . . . . . . . . .
Denitions for call time . . . . . . . . . . . . . . . . .
Call duration . . . . . . . . . . . . . . . . . . . . . . .

Chapter 3: Congurable UDR elds

Chapter 4: Congurable UDR formats
PttType . . . . . . . . . . .
StartTime and EndTime . . .
SourceMIN and SourceMDN .
TargetMIN and TargetMDN .
DisconnectReason . . . . . .

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

.
.
.
.
.

Chapter 5: Provisioning

ii

68P09278A31-A
FEB 2007

List
of
Figures

List of Figures

Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure

2-1:
2-2:
2-3:
2-4:
4-1:
4-2:
5-1:
5-2:
5-3:

Pointtopoint call record . . . . . . .

Group call record . . . . . . . . . . .
Adhoc call record . . . . . . . . . . .
Activity record . . . . . . . . . . . . .
Selection of the elds in congure UDR
Congurable UDR eld format. . . . .
CDR Collection Points . . . . . . . . .
Billing Conguration. . . . . . . . . .
Congured Billing Protocols . . . . . .

68P09278A31-A
FEB 2007

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.

2-26
2-27
2-27
2-28
4-7
4-8
5-3
5-4
5-1

iii

List of Figures

iv

68P09278A31-A
FEB 2007

List
of
Tables

List of Tables

Table
Table
Table
Table
Table
Table

2-1:
2-2:
2-3:
2-4:
2-5:
2-6:

Encoded special characters . . . .

UDR schema for Call Records . . .
UDR schema for Activity Records .
Corrupted/missing SID scenarios .
Release indicators . . . . . . . .
Disconnect scenarios . . . . . . .

68P09278A31-A
FEB 2007

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

.
.
.
.
.
.

2-2
2-7
2-18
2-29
2-31
2-32

List of Tables

vi

68P09278A31-A
FEB 2007

About
This
Manual

PoC Billing Guide

What is covered in this manual?

This document is intended as an interface specication between the billing NBI running on the
PushToTalk over Cellular (PoC) platform and a carriers billing system. This specication
may be used by the carrier to develop a post processor to convert PoC records into a record
format required by their billing system.

68P09278A31-A
FEB 2007

Revision history

Revision history

The following shows the status of this document since it was rst released.

Version information

Document issue

Date of issue

Remarks

FEB 2007

First issue

68P09278A31-A
FEB 2007

General information

General information

Motorola disclaims all liability whatsoever, implied or express, for any risk of damage,
loss or reduction in system performance arising directly or indirectly out of the
failure of the customer, or anyone acting on the customers behalf, to abide by the
instructions, system parameters or recommendations made in this document.

Purpose
Motorola cellular communications documents are intended to instruct and assist personnel in
the operation, installation, and maintenance of the Motorola cellular infrastructure equipment
and ancillary devices. It is recommended that all personnel engaged in such activities be
properly trained by Motorola.

Failure to comply with Motorolas operation, installation and maintenance instructions

may, in exceptional circumstances, lead to serious injury or death.
These documents are not intended to replace the system and equipment training offered by
Motorola, although they can be used to supplement and enhance the knowledge gained through
such training.

Cross references
Throughout this document, references are made to external publications, chapter numbers
and section names. The references to external publications are shown in italics. Chapter and
section name cross references are emphasized in blue text in electronic versions. These are
active links to the references.
This document is divided into uniquely identied and numbered chapters that, in turn, are
divided into sections. Sections are not numbered, but are individually named at the top of each
page, and are listed in the table of contents.

Text conventions
The following conventions are used in the Motorola cellular infrastructure documents to
represent keyboard input text, screen output text and special key sequences.

68P09278A31-A
FEB 2007

General information

Input
Characters typed in at the keyboard are shown like this.

Output
Messages, prompts, file listings, directories, utilities, and environmental
variables that appear on the screen are shown like this.

Special key sequences

Special key sequences are represented as follows:

CTRL-c

Press the Control and c keys at the same time.

ALT-f

Press the Alt and f keys at the same time.

Press the pipe symbol key.

CR or RETURN

Press the Return key.

68P09278A31-A
FEB 2007

Contacting Motorola

Contacting Motorola

Motorola appreciates feedback from the users of our documents.

Errors
To report a documentation error, call the CNRC (Customer Network Resolution Center) and
provide the following information to enable CNRC to open an SR (Service Request):

The document type

The document title, part number, and revision character

The page number(s) with the error

A detailed description of the error and if possible the proposed solution

Questions and comments

Send questions and comments regarding user documentation to the email address below:
mydocs@motorola.com

24 hour support
If you have problems regarding the operation of your equipment, please contact the Customer
Network Resolution Center (CNRC) for immediate assistance. The 24 hour telephone numbers
are listed at https://mynetworksupport.motorola.com. Select Customer Network Resolution
Center contact information. For additional CNRC contact information, contact your Motorola
account representative.
For additional CNRC contact information, contact your Motorola account representative.

68P09278A31-A
FEB 2007

Security Advice

Security Advice

Motorola systems and equipment provide congurable security parameters to be set by the
operator based on their particular operating environment. Motorola recommends setting and
using these parameters following industry recognized security practices. Security aspects
to be considered are protecting the condentiality, integrity, and availability of information
and assets. Assets include the ability to communicate, information about the nature of the
communications, and information about the parties involved.
In certain instances Motorola makes specic recommendations regarding security practices,
however the implementation of these recommendations and nal responsibility for the security
of the system lies with the operator of the system.
Please contact the Customer Network Resolution Center (CNRC) for assistance. The 24 hour
telephone numbers are listed at https://mynetworksupport.motorola.com/. Select Customer
Network Resolution Center contact information, from the menu located to the left of the
Login box. Alternatively if you do not have access to CNRC or the internet, contact the Local
Motorola Ofce.

68P09278A31-A
FEB 2007

Warnings and cautions

Warnings and cautions

The following describes how warnings and cautions are used in this document and in all
documents of this Motorola document set.

Failure to comply with warnings

Observe all warnings during all phases of operation, installation and maintenance of the
equipment described in the Motorola documents. Failure to comply with these warnings,
or with specic warnings elsewhere in the Motorola documents, or on the equipment
itself, violates safety standards of design, manufacture and intended use of the
equipment. Motorola assumes no liability for the customers failure to comply with
these requirements.

Warnings
A denition and example follow below:

Denition of Warning
A warning is used to alert the reader to possible hazards that could cause loss of life, physical
injury, or ill health. This includes hazards introduced during maintenance, for example, the use
of adhesives and solvents, as well as those inherent in the equipment.

Example and format

Do not look directly into ber optic cables or data in/out connectors. Laser radiation
can come from either the data in/out connectors or unterminated ber optic cables
connected to data in/out connectors.

Cautions
A denition and example follow below:

Denition of Caution
A caution means that there is a possibility of damage to systems, software or individual items of
equipment within a system. However, this presents no danger to personnel.

68P09278A31-A
FEB 2007

Warnings and cautions

Example and format

Do not use test equipment that is beyond its due calibration date; arrange for
calibration to be carried out.

Notes
A denition and example follow below:

Denition of Note
A note means that there is a possibility of an undesirable situation or provides additional
information to help the reader understand a topic or concept.

Example and format

The UDR version number is congured at installation time by Motorola personnel

and is not accessible by the customer.

68P09278A31-A
FEB 2007

General Safety

General Safety

Ground the equipment

To minimize shock hazard, the equipment chassis and enclosure must be connected to an
electrical ground. If the equipment is supplied with a three-conductor ac power cable, the
power cable must be either plugged into an approved three-contact electrical outlet or used
with a three-contact to two-contact adapter. The three-contact to two-contact adapter must
have the grounding wire (green) rmly connected to an electrical ground (safety ground) at
the power outlet. The power jack and mating plug of the power cable must meet International
Electrotechnical Commission (IEC) safety standards.

Refer to Grounding Guideline for Cellular Radio Installations 68P81150E62.

Do not operate in an explosive atmosphere

Do not operate the equipment in the presence of ammable gases or fumes. Operation of any
electrical equipment in such an environment constitutes a denite safety hazard.

Keep away from live circuits

Operating personnel must:

not remove equipment covers. Only Factory Authorized Service Personnel or other
qualied maintenance personnel may remove equipment covers for internal subassembly,
or component replacement, or any internal adjustment.

not replace components with power cable connected. Under certain conditions, dangerous
voltages may exist even with the power cable removed.

always disconnect power and discharge circuits before touching them.

Do not service or adjust alone

Do not attempt internal service or adjustment, unless another person, capable of rendering rst
aid and resuscitation, is present.

68P09278A31-A
FEB 2007

General Safety

Use caution when exposing or handling the CRT

Breakage of the CathodeRay Tube (CRT) causes a high-velocity scattering of glass fragments
(implosion). To prevent CRT implosion, avoid rough handling or jarring of the equipment. Only
qualied maintenance personnel wearing approved safety mask and gloves should handle the
CRT.

Do not substitute parts or modify equipment

Because of the danger of introducing additional hazards, do not install substitute parts or
perform any unauthorized modication of equipment. Contact Motorola Warranty and Repair
for service and repair to ensure that safety features are maintained.

Potentially hazardous procedure warnings

Warnings, such as the example below, precede potentially hazardous procedures throughout
this document. Instructions contained in the warnings must be followed. Employ all other safety
precautions necessary for the operation of the equipment in the operating environment.

Potentially hazardous voltages, capable of causing death, are present in this

equipment. Use extreme caution when handling, testing, and adjusting.

10

68P09278A31-A
FEB 2007

Devices sensitive to static

Devices sensitive to static

Certain metal oxide semiconductor (MOS) devices embody in their design a thin layer of
insulation that is susceptible to damage from electrostatic charge. Such a charge applied to the
leads of the device could cause irreparable damage.
These charges can be built up on nylon overalls, by friction, by pushing the hands into high
insulation packing material or by use of ungrounded soldering irons.
MOS devices are normally dispatched from the manufacturers with the leads short-circuited
together, for example, by metal foil eyelets, wire strapping, or by inserting the leads into
conductive plastic foam. Provided the leads are short-circuited it is safe to handle the device.

Special handling techniques

In the event of one of these devices having to be replaced, observe the following precautions
when handling the replacement:

Always wear a ground strap which must be connected to the electrostatic point on the
equipment.

Leave the short circuit on the leads until the last moment. It may be necessary to replace
the conductive foam by a piece of wire to enable the device to be tted.

Do not wear outer clothing made of nylon or similar man made material. A cotton overall
is preferable.

If possible work on an grounded metal surface or anti-static mat. Wipe insulated plastic
work surfaces with an anti-static cloth before starting the operation.

All metal tools should be used and when not in use they should be placed on an grounded
surface.

Take care when removing components connected to electrostatic sensitive devices. These
components may be providing protection to the device.

When mounted onto printed circuit boards (PCBs), MOS devices are normally less susceptible to
electrostatic damage. However PCBs should be handled with care, preferably by their edges
and not by their tracks and pins, they should be transferred directly from their packing to the
equipment (or the other way around) and never left exposed on the workbench.

68P09278A31-A
FEB 2007

11

Caring for the environment

Caring for the environment

The following information is provided to enable regulatory compliance with the European Union
(EU) Directive 2002/96/EC Waste Electrical and Electronic Equipment (WEEE) when using
Motorola Networks equipment in EU countries.

Disposal of Motorola Networks equipment in EU countries

Please do not dispose of Motorola Networks equipment in landll sites.

In the EU, Motorola Networks in conjunction with a recycling partner will ensure that equipment
is collected and recycled according to the requirements of EU environmental law.
Please contact the Customer Network Resolution Center (CNRC) for assistance. The 24 hour
telephone numbers are listed at https://mynetworksupport.motorola.com/. Select Customer
Network Resolution Center contact information. Alternatively if you do not have access
to CNRC or the internet, contact the Local Motorola Ofce.

Disposal of Motorola Networks equipment in non-EU countries

In non-EU countries, dispose of Motorola Networks equipment in accordance with national
and regional regulations.

12

68P09278A31-A
FEB 2007

Motorola document set

Motorola document set

The Motorola document sets provide the information needed to operate, install, and maintain
the Motorola equipment.

Ordering documents and CD-ROMs

With internet access available, to view, download, or order documents (original or revised), visit
the Motorola Lifecycles Customer web page at https://mynetworksupport.motorola.com/, or
contact your Motorola account representative.
Without internet access available, order hard copy documents or CD-ROMs with your Motorola
Local Ofce or Representative.
If Motorola changes the content of a document after the original printing date, Motorola
publishes a new version with the same part number but a different revision character.

Document banner denitions

A banner (oversized text on the bottom of the page, for example, PRELIMINARY UNDER
DEVELOPMENT) indicates that some information contained in the document is not yet approved
for general customer use.

68P09278A31-A
FEB 2007

13

Third Party Computer Software and Trademarks

Third Party Computer Software and Trademarks

Computer Software
The Motorola and 3rd Party supplied Software (SW) products described in this instruction
document may include copyrighted Motorola and other 3rd Party supplied computer programs
stored in semiconductor memories or other media. Laws in the United States and other
countries preserve for Motorola and other 3rd Party supplied SW certain exclusive rights for
copyrighted computer programs, including the exclusive right to copy or reproduce in any
form the copyrighted computer program. Accordingly, any copyrighted Motorola or other 3rd
Party supplied SW computer programs contained in the Motorola products described in this
instruction document may not be copied (reverse engineered) or reproduced in any manner
without the express written permission of Motorola or the 3rd Party SW supplier. Furthermore,
the purchase of Motorola products shall not be deemed to grant either directly or by implication,
estoppel, or otherwise, any license under the copyrights, patents or patent applications of
Motorola or other 3rd Party supplied SW, except for the normal non-exclusive, royalty free
license to use that arises by operation of law in the sale of a product.
Vendor

Copyright

Apache Software Foundation

Copyright 2001, 2002, 2003, 2004 , 2004 All

Rights Reserved

Artesyn

Copyright All Rights Reserved

CMU *

Copyright All Rights Reserved

Open Source Software Foundation *

Copyright 2000 All Rights Reserved

Open Source Tools / Utilities *

Copyright All Rights Reserved

GNOME Project *

Copyright 2004 All Rights Reserved

iodbc.org *

Copyright 2002 All Rights Reserved

Megastep *

Copyright 2002 All Rights Reserved

NIST *

Copyright 2002 All Rights Reserved

openBSD *

Copyright 2006 All Rights Reserved

openSSL *

Copyright 2006 All Rights Reserved

Performance Technologies

Copyright All Rights Reserved

Postgres *

Copyright 2005 All Rights Reserved

Sun Microsystems Inc. *

Copyright 2002 All Rights Reserved

Telelogic

Copyright All Rights Reserved

QNX *

Copyright All Rights Reserved

*= May contain purchased SW and Open Source SW which may be subject to a license fee.

14

68P09278A31-A
FEB 2007

Third Party Computer Software and Trademarks

Trademarks
Java Technology and/or J2ME: Java and all other Java-based marks are trademarks or
registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.
UNIX: UNIX is a registered trademark of The Open Group in the United States and other
countries.

68P09278A31-A
FEB 2007

15

Third Party Computer Software and Trademarks

16

68P09278A31-A
FEB 2007

Chapter

1
Introduction

This chapter deals with the MSSPoC billing interface and acronyms and abbreviations that are
used in this manual.

68P09278A31-A
FEB 2007

1-1

MSSPoC billing interface

Chapter 1: Introduction

MSSPoC billing interface

Motorola supports the following MSS-PoC billing interfaces:

Comma Separated Value

Veritas NetBackup

Billing interface

Comma Separated Value

Motorola chose a Comma Separated Value (CSV) format because it is easy to parse and convert
to any other required billing format.

Veritas NetBackup
Veritas NetBackup client software is used to create ofine backups.
Motorola requires the Veritas client software and server conguration information from the
carrier at least three weeks in advance of deployment so that the Veritas software is integrated
with the PoC software.
Motorola does not supply the Veritas NetBackup client or server software at this time.

Billing interface
An interface is maintained between the carrier and the Motorola Control Switch (CS) called the
Northbound Billing Interface (NBI). Each time the interface between the switch and the carrier
is restarted, the switch sends billing les. These les are sequentially numbered (N+1), where
N is the last le successfully sent.

Files are transferred to the northbound system using FTP.

1-2

68P09278A31-A
FEB 2007

PoC Billing Guide

Acronyms and abbreviations

Acronyms and abbreviations

The following acronyms and abbreviations are used in this manual.

ccswitch

Call Control Switch

CDR

Call Detail Record

CDRCP

Call Detail Record Collection Point

CSV

Comma Separated Value

EMS

Element Management Server

FTP

File Transfer Protocol

GMT

Greenwich Mean Time

GUI

Graphical User Interface

IMSI

International Mobile Station Identication

IP

Internet Protocol

MDN

Mobile Directory Number

MIN

Mobile Identication Number

MPTT

Motorola PushtoTalk

NAS

Network Application Server

NID

Network Identication Number

NBI

North Bound Interface

NTP

Network Time Protocol

OAMP

Operations, Administration, Maintenance, and Provisioning

PoC

PushtoTalk over Cellular

PTP

Point to Point

PTT

PushtoTalk

RTP

Real Time Protocol

SIP

Session Initiation Protocol

UDR

User Data Record

UTC

Universal Coordinated Time

68P09278A31-A
FEB 2007

1-3

Acronyms and abbreviations

1-4

Chapter 1: Introduction

68P09278A31-A
FEB 2007

Chapter

2
User Data Records

This chapter deals with the billing interface, versions, and User Data les.

68P09278A31-A
FEB 2007

2-1

Billing interface

Chapter 2: User Data Records

Billing interface

The Element Management Server (EMS) on the PoC Control Switch chassis generates one User
Data Record (UDR) for every PoC call segment or user and creates a le at specied time
intervals for processing. The EMS also generates an Activity Record each time a user registers
or reregisters for the service.
The PoC application relies on the biller to support rating plans, calculating packets, and
identifying off peak and peak calls.

Special characters
Special characters like comma (,) and percent sign (%) are URL encoded in the billing system
and the client billing system must expect the special characters in this format only. A group
name can contain these special characters.
For example, in the UDR generated for a group call, elds such as groupId, origDialedDigits,
and translatedDialedDigits can contain special characters.
If the group name is grp,123, then this group name is encoded as grp%2C123 in the UDR le.
The following table gives the URL encoded value of special characters.

Table 2-1

2-2

Encoded special characters

Special Character

URL Encoded Value

, (comma)

%2C

% (percent sign)

%25

68P09278A31-A
FEB 2007

PoC Billing Guide

Versions

Versions

This section describes the version number and the command for enabling UDR elds.

Version number
Versions other than Version 1 include the ASCII representation of the version number on the
same line as the checksum after the comma. UDR decoders can use this value to determine the
format of encoding of the subsequent call or activity records. The version is not encoded for
Version 1 for backward compatibility.

Version 1 call/activity records contain elds 1 through 26.

Version 2 call/activity records contain elds 1 through 27.

Version 3 call/activity records contain elds 1 through 33.

Version 4 call/activity records contain elds 1 through 34.

Version 5 call/activity records contain elds 1 through 40.

Version 6 call/activity records contain elds 1 through 47.

Version 7 call/activity records contain elds 1 through 48.

The UDR version number is congured at installation time by Motorola personnel

and is not accessible by the customer.

Enabling UDR elds

After changing the billing version, run the following command:
/opt/WMS/rel/scripts/enable_udr_fields <floating_ip_nmhosts> swuser <TL1_passwd>

68P09278A31-A

2-3
FEB 2007

UDR Files

Chapter 2: User Data Records

UDR Files

The User Data Record (UDR) le is written to the archive directory. This is a at le that
contains the data values separated by a delimiter comma.

File naming
All les are created using the following le naming specications:
{UDRPREFIX}YYYYMMDD_HH24MMSS_SeqNum
where

{UDRPrex} is congured by the operator in the GUI under OAMP >Billing -> Edit
-> Update

YYYY four digit year

MM two digit month

DD two digit day

HH24MMSS 24 hour clock in hours, minutes and seconds

SeqNum the unique sequence number (000999), which must be a part of the le name.
The time stamp within the le name is the time of le creation in GMT.

Archive
Archive directory
Motorola provides a primary directory where completed billing les are stored. This directory
is in the cluster partition.

Files remain in this primary directory (/cluster/amap) for three days.

At the end of this period the les are moved to an archive directory (/cluster/arch) where
they are stored for ve days.

At the end of this time period, the les are deleted.

The primary and archive directory have a login/password associated with it for access. The
same login and password can be used to retrieve les from either directory.

2-4

68P09278A31-A
FEB 2007

PoC Billing Guide

UDR Files

Ofine backups of archive directory

The PoC server provides Call Detail Record (CDR) backups in the Archive Directory.

In addition, ofine backups are available using carrier provided Veritas NetBackup
client software.

Time interval
New les are created every X minutes, with X congurable by the carrier. The default is ve
minutes. Files are created only if there are calls or activity records in the dened time interval.

File transfer
Files are transferred to the billing system of the carrier using FTP. The carrier system retrieves
les.

Checksum
At the beginning of each le, there is a checksum. The checksum is in ASCII Hex format. The
checksum value generated by the Billing NBI is based on the content of the at le. This value
only appears one time at the beginning of the at le and ends by a comma followed by a line
feed. The checksum algorithm is Posix.2 CRC32.

Tracking transferred les

The recommended method for tracking les transferred using FTP is to rename the les.

68P09278A31-A

2-5
FEB 2007

UDR Files

Chapter 2: User Data Records

To track les transferred using FTP, use the following method:

Successfully transferred les Rename the successfully transferred les by adding a

sufx to the lename.

All the report generation is done based on the congured UDR prex. DO
NOT change the prex of transferred UDR les.

The extension allows the UDR les to continue to exist in the cluster
archive directory.

Transfer failure Do NOT rename the UDR le. This allows the le to be replaced the next
time the le transfer is initiated.

The UDR le name before the FTP transfer is: WP0120050728_062033_213

After a successful transfer of the UDR le, the le is renamed:

WP0120050728_062033_213.rename

Example

Any extension may be used but needs to be consistent.

Status le names
If a status le needs to be created to track le transfers in the same directory as the UDR les,
do NOT use the same prex in the status le name as the UDR prex.

2-6

68P09278A31-A
FEB 2007

PoC Billing Guide

Schema for Call Records

Schema for Call Records

This section explains the UDR elements used in the Call Records.

UDR schema for Call Records

The Call Record uses the following format:
Target_MIN,startTime,endTime,Call_ID,NAS_Address,Framed_IP_Address,UserName,
Unique_Call_Id,Vendor_ID,StartTime,BWGMT_Offset,Source_MIN/IMSI,Source_MDN,
Target_MIN/IMSI,Target_MDN,Delta_Acct_Output_Octets,Delta_Acct_Input_Octets,
BW_Delta_Session_Duration,IP_Tech:,PTT_CntSw_ID,PTT_Group_ID,PTT_Called_IP,
Reason_ Ind,Event_Timestamp,SID, BW_Call_Orig_Cell_IDBase Station ID,
BW_Call_Dest_Cell_ID:,BW_Switch_ID(NID),PTT_Service_Type,Presence_State,
Subscriber_Type,Class_Of_Service,Activity_Type,Referred_By,Total_Talk_Time,
Total_Listen_Time,Wholesale_Name,Enterprise_name,ESN,Prepaid_Result,GCI,
Source_SIPURI,Target_SIPURI,Ptx_successful_files_count,
Ptx_unsuccessful_files_count,Ptx_octet_sent

Record_IDs are Target_MIN,startTime,endTime,Call_ID.

Table 2-2 UDR schema for Call Records

Field
No.

UDR Element

Type (Length
in Bytes)

Contents

Example

Record_ID

String (64)

Target_MIN, startTime,
endTime, Call_ID

00000978654354520011
108T16:29:412001110
8T16:29:4136AAACCCDD

NAS_Address

String (15)

Primary IP address of the PoC

Application Server generating
the UDR record (Primary IP
address is address of the EMS
system).

66.123.22.33

FramedIPAddress

String (15)

IP address of the subscriber

66.123.45.22

UserName (name of user

represented by this UDR)

String (64)

value = username@PTT.x
yz.com

[Default NAI]@ptt.com

Continued

68P09278A31-A

2-7
FEB 2007

Schema for Call Records

Chapter 2: User Data Records

Table 2-2 UDR schema for Call Records (Continued)

Field
No.
5

UDR Element
Call_Id

Type (Length
in Bytes)
String (10)

Contents
The same Correlation ID value
is populated in every UDR
generated for a given PoC call.

Example
36AAACCCDD

Additional information and examples for the Call_Id eld is found at the end of Table 2-2.
6

Vendor_ID

String (6)

Parse Vendor ID from CallID.

36

StartTime

String (19)

PoC call start time in GMT

formatDate/time.

20011108T16:29:41

The StartTime is based on either the time the Control Switch receives the SIP message or
the time the Control Switch sends the SIP message to the handset.
8

BWGMT_Offset

String (10)

Time offset in seconds

of local time referenced
to GMT. Local timezone
must reect timezone of
handset at start of call.
Reference Corrupt/Missing
SID topic for more
information.

3000

The GMT Offset is adjusted, if necessary to reect Daylight Savings Time. If SID is not
available, GMT offsets are set to 0 and SID is populated with .
9

Source_MIN/IMSI

String (15)
zero padded
on left

MIN/IMSI of the call

originator.

000009784321234

10

Source_MDN

String (15)
zero padded
on left

MDN of call originator.

000919786543545

11

Target_MIN/IMSI

String (15)
zero padded
on left

MIN/IMSI of handset
represented by this UDR.

000009786543545

Continued

2-8

68P09278A31-A
FEB 2007

PoC Billing Guide

Schema for Call Records

Table 2-2
Field
No.

UDR schema for Call Records (Continued)

UDR Element

12

Target_MDN

13

Type (Length
in Bytes)

Contents

Example

MDN of handset represented

by this UDR.

00009786543545

Delta_Acct_Output_Octets Integer (15)

Octets Sent (RTP + SIP Octets)

from server to handset.

3214

14

Delta_Acct_Input_ Octets

Integer (15)

Octets Received (RTP +

SIP Octets) from handset to
server.

2233

15

BW_Delta_Session_
Duration

Integer (20)

Duration of PoC call for this

user in seconds.

32

String (15)
zero padded
on left

This value is the time a Bye message for this leg of the call is received or generated
by the Control Switch the time the SIP 200 OK message was received or generated
for this call leg.
Integer (1)
Identies Simple IP, Mobile IP, 1
or another technology:
1= Simple IP
2= Mobile IP
Always 1

16

IP_Tech:

17

PTT_CntSw_ID

String (10)

Unique identier for Control

Switch.

PTTCS1.MA

18

PTT_Group_ID

String (64)

Called Party or Group Name

=username

919786543545@PTT or
marketing@PTT)

19

PTT_Called_IP

String (15)

IP address of the called party

(only used for PointToPoint
calls.

Optional, null if not a

pointtopoint call.

20

Reason_Ind

Integer (2)

Indicates how the session was

ended.

Details for Reason_Ind

values:

Example:

0= Maintenance Record
Maintenance record for
account activity not billable.

Subscriber A and
subscriber B are
registered.

1= Call completed Normally

Subscriber A makes a
PTP call to subscriber B.
The call is connected
and disconnected
normally because the
PoC Server was able
to tear down the call
gracefully.
Continued

68P09278A31-A

2-9
FEB 2007

Schema for Call Records

Chapter 2: User Data Records

Table 2-2 UDR schema for Call Records (Continued)

Field
No.

UDR Element

Type (Length
in Bytes)

Contents

Example

2 = Abnormal Disconnect
Disconnect indicating that
the PoC Server experienced a
timeout while trying to clear
the call (sent a BYE and did
not get an acknowledgment
message).

Subscriber A and
B are registered
with the server.
Subscriber A makes
an alert call to
subscriber B.
Callee ignores the
call and the call is
disconnected.

3 = Unconnected
Network Failure
Call could not be connected
due to a problem with the
network or PoC server.

Subscriber A and B
are registered with the
server. Subscriber A
makes a PTP call to
subscriber B who is not
in network. The call is
not connected.

4 = Unconnected
Invalid Address
Call could not be connected
because the number/group
name received was not a
valid number/group name (not
registered and active in PoC
server).

Subscriber A
is registered
with the server.
Subscriber A makes
a PTP call to subscriber
B who is not registered
or not provisioned
with the server.
Call is not connected.

5= Call ended due to RTP

timer expired (dark hole)
This leg of the call ended
when the person lost radio
contact.

Subscriber A and
B are registered
with the server.
Subscriber A makes
a PTP call to subscriber
B. Call is connected.
Remove the network
interface (RF Signal
goes to 0) and because
of network problem
(Radio link failure) the
call is teared down.

6 = Insufcient fund
In case of prepaid subscriber.

Subscriber A makes
a PTP call without
sufcient pre paid
funds available. The call
is not connected.
Continued

2-10

68P09278A31-A
FEB 2007

PoC Billing Guide

Schema for Call Records

Table 2-2
Field
No.

UDR schema for Call Records (Continued)

UDR Element

Type (Length
in Bytes)

Contents
7 = Blocked Call

Example
Subscriber B blocks
Subscriber A and
Subscriber A makes
a PTP call to subscriber
B. Since B has blocked
A, call is not setup.
In this case UDR is
generated only for
caller with disconnect
reason being set to 7
(Blocked Call) and no
UDR is generated for
callee.

A call is considered to be completed normally if a 200 OK is received by at least one called

party. If a 200 OK is not received then the Reason_Ind for the calling party is the same
as the reason indicator of the called party
21

EndTime

String (19)

GMT Format.

20011108T16:29:41

22

SID

String (4) hex

value

System ID taken from the

3GPP2_BSID value which is a
combination of SID, NID, and
Base Station ID where each
item is encoded using four
hexadecimal upper case ASCII
characters.

1212

SID may not be available under certain conditions such as, when error messages are
received from the handset for user unavailable, user not responding and user busy).
23
24
25

BW_Call_Orig_Cell_I
DBase Station ID
BW_Call_Dest_Cell_ID
BW_Switch_ID(NID)

Null

Cell ID for Call originator at

time call is started.

Null

Null

Cell ID for this user at time

call is started.

Null

Null

NID parsed from BSID of this

user.

Null

Continued

68P09278A31-A

2-11
FEB 2007

Schema for Call Records

Chapter 2: User Data Records

Table 2-2 UDR schema for Call Records (Continued)

Field
No.
26

UDR Element
PTT_Service_Type

Type (Length
in Bytes)
Integer (1)

Contents
PoC Type:
1 = PointtoPoint
2 = Group
3 = Acct
4 = Ad-hoc group
5 = Alert
6 = NNI Point-to-Point
7 = NNI Group
8 = NNI Ad-hoc Group
9 = NNI Alert

Example
2

NNI Point-to-Point, NNI Group,NNI Ad-hoc Group, NNI Alert service types are applicable
to the user not present in the current network (foreign user). For UDR version less than
7,1-1 Barge Call and Alert call are mapped to PTT_Service_Type 1. For UDR version 7
and above, 1-1 Barge Call is mapped to PTT_Service_Type 1 and Alert call is mapped
to PTT_Service_Type 5.
27

NoOfGrantedFloorControl Integer (2)

Indicates the number of oor

control granted to the user
during a call.

28

Original_dialed_digits

String (128)

The number originally dialed

by the caller.

9786543545

29

Translated_dialed_ digits

String (128)

The digits after number

translation to get the original
dialed number in E.164
format.

9786543545

30

Subscriber _Type

Integer (1)

Type of connection
for the subscriber:
1 = Prepaid subscriber
2 = Postpaid subscriber

31

Presence_State

Integer (1)

Present state of
the subscriber:
0 = Not applicable for
call records

32

Class_Of_Service

Integer (1)

Indicates subscribers
privilege services:
1 = Legacy presence
2 = No presence
3 = Premium service

33

Activity_Type

Integer (1)

Indicates the type

of activity record.
0 = Not applicable for
Call records

Continued

2-12

68P09278A31-A
FEB 2007

PoC Billing Guide

Table 2-2
Field
No.

Schema for Call Records

UDR schema for Call Records (Continued)

UDR Element

Type (Length
in Bytes)

Contents

Example

34

Referred_By

String (15)

MDN of user who referred

this party into the call.
This eld is set only if a new
user is added through Add
Request, otherwise value is
NULL.

9786543545

35

Total_Talk_Time

Integer (5)

Total seconds in call for which

this call leg had oor control.

20

36

Total_Listen_Time

Integer (5)

Total seconds in call for which

this call leg was on the call
and another leg had the oor.

15

37

Wholesale_Name

String (64)

Identies the type of customer

in billing system.

wholesale1

38

Enterprise_name

String (64)

Enterprise name of the

subscriber.

enterprise1

39

ESN

String (15)
zero padded
on left

40

Prepaid_Result

Integer (1)

Identies the result of a

prepaid operation for the
subscriber in a prepaid call.
This eld contains valid
values only in the call
records for prepaid
calls. Following are the
possible values of this eld:
0 = Not applicable
1 = Insufcient balance
2 = Debit not required
3 = Debit required
4 = Prepaid failure
5 = ECF unavailable

41

GCI

String (128)

Identies the cell ID of the

user which includes:

90802468001C
This value is NULL
for Activity records.

42

Source_SIPURI

String (128)

ESN/MeID from AD stored at

provisioning time.

Country Code

Network Code

LAC and

Cell ID

Identies the URI of the Caller.

This eld contains URI only if
the caller is congured with
the URI otherwise the value is
NULL.

000006106966302

user1@mot.com

Continued

68P09278A31-A

2-13
FEB 2007

Schema for Call Records

Chapter 2: User Data Records

Table 2-2 UDR schema for Call Records (Continued)

Field
No.
43

UDR Element
Target_SIPURI

Type (Length
in Bytes)
String (128)

Contents
Identies the URI used by
the caller to make a call.
This eld contains URI only
if the caller used URI to
originate the call.

For call record, the group call value is the group URI.

For adhoc call the value is set to the adhoc URI.

44

Ptx_successful_les_count Integer

45

Ptx_unsuccessful_les
_count

46

Example
user2@mot.com

Gives the integer count of

total number of successful
le(s) sent.

Integer

Gives the Integer count of

total number of unsuccessful
le(s) transfer.

Ptx_octet_sent

Integer

Total Octets sent(PTV media)

for PTV activity containing
retransmission of media.

12232

47

Ptx_le_size

Integer

For total size of le(s) sent for

PTV activity.

22242

48

Poc_Server_Role

Integer

Identies the role of the

server. Following are
the values for this eld:
0 = OMA_POC_DEFAULT,
1 =
OMA_POC_CONTROLLING
(Server role being
just Controlling)
2 =
OMA_POC_PARTICIPATING
(Server role being
just Participating)
3 =
OMA_POC_CONTROLLING_
AND_PARTICIPATING (Server
acting as both Controlling and
Participating)

2-14

68P09278A31-A
FEB 2007

PoC Billing Guide

Schema for Call Records

How the Call_Id is generated?

The expected behavior is where one nds that Call_Id maintained for release_ind is equal to
zero and is sequential, whereas Call_Id for release_ind not equal to zero is not sequential. The
Call_Id eld for maintenance records (release_ind = 0) is an internal count which is incremented
by the switch every time an activity record is generated. So the Call_Id is always sequential
until it wraps around. The Call_Id eld for call records (release_ind is not equal to zero) is the
same Call_Id allocated by the switch for assigning a call.
Therefore, it is possible that Call_Id = 1 is assigned for the fth call. In this case, the UDR for
rst call and the fth call has the same Call_Id. This Call_Id is not unique but the rst UDR
eld, the record_id eld, is unique and is differentiated based on the record_id eld. Also, the
Call_Id eld in the UDR is a combination of two elds and csm_id. Since csm_id is different for
CCSWs, that differentiates the records generated by each different CCSW. Therefore, Call_Id is
not the same for the records generated by different switches.
In the UDR examples given in Examples: on page 2-16, Call_Id = 5402000001, in Vendor_id
= 54, csm_id = 2, and Call_Id (switch) = 1. When the ccswitch process starts, it allocates a
pool of 1000 Call_Ids. The ccswitch takes the Call_Id from the pool and this Call_Id is returned
to the pool after the call is over. If at any point of time, all the Call_Ids in the pool are in use,
the ccswitch allocates 1000 more Call_Ids and grow the pool. So, to begin with the Call_Ids
wraparound at 1000. If at any point of time, the ccswitch is handling more than 1000 calls, it
starts rotating from 2000. This process repeats as necessary.

What Call_Id represents for calls and activity records?

In call records, the Call_Id eld is made up of three components:

Vendor_Id

csm_id

switch_Call_Id

In activity records, the Call_Id eld is made up of three components:

Vendor_Id

csm_id

reportId

Vendor_Id and csm_id are common to both the call and activity records.
If the Call_Id is 540c00000e the Vendor_Id is 54, the csm_id is 0c, the switch_Call_Id or reportId
is 00000e. In the Call Records, the switch_Call_Id is the Call_Id allocated by the switch. Initially
1000 Call_Ids are allocated in a pool and they are reused to assign to another call as soon as the
existing call is terminated. There is duplication of the Call_Id eld values in the UDR.
In the Activity Records, the reportId keeps track of the activity records that are generated. Its
value starts from one and keeps increasing for each activity record. There must not be any
duplicate Call_Ids for activity records. The Call_Id eld in the UDR is not unique as explained
above. The recordId eld is considered as unique for identication. This eld contains four
other UDR elds as mentioned in the billing specs (TargetMIN, StartTime, EndTime, and
Call_Id). Refer to the Examples: on page 2-16.

68P09278A31-A

2-15
FEB 2007

Schema for Call Records

Chapter 2: User Data Records

Examples:

UDRs generated by CCSW01

[swuser@nm3-02:cdrcp01]$ more udr-20060330_000231_8617c1ab44c,
50000070887000062006-03-29T23:43:352006-03-29T23:43:355402000001,
192.168.79.144,1 0.100.0.109,7088700006@PTT.com,5402000001,54,
2006-03-29T23:43:35,0,,,00000708870 0006,,239,214,0,1,WMS-SWITCH
,,,0,,,,,,3,0,,,2,0,1,1,,0,0,,,0,0
0000070887000082006-03-29T23:44:072006-03-29T23:44:075402000002,
192.168.79.144,1 0.100.0.102,7088700008@PTT.com,5402000002,54,
2006-03-29T23:44:07,0,,,00000708870 0008,,242,213,0,1,WMS-SWITCH
,,,0,,,,,,3,0,,,2,0,1,1,,0,0,,,0,0
0000070887000082006-03-29T23:44:302006-03-29T23:44:305402000003,
192.168.79.144,1 0.100.0.102,7088700008@PTT.com,5402000003,54,
2006-03-29T23:44:30,0,,,00000708870 0008,,242,213,0,1,WMS-SWITCH
,,,0,,,,,,3,0,,,2,0,1,1,,0,0,,,0,0
0000070887000082006-03-29T23:44:592006-03-29T23:44:595402000004,
192.168.79.144,1 0.100.0.102,7088700008@PTT.com,5402000004,54,
2006-03-29T23:44:59,0,,,00000708870 0008,,242,213,0,1,WMS-SWITCH
,,,0,,,,,,3,0,,,2,0,1,1,,0,0,,,0,0
0000070887000062006-03-29T23:45:312006-03-29T23:45:315402000005,
192.168.79.144,1 0.100.0.109,7088700006@PTT.com,5402000005,54,
2006-03-29T23:45:31,0,,,00000708870 0006,,242,214,0,1,WMS-SWITCH
,,,0,,,,,,3,0,,,2,0,1,1,,0,0,,,0,0

UDR generated by CCSW11

[swuser@nm3-02:cdrcp01]$ more udr-20060330_000235_86236f1361a,
50000070887000062006-03-29T23:43:392006-03-29T23:43:395401000001,
192.168.79.144,1 0.100.0.109,7088700006@PTT.com,5401000001,54,
2006-03-29T23:43:39,0,,,00000708870 0006,,290,178,0,1,WMS-SWITCH
,,,0,,,,,,3,0,,,2,0,0,5,,0,0,,,0,0
0000070887000082006-03-29T23:44:102006-03-29T23:44:105401000002,
192.168.79.144,1 0.100.0.102,7088700008@PTT.com,5401000002,54,
2006-03-29T23:44:10,0,,,00000708870 0008,,301,180,0,1,WMS-SWITCH
,,,0,,,,,,3,0,,,2,0,0,5,,0,0,,,0,0
0000070887000062006-03-29T23:44:422006-03-29T23:44:425401000003,
192.168.79.144,1 0.100.0.109,7088700006@PTT.com,5401000003,
Continued

2-16

68P09278A31-A
FEB 2007

PoC Billing Guide

Schema for Call Records

UDR generated by CCSW11

54,2006-03-29T23:44:42,0,,,00000708870 0006,,242,214,0,1,WMS-SWITCH
,,,0,,,,,,3,0,,,2,0,1,1,,0,0,,,0,0
0000070887000062006-03-29T23:45:122006-03-29T23:45:125401000004,
192.168.79.144,1 0.100.0.109,7088700006@PTT.com,5401000004,54,
2006-03-29T23:45:12,0,,,00000708870 0006,,242,214,0,1,WMS-SWITCH
,,,0,,,,,,3,0,,,2,0,1,1,,0,0,,,0,0

Differentiating between barge calls and between a barge and a

group call
The customer can use a combination of elds to differentiate between barge calls with the
same id and between a barge and a group call.
The combination of eld 1 and eld 5 are unique to each call. The eld 26 PTT_service_type
indicates if the type of call is a barge call or a group call.

68P09278A31-A

2-17
FEB 2007

Schema for Activity Records

Chapter 2: User Data Records

Schema for Activity Records

This section explains the UDR elements used in the Activity Record.

UDR schema for Activity Records

The Activity Record uses the following format:
Target_MIN,startTime,endTime,Call_Id,NAS_Address:,FramedIPAddress,
UserName,Unique_Call_Id,
Vendor_ID,BWGMT_Offset,Source_ MIN/IMSI,Source_MDN,Target_MIN/IMSI,Target_MDN,
Delta_Acct_Output_Octets,Delta_Acct_Input_Octets,BW_Delta_Session_Duration,,
IP_Tech:,PTT_CntSw_ID,PTT_Group_ID,PTT_Called_IP,Reason_Ind,EndTime,
SID,BW_Call_Orig_Cell_IDBase Station_ID,BW_Call_Dest_Cell_ID:,BW_Switch_ID(NID),
PTT_Service_Type,Presence_State,Subscriber_Type,Class_Of_Service,Activity_Type,
Referred_By,Total_Talk_Time,Total_Listen_Time,Wholesale_Name,Enterprise_name,
ESN,Prepaid_Result,GCI,Source_SIP,URITarget_SIPURI,Ptx_successful_files_count,
Ptx_unsuccessful_files_count,Ptx_octet_sent

Record_IDs are Target_MIN,startTime,endTime,Call_Id.

Table 2-3 UDR schema for Activity Records

Field
No.

UDR Element

Type (Length
in Bytes)

Contents

Example

Record_ID

String (64)

Target_MIN, startTime,
endTime, Call_Id

00000978654354520011
108T16:29:412001110
8T16:29:4136AAACCCD
D

NAS_Address

String (15)

Primary IP address of the PoC

Application Server generating
the UDR record (Primary IP
address is address of the EMS
System).

66.123.22.33

FramedIPAddress

String (15)

IP address of the subscriber.

66.123.45.22
Continued

2-18

68P09278A31-A
FEB 2007

PoC Billing Guide

Schema for Activity Records

Table 2-3 UDR schema for Activity Records (Continued)

Field
No.

UDR Element

Type (Length
in Bytes)

Contents

Example

UserName (name of
user represented by this
UDR)

String (64)

value=username@xyz.com

[Default NAI]@ptt.com

Call_Id

String (10)

Report identication number.

36AAACCCDD

Vendor_ID

String (6)

Parse Vendor ID from Call ID.

36

StartTime

String (19)

PoC call start time in GMT

formatDate/time.

20021108T9:32:23

BWGMT_Offset

String (10)

Time offset in seconds of local

time referenced to GMT. Local
timezone must reect timezone
of handset at start of call.

Null SID is not received

Source_MIN

String (15)

MIN of the call originator

Null

10

Source_MDN

String (15)

MDN of call originator

Null

Same as MIN until LNP takes place

11

Target_MIN

String (15)
zero padded
on left

MIN of handset represented by

this UDR.

000009786543545

For activity type 3 and 4, MDN of the subscriber is populated in Target_MIN eld since
MIN of the subscriber is not available.
12

Target_MDN

String (15)

MDN of handset represented

by this UDR.

Null

Same as MIN until LNP takes place

13

Delta_Acct_Output_
Octets (PTTIs835UE)

Integer (15)

Octets Sent (SIP Octets) from

server to handset.

3214

14

Delta_Acct_Input_ Octets
(PTTIs835UE)

Integer (15)

Octets Received (SIP Octets)

from handset to server.

2233

Continued

68P09278A31-A

2-19
FEB 2007

Schema for Activity Records

Table 2-3
Field
No.
15

Chapter 2: User Data Records

UDR schema for Activity Records (Continued)

UDR Element
BW_Delta_Session_
Duration (PTTIs835UE)

Type (Length
in Bytes)

Contents

Example

Integer (20)

Duration of PoC call for this

user in seconds always 0 in
this le.

16

IP_Tech:

Integer (1)

Identies Simple IP, Mobile IP,

or another technology:
1= Simple IP
2= Mobile IP
Always 1

17

PTT_CntSw_ID

String (10)

Unique identier for Control

Switch.

PTTCS1.MA

18

PTT_Group_ID

String (64)

Called Party or Group Name =

username

Null

19

PTT_Called_IP

String (15)

IP address of the called party

(only used for PointToPoint
calls.

Null

20

Reason_Ind

Integer (2)

Indicates how the

session was ended:
0 = Maintenance Record
1 = Call completed Normally
2 = Abnormal Disconnect
3 = Unconnected
Network Failure
4 = Unconnected
Invalid Address
5 = Call ended due to RTP
timer expired (dark hole)
6 = Insufcient fund
7 = Blocked Call

6+0

21

Event_Timestamp

String (19)

GMT Format.

Null

22

SID

String (4)
hex value

System ID taken from the

3GPP2_BSID value which is a
combination of SID, NID, and
Base Station ID where each
item is encoded using four
hexadecimal upper case ASCII
characters.

Null

23

BW_Call_Orig_Cell_I
DBase Station ID

Null

Cell ID for Call originator at

time call is started.

Null

Null

Cell ID for this user at time call

is started.

Null

Null

ID parsed from BSID of this

user.

Null

24
25

BW_Call_Dest_Cell_I D:
BW_Switch_ID(NID)

Continued

2-20

68P09278A31-A
FEB 2007

PoC Billing Guide

Schema for Activity Records

Table 2-3 UDR schema for Activity Records (Continued)

Field
No.

UDR Element

26

PTT_Service_Type

27

Type (Length
in Bytes)

Contents

Example

PoC Type:
1 = PointtoPoint
2 = Group
3 = Acct
4 = Ad-hoc Group
5 = Alert
6 = NNI Point-to-Point
7 = NNI Group
8 = NNI Ad-hoc Group
9 = NNI Alert

NoOfGrantedFloorControl Integer (2)

Indicates the number of

oor control granted to
the user during a call.
For activity record the value is
zero.

28

Original_dialed_digits

String (128)

The number originally dialed

by the caller

Null

29

Translated_dialed_digits

String (128)

The digits after number

translation to get the original
dialed number in E.164 format.

Null

30

Subscriber_Type

Integer (1)

Type of connection
for the subscriber:
1 Prepaid subscriber
2 Postpaid subscriber

31

Presence_State

Integer (1)

Present state of the subscriber:

0 = Not applicable
for call records
1 = Available
2 = Busy
3 = On the phone
4 = On a data session
5 = Out of ofce
6 = Do not disturb
7 = Not available

Integer (1)

This eld contains a valid value only when the activity type is 3 or 18 otherwise for all
activity records value is 0.
32

Class_Of_Service

Integer (1)

Indicates subscribers
privilege services:
1 = Legacy presence
2 = No presence
3 = Premium service

Continued

68P09278A31-A

2-21
FEB 2007

Schema for Activity Records

Table 2-3
Field
No.
33

UDR Element
Activity_Type

Chapter 2: User Data Records

UDR schema for Activity Records (Continued)

Type (Length
in Bytes)
Integer (1)

Contents

Example

Indicates the type of activity

record.

1 Record for register

2 Record for deregister

3 User settable presence

update

4 User initiated presence

update

5 Buddy List Lookup

6 Group List Look up

7 Buddy Add

8 Buddy Modify

9 Buddy Delete

10 Group Add

10

11 Group Delete22 Group

member list NOTIFY

11

12 GroupBuddy Add

12

13 Group Rename

13

16 Buddy Presence Push

16

17 Group Presence Push

17

18 Presence State
Update NOTIFY response
of server to user settable
presence request

18

19 POC Alert Msg Response

Response to the Alter MSG
sent)

19

20 PUBLISH Response
to the PUBLISH Message,
which is used to update the
handset specic settings onto
the server

20

21 Record for failed

registration

21

23 Group member list

NOTIFY

23

24 Group member list for a

specic group

24

25 Group member delete

25
Continued

2-22

68P09278A31-A
FEB 2007

PoC Billing Guide

Schema for Activity Records

Table 2-3 UDR schema for Activity Records (Continued)

Field
No.

UDR Element

Type (Length
in Bytes)

Contents

Example

26 PRESENCE_PUBLISH
Subscriber sends OMA
presence PUBLISH

26

27 PRESENCE_SUBSCRIBE
Subscriber sends OMA
presence SUBSCRIBE

27

28 PRESENCE_NOTIFY
Presence server sends
OMA presence NOTIFY to the
subscriber

28

34

Referred_By

String (15)

MDN of user who referred

this party into the call.
This eld is set only if a new
user is added through Add
Request, otherwise value is
NULL.

9786543545

35

Total_Talk_Time

Integer (5)

Total seconds in call for which

this call leg had oor control.

NULL

36

Total_Listen_Time

Integer (5)

Total seconds in call for which

this call leg was on the call and
another leg had the oor.

NULL

37

Wholesale_Name

String (64)

Identies the type of customer

in billing system.

wholesale1

38

Enterprise_name

String (64)

Enterprise name of the

subscriber.

enterprise1

39

ESN

String (15)
zero padded
on left

ESN/MeID from Active

Directory stored at
provisioning time.

000006106966302

40

Prepaid_Result

Integer (1)

Identies the result of a

prepaid operation for the
subscriber in a prepaid call.
This eld contains valid values
only in the call records for
prepaid calls. Following are
the possible values of this eld.
0 = Not applicable
1 = Insufcient balance
2 = Debit not required
3 = Debit required
4 = Prepaid failure
5 = ECF unavailable

Continued

68P09278A31-A

2-23
FEB 2007

Schema for Activity Records

Table 2-3
Field
No.
41

42

Chapter 2: User Data Records

UDR schema for Activity Records (Continued)

UDR Element
GCI

Type (Length
in Bytes)
String (128)

Source_SIPURI

String (128)

Contents
Identies the cell ID of the
user which includes the:

Country Code

Network Code

LAC and

Cell ID

Identies the URI of the Caller.

This eld contains URI only if
the caller is congured with
the URI otherwise the value is
NULL.

Example
NULL

user1@mot.com

This eld contains valid values in activity records for register, deregister, PUBLISH, and
MESSAGE. For all other activity records, value is NULL.
43

Target_SIPURI

String (128)

Identies the URI used by

the caller to make a call.
This eld contains URI only if
the caller used URI to originate
the call.

NULL

This eld has a NULL value for all the Activity Records.
44

Ptx_successful_les_
count

Integer

Gives the integer count of total

number of successful le(s)
sent.

45

Ptx_unsuccessful_les
_count

Integer

Gives the Integer count of total

number of unsuccessful le(s)
transfer.

46

Ptx_octet_sent

Integer

Total Octets sent (PTV media)

for PTV activity containing
retransmission of media.

12232

47

Ptx_le_size

Integer

For total size of le(s) sent for

PTV activity.

22242

Continued

2-24

68P09278A31-A
FEB 2007

PoC Billing Guide

Schema for Activity Records

Table 2-3 UDR schema for Activity Records (Continued)

Field
No.
48

UDR Element
Poc_Server_Role

68P09278A31-A

Type (Length
in Bytes)
Integer

Contents
Identies the role of the
server. Following are
the values for this eld:
0 = OMA_POC_DEFAULT,
1 =
OMA_POC_CONTROLLING
(Server role being
just Controlling)
2 =
OMA_POC_PARTICIPATING
(Server role being
just participating)
3 =
OMA_POC_CONTROLLING
_AND_PARTICIPATING (Server
acting as both Controlling and
Participating)

Example
0

2-25
FEB 2007

UDR examples

Chapter 2: User Data Records

UDR examples

This section explains the examples for UDR le from the PoC Control Switch for different PoC
calls and activity record.

Pointtopoint call
Figure 2-1 shows a sample UDR le from the PoC Control Switch is for one PoC call with two
participants:

Figure 2-1

Pointtopoint call record

0000099900000642004-05-03T11:32:122004-05-03T11:32:14000a00306c,
10.232.115.3,10.232.115.13,9990000064@PTT.com,000a00306c,00,2004-05-03T11:32:12,
-1076400,000009990000064,000009990000064,000009990000064,000009990000064,741,1640,
2,1,CCSW,9990000063@PTT.com,10.232.115.13,1,2004-05-03T11:32:14,001C,,,,1,1,
000009990000063,000009990000063,2,0,1,0,,20,15,wholesale1,enterprise1,000006106966302,
0,90802468001C,user1@mot.com,user2@mot.com,2,4,12232,22242,0
0000099900000632004-05-03T11:32:122004-05-03T11:32:15000a00306c,
10.232.115.3,@10.232.115.13,9990000063@PTT.com,000a00306c,00,2004-05-03T11:32:12,
-1076400,000009990000064,000009990000064,000009990000063,000009990000063,1644,406,
3,1,CCSW,9990000063@PTT.com,10.232.115.13,1,2004-05-03T11:32:15,001C,,,,1,0,
000009990000063,000009990000063,2,0,1,0,,,15,20,wholesale2,enterprise1,000006106966302,
0,90802468001C,user1@mot.com,user2@mot.com,2,4,12232,22242,0

Originating
Leg

Terminating
Leg

ag_cn_POC_Billing_Point2PointCallRec.eps

Group call
Figure 2-2 shows a sample UDR le from the PoC Control Switch for one PoC call with three
participants.

2-26

68P09278A31-A
FEB 2007

PoC Billing Guide

UDR examples

Figure 2-2 Group call record

0000090330030092004-05-03T12:30:242004-05-03T12:30:30000a000001,
10.232.115.13,10.232.115.13,9033003009@PTT.com,000a000001,00,2004-05-03T12:30:24,
-14400,000009033003009,000009033003009,000009033003009,000009033003009,972,3632,6,1,
CCSW,g25@PTT.com,,1,2004-05-03T12:30:30,001C,,,,2,1,g25,g25.9033003009,2,0,1,0,,20,15,
wholesale1,enterprise1,000006106966302,0,90802468001C,user1@mot.com,group@mot.com,2,4,
12232,22242,0
0000090330030082004-05-03T12:30:242004-05-03T12:30:30000a000001,
10.232.115.13,10.232.115.13,9033003008@PTT.com,000a000001,00,2004-05-03T12:30:24,
-14400,000009033003009,000009033003009,000009033003008,000009033003008,3687,585,6,1,
CCSW,g25@PTT.com,,1,2004-05-03T12:30:30,001C,,,,2,0,g25,g25.9033003009,2,0,1,0,,15,20,
wholesale1,enterprise1,000006106966302,0,90802468001C,user1@mot.com,group@mot.com,2,4,
12232,22242,0
0000090330030052004-05-03T12:30:242004-05-03T12:30:30000a000001,
10.232.115.13,10.232.115.13,9033003005@PTT.com,000a000001,00,2004-05-03T12:30:24,
-14400,000009033003009,000009033003009,000009033003005,000009033003005,3687,585,6,1,
CCSW,g25@PTT.com,,1,2004-05-03T12:30:30,001C,,,,2,0,g25,g25.9033003009,2,0,1,0,,15,20,
wholesale1,enterprise1,000006106966302,0,90802468001C,user1@mot.com,group@mot.com,2,4,
12232,22242,0

Originating
Leg

Terminating
Leg 1

Terminating
Leg 2

ag_cn_POC_Billing_GroupCallRec.eps

Adhoc call
Figure 2-3 shows a sample UDR le from the PoC Control Switch for an Adhoc PoC call with
three participants.

Figure 2-3 Adhoc call record

0000090550051012004-05-11T05:52:422004-05-11T05:52:46000a000002,
10.232.115.3,10.232.115.13,9055005001@PTT.com,000a000002,00,2004-05-11T05:52:42,
-1076400,000009055005101,000009055005001,000009055005101,000009055005001,977,2760,
4,1,CCSW,adhoc@PTT.com,,1,2004-05-11T05:52:46, 001C,,,,4,1,adhoc,adhoc.9055005001,
2,0,1,0,,20,15,wholesale1,enterprise1,000006106966302,0,90802468001C,user1@mot.com,
adhoc@mot.com,2,4,12232,22242,0
0000099900001632004-05-11T05:52:422004-05-11T05:52:46000a000002,10.232.115.3,
10.232.115.13,9990000063@PTT.com,000a000002,00,2004-05-11T05:52:42,-1076400,
000009055005101,000009055005001,000009990000163,000009990000063,2765,585,4,1,
CCSW,adhoc@PTT.com,,1,2004-05-11T05:52:46,001C,,,,4,0,adhoc,adhoc.9055005001,2,
0,1,0,,15,20,wholesale1,enterprise1,000006106966302,0,90802468001C,user1@mot.com,
adhoc@mot.com,2,4,12232,22242,0
0000099900001642004-05-11T05:52:422004-05-11T05:52:46000a000002,10.232.115.3,
10.232.115.13,9990000064@PTT.com,000a000002,00,2004-05-11T05:52:42,-1076400,
000009055005101,000009055005001,000009990000164,000009990000064,2765,585,4,1,
CCSW,adhoc@PTT.com,,1,2004-05-11T05:52:46,001C,,,,4,0,adhoc,adhoc.9055005001,2,
0,1,0,,15,20,wholesale1,enterprise1,000006106966302,0,90802468001C,user1@mot.com,
adhoc@mot.com,2,4,12232,22242,0

Originating
Leg

Terminating
Leg 1

Terminating
Leg 2

ag_cn_POC_Billing_AdhocCallRec.eps

Activity record
Figure 2-4 shows an activity record that is representative of all the activity types except for a
different value for activity type eld.

68P09278A31-A

2-27
FEB 2007

UDR examples

Chapter 2: User Data Records

Figure 2-4 Activity record

0000099900000642004-05-03T11:31:592004-05-03T11:31:59000a000001,10.232.115.3,
10.232.115.13,9990000064@PTT.com,000a000001,00,2004-05-03T11:31:59,,,,
000009990000064,,243,201,0,1,CCSW,,,0,,,,,,3,0,,,1,0,1,1,,0,0,wholesale1,
enterprise1,000006106966302,0,,user1@mot.com,,0,0,0,0,0
0000099900000642004-05-07T11:26:222004-05-07T11:26:22000a000008,10.232.115.3,
10.232.115.113,9990000064@PTT.com,000a000008,00,2004-05-07T11:26:22,,,,
000009990000064,,214,165,0,1,CCSW,,,0,,,,,,3,0,,,1,0,1,2,,0,0,wholesale1,
enterprise1,000006106966302,0,,user1@mot.com,,0,0,0,0,0
0000099900000642004-05-07T11:23:262004-05-07T11:23:26000a000005,10.232.115.3,
10.232.115.113,9990000064@PTT.com,000a000005,00,2004-05-07T11:23:26,,,,
000009990000064,,0,0,0,1,CCSW,,,0,,,,,,3,0,,,1,3,0,3,,0,0,,,000006106966304,0,,,,,
0,0,0,0,0
0000099900000642004-05-07T11:23:262004-05-07T11:23:26000a000005,10.232.115.3,
10.232.115.113,9990000064@PTT.com,000a000005,00,2004-05-07T11:23:26,,,,
000009990000064,,0,0,0,1,CCSW,,,0,,,,,,3,0,,,1,0,0,4,,0,0,,,000006106966304,0,,,,,
0,0,0,0,0

Register

De-register

User Settable
Presence

User Initiated
Presence

ag_cn_POC_Billing_ActivityRec.eps

2-28

68P09278A31-A
FEB 2007

PoC Billing Guide

Corrupted or missing SID

Corrupted or missing SID

This section explains the scenarios for corrupted or missing SIDs.

Scenarios
There are several cases where the handset is required to pass a valid SID to calculate GMT
offset, but the value sent to the Control Switch may not be a recognized, valid SID for the
network or the value may be missing. These scenarios are outlined Table 2-4:

Table 2-4 Corrupted/missing SID scenarios

SID

GMT
Offset

3 call leg torn

down

99

3 call leg torn

down

3 call leg torn

down

99

3 call leg torn

down

Called Party: Failure response to SIP INVITE

with missing SID

whatever the
failure response
would indicate

Called Party: Failure response to SIP INVITE

with invalid SID

99

whatever the
failure response
would indicate

Scenario
Calling Party: SIP INVITE with no SID
Calling Party: SIP INVITE with invalid SID
Called Party: 200 OK with no SID
Called Party: 200 OK with invalid SID

68P09278A31-A

Reason Indicator

2-29
FEB 2007

Alert Call or Alert Message

Chapter 2: User Data Records

Alert Call or Alert Message

Alert call is a call established when an MPTT caller alerts a callee. A call record is generated
with eld 26 PTT_Service_Type having value set to 5, if UDR version is 7 and above otherwise
value is 1.
In case of an IPA (Instant Personal Alert) for OMA subscriber an activity record is generated
since sending Alert message (MESSAGE) to other party is an event based procedure. This is
indicated in the activity record of UDR in eld 33 Activity_type with value 19.

2-30

68P09278A31-A
FEB 2007

PoC Billing Guide

Disconnect reasons

Disconnect reasons

This section explains the indicators and disconnect reasons with their description.

Release indicators
Following are the denitions of all the release indicators.

Table 2-5 Release indicators

Indicator

Description

Value

Maintenance_record

The user registered with the server.

Normal Call Clearing

The call leg was disconnected after it had

transitioned into the connect state.
Typically when the user sends the BYE request
to the server and receives 200 OK response,
the call leg is said to be disconnected normally.
The other scenarios where normal clearing would happen is:

Abnormal Disconnect

Unconnected Network
Failure

A oor timeout, where the call legs are connected but the
server send BYE message to both the parties of the call.

The user receives BYE message from the server because

of the other party in the call has disconnected normally.

The PoC server experienced the timeout. This could be caused

by various reasons such as:

no answer from the person called

the callee is busy in another call

The call is not connected due to:

The network failure

PoC server experienced a problem with the network.

The typical problem for this could be:

Unconnected Invalid
Address

The server unable to reach the person called

The server has lost connection with the HLR.

The call is not connected because of one of the following:

The caller or person called is not registered with the

server

The subscriber number is not present in the database

Continued

68P09278A31-A

2-31
FEB 2007

Disconnect reasons

Table 2-5

Chapter 2: User Data Records

Release indicators (Continued)

Indicator

Description

Value

The group is not a valid group name in the case of a

group call

RTP timer expired

The user experience the Radio link interface failure during

the connected call.

Insufcient funds

The Prepaid user does not have enough currency to talk.

Blocked calls

The caller is present in the blocked list of callee.

Scenarios
There are several reasons why a call is disconnected. These scenarios are outlined below:

Table 2-6

Disconnect scenarios
Description

Disconnect Reason

Subscriber A makes a PTP call to subscriber B. Call is connected and

disconnected normally.

1 for both parties

Subscriber A makes a PTP call to

subscriber B. Subscriber A has invalid SID.
Call is disconnected because invite is sent with invalid SID.

3 for the caller only

Subscriber A makes a PTP call to

subscriber B. Subscriber B has invalid SID.
Call is disconnected as server received 200 OK with invalid SID.

3 for both parties

Subscriber A makes an alert call to subscriber B. Subscriber B does not

answer the call and timer times out.

2 for both parties

Subscriber A makes an alert call to subscriber B. Subscriber B ignores

the call.

2 for both parties

Subscriber A makes a call to subscriber B.

Subscriber B is registered with the server but presently
the party is out of the network.

3 for both parties

Subscriber A makes a PTP call to subscriber B who is not registered

with the server.

4 for the caller only

Subscriber A makes a PTP call to subscriber B. The call is connected.

Subscriber B goes out of network and the call is disconnected because
of a Radio Interface failure.

1 for the caller 5 for the callee

Subscriber A makes a group call to a group which does not exist.

4 for the caller only

A and B are registered with the server, however

the server has lost the connection with ADHLRs.
Subscriber A makes a PTP call to Subscriber B and the call
fails.

0 for both parties for the

registration and 3 for the caller
only

Subscriber A makes a PTP call to a prepaid

subscriber B who is registered with the network.
The call fails because Subscriber B had less currency than the
minimum available.

2-32

6 for callee
1 for caller

68P09278A31-A
FEB 2007

PoC Billing Guide

Disconnect reasons

Table 2-6 Disconnect scenarios (Continued)

Description
Subscriber A makes call to Subscriber B who has included Subscriber A
in the blocked list.

68P09278A31-A

Disconnect Reason
7 for the Caller

2-33
FEB 2007

Time measurement

Chapter 2: User Data Records

Time measurement

This section explains the timestamps, denitions for call time and the call duration.

Timestamps
The timestamps used in the whole system is the time that is set on the ccswitch machine, which
is NTP synchronized with the EMS. In turn the server is synchronized with the external clock,
which is UTC (Universal Coordinated Time). This would mean that the absolute time on the
ccswitch, is the time settings on the server, which is NTP synchronized with the external clock.

Denitions for call time

Following are some of the denitions related to the call time.

Call Start Time The time at which the server received the INVITE request from the
calling party.

Call Connect Time The time at which the server received 200 OK response from the
called party.

Call Clear Time The time at which the server responds with a 200 OK for the BYE request
from user or when server sends BYE message to the user.

Call duration
The time difference between clearing the call (server receiving/sending SIP message BYE) to
connecting the call (server receiving/sending SIP 200 OK response to a prior sent / received
SIP INVITE message).
If there are unconnected calls, the duration of the call is zero.

2-34

68P09278A31-A
FEB 2007

Chapter

3
Congurable UDR elds

There are about 48 UDR elds populated in the UDR le. Every customers do not use all the
elds for their billing purposes. So it is an overhead to encode all the elds when they are
not needed for the customers billing client.
The Congurable UDR Fields feature allows the user to choose from the UDR elds what the
billing clients actually needs. Hence the user is able to encode only desired elds.
The user enables or disables the elds to be encoded or decoded through TL1 (Transaction
Language1) or Prov UI (Provisioning User Interface). Only the enabled elds are considered for
encoding into the UDR le.
Example: The user enables or disables pttType UDR elds by typing the following command at
the TL1 command prompt:
WMS-TL1>ED-udr_config::pttType:C1::is_enabled=true;
WMS-TL1>ED-udr_config::pttType:C1::is_enabled=false;
To check if pttType eld is enabled for encoding, the following command is used:
WMS-TL1>RTRV-udr_config::pttType:C1::is_enabled;
A header le named UDRHeaderFile.cfg is generated after enabling or disabling the elds.
This le contains the eld names and formats of the enabled elds separated by colon (:) a new
line separates each eld. Only values for these elds are in the UDR. The decoding utility reads
from the UDRHeaderFile.cfg and the UDR le to generate the decoded UDR information.
This le is created in the same directory where the UDR les are generated. The user cannot
tamper or delete this le as it results in malfunctioning of the decode utility. The user can
take the backup of UDRHeaderFile.cfg with the UDR generated before enabling or disabling
the elds. Otherwise, decoding the UDR le is not proper as the UDRs generated uses the
old UDRHeaderFile.cfg.

68P09278A31-A
FEB 2007

3-1

Time measurement

3-2

Chapter 3: Congurable UDR elds

68P09278A31-A
FEB 2007

Chapter

4
Congurable UDR formats

The UDR eld values are displayed in xed format for each eld of the UDR. The value format
expected for a UDR eld is different for each billing system (Example: Date format: mm-dd-yy).
The UDR format was not congurable through PROV UI till UDR version 6.
The Congurable UDR format feature allows the exibility to choose the UDR format to be
displayed in the UDR. Hence, the user is able to get the desired format of eld value in the
UDR. UDR eld congurable format option is not required for all the elds in the UDR. This
functionality is offered through the TL1 interface.
The user cannot add extra elds to the UDR formats, nor delete any elds. The user can only
select the format by updating the eld version in the billingnbi_udr_eld_cong table.
Type the following command to get the maximum number of versions (formats) for a eld:
WMS-TL1>RTRV-udr_config::

startTime:C4::max_version;

Type the following command to view the format for pttType Version 1 eld format:
WMS_TL1>RTRV-udr_field_format::" pttType-1":C2::

format;

Type the following command to view the format for start time Version 3 eld format:
WMS_TL1>RTRV-udr_field_format::"startTime-3":C3::format;
Type the following command to update the desired format for a UDR eld:
WMS-TL1>ED-udr_config::startTime:C6::version=3;
Congurable UDR eld format option is implemented for following elds:

PttType

StartTime

EndTime

Sourcemin

Sourcemdn

Targetmin

Targetmdn

Disconnectreason

68P09278A31-A
FEB 2007

4-1

PttType

Chapter 4: Congurable UDR formats

PttType

PttType eld is service type supported (Example: POINT_TO_POINT, GROUP, ACCOUNT) and
the options are:

Version 1 Supported types are:

POINT_TO_POINT
GROUP
ACCOUNT
In Version 1, AD-HOC GROUP call is mapped to GROUP.

Version 2 Supported types are:

POINT_TO_POINT
GROUP
ACCOUNT
AD-HOC GROUP

Version 3 Supported types are:

POINT_TO_POINT
GROUP
ACCOUNT
AD-HOC GROUP
ALERT
NNI POINT TO POINT
NNI GROUP
NNI AD-HOC GROUP
NNI ALERT

4-2

68P09278A31-A
FEB 2007

PoC Billing Guide

StartTime and EndTime

StartTime and EndTime

StartTime and EndTime are date formats supported (Example: 2005-11-11T12:14:25).

Version 1 Date is displayed as gmtTime,%Y-%m-%dT%H:%M:%S format

Version 2 Date is displayed as localTime,%Y-%m-%dT%H:%M:%S format

Version 3 Date is displayed as gmtTime,%d-%m-%YT%H:%M:%S format

Version 4 Date is displayed as localTime,%d-%m-%YT%H:%M:%S format

68P09278A31-A

4-3
FEB 2007

SourceMIN and SourceMDN

Chapter 4: Congurable UDR formats

SourceMIN and SourceMDN

SourceMIN and SourceMDN are padding formats supported (Example: 000002220001103).

4-4

Version 1 Zeros are padded on the LEFT as 00000XXXXXXXXXX format (where Xs are
MIN/MDN)

Version 2 Zeros are padded on the RIGHT as XXXXXXXXXX00000 format (where Xs are
MIN/MDN)

Version 3 No Padding as XXXXXXXXXX format (where Xs are MIN/MDN)

68P09278A31-A
FEB 2007

PoC Billing Guide

TargetMIN and TargetMDN

TargetMIN and TargetMDN

TargetMIN and TargetMDN are padding formats supported (Example: 000002220001103).

Version 1 Zeros are padded on the LEFT as 00000XXXXXXXXXX format (where Xs are
MIN/MDN)

Version 2 Zeros are padded on the RIGHT as XXXXXXXXXX00000 format (where Xs are
MIN/MDN)

Version 3 No Padding as XXXXXXXXXX format (where Xs are MIN/MDN)

68P09278A31-A

4-5
FEB 2007

DisconnectReason

Chapter 4: Congurable UDR formats

DisconnectReason

DisconnectReason is session disconnect reasons supported (Example: CALL_COMPLETED).

Version 1 Following values for DisconnectReason are supported:

0 MAINTENANCE_RECORD
1 CALL_COMPLETED
2 ABNORMAL_DISCONNECT
3 UNCONNECTED_NETWORK_FAILURE
4 UNCONNECTED_INVALID_ADDRESS
5 RTP_TIMER_EXPIRED
In Version 1, INSUFFICIENT_FUNDS is mapped to ABNORMAL_DISCONNECT.

Version 2 Following value is supported with above values:

0 MAINTENANCE_RECORD
1 CALL_COMPLETED
2 ABNORMAL_DISCONNECT
3 UNCONNECTED_NETWORK_FAILURE
4 UNCONNECTED_INVALID_ADDRESS
5 RTP_TIMER_EXPIRED
6 INSUFFICIENT_FUNDS

In version2, INSUFFICIENT FUND is given an explicit value 6, which in

the earlier version was mapped to ABNORMAL_DISCONNECT.

Also, in version1 and version 2, BLOCKED_CALL is mapped to

ABNORMAL_DISCONNECT.

Version 3 Following value is supported with above values:

0 MAINTENANCE_RECORD
1 CALL_COMPLETED
2 ABNORMAL_DISCONNECT
3 UNCONNECTED_NETWORK_FAILURE

4-6

68P09278A31-A
FEB 2007

PoC Billing Guide

DisconnectReason

4 UNCONNECTED_INVALID_ADDRESS
5 RTP_TIMER_EXPIRED
6 INSUFFICIENT_FUNDS
7 BLOCKED CALL

In Version 3, BLOCKED CALL is mapped to 7, which was earlier mapped to

ABNORMAL_DISCONNECT.

Figure 4-1 Selection of the elds in congure UDR

68P09278A31-A

4-7
FEB 2007

DisconnectReason

Figure 4-2

4-8

Chapter 4: Congurable UDR formats

Congurable UDR eld format

68P09278A31-A
FEB 2007

Chapter

5
Provisioning

This chapter deals with provisioning the billing interface.

68P09278A31-A
FEB 2007

5-1

Provisioning the Billing Interface

Chapter 5: Provisioning

Provisioning the Billing Interface

This section explains the steps to be followed for provisioning the billing interface.

Instructions
The PoC Control Switches are provisioned to create the Call Detail Record (CDR) les in the
Motorola SoftSwitch Server (NMHost).

Procedure 5-1

Provisioning the Billing Interface

Select OAMP>CDRCP to access the CDR Collection Points screen as

shown in Figure 5-1.

Congure the CDR Collection Point (CDRCP) process.

Select the CDR CP process that is to be provisioned and congure the

following information:

Port number that the CDR CP process listens for the data from the
Control Switch

Partition where CDRs are written

Start and end sequence for CDR numbers

Frequency of acknowledging to the CCSwitch process that the records

have been received

Frequency with which CDR records are rotated

Frequency to write CDRs to disk

Output format must be csv

Select OAMP>Billing>Add>PTT to access the Billing Conguration

screen as shown in Figure 5-2.

Specify information related to the billing north bound interface including:

Domain Name

File Prex Default Value is WPx where x is the number for this
control switch.

CDR CP name CDRCP process(es) that this billing NBI process

receives les from

UDR version Version of the UDR

Continued

5-2

68P09278A31-A
FEB 2007

PoC Billing Guide

Provisioning the Billing Interface

Procedure 5-1 Provisioning the Billing Interface (Continued)

6

Click INSERT.

Select OAMP>Billing>Protocols to access the Congure Billing

Protocol screen as shown in Figure 5-3.

Specify the billing protocol as BILL_FOR_PTT.

Click INSERT.

Figure 5-1 CDR Collection Points

ag_cn_POC_Billing_CDRCollectionPointScrn

68P09278A31-A

5-3
FEB 2007

Provisioning the Billing Interface

Chapter 5: Provisioning

Figure 5-2 Billing Conguration

ag_cn_POC_Billing_BillConfigScrn

5-4

68P09278A31-A
FEB 2007

PoC Billing Guide

Provisioning the Billing Interface

Figure 5-3 Congured Billing Protocols

ag_cn_POC_Billing_ConfiguBillingProtocols

68P09278A31-A
FEB 2007

5-1

Provisioning the Billing Interface

5-2

Chapter 5: Provisioning

68P09278A31-A
FEB 2007

*68P09278A31-A*
68P09278A31-A

Technical
Information

POC BILLING GUIDE

SOFTWARE RELEASE 6.1.X.X
POC
US/HONG KONG, ROW

ENGLISH
FEB 2007
68P09278A31-A

POC BILLING GUIDE

SOFTWARE RELEASE 6.1.X.X
POC
US/HONG KONG, ROW

ENGLISH
FEB 2007
68P09278A31-A

Standard Printing Instructions

Part Number

68P09278A31-A

Manual Title

PoC Billing Guide

Date

FEB 2007

CSD/CND (US)
Binder

Printing

Finishing

3 Slant D-ring binder - letter size (11.75 in x 11.5 in) white PVC.

Capacity depends on size of document. (no larger than 3 in).

Clear pockets on front and spine.

Cover / spine text overprinted onto Motorola cover stock.

Body- printed double sided onto white letter size (8.5 in x 11 in) 70 lb.

Shrink wrap contents.

CMM labeling and disclosure table

The Peoples Republic of China requires that Motorolas products comply with
China Management Methods (CMM) environmental regulations. (China
Management Methods refers to the regulation Management Methods for
Controlling Pollution by Electronic Information Products.) Two items are used to
demonstrate compliance; the label and the disclosure table.
The label is placed in a customer visible position on the product.

Logo 1 means that the product contains no substances in excess of the

maximum concentration value for materials identified in the China
Management Methods regulation.

Logo 2 means that the product may contain substances in excess of the
maximum concentration value for materials identified in the China
Management Methods regulation, and has an Environmental Friendly
Use Period (EFUP) in years, fifty years in the example shown.

Logo 1

Logo 2

The Environmental Friendly Use Period (EFUP) is the period (in years) during
which the Toxic and Hazardous Substances (T&HS) contained in the Electronic
Information Product (EIP) will not leak or mutate causing environmental pollution
or bodily injury from the use of the EIP. The EFUP indicated by the Logo 2 label
applies to a product and all its parts. Certain field-replaceable parts, such as
battery modules, can have a different EFUP and are marked separately.
The Disclosure Table is intended only to communicate compliance with China
requirements; it is not intended to communicate compliance with EU RoHS or any
other environmental requirements.

2007 Motorola, Inc.

68P02901W00-E