Reference13r2:IP4/RTPTP/Config

An IP4 server or client RTPTP interface can be confured here. The RTPTP interface can receive (server) or make (client) H.323 calls to another RTPTP interface. The calls use TRANSPARENT Data (clearmode) to forward IP packets. The calls can be made as direct IP calls or via a registration at the PBX. ICE for firewall traversal and DTLS for encryption of the data is used.

Remote networks with a fixed address can be connected as clients with a single automatically assigned address.

Calls are established automatically and reestablished if the connection breaks. The connection is constantly tested. If no data is received during a 10s period, the call is reestablished. At least one packet is sent every second. If there is no IP paket to forward, a one byte packet with the value of 0 is sent.

A private facility is used to send network info to a client.

Interface Configuration

Mode

Sets the operation mode of the interface. Can be "Server" for the server side, which receives calls, "Client" for the client, which makes calls and "Off" to turn it off.

Connect To

Peer host name or IP address. If registration is used, this is the PBX. For direct call the host of the other RTPTP interface is configured here.

Call

The H.323 name / SIP URI, which is called by the client

User

Username used to register and as source of the call. If TLS is used for authentication, the device certificate name should be used here.

@

The gatekeeper name used for the registration and the calls. This is needed if the registration or call is to be forwarded thru a reverse proxy

Password

The password used for the registration and to authenticate call control pakets. Not needed if TLS authentication is used.

Address

The local IP address of the RTPTP interface. With this address connections to the device itself can be established. This can be the same as one of the other IP interfaces. So it is not necessary to spend another IP address for this purpose.

Mask