Steel-Belted Radius Carrier 7.2.x Administration and Configuration Guide > Technical Bulletins > Uniport Plug-In

Uniport Plug-In

The 3Com Corporation Uniport project can operate with Steel-Belted Radius Carrier via a plug-in.

Operation

Uniport requires RADIUS call-type determination as a back-up for SIP call-type determination. To determine call-type, the HiPerARC system sends Steel-Belted Radius Carrier a request containing a Service-Type attribute of Call-Check (10) and a User-Name attribute in which the value is the same as the Called-Station-Id (DNIS) attribute. The type of call is then determined based on the User-Name (DNIS), and the appropriate Service-Type attribute returned in the Access-Accept packet.

A Uniport plug-in method is instantiated for each value of the Service-Type attribute which can be returned in the Access-Accept. The proper method is utilized using proxy mapping to a directed realm which specifies the method instance. The method then sets the configured profile in the response and indicates it was successful.

The Uniport methods return a Reject if a Service-Type attribute with a Call-Check value is not present in the request, if User-Name or Called-Station-Id attributes are not present, or if their values are not identical.

Configuration

The attributes to be returned in the Access-Accept to identify the call-type are defined as Steel-Belted Radius Carrier profiles. For example, a fax profile may be created which would return a value of 96 in a Service-Type attribute.

The Uniport methods are configured with *.aut files which specify the profile to return. The method is identified and associated with a directed realm by the initialization string.

For example, a method to return the FAX profile may use a configuration file such as fax.aut, with these settings:

[Bootstrap]

Enable = 1

InitializationString = UNIPORT FAX

Profile = FAX

LibraryName = Uniport.so

The corresponding directed realm identifies the method in its *.dir file. For example, in the fax.dir file the settings might be:

[Auth]

Enable = 1

[AuthMethods]

Uniport fax

The directed realms that refer to the Uniport methods are mapped in the [AuthAttributeMap] of proxy.ini. A sample map might appear as:

[AuthAttributeMap]

Fax

    Service-Type = 10

    Called-Station-Id = 6175471047

FoIP

    Service-Type = 10

    Called-Station-Id = 617*

VoIP

    Service-Type = 10

In this example, the number 6175471047 is directed to the Fax realm, which in turn uses the Uniport method to return the fax profile.

NOTE: Wild cards must be listed after any numbers that they might contain. In the preceding example, the 617* wildcard must appear after the number 6175471047, because this last number is contained within the range of numbers described by the wildcard.

If you want a default profile, the map may be configured to direct the request to a Uniport method by default. The same result may be obtained by omitting the default from the map and setting the first method in the authentication method chain to the desired default.

If you do not want a default profile, configure the map to direct requests by default to a method which has no profile set; the method returns with a value to indicate a failure to authenticate.