Configuring SIP settings

This setting affects outgoing SIP calls and registration. The options are:

Use registrar enables SIP registration and routes outbound SIP calls via the registrar.

Use trunk disables SIP registration and tears down existing registrations. Routes outbound calls to the trunk destination, e.g. VCS or CUCM.

Call direct disables SIP registration and tears down existing registrations. Outbound SIP calls go directly (not via registrar or trunk).

Use registrar:

• Enables SIP registrations, on a system-wide basis, with the registrar address you provide.

• Outgoing calls always go via registrar.

• An outbound call will fail if the registrar does not respond.
• Incoming calls should come through the registrar and will fail if the registrar does not respond.

Use trunk:

• Directs outbound SIP calls via the trunk to the SIP server address you provide.
• The SIP server, for example Cisco Video Communication Server (VCS) or Cisco Unified Call Manager (CUCM), is responsible for the onward routing of outbound SIP calls from the MCU.

• If the dialed SIP address does not have a domain then Outbound domain gets appended if present, otherwise Outbound address gets appended.

Call direct:

• The MCU will connect SIP calls directly if possible. It does not use the Outbound address or Outbound domain parameters.
• The MCU does not attempt to use either the registrar or trunk.

The hostname or IP address of the SIP registrar or trunk destination.

The MCU ignores this field if Outbound call configuration is set to Call direct.

The domain of the SIP registrar or trunk destination.

The MCU ignores this field if Outbound call configuration is set to Call direct.

The MCU uses this value in the following ways:

• username@outbounddomain to register a user with a SIP registrar (if SIP registration is enabled)
• numericId@outbounddomain to register a conference's numeric ID with a SIP registrar (if conference has SIP registration enabled)
• Any outbound SIP calls where the supplied address does not contain an @ symbol.

If you do not specify an outbound domain, the MCU uses the outbound address instead.

The MCU uses this name if it registers with a SIP registrar.

The MCU uses this name to authenticate with the SIP device (registrar, trunk destination, or endpoint) if that device requires authentication.

The MCU will use this name to register itself with the SIP registrar if you have enabled SIP registration. It will not register itself if you do not provide this, but it will still be able to register individual conferences (assuming they are enabled to register and have numeric IDs).

If a conference does not have a numeric ID, then it cannot register. Calls out from such a conference will appear to come from the MCU's own SIP registration (this_username@outbounddomain). It is impossible for a participant to call into such a conference because it does not have a numeric ID.

If you enter a full URI here (e.g. host@domain), then the MCU will ignore the Outbound domain setting.

The SIP destination may not require authentication; if it does, you need to configure it to accept a log in from this username and password combination.

Select the protocol that the MCU will use for outbound calls (and registrations, if enabled).

One of TCP, UDP, or TLS.

The MCU uses this protocol for communicating with the SIP registrar or trunk destination.

If you have the encryption feature key installed and want to encrypt signaling, select TLS.

The MCU accepts incoming connections on whichever protocol the connection uses (TCP, UDP or TLS), and will respond using the same protocol, irrespective of this Outbound transport setting. Make sure that you enable those services on the Network > Services page.

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.