Conf ig ur in g Di amet er Cli ent Nod es an d Re lay Ag ent s
One or more server instances may be also be configured as Diameter relay agents, which route
Diameter messages from the client nodes to a configured Home Subscriber Server (HSS) or other
nodes in the network, but do not modify the messages. BEA recommends configuring one or
more servers to act as relay agents in a domain. The relays simplify the configuration of Diameter
client nodes, and reduce the number of network connections to the HSS. Using at least two relays
ensures that a route can be established to an HSS even if one relay agent fails.
Note: In order to support multiple HSSs, the 3GPP defines the Dh interface to look up the
correct HSS. WebLogic SIP Server 3.1 does not provide a Dh interface application, and
can be configured only with a single HSS.
Note that relay agent servers do not function as either engine or data tier instances—they should
not host applications, store call state data, maintain SIP timers, or even use SIP protocol network
resources (sip or sips network channels).
WebLogic SIP Server also provides simulator applications for the Sh and Ro protocols. You can
use the simulator applications for testing while developing Sh and Ro clients. The simulator
applications are not intended for deployment to a production system.
Steps for Configuring Diameter Client Nodes and Relay
Agents
To configure Diameter support in a WebLogic SIP Server domain, follow these steps:
1. (Optional) Install the WebLogic SIP Server Diameter Domain. Install the Diameter domain,
which contains a sample configuration and template applications configured for different
Diameter node types. You may use the Diameter domain as a template for your own domain,
or to better understand how different Diameter node types are configured.
2. (Optional) Enable the Diameter console extension. If you are working with the sample
Diameter domain, the Diameter console extension is already enabled. If you are starting with
a basic Weblogic SIP Server domain, edit the config.xml file to enable the extension.
3. Create Diameter network channels. Create the network channels necessary to support
Diameter over TCP, TLS, or SCTP transports on engine tier servers and relays.
4. Create and configure the Diameter nodes. Configure the Diameter protocol client applications
on engine tier servers with the host name, peers, and routes to relay agents or other network
elements, such as an HSS. You can also configure Diameter nodes that operate in standalone
mode, without a WebLogic SIP Server instance.
4-2
Configuring Network Resources