Configuring SIP settings

Specifies the level of SIP registration for the MCU.

Can be set to:

• No registration: The MCU will not register with the SIP registrar. This means that a user with a SIP endpoint can only connect to the MCU by dialing its IP address or hostname
• Register MCU only: Enables conference participants to dial in to the auto attendant of the MCU
• Allow conference registration: Enables conference participants to dial directly in to conferences. For this to work, you must configure the SIP registrar with conference IDs

Identifies the network address of the SIP registrar to which MCU registrations should be made.

This can be specified either as a host name or as an IP address. This field will have no effect if SIP registration settings is set to No registration.

Select this option to force the MCU to present its local certificate when registering with the SIP registrar.

Often, the SIP registrar will not require the local certificate from the MCU. Only select this option if your environment dictates that the SIP registrar must receive the local certificate.

The login name for the MCU on the SIP registrar.

You need to configure the SIP registrar with details of the devices that will register with it and create a login for each device.

If you are using Microsoft OCS or LCS, you need to enter the full URI (for example, [email protected]).

Note that this username will be used anywhere where one is required in a SIP call; for example, it will be used where authentication is required with a SIP server where no registrar is used.

The password for the MCU on the SIP registrar.

You need to configure the SIP registrar with details of the devices that will register with it and create a login for each device. The password configured on this page needs to match the password in the SIP registrar. For Microsoft OCS or LCS, do not enter a password.

Note that this username will be used anywhere where one is required in a SIP call; for example, it will be used where authentication is required with a SIP server where no registrar is used.

Identifies the network address of the SIP proxy.

If set, the proxy is used for all SIP calls, whether through a registrar or not.

Select a maximum bit rate to use from Microsoft OCS/LCS clients.

Microsoft OCS/LCS clients will try to use the maximum bit rate that the MCU advertises during the initial call setup. In most scenarios, you will not want OCS/LCS clients to use the Default bandwidth from MCU that is configured on the Settings > Conferences page (Configuring global conference settings). Use this setting to select an appropriate bit rate for Microsoft OCS/LCS clients.

<limit disabled> will cause the MCU to advertise the Default bandwidth from MCU.

Identifies the protocol to be used for call control messages for outgoing call connections.

If your SIP devices use TCP, select TCP as the outgoing transport. If your SIP devices use UDP, select UDP as the outgoing transport. If you want to use encrypted SIP, select TLS. Note that if you want to use TLS, you must have the encryption feature key (or the Secure management feature key) and the TLS service must be enabled on the Network > Services page.

Note that this unit-wide setting can be overriden on a per-configured endpoint basis if you require different settings for individual endpoints. For more information about configuring SIP endpoints, refer to Configuring SIP endpoints

Using TLS for call setup is not sufficient for the call to be considered encrypted such that it can participate in a conference which requires encryption. Where encryption is required in the conference configuration, a SIP call must use SRTP. For more information about SIP encryption, refer to Configuring encryption settings.

The MCU can accept connections on TCP, UDP, and TLS providing those services are enabled on the Network > Services page (Configuring network services).