Cisco Cisco Packet Data Interworking Function (PDIF)
Diameter Endpoint Configuration Mode Commands
use-proxy ▀
Command Line Interface Reference, StarOS Release 18 ▄
3573
use-proxy
This command enables/disables Diameter proxy for the Diameter endpoint. By default this command is disabled.
Product
IPCF
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
use-proxy [ server-mode [ demux-mode ] ]
no use-proxy
no
Disables Diameter proxy for the current endpoint.
This command at endpoint level will equip an application to use Diameter proxy to route all its messages to
an external peer.
This command at endpoint level will equip an application to use Diameter proxy to route all its messages to
an external peer.
server-mode
Specifies that the Diameter endpoint to establish the Diameter proxy as the server side endpoint of the
connection.
connection.
demux-mode
Specifies that the Diameter endpoint to establish the Diameter proxy to use the Demux manager to identify
the appropriate session manager. If this keyword is not enabled, the proxy will route the request directly to a
session manager.
IPCF uses BindMux to identify the appropriate session manager.
the appropriate session manager. If this keyword is not enabled, the proxy will route the request directly to a
session manager.
IPCF uses BindMux to identify the appropriate session manager.
Usage
Use this command to establish a Diameter proxy to route all its messages to an external peer. The proxy acts
as an application gateway for Diameter. It gets the configuration information at process startup and decides
which Diameter peer has to be contacted for each application. It establishes the peer connection upon finding
no peer connection already exists.
IPCF uses Bindmux as a Demux manager to help distribute new incoming sessions across available Sessmgrs
on the system.
All the incoming Diameter requests/responses land on Diamproxy. Diamproxy checks if a Sessmgr is already
serving this session based on parameters like session-id and peer-id of the request/response.
If no Sessmgr is allocated to the request and the Demux mode is ON, the DiamProxy forwards the new
request to Demux/Bindmux for sessmgr allocation. Demux/Bindmux has updated information about the load
as an application gateway for Diameter. It gets the configuration information at process startup and decides
which Diameter peer has to be contacted for each application. It establishes the peer connection upon finding
no peer connection already exists.
IPCF uses Bindmux as a Demux manager to help distribute new incoming sessions across available Sessmgrs
on the system.
All the incoming Diameter requests/responses land on Diamproxy. Diamproxy checks if a Sessmgr is already
serving this session based on parameters like session-id and peer-id of the request/response.
If no Sessmgr is allocated to the request and the Demux mode is ON, the DiamProxy forwards the new
request to Demux/Bindmux for sessmgr allocation. Demux/Bindmux has updated information about the load