Collapse AllExpand All

6.2.5.2. Configurable Elements Previous topic Parent topic Child topic Next topic

IMPORTANT:
The indication "(n-digit)" in an element refers to the possible infor­mation content (digits or characters) of the element in question. A shorter or longer length can be configured for the elements unless the entry in the table reads "max. n-digit".

Example 1:

The element CHRGEE (party responsible for connection costs) with the statement "(6-digit)" can, for  example, be configured to be four digits. This is useful if the party responsible for connection costs (paying party) has only four digits. On the other hand, the field can also be configured as eight digits if, for example, the DP application is expecting an 8-digit field. In this case, 6 digits contain the actual value and the remaining digits contain the fill character.
For certain elements, you must use AMO TEXT to set up text strings for all possible values (while taking the number of possible digits into consideration).

Example 2:

For the element OUTDAYC (date of the output: name of the day of the week),
"MONDAY ", "TUESDAY ", "WEDNESDAY ", "THURSDAY " and so on (each 10 characters long)
 or "MO", "TU", "WE", "TH", and so on
 or the short form  "1", "2", "3", "4", and so on
can be set up as values.

Configurable Elements

Table 45. Configurable Elements

Name
Description
ACCTCODE
The call's account code. The user enters the account code either before or during the call (12-digit)
ACDAGTID
ACD Agent ID (6 characters). ID of an ACD Agent for an incoming or outgoing answered call
ACDGRPID
ACD Group ID (3 Zeichen). Group ID for an ACD call
ADPLOAD
Processor load of the ADP in 1/10 percent. This is the average load over 10 seconds (4-digit). The time stamp, showing when the load was determined, is in the field "end of connection"->ENDDAY (2-digit), ENDMONTH (2-digit), ENDHOUR (2-digit), ENDMIN (2-digit), ENDSEC (2-digit), END10 (1-digit).
AOCTYPE
Type of the call charge accounting message (10-digit)
You can use AMO TEXT to set up text strings for this element, which can have the following values:
Call detail information during the call (D_AOC)
Call detail information when the call ends (E-AOC)
Call detail information when setting up the connection (S_AOC)
ATNDGRNO
Attendant Group (2-digit) (see In the fields for incoming calls are:)
ATTCALLP
Attendant Call Priority - priority of a call in an attendant queue. Only available for ACWinMQ (2 characters)
ATTCALLR
Attendant Intercept Reason - only available for ACWinMQ (2 characters)
ATTCALLT
Attendant Call Type- only available for ACWinMQ (2 characters)
ATTQUEID
Attendant Queue ID - queue ID assigned to a call. Only available for ACWinMQ (2 characters)
BCHLCNT
Number of B channels (max. 2-digit). No longer maintained
BLENBYT
Block length in bytes (5-digit)
BLENREC
Number of records per block (5-digit) (The number of data records in the block with record ID = "AB" or "AI" )
CALCTYPE
Type of billing used (10-digit)
You can use AMO TEXT to set up text strings for this element, which can have the following values:
Pay phone (RURAL) (CLOCK)
Pulse or amounts from CO (PULSES)
Accounting of call charges based on time (WOUT)
CALLEPTY
Called party: number that was dialed by the calling station. (22-digit)
CALLIID
Station ID of the calling party (text parameter STNID is defined in AMO TEXT) (10-digit)
CALLILV0
Node number of calling party (3-digit max.)
CALLILV1
Subdomain number of the calling party (max. 3-digit)
CALLILV2
Domain number of the calling party (max. 2-digit)
CALLIPTY
Calling party: party that initiated the existing connection/segment. (22-digit)
CALLIONI
Originating network ID of calling party
CARRIER
Identifier for the communication network as text string (10-digit, see In the fields for incoming calls are: and In the fields for internal calls are:)
You can use AMO TEXT to set up text strings for this element, which can have the following values:
CARRIER_0 (internal)
CARRIER_1
CARRIER_n
CARRIER_9
CAUSE
Output of the cause of the clearing of a connection (3-digit, see table Meaning of the Values for the Element CAUSE in AMO FTBL)
CHOFCON
Output of the type of connection (10-digit, see In the fields for incoming calls are: and In the fields for internal calls are:)
You can use AMO TEXT to set up text strings for this element, which can have the following values:
Local connection
Long-distance connection
Local connection with exceeded limiting value
Long-distance connection with exceeded limiting value
No entry
Rerouting / Routopt
You can set up the limiting value for the number of the call charge pulses or the connection duration with AMO GRZW.
CHRGUNIT
Call charge units: The units in this field are recalculated from the calculated costs. (5-digit, see In the fields for internal calls are:)
CON10
Call duration: 1/10 seconds (1-digit)
CONCHRG
Output of the costs including sales tax. For calculation in 1/100th (max. 8-digit) For calculation in 1/100000th (max. 12 digits) OpenScape 4000 calculates this value according to the price per pulse set up with AMO TTBL (tariff table administration)
CONCHRN
Output of the net costs without sales tax. For calculation in 1/100th (max. 8 digits) For calculation in 1/100000th (max. 12 digits)
CONHOUR
Call duration: hours (2-digit)
CONMIN
Call duration: minutes (2-digit)
CONNSTEP
All of a connections's CDB records are numbered in order (starting with contents 1), (3-digit).
CONNTYPE
Output of the connection type as text string (10 characters, see In the fields for incoming calls are:).
You can use AMO TEXT to set up text strings for this element, which can have the following values:
Outgoing connections (OUTGO)
Internal connections (INTERN)
Incoming connections (INCO)
Attendant activity (ACACT)
Processor load (LOAD)
CONSEC
Connection duration: seconds (2-digit)
CONSECT
Connection duration, total in tenths of seconds (6-digit)
COPIN
Output of the PIN class (see AMO PERSI) as text string (10 characters)
You can use AMO TEXT to set up text strings for this element, which can have the following values:
No PIN available
PIN Class_1
PIN Class_n
PIN Class_8
CTRDIFF
CDRS difference counter, only CDRS functionality (5-digit)
CTRTOT
CDRS summation counter, only CDRS functionality (5-digit)
DESTLV0
Node number of the new or connected party, (3-digit)
DESTLV1
Subdomain number of the new or connected party, (3-digit)
DESTLV2
Domain number of the new or connected party, (2-digit)
DESTPID
Station ID of the new or connected party. It is not possible to determine the ID for dialed numbers. In this case, "unknown" is output. The text parameter STNID is defined in AMO TEXT (10 digits)
DESTPTY
connected party: Newly selected or through connected destination for a connection (22 digits).
DISPCHRG
Connection charges, including sales tax, shown on display. Calculated during the connection. For calculation in 1/100th (max. 8-digit) For calculation in 1/100000th (max. 12-digit)
DISPCHRN
Connection charges, not including sales tax, shown on display. Calculated during the connection. For calculation in 1/100th (max. 8-digit) For calculation in 1/100000th (max. 12-digit)
DNIS
Text string regarding the called party. Output of the Identification Service Number belonging to the dialed number. The DNIS number is provided by the BREAKIN trunk and refers to the called party (11-digit)
END10
End-of-connection: tenths of seconds (1-digit)
ENDDAY
End-of-connection: day (2-digit)
ENDHOUR
End-of-connection: hour (2-digit)
ENDMIN
End-of-connection: minute (2-digit)
ENDMONTH
End-of-connection: month (2-digit)
ENDSEC
End-of-connection: second (2-digit)
ENDYDAY
End-of-connection: day of year (1...366, 3-digit)
ENDYEAR
End-of-connection: year (4-digit)
EXPENS
Output of the identifier 'Expensive connection' as text string (10-digit)
You can use AMO TEXT to set up text strings for this element, which can have the following values:
Cheap
Expensive
Free A-station
Free B-station
FACA
Values for FX or TTA trunk access on BREAKIN trunk as part of the NI2 PRI service (5-digit)
FACB
Values for FX or TTA trunk access on BREAKOUT trunk as part of the NI2 PRI service (5-digit)
FLAG1
No longer maintained
FLAG2
No longer maintained
GLOBLLV0
Node number of the global leg ID (3-digit), identical to LEGLV0
GLOBLLV1
Subdomain number of the global leg ID (3-digit), identical to LEGLV1
GLOBLLV2
Domain number of the global leg ID (2-digit), identical to LEGLV2
GLOBLSEQ
Sequence number of the global leg ID. A new global call ID is provided only when there is a new connection (8-digit), identical to LEGSEQ
GLOBLV0
Node number of the global call id, (3-digit)
GLOBLV1
Subdomain number of the global call id, (3-digit)
GLOBLV2
Domain number of the global call id, (2-digit)
GLOBSEQ
Global call ID: a number global call ID may only be created when a new connection is set up (8-digit).
HOLDDUR
Total hold time in 1/10 seconds (5-digit)
IDPP
Output of the CDRS station number as text string (10 characters)
You can use AMO TEXT to set up text strings for this element, which can have the following values:
Trunk circuit (TC)
Main PBX tie trunk (MTLC)
Station (STN)
Attendant console (ATND)
INFOTYPE
Type of information (10-digit), If accounting call charges from CO, then units or amounts.
You can use AMO TEXT to set up text strings for this element, which can have the following values:
Amounts from CO (AMO UNT)
Units from CO (UNITS)
INTNBCHA
B channel of the real trunk number of the location that is not recording
INTNLIST
Fictitious trunk number converted from INTNREAL (max. 6-digit, see AMO FBTN)
INTNREAL
Real trunk number of the location that is not recording (see TKNOREAL, 5-digit)
Outgoing connection: A-station PEN or incoming circuit
Incoming connection: B-station PEN or outgoing circuit
Internal connection: same as private automatic branch exchange: B-station PEN
Network-wide: A-station PEN or incoming circuit
INTNTRGR
Trunk number group of INTNREAL (real trunk number of the location that is not recording). If the location that is not recording is a telephone instead of a trunk, this has the value 0 (5-digit)
KEYLV0
Node number of the key line used party, (3-digit)
KEYLV1
Subdomain number of the key line used party, (3-digit)
KEYLV2
Domain number of the key line used party, (2-digit)
KEYPTY
Key line used party: the selected trunk (number) of a multi-trunk equipped with a key phone (22-digit).
LCALLENO
Length of the called number (called party), (2-digit)
LDESTNO
Length of the destination number (2-digit). The dialed selection number can be transmitted to the DPA either in its complete form or – for reasons of data protection – partly deleted; the partial deletion can be done in two ways:
only the first n digits of the destination number are transmitted to the DPA
the last n (of the actually dialed) digits are deleted
You can use AMO SELG to select the method that you want to use.
LEGLV0
Node number of the leg id, (3-digit)
LEGLV1
Subdomain number of the leg ID, (3-digit)
LEGLV2
Domain number of the leg ID, (2-digit)
LEGSEQ
Leg ID: If the destination station is changed in an existing connection, a new leg ID is generated but the global call ID itself is not changed (8-digit).
PINLEN
Length of the personal ID (2-digit)
LISTTYPE
Output of the type of the CDRS output format as text string, only CDRS functionality (16 characters)
You can use AMO TEXT to set up text strings for this element, which can have the following values:
Individual call charge calculation (IND)
Partial call charge calculation (PART)
Total call charge calculation (TOTAL)
MOBUCLV0
Node number of mobile user calling party, (3-digit)
MOBUCLV1
Subdomain number of mobile user calling party, (3-digit)
MOBUCLV2
Domain number of mobile user calling party (2-digit)
MOBUCPTY
Mobile user calling party: the user identifies himself/herself at the called station with a PIN (22-digit)
MSGNO
Message's consecutive number of the S&F (Store & Forward) connection (5-digit)
NCT
Flag that shows that a network call transfer (NCT) was successfully performed. The transfer is done in the public network and all connections over the OpenScape 4000 are released. Because of this, it is no longer possible to record the accounting of call charges of the remaining call (1-char)
NETCARA
The trunk-related access code of the network carrier (related to the BREAKIN trunk) (4-digit)
NETCARB
The trunk-related access code of the network carrier (related to the BREAKOUT trunk) (4-digit)
NETPULS
Pulse: call detail information from the network (5-digit)
NETSVCA
Service for a long-distance call carrier that supplies the PRI rate call (call ends in the PBX); this service is used or requested for an incoming PRI rate call (2-digit)
NETSVCB
Service for a long-distance call carrier that supplies the PRI rate call (call ends in the PBX); this service is used or requested for an outgoing PRI rate call (2-digit)
NETTYPE
Output of the network description as text string (10 characters)
You can use AMO TEXT to set up text strings for this element, which can have the following values:
- Analog network (ANA) - Integrated Data Network (IDN) - Integrated Service Data Network (ISDN)
ORIGIPA
Originating IP Address of the call (15-digits)
OSAA
Operator system access for incoming trunk connections (area 0-2) (1-digit)
OSAB
Operator system access for outgoing trunk connections (area 0-2) (1-digit)
OUTDAY
Date of the output: day of the year (1...366, 3-digit)
OUTDAYC
Date of the output: name of the day (10-digit)
You can use AMO TEXT to set up text strings for this element, which can have the following values:
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday
See also Example 2: before the start of the table.
OUTDAYN
Date of the output: day (2-digit)
OUTHOUR
Date of the output: hour (2-digit)
OUTMIN
Date of the output: minute (2-digit)
OUTMONN
Date of the output: month (2-digit)
OUTMONC
Date of the output: name of the month (10-digit)
You can use AMO TEXT to set up text strings for this element, which can have the following values:
January
February
March
April
May
June
July
August
September
October
November
December
OUTSEC
Date of the output: second (2-digit)
OUTYEAR
Date of the output: year (4-digit)
CHRGEE
Paying party: connection's party responsible for connection costs (22-digit) (see In the fields for incoming calls are:).
Information on the right or left justified output field Section 59.5.2, "CALLEPTY".
PPLV0
Node number of the paying party, (3-digit)
PPLV1
Subdomain number of the paying party, (3-digit)
PPLV2
Domain number of the paying party, (2-digit)
PRECLEV
Precedence level of the calling party, (2-digit)
QUEUEDUR
Queuing duration: total delay time in the queue in 1/10 seconds (5-digit).
RECNO
Consecutive number of the record to be output (1...9999, 4-digit) by selection group.
The consecutive number is initialized to 1 for each dialog field
for "Data transmission on demand"
or
for "Restart" (also for "RELOAD" or "Power on") and
is continually incremented for "immediate output" (even after soft restart).
RECPT
Record point (max. 1 digit)
Possible values:
0 = transit 1 = exit to trunk 2 = record directly at origin 3 = record directly at origin and exit to trunk 4 = incoming
RECTYPE
Type of recording, either relating to the accounting of call charges or traffic measurement or both (1-digit)
RING10
1/10 seconds part of the ring duration in the format minutes:seconds;1/10 seconds (1-digit)
RINGDUR
Total ring duration in format 1/10 seconds (5-digit) (see In the fields for internal calls are:)
RINGMIN
Minute portion of the ring duration in format minutes:seconds;1/10 seconds (2-digit)
RINGSEC
Second portion of the ring duration in the format minutes:seconds:1/10 seconds (2-digit)
ROUTCC
Trunk group code as text string (10-digit), (see In the fields for incoming calls are: and In the fields for internal calls are:) You can use AMO TEXT to set up text strings for the different trunk group codes, for example, "BUSINESS ", "PRIVATE " (each 10 characters long).
ROUTCN
Instead of the actual trunk group code that is used for seizing the trunk or tie trunk when setting up the connect (for external calls, the prefix "0"), the customer can specify 2-digit numbers (see AMO RNKR). For example, this allows you to use different codes to distinguish between external calls for business or private purposes so that they can be billed separately.
RTINGLV0
Node number of the redirecting party, (3-digit)
RTINGLV1
Subdomain number of the redirecting party, (3-digit)
RTINGLV2
Domain number of the redirecting party, (2-digit)
RTINGPTY
Redirecting party: party that forwards a call (22-digit).
RTIONLV0
Node number of the redirection party, (3-digit)
RTIONLV1
Subdomain number of the redirection party, (3-digit)
RTIONLV2
Domain number of the redirection party, (2-digit)
RTIONPTY
Redirection party: where a call is redirected to (22-digit).
RURAL
Flag for pay phone call, (1-digit)
Possible values:
0 = pay phone 1 = other telephone
SELGRUNO
Number of the selection group that created the CDR record (1-digit).
You can use AMO SELG (selection group administration) to put the selection group together with different criteria
For example, the criteria could be:
the connection type (local and long-distance),
the entry of a user in a user list,
or
exceeding a limiting value for the time or cost.
By indicating the selection group number, all connections that meet all set criteria of the chosen selection group are recorded.
SERVICE
Output of the service as a text string (10-digit)
You can use AMO TEXT to set up text strings for this element, which can have the following values:
Voice connection (VOICE)
Facsimile (FAX)
Data terminal (DTE)
SIDANI
Text string referring to the calling party. The BREAKIN trunk provides the SIDANI number, which refers to the calling party (24-digit)
SIGDATA
Code indicating whether the output data record is correct, incorrect, or a duplicate (10-digit).
You can use AMO TEXT to set up text strings for this element, which can have the following values:
imprecise or duplicated data record
correct data record
A data record is identified as imprecise if discrepancies are found while processing the call detail data. For example, this could happen if the connection was automatically restored after a OpenScape 4000 soft restart and the number of call charge pulses and the call duration can not be exactly determined.
SPEED
Output of the transmission speed as a text string (10-digit)
You can use AMO TEXT to set up text strings for this element, which can have the following values:
No speed information
2400 baud
4800 baud
9600 baud
48000 baud (only for S0 link)
64000 baud (only for S0 link)
See the table Meaning of the Values for the Element SPEED in AMO FTBL.
ST10
Connection start: 1/10 second (1-digit)
STDAY
Connection start: day (2-digit)
STHOUR
Connection start: hour (2-digit)
STMIN
Connection start: minute (2-digit)
STMONTH
Connection start: month (2-digit)
STSEC
Connection start: second (2-digit)
STYDAY
Connection start: day of the year (1...366, 3-digit)
STYEAR
Connection start: year (4-digit)
STNID
Output of the station identification as text string (10-digit), (see Note 1)
You can use AMO TEXT to set up text strings for this element, which can have the following values:
Attendant console
Main PBX tie trunk
Night server
Station
Service module (TCS)
Special call charge accounting
Maintenance equipment
Public telephone
Mobile user
External trunk number (keyset)
SUPLSERV
Output of the supplement service as a text string (10-digit)
You can use AMO TEXT to set up text strings for this element, which can have the following values:
Not defined Normal call Consultation call Call transfer Callback Forwarding on busy station Call forwarding Call forwarding, no answer Call pick-up Conference call Override Hunt group Mailbox Radio paging (scroll) Dictation Credit card charge Acceptance of reverse charges Call redirection Door opener Ringing state Hang up on hold Hang up on hold in the attendant queue Busy Removal from the attendant queue Entry into the attendant queue Transfer of a conference by the master Automatic recall when transferring Interruption by the attendant Call forwarding to central attendant console No CDR with eos CDR lost buffer Attendant (ATND) activating night service Attendant (ATND) deactivating night service Attendant (ATND) pulls out the plug (log off) Attendant (ATND) inserts plug (log on) Attendant (ATND) deactivated Attendant (ATND) restart Hang up on hold in the hunt group queue
 
- Hunt group busy - Data record with SWU and ADP load - Passing the call through (transit) - Call rerouting - Incoming call barred - Destination station deactivated - Resource unavailable - Call rejected - Non-allocated number - Account code - The chargeable convener is integrated in the conference - The chargeable convener has left the conference - A-station on hold - B-station on hold - A-station back from hold - B-station back from hold - A-station cradled on hold - B-station cradled on hold - Ringing after connected
SVCDOM
Service Domain of the calling party, (19-digit),
SWP
Partial switching procedures (10-digit)
You can use AMO TEXT to set up text strings for this element, which can have the following values:
- No switching procedure (EMPTY) - Section after section (SECASEC) - Section after account code (SECACC) - Section after seizure (SECS) - Section after limit value (SECL) - End of call after section (ENDSEC) - End of call after seizure (ENDS) - End of call after limiting value (ENDL) - Limit after section (LASEC) - Limit after seizure (LAS) - Limit after first limit (LAL)
Explanation: The values two to ten arise as possible combinations of the events at the beginning and end of the time frame to which the CDR record refers. The following events are considered:
Seizure of a line Beginning a data record
Section, change of the party responsible for connection costs (for example, transferring the connection) Closing up the old data record and starting a new one
Limiting value exceeded for call charge pulses or time Closing up the old data record and starting a new one
End-of-connection Closing up the data record
The last of the values given above identifies a section for chained fax messages.
SWULOAD
SWU processor load in 1/10 percent. This is an average value over 10 seconds (4-digit). The time stamp indicating when the load was measured is in the field "Start of the connection"->STDAY(2-digit), STMONTH(2-digit), STHOUR(2-digit), STMIN(2-digit), STSEC(2-digit),ST10(1-digit)
TERMIPA
Terminating IP Address of the call (15-digit)
THRELV0
Node number of the global thread ID (3-digit), identical to GLOBLV0
THRELV1
Subdomain number of the global thread ID (3-digit), identical to GLOBLV1
THRELV2
Domain number of the global thread ID (2-digit), identical to GLOBLV2
THRESEQ
Sequence number of the global thread ID (8-digit), identical to GLOBSEQ
TKNOBCHA
B channel of the real trunk number of the recording point.
TKNOTRGR
Trunk number group of TKNOREAL (real trunk number of the recording point). If the recording point is a telephone, 0 (zero) is output instead of a trunk (2-digit)
TKNOLIST
Fictitious circuit number, converted from TKNOREAL (Trunk no. list, 6-digit)
The real circuit number (board number) is depicted on a fictitious circuit number specifically for this customer with the help of a table. You can customize this table with AMO FBTN (administration of the flat byte and trunk number table).
TKNOREAL
Real trunk number of the recording point (trunk no. real, 5-digit):
Outgoing connection: outgoing circuit
Incoming connection: incoming circuit
Internal connection: same private automatic branch exchange: A-station PEN
Internal connection: network-wide: outgoing circuit
TRNSFLV0
Node number of transferring party, (3-digit)
TRNSFLV1
Subdomain number of the transferring party, (3-digit)
TRNSFLV2
Domain number of the transferring party, (2-digit)
TRNSFPTY
Transferring party: party that transfers a call (22-digit).
Information on the right or left justified output field (see Section 59.5.2, "CALLEPTY").
TRANSCNT
Number of transit nodes passed through (2-digit max.)
UNANS
through connect/ no through connect (10-digit)
You can use AMO TEXT to set up text strings for this element, which can have the following values:
Through connection (THRCONN)
Non-through connection (NTHRCONN)
UNITERAS
Output whether CDRS call charge totals are deleted after being output as text string, only CDRS functionality (22-digit).
You can use AMO TEXT to set up text strings for this element, which can have the following values:
Difference counter deleted or through-connected
Difference counter not deleted or not through-connected
PIN
Personal ID (max. 12-digits)
ZONE
Output of the distance zone as a text string (10-digit, see In the fields for incoming calls are: and In the fields for internal calls are:)
You can use AMO TEXT to set up text strings for this element, which can have the following values:
1st incoming zone (INC01) n-th incoming zone (INCnn) 9th incoming zone (INC09) 1st abroad (ABROAD01) n-th abroad (ABROADnn) 99th abroad (ABROAD99) 1st distance (LONG01) n-th distance (LONGnn) 50th distance (LONG50) No charge (NOCHRG) Call detail information from carrier (CHRGINFO) 1st internal zone (INT01) n-th internal zone (INTnn) 9th internal zone (INT09) Empty entry (EMPTY) Short zone (SHORT) Local Zone (LOCAL) 1st zone for tie trunks (TIE01) n-th zone for tie trunks (TIEnn) 9th zone for tie trunks (TIE09)

Remarks:

  1. In the fields for incoming calls are:
ATNDGRNO
=
Group number of the attendant console that answered and forwarded this call
CARRIER
=
a carrier that can be allocated to an incoming trunk group (AMO TACSU / TDCSU)
CHOFCON
=
always "LONG"
CONNTYPE
=
"INCOMING"
ROUTCC
=
empty (fill character)
ROUTCN
=
empty (fill character)
STNID
=
station identification of the called station
ZONE
=
a zone INC01 - INC09 that can be allocated to an incoming trunk group (AMO TACSU / TDCSU)
  1. In the fields for internal calls are:
CARRIER
=
always "0"
CHRGUNIT
=
empty (fill character)
CONNTYPE
=
"INTERN"
CHOFCON
=
always "LOCAL"
ROUTCN
=
empty (fill character)
ROUTCC
=
empty (fill character)
RINGDUR
=
"0" for ZAND parameter CDRRINGB = NO (AMO ZAND)
ZONE
=
zone INT01 - INT09 determined from the ITR group (AMO VBZGR)