Technical References

D14 641.11 Codec C90 API Reference Guide TC6.2, JULY 2013. Copyright © 20102013 Cisco Systems, Inc. All rights reserved. 45
Cisco TelePresence System Codec C90 API Reference Guide
xConfiguration H323 Profile [1..1] H323Alias E164
The H.323 Alias E.164 defines the address of the system, according to the numbering plan
implemented in the H.323 Gatekeeper. The E.164 alias is equivalent to a telephone number,
sometimes combined with access codes.
Requires user role: ADMIN
Value space: <S: 0, 30>
Format: Compact string with a maximum of 30 characters. Valid characters are 0-9, * and #.
Example:
xConfiguration H323 Profile 1 H323Alias E164: "90550092"
xConfiguration H323 Profile [1..1] H323Alias ID
Lets you specify the H.323 Alias ID which is used to address the system on a H.323 Gatekeeper and
will be displayed in the call lists. Example: "firstname.lastname@company.com", "My H.323 Alias
ID"
Requires user role: ADMIN
Value space: <S: 0, 49>
Format: String with a maximum of 49 characters.
Example:
xConfiguration H323 Profile 1 H323Alias ID: "firstname.lastname@company.com"
xConfiguration H323 Profile [1..1] PortAllocation
The H.323 Port Allocation setting affects the H.245 port numbers used for H.323 call signalling.
Requires user role: ADMIN
Value space: <Dynamic/Static>
Dynamic: The system will allocate which ports to use when opening a TCP connection. The reason
for doing this is to avoid using the same ports for subsequent calls, as some firewalls consider this
as a sign of attack. When Dynamic is selected, the H.323 ports used are from 11000 to 20999.
Once 20999 is reached they restart again at 11000. For RTP and RTCP media data, the system
is using UDP ports in the range 2326 to 2487. Each media channel is using two adjacent ports,
ie 2330 and 2331 for RTP and RTCP respectively. The ports are automatically selected by the
system within the given range. Firewall administrators should not try to deduce which ports are
used when, as the allocation schema within the mentioned range may change without any further
notice.
Static: When set to Static the ports are given within a static predefined range [5555-6555].
Example:
xConfiguration H323 Profile 1 PortAllocation: Dynamic
Network configuration
xConfiguration Network [1..1] IPStack
Select if the system should use IPv4, IPv6 or Dual on the network interface. Dual means that the
system will be able to operate on both IP versions at the same time. This means that the system can
have both an IPv4 and an IPv6 address at the same time.
NOTE: Restart the system after changing this setting.
Requires user role: ADMIN
Value space: <Dual/IPv4/IPv6>
Dual: When set to Dual, the network interface can operate on both IP versions at the same time,
and can have both an IPv4 and an IPv6 address at the same time.
IPv4: When set to IPv4, the system will use IPv4 on the network interface.
IPv6: When set to IPv6, the system will use IPv6 on the network interface.
Example:
xConfiguration Network 1 IPStack: IPv4
xConfiguration Network [1..1] IPv4 Assignment
Define how the system will obtain its IPv4 address, subnet mask and gateway address. This setting
only applies to systems on IPv4 networks.
Requires user role: ADMIN
Value space: <Static/DHCP>
Static: The addresses must be configured manually using the Network IPv4 Address, Network IPv4
Gateway and Network IPv4 SubnetMask settings (static addresses).
DHCP: The system addresses are automatically assigned by the DHCP server.
Example:
xConfiguration Network 1 IPv4 Assignment: DHCP
xConfiguration Network [1..1] IPv4 Address
Enter the static IPv4 network address for the system. This setting is only applicable when Network
Assignment is set to Static.
Requires user role: ADMIN
Value space: <S: 0, 64>
Format: A valid IPv4 address.
Example:
xConfiguration Network 1 IPv4 Address: "192.0.2.2"
Contents
Introduction
About the API
xConfiguration
Appendices
xCommand
xStatus
xConfiguration