The following table lists the release link Trunking sub-fields:

Table 1: Release Link Trunking Sub-Fields

Sub-
Field

Name

Max
Length

Type

Redirect

Bridging

Description

1

Feature Identifier

3

Characters

M

M

Always "RLT"

2

Number of Sub-Fields to Follow

2

Decimal

M

M

Always "30"

3

IAM Generic Digit Billing Number

24

Encoding:Data

O

O


4

IAM Generic Digit Universal Access Number

24

Encoding:Data

O

O


5

IAM Generic Digit Originating Switch ID

24

Encoding:Data

O

O


6

IAM Generic Digit Originating Trunk ID

24

Encoding:Data

O

O


7

Billing FAR Generic Digit Billing Number

24

Encoding:Data

O

O


8

Billing FAR Generic Digit Universal Access Number

24

Encoding:Data

O

O


9

Billing FAR Generic Digit Originating Switch ID

24

Encoding:Data

O

O


10

Billing FAR Generic Digit Originating Trunk ID

24

Encoding:Data

O

O


11

Time Elapsed from Receipt of AR Setup Message to Billing FAR Received

10

Decimal

M

M

Time in 10 ms ticks

12

Redirecting FAR Generic Digit Billing Number

24

Encoding:Data

O



13

Redirecting FAR Generic Digit Universal Access Number

24

Encoding:Data

O



14

Redirecting FAR Generic Digit Originating Switch ID

24

Encoding:Data

O



15

Redirecting FAR Generic Digit Originating Trunk ID

24

Encoding:Data

O



16

Redirecting FAR Called Party Number

30

Digits

O



17

Redirecting FAR Calling Party Number

30

Digits

O


Value from AR record is populated if CPN is not in FAR

18

Redirecting FAR Charge Number

30

Digits

O


Value from AR record is populated if CN is not in FAR

19

Redirecting FAR Originating Line Information

3

Decimal

O


Value from AR record is populated if OLIP is not in FAR

20

Redirecting FAR Attempt Failed Counter

3

Decimal

M



21

Time Elapsed from Receipt of AR Setup Message to Redirect FAR Received

10

Decimal

M


Time in 10 ms ticks

22

Time Elapsed from Receipt of AR Setup Message to AB Setup Message

10

Decimal

M

M

Time in 10 ms ticks

23

Bridging FAR Generic Digit Billing Number

24

Encoding:Data


O


24

Bridging FAR Generic Digit Universal Access Number

24

Encoding:Data


O


25

Bridging FAR Generic Digit Originating Switch ID

24

Encoding:Data


O


26

Bridging FAR Generic Digit Originating Trunk ID

24

Encoding:Data


O


27

Bridging FAR Called Party Number

30

Digits


O


28

Bridging FAR Calling Party Number

30

Digits


O


29

Bridging FAR Call Reference

12

6 Octets


M

Call ID:Point Code

30

Bridging FAR Attempt Failed Counter

3

Decimal


M


31

Time Elapsed from Receipt of AR Setup Message to Bridging FAR Received

10

Decimal


M

Time in 10 ms ticks

32

Time Elapsed from Receipt of AR Setup Message to Receipt of BR Setup Message

10

Decimal


M

Time in 10 ms ticks
Populated in BR record but not in AR record

M = Mandatory Parameter, O = Optional Parameter

Table 2: Encoding Data Detail

CDR
Value

Encoding

DATA Notes

(Example) CDR Value for 5
Raw Data bytes - 0x48656C6C6F

0

CPC_GEN_DIGITS_ENCODING_BCD_EVEN

All data is in hexadecimal format, but without "0x" prefix.
These nibbles are swapped so that the number is displayed in its "natural" format.

0:8456C6C6F6

1

CPC_GEN_DIGITS_ENCODING_BCD_ODD

All data is in hexadecimal format, but without the "0x" prefix.
These nibbles are swapped as above. Because the length is odd, the last nibble, although present, is meaningless.

1:8456C6C6F6
(ignore "F")

2

CPC_GEN_DIGITS_ENCODING_IA5

All data is in hexadecimal format, but without the "0x" prefix.

2:48656C6C6F

3

CPC_GEN_DIGITS_ENCODING_BINARY

All data is in hexadecimal format, but without the "0x" prefix.

3:48656C6C6F

4

CPC_GEN_DIGITS_ENCODING_SPARE04

All data is in hexadecimal format, but without the "0x" prefix.

4:48656C6C6F

5

CPC_GEN_DIGITS_ENCODING_SPARE05

All data is in hexadecimal format, but without the "0x" prefix.

5:48656C6C6F

6

CPC_GEN_DIGITS_ENCODING_SPARE06

All data is in hexadecimal format, but without the "0x" prefix.

6:48656C6C6F

7

CPC_GEN_DIGITS_ENCODING_SPARE07

All data is in hexadecimal format, but without the "0x" prefix.

7:48656C6C6F

Raw data shown in the Example column above represents bytes contained in incoming signaling message, such as a Bridging FAR signaling message.

Table 3: Logging RLT Feature Specific Data

RLT Type

Call 1

Call 2

Success?

Where Logged

RLT Type

Call 1

Call 2

Success?

Where Logged

Bridge

A calls R (AR)

R calls B (BR)

Yes

Redirecting GSX/SBC in BR record

Bridge

A calls R (AR)

R calls B (BR)

No

Redirecting GSX/SBC in BR record. If the BR call does not exist, then logged by the originating GSX/SBC in AR record.

Redirect

A calls R (AR)

R redirects to B (AB)

Yes

Redirecting GSX/SBC in AB record.

Redirect

A calls R (AR)

R redirects to B (BR)

No

Redirecting GSX/SBC in BR (ATTEMPT) record


  • No labels