Figure 2-77 Example Of Twice Through Virtual Loop (Reverse Direction); Table 2-93 Smdr Report Definitions - NEC Univerge SV8100 Features And Specifications Manual

Issue 13.0
The SMDR output looks very similar to the one before, where the call was routed through the same T-
and S-point ports, but in the other direction:

Figure 2-77 Example of Twice Through Virtual Loop (Reverse Direction)

This intended purpose of the tagging is to link the first and last port of such a chain together. Note that
the internal SMDR feature needs to be switched on in this case to get the call leg from S-point to
extension printed.
Limitation

These programs must be set correctly to function:
Program 35-02-03= 1: Trunk Number
Program 35-02-09= 1: Extension Number
 This is not a real limitation however, if both are set to 0, matching names may be given to the T-point and S-point
ports (e.g. "V-one", "V-two", ...) yielding the same functionality.
Program 35-02-16 must be set to 1: Trunk Name/Number otherwise, the received dialed number
not the trunk port information is printed.
Report Headings
Call Record Number
CLASS
TIME
DATE
LINE
DURATION
STATION
2 - 1510

Table 2-93 SMDR Report Definitions

Definitions
SMDR record number (consecutive)
Type of call (see Class Definitions below)
Time call placed or answered. (For Transferred calls, shows time user picked up
Transfer.)
Date the call was made (Program 35-02-14=1). For Extension calls, this area is blank.
Trunk number used for call. For Extension calls, this area is blank.
The time the call lasted. (For Transferred calls, shows how long user was on call after
answering the Transfer.)
Extension number of call owner (i.e., extension that first placed or answered call) (For
Transferred calls, there can be more than one owner – depending on how many
extensions shared the call.)
UNIVERGE SV8100
Station Message Detail Recording