Gx Interface Support
▀ Rel. 8 Gx Interface
▄ Cisco ASR 5x00 Packet Data Network Gateway Administration Guide
316
connection timeout
<timeout_duration>
connection retry-timeout
<timeout_duration>
peer
<primary_peer_name>
[ realm
<primary_realm_name>
] address
<ip_address>
[
port
<port_number>
]
peer
<secondary_peer_name>
[ realm
<secondary_realm_name>
] address
<ip_address>
[ port
<port_number>
]
end
Notes:
<context_name>
must be the name of the context where you want to enable IMSA service.
<imsa_service_name>
must be the name of the IMSA service to be configured for Rel. 8 Gx interface
authentication.
A maximum of 16 authorization services can be configured globally in a system. There is also a system limit for
the maximum number of total configured services.
To enable Rel. 8 Gx interface support, pertinent Diameter dictionary must be configured. For information on the
specific Diameter dictionary to use, contact your Cisco account representative.
The Round Robin algorithm for PCRF selection is effective only over a large number of PCRF selections, and
not at a granular level.
To configure the PCRF host destinations configured in the PCEF, use the diameter host-select CLI commands.
To configure the PCEF to use a pre-defined rule when the Gx fails, set the
failure-handling cc-request-
type
CLI to
continue
. Policies available/in use will continue to be used and there will be no further
interaction with the PCRF.
Verifying the IMSA Service Configuration
To verify the IMSA service configuration:
Change to the context where you enabled IMSA service by entering the following command:
context
<context_name>
Verify the IMSA service’s configuration by entering the following command:
show ims-authorization service name
<imsa_service_name>
Applying IMS Authorization Service to Subscriber Template
After configuring IMSA service at the context-level, within the same context subscriber template must be configured to
use the IMSA service for IMS subscribers.
Use the following example to apply IMSA service functionality to subscriber template within the context previously
configured in the
Configuring IMS Authorization Service at Context Level
section.
configure
context
<context_name>
subscriber default
encrypted password
<encrypted_password>
