You are on page 1of 12

Description of different tables involved

Basic Concepts Call Source


Call source refers to the subscriber or incoming trunk which initiate calls with the same call process attributes
The call source name is obtained by checking the subscriber data table or trunk

group table according to the calling subscriber or the incoming trunk group number.

Route Selection Source Name (RSSN)


It defines the category number of the routing policy for outgoing calls from the call source (local subscribers or incoming trunks). Same number prefix having different RSSN can be treated in different way i.e. can be routed to different routes. Definition: ADD CALLSRC, Use: ADD RTANA

Basic Concepts Route Selection Name (RSN)


It defines a route selection strategy that the MSOFTX3000 uses to handle an outgoing call.
Definition: ADD RTANA, Use: ADD CNACLD

Combination of RSSN and RSN defines one RT

RSN + RSSN RN

RelationConcept of CALLSRC, RSSN, RSN Basic


Incoming Call (BSC) RSSN = 0

LAIGCI Table

Call Source, RSSN

CALLSRC
(RSSN) Call Source, RSSN

Call Prefix + RSSN

CNACLD
(Call prefix-> RSN)

Call to selected Route (RN)

Trunk Group Table


Incoming Call Own / Other PLMN

RSSN + RSN

RN

RSSN = 0, 10

RTANA
(RSN) Combination of (RSN, RSSN) selects a particular Route (RN) RSN + RSSN RN

Basic Concepts

Important Features related to RSN, RSSN


1. 2. 3.

Same prefix from different call source (with different RSSN) can be routed to different route. Call block from particular call source. Blocking Transit calls through BL network.

Basic Concepts

Same Call prefix to different Route


Using different RSSN for different Call source, one particular call prefix from different call source can be routed to different Routes. Use in BL network Switch: MGKL01

Scenario: One BL subscriber under coverage of Khulna MSC calls a BL subscriber at MGCT01. The call goes to TGDH01 and TGDH02 on 50-50 load share basis.
But if a GP subscriber of Khulna calls a BL subscriber at MGCT01, the call is routed 50-50 load share to both Gateways.

Basic Concept
Same Call prefix to different Route
Incoming Call

TGDH01

Own PLMN

CALLSRN = BSC

RN=BL SRT2

TGDH02

Trunk Group Table

RSSN = 0

Call Prefix

CALLSRC
Incoming Call RSSN + RSN Other PLMN

CNACLD
RN=PLMN RN

GGDH01

Trunk Group Table


CALLSRN = GPKL01 RSSN = 10

GGDH02
Combination of (RSN, RSSN) selects a particular Route (RT) RSN + RSSN RT

RTANA
(RSN)

Call Source BSC GPKL01

RSSN 0 10

Call Prefix 019000207 019000207

RSN BL_ROUTE BL_ROUTE

RN BL PLMN

Basic Concepts Call Block from Particular Call Source

Define the call source with a RSSN which is not used normally,

for example, RSSN=5. In Route Analysis table (RTANA), there is no entry for RSSN = 5. So, no Route (RT) is selected and the call is dropped
GPDH01: IAM (Call Prefix) As no RT is selected,

Incoming Call Other PLMN

Trunk Group Table


RSSN = 5

Call Prefix + RSSN = 5

CNACLD
(Call prefix-> RSN)

call is dropped

CALLSRC
(RSSN)

RSSN=5 + RSN

RTANA
(RSN)

No Match for RSSN = 5 So, No Route is selected

Blocking Transit call

Transit call: Call from one PLMN is going to another PLMN using BL network
CALLSRN:MGDH07

Trunk Group Table BL VMSC is sending 018XX

RSSN = 0
Call Prefix 018xxxxx AKTEL Route Route No = 201

AKTEL

CALLSRC

CNACLD
RSSN + RSN RN

Trunk Group Table


GP is sending 018XX A party=017xxx B party=018xxx

CALLSRN:GPDH01

RSSN = 10

RTANA
(RSN) Call Source 115 (VMSC) MGDH07 RSSC RSSN 0 0 Call Prefix Call Prefix 018 018

BL Calls can pass through the RTANA table Call From GP fails to pass RTANA due to different RSSN which is not defined in RTANA
RSC RSN 201 AKTEL_ROUTE Route 201 AKTEL

If we define RSSN 10 for RSN AKTEL_ROUTE, transit call will pass to AKTEL

Lesson: Outgoing Routes to other PLMN should only pass RSSN=0

MSRN Routes are used to pass MSRN. MSRN Routes MSRN Routes should be accessible for own PLMN and other PLMN. For own PLMN RSSN=0, for Other PLMN RSSN=10. Perform RTANA for both RSSN=0 & 10.

BL Subscriber dials 019XX

HLR MGDH07

MGCT01
GP is sending 019XX A party=017xxx B party=019xxx Call from own PLMN and other PLMN should pass MSRN Routes Two entries are required in RTANA
Call Source BSC GPKL01 RSSN 0 10 Call Prefix 019000207 019000207 RSN BL_ROUTE BL_ROUTE Route BL BL

If RTANA for RSSC 10 is not defined in MSRN Route, call from Other PLMN to that VMSC fails

One BL subscriber from Khulna VMSC calls a BL subscriber of Same MSRN to Different Example MGCT01.MSC: The call goes directly via MGCT01 But if a GP subscriber of Khulna calls a BL subscriber of MGCT01, the call is routed 50-50 load share to both Tandem MSC

BL Subscriber dials 019XX

MGKL01
HLR interrogation

RSN = BL_ROUTE Route = MGCT01 SRT = MGCT01 RSN = BL_ROUTE Route = PLMN

MGCT01

GP subscriber call BL A party=017xxx B party=019xxx

SRT=GGDH01 SRT=GGDH02

GGDH01 GGDH02

HLR

Analysis Table
Call Source (BSC) (GP) RSSN 0 10 Call Prefix 8801900207 RSN Route MGCT01 PLMN Subroute-1 MGCT01 TGDH01 Subroute-2 X TGDH01

BL_ROUTE

Basic Concepts
Thanks

You might also like