Cisco BTS 10200 Softswitch Manual page 135

Chapter 2 Routing
Donor Switch
•
•
•
Intermediate or Transit Switch
•
•
Originating Switch
•
•
•
•
OL-8001-10
Normal case—When the BTS receives a call to a DN with a DN2subscriber record, if the STATUS
has a value of PORTED-OUT, and if the LNP Profile table indicates QUERY-ON-RELEASE=Y,
then a backward release (REL) is sent with the QOR ported number release cause defined in the LNP
Profile table (defaults to cause value QOR: Ported Number (14)).
QOR not supported by backward switch—For a trunk originated call to a ported-out subscriber, the
incoming trunk group may indicate that QOR is not supported by the previous switch or network
and that the BTS is expected to perform the QOR query (LNP Profile table
QUERY-ON-RELEASE=Y and Trunk Group table PERFORM-LNP-QUERY =Y). In this case, a
QOR query is performed by the BTS and the call is re-routed onward to the recipient switch.
Misrouted call or configuration error—If the dn2subscriber record STATUS has a value of
PORTED-OUT, but the LNP Profile table QUERY-ON-RELEASE=N and
ONWARD-CALL-ROUTING=N, a network routing error has occurred (for example, the CRD LNP
database is incorrect, the originating switch performing ACQ misrouted the call, or the BTS
DN2subscriber or LNP Profile flags are incorrect). For a misrouted call where the CdPN contained
a regular non-ported DN, the BTS will clear the call with a non-LNP release cause indicating an
unallocated number ; otherwise, if the CdPN contained the ported NOA as a result of the incoming
trunk call or subscriber origination on this switch, then the cause misrouted ported number is used.
Normal case—When the BTS receives a backward REL with the QOR ported number release cause,
the BTS clears the call and sends a backward REL with the same release cause.
QOR not supported by backward switch—If the incoming trunk group indicates that QOR is not
supported by the previous switch or network and that the BTS is expected to perform the QOR query
(LNP Profile table QUERY-ON-RELEASE =Y and Trunk Group table
PERFORM-LNP-QUERY=Y) , a QOR query is performed by the BTS and the call is re-routed
onward to the recipient switch.
Normal case—When the BTS receives a backward REL with the QOR ported number release cause,
if the LNP Profile table QUERY-ON-RELEASE=Y, a query is preformed. The call is then re-routed
onward to the recipient switch.
When the BTS receives a backward REL with cause QOR: Ported Number (14), if the LNP Profile
table QUERY-ON-RELEASE=N, this cause value is not defined as a QOR ported number cause
value. If the operator desires explicit cause mapping for this cause, cause-code mapping should be
provisioned.
When the BTS receives a backward REL with the QoR ported number release cause, and the LNP
Profile table QUERY-ON-RELEASE=Y, if the BTS determines that a query was done previously
(ACQ) which did not find an RN and the call was routed with the DN, the call is cleared with a cause
unallocated number.
When the BTS receives a backward REL with the QOR Ported Number release cause, if the BTS
determines that a query was done previously (ACQ) that returned an RN, and the call was routed
using the RN and NOA for ported number, then the call is cleared with a cause 31 unspecified This
case is normally not expected to occur. If the BTS is the donor switch in this case and receives a
called party number with ported NOA, then REL with cause unallocated number is sent back to the
originating switch. Cause QoR: Ported Number (14) is not used for an incoming call containing a
ported number NOA.
Cisco BTS 10200 Softswitch Dial Plan Guide, Release 4.5.x
Routing Types
2-19