Reference:Administration/Relay/VOIP/GW

FIXME: does not exist, list of keywords only so far

Basic

Name

Descriptive namne of this gateway interface.

Disable

Disables an interface without deleting the interface configuration.

Protocol

Select the Voice over IP signaling protocol here. You can choose between:

• H.323
• SIP (over UDP)
• TSIP (over TCP)
• SIPS (over TLS)

Mode

Select the interface type here.

• Gateway without Registration

This interface type does not register at any gatekeeper/registrar.

• Register as Endpoint / Register as Gateway

This interface type acts as a registration client and registers itself at the configured gatekeeper/registrar.

• ENUM

Like the 'Gateway without Registration' this type does not register itself. It additionally performs ENUM lookups for the called party number in order to find a appropriate URI (h323 or sip). If no useful URI can be retrieved, the call is re-routed to find another outgoing interface.

• Gatekeeper / Registrar

This interface type acts as a registration server (gatekeeper/registrar). It does not register itself. I receives incoming registrations for the configured aliases (name and/or number).

SIP Interop Tweaks

Accept INVITE's from Anywhere: By default, registered interfaces will reject INVITE's not coming from the SIP server with "305 Use Proxy".

Enforce Sending Complete:

No Inband Information on Error: Regards ISUP-to-SIP signaling. On receipt of DISCONNECT with progress indicator on an early call (not yet connected) a "183 Session Progress" is going to be sent in SIP in order to make the caller hear the inband announcement (tone pattern) provided by the PSTN. The caller will terminate the call then. If this option is enabled, a final error response will be sent to the caller and no inband announcement will be heard at the callers side.

From Header when Sending INVITE:

Identity Header when Sending INVITE:

Notes (SIP specific)

domain/realm

normally, it is sufficiant to specify domain/realm. the DNS is queried then with this name to obtain the DNS SRV entry _sip._tcp or _sip._udp, respectively. this may result in a list of service addresses, ordered by priority and weight.

if no SRV entry is found, then the configured domain is queried as a host name.

if there is a Server Adress configured, then no DNS SRV lookup is done and the address provided is used. The domain/realm is used only for SIP URIs. If there is no domain/realm, the Server Address is used for building SIP URIs.

The two Server Address fields will be DNS-resolved.

[ will be enhanced in V7 ]

Both DNS lookups (HOST and SRV) currently only works for registered GWs (not Gateways without registration).