CommandText goes hereReference - xStatus

TANDBERG VIDEO COMMUNICATION SERVER ADMINISTRATOR GUIDE

Calls continued...

MediaRouted: <True/False>

Participants:

Leg: <1..300> {2 entries}

Bandwidth: <0..100000000> kbps

Route:

Zone/Link: <S: 1,50 Node name> {0..150 entries}

Registrations:

Registration [1..3750]:

Protocol: <H323/SIP>

Node: <S: 1,50 Node name>

SerialNumber: <S: 1,255>

CreationTime: <Date Time>

SecondsSinceLastRefresh: <1..65534> {Visible if Protocol is SIP}

SecondsToExpiry <1..65534> {Visible if Protocol is SIP}

VendorInfo: <S: 1,255>

H323: {Visible if Protocol is H323}

Type: <Endpoint/MCU/Gateway/Gatekeeper>:

CallSignalAddresses:

Address: <IPv4Addr/[IPv6Addr]>:<1..65534>

RASAddresses:

Address: <IPv4Addr/[IPv6Addr]>:<1..65534>

Apparent: <IPv4Addr/[IPv6Addr]>:<1..65534>

Prefix: <S: 1,20> {0..50 entries}

Aliases:

Alias [1..50]:

Type: <E164/H323Id/URL/GW Prefix/MCU Prefix/Prefix/Suffix/IPAddress>

Origin: <Endpoint/LDAP/Combined>

Value: <S: 1,60>

Traversal: <Assent/H46018> {Visible for Traversal calls}

SIP: {Visible if Protocol is SIP}

AOR: <S: 1,128>

Introduction

Getting

System

System

H.323 & SIP

Registration

Zones and

Call

Firewall

Bandwidth

Maintenance

Appendices

Started

Overview

Configuration

Configuration

Control

Neighbors

Processing

Traversal

Control

 

 

 

D 14049.01

 

 

 

 

161

 

 

 

 

 

07.2007

 

 

 

 

 

 

 

 

 

Page 161
Image 161
TANDBERG D14049.01 manual 161