Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Use this object to support local authentication autonomously on a per-IP trunk group basis in situations where an IP-PBX does not perform a registration and the service provider does not require/want registrations. This section describes the NASS-IMS-Bundled-Authentication (NBA) configuration for providing access to the IMS (IP Multimedia Subsystem) network for legacy equipment that cannot support IMS access security (IMS AKA).

To View and Edit

...

Nass Ims Auth Configuration

On the SBC main screen, go navigate to All > Address Context > Zone > Sip SIP Trunk Group > Signaling > Authentication. The Authentication window is displayed.

The Authentication can be checked for each Address Context, for each Zone, for each Sip Trunk Group created or for all the Address Contexts, Zones and Sip Trunk Groups created. Use the drop-down box to select the desired Address Context, Zone and Sip Trunk Group.

The Edit Authentication window is displayed.

Caption
0Figure
1Sip Trunk Group - Signaling - Authentication
 

Image Removed

The following fields are displayed:

Caption
0Table
1Sip Trunk Group - Signaling - Authentication parameters
 

...

Enable this flag on the ingress IP Trunk Group (IPTG), respective to the request, to allow the SBC to reply locally to egress IPTG authentication challenges. If this flag is disabled, the SBC will not reply to authentication challenges locally even if credentials are configured on the egress IPTG. The options are:

  • disabled (default) – If this flag is disabled, Inc Internal Credentials is not used.
  • enabled

...

 Nass Ims Auth.

Excerpt Include
Signaling - Nass Ims Auth
Signaling - Nass Ims Auth
nopaneltrue

Pagebreak

Enable this flag on the ingress IP Trunk Group, respective to the request, to allow egress IPTG authentication to be internally created using the authorization information in mid-dialogue without being challenged. The options are:

  • disabled (default)
  • enabled 

 

Note

The SBC will not use IPTG credentials if a call originates from a surrogate originated peer even if Int Challenge Response is enabled on the ingress leg.

Note

If IPTG authentication is configured for both ingress IPTG and IP Peer, the IP Peer configuration takes precedence. If you wish to use the flags configured on IPTG, the IP Peer must not be present in the configurations. Otherwise, the IP Peer flags default to 'disabled' state and take precedence over IPTG flags.

Make the required changes and click Save at the right hand bottom of the panel to save the changes made.