Reference11r1:Concept ICE

From innovaphone wiki
Revision as of 18:26, 25 August 2014 by Msc (talk | contribs) (created)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
There are also other versions of this article available: Reference11r1 (this version) | Reference12r1 | Reference12r2


Applies To

This information applies to

  • all innovaphone devices from V11

Overview

ICE is a protocol for finding and selecting a working network path between two media endpoints.

Configuration

Activation

From v11 ICE is the default call establishment mechanism, so it does not have to be activated. However it can be deactivated using an interop config option, if needed.

 config add H323 /ice-disabled
 config add SIP /ice-disabled
 config add SIPS /ice-disabled
 config add TSIP /ice-disabled
 config add TSIPS /ice-disabled

STUN

The STUN server is used for gathering server reflexive candidates. The server configuration is a string in one of the following formats:

  • a single DNS name and an optional port (e.g. stun.example.com:1234).
  • a comma separated list of one or two IP addresses and optional ports (e.g. 172.16.13.1:1234,172.16.13.2).

The STUN server string can be configured at the following places:

  • For many boxes using the DHCP Server (on page IP4/ETHx/DHCP-Server)
  • For an individual box (on page IP4/General/STUN)
  • For an individual registration (as part of the configuration of the registration)

If it is configured in more than one place, the more specific one is used. For example the configuration at the registration overwrites the DHCP config.

Tracing

Activation

Traces for debugging ICE can be activated at the signalling module. The trace flags are also available on the debug.xml page.

config add H323 /ice-trace on
config add SIP /ice-trace on
config add SIPS /ice-trace on
config add TSIP /ice-trace on
config add TSIPS /ice-trace on

Reading traces