To configure IP services, go to
.Use this page to control the type of services that may be accessed via Ethernet ports A and B. For example, if one Ethernet port is connected to a network outside your organization's firewall, you can restrict the level of access that external users are entitled to on that port by, for example, enabling HTTPS for IPv4 and IPv6.
To prevent accidental lock-outs, the system does not allow you to disable the service that is currently being used to administer the MCU. For example, if you are configuring the gateway over HTTP and coming in on Port A, then the option to change the HTTP service for Port A will be unavailable in the interface.
Refer to the table below for more details.
In addition to controlling the Ethernet interfaces over which a service operates, this page also allows an administrator to specify the port number on which that service is provided. If the port number for a service is changed, it is necessary to ensure that the new value chosen does not clash with the port number used by any of the other services. However, in most circumstances, the pre-configured default values will suffice.
The settings on this page apply to both IPv4 and IPv6 addressing. The page displays the IPv4 and/or IPv6 values per port, depending on whether IPv4 and/or IPv6 are enabled for the port. When specifying settings use the appropriate column for the required addressing scheme.
Note that by default SNMP Traps are sent to UDP port 162 (on the destination network management station); this is configurable. For more information, refer to Configuring SNMP settings.
To reset all values back to their factory default settings, click
and then click Apply changes.Field | Field description | Usage tips |
---|---|---|
TCP service | ||
HTTP |
Enable/disable HTTP access on the specified interface or change the port that is used for this service. |
HTTP access is required to view and change the MCU web pages and read online help files. If you disable HTTP access on both Ports A and B, you will need to use the serial console interface to re-enable it. If you require advanced security for the MCU, enable HTTPS and disable HTTP access. If a port is disabled, this option will be unavailable. |
HTTPS |
Enable/disable HTTPS access, or change the port number used for HTTPS, on the specified interface. |
This field is only visible if the MCU has the Secure management (HTTPS) feature key or an Encryption feature key installed. For more information about installing feature keys, refer to Upgrading and backing up the MCU. By default, the MCU has its own SSL certificate and private key. However, you can upload a new private key and certificates if required. For more information about SSL certificates, refer to Configuring SSL certificates. If a port is disabled, this option will be unavailable. |
Incoming H.323 |
Enable/disable the ability to receive incoming calls to the MCU using H.323 or change the port that is used for this service. |
Disabling this option will not prevent outgoing calls to H.323 devices being made by the MCU. That is, the MCU will need to dial out to conference participants who are using H.323. If a port is disabled, this option will be unavailable. |
SIP (TCP) |
Allow/reject incoming calls to the MCU using SIP over TCP or change the port that is used for this service. |
Disabling this option will not prevent outgoing calls to SIP devices being made by the MCU. That is, the MCU will need to dial out to conference participants who are using SIP over TCP. Note that if a SIP Outbound connection is negotiated with the registrar, SIP calls incoming via the registrar will still be accepted by the MCU. If a port is disabled, this option will be unavailable. |
Encrypted SIP (TLS) |
Allow/reject incoming encrypted SIP calls to the MCU using SIP over TLS or change the port that is used for this service. |
Disabling this option will not prevent outgoing calls to SIP devices being made by the MCU. That is, the MCU will need to dial out to conference participants who are using SIP over TLS. If a port is disabled, this option will be unavailable. |
UDP service | ||
SNMP |
Enable/disable the receiving of the SNMP protocol on this port or change the port that is used for this service. |
If a port is disabled, this option will be unavailable. If you want to enable the receiving of the SNMP protocol on Port B, ensure that you have the video firewall as an activated feature (refer to Upgrading and backing up the MCU) and you have selected the check box for SNMP on Port B. Note that by default SNMP Traps are sent to port UDP port 162 (on the destination network management station); this is configurable. For more information, refer to Configuring SNMP settings. If you require advanced security for the MCU, disable the SNMP service. |
SIP (UDP) |
Allow/reject incoming and outgoing calls to the MCU using SIP over UDP or change the port that is used for this service. |
Disabling this option will prevent calls using SIP over UDP. If a port is disabled, this option will be unavailable. If you want to allow incoming and outgoing SIP (UDP) calls on Port B, ensure that you have the video firewall as an activated feature (refer to Upgrading and backing up the MCU) and you have selected the check box for SIP (UDP) on Port B. |
(c) Copyright Cisco Systems 2003-2014, License information |