This command adds/appends
rows with primary and/or secondary IPv4/IPv6 addresses
to a P-CSCF discovery table with precedence for P-CSCF discovery.
Privilege
Security Administrator,
Administrator
Mode
Exec > Global Configuration
> Context Configuration > IMS Authorization Service Configuration
configure > context context_name > ims-auth-service service_name
Entering the above
command sequence results in the following prompt:
[context_name]host_name(config-imsa-service)#
Syntax
In
releases prior to 18:
p-cscf table { 1 | 2 } row-precedence precedence_value { address ipv4_address | ipv6-address ipv6_address } [ secondary { address ipv4_address | ipv6-address ipv6_address } ] [ weight value ]
no p-cscf table { 1 | 2 } row-precedence precedence_value
In
18 and later releases:
p-cscf table { 1 | 2 } row-precedence precedence_value { ipv4-address ipv4_address [ ipv6-address ipv6_address ] | ipv6-address ipv6_address [ ipv4-address ipv4_address ] } [ secondary { ipv4-address ipv4_address [ ipv6-address ipv6_address ] | ipv6-address ipv6_address [ ipv4-address ipv4_address ] } [ weight value ]
no p-cscf table { 1 | 2 } row-precedence precedence_value
no
Removes/deletes
configured row with precedence in specified table for P-CSCF discovery address.
{ 1 | 2 }
Specifies which P-CSCF
table is to be used to add/append the primary and secondary
P-CSCF addresses. Two tables can be configured for P-CSCF discovery
address.
row-precedence precedence_value
This keyword adds/appends
the row with the specified row-precedence to the P-CSCF address
table.
In 8.1 and later releases, precedence_value must
be an integer from 1 through 128, and a maximum of 128 rows can
be added to a table.
In
release 8.0, precedence_value must
be an integer from 1 through 100, and a maximum of 16 rows can be
added to a table.
secondary
Specifies the secondary
IPv4/IPv6 address to be entered in P-CSCF table rows.
address ip_address
Specifies the primary
and/or secondary IPv4 address for P-CSCF discovery table.
This keyword, if used with secondary keyword,
specifies the secondary IPv4 address.
Important
|
This keyword is available only in releases
prior to 18. In 18 and later releases, this keyword is concealed
and is replaced with ipv4-address to
support the PDN type v4v6 request for VoLTE setup.
|
ip_address must
be entered in IPv4 dotted-decimal notation.
ipv4-address ipv4_address
Specifies the primary
and/or secondary IPv4 address for P-CSCF discovery table.
This keyword, if used with secondary keyword,
specifies the secondary IPv4 address.
ipv4_address must
be entered in IPv4 dotted-decimal notation.
Important
|
This keyword is available in 18 and later
releases to support the PDN type v4v6 request for VoLTE setup.
|
In releases prior to
18, the P-CSCF configuration accepts only one primary and one secondary
P-CSCF IP addresses – both IPv4 and IPv6 addresses per
row in the P-CSCF address table. Two IP addresses are not sufficient
enough to address the requirement with PDN type v4v6 request for
VoLTE setup. Hence, in release 18, the P-CSCF configuration has
been enhanced to allow users to configure a maximum of two IPv4
addresses (primary/secondary) and two IPv6 addresses (primary/secondary)
per P-CSCF table row.
ipv6-address ipv6_address
Specifies the primary
and/or secondary IPv6 address for P-CSCF discovery table.
This keyword, if used with secondary keyword,
specifies the secondary IPv6 address.
ipv6_address must
be entered in IPv6 colon-separated-hexadecimal notation.
In releases prior to
18, the P-CSCF configuration accepts only one primary and one secondary
P-CSCF IP addresses – both IPv4 and IPv6 addresses per
row in the P-CSCF address table. Two IP addresses are not sufficient
enough to address the requirement with PDN type v4v6 request for
VoLTE setup. Hence, in release 18, the P-CSCF configuration has
been enhanced to allow users to configure a maximum of two IPv4
addresses (primary/secondary) and two IPv6 addresses (primary/secondary)
per P-CSCF table row.
weight value
This keyword designates
weight to a row-precedence relative to other row-precedences configured
under this table, Default value is 1. value must
be an integer from 1 through 10.
Within the IMS Authorization
configuration, the P-CSCF address is selected based on round robin
fashion. This feature allows the customer to perform P-CSCF selection
based on weight factor.
With this CLI option,
the user can configure and add weight (in the scale of 1 to 10)
to each row, and the rows are selected based on weighted round-robin.
That is, the row with higher weight parameter is selected more number
of times than the row with less number of weights.
Usage Guidelines
Use this command to
add rows with primary and/or secondary IP addresses for
P-CSCF discovery. The row is added with the specified row-precedence.
In releases prior to
17.0, IMSA will select the servers if requested server address type
and selected row server-address type are the same. Otherwise, it
will return NULL. In 17.0 and later releases, P-CSCF server selection
algorithm is modified such that the P-CSCF server selection happens
based on UE-requested server-type.
The operator can add/remove
rows to the table that is not currently selected by the diameter host-select
table command in Policy Control Configuration Mode.
In releases prior to
18, the look-up and forwarding of P-CSCF server information from
P-CSCF table to the session manager were performed by IMS Authorization
(IMSA) server only during the setup. In 18 and later releases, whenever
IMSA receives a Modify Bearer request with P-CSCF Address request
indication, then the list of P-CSCF IP addresses are sent to the session
manager through Modify Bearer Response message.
This look-up and forwarding
functionality works even when the call is with the Local Policy
(LP) engine during the time the Modify Bearer Request is triggered.
Example
The following command adds a row in table 2 with primary IP address 209.165.200.228 , secondary IP address as 209.165.200.232 , and row-precedence value as 20 for P-CSCF discovery.p-cscf table 2 row-precedence 20 address 209.165.200.228 secondary 209.165.200.232
Feedback