Conf ig ur in g Di amet er Cli ent Nod es an d Re lay Ag ent s
Table 4-1 describes the server configuration installed with the Diameter domain.
Table 4-1 Key Configuration Elements of the Diameter Domain
Server Name
Network Channel
Configuration
AdminServer n/a
hssclient
diameter (TCP over
port 3868)
Diameter Applications Notes
n/a The Administration Server provides no SIP
or Diameter protocol functionality.
WlssShApplication The hssclient engine functions as a
Diameter Sh client node. The server contains
network channels supporting both SIP and
Diameter traffic. The Diameter node
configuration deploys
WlssShApplication
( com.bea.wcp.diameter.sh.WlssSh
Application ) to provide IMS Sh interface
functionality for deployed SIP Servlets.
RelayApplication The relay engine functions as a Diameter
Sh relay node. The server contains a network
channel to support both Diameter traffic. The
server does not contain a channel to support
SIP traffic, as a relay performs no SIP
message processing.
sip (UDP/TCP over
port 5060)
relay
diameter (TCP over
port 3869)
The Diameter node configuration deploys
RelayApplication
( com.bea.wcp.diameter.relay.Rel
ayApplication ) to provide relay services.
The node configuration also defines a
realm-based route for relaying messages from
the hssclient engine.
hss
4-4
diameter (TCP over
port 3870)
Configuring Network Resources
HssSimulator
The hss engine’s Diameter node
configuration deploys only the
HssSimulator application
( com.bea.wcp.diameter.sh.HssSim
ulator ). The server is configured with a
Diameter network channel.