logo.gif MCU 4210
host: pont

Configuring SIP settings

To configure SIP settings on the MCU, go to Settings > SIP.

To allow conference participants with SIP endpoints to connect to the MCU by dialing a directory number rather than an IP address, you must configure a SIP registrar. The settings on this page control the MCU's interaction with the SIP registrar and with SIP endpoints. The MCU can register up to 50 URIs with the SIP Registrar; these URIs comprise conferences' Numeric IDs and the MCU itself. If you need to register more than 50 SIP URIs, use prefix based call routing on SIP proxy to route calls to the MCU, rather than registering individual conferences with the Registrar. Strip the prefix and leave only conference IDs in the URI before proxy the call to MCU.

A SIP call will select the audio and video codecs to use from the set of those both allowed on the Settings > Conference page and supported by SIP, unless the call is with an endpoint configured with a Custom codec (refer to Configuring SIP endpoints for more information).

Refer to this table for assistance configuring the SIP settings. After making any configuration changes, click Apply changes .

 

Field Field description Usage tips
SIP registrar usage

Enables the MCU to use a SIP registrar for registrations of numeric identifiers for its conferences and/or auto attendants.

When set to Disabled then no SIP registrar registrations are attempted (and existing registrations are torn down), regardless of other per-conference settings.

When set to Enabled registrations with the registrar are attempted, and calls can be made through the registrar. Note that 'Use SIP registrar' must be Enabled when adding a participant.

SIP registrar domain

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. Note that square brackets are mandatory for IPv6 addresses.

SIP registrar type

Choose between:

  • Standard SIP: for non-Microsoft SIP registrars
  • Microsoft OCS/LCS: for Microsoft SIP registrars

Your choice is dependent on the type of SIP registrar you are using.

This field will have no effect if SIP registration settings is set to No registration.

Username

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, MCU@example.com).

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.

Password

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.

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.

Allow numeric ID registration for conferences

This field controls whether any conferences' configured numeric IDs are allowed to be registered with the registrar.

This setting is the global control that allows or disallows conferences to be registered with the SIP registrar.

Individual conferences will be registered or not depending on the per-conference Numeric ID registration setting which is on the Add conference page for scheduled conferences and for ad hoc conferences it is in the ad hoc conference template.

This would normally be Enabled; by setting it to Disabled, an administrator can prevent users from adding to the set of IDs registered with the configured registrar, even if those users enable the registrar Numeric ID registration setting for conferences they control. This may be desired when working with certain types of SIP registrars whose behavior in some modes is to disconnect active calls when the set of registered IDs changes.

This setting affects both the registration of numeric IDs configured for scheduled conferences and the registration of the numeric IDs of ad hoc conferences.

This field will have no effect if SIP registrar usage is set to Disabled.

SIP call settings

Field Field description Usage tips
SIP proxy address

Identifies the network address of the SIP proxy.

If set, the proxy is used for all SIP calls, whether through a registrar or not. Note that square brackets are mandatory for IPv6 addresses.

Maximum bit rate from Microsoft OCS/LCS clients

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.

Outgoing transport

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/blade-wide setting can be overridden 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).

Use local certificate for outgoing connections and registrations

If this option is selected, the MCU will send its local certificate if requested when registering with the SIP registrar and when making outgoing TLS calls.

Select this option if your environment dictates that the SIP registrar must receive the local certificate. Often, the SIP registrar will not require the local certificate from the MCU, however, for most circumstances we recommend that you select this option.

Related topics