Setup Wizard: VoIP

Last Updated : Jun 28, 2022 |

You can use this panel to configure the H323 Gatekeeper and SIP Registrar support provided on each of the system's LAN interfaces.

LANS

Field

Description

Select LAN

Use this control to switch between configuring LAN1 or LAN2.

H.323 Gatekeeper

These settings relate to the H.323 extension support provided by the system on the currently selected LAN.

Field

Description

H.323 Gatekeeper Enable

Default = Off

If enabled, the system will support H.323 trunk and extension connections on the LAN.

H.323 Signaling over TLS

Default = Disabled. For hosted deployments, default = Preferred.

When enabled, TLS is used to secure the registration and call signaling communication between IP Office and endpoints that support TLS. The H.323 phones that support TLS are 9608, 9611, 9621, and 9641 running firmware version 6.6 or higher.

When enabled, certificate information is configured in the 46xxSettings.txt file on IP Office and automatically downloaded to the phone. When IP Office receives a request from the phone for an identity certificate, IP Office searches its trusted certificate store and finds the root CA that issued its identity certificate. IP Office then provides the root CA as an auto-generated certificate file named Root-CA-xxxxxxxx.pem.

For information on IP Office certificates, see Security > Certificates.

The options are:

  • Disabled: TLS is not used.

  • Preferred: Use TLS when connecting to a phone that supports TLS.

  • Enforced: TLS must be used. If the phone does not support TLS, the connection is rejected.

    When set to Enforced, the Remote Call Signaling Port setting is disabled.

If TLS security is enabled (Enforced or Preferred), it is recommended that you enable a matching level of media security on System Settings > System > VoIP Security.

H.323 Remote Extn Enable

Default = Off

The system can be configured to support remote H.323 extensions in the case where NAT is used in the connection path. This could be the case where the IP Office is located behind a corporate NAT/Firewall router and/or the  H.323 phone is located behind residential NAT enable router.

Currently, only 9600 Series phones are supported as H.323 remote extensions.

Remote Call Signaling Port

Default = 1720

The call signaling port used for remote H.323 extensions.

Auto-create Extension

Default = Off

If enabled, the system will automatically create a extension entry in its configuration in respond to successful registration by an H.323 IP phone.

  • This setting is automatically disabled 24-hours after being enabled.

Password

Default = Blank

If set, sets the password for extension registration using auto-creation. If left blank, the system Default Extension Password setting is used.

Auto-create User

Default = Off

If enabled, the automatic creation of an H.323 extension entry in the system configuration also causes the automatic creation of a matching user entry for the extension.

SIP Trunks

Field

Description

SIP Trunks Enable

Default = On.

This settings enables support of SIP trunks. It also requires entry of SIP Trunk Channels licenses.

Enabling SIP Trunks Enable allows configuration of the RTP Port number Range (NAT) settings.

SIP Registrar

These setting relate to the support of SIP extensions on the selected LAN.

Field

Description

SIP Registrar Enable

Default = Off

Used to set the system parameters for the system acting as a SIP Registrar to which SIP endpoint devices can register. Separate SIP registrars can be configured on LAN1 and LAN2. Registration of a SIP endpoint requires an available IP Endpoints license. SIP endpoints are also still subject to the extension capacity limits of the system.

Auto-create Extn/User

Default = Off.

The field to set up auto creation of extensions for SIP phones registering themselves with the SIP registrar. If selected, the system prompts you to enter and confirm the password is used for subsequent auto creation of extensions.

  • This setting is not supported on systems configured to use WebLM server licensing.

  • For security, any auto-create settings set to On are automatically set to Off after 24 hours.

SIP Remote Extn Enable

Default = Off.

The system can be configured to support remote SIP extensions in the case where NAT is used in the connection path. This could be the case where the IP Office is located behind a corporate NAT/Firewall router and/or the SIP phone is located behind residential NAT enable router.

  • This option cannot be enabled on both LAN1 and LAN2.

  • The use of this option and the interaction and configuration of external third party elements is beyond the scope this help file.

In the case where the public IP address of the corporate router is unknown, the LAN's Network Topology settings should be used to configure a STUN Server. Enabling SIP Remote Extn Enable allows configuration of:

  • the Remote UDP Port, Remote TCP Port, Remote TLS Port settings

  • the Port Number Range (NAT) settings

SIP Domain Name

Default = Blank

This value is used by SIP endpoints for registration with the IP Office system. SIP endpoints register with IP Office using their SIP address that consists of their phone number and IP Office SIP domain. Since IP Office does not allow calls from unauthorized entities, the SIP domain does not need to be resolvable. However, the SIP domain should be associated with FQDN (Fully Qualified Domain Name) for security purposes. The entry should match the domain suffix part of the SIP Registrar FQDN below, for example, example.com. If the field is left blank, registration uses the LAN 1, LAN2, or public IP address.

Note:

For Avaya SIP telephones supported for resilience, the SIP Domain Name must be common to all systems providing resilience.

SIP Registrar FQDN

Default = Blank

The fully-qualified domain name to which the SIP endpoint send their registration requests. For example, sbc.example.com.

  • This FQDN is also used for Avaya Cloud Services and Avaya Push Notification Services

The customer DNS must resolve this FQDN to an IP address that routes to the IP Office. That is:

  • For local extensions, the IP address of the IP Office LAN.

  • For remote extensions, the external IPv4 address of the Avaya SBC or customer firewall that routes to the IP Office.