Configuring Diameter Nodes
Configuring and Using SCTP for Diameter Messaging
SCTP is a reliable, message-based transport protocol that is designed for use in telephony
networks. SCTP provides several benefits over TCP:
z SCTP preserves the internal structure of messages when transmitting data to an endpoint,
whereas TCP transmits raw bytes that must be received in order.
z SCTP supports multihoming, where each endpoint may have multiple IP addresses. The
SCTP protocol can transparently failover to another IP address should a connection fail.
z SCTP provides multistreaming capabilities, where multiple streams in a connection
transmit data independently of one another.
WebLogic SIP Server supports SCTP for Diameter network traffic, with several limitations:
z Only 1 stream per connection is currently supported.
z SCTP can be used only for Diameter network traffic; SIP traffic cannot use a configured
SCTP channel.
z TLS is not supported over SCTP.
In addition, WebLogic SIP Server only supports SCTP channels on the following software
platforms:
z Red Hat Enterprise Linux 4.0 AS, ES, WS (Kernel 2.6.9, GCC 3.4 or higher) on 32- or
64-bit hardware
z Sun Solaris 10 on SPARC
SCTP channels can operate on either IPv4 or IPv6 networks. Creating TCP, TLS, and SCTP
Network Channels for the Diameter Protocol describes how to create a new SCTP channel. To
enable multihoming capabilities for an existing SCTP channel, specify the IPv4 address 0.0.0.0
as the listen address for the channel (or use the :: address for IPv6 networks).
Configuring Diameter Nodes
The Diameter node configuration for WebLogic SIP Server engines is stored in the
diameter.xml configuration file ( domain_home/config/custom/diameter.xml ). If you
want to provide diameter services (client, server, or relay functionality) on an engine tier server,
you must create a new node configuration and target the configuration to an existing engine
server instance.
Configuring Network Resources
4-9