Cisco Cisco Packet Data Interworking Function (PDIF)
Diameter Endpoint Configuration Mode Commands
▀ destination-host-avp
▄ Command Line Interface Reference, StarOS Release 16
3420
destination-host-avp
This command controls encoding of the Destination-Host AVP in initial/retried requests.
Product
All
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration > Context Configuration > Diameter Endpoint Configuration
configure > context context_name > diameter endpoint endpoint_name
Entering the above command sequence results in the following prompt:
[context_name]host_name(config-ctx-diameter)#
Syntax
destination-host-avp { session-binding | always | initial-request | retried-request }
default destination-host-avp
default
Configures this command with the default setting. Default: session-binding
session-binding
Includes the Destination-Host AVP when the Diameter session is bound with a host.
always
Includes the Destination-Host AVP in all types of request messages.
initial-request
Includes the Destination-Host AVP in an initial request but not in a retried request.
retried-request
Includes the Destination-Host AVP in a retried request but not in an initial request.
Usage
Use this command to control encoding of the Destination-Host AVP in initial/retried requests.
This command has been introduced in release 12.0, in earlier releases, the Destination-Host AVP is not sent
in session-setup/initial request (first message sent on that interface for that subscriber. The message will vary
with different interfaces. For example, CCR-Initial for Gy, ACR-start for Rf, and so on). Also, Destination-
Host AVP was not sent in retried requests. For example, CCR-Update failed to be responded by server. The
message was retransmitted to alternate server.
In both these scenarios, it is not known which server will respond to the initial/retried message, so the
Destination-Realm is encoded but not the Destination-Host. Only after a response for this message is received
This command has been introduced in release 12.0, in earlier releases, the Destination-Host AVP is not sent
in session-setup/initial request (first message sent on that interface for that subscriber. The message will vary
with different interfaces. For example, CCR-Initial for Gy, ACR-start for Rf, and so on). Also, Destination-
Host AVP was not sent in retried requests. For example, CCR-Update failed to be responded by server. The
message was retransmitted to alternate server.
In both these scenarios, it is not known which server will respond to the initial/retried message, so the
Destination-Realm is encoded but not the Destination-Host. Only after a response for this message is received