The SBC can communicate over IPv6 with an external PSX server using a single socket communicating to two different destination ports:

  • Non-call transaction destination port—Configurable on the SBC when the remote policy server is defined (default:3055). This channel is used for the initial registration request and keep-alive indications between the SBC and PSX.
  • Call transaction destination port—The port number for this socket is returned by the PSX in the registration response (this is configurable in the PSX svc.pes.conf file). This channel is used for call processing policy requests and responses using the Diameter+ protocol.

The SBC accommodates up to nine different external PSX servers. If more than one active server is configured, the SBC policy request is load shared between the active servers in a round robin sequence. A combination of both IPv4 and IPv6 policy servers can be configured on the SBC.

The high-level steps required to establish communication are listed below:

  1. Configure the SBC with an IPv6 management address.
  2. Configure a PSX (remote policy server) running release 8.x or higher with an IPv6 address (ensure that SBC is configured as a gateway on the PSX or else SBC registration will fail).
  3. Configure the SBC to use the remote policy server for initial REGISTRATION on port 3055:

    1. Disable the local policy server:

      % set system policyServer localServer PSX_LOCAL_SERVER mode outOfService state disabled

    2. Configure and enable the remote policy server:

      % set system policyServer remoteServer IPV6_PSX ipAddress fc00::3100:0:0:240:106 portNumber 3055 mode active state enabled


      The SBC sends a Registration Request message to the external PSX which replies with the port number to use for call processing communication.

  4. System adds ACL rules dynamically to allow a remote PSX access rights to communicate with the SBC.

    Ports for initial registration – port 3055 (configured default) and the call transaction communication port 3054 (default) – are added once registration is successful.

    DIAMETER AVP structures that incorporate IP addresses allow support of the larger (128 byte) IPv6 address.

 

  • No labels