This guide will introduce you to the Application Programmer
Interface (API) and ser ve as a reference guide for the
command line commands for Cisco TelePresence ISDN Link.
User documentation
The user documentation for the Cisco TelePresence ISDN Link,
running the IL software, have several guides.
• Installation guide
• Software release notes
• Administrator guide
• API reference guide
• Regulatory compliance and safety information
• License information
Download the user documentation
Go to:
Software
You can download the software for your product from the
Cisco web site.
The API-engine can be accessed by an easyto-use Command Line Interface called XACLI
using RS-232 or SSH.
The information is stored in a hierarchic tree
structure which is accessible from dierent
interfaces.
• When accessing the API-engine using
XACLI (RS-232 or SSH), the information is
formatted in a proprietary Command Line
style or in XML formatting.
The API-Engine
The API-Engine is optimized for easy, yet
advanced, machine-machine interaction
between a Cisco system and an external
control application.
The main features can be summarized to:
1. Structuring of information
2. Addressing using XPath (XML Path
Language) or SimplePath
3. Feedback
XACLI
(XML)
SSH
via LAN
API-Engine
Structuring of Information
An application programming interface (API)
can be seen as a gate where information is
exchanged between two systems – a control
application and a target system.
The control application transmits instructions
to the target system, while the target system
supplies information about how these
instructions are executed, in addition to other
system related information.
RS-2 32
cable
Consequently, the exchange of information
can be divided into:
1. Information owing from target. This
we call READ information (R). The (R)
should not be confused with the (r)
used to indicate required parameters for
xCommand.
2. Information owing to target. This we call
WRITE information (W).
Main types of information
• READ information (R)
• WRITE information (W)
• READ/WRITE information (RW)
(R) RE AD information: xStatus.
Typical examples include: read the network
status, ISDN status etc. All status information
is structured in a hierarchy, making up a
database constantly being updated by the
system to reect process changes.
(W) WRITE information: xCommand.
Typical examples include: set date and time,
get date and time, software upgrade, etc.
A command is usually followed by a set of
parameters to specify how the given action is
to be executed.
(RW) READ/WRITE information: xConguration.
Typical examples include: set or read the
value of the H320 network type, ISDN PRI
switch type, call rate, etc. All conguration
information is structured in a hierarchy making
up a database of system settings.
D14953.01 ISDN Link A PI Reference Guide IL1.0 June 2012.
To address information in the hierarchic structure of Status and
Conguration information, the systems support abbreviated
XML Path Language (XPath) and a proprietary notation called
SimplePath (only available using XACLI).
This allows the user to address everything from a single
element of data (for example the call rate of a specic call)
to larger parts of the hierarchy (for example all information
available for a given call).
Using XPath
Addressing the 1st DNS Server Address of the 1st Network:
Each level is separated with a slash (‘/’). Item numbers are
added in brackets after the element name:
• Network[1]/DNS Server[1]/Address
Example:
xCong uration Network[1]/DNS Server[1]/Address
*c xConguration Network 1 DNS Server 1 Address:
“test”
OK
Using SimplePath
Addressing the 1st DNS Server Address of the 1st Network:
Both levels and item numbers are separated with white spaces:
• Network 1 DNS Server 1 Address
Feedback
Feedback is an extremely powerful feature where the system
actively returns updated status and conguration information to
the user whenever changes occur.
The user can specify what parts of the status and conguration
hierarchies it wants to monitor by using XPath. The user can
thereby limit the amount of information it receives from the
target system to only those parts being of interest for the
given application. This will also reduce the load on the link
connecting the systems.
Feedback is supported on XACLI (RS-232/SSH).
The system uses SimplePath when presenting congurations.
The structuring of information together with XPath and
SimplePath for addressing, makes up powerful features as
the ability to search and setting of multiple instances of a
conguration.
Example:
xCong uration Network 1 DNS Server 1 Address
*c xConguration Network 1 DNS Server 1 Address:
“test”
OK
D14953.01 ISDN Link A PI Reference Guide IL1.0 June 2012.
XACLI can be accessed through SSH via the LAN interface or
through the COM port by connecting a serial cable to the serial
interface connector, referred to as the COM port.
The COM port (RS-232) is a 9-pin, female, D-sub connector
located on the back of the unit. The connector is marked with
the text: COM.
COM Port settings
Use: 115200 bps, 8 data bits, 1 stop bit, no parity.
SSH login
• User name is: admin
• The default password is blank.
Serial port login
• User name is: admin
• The default password is blank.
Hardware & Cabling (RS-232)
The pin outs for the RS-232 are dened in the tables to the
right. Observe that the DTE (Data Terminal Equipment), could
be a PC or any other device capable of serial communication.
Cable. A straight-through cable should be used between
the RS-232 port and the DTE. The lower table shows the
recommended cable-wiring scheme when connecting the
ISDN Link to a PC through RS-232.
DTR and RTS are ignored. DSR, CD, and CTS are always
asserted, while RI is not used.
Troubleshooting (RS-232)
If communication cannot be established between the PC/
terminal and the unit, the following should be checked:
1. Verify that the serial cable is a straight-through 9-pin to
9-pin cable.
2. Conrm that the conguration of the PC/terminal’s serial
RS-232 port is identical to the conguration of the RS-232
port.
3. Verify that the PC/terminal’s serial RS-232 port is working
properly by connecting it back-to-back to another PC/
terminal (using a special crossover cable for that purpose)
and send characters in both directions.
COMport(RS-232)
PinSignal name
1Carrier detect, CD
2Receive data, RXD
3Transmit data, TXD
4Data terminal ready, DTR
5Signal GND
6Data set ready, DSR
7Ready to send, RTS
8Clear to send, CTS
9Ring indicator, RI
Cablewiring(RS-232)DCE<->PC
DCE 9 pinDirectionPC DTE, 9 pin
1 CD
2 RD
3 TD
4 DTR<—
5 GND<—>5 GND
6 DSR—>6 DSR
7 RTS<—7 RTS
8 CTS—>8 CTS
9 RI—>9 RI
—>1 CD
—>2 RD
<—
Direction
From DCE
From DCE
To D CE
From DCE
From DCE
To D CE
From DCE
From DCE
3 TD
4 DTR
D14953.01 ISDN Link A PI Reference Guide IL1.0 June 2012.
The XACLI is divided into three main types of
commands, reecting the information types
supported by the API Engine.
The main types are:
• Conguration type commands
• Status type commands
• Command type commands
Conguration type commands
Conguration type commands denes the
system settings. Conguration commands are
either supplied or read by the user.
System settings made by Conguration type
commands are persistant over a reboot.
Example: Congure ISDN settings, external
network settings, and enabling/disabling of
various features etc.
The Conguration commands are structured
in a hierarchy, making up a database of
system settings.
Supported Conguration type commands:
xConguration
Special commands
In addition to the above sets of commands,
XACLI supports the following set of special
commands:
Command type commands
Command type commands instructs the
system to perform an action. Command
commands are supplied by the user.
Actions performed by a Command type
command are not persitant over a reboot.
Example: instructing the system to place a
call, assign oor to a specic site, disconnect
a call etc.
A xCommand command is usually followed by
a set of parameters to specify how the given
action is to be executed.
Supported Command type commands:
xCommand
Feedback type command
The Feedback commands are used to specify
what parts of the conguration and status
hierarchies to monitor. Feedback will only be
issued on the RS-232/SSH session for which
it is specied. If connecting to the system with
multiple sessions, each session can dene
feedback individually.
Status type commands
Status type commands returns information
about the system and system processes.
xStatus type commands are read by the user.
Example: Information generated by the
system about ongoing calls, network status,
conference status etc.
All status information is structured in a
hierarchy, making up a database constantly
being updated by the system to reect system
and process changes.
Supported Status-type commands:
xStatus
Preferences type command
The Preference type command is used to
set various preferences for the RS-232/
SSH sessions. Each session can dene
preferences individually. IMPORTANT! This
command has various settings to dene the
formatting of the X ACLI output. It is therefore
important to dene settings to match the
parser used on the control system. XACLI is
designed to make parsing of data from the
system very simple.
D14953.01 ISDN Link A PI Reference Guide IL1.0 June 2012.
The xConguration type commands denes the system
settings and are either supplied or read by the user. The
xCongurations commands are organized in a hierarchic tree
structure.
To get an overview of the supported xConguration
commands, type ? or help after the xConguration command:
• xConguration ?
• xConguration help
To get an overview of the supported xConguration
commands, with the corresponding value space, type ?? after
the xConguration command:
• xConguration ??
When issuing a xConguration command, the command
consists of three parts:
1. The type of command: xConguration
2. The path: An address expression, terminated by a colon
The xFeedback is a feature that lets you subscribe to
noticatons of changes from the system.
• This can be xConguration, xStatus changes and changes
in the state of the unit.
The xFeedback command is used to specify what parts of the
xConguration and xStatus hierarchies to monitor, and will only
be issued on the RS-232/SSH for which it is specied.
If connecting to the system with multiple sessions, each
session can dene feedback individually.
CAUTION: We discourage registering all status changes as
this may give more feedback information than the system is
able to handle.
xFeedback ?
xFeedback help:
xFeedback Register XPathEx pression[1..255] - Registers feedback on expression XPathExpression
xFeedback Deregister XPathExpression[1..255] - Deregisters feedback if resistered on XPathExpression
xFeedback deregisterall - Deregister all expressions
xFeedback List - Generate list of currently registered XPathExpressions
xFeedback Help - Display this help text
ExamplewithxFeedback
xFeedback register Status/ISDN
xFeedback register Conguration/ISDN
xFeedback list
xFeedback deregister Conguration/ISDN
xFeedback list
D14953.01 ISDN Link A PI Reference Guide IL1.0 June 2012.
The xPreferences command is used to set various preferences
for the RS-232/SSH sessions.
Each session can dene preferences individually.
IMPORTANT! This command has various settings to dene
the formatting of the XACLI output. It is therefore important to
dene settings to match the parser used on the control system.
XACLI is designed to make parsing of data from the unit very
simple.
To get an overview of the supported xPreferences commands
and their value space, type ? or help after the xPreferences:
• xPreferences ?
• xPreferences help
The xPreferences output modes
• Terminal: Line based XACLI output for use with line based
control systems
• XML: Pure XML output for use with control systems that
understand XML.
xPreferences ?
xpreferences usage:
xpreferences outputmode <terminal/xml>
xpreferences apiversion <1/2>
OK
D14953.01 ISDN Link A PI Reference Guide IL1.0 June 2012.
The systemtools command is used for administrative control
of the ISDN Link and is only available from a command line
interface.
Supported commands
To get an overview of the supported commands type
“systemtools ?”.
systemtools bondingtrace on|o
Control logging of misc. bonding related events. Logging is
typically sent to the application log le, but can be enabled for
a console by enabling ‘log’ output, see separate command for
this. Please notice that the bonding log may interfere with real
time characteristics, and increases the chance of loosing H.320
side trac data.
on/o: Enable/disable decoding trace output.
API Reference Guide
systemtools license list
Lists all the licenses for the ISDN Link.
systemtools license show <name>
Shows the content of a license le, dene by the name.
name(r): The name of the license le.
Example:
systemtools ?
bondingtrace
dumph221
isdntrace
license
network
passwd
rootsettings
securitysettings
securitystatus
showlog
OK
Parameters
Required parameters in angle brackets: <text>
Optional parameters in square brackets: [text]
Detailed information
To see the usage of the commands add a question mark
after the command.
Example:
systemtools license ?
usage: license <list | show <name>>
OK
systemtools dumph221 [inst] toggle
Dump H.221 internal information used for debugging purposes.
In the following pages you will nd a complete list of the xConguration commands. The
examples shows either the default value or an example of a value.
We recommend you visit our web site regularly for updated versions of the manual.
Go to:
The E1 conguration
xConguration E1 Interface [1..1] CRC4
http://www.cisco.com/go/isdnlink-docs
E1 CRC-4 (Cyclic Redundancy Check 4-bit) is used for most E1-PRI congurations.
Value space: <On/Off>
On: The default value is On.
O: Some manufactures do not support this feature. By setting E1 CRC4 to O this functionality
Congure the clocking signal which is compatible with the external equipment.
Value space: <Dual/Single>
Dual: (RS449/V35 Compatible) Use this setting when the external equipment provides two clock
signals, one for transmit and one for receive. The dierence between RS449 and V35 lies solely in
the cable.
Single: (X21 Compatible) Use this setting when the external equipment provides a common clock
signal for both transmit and receive.
Congure the dialling sheme which is compatible with the external equipment.
Value space: <Manual/RS366/RS366AdtranIMUX/RS366CustomIMUX/LeasedLine>
Manual: Select Manual used when no handshake signals are available and the external equipment
requires a constantly connected line.
RS366: This is the only dialling protocol supported and would normally be used together with Dual
network clocking when the external equipment uses RS366 ports.
RS366AdtranIMUX: This setting oers extra usability when dialling RS366 via an ADTR AN IMUX.
This dialling scheme will map the call type and bandwidth selection to ADTRAN IMUX specic
suxes to the dialled number. Should only be used when connected to an ADTRAN IMUX. The
Adtran IMUX uses the following suxes <Number>#C#R, where #C = Call Type #2 = audio #3 =
56kbps #4 = 64kbps #R = Channel Rate #0 = 2xh221 (2x56\64kbps) #1 to 8 = the Call Rate.
RS366CustomIMUX: Uses a custom prex/sux table which describes the available bandwidths.
The prexes/suxes are set from the Web Interface or Command Line interface. The user
(administrator) shall be able to specify a IMUX prex/sux table for the following bandwidths
(kbps): 64, 64 Restrict, 128, 128 Restrict, 192, 192 Restrict, 256, 256 Restrict, 320, 320 Restrict,
384, 384 Restrict, 512, 512 Restrict, 768, 768 Restrict, 1152, 1152 Restrict, 1472, 1472 Restrict,
1920, 1920 R estr i ct.
LeasedLine: Leased Line is a non-dialling protocol and should be used when two codecs are
connected in a point-to-point connection. Use Leased Line when the handshaking signals DTR
and CD are available. DTR and CD correspond to the X.21 network's C and I signals.
Set the address be used to reach the peer codec for incoming H.320 side calls when SIP (VCS)
registered mode is used. It should hold the same setting as the peer codec uses to register itself
on the VCS server. If SIP registered mode is not used, this setting is not used. (VCS = Video
Communication Server)
Value space: <S: 0, 256>
Format: Compact string with a maximum of 256 characters.
Set the IP address of the peer SIP codec using the ISDN link. Only one SIP codec can use the ISDN
link, and it must be on the same subnet as the ISDN link. This IP address must correspond to the IP
address type (IPv4 or IPv6) that the codec is congured to use for SIP calls.
The address is used for:
1) Verication of the SIP remote media transpor t addresses (if there is a mismatch, the call will be
rejected/disconnected).
2) System status monitoring, indicating alarm etc if specied codec is not reachable.
3) If not SIP (VCS) registered, this address is used to call the SIP codec for incoming H.320 side calls.
(VCS = Video Communication Server)
Value space: <S: 0, 64>
Format: Compact string with a maximum of 64 characters.
BRI: Select BRI for the BRI network.
PRI: Select PRI for the PRI network.
External: Select External for the external network (Net/V.35).
G703: For test purpose only.
Example: xConguration H320 NetType: BRI
xConguration H320 Bonding Timer
Relaxed bonding timer is used when B channels requires additional time before they can become
transparent.
Value space: <Normal/Rela xed>
Normal: The default value is Normal.
Relaxed: Relaxed bonding timing should be used with applications where the B channels use
some additional time before they become transparent, like external encryption devices etc.
Example: xConguration H320 Bonding Timer: Normal
xConguration H320 Bonding Rebonding
Rebonding is used to re-establish H.320 calls if corrupted data is received for a longer period (10 15 sec).
Value space: <On/Off>
On: The default value is On.
O: Some manufactures do not support this feature. By setting Rebonding to O this functionality
will be disabled.
Example: xConguration H320 Bonding Rebonding: On
xConguration H320 DefaultCall Restrict
A restricted call uses 56 kbps channels rather than the default unrestricted 64 kbps channels.
Some older networks (primarily in the USA) do not support 64 kbps channels and require the use
of restricted 56 kbps calls. By default, the system will dial an unrestricted call and downspeed to 56
kbps if necessary.
Value space: <On/Off>
On: Set to On to force restricted (56 kbps) calls.
O: Set to O to disable restricted calls.
Example: xConguration H320 DefaultCall Restrict: Off
The ISDN conguration
xConguration ISDN SendComplete
Select if the ISDN message should contain sending complete information.
Value space: <On/Off>
On: If set to On the system will send the ISDN message information element Sending Complete.
O: If set to O The system will not send Sending Complete.
Example: xConguration ISDN SendComplete: Off
xConguration ISDN SendNumber
Select if the system should send its own number to the far end.
Value space: <On/Off>
On: When set to On, the system will send its own numbers to the far end.
O: When set to O, the system will not send its own numbers to the far end. Note that the
network may still send your numbers to the far end.
Example: xConguration ISDN SendNumber: On
xConguration ISDN ParallelDial
Select if the channels in bonding calls should be connected in parallel or one by one.
Value space: <On/Off>
On: When set to On, channels will be dialled and connected in parallel when setting up a bonding
call.
O: When set to O, channels will be dialled one by one, which may increase the dialling time.
Example: xConguration ISDN ParallelDial: On
xConguration ISDN HCL
Select if HCL (Higher Level Capability) information should be included in the setup message (video
calls only).
Value space: <On/Off>
On: When set to On, the system will signal, type of call i.e. video call, telephony or data. HLC must
be enabled to work with some PRI networks in Italy.
O: When set to O, no HCL information will be sent.
Example: xConguration ISDN HCL: Off
D14953.01 ISDN Link A PI Reference Guide IL1.0 June 2012.
Select if scpeech timers should be active for ISDN Layer 3, telephony calls.
Value space: <On/Off>
On: Set to On to enable speech timers (T310, T304, T301).
O: When set to O, there will be no T310, T304, T301.
Example: xConguration ISDN SpeechTimers: On
xConguration ISDN MSN
The use of MSN (Multiple Subscriber Number) enables the system to attach dierent ISDN terminals,
with dierent numbers, to the same physical ISDN telephone line. This service can be ordered from
your telephone company.
Value space: <On/Off>
On: Set to On to enable MSN on the video system when you have subscribed to a MSN service
from your telephone company.
O: When set to O, only calls to numbers specied for the specic ISDN interfaces will be
answered.
Example: xConguration ISDN MSN: Off
xConguration ISDN SubAddress
Using a sub address enables you to connect up to eight ISDN terminals to the same ISDN telephone
number and line. The terminals are addressed by using dierent sub addresses. To call a terminal
with a sub address, separate the ISDN telephone number and the sub address with a * (asterisk).
Note that this service has limited access on some ISDN networks.
Value space: <S: 0, 20>
Format: String with a maximum of 20 characters.
Example: xConguration ISDN SubAddress: ""
xConguration ISDN SubAddressSend
Using a sub address enables you to connect up to eight ISDN terminals to the same ISDN telephone
number and line. The terminals are addressed by using dierent sub addresses. To call a terminal
with a sub address, separate the ISDN telephone number and the sub address with a * (asterisk).
Note that this service has limited access on some ISDN networks.
Value space: <On/Off>
On: When set to on, the system will use the values set by "ISDN SubAddress".
O: Set to O to disable use of sub addresses.
Example: xConguration ISDN SubAddressSend: On
xConguration ISDN CliNumbSpec
Select if calling party numbers should be enabled. Explicitely specify Calling Party Number elds
Type/Plan to be used in outgoing calls in the ISDN setup message.
Value space: <On/Off>
On: When set to on, the system will use the values set by "ISDN CliNumPlan" and "ISDN
CliNumbType".
O: When set to O, default values are used.
Example: xConguration ISDN CliNumbSpec: Off
xConguration ISDN CliNumbType
Value to be used for calling part y number eld Type. If the value is set to 2, the number type in the
setup message will be set to National. This is required in the UAE (United Arab Emirates).
Value space: < 0..6 >
Range: Select a value between 0 and 6.
Example: xConguration ISDN CliNumbTy pe: 0
xConguration ISDN CliNumbPlan
Value to be used for calling part y number eld Plan in the ISDN setup message. If the value is set to
1, the numbering plan in the setup message will signal ISDN. This is required in the UAE (United Arab
Emirates).
Value space: < 0..14 >
Range: Select a value between 0 and 14.
Example: xConguration ISDN CliNumbPlan: 0
xConguration ISDN PRI SwitchType
Selects the type of PRI switch the system is connected to.
Value space: <NI/ATT/Euro/Jap a n>
NI: Select NI if the switch is a National ISDN switch type.
AT T: Select ATT if the switch is an AT&T (for the U.S.) ISDN switch type.
Euro: Select Euro if the switch is an Euro (UK and others) ISDN switch type.
Japan: Select Japan if the switch is a Japanese ISDN switch type.
Example: xConguration ISDN PRI SwitchType: NI
xConguration ISDN PRI InitialRestart
Select if the system should re-initialize the PRI interfaces after the system has been restarted.
Value space: <On/Off>
On: When set to On, the PRI interfaces will be re-initialized after restart of the system.
O: When set to O, the PRI interface will not be re-initialized after restart.
Example: xConguration ISDN PRI InitialRestart: On
D14953.01 ISDN Link A PI Reference Guide IL1.0 June 2012.
Select if the system should respond with an alert message to all incoming setup messages, or to the
rst incoming channel only.
Value space: <On/Off>
On: When set to On, the system will respond with an alert message to all incoming setup
messages.
O: When set to O (default) the system will respond with an alert message only to the incoming
setup message related to the initial channel. Note that if the PBX requires this signalling you will
only get connected on the rst incoming channel.
Example: xConguration ISDN PRI Alert: Off
xConguration ISDN PRI ChanId
Select if PRI Channel ID information should be sent to the PXB.
Value space: <On/Off>
On: When set to On, the system will signal to the PBX which PRI channels is used for the call.
Note: This setting must be set to On, to work with an Ericsson MD110 PBX.
O: When set to O, Channel ID information is not sent. Default setting is O.
Example: xConguration ISDN PRI ChanId: Off
xConguration ISDN PRI L2WindowSize
Set Layer 2 window size (ISDN Layer 2).
Value space: < 1..7 >
Range: Select a value between 1 and 7.
Example: xConguration ISDN PRI L2WindowSize: 7
xConguration ISDN PRI NSFTelephony Mode
Congure the NSF (Network Service Facility) mode for telephony.
Value space: <On/Off>
On: Set to On, to enable Network Service Facility for telephony.
O: Set to O to disable Net work Service Facility for telephony.
Example: xConguration ISDN PRI NSFTelephony Mode: Off
xConguration ISDN PRI NSFTelephony Number
Denes what Service Facility to use for telephony. Requires the NSFTelephony Mode set to On.
Service proles for AT&T (ref. 1):
NSF Service
0 Disable
1 SDN (including GSDN)
2 Toll Free Megacom (800)
3 Megacom
6 ACCUNET Switched Digital Service (including Switched Digital International)
7 Long Distance Ser vice (including AT&T World Connect)
8 International Toll Free Service (I800)
16 AT&T MultiQuest
23 Call Redirection Service
Service proles for Sprint (ref. 2):
NSF Service
0 Reserved
1 Private
2 Inwatts
3 Outwatts
4 FX
5 TieTrunk
Service proles for MCI (ref. 3):
NSF Service
1 V NET/Vi sio n
2 800
3 PRISM1, PRISMII, WATS
4 900
5 DAL
Value space: < 0.. 31>
Range: Select a value between 0 and 31.
Example: xConguration ISDN PRI NSFTelephony Number: 0
D14953.01 ISDN Link A PI Reference Guide IL1.0 June 2012.
Congure the NSF (Network Service Facility) mode for video telephony.
Value space: <On/Off>
On: Set to On, to enable Network Service Facility for video telephony.
O: Set to O, to disable Network Ser vice Facility for video telephony.
Example: xConguration ISDN PRI NSFVideoTelephony Mode: Off
xConguration ISDN PRI NSFVideoTelephony Number
Denes what Service Facility to use for video telephony. Requires NSFVideoTelephony Mode set to
On.
Value space: < 0.. 31>
Range: Select a value between 0 and 31.
Example: xConguration ISDN PRI NSFVideoTelephony Number: 0
xConguration ISDN PRI Interface [1..1] MaxChannels
Set the maximum number of channels the system may use at any given time.
Value space: < 1.. 3 0 >
Range: Select a value between 1 and 30.
Example: xConguration ISDN PRI Interface 1 MaxChannels: 23
xConguration ISDN PRI Interface [1..1] HighChannel
Set the highest numbered B-channel that may be used by the system when selecting channels for
outgoing calls.
Value space: <1..31>
Range: Select a value between 1 and 31.
Example: xConguration ISDN PRI Interface 1 HighChannel: 31
xConguration ISDN PRI Interface [1..1] LowChannel
Set the lowest numbered B-channel that may be used by the system when selecting channels for
outgoing calls.
Value space: <1..31>
Range: Select a value between 1 and 31.
Example: xConguration ISDN PRI Interface 1 LowChannel: 1
xConguration ISDN PRI Interface [1..1] Search
Selects whether to start searching for available B-channels from the highest numbered channel or
from the lowest numbered channel.
Value space: <High/Low>
High: When set to High, the system will start searching for available B-channels from the highest
numbered channel.
Low: When set to Low, the system will start searching for available B-channels from the lowest
numbered channel.
Example: xConguration ISDN PRI Interface 1 Search: High
xConguration ISDN PRI Interface [1..1] NumberRangeStart
If the PRI line has a range of numbers, the rst number in the range should be entered in the Number
Range Start eld.
Value space: <S: 0, 24>
Format: String with a maximum of 24 characters.
Example: xConguration ISDN PRI Interface 1 NumberRangeStart: ""
xConguration ISDN PRI Interface [1..1] NumberRangeStop
If the PRI line has a range of numbers, the last number in the range is entered in the Number Range
Stop eld.
Value space: <S: 0, 24>
Format: String with a maximum of 24 characters.
Example: xConguration ISDN PRI Interface 1 NumberRangeStop: ""
xConguration ISDN BRI Alert
Select if the system should respond with an alert message to all incoming setup messages, or to the
rst incoming channel only.
Value space: <On/Off>
On: When set to On, the system will respond with an alert message to all incoming setup
messages.
O: When set to O (default) the system will respond with an alert message only to the incoming
setup message related to the initial channel. Note that if the PBX requires this signalling you will
only get connected on the rst incoming channel.
Example: xConguration ISDN BRI Alert: Off
D14953.01 ISDN Link A PI Reference Guide IL1.0 June 2012.
Select if BRI Channel ID information should be sent to the PXB.
Value space: <On/Off>
On: When set to On, the system will signal to the PBX which BRI channels is used for the call.
Note: This setting must be set to On, to work with an Ericsson MD110 PBX.
O: When set to O, Channel ID information is not sent. Default setting is O.
Example: xConguration ISDN BRI ChanId: Off
xConguration ISDN BRI InterfaceSearch
Selects whether to start searching for available B-channels from the highest numbered interface or
from the lowest numbered interface.
Value space: <High/Low>
High: When set to High, the system will start searching for available B-channels from the highest
numbered interface.
Low: When set to Low, the system will start searching for available B-channels from the lowest
numbered interface.
Example: xConguration ISDN BRI InterfaceSearch: High
xConguration ISDN BRI SwitchType
Select the type of BRI switch the system is connected to.
Value space: <NI/ATT/Euro/Jap a n/1T R6/Austr alia/F ET EX>
NI: Select NI if the switch is a National ISDN switch type.
AT T: Select ATT if the switch is an AT&T (for the U.S.) ISDN switch type.
Euro: Select Euro if the switch is an Euro (UK and others) ISDN switch type.
Japan: Select Japan if the switch is a Japanese ISDN switch type.
1TR6: Select 1TR6 if the switch is an 1TR6 switch type.
Australia: Select Australia if the switch is an Australian ISDN switch type.
FETEX: Select FETEX if the switch is a FETEX ISDN switch type.
Example: xConguration ISDN BRI SwitchType: Euro
xConguration ISDN BRI MaxDeactiveTime
Set the maximum duration for Layer 1 in de-active state before auto activation (re)starts.
Set the auto activation mode of the BRI interface (ISDN Layer 1).
Value space: <Off/Selected/All>
O: When set to O, no interfaces will be activated.
Selected: When set to Selected, the system will activate the interfaces which are already on.
All: When set to All, the system will activate all interfaces regardless of status.
Example: xConguration ISDN BRI AutoActivation: All
D14953.01 ISDN Link A PI Reference Guide IL1.0 June 2012.
Value space: < Aut o/10 half/10f ull/100 h a lf/100ful l/1000f ull >
Auto: Autonegotiate link speed.
10h alf: Force link to 10 Mbps half-duplex.
10ful l: Force link to 10 Mbps full-duplex.
100 half: Force link to 100 Mbps half-duplex.
100full: Force link to 100 Mbps full-duplex.
1000full: Force link to 1 Gbps full-duplex.
Example: xConguration Network 1 Link Network: Auto
xConguration Network [1..1] Link Endpoint
Set the Ethernet link speed for the endpoint (video system).
Value space: < Aut o/10 half/10f ull/100 h a lf/100ful l/1000f ull >
Auto: Autonegotiate link speed.
10h alf: Force link to 10 Mbps half-duplex.
10ful l: Force link to 10 Mbps full-duplex.
100 half: Force link to 100 Mbps half-duplex.
100full: Force link to 100 Mbps full-duplex.
1000full: Force link to 1 Gbps full-duplex.
Example: xConguration Network 1 Link Endpoint: Auto
xConguration Network [1..1] Assignment
Dene whether to use DHCP or Static IPv4 assignment.
Value space: <Static/DH CP>
Static: Set the network assignment to Static and congure the static IPv4 settings (IP Address,
SubnetMask and Gateway).
DHCP: The system addresses are automatically assigned by the DHCP server.
Example: xConguration Network 1 Assignment: DHCP
xConguration Network [1..1] DNS Domain Name
DNS Domain Name is the default domain name sux which is added to unqualied names.
Example: If the DNS Domain Name is "domain.com" and the name to lookup is "MyVideoSystem",
this will result in the DNS lookup "MyVideoSystem.domain.com".
Value space: <S: 0, 64>
Format: String with a maximum of 64 characters.
Example: xConguration Network 1 DNS Domain Name: ""
xConguration Network [1..1] DNS Server [1..3] Address
Dene the network addresses for DNS servers. Up to 3 addresses may be specied. If the network
addresses are unknown, contact your administrator or Internet Service Provider.
Value space: <S: 0, 64>
Format: String with a maximum of 64 characters.
Example: xConguration Network 1 DNS Server 1 Address: ""
xConguration Network [1..1] IPStack
Select which internet protocols the system will support.
Value space: <IPv4/IPv6>
IPv4: IP version 4 is supported.
IPv6: IP version 6 is supported, and the IPv4 settings (IP Address, IP Subnet Mask and Gateway)
will be disabled.
Example: xConguration Network 1 IPStack: IPv4
xConguration Network [1..1] IPv4 Address
Enter the static IPv4 network address for the system. Only applicable if the Network Assignment is set
to Static.
Value space: <S: 0, 64>
Format: Only the valid IP address format is accepted. Any IP address that contains letters
(192.a.2.0) or unvalid IP addresses (192.0.1234.0) will be rejected.
Retrieves a set of DHCP options from a DHCPv6 server.
Value space: <On/Off>
On: Enable the retrieval of a selected set of DHCP options from a DHCPv6 server.
O: Set to O when IPv6 Assignment is set to Static.
Example: xConguration Network 1 IPv6 DHCPOptions: On
xConguration Network [1..1] QoS Mode
The QoS (Quality of Service) is a method which handles the priorit y of audio, video, data, etc. in
the network. The QoS settings must be supported by the infrastructure. Diserv (Dierentiated
Services) is a computer networking architecture that species a simple, scalable and coarse-grained
mechanism for classifying, managing network trac and providing QoS priorities on modern IP
networks.
Value space: <Off/Diffserv>
O: No QoS method is used.
Diserv: When you set the QoS Mode to Diserv you must congure the Diserv sub menu
settings (Audio, Data, Signalling, Video, ICMPv6 and NTP).
The Diserv Audio denes which priorit y Audio packets should have in an IP network. The higher the
number, the higher the priority. These priorities might be overridden when packets are leaving the
network controlled by the local network administrator.
Value space: < 0..6 3 >
Range: Select a value from 0 to 63. A recommended value for Audio packets is Diserv Code
Point (DSCP) AF41, which equals the value 34. If in doubt, contact your network administrator.
The Diserv Data denes which priority Data packets should have in an IP network. The higher the
number, the higher the priority. These priorities might be overridden when packets are leaving the
network controlled by the local network administrator.
Value space: < 0..6 3 >
Range: Select a value from 0 to 63. A recommended value for Data packets is Diserv Code Point
(DSCP) AF23, which equals the value 22. If in doubt, contact your network administrator.
The Diserv Signalling denes which priority Signalling packets should have in an IP network. The
higher the number, the higher the priority. These priorities might be overridden when packets are
leaving the network controlled by the local network administrator.
Value space: < 0..6 3 >
Range: Select a value from 0 to 63. A recommended value for Signalling packets is Diserv Code
Point (DSCP) AF31, which equals the value 26. If in doubt, contact your network administrator.
The Diserv ICMPv6 denes which priority ICMPv6 packets should have in an IP network. The higher
the number, the higher the priority. These priorities might be overridden when packets are leaving the
network controlled by the local network administrator.
Value space: < 0..6 3 >
Range: Select a value from 0 to 63. A recommended value for ICMPv6 packets is Diserv Code
Point (DSCP) CS7, which equals the value 56. If in doubt, contact your network administrator.
The Diserv NTP denes which priority NTP packets should have in an IP network. The higher the
number, the higher the priority. These priorities might be overridden when packets are leaving the
network controlled by the local network administrator.
Value space: < 0..6 3 >
Range: Select a value from 0 to 63. A recommended value for NTP packets is Diserv Code Point
(DSCP) CS7, which equals the value 56. If in doubt, contact your network administrator.
The Diserv Video denes which priority Video packets should have in an IP network. The higher the
number, the higher the priority. These priorities might be overridden when packets are leaving the
network controlled by the local network administrator.
Value space: < 0..6 3 >
Range: Select a value from 0 to 63. A recommended value for Video packets is Diserv Code
Point (DSCP) AF41, which equals the value 34. If in doubt, contact your network administrator.
The Network Time Protocol (NTP) is used to synchronize the time of the system to a reference time
server. The time server will subsequently be queried ever y 24th hour for time updates. The time
will be displayed on the top of the screen. The system will use the time to timestamp messages
transmitted to Gatekeepers or Border Controllers requiring H.235 authentication. The system will
use the time to timestamp messages transmitted to Gatekeepers or Border Controllers that requires
H.235 authentication. It is also used for timestamping Placed Calls, Missed Calls and Received Calls.
Value space: <Off/Auto/Manual>
O: The system will not use an NTP server.
Auto: The system will use the NTP server, by which address is supplied from the DHCP server in
the network. If no DHCP ser ver is used, or the DHCP server does not provide the system with a
NTP server address, the system will use the static dened NTP server address specied by the
us e r.
Manual: The system will always use the static dened NTP server address specied by the user.
Enter the NTP Address to dene the network time protocol server address. This address will be used
if NTP Mode is set to Manual, or if set to Auto and no address is supplied by a DHCP server.
Set the conference encryption mode. A padlock with the text "Encryption On" or "Encryption O"
displays on screen for a few seconds when the conference starts.
Value space: <Bes t Effo r t/O n/Of f>
BestEort: The system will use encryption whenever possible.
1) In Point to point calls: If the far end system supports encryption (AES-128), the call will be
encrypted. If not, the call will proceed without encryption.
2) In MultiSite calls: In order to have encrypted MultiSite conferences, all sites must support
encryption. If not, the conference will be unencrypted.
On: The system will only allow calls that are encrypted.
O: The system will not use encryption.
Example: xConguration SIP Encryption: BestEffort
xConguration SIP Prole [1..1] URI
The SIP URI or number is used to address the system. This is the URI that is registered and used
by the SIP services to route inbound calls to the system. A Uniform Resource Identier (URI) is a
compact string of characters used to identify or name a resource.
Value space: <S: 0, 255>
Format: Compact string with a maximum of 255 characters.
The Proxy Address is the manually congured address for the outbound proxy. It is possible to use a
fully qualied domain name, or an IP address. The default port is 5060 for TCP and UDP but another
one can be provided. If Outbound is enabled, multiple proxies can be addressed.
Value space: <S: 0, 255>
Format: Compact string with a maximum of 255 characters. An IP address that contains letters
(192.a.2.0) or unvalid IP addresses (192.0.1234.0) will be rejected.
Select the transport protocol to be used over the LAN.
Value space: < U D P/TCP/T l s/ A u t o >
UDP: The system will always use UDP as the default transport method.
TCP: The system will always use TCP as the default transport method.
Tls: The system will always use TLS as the default transpor t method. For TLS connections a SIP
CA-list can be uploaded to the video system. If no such CA-list is available on the system then
anonymous Die Hellman will be used.
Auto: The system will try to connect using transport protocols in the following order: TLS, TCP,
U D P.
Example: xConguration SIP Prole 1 DefaultTransport: Auto
xConguration SIP Prole [1..1] Type
Enables SIP extensions and special behaviour for a vendor or provider.
Value space: <Standard/Alcatel/Avaya/Cisco/Microsoft/Nortel/Broadsoft>
Standard: To be used when registering to standard SIP Proxy (tested with Cisco TelePresence
VCS and Broadsoft)
Alcatel: To be used when registering to Alcatel-Lucent OmniPCX Enterprise. NOTE: This mode is
not fully supported.
Avaya: To be used when registering to Avaya Communication Manager. NOTE: This mode is not
fully supported.
Cisco: To be used when registering to Cisco Unied Communication Manager.
Microsoft: To be used when registering to Microsoft LCS or OCS. NOTE: This mode is not fully
supported.
Nortel: To be used when registering to Nortel MCS 5100 or MCS 5200 PBX. NOTE: This mode is
not fully supported.
Broadsoft: To be used when registering to Broadsoft.
Example: xConguration SIP Prole 1 Type: Standard
xConguration SIP Prole [1..1] Outbound
The client initiated connections mechanism for rewall traversal, connection reuse and redundancy.
The current version supports http://tools.ietf.org/html/draft-ietf-sip-outbound-20.
Value space: <On/Off>
On: Set up multiple outbound connections to servers in the Proxy Address list.
O: Connect to the single proxy congured rst in Proxy Address list.
Example: xConguration SIP Prole 1 Outbound: Off
xConguration SIP Prole [1..1] TlsVerify
For TLS connections a SIP CA-list can be uploaded to the video system.
Value space: <On/Off>
On: Set to On to verify TLS connections. Only TLS connections to servers, whose x.509 certicate
is validated against the CA-list, will be allowed.
O: Set to O to allow TLS connections without verifying them. The TLS connections are allowed
to be set up without verifying the x.509 certicate received from the server against the local CAlist. This should typically be selected if no SIP CA-list has been uploaded.
Example: xConguration SIP Prole 1 TlsVerify: Off
D14953.01 ISDN Link A PI Reference Guide IL1.0 June 2012.
Set the time zone where the system is located, using Windows time zone description format.
Value space: <GMT-12:00 (International Date Line West)/GMT-11:00 (Midway Island,
Samoa)/GMT-10:00 (Hawaii)/GMT-09:00 (Alaska)/GMT-08:00 (Pacic Time (US &
Canada); Tijuana)/GMT-07:00 (Arizona)/GMT-07:00 (Mountain Time (US & Canada))/
GMT-07:00 (Chihuahua, La Paz, Mazatlan)/GMT-06:00 (Central America)/GMT-06:00
(Saskatchewan)/GMT-06:00 (Guadalajara, Mexico City, Monterrey)/GMT-06:00 (Central
Time (US & Canada))/GMT-05:00 (Indiana (East))/GMT-05:00 (Bogota, Lima, Quito)/
GMT-05:00 (Eastern Time (US & Canada))/GMT-04:30 (Caracas)/GMT-04:00 (La Paz)/
GMT-04:00 (Santiago)/GMT-04:00 (Atlantic Time (Canada))/GMT-03:30 (Newfoundland)/
GMT-03:00 (Buenos Aires, Georgetown)/GMT-03:00 (Greenland)/GMT-03:00 (Brasilia)/
GMT-02:00 (Mid-Atlantic)/GMT-01:00 (Cape Verde Is.)/GMT-01:00 (Azores)/GMT
(Casablanca, Monrovia)/GMT (Coordinated Universal Time)/GMT (Greenwich Mean
Time : Du blin, Edinburgh, Lisbon, London)/GMT+01:00 (West Central Africa)/
GMT+01:00 (Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna)/GMT+01:00
(Brussels, Copenhagen, Madrid, Paris)/GMT+01:00 (Sarajevo, Skopje, Warsaw,
Zagreb)/GMT+01:00 (Belgrade, Bratislava, Budapest, Ljubljana, Prague)/GMT+02:00
(Harare, Pretoria)/GMT+02:00 (Jerusalem)/GMT+02:00 (Athens, Istanbul, Minsk)/
GMT+02:00 (Helsinki, Kyiv, Riga, Soa, Tallinn, Vilnius)/GMT+02:00 (Cairo)/
GMT+02:00 (Bucharest)/GMT+03:00 (Nairobi)/GMT+03:00 (Kuwait, Riyadh)/GMT+03:00
(Moscow, St. Petersburg, Volgograd)/GMT+03:00 (Baghdad)/GMT+03:30 (Tehran)/
GMT+04:00 (Abu Dhabi, Muscat)/GMT+04:00 (Baku, Tbilisi, Yerevan)/GMT+04:30
(Kabul)/GMT+05:00 (Islamabad, Karachi, Tashkent)/GMT+05:00 (Ekaterinburg)/
GMT+05:30 (Chennai, Kolkata, Mumbai, New Delhi)/GMT+05:45 (Kathmandu)/GMT+06:00
(Sri Jayawardenepura)/GMT+06:00 (Astana, Dhaka)/GMT+06:00 (Almaty, Novosibirsk)/
GMT+06:30 (Rangoon)/GMT+07:00 (Bangkok, Hanoi, Jakarta)/GMT+07:00 (Krasnoyarsk)/
GMT+08:00 (Perth)/GMT+08:00 (Taipei)/GMT+08:00 (Kuala Lumpur, Singapore)/GMT+08:00
(Beijing, Chongqing, Hong Kong, Uru mqi)/GMT+08:00 (Irkutsk, Ulaan Bataar)/
GMT+09:00 (Osaka, Sapporo, Tokyo)/GMT+09:00 (Seoul)/GMT+09:00 (Yakutsk)/GMT+09:30
(Darwin)/GMT+09:30 (Adelaide)/GMT+10:00 (Guam, Port Moresby)/GMT+10:00 (Brisbane)/
GMT+10:00 (Vladivostok)/GMT+10:00 (Hobart)/GMT+10:00 (Canberra, Melbourne,
Sydney)/GMT+11:00 (Magadan, Solomon Is., New Caledonia)/GMT+12:00 (Fiji,
Kamchatka, Marshall Is.)/GMT+12:00 (Auckland, Wellington)/GMT+13:00 (Nuku alofa)>
Range: Select a time zone from the list time zones. If using a command line interface; watch up for
typos.
Example: xConguration Time Zone: "GMT (Greenwich Mean Time : Dublin,
Edinburgh, Lisbon, London)"
The Experimental conguration
The Experimental settings are for testing only and should not be used unless agreed with Cisco.
These settings are not documented and WILL change in later releases.
D14953.01 ISDN Link A PI Reference Guide IL1.0 June 2012.
In the following pages you will nd a complete list of all xCommand type commands with
parameters. We recommend you visit our web site regularly for updated versions of the manual.
Go to: http://www.cisco.com/go/isdnlink-docs
API Reference Guide
The Boot commands
xCommand Boot
Reboot system.
Requires user role: USER
Example:
xCom mand Boot
*r BootResult (status=OK):
** end
OK
CUIL reboot request, restarting
Connection closed by foreign host.
The Security commands
xCommand Security FIPSMode Activate
Activate FIPS (140-2) mode. NOTE: Activating FIPS mode implies a reset to factory defaults.
While in FIPS mode, software upgrade is disabled and the following limitations will apply: All calls will
be encrypted. IEEE802.1x and SNMP are disabled. The SIP Prole Type setting cannot be Microsoft.
The root user is not available (root settings cannot be changed). To exit FIPS mode, perform a
factory reset.
Conrm: <Yes>
Requires user role: ADMIN
Parameters:
Conrm(r): <Yes>
Example:
xCom mand Security FIPSMode Activate Conrm: "Yes"
OK
*r SecurityFIPSModeActivateResult (status=OK)
** end
D14953.01 ISDN Link A PI Reference Guide IL1.0 June 2012.
Set an administrator password to restrict access to the ISDN Link.
Requires user role: USER
Parameters:
Password(r): <S: 0, 64>
Example:
xCom mand SystemUnit AdminPassword Set Password: ""
*r SystemUnitAdminPasswordSetResult (status=OK):
** end
xCommand SystemUnit DateTime Set
Set the date and time for the system, if not available from NTP (Network Time Protocol). See the
xConguration NetworkServices NTP Mode
Requires user role: ADMIN
Parameters:
Year: <2008..2037>
Mo n t h : <1..12 >
Day : <1. .31>
Hour: <0..23>
Minute: <0..59>
Second: <0..59>
Example:
xCom mand SystemUnit DateTime Set Year:2012 Month:7 Day:1 Hour:12 Minute:0
Se c ond:0
*r SystemUnitDateTimeSetResult (status=OK):
** end
xCommand SystemUnit DateTime Get
Read the time and date from the system.
Requires user role: USER
Example:
xCom mand SystemUnit DateTime get
*r SystemUnitDateTimeGetResult (status=OK):
Year: 2012
Month: 7
Day: 1
Hour: 12
Minute: 0
Second: 0
** end
xCommand SystemUnit FactoryReset
Reset the codec to factory default settings. The call logs will be deleted and all system parameters
will be reset to default values. All les that have been uploaded to the codec will be deleted. The
Release key and Option key will not be aected.
As a default the system restar ts after the factory reset.
Requires user role: ADMIN
Parameters:
Conrm(r): <Yes>
Example:
xCom mand SystemUnit FactoryReset Conrm: Yes
*r SystemUnitFactoryResetResult (status=OK):
** end
D14953.01 ISDN Link A PI Reference Guide IL1.0 June 2012.
The following pages will list an example of the xStatus commands and the response. Status
type commands returns information about the system and system processes. You can query all
information or just some of it.
We recommend you visit our web site regularly for updated versions of the manual.
Go to:
http://www.cisco.com/go/isdnlink-docs
API Reference Guide
Call status
ISDN Link operates as a gateway between a Caller and a Callee. Thus xStatus referring to
"Caller" is about the calling party or the connection between the calling party and the ISDN
Link. Similarly xStatus referring to "Callee" is about the called party or the connection between
the ISDN Link and the called party.
xStatus Call
Shows the top level overview of the call status. The call identity is used when querying for additional
information about the call.
xStatus Call [1..n] Caller Status
xStatus Call [1..n] Callee Status
Shows the call status between the calling par ty and the ISDN Link (Caller Status) or between the
ISDN Link and the called party (Callee Status). You can run the command xStatus Call to nd the call
identity.
Shows the call protocol being used between the calling party and the ISDN Link (Caller Protocol) or
between the ISDN Link and the called party (Callee Protocol).You can run the command xStatus Call
to nd the call identity.
Shows the number or URI of the calling party (Caller RemoteNumber) or called party (Callee
RemoteNumber). You can run the command xStatus Call to nd the call identity.
Shows the number or URI that ISDN Link shall use when calling back to the calling party (Caller
CallbackNumber) or called party (Callee CallbackNumber). You can run the command xStatus Call to
nd the call identity.
Value space of the result returned:
<String>
Example:
xStatus Call 20 Callee CallbackNumber
*s Call 20 Callee Call backNum ber: "1234"
** end
xStatus Call [1..n] Caller LocalNumber
Shows the number called to reach the ISDN Link. For SIP callers this would be the number and
parameters needed to reach the callee.
Shows the number from which the ISDN Link is calling. This number is the callback number for the
called party. For SIP callee's this would include the number and parameters to perform callback to the
caller side.
Shows the transmit bandwidth used between the calling party and the ISDN Link (Caller
TransmitCallRate) or between the ISDN Link and the called party (Callee TransmitCallRate). The
bandwidth is in kilobits per second (kbps). You can run the command xStatus Call to nd the call
identity.
Shows the receive bandwidth used between the calling party and the ISDN Link (Caller
ReceiveCallRate) or between the ISDN Link and the called par ty (Callee ReceiveCallRate). The
bandwidth is in kilobits per second (kbps). You can run the command xStatus Call to nd the call
identity.
Value space of the result returned:
<Integer>
Example:
xStatus Call 20 Caller ReceiveCallRate
*s Call 20 Caller ReceiveCallRate: 1920
** end
xStatus Call [1..n] Caller Encryption Type
xStatus Call [1..n] Callee Encryption Type
Shows the encryption type used between the calling party and the ISDN Link (Caller Encryption Type)
or between the ISDN Link and the called part y (Callee Encryption Type). You can run the command
xStatus Call to nd the call identity
Value space of the result returned:
< "N o n e "/ "Ae s -12 8">
Example:
xStatus Call 20 Caller Encryption Type
*s Call 20 Caller Encryption Ty pe: "Aes-128"
** end
D14953.01 ISDN Link A PI Reference Guide IL1.0 June 2012.
Shows the top level overview of the External Network inter face (V.35, RS-366, RS-449 or RS-530)
status.
Cisco TelePresence ISDN Link has three communication interfaces: ISDN BRI, ISDN PRI and External
Network. Only one of these interfaces can be enabled at any time.
Shows the status of the External Network interface.
Ready: The external network is ready to relay calls.
NotReady: The external network is not ready for use, e.g. when clock is missing or the line is broken.
O: The external network is not enabled (i.e. xConguration H320 NetType is not set to External).
Shows the clock rate (in kbps) used for synchronous communication on the external network. This
clock is provided by the attached equipment.
Value space of the result returned:
<Integer>
Example:
xStatus ExternalNetwork Interface 1 ClockRate
*s ExternalNetwork Interface 1 ClockRate: 1920
** end
xStatus ExternalNetwork Interface [1..1] Channel [1..n] Status
Gives information about the call progress in a channel on the external interface. The information
indicates the various stages each channel goes through whilst establishing a connection.
Idle: The channel is idle. This state is normally only seen if the channel has never been used.
Calling: The network has acknowledged an incoming call, but the connection is not yet established.
Answering: The network has acknowledged an outgoing call, but the connection is not yet
established.
Connect: The connection is established.
Disconnecting: Waiting for the network to conrm the termination of the incoming or outgoing call.
Disconnected: The network has acknowledged the termination of the call. The channel is available for
Shows where the disconnection of a call on the external network is originated. The location codes are
specied in ITU-T Recommendation Q.931 (the Cause information element).
Shows the reason why a call on the external network is disconnected. The cause values are specied
in ITU-T Recommendation Q.931 (the Cause information element).
Some common cause values are listed below; ITU-T Q.931 contains the complete list.
1: Unallocated (unassigned) number
2: No route to specied transit network
16: Normal call clearing
17: User busy
18: No user responding
21: Call rejected
28: Invalid number format
29: Facility rejected
31: Normal, unspecied
34: No circuit/channel available
41: Temporary failure
58: Bearer capability not presently available
65: Bearer capability not implemented
69: Requested facility not implemented
81: Invalid call reference value
88: Incompatible destination
100: Invalid information element contents
102: Recovery on timer expiry
127: Interworking, unspecied
128-255: Cisco specic codes
Shows which one of ISDN Link's communication interfaces is enabled. Note that only one inter face is
enabled at a time.
BRI: The ISDN BRI interface is enabled.
PRI: The ISDN PRI interface is enabled.
External: The external network (NET) interface is enabled.
G703: For testing only.
Shows the status of the PRI interface.
Ready: The PRI interface is ready to relay calls.
NotReady: The PRI interface is not ready for use, e.g. when synchronization is missing or the line is
broken.
O: The PRI interface is not enabled (i.e. xConguration H320 NetType is not set to PRI).
Value space of the result returned:
<Ready/NotReady/O>
Example:
xStatus ISDN PRI Interface 1 Status
*s ISDN PRI Interface 1 Status: Ready
** end
xStatus ISDN PRI Interface [1..1] BChansFree
Shows the number of B channels (bearer channels, 64 kbps) currently available on the PRI interface.
Value space of the result returned:
<0..30>
Example:
xStatus ISDN PRI Interface 1 BChansFree
*s ISDN PRI Interface 1 BChansFree: 18
** end
D14953.01 ISDN Link A PI Reference Guide IL1.0 June 2012.
Shows how many B channels (bearer channels, 64 kbps) the PRI interface oers in total.
Value space of the result returned:
<1..30 >
Example:
xStatus ISDN PRI Interface 1 BChansTotal
*s ISDN PRI Interface 1 BChansTotal: 30
** end
xStatus ISDN PRI Interface [1..1] Layer1Status
Shows whether there are issues relating to framing information (physical layer).
Sync: The system is receiving framing information and the channels are synchronized.
Yellow: The system is receiving framing information, but the remote system is not receiving the
transmitted framing information. This may be caused by a broken connector in the TX part of your PRI
cable. It could also indicate a weak or noisy signal in the TX part of the PRI cable.
Red: There is no signal and thus the system receives no framing information from the remote site (this
has the same eect as pulling out the PRI cable).
Blue: The network on the far side of the CSU (Channel Services Unit) is unavailable. For example,
assume that a system is connected via a CSU (Channel Services Unit) as follows: System–CableA–
CSU–CableB–Network. If the CSU loses framing/synchronisation from the network, e.g. due to a bad
CableB, it will no longer send valid framing out on CableA towards the system. Instead it transmits
"Blue Alarm". Seen from the system receiving the blue alarm, this means that the network on the far
side of the CSU is unavailable.
Unknown: The system is not able to determine the layer 1 status.
Value space of the result returned:
<Sync/Yellow/Red/Blue/Unknown>
Example:
xStatus ISDN PRI Interface 1 Layer1Status
*s ISDN PRI Interface 1 Layer1Status: Sync
** end
xStatus ISDN PRI Interface [1..1] Channel [1..n] Type
Shows the channel type for a channel on the PRI interface. The PRI interface comprises a number of
channels, each dedicated to either the primary communication or to control and signalling information.
DChannel: The channel is a data channel (D channel), which carries the control and signalling
information in ISDN. The bit rate of the D channel on a PRI interface is 64 kbps.
BChannel: The channel is a bearer channel (B channel), which carries the primary video conference
or speech call communication in ISDN. The bit rate of a B channel on a PRI interface is 64 kbps.
Value space of the result returned:
<DChannel/BChannel>
Example:
xStatus ISDN PRI Interface 1 Channel 1 Ty pe
*s ISDN PRI Interface 1 Channel 1 Type: BChannel
** end
xStatus ISDN PRI Interface [1..1] Channel [1..n] Status
Gives information about the call progress in a channel on the PRI interface. The information indicates
the various stages each channel goes through whilst establishing a connection.
Idle: The channel is idle. This state is normally only seen if the channel has never been used.
Calling: The network has acknowledged an incoming call, but the connection is not yet established.
Answering: The network has acknowledged an outgoing call, but the connection is not yet
established.
Connect: The connection is established.
Disconnecting: Waiting for the network to conrm the termination of the incoming or outgoing call.
Disconnected: The network has acknowledged the termination of the call. The channel is available for
xStatus ISDN PRI Interface [1..1] Channel [1..n] Call [1..n] CallingNumber
Shows the number calling into the ISDN PRI interface (for an incoming call), and the number that ISDN
Link is making a call to on the ISDN PRI interface (for an outgoing call).
Value space of the result returned:
<String>
Example:
xStatus ISDN PRI Interface 1 Channel 1 Call 20 CallingNum ber
xStatus ISDN PRI Interface [1..1] Channel [1..n] Call [1..n] CauseLocation
Shows where the disconnection of a call on the PRI interface is originated. The location codes are
specied in ITU-T Recommendation Q.931 (the Cause information element).
Value space of the result returned:
<Integer>
Example:
xStatus ISDN PRI Interface 1 Channel 1 Call 20 CauseLocation
xStatus ISDN PRI Interface [1..1] Channel [1..n] Call [1..n] ChannelCause
Shows the reason why a call on the PRI interface is disconnected. The cause values are specied in
ITU-T Recommendation Q.931 (the Cause information element).
Some common cause values are listed below; ITU-T Q.931 contains the complete list.
1: Unallocated (unassigned) number
2: No route to specied transit network
16: Normal call clearing
17: User busy
18: No user responding
21: Call rejected
28: Invalid number format
29: Facility rejected
31: Normal, unspecied
34: No circuit/channel available
41: Temporary failure
58: Bearer capability not presently available
65: Bearer capability not implemented
69: Requested facility not implemented
81: Invalid call reference value
88: Incompatible destination
100: Invalid information element contents
102: Recovery on timer expiry
127: Interworking, unspecied
128-255: Cisco specic codes
Value space of the result returned:
<Integer>
Example:
xStatus ISDN PRI Interface 1 Channel 1 Call 20 ChannelCause
Shows the status of the BRI interface.
Ready: The BRI interface is ready to relay calls.
NotReady: The BRI interface is not ready for use, e.g. when synchronization is missing or the line is
broken.
O: The BRI interface is not enabled (i.e. xConguration H320 NetType is not set to BRI).
Value space of the result returned:
<Ready/NotReady/O>
Example:
xStatus ISDN BRI Interface 1 Status
*s ISDN BRI Interface 1 Status: Ready
** end
xStatus ISDN BRI Interface [1..4] Layer1Alarm
Shows whether or not there are any alarms related to the physical layer, e.g. cable not properly
connected to switch.
On: Layer 1 alarm.
O: No alarm.
Value space of the result returned:
<On/O>
Example:
xStatus ISDN BRI Interface 1 Layer1Alarm
*s ISDN BRI Interface 1 Layer1Alarm: Off
** end
D14953.01 ISDN Link A PI Reference Guide IL1.0 June 2012.
Shows whether there are any alarms related to the data-link layer.
On: Layer 2 alarm.
O: No alarm.
Value space of the result returned:
<On/O>
Example:
xStatus ISDN BRI Interface 1 Layer2Alarm
*s ISDN BRI Interface 1 Layer2Alarm: Off
** end
xStatus ISDN BRI Interface [1..4] Channel [1..3] Type
Shows the channel type for a channel on a BRI interface. A BRI interface comprises two channels for
the primary communication and one channel for control and signalling information.
DChannel: The channel is a data channel (D channel), which carries the control and signalling
information in ISDN. The bit rate of the D channel of a BRI interface is 16 kbps.
BChannel: The channel is a bearer channel (B channel), which carries the primary video conference
or speech call communication in ISDN. The bit rate of a B channel on a BRI interface is 64 kbps.
Value space of the result returned:
<DChannel/BChannel>
Example:
xStatus ISDN BRI Interface 1 Channel 1 Ty pe
*s ISDN BRI Interface 1 Channel 1 Type: BChannel
** end
xStatus ISDN BRI Interface [1..4] Channel [1..3] Status
Gives information about the call progress in a channel on a BRI interface. The information indicates
the various stages each channel goes through whilst establishing a connection.
Idle: The channel is idle. This state is normally only seen if the channel has never been used.
Calling: The network has acknowledged an incoming call, but the connection is not yet established.
Answering: The network has acknowledged an outgoing call, but the connection is not yet
established.
Connect: The connection is established.
Disconnecting: Waiting for the network to conrm the termination of the incoming or outgoing call.
Disconnected: The network has acknowledged the termination of the call. The channel is available for
Shows the number calling into the ISDN BRI interface (for an incoming call), and the number that ISDN
Link is making a call to on the ISDN BRI interface (for an outgoing call).
Shows where the disconnection of a call on the BRI interface is originated. The location codes are
specied in ITU-T Recommendation Q.931 (the Cause information element).
Shows the reason why a call on the BRI interface is disconnected. The cause values are specied in
ITU-T Recommendation Q.931 (the Cause information element).
Some common cause values are listed below; ITU-T Q.931 contains the complete list.
1: Unallocated (unassigned) number
2: No route to specied transit network
16: Normal clearing
17: User busy
18: No user responding
21: Call rejected
28: Invalid number format
29: Facility rejected
31: Normal, unspecied
34: No circuit/channel available
41: Temporary failure
58: Bearer capability not presently available
65: Bearer capability not implemented
69: Requested facility not implemented
81: Invalid call reference value
88: Incompatible destination
100: Invalid information element contents
102: Recovery on timer expiry
127: Interworking, unspecied
128-255: Cisco specic codes
ISDN Link operates as a gateway between a Caller and a Callee. Thus xStatus referring to
"Caller" is about the calling party or the connection between the calling party and the ISDN Link.
Similarly xStatus referring to "Callee" is about the called party or the connection between the
ISDN Link and the called party.
xStatus MediaChannels
Shows the top level overview of the media channel status. The example shows the status for an
ongoing call. The identities of the call and channels are used when querying additional information.
Example:
xStatus MediaChannels
*s MediaChannels Call 20 Caller IncomingAudioChannel 1 Encryption Status:
On
*s MediaChannels Call 20 Callee OutgoingVideoChan nel 2 Encry ption Status:
Off
*s MediaChannels Call 20 Callee OutgoingVideoChan nel 2 ChannelRole: Main
*s MediaChannels Call 20 Callee OutgoingVideoChan nel 2 Video Protocol: H264
*s MediaChannels Call 20 Callee OutgoingVideoChan nel 3 Encry ption Status:
Off
*s MediaChannels Call 20 Callee OutgoingVideoChan nel 3 ChannelRole:
Presentation
*s MediaChannels Call 20 Callee OutgoingVideoChan nel 3 Video Protocol: Off
** end
xStatus MediaChannels Call [1..n] Caller IncomingAudioChannel [1..n] Encryption Status
xStatus MediaChannels Call [1..n] Caller OutgoingAudioChannel [1..n] Encryption Status
xStatus MediaChannels Call [1..n] Callee IncomingAudioChannel [1..n] Encryption Status
xStatus MediaChannels Call [1..n] Callee OutgoingAudioChannel [1..n] Encryption Status
Shows the encryption status on the incoming or outgoing audio channel, on the connection between
the ISDN Link and the calling party (Caller) or between the ISDN Link and the called party (Callee).
Value space of the result returned:
<On/O>
Example:
xStatus MediaChannels Call 20 IncomingAudioChannel 1 Encry ption Status
*s MediaChannels Call 20 IncomingAudioChannel 1 Encry ption Status: On
Shows the audio algorithm for the incoming or outgoing audio channel, on the connection between
the ISDN Link and the calling party (Caller) or between the ISDN Link and the called party (Callee).
G722: The G.722 algorithm is an ITU-T standard.
G7221: The G.722.1 algorithm is a licensed royalty-free ITU-T standard.
G711Mu: The G.711 Mu-law compression algorithm is used in North America and Japan.
G711A: The G.711 A-law compression algorithm is used in Europe and the rest of the world.
Audio mute status of incoming audio on the connection between the ISDN Link and the calling party
(Caller) or between the ISDN Link and the called party (Callee).
Shows the number of incoming or outgoing audio channels, on the connection between the ISDN Link
and the calling party (Caller) or between the ISDN Link and the called party (Callee).
xStatus MediaChannels Call [1..n] Caller IncomingAudioChannel [1..n] Transport RTP
Local IpAddress
xStatus MediaChannels Call [1..n] Caller OutgoingAudioChannel [1..n] Transport RTP
Local IpAddress
xStatus MediaChannels Call [1..n] Callee IncomingAudioChannel [1..n] Transport RTP
Local IpAddress
xStatus MediaChannels Call [1..n] Callee OutgoingAudioChannel [1..n] Transport RTP
Local IpAddress
Shows the local IP address of the Real-time Transport Protocol (RTP) port for the incoming or
outgoing audio, on the connection between the ISDN Link and the calling par ty (Caller) or between
the ISDN Link and the called party (Callee).
Value space of the result returned:
<String>
Example:
xStatus MediaChannels Call 20 IncomingAudioChannel 1 Transport RTP Local
IpAddress
*s MediaChannels Call 20 IncomingAudioChannel 1 Transport RTP Local
Ip A d d r e ss: "192.0.2.54"
** end
xStatus MediaChannels Call [1..n] Caller IncomingAudioChannel [1..n] Transport RTP
Local Port
xStatus MediaChannels Call [1..n] Caller OutgoingAudioChannel [1..n] Transport RTP
Local Port
xStatus MediaChannels Call [1..n] Callee IncomingAudioChannel [1..n] Transport RTP
Local Port
xStatus MediaChannels Call [1..n] Callee OutgoingAudioChannel [1..n] Transport RTP
Local Port
Shows the local UDP port number of the Real-time Transport Protocol (RTP) port for the incoming or
outgoing audio, on the connection between the ISDN Link and the calling par ty (Caller) or between
the ISDN Link and the called party (Callee).
Value space of the result returned:
<Integer>
Example:
xStatus MediaChannels Call 20 IncomingAudioChannel 1 Transport RTP Local
Port
*s MediaChannels Call 20 IncomingAudioChannel 1 Transport RTP Local Port:
2326
Shows the remote IP address of the Real-time Transport Protocol (RTP) port for the incoming or
outgoing audio, on the connection between the ISDN Link and the calling par ty (Caller) or between
the ISDN Link and the called party (Callee).
Value space of the result returned:
<String>
Example:
xStatus MediaChannels Call 20 IncomingAudioChannel 1 Transport RTP Remote
IpAddress
*s MediaChannels Call 20 IncomingAudioChannel 1 Transport RTP Remote
Ip A d d r e ss: "192.0.2.181"
** end
D14953.01 ISDN Link A PI Reference Guide IL1.0 June 2012.
xStatus MediaChannels Call [1..n] Caller IncomingAudioChannel [1..n] Transport RTP
Remote Port
xStatus MediaChannels Call [1..n] Caller OutgoingAudioChannel [1..n] Transport RTP
Remote Port
xStatus MediaChannels Call [1..n] Callee IncomingAudioChannel [1..n] Transport RTP
Remote Port
xStatus MediaChannels Call [1..n] Callee OutgoingAudioChannel [1..n] Transport RTP
Remote Port
Shows the remote UDP port number of the Real-time Transport Protocol (RTP) port for the incoming
or outgoing audio, on the connection between the ISDN Link and the calling party (Caller) or between
the ISDN Link and the called party (Callee).
Value space of the result returned:
<Integer>
Example:
xStatus MediaChannels Call 20 IncomingAudioChannel 1 Transport RTP Remote
Port
xStatus MediaChannels Call [1..n] Caller IncomingAudioChannel [1..n] Transport RTCP
Local IpAddress
xStatus MediaChannels Call [1..n] Caller OutgoingAudioChannel [1..n] Transport RTCP
Local IpAddress
xStatus MediaChannels Call [1..n] Callee IncomingAudioChannel [1..n] Transport RTCP
Local IpAddress
xStatus MediaChannels Call [1..n] Callee OutgoingAudioChannel [1..n] Transport RTCP
Local IpAddress
Shows the local IP address of the Real-time Transport Control Protocol (RTCP) port for the incoming
or outgoing audio, on the connection between the ISDN Link and the calling party (Caller) or between
the ISDN Link and the called party (Callee).
Value space of the result returned:
<String>
Example:
xStatus MediaChannels Call 20 IncomingAudioChannel 1 Transport RTCP Local
IpAddress
*s MediaChannels Call 20 IncomingAudioChannel 1 Transport RTCP Local
Ip A d d r e ss: "192.0.2.54"
** end
xStatus MediaChannels Call [1..n] Caller IncomingAudioChannel [1..n] Transport RTCP
Local Port
xStatus MediaChannels Call [1..n] Caller OutgoingAudioChannel [1..n] Transport RTCP
Local Port
xStatus MediaChannels Call [1..n] Callee IncomingAudioChannel [1..n] Transport RTCP
Local Port
xStatus MediaChannels Call [1..n] Callee OutgoingAudioChannel [1..n] Transport RTCP
Local Port
Shows the local UDP port number of the Real-time Transport Control Protocol (RTCP) port for the
incoming or outgoing audio, on the connection between the ISDN Link and the calling party (Caller) or
between the ISDN Link and the called party (Callee).
Value space of the result returned:
<Integer>
Example:
xStatus MediaChannels Call 20 IncomingAudioChannel 1 Transport RTCP Local
Port
*s MediaChannels Call 20 IncomingAudioChannel 1 Transport RTCP Local Port:
2327
Shows the remote IP address of the Real-time Transport Control Protocol (RTCP) port for the
incoming or outgoing audio, on the connection between the ISDN Link and the calling party (Caller) or
between the ISDN Link and the called party (Callee).
Value space of the result returned:
<String>
Example:
xStatus MediaChannels Call 20 IncomingAudioChannel 1 Transport RTCP Remote
IpAddress
*s MediaChannels Call 20 IncomingAudioChannel 1 Transport RTCP Remote
Ip A d d r e ss: "192.0.2.181"
** end
D14953.01 ISDN Link A PI Reference Guide IL1.0 June 2012.
xStatus MediaChannels Call [1..n] Caller IncomingAudioChannel [1..n] Transport RCTP
Remote Port
xStatus MediaChannels Call [1..n] Caller OutgoingAudioChannel [1..n] Transport RTCP
Remote Port
xStatus MediaChannels Call [1..n] Callee IncomingAudioChannel [1..n] Transport RTCP
Remote Port
xStatus MediaChannels Call [1..n] Callee OutgoingAudioChannel [1..n] Transport RTCP
Remote Port
Shows the remote UDP port number of the Real-time Transport Control Protocol (RTCP) port for the
incoming or outgoing audio, on the connection between the ISDN Link and the calling party (Caller) or
between the ISDN Link and the called party (Callee).
Value space of the result returned:
<Integer>
Example:
xStatus MediaChannels Call 20 IncomingAudioChannel 1 Transport RTCP Remote
Port
xStatus MediaChannels Call [1..n] Caller IncomingVideoChannel [1..n] Encryption Status
xStatus MediaChannels Call [1..n] Caller OutgoingVideoChannel [1..n] Encryption Status
xStatus MediaChannels Call [1..n] Callee IncomingVideoChannel [1..n] Encryption Status
xStatus MediaChannels Call [1..n] Callee OutgoingVideoChannel [1..n] Encryption Status
Shows the encryption status on the incoming or outgoing video channel, on the connection between
the ISDN Link and the calling party (Caller) or between the ISDN Link and the called party (Callee).
Value space of the result returned:
<On/O>
Example:
xStatus MediaChannels Call 20 IncomingVideoCha nnel 2 Encryption Status
*s MediaChannels Call 20 IncomingVideoChannel 2 Encryption Status: On
Shows whether the incoming or outgoing channel is the main video channel or the presentation
channel. The status is for the connection between the ISDN Link and the calling party (Caller) or
between the ISDN Link and the called party (Callee)
*s MediaChannels Call 20 IncomingVideoChannel 2 ChannelRole: Main
** end
xStatus MediaChannels Call [1..n] Caller IncomingVideoChannel [1..n] Video Protocol
xStatus MediaChannels Call [1..n] Caller OutgoingVideoChannel [1..n] Video Protocol
xStatus MediaChannels Call [1..n] Callee IncomingVideoChannel [1..n] Video Protocol
xStatus MediaChannels Call [1..n] Callee OutgoingVideoChannel [1..n] Video Protocol
Shows the video algorithm for the incoming or outgoing video channel, on the connection between
the ISDN Link and the calling party (Caller) or between the ISDN Link and the called party (Callee).
H264: The H.264 algorithm is an ITU-T standard for video compression.
H263pp: The H.263pp algorithm is an ITU-T standard for video compression.
H263: The H.263 algorithm is an ITU-T standard for video compression.
H261: The H.261 algorithm is an ITU-T standard for video compression.
Value space of the result returned:
<H264/H263pp/H263/H261>
Example:
xStatus MediaChannels Call 20 IncomingVideoCha nnel 2 Video Protocol
*s MediaChannels Call 20 IncomingVideoChannel 2 Video Protocol: H264
** end
D14953.01 ISDN Link A PI Reference Guide IL1.0 June 2012.
xStatus MediaChannels Call [1..n] Caller IncomingVideoChannel [1..n] Transport RTP
Local IpAddress
xStatus MediaChannels Call [1..n] Caller OutgoingVideoChannel [1..n] Transport RTP
Local IpAddress
xStatus MediaChannels Call [1..n] Callee IncomingVideoChannel [1..n] Transport RTP
Local IpAddress
xStatus MediaChannels Call [1..n] Callee OutgoingVideoChannel [1..n] Transport RTP
Local IpAddress
Shows the local IP address of the Real-time Transport Protocol (RTP) port for the incoming or
outgoing video, on the connection bet ween the ISDN Link and the calling party (Caller) or between
the ISDN Link and the called party (Callee).
Value space of the result returned:
<String>
Example:
xStatus MediaChannels Call 20 IncomingVideoCha nnel 2 Transport RTP Local
IpAddress
*s MediaChannels Call 20 IncomingVideoChannel 2 Transport RTP Local
Ip A d d r e ss: "192.0.2.54"
** end
xStatus MediaChannels Call [1..n] Caller IncomingVideoChannel [1..n] Transport RTP
Local Port
xStatus MediaChannels Call [1..n] Caller OutgoingVideoChannel [1..n] Transport RTP
Local Port
xStatus MediaChannels Call [1..n] Callee IncomingVideoChannel [1..n] Transport RTP
Local Port
xStatus MediaChannels Call [1..n] Callee OutgoingVideoChannel [1..n] Transport RTP
Local Port
Shows the local UDP port number of the Real-time Transport Protocol (RTP) port for the incoming or
outgoing video, on the connection bet ween the ISDN Link and the calling party (Caller) or between
the ISDN Link and the called party (Callee).
Value space of the result returned:
<Integer>
Example:
xStatus MediaChannels Call 20 IncomingVideoCha nnel 2 Transport RTP Local
Port
*s MediaChannels Call 20 IncomingVideoChannel 2 Transport RTP Local Port:
2342
Shows the remote IP address of the Real-time Transport Protocol (RTP) port for the incoming or
outgoing video, on the connection bet ween the ISDN Link and the calling party (Caller) or between
the ISDN Link and the called party (Callee).
*s MediaChannels Call 20 IncomingVideoChannel 2 Transport RTP Remote
Ip A d d r e ss: "192.0.2.181"
** end
xStatus MediaChannels Call [1..n] Caller IncomingVideoChannel [1..n] Transport RTP
Remote Port
xStatus MediaChannels Call [1..n] Caller OutgoingVideoChannel [1..n] Transport RTP
Remote Port
xStatus MediaChannels Call [1..n] Callee IncomingVideoChannel [1..n] Transport RTP
Remote Port
xStatus MediaChannels Call [1..n] Callee OutgoingVideoChannel [1..n] Transport RTP
Remote Port
Shows the remote UDP port number of the Real-time Transpor t Protocol (RTP) port for the incoming
or outgoing video, on the connection between the ISDN Link and the calling party (Caller) or between
the ISDN Link and the called party (Callee).
Value space of the result returned:
<Integer>
Example:
xStatus MediaChannels Call 20 IncomingVideoCha nnel 2 Transport RTP Remote
Port
xStatus MediaChannels Call [1..n] Calller IncomingVideoChannel [1..n] Transport RTCP
Local IpAddress
xStatus MediaChannels Call [1..n] Caller OutgoingVideoChannel [1..n] Transport RTCP
Local IpAddress
xStatus MediaChannels Call [1..n] Callee IncomingVideoChannel [1..n] Transport RTCP
Local IpAddress
xStatus MediaChannels Call [1..n] Callee OutgoingVideoChannel [1..n] Transport RTCP
Local IpAddress
Shows the local IP address of the Real-time Transport Control Protocol (RTCP) port for the incoming
or outgoing video, on the connection between the ISDN Link and the calling party (Caller) or between
the ISDN Link and the called party (Callee).
Value space of the result returned:
<String>
Example:
xStatus MediaChannels Call 20 IncomingVideoCha nnel 2 Transport RTCP Local
IpAddress
*s MediaChannels Call 20 IncomingVideoChannel 2 Transport RTCP Local
Ip A d d r e ss: "192.0.2.54"
** end
xStatus MediaChannels Call [1..n] Caller IncomingVideoChannel [1..n] Transport RTCP
Local Port
xStatus MediaChannels Call [1..n] Caller OutgoingVideoChannel [1..n] Transport RTCP
Local Port
xStatus MediaChannels Call [1..n] Callee IncomingVideoChannel [1..n] Transport RTCP
Local Port
xStatus MediaChannels Call [1..n] Callee OutgoingVideoChannel [1..n] Transport RTCP
Local Port
Shows the local UDP port number of the Real-time Transport Control Protocol (RTCP) port for the
incoming or outgoing video, on the connection between the ISDN Link and the calling party (Caller) or
between the ISDN Link and the called party (Callee).
Value space of the result returned:
<Integer>
Example:
xStatus MediaChannels Call 20 IncomingVideoCha nnel 2 Transport RTCP Local
Port
*s MediaChannels Call 20 IncomingVideoChannel 2 Transport RTCP Local Port:
2343
Shows the remote IP address of the Real-time Transport Control Protocol (RTCP) port for the
incoming or outgoing video, on the connection between the ISDN Link and the calling party (Caller) or
between the ISDN Link and the called party (Callee).
*s MediaChannels Call 20 IncomingVideoChannel 2 Transport RTCP Remote
Ip A d d r e ss: "192.0.2.181"
** end
xStatus MediaChannels Call [1..n] Caller IncomingVideoChannel [1..n] Transport RCTP
Remote Port
xStatus MediaChannels Call [1..n] Caller OutgoingVideoChannel [1..n] Transport RTCP
Remote Port
xStatus MediaChannels Call [1..n] Callee IncomingVideoChannel [1..n] Transport RTCP
Remote Port
xStatus MediaChannels Call [1..n] Callee OutgoingVideoChannel [1..n] Transport RTCP
Remote Port
Shows the remote UDP port number of the Real-time Transpor t Control Protocol (RTCP) port for the
incoming or outgoing video, on the connection between the ISDN Link and the calling party (Caller) or
between the ISDN Link and the called party (Callee).
Value space of the result returned:
<Integer>
Example:
xStatus MediaChannels Call 20 IncomingVideoCha nnel 2 Transport RTCP Remote
Port
Shows the status of the communication between the endpoint and the SIP Proxy server.
Active: The communication between the endpoint and the SIP Proxy is active.
DNSFailed: The attempt to establish communication to the DNS server failed.
O: There is no communication between the endpoint and the SIP Proxy.
Timeout: The attempt to establish communication to the SIP Proxy timed out.
UnableTCP: The system is unable to use TCP as the transport method.
UnableTLS: The system is unable to use TLS as the transport method.
Unknown: The status of the communication is not known.
Shows the address of the SIP Proxy that the system communicates with.
Value space of the result returned:
<String>
Example:
xStatus SIP Prole 1 Proxy 1 Address
*s SIP Prole 1 Proxy 1 Address: "192.0.2.50"
** end
xStatus SIP Prole [1..1] Secure
Shows the encryption status of the signalling with the SIP Proxy server.
Value space of the result returned:
<True/False>
Example:
xStatus SIP Prole 1 Secure
*s SIP Prole 1 Secure: True
** end
xStatus SIP Prole [1..1] Veried
Shows whether or not the SSL certicate of the server that the video system / codec tries to register
to is included in the codec’s trusted CA-list. The ser ver will typically be a Cisco VCS or Cisco Unied
CM (CUCM).
True: The server’s SIP certicate is checked against the trusted CA-list on the codec and found valid.
Additionally, the fully qualied domain name of the server matches the valid certicate.
False: A TLS connection is not set up because the SIP cer ticate verication failed or the domain
name did not match. Note that the status will also return False when TLS is not used (SIP Prole [1..1]
DefaultTransport not set to TLS) or certicate verication is switched o (SIP Prole TlsVerify set to
O).
Value space of the result returned:
<True/False>
Example:
xStatus SIP Prole 1 Veried
*s SIP Prole 1 Veried: False
** end
D14953.01 ISDN Link A PI Reference Guide IL1.0 June 2012.
Shows which authentication mechanism is used when registering to the SIP Proxy Server.
Digest: Uses the Digest access authentication method, as specied by RFC 2069.
NTLM: Uses the NTLM authentication method, which is a Microsoft authentication protocol.
O: No authentication mechanism is used.
Value space of the result returned:
<Digest/NTLM/O>
Example:
xStatus SIP Prole 1 Authentication
*s SIP Prole 1 Authentication: Off
** end
xStatus SIP Prole [1..1] Registration [1..n] Status
Shows the status of the registration to the SIP Proxy Server.
Deregister: The system is in the process of de-registering to the SIP Proxy.
Failed: The system failed to register to the SIP Proxy.
Inactive: The system is not registered to any SIP Proxy.
Registered: The system is registered to the SIP Proxy.
Registering: The system is in the process of registering to the SIP Proxy.
Shows the system state, i.e. whether there are any errors or warnings issued.
Initializing: The system is initializing and not yet ready for use.
OK: The system is ready for use.
OKWithWarning: The system can be used for making calls, but there are warnings issued that might
inuence its behavior.
Error: The system is in an erroneous state and cannot be used for making calls.
Value space of the result returned:
<Initializing/OK/OKWithWarning/Error>
Example:
xStatus SystemUnit State Status
*s SystemUnit State Status: Error
** end
xStatus SystemUnit State StatusCode
Shows the type of error or warning that is issued for the system (if any).
OK: The system is ready for use.
EthLinkDown: There is no Ethernet connection, and thus the ISDN Link cannot be used.
BRIWarning: A warning is issud for the BRI interface.
BRIError: There is an error on the BRI interface.
PRIError: There is an error on the PRI inter face.
ExtNetError: There is an error on the external network interface (NET).
Initializing: The system is initializing and not yet ready for use.
Shows the number that can be used to dial in on the ISDN BRI/PRI interface in order to reach this
ISDN Link and subsequently the endpoint associated with the ISDN Link. This requires that numbers
have been assigned to the BRI or PRI interfaces respectively.
Not applicable when using the external network (NET) interface.
Value space of the result returned:
<String>
Example:
xStatus SystemUnit State H320Number
*s SystemUnit State H320Number: "5678"
** end
D14953.01 ISDN Link A PI Reference Guide IL1.0 June 2012.
On our web site you will nd an overview of the worldwide Cisco contacts.
Go to: http://www.cisco.com/web/siteassets/contacts
Corporate Headquar ters
Cisco Systems, Inc.
170 West Tasman Dr.
San Jose, CA 95134 USA
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND
RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE
INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFT WARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-
NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILIT Y, FITNESS FOR A PARTICULAR PURPOSE AND
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR
LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its aliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks.
Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network
topology diagrams, and other gures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and
D14953.01 ISDN Link A PI Reference Guide IL1.0 June 2012.