Native Telephony Features in Version 5.

0P1

March 2007

Document No. DC-4215-20

Gilat Satellite Networks Ltd.

This document contains information proprietary to Gilat Satellite Networks Ltd. and may not be
reproduced in whole or in part without the express written consent of Gilat Satellite Networks Ltd. The
disclosure by Gilat Satellite Networks Ltd. of information contained herein does not constitute any
license or authorization to use or disclose the information, ideas or concepts presented. The contents of
this document are subject to change without prior notice.
 Native Telephony Features in Version 5.0P1

Contents

1. Introduction....................................................................................................................1

2. Subscriber Carrier Pre-Selection ..................................................................................2

2.1 Overview .................................................................................................................2
2.2 Carrier Pre-Selection in SkyEdge ............................................................................2
2.2.1 Default Manipulation Enhancements in Global Manipulation Tables ..............3
2.2.2 DCAS Phonebook Search Enhancement.......................................................5
2.2.3 SS7 Carrier Selection....................................................................................6
2.2.4 Requirements................................................................................................6
2.2.5 Limitations.....................................................................................................6
2.2.6 Network Downtime Required .........................................................................6
2.2.7 Backward Compatibility .................................................................................6
2.3 Configuration ...........................................................................................................7
2.3.1 Configuring DCAS .........................................................................................7
2.3.2 Configuring VSATs......................................................................................10
2.3.3 Resetting VSATs.........................................................................................14

3. Call-by-Call Unconditional Call Forwarding ...............................................................16

3.1 Overview ...............................................................................................................16
3.2 Call Forwarding .....................................................................................................16
3.2.1 Call-by-Call Unconditional Call Forwarding .................................................16
3.2.2 Requirements..............................................................................................17
3.2.3 Limitations...................................................................................................18
3.2.4 Network Downtime Required .......................................................................18
3.3 Configuration Procedures ......................................................................................18
3.3.1 Configuring Supplementary Service Control Codes at the DCAS.................19
3.3.2 Verifying Supplementary Service Control Codes at the VSAT Telephony
Template.....................................................................................................22
3.3.3 Configuring CPG Tones in the VSAT Telephony Template ..........................24
3.3.4 Configuring Unconditional Call Forwarding at the VSAT ..............................26

4. Call-by-Call Call Line Identification Restriction (CLIR)..............................................30

4.1 Overview ...............................................................................................................30
4.2 Call-by-Call CLIR...................................................................................................30
4.2.1 Requirements..............................................................................................31
4.2.2 Limitations...................................................................................................31
4.2.3 Network Downtime Required .......................................................................31
4.3 Configuration Procedures ......................................................................................31
4.3.1 Configuring Supplementary Service Control Codes at the DCAS.................31

Native Telephony Features in

Version 5 i
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

4.3.2 Verifying Supplementary Service Control Codes at the VSAT Telephony

Template.....................................................................................................35
4.3.3 Configuring Call-by-Call CLIR at the VSAT..................................................37
Figures

Figure 1: DCAS License Management.............................................................................7

Figure 2: DCAS General Parameters ..............................................................................8
Figure 3: DCAS Routing Parameters...............................................................................8
Figure 4: VSAT Configuration........................................................................................11
Figure 5: VSAT Telephony Unique Parameters .............................................................11
Figure 6: FXS Card Instances .......................................................................................12
Figure 7: FXS Card Port Parameters.............................................................................12
Figure 8: FXS Card Port Default Carrier ........................................................................12
Figure 9: DCAS License Management...........................................................................19
Figure 10: DCAS General Parameters...........................................................................20
Figure 11: DCAS Supplementary Services ....................................................................20
Figure 12: Committing DCAS Configuration Changes and Linked Parameters ..............21
Figure 13: Commit Confirmation....................................................................................22
Figure 14: VSAT Telephony Configuration ....................................................................23
Figure 15: VSAT Telephony Template – Supplementary Services Control Codes..........23
Figure 16: Call Progress Tones .....................................................................................25
Figure 17: Call Progress Tone Configuration.................................................................25
Figure 18: VSAT Configuration......................................................................................27
Figure 19: VSAT Telephony Parameters .......................................................................27
Figure 20: FXS Card Instances .....................................................................................28
Figure 21: FXS Port Parameters – Call Forwarding .......................................................28
Figure 22: Call Forwarding Type Options ......................................................................29
Figure 23: DCAS License Management.........................................................................32
Figure 24: DCAS General Parameters...........................................................................33
Figure 25: DCAS Supplementary Services ....................................................................33
Figure 26: Committing DCAS Configuration Changes and Linked Parameters ..............34
Figure 27: Commit Confirmation....................................................................................35
Figure 28: VSAT Telephony Configuration ....................................................................36
Figure 29: VSAT Telephony Template – Supplementary Services Control Codes..........36
Figure 30: VSAT Configuration......................................................................................38
Figure 31: VSAT Telephony Parameters .......................................................................38
Figure 32: FXS Card Instances .....................................................................................39
Figure 33: FXS Port Parameters – Call Forwarding and CLIR Parameters ....................39
Tables

Table 1: DCAS Routing Parameters ................................................................................9

Native Telephony Features in

Version 5 ii
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

1. Introduction

This document describes the following SkyEdge Native telephony features:

„ Subscriber Carrier Pre-Selection

„ Call-by-Call Unconditional Call Forwarding

„ Call-by-Call Call Line Identification Restriction (CLIR)

Native Telephony Features in

Version 5 1
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

2. Subscriber Carrier Pre-Selection

2.1 Overview

In many countries, dialing national and international destinations requires selection

of a carrier (a service provider). Selecting of the carrier is done by prefixing the
dialed number with a carrier code.

Generally, carrier selection is done in two ways:

„ Call-by Call – the subscriber dials a carrier code for each call attempt. If no
carrier code is dialed the call is rejected.

Or

„ Carrier Pre-Selection – the subscriber has a preconfigured carrier code. When a

call is attempted and a carrier code is not dialed with the number, the predefined
carrier code is automatically added to the dialed number.

2.2 Carrier Pre-Selection in SkyEdge

In previous versions, SkyEdge supported only call-by-call carrier selection. Starting

from version 5.0P1, SkyEdge supports carrier pre-selection.

In SkyEdge, a default carrier code can be defined for each subscriber. The Default
Carrier parameter can be defined for each FXS port. This parameter contains up to 8
digits.

If a default carrier is not used, the Default Carrier parameter is left blank. If a
default carrier is defined for a specific FXS port, it is part of this port’s registration
information.

NOTE
Dialing with a carrier code overrides the pre-selected carrier code.

Native Telephony Features in

Version 5 2
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

2.2.1 Default Manipulation Enhancements in Global Manipulation Tables

In previous SkyEdge versions, the Outgoing Global Manipulation and Incoming

Global Manipulation tables had an associated default manipulation rule that was
applied in case the dialed number did not match any of the specified rules in the
tables. According to this rule, the area code associated with the originating VSAT
was added as prefix to the dialed number.

In SkyEdge version 5.0P1, the operation of the Outgoing and Incoming Global
Manipulation tables has been modified as described in the sections below.

NOTE
The DCAS OGMT and IGMT table settings are configured for the entire
network.

2.2.1.1 Outgoing Global Manipulation Table

When the default manipulation rule is activated in the OGMT table, the prefix is
added to the dialed number in one of the two ways:

„ The area code of the originating VSAT. This is the default value.

Or

„ The default carrier of the originating subscriber as defined in the settings of the
VSAT FXS port.

In the OGMT table, the default manipulation rule can be applied in one of the
following ways:

„ Upon no match – the default rule is applied if no match for the dialed number is
found in the OGMT table. If this option is selected, one manipulation is always
performed in the OGMT table.

„ Always, after surveying the manipulation table – the default rule is applied
after the manipulation table (OGMT) is checked and no match has been found. If
this option is selected, one or two manipulations are performed in the OGMT
table.

− If the table is scanned and no match is found, one manipulation is performed

and the default rule is applied.

Native Telephony Features in

Version 5 3
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

− If the table is checked and a matching value is found, two manipulations are
performed: the matching value from the table is applied followed by the
default rule.

„ Always, before surveying the manipulation – the default rule is applied before
the manipulation table (OGMT) is checked. If this option is selected, one or two
manipulations are performed in the OGMT table.

− The default rule is applied before the OGMT table is checked resulting in
one manipulation. If the table is scanned and a matching value is found,
additional manipulation is performed and the value is added to the default
rule.

− The default rule is applied before the OGMT table is checked resulting in
one manipulation. If the table is scanned and no match is found, only the
default rule is applied.

„ Never – the default rule is not applied. If this option is selected, zero or one
manipulation is performed.

2.2.1.2 Incoming Global Manipulation Table

When the default manipulation rule is activated in the IGMT table, the prefix in a
form of the area code of the originating remote is added to the dialed number.

In the IGMT table, the default manipulation rule can be applied in one of the
following ways:

„ Upon no match – the default rule is applied if no match for the dialed number is
found in the IGMT table. If this option is selected, one manipulation is always
performed in the IGMT table.

„ Always, after surveying the manipulation table – the default rule is applied
after the manipulation table (IGMT) is checked and no match has been found. If
this option is selected, one or two manipulations are performed in the IGMT
table.

− If the table is scanned and no match is found, one manipulation is performed

and the default rule is applied.

− If the table is checked and a matching value is found, two manipulations are
performed: the matching value from the table is applied followed by the
default rule.

Native Telephony Features in

Version 5 4
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

„ Always, before surveying the manipulation – the default rule is applied before
the manipulation table (IGMT) is checked. If this option is selected, one or two
manipulations are performed in the IGMT table.

− The default rule is applied before the IGMT table is checked resulting in one
manipulation. If the table is scanned and a matching value is found,
additional manipulation is performed and the value is added to the default
rule.

− The default rule is applied before the IGMT table is checked resulting in one
manipulation. If the table is scanned and no match is found, only the default
rule is applied.

„ Never – the default rule is not applied. If this option is selected, zero or one
manipulation is performed.

NOTE
When a call addressed to a VSAT subscriber is forwarded, the area code
or the default carrier code used for default manipulation is that of the
chain originator.

2.2.2 DCAS Phonebook Search Enhancement

In previous versions, when DCAS searched the manipulated number in the

phonebook, it always attempted to match the entire manipulated number, starting at
the first digit. In the past, both the manipulated number and the VSAT phone number
were in the format of an area code prefix followed by a subscriber number. In such
case, it was possible to find the destination VSAT in the phonebook, if the called
subscriber was a VSAT subscriber.

The Carrier code which is part of SkyEdge version 5.0P1 is not part of the VSAT
subscriber number. The above phonebook match can no longer be made, since the
manipulated number most likely contains a default carrier code which does not
appear in the phonebook.

This problem is solved by the following new DCAS parameters: Phonebook Offset
Outgoing and Phonebook Offset Incoming. These parameters define in the
applicable search offsets for outgoing and incoming calls.

The Phonebook Offset Outgoing parameter defines the offset within the
manipulated number used for searching the phonebook for calls originated from the
FXS ports (outgoing).

Native Telephony Features in

Version 5 5
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

The Phonebook Offset Incoming parameter defines the offset within the
manipulated number used for searching the phonebook for calls originated from E1
ports (incoming). All calls entering the satellite system via an E1 port are regarded as
incoming.

With the relevant offset option set to n, the DCAS attempts to match the manipulated
number to the phonebook starting at the nth digit of the manipulated number.

For backward compatibility, the default value for both offset parameters is 1.

2.2.3 SS7 Carrier Selection

The Carrier Selection parameter used in some SS7 implementations is not supported
in SkyEdge and is not relevant to the default carrier pre-selection feature described in
this document.

2.2.4 Requirements

SkyEdge system upgraded to version 5.0P1.

2.2.5 Limitations

None

2.2.6 Network Downtime Required

Configuration of the predefined subscriber carrier requires modifying configuration

of the DCAS and of the VSATs. For the configuration changes to take effect, the
DCAS and VSATs must be rebooted.

2.2.7 Backward Compatibility

„ DCAS supporting subscriber carrier pre-selection is compatible with VSATs

from previous versions. In this case, the system is operational, but the subscriber
carrier pre-selection feature is not supported.

„ VSAT supporting subscriber carrier pre-selection is compatible with DCAS from

previous versions. In this case, the system is operational, but the subscriber
carrier pre-selection feature is not supported.

NOTE
To ensure the proper operation of the subscriber carrier pre-selection
feature, the entire system including the DCAS and VSATs must be
upgraded to version 5.0P1.

Native Telephony Features in

Version 5 6
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

2.3 Configuration

2.3.1 Configuring DCAS

To configure DCAS:

1. In the NMS Hub View window, double-click the DCAS icon.

Result: The DCAS Configuration window opens.

2. In the DCAS tree view, click License Management.

Result: The DCAS License Management parameters are displayed.

Figure 1: DCAS License Management

3. Verify that the Network Simultaneous Calls parameter is set to Activate.

4. In the DCAS tree view, click General Parameters.

Result: The DCAS General Parameters tabs are displayed.

Native Telephony Features in

Version 5 7
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

Figure 2: DCAS General Parameters

5. Click the Routing tab in the right pane.

Result: The DCAS Routing parameters are displayed.

Figure 3: DCAS Routing Parameters

6. Configure the default carrier and phonebook parameters as shown in Table 1,

below.

Native Telephony Features in

Version 5 8
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

Table 1: DCAS Routing Parameters

Parameter Name Description Values

OGMT Default The OGMT (Outgoing Area code prefix
Manipulation Type Manipulation Table) default
manipulation rule). Default carrier prefix
Default value: Area code
prefix.
OGMT Default Defines when the OGMT Default Upon no match
Manipulation Mode Manipulation mode is used
Always, after table survey
Always, before table survey,
Never
Default value: Upon no
match
IGMT Default Defines the default rule Upon no match
Manipulation Mode operation mode
Always, after table survey
Always, before table survey,
Never
Default value: Upon no
match
Phonebook Offset The offset within the 1-20
Outgoing manipulation number used for
searching the phonebook for Default value:1
outgoing calls (originated from
FXS ports).
Phonebook Offset The offset within the 1-20
Incoming manipulation number used for
searching the phonebook for Default value:1
incoming calls (originated from
E1 ports).

7. Click the Save button.

Result: The Save Confirmation window is displayed.

8. Click OK.

9. Click the Commit button.

Result: The Commit Confirmation window is displayed.

10. Click OK.

Native Telephony Features in

Version 5 9
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

11. For the DCAS configuration changes to take effect, the DCAS must be rebooted:

„ To reset a non-redundant DCAS, right-click the DCAS icon and select

CommandsŒReboot.

„ To reset a redundant DCAS, right-click the DCAS icon and select

CommandsŒReboot Active & Standby.

Result: The DCAS Reset confirmation window is displayed.

12. Click OK.

Result: The DCAS starts the reboot sequence.

13. Verify that the DCAS completes the power-up sequence successfully and goes
online.

2.3.2 Configuring VSATs

NOTE
Perform this procedure for all VSATs in the systems that support
telephony.

To configure a VSAT:

1. Click the VSATs View button.

Result: The VSATs View window is displayed.

2. Browse to the relevant VSAT.

3. Double-click the relevant VSAT icon.

Result: The VSAT Configuration window is displayed.

Native Telephony Features in

Version 5 10
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

Figure 4: VSAT Configuration

4. Click the Telephony tab.

Result: The VSAT Telephony unique parameters are displayed.

Figure 5: VSAT Telephony Unique Parameters

5. In the tree view, click TelephonyŒFXS Card Instances.

Result: The VSAT FXS Card Instance parameters are displayed.

Native Telephony Features in

Version 5 11
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

Figure 6: FXS Card Instances

6. Scroll to the right and click Open Element under Ports.

Result: Configuration parameters of the selected FXS port.

Figure 7: FXS Card Port Parameters

7. Scroll to the Default Carrier parameter.

Figure 8: FXS Card Port Default Carrier

Native Telephony Features in

Version 5 12
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

8. Enter the code (up to 8 digits) of the default carrier for calls originated by this
subscriber.

9. (If applicable) Configure the default carrier for calls for the rest of the FXS Card
ports as described in steps 7 and 8.

10. Perform steps 6- 9 to configure additional FXS Card slots.

11. Click the Save button.

Result: The Save Confirmation window is displayed.

12. Click OK.

13. Click the Commit button.

Result: The Commit and Reset Confirmation window is displayed.

14. Perform either of the following:

„ Click Yes to commit the VSAT configuration and reboot the VSAT.

Or

„ Click No to commit the VSAT configuration without rebooting the VSAT. For
information on how to reset a single or multiple VSATs, refer to Section 2.3.3.

NOTE
For the VSAT configuration changes to take effect, the VSAT must be
reset.

15. If the VSAT was rebooted, verify that it successfully completes its power-up
sequence and goes online.

16. Verify that the VSAT is operational.

Native Telephony Features in

Version 5 13
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

2.3.3 Resetting VSATs

If VSATs were not reset with the commit commands, the modified VSATs and
VSATs associated with the modified Telephony template must be reset later,
following these guidelines:

„ VSAT can be reset one at a time.

„ VSATs can also be reset in groups.

2.3.3.1 Resetting a Single VSAT

To reset a single VSAT:

1. In the NMS Browser Toolbar, click VSATs View.

Result: The VSAT View window is displayed.

2. Select and right-click the desired VSAT from the VSAT list, and select
Commands→Access→Reset from the context menu.

Result: The Reset confirmation request is displayed.

3. Click Yes to reset the selected VSAT.

Result: The VSAT is reset; the roll-off factor changes take place.

4. Once the VSAT completes its power-up cycle, verify that it has returned to the
Online state.

2.3.3.2 Resetting a Group of VSATs

NOTE
It is recommended to reset VSATs in groups of up to 100.

To reset a group of VSATs:

1. In the NMS Browser Toolbar, click VSATs View.

Result: The VSAT View window is displayed.

2. Select and right-click the desired VSATs from the VSAT list, and select
Multiple Reset from the context menu.

Result: The VSAT Reset confirmation request is displayed.

Native Telephony Features in

Version 5 14
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

3. Click Yes to reset the VSATs associated with this Access template.

Result: The VSATs are reset; the roll-off factor changes take place.

4. Once the VSATs complete the power-up cycle, verify that each VSAT has
returned to the Online state.

Native Telephony Features in

Version 5 15
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

3. Call-by-Call Unconditional Call Forwarding

3.1 Overview

The Call Forwarding and CLIR features are part of the SkyEdge Native telephony
supplementary services. In the previous SkyEdge versions, these features could be
controlled only from the NMS by the hub operator. VSAT subscribers had no control
over these features.

In SkyEdge version 5.0P1, VSAT subscribers can control the Call Forwarding
Unconditional (CFU) and Call-by-Call CLIR and services via their phones.

NOTE
For information on how to configure the CLIR feature, refer to Section 4.

3.2 Call Forwarding

The Call Forwarding feature is relevant for incoming calls addressed to the VSAT
subscriber. If the service is activated, incoming calls matching the Call Forwarding
type are diverted to another destination, which is provided during the service
activation.

The following four types of the Call Forwarding service are supported:

„ Busy – the Call Forwarding service is activated if the VSAT subscriber number
is busy.

„ No Reply – the Call Forwarding service is activated if there is no reply at the

VSAT subscriber number.

„ Busy & No Reply - the Call Forwarding service is activated in case the VSAT
subscriber number is busy and if there is no reply at the VSAT subscriber
number.

„ Unconditional – the Call Forwarding service is activated on all incoming calls.

All calls addressed to the VSAT subscriber are automatically forwarded to
another destination. When the CFU service is used in the system, the VSAT
subscriber never receives incoming calls.

3.2.1 Call-by-Call Unconditional Call Forwarding

In SkyEdge version 5.0P1, in addition to the NMS configuration, the user can
activate or deactivate Unconditional Call Forwarding, by dialing pre-defined service

Native Telephony Features in

Version 5 16
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

control strings. The same strings can be used for reactivating the service with a
different forwarding number or changing the forwarding type from anything else to
unconditional call forwarding.

The CFU activation and deactivation codes are configured in the DCAS
Supplementary Services table. The codes are the same for all VSAT subscribers.

When the VSAT recognizes the CFU service code, it sends a Call Request message
to DCAS. DCAS attempts to set the call forwarding parameters in the NMS database
as requested. This operation includes committing of the VSAT parameters. The
commit operation is applied only to the forwarding parameters; other modified
parameters that were not committed yet are not being committed.

When the NMS database is updated, DCAS changes the forwarding information in its
database and terminates the call with the Call Clearing message. According to the
status code included in the message, the VSAT learns whether the request was
accepted or denied. If the request was accepted, the VSAT updates its own table and
plays a Confirmation tone towards the subscriber. Otherwise, the VSAT provides an
out of order tone and does not update its table.

NOTE
If the CFU number is identical to the subscriber’s own number, any
incoming call to that subscriber will be rejected due to the cyclic
forwarding process.

The Call Forwarding service is configured for each VSAT subscriber. The service is
configured using the Call Forwarding Type and the forwarding Phone Number
parameters. When using the Unconditional Call Forwarding type, the User Control
parameter is also configured to enable or disable the VSAT subscriber control over
the service.

3.2.2 Requirements

SkyEdge system upgraded to version 5.0P1.

Native Telephony Features in

Version 5 17
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

3.2.3 Limitations

The current implementation of the CFU feature does not include the following
features:

„ Maximum Session Rate – DCAS can support up to 10 service control sessions

(changes to the CFU service) per minute. If there is an attempt to open more
sessions, some sessions are rejected due to inability of DCAS to establish the
required connection with the NMS.
DCAS handles only one control session at any given time. If DCAS receives a
request for another session, while another session is still open, the request is
rejected.

„ Mutual Operations – If the OpServ interface is used in the system, it may

happen that the database of the same VSAT is simultaneously modified from
more than one interface. In this case, the last save operation determines the
content of the database.

„ No Verification of the Forwarding Number – The SkyEdge system does not

support verification of the forwarding number before activating the Call
Forwarding service and confirming the operation.

„ Using the Star Sign in the Forwarding Number - A forwarding number can
contain only regular digits (0-9). Inserting a star sign will cause all digits
following the star sign to be ignored.

3.2.4 Network Downtime Required

Configuration of the Unconditional Call Forwarding feature requires modifying

configuration of the DCAS and of the VSATs. For the configuration changes to take
effect, the DCAS and VSATs must be rebooted.

3.3 Configuration Procedures

This section describes the following procedures:

„ Configuring Supplementary Service Control Codes at the DCAS

„ Verifying Supplementary Service Control Codes at the VSAT Telephony

Template

„ Configuring CPG Tones in the VSAT Telephony Template

„ Configuring Unconditional Call Forwarding at the VSAT

Native Telephony Features in

Version 5 18
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

3.3.1 Configuring Supplementary Service Control Codes at the DCAS

This section describes how to configure the CLIR and CFU activation/deactivation
codes at the DCAS.

NOTE
The codes are the same for all VSAT subscribers. The CLIR and CFU
control codes at the DCAS are linked to the relevant parameters in the
VSAT Telephony template.

To configure DCAS:

1. In the NMS Hub View window, double-click the DCAS icon.

Result: The DCAS Configuration window opens.

2. In the DCAS tree view, click License Management.

Result: The DCAS License Management parameters are displayed.

Figure 9: DCAS License Management

3. Verify that the Network Simultaneous Calls parameter is set to Activate.

4. In the DCAS tree view, click General Parameters.

Result: The DCAS General Parameters tabs are displayed on the right.

Native Telephony Features in

Version 5 19
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

Figure 10: DCAS General Parameters

5. Click the Supplementary services tab in the right pane.

Result: The DCAS Supplementary services tab is displayed.

Figure 11: DCAS Supplementary Services

NOTE
CFU stands for Call Forwarding Unconditional.

6. Enter the CFU Activation Code. The CFU activation code is a telephone number
of up to 8 digits. The code can include star signs (*) and pound signs (#).

7. Enter the CFU Deactivation Code. The CFU deactivation code is a telephone
number of up to 8 digits. The code can include star signs (*) and pound signs (#).

Native Telephony Features in

Version 5 20
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

CAUTION
Defining a control code identical to a prefix of another control code is not
recommended.
This configuration will render one of the services unusable.

8. Click the Save button.

9. Close the DCAS Configuration window.

NOTE
The CFU control codes at the DCAS are linked to the relevant
parameters in the VSAT Telephony template.
For the changes to be updated in the DCAS and in the VSAT templates,
the DCAS configuration must be committed using the Commit Changes
(Include Linked Hub and Templates) command.

10. Right-click the DCAS icon and select

ConfigurationŒCommit Changes (Include Linked HUB and Templates).

Figure 12: Committing DCAS Configuration Changes and Linked Parameters

Result: The Commit Confirmation window is displayed.

Native Telephony Features in

Version 5 21
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

Figure 13: Commit Confirmation

11. Click Yes.

12. For the DCAS configuration changes to take effect, the DCAS must be rebooted:

„ To reset a non-redundant DCAS, right-click the DCAS icon and select

CommandsŒReboot.

„ To reset a redundant DCAS, right-click the DCAS icon and select

CommandsŒReboot Active & Standby.

Result: The DCAS Reset confirmation window is displayed.

13. Click OK.

Result: The DCAS starts the reboot sequence.

14. Verify that the DCAS completes the power-up sequence successfully and goes
online.

3.3.2 Verifying Supplementary Service Control Codes at the VSAT Telephony Template

CFU activation/deactivation codes are configured at the DCAS as described in

Section 3.3.1.

CFU parameters at the VSAT Telephony template are linked to the DCAS
parameters and are updated with each change. This section describes how to verify
that the link between the DCAS and VSAT Telephony parameters has not been
broken.

To verify that the CFU codes are linked to the DCAS:

1. On the NMS Browser, click the Templates button.

Result: The VSAT Templates Configuration window is displayed.

2. In the VSAT Software column, select the relevant software version.

Native Telephony Features in

Version 5 22
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

3. In the VSAT RPs column, select Telephony.

4. In the Template Name column, double-click the relevant Telephony template.

Result: The VSAT Telephony Template Configuration window is displayed.

Figure 14: VSAT Telephony Configuration

5. Click the Supplementary Services tab on the right.

Result: The Supplementary Services tab is displayed.

Figure 15: VSAT Telephony Template – Supplementary Services Control Codes

6. Verify the CFU activation/deactivation codes are in the linked state as shown in
Figure 15, above.

Native Telephony Features in

Version 5 23
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

NOTE
If the connection between the VSAT Telephony template and the DCAS
is temporarily lost, it may be necessary to restore it. If the CLIR and CFU
fields are blank and/or the Link icon to the right of the fields includes the
red X indicating the loss of connection (Unlinked state), right-click the
Link icon and select Re-Link Parameter in order to refresh the fields
and/or re-establish the connection with the DCAS.

7. Configure the new CPG tones as shown in Section 3.3.3.

3.3.3 Configuring CPG Tones in the VSAT Telephony Template

In SkyEdge version 5.0P1, two new tones were added to the Call Progress Tones
table:

„ Special Dial Tone – This tone is sounded in the systems where VSAT subscriber
has an active forwarding service instead of a regular one. The Special Dial Tone
is displayed upon off hook.

„ Confirmation Tone – This tone is sounded when the call forwarding request has
been accepted and the call is being forwarded.

3.3.3.1 Configuring CPG Tones

NOTE
If more than one Telephony template is used in the system, perform this
procedure for all Telephony templates configured in the system.
The method for configuring the Special Dial Tone and Confirmation Tone
is similar to that of all other call progress tones.

To configure the CPG tones in the VSAT Telephony template:

1. On the NMS Browser, click the Templates button.

Result: The VSAT Templates Configuration window is displayed.

2. In the VSAT Software column, select the relevant software version.

3. In the VSAT RPs column, select Telephony.

4. In the Template Name column, double-click the relevant Telephony template.

Result: The VSAT Telephony Template Configuration window is displayed.

5. In the tree view, click Call ProgressŒCall Progress Tones Instances.

Native Telephony Features in

Version 5 24
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

Figure 16: Call Progress Tones

6. In the Special Dial Tone row (7), click Open Element.

Result: The Special Dial Tone configuration parameters are displayed.

Figure 17: Call Progress Tone Configuration

7. Configure the relevant parameters for the Special Dial Tone.

8. In the Confirmation Tone row (8), click Open Element.

Result: The Confirmation Tone configuration parameters are displayed.

9. Configure the relevant parameters for the Confirmation Tone.

10. Click the Save button.

Result: The Configuration Saved dialog box is displayed.

11. Click OK.

Native Telephony Features in

Version 5 25
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

12. Click the Commit button.

Result: The Reset the VSATs associated with this template window is
displayed.

13. Perform either of the following:

„ Click Yes to commit and reset the VSATs associated with the modified template.

Or

„ Click No to commit the Template configuration without resetting the VSATs. For
information on how to reset a single or multiple VSATs, refer to Section 2.3.3.

NOTE
For the VSAT configuration changes to take effect, the VSAT must be
reset.

14. If the VSAT was rebooted, verify that it successfully completes its power-up
sequence and goes online.

15. Verify that the VSAT is operational.

3.3.4 Configuring Unconditional Call Forwarding at the VSAT

NOTE
Perform this procedure for each VSAT that will be using the
Unconditional Call Forwarding feature.

To configure Unconditional Call Forwarding at the VSAT:

1. Click the VSATs View button.

Result: The VSATs View window is displayed.

2. Double-click the relevant VSAT icon.

Result: The VSAT Configuration window is displayed.

Native Telephony Features in

Version 5 26
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

Figure 18: VSAT Configuration

3. Click the Telephony tab.

Result: The VSAT Telephony parameters are displayed.

Figure 19: VSAT Telephony Parameters

4. Verify that the correct Telephony template is selected in the Telephony

Template field.

Native Telephony Features in

Version 5 27
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

5. In the Telephony tree view, click FXS Card Instances.

Result: The FXS Card Instances are displayed.

Figure 20: FXS Card Instances

NOTE
CFU configuration (see steps 6 - 10) must be performed for each port of
the VSAT FXS card.

6. Scroll to the right and click Open Element in the Ports column.

Result: The Port parameters are displayed.

7. Scroll to the Call Forwarding parameters.

Figure 21: FXS Port Parameters – Call Forwarding

8. In the Call Forwarding section, set the Type parameter to Unconditional.

Native Telephony Features in

Version 5 28
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

Figure 22: Call Forwarding Type Options

9. In the Phone Number parameter, enter the phone number to which all phone
calls will be forwarded.

10. Set the User control parameter to Enable.

11. Click the Save button.

12. Click the Commit button.

Result: The Reset the VSAT with Commit command confirmation window is
displayed.

13. Perform either of the following:

„ Click Yes to commit and reset the modified VSAT.

Or

„ Click No to commit the VSAT configuration without resetting the VSAT. For
information on how to reset a single or multiple VSATs, refer to Section 2.3.3.

NOTE
For the VSAT configuration changes to take effect, the VSAT must be
reset.

Native Telephony Features in

Version 5 29
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

4. Call-by-Call Call Line Identification Restriction (CLIR)

4.1 Overview

The Call Forwarding and CLIR features are part of the SkyEdge Native telephony
supplementary services. In the previous SkyEdge versions, these features could be
controlled only from the NMS by the hub operator. VSAT subscribers had no control
over these features.

In SkyEdge version 5.0P1, VSAT subscribers can control the Call Forwarding
Unconditional (CFU) and Call-by-Call CLIR and services via their phones.

NOTE
For information on how to configure the Call Forwarding Unconditional
feature, refer to Section 3.

4.2 Call-by-Call CLIR

The CLIR (Call Line Identification Restriction) service is applicable to outgoing

calls made by the VSAT subscriber. Normally, the subscriber's phone number may
be presented to the called party if the Calling Line Identification Presentation (CLIP)
feature exists. If the CLIR service is activated, the Calling Line Identification
Presentation is blocked and the number is not displayed.

The Calling Line Identification (number) is always included in the relevant signaling
messages. If CLIR is activated, the signaling messages contain an appropriate
indication that causes the number to be blocked.

In the SkyEdge system, the CLIR service can be activated for each VSAT subscriber.
The setting is applicable for all calls made by the VSAT subscriber.

In SkyEdge version 5.0P1, the user can override the CLIR service setting for a
specific call by prefixing the dialed number with the call-by-call CLIR
activation/deactivation code.

The status of the CLIR service for such call is determined by the service code dialed
regardless of the CLIR service setting in the system.

NOTE
When the VSAT recognizes the call-by-call CLIR service code prefix, it
removes the code prefix from the dialed string. Consequently, all
manipulation rules are applied to the dialed destination number.

Native Telephony Features in

Version 5 30
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

The CLIR activation and deactivation codes are configured in the DCAS
Supplementary Services table. The codes are the same for all VSAT subscribers.

4.2.1 Requirements

SkyEdge system upgraded to version 5.0P1.

4.2.2 Limitations

The current implementation of the CLIR feature does not include the following
features:

„ Mutual Operations – If the OpServ interface is used in the system, it may

happen that the database of the same VSAT is simultaneously modified from
more than one interface. In this case, the last save operation determines the
content of the database.

4.2.3 Network Downtime Required

Configuration of the Caller ID Restriction feature requires modifying configuration

of the DCAS and of the VSATs. For the configuration changes to take effect, the
DCAS and VSATs must be rebooted.

4.3 Configuration Procedures

This section describes the following procedures:

„ Configuring Supplementary Service Control Codes at the DCAS

„ Verifying Supplementary Service Control Codes at the VSAT Telephony

Template

„ Configuring Call-by-Call CLIR at the VSAT

4.3.1 Configuring Supplementary Service Control Codes at the DCAS

This section describes how to configure the CLIR activation/deactivation codes at the
DCAS.

NOTE
The codes are the same for all VSAT subscribers. The CLIR control
codes at the DCAS are linked to the relevant parameters in the VSAT
Telephony template.

Native Telephony Features in

Version 5 31
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

To configure DCAS:

1. In the NMS Hub View window, double-click the DCAS icon.

Result: The DCAS Configuration window opens.

2. In the DCAS tree view, click License Management.

Result: The DCAS License Management parameters are displayed.

Figure 23: DCAS License Management

3. Verify that the Network Simultaneous Calls parameter is set to Activate.

4. In the DCAS tree view, click General Parameters.

Result: The DCAS General Parameters tabs are displayed on the right.

Native Telephony Features in

Version 5 32
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

Figure 24: DCAS General Parameters

5. Click the Supplementary services tab in the right pane.

Result: The DCAS Supplementary services tab is displayed.

Figure 25: DCAS Supplementary Services

6. Enter the CLIR Activation Code. This parameter activates the CLIR feature for
the current call. The CLIR activation code is telephone number of up to 8 digits.

7. Enter the CLIR Deactivation Code. This parameter deactivates the CLIR feature
for the current call. The CLIR deactivation code is telephone number of up to 8
digits.

Native Telephony Features in

Version 5 33
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

CAUTION
Defining a control code identical to a prefix of another control code is not
recommended.
This configuration will render one of the services unusable.

8. Click the Save button.

9. Close the DCAS Configuration window.

NOTE
The CLIR control codes at the DCAS are linked to the relevant
parameters in the VSAT Telephony template.
For the changes to be updated in the DCAS and in the VSAT templates,
the DCAS configuration must be committed using the Commit Changes
(Include Linked Hub and Templates) command.

10. Right-click the DCAS icon and select

ConfigurationŒCommit Changes (Include Linked HUB and Templates).

Figure 26: Committing DCAS Configuration Changes and Linked Parameters

Result: The Commit Confirmation window is displayed.

Native Telephony Features in

Version 5 34
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

Figure 27: Commit Confirmation

11. Click Yes.

12. Perform either of the following to reboot the DCAS:

„ To reset a non-redundant DCAS, right-click the DCAS icon and select

CommandsŒReboot.

„ To reset a redundant DCAS, right-click the DCAS icon and select

CommandsŒReboot Active & Standby.

Result: The DCAS Reset confirmation window is displayed.

13. Click OK.

Result: The DCAS starts the reboot sequence.

14. Verify that the DCAS completes the power-up sequence successfully and goes
online.

4.3.2 Verifying Supplementary Service Control Codes at the VSAT Telephony Template

CLIR activation/deactivation codes are configured at the DCAS as described in

Section 3.3.1.

CLIR parameters at the VSAT Telephony template are linked to the DCAS
parameters and are updated with each change. This section describes how to verify
that the link between the DCAS and VSAT Telephony parameters has not been
broken.

To verify that the CLIR codes are linked to the DCAS:

1. On the NMS Browser, click the Templates button.

Result: The VSAT Templates Configuration window is displayed.

2. In the VSAT Software column, select the relevant software version.

Native Telephony Features in

Version 5 35
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

3. In the VSAT RPs column, select Telephony.

4. In the Template Name column, double-click the relevant Telephony template.

Result: The VSAT Telephony Template Configuration window is displayed.

Figure 28: VSAT Telephony Configuration

5. Click the Supplementary Services tab on the right.

Result: The Supplementary Services tab is displayed.

Figure 29: VSAT Telephony Template – Supplementary Services Control Codes

6. Verify the CLIR activation/deactivation codes are in the linked state as shown in
Figure 15, above.

Native Telephony Features in

Version 5 36
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

NOTE
If the connection between the VSAT Telephony template and the DCAS
is temporarily lost, it may be necessary to restore it. If the CLIR and CFU
fields are blank and/or the Link icon to the right of the fields includes the
red X indicating the loss of connection (Unlinked state), right-click the
Link icon and select Re-Link Parameter in order to refresh the fields
and/or re-establish the connection with the DCAS.

4.3.3 Configuring Call-by-Call CLIR at the VSAT

This section describes how to configure the call-by-call Call Line Identification
Restriction at the VSAT.

NOTE
Perform this procedure for each VSAT that will be using the call-by-call
CLIR feature.

To configure the call-by-call CLIR feature at the VSAT:

1. Click the VSATs View button.

Result: The VSATs View window is displayed.

2. Double-click the relevant VSAT icon.

Result: The VSAT Configuration window is displayed.

Native Telephony Features in

Version 5 37
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

Figure 30: VSAT Configuration

3. Click the Telephony tab.

Result: The VSAT Telephony parameters are displayed.

Figure 31: VSAT Telephony Parameters

4. In the Telephony tree view, click FXS Card Instances.

Native Telephony Features in

Version 5 38
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

Result: The FXS Card Instances are displayed.

Figure 32: FXS Card Instances

NOTE
CLIR configuration (see steps 5 - 8) must be performed for each port of
the VSAT FXS card.

5. Scroll to the right and click Open Element in the Ports column.

Result: The Port parameters are displayed.

6. Scroll to the CLIR parameters.

Figure 33: FXS Port Parameters – Call Forwarding and CLIR Parameters

7. Check the Restriction Enable option.

8. Set the User control parameter to Enable for Call-by-Call.

9. Click the Save button.

10. Click the Commit button.

Native Telephony Features in

Version 5 39
March, 2007
Proprietary and Confidential
 Native Telephony Features in Version 5.0P1

Result: The Reset the VSAT with Commit command confirmation window is
displayed.

11. Perform either of the following:

„ Click Yes to commit and reset the modified VSAT.

Or

„ Click No to commit the VSAT configuration without resetting the VSAT. For
information on how to reset a single or multiple VSATs, refer to Section 2.3.3.

NOTE
For the VSAT configuration changes to take effect, the VSAT must be
reset.

Native Telephony Features in

Version 5 40
March, 2007
Proprietary and Confidential