Cisco Cisco Packet Data Gateway (PDG)

 

▄  SaMOG Administration Guide, StarOS Release 19 

The SaMOG Gateway uses the custom24 GTPP dictionary to generate SGW and SGSN CDRs. 

The following table lists the configuration commands related to creating and formatting the CDRs. These commands 
appear at different portions of the system configuration file. 



 

gttp group <name>

 - These are commands specified within the billing context.  

Trigger-related Configuration 

gttp group<name>

 in Billing Context 

 

Enabled 

When this trigger is disabled, no partial record closure occurs when 
the volume limit is reached. 

 

Enabled 

When this trigger is disabled, no partial record closure occurs when 
the configured time limit is reached. 

 

Enabled 

When this trigger is disabled, container closure does not occur for a 
tariff-time change. 

 

Enabled 

Disabling this trigger ignores a qos-change and does not open a new 
CDR for it. 

CDR Attribute-related Configuration 

 

No 

Includes the Diagnostic field in the CDR that is created when PDP 
contexts are released. 

 

No 

Specifying this option results in mandatory "Duration" field in the 
CDR to be recorded in milliseconds rather than seconds. 

 

No 

Specifying this option includes optional fields "Local Record 
Sequence Number" and "Node-ID" in the CDR. Since the "Local 
Record Sequence Number" has to be unique within one node 
(identified by "Node-ID"), "Node-ID" field will consist of sessMgr 
Recovery count + AAA Manager identifier + the name of the GSN 
service.  
Since each AAA Manager generate S-CDRs independently, the 
"Local Record Sequence Number" and "Node ID" fields will 
uniquely identify a CDR. 

 

Enabled 

Specifying this option includes field "MSISDN" in the CDR. 

gtpp attribute node-id-suffix 
<string>

 

No 
String 
between 1 
and 16 
characters 

Specifies the string suffix to use in the NodeID field of S- CDRs. 
With the default setting of "no", the SaMOG Gateway uses the 
GTPP context name for the Node ID field.