Eagle: CONNECT response from EAGLE STP was sent in RN+DN format instead of CC+RN+DN

Asset ID:	1-72-2386599.1
Update Date:	2018-04-16
Keywords:

Solution Type Problem Resolution Sure

Solution 2386599.1 : Eagle: CONNECT response from EAGLE STP was sent in RN+DN format instead of CC+RN+DN

Applies to:

Oracle Communications EAGLE (Software) - Version EAGLE 46.3 and later
Tekelec

Symptoms

Destination Routing Address (DRA) in the CONNECT response message from EAGLE STP was sent in RN+DN format instead of CC+RN+DN

Changes

Cause

The issue is related to INP functionality in Prepaid IDP Query Relay feature.

1) The incoming IDP message is triggering the IDPR service as highlighted in the below SRVSEL table.

> rtrv-srvsel

tekelecstp 18-03-22 10:52:10 IST EAGLE 46.3.0.0.1-68.27.0
rtrv-srvsel
Command entered at terminal #26.
;

Command Accepted - Processing
tekelecstp 18-03-22 10:52:10 IST EAGLE 46.3.0.0.1-68.27.0

GTIN TT NP NAI SSN SNP SNAI SERV GTTRQD
4 0 e164 intl 6 e164 intl gport on
DFLTACT=fallback GTTSELID=none
4 0 e164 intl 12 ---- ----- idpr off
DFLTACT=fallback GTTSELID=none
4 0 e164 intl 146 ---- ----- idpr off
DFLTACT=fallback GTTSELID=none
4 0 e164 intl 241 ---- ----- idpr off
DFLTACT=fallback GTTSELID=none
4 6 e164 intl 6 e164 intl gport on
DFLTACT=fallback GTTSELID=none

SRV SELECTOR table is (5 of 20992) 1 % full
;
Command Executed

2) The CdPA GT in the incoming IDP message is "111111111111" and SK+BCSM is "002222" and the same is configured in CSL table as shown below.

> rtrv-csl

tekelecstp 18-03-22 10:52:17 IST EAGLE 46.3.0.0.1-68.27.0
rtrv-csl
Command entered at terminal #26.
;

Command Accepted - Processing
tekelecstp 18-03-22 10:52:18 IST EAGLE 46.3.0.0.1-68.27.0

Prepaid IDP Query Relay
GT List
DS CDPN BCD
--------------- ----------
111111111111 0

GT List ( 43 of 500) 9%

Prepaid IDP Query Relay
SK+BCSM List
DS PT IDPRCDPN SCPGTA
--------------- ---------- ---------- ---------------------

0000002222 prepaidno idprcdpn2 none

SK+BCSM List ( 10 of 150) 7%

;
Command Executed

3) The CDPN in the INAP layer of incoming IDP message is 2222222222 and nature of address indicator (NAI) of the CDPN is national (significant) number i.e NAI=3. Therefore below highlighted entry in the NPP-SRS table will be triggered.

> rtrv-npp-srs

tekelecstp 18-03-22 10:52:24 IST EAGLE 46.3.0.0.1-68.27.0
rtrv-npp-srs
Command entered at terminal #26.
;

Command Accepted - Processing
tekelecstp 18-03-22 10:52:24 IST EAGLE 46.3.0.0.1-68.27.0
SRVN FPFX FDL FNAI ASN INVKSERV
---------- ---------------- ------- ---- ---------- ----------
idprcdpn2 8 10 natl inp10natl none

NPP-SRS table is (25 of 8192) 1% full.

;

4) Now looking into the NPP-AS table for action set name " ASN=inp10natl ", the service action (SA) is configured as "inprtg" and FARN is configured as "cc,rn,dn"

Where,

FARN = Formatting action list to format digits when RN network entity is associated with the DN in the RTDB.

> rtrv-npp-as:mode=full

tekelecstp 18-03-22 16:39:29 IST EAGLE 46.3.0.0.1-68.27.0
rtrv-npp-as:mode=full
Command entered at terminal #18.
;

Command Accepted - Processing
tekelecstp 18-03-22 16:39:29 IST EAGLE 46.3.0.0.1-68.27.0
ASN CA SA SA DATA FA OFNAI REFS
---------- ---------- ---------- ------------- ---------- ----- ----

inp10natl dn10 inprtg cc intl 4

ccdef rn
grn
dn

FANE : none
FANF : none
FARN : cc, rn, dn
FASP : cc, sp, dn
FASCRCD : none
FASCRCG : none

;

Command Executed

5) RTDB data for DN xx2222222222 is as below. We can see entity type associated with the DN is RN. So the Destination Routing Address (DRA) in the CONNECT response message sent by EAGLE STP is expected to be encoded as "CC+RN+DN" as we have FARN configured as "cc,rn,dn". But we see tekelec STP is sending destination routing address (DRA) in RN+DN format.

> rtrv-data-rtdb:dn=xx2222222222

tekelecstp 18-03-22 19:33:20 IST EAGLE 46.3.0.0.1-68.27.0

rtrv-data-rtdb:dn=xx2222222222

Command entered at terminal #26.

;

Command Accepted - Processing

tekelecstp 18-03-22 19:33:20 IST EAGLE 46.3.0.0.1-68.27.0

Card Loc : 1201 Status:Coherent

BEG DNBLK END DNBLK Portability Type ( 36) Category

xx2200200000 xx2200299999 Not Identified to be ported Public

EntIdx1 EntIdx2

H'0000004d -------

Entity Address Type PC(ANSI ) RI SSN TT NP NAI DA

yyyy RN -------------- GT 000 000 00 000 none

SRFIMSI NSSN CCGT NTT NNP NNAI

no no no no no

ASD Address: ----------

Solution

The Incoming IDP message was coming with CdPA RI as "route on SSN". The SSN in the CdPA is aaa. The SSN aaa was defined in the SS-APPL table for INP feature. So the message was subjected to INP feature instead of INP functionality in Prepaid IDP Query Relay feature.

Attachments

This solution has no attachment