Feature 681: Support of

Optimal Routing (SOR) for Late

CF

DN99621306

Issue 15-0-0
 Feature 681: Support of Optimal Routing (SOR) for
Late CF

The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under which
the document is submitted, and no part of it may be used, reproduced, modified or transmitted
in any form or means without the prior written permission of Nokia Siemens Networks. The
documentation has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes
customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability, capacity,
or performance of the mentioned hardware or software products are given "as is" and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Nokia Siemens Networks and the customer. However,
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which
may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-
TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-
RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED
TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY
OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION
IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark
of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective
owners, and they are mentioned for identification purposes only.
Copyright © Nokia Siemens Networks 2010/5/27. All rights reserved

f Important Notice on Product Safety

Elevated voltages are inevitably present at specific points in this electrical equipment.
Some of the parts may also have elevated operating temperatures.
Non-observance of these conditions and the safety instructions can result in personal
injury or in property damage.
Therefore, only trained and qualified personnel may install and maintain the system.
The system complies with the standard EN 60950 / IEC 60950. All equipment connected
has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit
In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Span-
nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.
Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-
zungen und Sachschäden führen.
Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die
Anlagen installiert und wartet.
Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene
Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.

2
Feature 681: Support of Optimal Routing (SOR) for
Late CF

Table of Contents
This document has 11 pages.

1 Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 Installation and testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.1 Configuration requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1.1 Network elements involved . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1.2 Hardware effects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1.3 Firmware effects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2 Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.3 Installation and activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.4 Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.4.1 Test environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.4.2 Prerequisites for testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.4.3 Test execution and expected results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.5 Deactivation of feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.6 Deactivation testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Id:0900d805806b627c 3
 Feature 681: Support of Optimal Routing (SOR) for
Late CF

4 Id:0900d805806b627c
Feature 681: Support of Optimal Routing (SOR) for Summary of changes
Late CF

1 Summary of changes
Changes made between issues 15–0-0 and 14-1
Sections referring to the interworking of the feature with CAMEL Phase 2, 3 and 4 have
been added.

Changes made between issues 14–1 and 14-0

The title of the document has been corrected according to the approved feature name.

Changes made between issues 14–0 and 13-0

The company and product names have been changed according to the official Nokia
Siemens Networks portfolio naming.

Changes made between issues 13–0 and 12–1

Two new parameters have been added to step three in Chapter Installation and activa-
tion, Section Using End of Selection (EOS) cause codes.
For more information on the feature refer to the corresponding feature description.

Changes made between issues 12–1 and 12–0

The syntax of the RXI, RXC, and RXM commands have been modified.

Changes made between issues 12–0 and 11–0

Standalone and Integrated MSS added to Section Network elements involved.
For more information on the feature refer to the corresponding feature description.

Id:0900d805806b6276 5
Installation and testing Feature 681: Support of Optimal Routing (SOR) for
Late CF

2 Installation and testing

2.1 Configuration requirements

2.1.1 Network elements involved

The following network elements are needed:
• DX MSC/VLR
• DX HLR
• BC
• IN/SCP
• Standalone MSS
• Integrated MSS

2.1.2 Hardware effects

If the Gateway MSS (GMSS) is used as a Call Mediation Node (CMN), the functionality
of the feature does not work. If the GMSC controls an MGW, the functionality works
properly.

2.1.3 Firmware effects

None.

2.2 Remarks
The country codes in North America are the same (1). It is possible to set the charging
check off with the Parameter Handling MML and to avoid the comparison of the country
codes. It is recommended to have the charging check set off in North America MSCs.
If the operator has CAMEL feature (at least Phase 2) installed, interworking between
RCH and SRI-Ack operations on O-CSI level happens in the following way.
If both the HLR-inquiry answer (SRI-Ack) and the RCH message contained an O-CSI,
then the one in the SRI-Ack has priority. The one from RCH is not taken into account. If
only one of the above mentioned two operations contained O-CSI, then this interworking
restriction does not apply.

2.3 Installation and activation

Installing the software
The feature is available after that:
• a specific software has been installed
• the correct CDR format has been installed
• the generation of the FORW CDR has been activated with the GTM command
After the software installation, the status is inactive by default. If the GMSC differs from
the VMSC, the feature must be installed and activated in both MSCs.
The feature also has to be activated in the HLR.

6 Id:0900d805806b6278
Feature 681: Support of Optimal Routing (SOR) for Installation and testing
Late CF

Outputting and updating the activation status of the feature

1 Check whether the feature has been activated with the following MML command:
ZWOS:2,560;
The value of the SOR_LCF_SUPPORTED parameter (Identifier 00560) has to be
'activated'.
2 Activate the feature, if it has not been activated yet, with the following command:
ZWOA:2,560,A;

Interrogating and changing the activation status of the charging check

This feature makes the charging check in optimisation cases. You can make optimal
routing in all Late Call Forwarding (LCF) cases by deactivating the charging check.
1 Check whether the charging check has been activated with the following command:
ZWOI:2,575;
The value of the LCF_CHA_CHECK parameter (Identifier 00575) has to be '00FF'
(default value).
2 Deactivate the charging check with the following command:
ZWOC:2,575,0000;
3 Activate the charging check with the following command:
ZWOC:2,575,00FF;

Using End of Selection (EOS) cause codes

The Support of Optimal Routing (SOR) uses the following cause codes for LCF:
• lcf_busy_notif_to_a = 1035
LCF (OR) when the Mobile Station (MS) is busy, notification to subscriber A.
• lcf_busy_no_notif_to_a = 1036
LCF (OR) when the MS is busy, no notification to subscriber A.
• lcf_no_answ_notif_to_a = 1037
LCF (OR) when the MS does not answer, notification to subscriber A.
• lcf_no_answ_no_notif_to_a = 1038
LCF (OR) when the MS does not answer, no notification to subscriber A.
• lcf_no_reach_notif_to_a = 1039
LCF (OR) when the MS is not reachable, notification to subscriber A.
• lcf_no_reach_no_notif_to_a = 103A
LCF (OR) when the MS is not reachable, no notification to subscriber A.
These event codes are analysed in the EOS analysis. As a result, it returns the analysis
tree in which the C-number must be analysed (the charging origin that is to be used for
the call forwarding), and the announcements and notifications for the calling party has
to be given. You have to create these codes.
1 Check with the following MML command whether the cause code exists:
ZRXI:RESGR=<analysis result group>,CAUSE=<cause code>;
2 Create the cause code with the following MML command:
ZRXC:<cause code>:<analysis result group>,<analysis result
identifier>;
where:

Id:0900d805806b6278 7
Installation and testing Feature 681: Support of Optimal Routing (SOR) for
Late CF

<analysis result group> The value of the parameter is 'ALL'.

<analysis result identifier> The value of the parameter is 'CONT'.
3 Modify the analysis with the following MML command: ZRXM:<analysis
result group>:<cause code>:<analysis result identifier>,<num-
ber of reattempts>,<action after reattempts>,<cm analysis
tree>,<charging origin>,<notification info>,<tsl of the signal
tone>,<announcement number>:;
where:
<analysis result group> The value of the parameter is '2'.
<analysis result identifier> The value of the parameter is 'CMANAL'.
<cm analysis tree> The value of the parameter is '20'.
<notification info> The value of the parameter is '#' or 'NOTIF' according to the cause
code functionality.

Interworking with CAMEL Phase 2, 3 and 4 configuration

The interworking issue referred to in section, Remarks can be configured with the
Parameter Handling, WO MML command group. If the operator wants to use O-CSI
received from RCH operation over the O-CSI received in SRI-Ack, then the following
command has to be issued:
ZWOC:41,69,00FF;

2.4 Testing

2.4.1 Test environment

A mobile station (MS_B) and the following network elements are needed to test this
feature:
• DX MSC/VLR
• DX HLR
• BSC
• BTS

2.4.2 Prerequisites for testing

MAP interface
The MAP-protocol in the MSC/VLR and the HLR for application context 1, 3, 5, and 6,
need to be at least in version 3.

Interrogating and modifying application context parameters

1 Check the current values for the application context parameters in the MSC and the
HLR with the following command:
ZOPH;
Example:
To set version 3 for call control transfer context, use the following command:
ZOPH:MODIFY:AC=6,:VER=3,;

8 Id:0900d805806b6278
Feature 681: Support of Optimal Routing (SOR) for Installation and testing
Late CF

Handling charging
If there is a working Billing Centre connected to the MSC, it must be able to handle the
changed CDR format.
If there is no CHU in the MSC, STU is used instead. Charging Data is stored on the CHU
disks by default.
1 Find out the data block storing time with the following commands:
• If there are multiple CHU-pairs in the configuration, use the following command:
ZGEI::CHU=<CHU_pair_index>;
• If there is just one CHU-pair in the configuration, use the following command:
ZGEI:;
2 Empty the current charging data block into a disk file by giving the parameter of the
GET command in form of HH-MM.
where:
HH hours
MM minutes
ZGET::TIME=<current_time + 1 min>;
(Wait until time is up <current_time + 1 min>.)
These values are restored after the test is completed.
3 Close the open file:
• If there are multiple CHU-pairs in the configuration, use the following command:
ZIFS:CHU,<CHU_pair_index>:GSMCHA:,OPEN:F;
• If there is just one CHU-pair in the configuration, use the following command:
ZIFS:CHU:GSMCHA:,OPEN,:F;
4 Move the produced CDRs to the new charging data disk file.

2.4.3 Test execution and expected results

Make a test call from PSTN or from an MS to mobile subscriber B, who forwards the call
(to PSTN or MS subscriber) because for example, MS_B is busy.
If the charging check is in use, the country code of the forwarded-to-exchange has to be
the same as the country code of the GMSC, or the HPLMNB, or the VPLMNB.

Test execution
1. Check whether Call Forwarding Busy (CFB) is available in the MSC/VLR with the
following command:
ZMXO;
If CFB is not available in the MSC/VLR, use the following command:
ZMXM:::CFB=Y,;
2. Provide and activate CFB for subscriber B in the HLR with the following commands:
ZMSD:IMSI=<imsi>,:CFB=Y;
ZMSS:IMSI=<imsi>,:CFB=<redirection number>;
3. Make subscriber B busy by making a call from MS_B to subscriber D.
4. Make a call from subscriber A to subscriber B.
5. Make sure that the call is successfully forwarded to subscriber C.

Id:0900d805806b6278 9
Installation and testing Feature 681: Support of Optimal Routing (SOR) for
Late CF

6. Release the calls and empty the current charging data block into a disk file by using
the following command:
ZGET::TIME=<current_time + 1 min>;
(Wait until the time is up.)
– If there are multiple CHU-pairs in the configuration, use the following command:
ZIFI:CHU,<CHU_pair_index>:GSMCHA:S;
– If there is just one CHU-pair in the configuration, use the following command:
ZIFI:CHU:GSMCHA:S;
Look for the current disk file number.
To close the charging data disk file, currently open one or several CHAs:
– If there are multiple CHU-pairs in the configuration, use the following command:
ZIFS:CHU,<CHU_pair_index>:GSMCHA:,OPEN:F;
– If there is just one CHU-pair in the configuration, use the following command:
ZIFS:CHU:GSMCHA:,OPEN,:F;
7. The CDRs are in the charging data disk file CFnnnn.DAT, on the CHU Winchester
disk ('nnnn' is the current disk file number in the output of the previous IFI com-
mand).
Restore the data blocking storing time that was defined before the test by using the
following command:
ZGET::TIME=<old_value>;
8. Analyse CFnnnn.DAT file in the Billing Centre.
When this feature is implemented in an operating MSC, it is not possible to isolate
the CDRs produced from test calls to one CFnnnn.DAT file. In this case, you do not
have to close the data files with the IFS command. The Billing Centre is responsible
for finding the CDRs among the charging data (for the calls in question).

Expected results
Make sure that there is a FORW CDR generated for this call and that the value 1 is
updated into the OR_FLAG field.

Interworking with CAMEL Phase 2, 3 or 4 O-CSI

If the O-CSI from the RCH operation was configured to have precedence over the O-
CSI from SRI-Ack, then it was used for triggering in the GMSC.

2.5 Deactivation of feature

1. Deactivate the feature with the following command:
ZWOA:2,560,D;
2. Check whether the feature has been deactivated by using the following command:
ZWOS:2,560;
The value of the SOR_LCF_SUPPORTED parameter (Identifier 00560) has to be 'deac-
tivated'.

Using EOS cause codes

SOR uses the following cause codes for LCF:
• lcf_busy_notif_to_a = 1035
LCF (OR) when the MS is busy, notification to subscriber A.
• lcf_busy_no_notif_to_a = 1036
LCF (OR) when the MS is busy, no notification to subscriber A.

10 Id:0900d805806b6278
Feature 681: Support of Optimal Routing (SOR) for Installation and testing
Late CF

• lcf_no_answ_notif_to_a = 1037
LCF (OR) when the MS does not answer, notification to subscriber A.
• lcf_no_answ_no_notif_to_a = 1038
LCF (OR) when the MS does not answer, no notification to subscriber A.
• lcf_no_reach_notif_to_a = 1039
LCF (OR) when the MS is not reachable, notification to subscriber A.
• lcf_no_reach_no_notif_to_a = 103A
LCF (OR) when the MS is not reachable, no notification to subscriber A.
Check whether the cause code exists by using the following MML command:
ZRXI:RESGR=<analysis result group>,CAUSE=<cause code>;
Delete the cause code by using the following MML command :
ZRXD:<cause code>;

2.6 Deactivation testing

If the feature is deactivated, all calls are routed normally.

Id:0900d805806b6278 11