Add_workflow_for_techpubs | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Excerpt | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
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. Refer to IP Trunk Group Authentication for for additional feature functionality.
To View and Edit AuthenticationOn the SBC main screen, go to All > Address Context > Zone > 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. Figure 1: Sip Trunk Group - Signaling - Authentication The following fields are displayed: Table 1: Sip Trunk Group - Signaling - Authentication parameters
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 flagsMake the required changes and click Save at the right hand bottom of the panel to save the changes made. |