An IP4 server or client RTPTP interface can be configured 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 packet 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.
- 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.
- The H.323 name / SIP URI, which is called by the client.
- 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.
- The password used for the registration and to authenticate call control packets. Not needed if TLS authentication is used.
- 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.
- Together with the address, this definies a local route to the RTPTP interface. On the server side this network is used for dynamic client addresses. On the client it is used to specify the network on the server side for routing.
- Defines the network for a route on the client side. This is sent via a facility to the client so that the client can set the route. It overrides the route defined by Address/Mask on the client.
- DNS server addresses which are sent via facility to the client.
- RDP Port
- Port for RDP protocol for RDP only feature for users
On the server a list of users can be configured, which are allowed to call this interface. If the interface is registered, these users are verified by the PBX. For each user there is some configuration possible:
- The name of the user
- For clients with automatic addresses assigned this should be left empty. It is used for remote static networks, to configured the local route.
- RDP only
- If set only RDP or DNS is forwarded from the client
- Use Proxy-ARP on the server side, if no routes to the device are configured in the network