Virtual Signaling Transfer Point (VSTP) Running V8.4 Uses True Point Code (TPC) Instead Of Secondary Point Code (SPC) On Message Transfer Part Layer 2 (MTP2)-User Peer-to-Peer Adaptation Layer (M2PA) Link
(Doc ID 2771004.1)
Last updated on AUGUST 11, 2022
Applies to:
Oracle Communications Diameter Signaling Router (DSR) - Version DSR 8.4.0 to DSR 8.4.0 [Release DSR 8.0]Information in this document applies to any platform.
Symptoms
vSTP release 8.4 uses TPC instead of SPC.
Changes
- Ingress traffic is sent to the TPC.
- Outgoing Linkset is configured with SPC as the Local Signaling Point (LSP) of the M2PA linksets.
- The Multiple Point code (MPC) feature is already enabled on the release: it allows provisioning and usage of SPCs in vSTP; you are able to set SPC on the Local Signaling Point (SP).
The routing of messages on vSTP supports routing using any of the vSTP Capability Point Code (CPC), TPC or SPC used in DPC of the incoming message.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |