102 CHAPTER 2: D IAL P LANViewing andResetting Virtual TieLine StatisticsYou can view the statistics for a VTL at any time.To view statistics for a VTL:1 In the NBX NetSet - Main Menu window, click Device Configuration.2 Click the Virtual Tie Lines tab.3 From the list, select the VTL.4 Click the Statistics button. The Statistics dialog box appears. The fields aredescribed in Table 21.5 To reset all VTL statistics, click Reset.Another way to reset all VTL statistics is to restart the NBX system.6 When you are finished, click Close.Table 21 Virtual Tie Line Statistics FieldsField DescriptionNOTE: All statistics apply to the time period since the most recent Reset commandor since the most recent system reboot, whichever was more recent. To determinethe starting time for the displayed statistics, compare the Last reset command withthe time of the Last system reboot. Both are displayed at the bottom of the VTLStatistics window.Number of outgoingVTL calls madeThe number of outgoing calls made over all virtual tie lines(VTLs) since the most recent reset command or since the timethe NBX system was last restarted. Each time you restart theNBX system, you reset the statistics for all VTLs.Number of incomingVTL calls receivedThe number of incoming calls received over all VTLs since themost recent reset command or since the time the NBXsystem was last restarted.Number of active VTLcallsThe number of calls currently active on all VTLs.Maximum number ofconcurrently activeVTL callsThe maximum number of VTL calls that have been active atthe same time on this NBX system since the most recentreset command or since the time the NBX system was lastrestarted.Incoming VTL callsrejected due to allVTLs busyThe number of telephone calls that would have arrived fromother NBX systems over VTL channels, but could not beaccepted because all local VTL ports were busy when thecalls arrived.Outgoing VTL callsrejected due to allVTLs busyThe number of telephone calls that would have been sentfrom the local NBX system over VTL channels, but could notbe sent because all local VTL ports were busy when the callswere made.
