Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c85bb25531015bc4122a4f0003, userName='null'}
JIRAIDAUTHSBX-88484
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ca16038e, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ca16038e, userName='null'}

The

Spacevars
0product
 can

Noprint
Panel
borderColorgreen
bgColortransparent
borderWidth2

Back to Table of Contents

Back to SIP Services

Back to IPv6 Support

The SBC can communicate between two nodes using GW-GW protocol over IPv6 by opening a TCP connection between the communicating nodes over the newly-assigned IPv6 addresses on each GW server. Once the link is established, a keep- alive mechanism over IPv6 link ensures that the gateways remain in communication. Additionally, GW-GW protocol messages are exchanged over the IPv6 link.

The “IP Version Control for Media” configured on the Packet Service Profile and returned by the PSX is encoded and sent to the egress GW.

The SBC does

Spacevars
0product
 does not allow both IPV4 IPv4 and IPV6 IPv6 address types on the same gateway signaling port. Also, SBC does the
Spacevars
0product
 does not currently allow more than one gateway signaling port configuration.

An example of configuring a GW with an IPv6 link on SBC is the

Spacevars
0product
 is shown on theConfiguring Gateways page. Include PageNot_for_SWeNot_for_SWe


Pagebreak