Call Routing in Huawei MSOFT
-
Upload
emyl97 -
Category
Technology
-
view
1.246 -
download
31
description
Transcript of Call Routing in Huawei MSOFT
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 RTRSN + RSSN RN
Basic Concept
Trunk Group Table
Trunk Group Table
CALLSRC(RSSN)CALLSRC
(RSSN)
Incoming Call
Own / Other PLMN
LAIGCI TableLAIGCI Table
Call Source, RSSN
Incoming Call (BSC) RSSN = 0
RSSN = 0, 10
Call Source, RSSN
CNACLD(Call prefix-> RSN)
CNACLD(Call prefix-> RSN)
Call Prefix + RSSN
RTANA (RSN)
RTANA (RSN)
Combination of (RSN, RSSN) selects a particular Route (RN)
RSN + RSSN RN
Call to selected Route (RN)
RSSN
+
RSN
RN
Relation of CALLSRC, RSSN, RSN
Basic Concepts
Important Features related to RSN, RSSN
1. Same prefix from different call source (with different RSSN) can be routed to different route.
2. Call block from particular call source.3. 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
Call Source RSSN Call Prefix RSN RN
BSC 0 019000207 BL_ROUTE BL
GPKL01 10 019000207 BL_ROUTE PLMN
Incoming Call
Other PLMNTrunk Group
TableTrunk Group
Table
CALLSRCCALLSRC
Trunk Group Table
Trunk Group Table
CALLSRN = BSC
RSSN = 0
CALLSRN = GPKL01
RSSN = 10
Call Prefix
Combination of (RSN, RSSN) selects a particular Route (RT)
RSN + RSSN RT
CNACLD CNACLD
RTANA (RSN)
RTANA (RSN)
RSSN
+
RSN
RN
Same Call prefix to different Route
Incoming Call
Own PLMN
GGDH01GGDH01
GGDH02GGDH02
RN=PLMN
TGDH01TGDH01
TGDH02TGDH02RN=BL
SRT1
SRT2
SRT1
SRT2
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
CNACLD(Call prefix-> RSN)
CNACLD(Call prefix-> RSN)
Call Prefix + RSSN = 5
RTANA (RSN)
RTANA (RSN)
No Match for RSSN = 5
So, No Route is selected
As no RT is selected,
call is dropped
RSSN
=5
+ R
SN
Trunk Group Table
Trunk Group Table
CALLSRC(RSSN)CALLSRC
(RSSN)
Incoming Call
Other PLMN RSSN = 5
GPDH01: IAM (Call Prefix)
Blocking Transit call
GP is sending 018XXA party=017xxxB party=018xxx
Trunk Group Table
Trunk Group Table
CALLSRCCALLSRC
Trunk Group Table
Trunk Group Table
CALLSRN:MGDH07
RSSN = 0
CALLSRN:GPDH01
RSSN = 10
Call Prefix 018xxxxx
CNACLD CNACLD
RTANA (RSN)
RTANA (RSN)
RSSN
+
RSN
RN
BL VMSC is sending 018XX
AKTELAKTEL RouteRoute No = 201
• 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
If we define RSSN 10 for RSN AKTEL_ROUTE, transit call will pass to AKTEL
Transit call: Call from one PLMN is going to another PLMN using BL network
Lesson: Outgoing Routes to other PLMN should only pass RSSN=0
Call Source RSSN Call Prefix RSN Route
MGDH07 0 018 AKTEL_ROUTE AKTEL
MSRN Routes
If RTANA for RSSC 10 is not defined in MSRN Route, call from Other PLMN to that VMSC fails
GP is sending 019XXA party=017xxxB party=019xxx
BL Subscriber dials 019XX
Call from own PLMN and other PLMN should pass MSRN Routes Two entries are required in RTANA
MGDH07
HLR
MGCT01
SRI
Route: BL
MSRN Routes are used to pass MSRN. 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.
PRN
Call Source RSSN Call Prefix RSN Route
BSC 0 019000207 BL_ROUTE BL
GPKL01 10 019000207 BL_ROUTE BL
IAM
Same MSRN to Different MSC: Example
Call Source RSSN Call Prefix RSN Route Subroute-1 Subroute-2
(BSC) 08801900207 BL_ROUTE
MGCT01 MGCT01 X
(GP) 10 PLMN TGDH01 TGDH01
One BL subscriber from Khulna VMSC calls a BL subscriber of MGCT01. 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
GP subscriber call BLA party=017xxxB party=019xxx
BL Subscriber dials 019XX
MGKL01
HLR
MGCT01
HLR interrogation
RSN = BL_ROUTERoute = MGCT01SRT = MGCT01
GGDH01
GGDH02
RSN = BL_ROUTERoute = PLMNRSN = BL_ROUTERoute = PLMN
SRT=GGDH02
SRT=GGDH01
Analysis Table
Basic Concepts
Thanks