MSM7xx Controllers Configuration Guide v6.4.0

MIME type
Specify the content-type string that identifies this MIME-type. This is the value that must appear
in an HTTP Content-type header for the controller to recognize this MIME type.
Types should be specified in the following format: type/subtype
For example: text/xml
MIME type is text-based
Enable this option if the MIME type identifies files that are text-based.
Security
Use this option to control access to the Web server.
Allowed addresses
The Web server will only accept connections from devices whose IP addresses appear in this
list.
When the list is empty, authentication requests are accepted from any address.
Active interfaces
Select the interface(s) on which the controller will accept connections.
When NOC authentication is active, this is the interface on which the remote login Web server
application can be reached. For more information on NOC authentication, see “NOC
authentication” (page 480) and “NOC authentication” (page 549).
NOTE: Ingress interfaces configured inside VSCs (including the LAN port) always have access
to the Web server when NOC-based authentication is disabled.
Managing payment services
The controller can directly interact with payment processing services service such as Authorize.NET
and WorldPay, so that users can pay for network access from within their Web browser.
Payment services configuration
To configure payment services, follow this procedure:
1. Select Controller >> Public access > Payment services.
Use this page to define the type of payment options that the public access interface will support.
2. Enable Credit card. Specify the three-letter Currency code (see online help for list of codes)
and Tax rate.
3. For Credit card payment authorization, select either Authorize.NET or WorldPay, and
specify the appropriate information. Merchant accounts must be set up to use these services
(www.authorize.net or www.worldpay.com).
Managing payment services 421