Chapters Download(878 KB)
Table of Contents
1.1.1 Introduction to Call Services
1.1.2 Call Interception Function
Chapter 2 Subscriber Management Service
2.1 Introduction to Subscriber Management Service
2.2 Subscriber Management Configuration
2.3.1 Configuration Requirements
Chapter 3 Emergency Call Service
3.1 Introduction to Emergency Call Service
3.2 Emergency Call Service Configuration
3.3.1 Configuration Requirements
Chapter 4 Inter-Group Call Restriction Service
4.1 Introduction to Inter-Group Call Restriction Service
4.2 Inter-Group Call Restriction Service Configuration
4.3.1 Configuration Requirements
Chapter 5 Outgoing Call Authority Control Service
5.1 Introduction to Outgoing Call Authority Control Service
5.1.3 Introduction to Outgoing Call Authority Control Service
5.2 Call Authority Control Service Configuration
5.3.1 Configuration Requirements
Chapter 6 Abbreviated Dialing Service
6.1.1 Introduction to Abbreviated Dialing Service
6.1.2 Using Abbreviated Dialing Service
6.2 Abbreviated Dialing Service Configuration
6.3.1 Configuration Requirements
Chapter 7 Do-Not-Disturb Service
7.1.1 Introduction to Do-Not-Disturb Service
7.1.2 Using Do-Not-Disturb Service
7.2 Do-Not-Disturb Service Configuration
7.2.1 Configuring Do-not-disturb Service
7.3.1 Configuration Requirements
Chapter 8 Calling Line Identification Services
8.1.3 Temporary Reservation for CLIR Service
8.2 Calling Line Identification Control Service Configuration
8.2.1 Configuring CLIP Service
8.2.2 Configuring CLIR Service
8.2.3 Configuring Temporary reservation for CLIR service
8.2.4 Configuring CLIR Override Service
8.3.1 Configuration Requirements
Chapter 9 Password Call Service
9.1.1 Introduction to Password Call Service
9.1.2 Using Password Call Service
9.2 Password Call Service Configuration
9.3.1 Configuration Requirements
Chapter 10 Call Forwarding Services
10.2.1 Introduction to CFU Service
10.2.3 Configuration Procedure
10.3.1 Introduction to CFC Service
10.3.3 Configuration Procedure
10.4.1 Introduction to CFT Service
10.4.2 Configuration Procedure
10.5.1 Introduction to CFO Service
10.5.3 Configuration Procedure
10.6.1 Introduction to CFB Service
10.6.3 Configuration Procedure
10.7.1 Introduction to CFNR Service
10.7.3 Configuration Procedure
Chapter 11 Third Party Call Termination Service
11.1.1 Introduction to Third Party Call Termination Service
11.2 Third Party Call Termination Service Configuration
11.2.1 Configuration Procedure
11.3.1 Configuration Requirements
11.3.3 Configuration Procedure
12.2 ONLY Service Configuration
12.2.1 Configuration Procedure
12.3.1 Configuration Requirements
Chapter 13 Time Limit Call Service
13.1.1 Introduction to Time Limit Call Service
13.1.2 Time Limit Call Mechanism
13.2 Time Limit Call Service Configuration
13.2.1 Configuration Procedure
13.3.1 Configuration Requirements
13.3.3 Configuration Procedure
Chapter 14 Third Party Call Control Service
14.1.1 Introduction to Third Party Call Control Service
14.1.2 Working Process of Third Party Call Control Service
14.2 Third Party Call Control Service Configuration
14.2.1 Configuration Procedure
14.3.1 Configuration Requirements
14.3.3 Configuration Procedure
Chapter 15 Callback-On-Busy Service
15.1.1 Introduction to Callback-On-Busy Service
15.1.3 Configuring and Using Callback-On-Busy Service
15.2 Callback-On-Busy Service Configuration
15.2.1 Setting Callback-On-Busy Parameters
15.2.2 Enabling/Disabling Callback-On-Busy Service
15.3.1 Configuration Requirements
15.3.3 Configuration Procedure
Chapter 16 Call Pickup Service
16.1.1 Introduction to Call Pickup Service
16.1.2 Using Call Pickup Service
16.2 Call Pickup Service Configuration
16.2.1 Configuration Procedure
16.3.1 Configuration Requirements
16.3.3 Configuration Procedure
Chapter 17 Call Intervention Service
17.1.1 Introduction to Call Intervention Service
17.1.2 Using Call Intervention Service
17.2 Call Intervention Service Configuration
17.2.1 Configuration Procedure
17.3.1 Configuration Requirements
17.3.3 Configuration Procedure
Chapter 18 Dialing Test Service
18.1.1 Introduction to Dialing Test Service
18.2 Using Dialing Test Service
18.3 Dialing Test Service Configuration
18.4.1 Configuration Requirements
18.4.3 Configuration Procedure
Chapter 19 Time Announcement Service
19.1.1 Introduction to Time Announcement Service
19.1.2 Using Time Announcement Service
19.2 Time Announcement Service Configuration
19.2.1 Enabling/Disabling Time Announcement Service
19.3.1 Configuration Requirements
19.3.3 Configuration Procedure
20.1.1 Introduction to MyRing Service
20.1.2 Configuring and Using MyRing Service
20.2 MyRing Service Configuration
20.2.1 Basic Configurations of MyRing Service
20.2.2 Configuring Caller Groups and Related Information
20.3.1 Configuration Requirements
20.3.3 Configuration Procedure
21.1.1 Introduction to CPCP Service
21.1.2 Configuring and Using CPCP Service
21.2 CPCP Service Configuration
21.2.1 Configuring CPCP Service
21.3.1 Configuration Requirements
21.3.3 Configuration Procedure
Chapter 22 Automatic Operator Service
22.1.1 Introduction to Automatic Operator Service
22.1.2 Features of Automatic Operator Service
22.1.3 Configuring and Using Automatic Operator Service
22.2 Automatic Operator Service Configuration
22.2.1 Configuration Procedure
22.3.1 Configuration Requirements
22.3.3 Configuration Procedure
Chapter 23 Group Notification Service
23.1.1 Introduction to Group Notification Service
23.1.2 Using Group Notification Service
23.2 Group Notification Service Configuration
23.2.1 Configuring Notification Receiver Group
23.2.2 Configuring Local Group Notification
23.2.3 Configuring Remote Group Notification
23.3.1 Configuration Requirements
23.3.3 Configuration Procedure
Chapter 24 Call Transfer Service
24.1.1 Introduction to Call Transfer Service
24.1.2 Using Call Transfer Service
24.2 Call Transfer Service Configuration
24.2.1 Enabling/Disabling Call Transfer Service
24.3.1 Configuration Requirements
24.3.3 Configuration Procedure
Chapter 25 Number Query Service
25.1.1 Introduction to Number Query Service
25.1.2 Configuring and Using Number Query Service
25.2 Number Query Service Configuration
25.2.1 Configuration Procedure
25.3.1 Configuration Requirements
25.3.3 Configuration Procedure
Chapter 26 Alarm Clock Service
26.1.1 Introduction to Alarm Clock Service
26.1.2 Configuring and Using Alarm Clock Service
26.2 Alarm Clock Service Configuration
26.2.1 Enabling/Disabling Alarm Clock Service for a Subscriber
26.2.2 Setting Alarm Clock Task through Command Lines on XE IP PBX
26.3.1 Configuration Requirements
26.3.3 Configuration Procedure
27.1 List of Access Codes for Different Call Services
27.2 Media IDs Reserved for Voice Prompts
27.3 Nested Relationship Between Two Call Services
Call services are implemented on H3C XE 200/2000 IP PBX (hereinafter referred to as the XE IP PBX). They include the following services.
l Subscriber Management Service
l Inter-Group Call Restriction Service (including the white and black groups)
l Outgoing Call Authority Control Service
l Calling Line Identification Services (CLIP, CLIR, temporary reservation for CLIR, CLIR override)
l Call Forwarding Services (CFU, CFC, CFT, CFO, CFB, and CFNR)
l Third Party Call Termination Service
l Third Party Call Control Service
This manual includes introduction to the above call services, and related command line configuration operations. The services can also be configured through GUIs (graphical user interfaces). Refer to H3C XE 200/2000 IP PBX G-Remote User Manual for more information.
& Note:
In this manual, call services are described with the precondition that involved telephone numbers are uniformly assigned on the XE IP PBX.
Enabling the media server, the XE IP PBX can provide subscribers with the call interception function. When a subscriber fails to use a voice service correctly or operate properly, like dialing a vacant or changed number, or meeting with a known route failure, the XE IP PBX can play the voice prompt to explain the further step or the related information.
The voice prompt, a media file recorded in advance, is saved and placed in the Flash in the recognizable format for the XE IP PBX. It defines a media resource ID, which is used to identify the media file to be broadcast, for each media file.
By default, the XE IP PBX defines reserved media resource IDs and their matching media files cannot be changed randomly. You must operate it with caution when change is really necessary, or the voice prompt will be in confusion. System reserved media resource IDs range from 0 to 10000. Subscribers can record their favorite media files to expand the service range, like service for customized rings. Note that the customized media resource ID must exceed 10000.
For details on system reserved media resource IDs, media file names and voice prompt content, refer to Media IDs Reserved for Voice Prompts.
Subscriber management service is used to manage subscribers and set call rights, including normal, forbid, callout and callin, for subscribers.
Table 2-1 Subscriber management functions
Subscriber management |
Right to call |
Right to be called |
Normal |
Yes |
Yes |
Forbid |
No |
No |
Callout |
Yes |
No |
Callin |
No |
Yes |
& Note:
Placing an emergency call is available anytime and anywhere.
According to the subscriber management service configuration of both parties (the caller and the callee), the XE IP PBX decides whether to allow the call setup in the call setup process.
Table 2-2 Configuring subscriber management
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-GW view. |
gateway device-id |
Required |
Enter subscriber number view. |
subscriber short-number long-number |
Required |
Enter subscriber management service view. |
sscb-manage |
Required |
Configure the subscriber status. |
subscriber-status { normal | callout | callin | forbid } |
Required |
l Configure subscriber 8801 under GW01 as the callin state so that only incoming calls are permitted.
l Configure subscriber 8802 under GW01 as the callout state so that only outgoing calls are permitted.
l Configure subscriber 8803 under GW01 as neither incoming nor outgoing calls are permitted.
Figure 2-1 Typical network diagram of the XE IP PBX
1) Configure basic parameters of the XE IP PBX.
# Configure the Ethernet interface.
<XE>system-view
System View: return to User View with Ctrl+Z.
[XE]interface GigabitEthernet 0/0
[XE-GigabitEthernet0/0]ip address 192.168.11.1 255.255.255.0
[XE-GigabitEthernet0/0]quit
[XE]
# Configure the process server (PS).
[XE]process-server
[XE-ps]ps-config gk interface GigabitEthernet 0/0
[XE-ps]ls-mode 0 local
[XE-ps]heartbeat password key0
[XE-ps]start
[XE-ps]quit
[XE]
# Configure the media server (MS).
[XE]media-server
[XE-ms]ms-config ms interface GigabitEthernet 0/0
[XE-ms]language Chinese
[XE-ms]heartbeat password key1
[XE-ms]ls-mode local
[XE-ms]start
[XE-ms]quit
[XE]
# Configure the location server (LS).
[XE]location-server
[XE-ls]ls-config interface GigabitEthernet 0/0
[XE-ls]start
[XE-ls]quit
[XE]
# Configure PS information under the LS.
[XE-ls]process-server gk
[XE-ls-ps-gk]heartbeat password key0
[XE-ls-ps-gk]quit
[XE-ls]quit
[XE]
# Configure parameters of MS under the LS.
[XE-ls]media-server ms
[XE-ls-ms-ms]language Chinese
[XE-ls-ms-ms]heartbeat password key1
# Configure media resource files.
[XE]media-ability
[XE-ma]language Chinese
[XE-ma-Chinese]format G711a
[XE-ma-Chinese-G711a]set-media 0 /g711wav/0.wav
[XE-ma-Chinese-G711a]set-media 1 /g711wav/1.wav
[XE-ma-Chinese-G711a]set-media 10 /g711wav/10.wav
...
& Note:
Before configuring media resource files, make sure that they were uploaded to the Flash memory of the XE IP PBX. For details about the uploading operations, refer to the “Media Server Operation” module of this manual. This example assumes that these files are located in the /g711wav directory of the Flash.
# Configure basic parameters of gateways GW01, GW02, and GW03 under the LS.
[XE]location-server
[XE-ls]gateway GW01
[XE-ls-gw-GW01]dynamic-ip enable
[XE-ls-gw-GW01]device-type h323
[XE-ls-gw-GW01]subscriber #1 8801
[XE-ls-gw-GW01 #1 8801]quit
[XE-ls-gw-GW01]quit
[XE-ls]gateway GW02
[XE-ls-gw-GW02]dynamic-ip enable
[XE-ls-gw-GW02]device-type h323
[XE-ls-gw-GW02]subscriber #1 8802
[XE-ls-gw-GW02 #1 8802]quit
[XE-ls-gw-GW02]quit
[XE-ls]gateway GW03
[XE-ls-gw-GW03]dynamic-ip enable
[XE-ls-gw-GW03]device-type h323
[XE-ls-gw-GW03]quit
[XE-ls]subscriber #1 8803
[XE-ls-gw-GW03 #1 8803]return
<XE>
1) Configure basic parameters of GW01.
# Configure the Ethernet interface.
[VG1]interface ethernet 0
[VG1-Ethernet0]ip address 192.168.11.2 255.255.255.0
[VG1-Ethernet0]quit
[VG1]
# Configure the voice entity.
[VG1]voice-setup
[VG1-voice]dial-program
[VG1-voice-dial]entity 8888 voip
[VG1-voice-dial-entity8888]address ras
[VG1-voice-dial-entity8888]match-template ....
[VG1-voice-dial-entity8888]fast-connect
[VG1-voice-dial-entity8888]outband h225
[VG1-voice-dial-entity8888]quit
[VG1-voice-dial]entity 1 pots
[VG1-voice-dial-entity1]line 1
[VG1-voice-dial-entity1]match-template #1
[VG1-voice-dial-entity1]outband h225
[VG1-voice-dial-entity1]return
<VG1>
# Configure the GK client.
<VG1>system
[VG1]voice-setup
[VG1-voice]gk-client
[VG1-voice-gk]gw-id GW01
[VG1-voice-gk]gw-address ip 192.168.11.2
[VG1-voice-gk]gk-id gk gk-addr 192.168.11.1 1719
[VG1-voice-gk]ras-on
2) Configure basic parameters of GW02 and GW03.
& Note:
Configurations of GW02 and GW03 similar to that of GW01, and therefore they are omitted here.
3) Configure service parameters on the XE IP PBX.
<XE>system-view
[XE]location-server
[XE-ls]gateway GW01
[XE-ls-gw-GW01]subscriber #1 8801
[XE-ls-gw-GW01 #1 8801]sscb-manage
[XE-ls-gw-GW01 #1 8801-ssbm]subscriber-status callin
[XE-ls-gw-GW01 #1 8801-ssbm]quit
[XE-ls-gw-GW01 #1 8801]quit
[XE-ls-gw-GW01]quit
[XE-ls]gateway GW02
[XE-ls-gw-GW02]subscriber #1 8802
[XE-ls-gw-GW02 #1 8802]sscb-manage
[XE-ls-gw-GW02 #1 8802-ssbm]subscriber-status callout
[XE-ls-gw-GW02 #1 8802-ssbm]quit
[XE-ls-gw-GW02 #1 8802]quit
[XE-ls-gw-GW02]quit
[XE-ls]gateway GW03
[XE-ls-gw- GW03]subscriber #1 8803
[XE-ls-gw- GW03#1 8803]sscb-manage
[XE-ls-gw- GW03#1 8803-ssbm]subscriber-status forbid
[XE-ls-gw- GW03#1 8803-ssbm]return
<XE>
Emergency call service enables subscribers to call emergency numbers, some well-known special numbers that the administrator configured on the XE IP PBX. In emergency situations, subscribers can call these numbers without limitation of other services. At present, the XE IP PBX supports up to 16 emergency numbers.
The administrator can configure emergency numbers in two ways:
l Specify some numbers as the emergency numbers directly.
l Configure an emergency number template.
All numbers that match the emergency template are emergency numbers. Emergency calls are made in the same way as common calls.
Only system administrators can configure the emergency call services. Subscribers cannot add or delete an emergency call number, but all of them can use this efficient service.
Table 3-1 Configure emergency call service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter emergency call service view. |
emergency-call |
— |
Add an emergency call number or an emergency call number template. |
emergency-call emergency-prefix |
Required |
& Note:
If you have configured and enabled the country code and area code on the XE IP PBX, you must configure a full number for an emergency call number including the country code and the area code.
Configure three emergency call numbers on the XE IP PBX: 119, 110, and 120.
& Note:
Refer to the network diagram in Network Diagram.
1) Configure basic parameters of the XE IP PBX.
2) Configure basic parameters of gateways GW01, GW02, and GW03.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
<XE>system-view
[XE]location-server
[XE-ls]emergency-call
[XE-ls-emgc]emergency-call-number 119
[XE-ls-emgc]emergency-call-number 110
[XE-ls-emgc]emergency-call-number 120
[XE-ls-emgc]return
<XE>
The XE IP PBX provides the inter-group call restriction service for easy management on call relationship between groups.
Call limit group is a logical concept. The administrator can define different groups and set call limit relationship between them.
Before subscribers utilize the call limit service, the administrator sets the limit groups for the two parties. After the setting, the XE IP PBX decides whether to allow the setup according to the call limit relationship between groups that the caller and callee belong to.
The call limit relationship between groups is unidirectional. By default, any two common call limit groups can make calls to each other.
By default, there is one black group, a white group and a default common group, named black-table, white-table and normal-table respectively. The default common group and groups defined by the administrator are all common groups. Any subscriber number and route number which are not covered in the black group, the white group or any other group defined by the administrator go into the default common group (normal-table). You cannot change the call limit relationship between the three groups. The call limit relationship is shown in Table 4-1.
Table 4-1 Call limit relationship between common groups, the white group and the black group
Caller group Called group |
Black-table |
White-table |
Normal-table |
Black-table |
N |
Y |
N |
White-table |
N |
Y |
Y |
Normal-table |
N |
Y |
Y |
In Table 4-1, N means no calls are permitted and Y means calls are permitted.
& Note:
A number in a black group can dial any emergency call number, and can be called by any number when it is set as an emergency call number.
Table 4-2 Configure the inter-group call restriction service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter call limit group view. |
call-limit-group |
— |
Create a call limit group. |
limited-group call-limit-group-name |
Required |
Change the name of a call limit group. |
change old-group-name new-group-name |
Optional |
Set call limit relationship between groups. |
forbid src-call-limit-group call dst-call-limit-group |
Required |
Exit call limit group view. |
quit |
— |
Enter LS-GW view. |
gateway device-id |
Required |
Enter subscriber number view. |
subscriber short-number long-number |
Required |
Enter call limit group service view. |
limited-call-group |
— |
Add a subscriber to a call limit group. |
limited-call-group limited-call-group |
Required |
Exit call limit group view. |
quit |
— |
Enable/disable the call limit group service. |
srv-switch group-limited-call {on | off |
Required |
l Define two call limit groups named private-group and public-group respectively.
l Set the call limit relationship to allow subscribers in private-group make calls to subscribers in public-group and forbid subscribers in the latter make calls to subscribers in the former.
l Add subscriber 8801 under GW01 into private-group and subscriber 8802 under GW01 into public-group.
l Enable the call limit group service.
& Note:
Refer to the network diagram in Network Diagram.
1) Configure basic parameters of the XE IP PBX.
2) Configure basic parameters of gateways GW01, GW02, and GW03.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
# Define call limit groups: private-group and public-group.
<XE>system-view
[XE]location-server
[XE-ls]call-limit-group
[XE-ls-clg]limited-group private-group
[XE-ls-clg]limited-group public-group
# Set call limit relationship between the two groups.
[XE-ls-clg]forbid public-group call private-group
# Add the subscriber number 8801 to the corresponding group.
[XE-ls-clg]quit
[XE-ls]gateway GW01
[XE-ls-gw-GW01]subscriber #1 8801
[XE-ls-gw-GW01 #1 8801]limited-call-group
[XE-ls-gw-GW01 #1 8801-lcg]limited-call-group private-group
[XE-ls-gw-GW01 #1 8801-lcg]quit
[XE-ls-gw-GW01 #1 8801]quit
# Enable the inter-group call restriction service.
[XE-ls-gw-GW01 #1 8801]srv-switch group-limited-call on
[XE-ls-gw-GW01 #1 8801]quit
[XE-ls-gw-GW01]quit
# Add the subscriber number 8802 to the corresponding group
[XE-ls]gateway GW02
[XE-ls-gw-GW02]subscriber #1 8802
[XE-ls-gw-GW02 #1 8802]limited-call-group
[XE-ls-gw-GW02 #1 8802-lcg]limited-call-group public-group
[XE-ls-gw-GW02 #1 8802-lcg]quit
# Enable the inter-group call restriction service.
[XE-ls-gw-GW02 #1 8802]srv-switch group-limited-call on
[XE-ls-gw-GW02 #1 8802]return
<XE>
Numbers with the same characteristics belong to the same type. Number characteristics are described by the administrator through defining regular expressions. Note that a number matching any regular expression of a subscriber type belongs to this type.
One subscriber type can be configured with 16 regular expressions at most. The administrator should make sure that the regular expressions configured for different subscriber types do not conflict with each other.
Subscribers are defined as different roles for outgoing call right assignment. Each role supports one or more available subscriber types. That is, a role can make calls to subscriber numbers that belong to any of these types.
The XE IP PBX reserves a role named default, which cannot be deleted but can be added with supported subscriber types.
One subscriber role can support up to 8 subscriber types.
By defining subscriber roles, outgoing call authority control service decides subscribers’ rights to make outgoing calls. Only the administrator can set subscriber roles. Subscribers have no right for this operation.
After a subscriber is assigned a role by the administrator, its call rights is determined as follows:
l If a number belongs to a subscriber type supported by the subscriber’s role, it is allowed to be called.
l If a number does not belong to any subscriber type supported by the subscriber’s role, it is denied to be called.
l If a number does not belong to any number type, it is also allowed to be called.
In the context of call authority, relationship between the subscriber, subscriber role and number types is shown in Figure 5-1.
Figure 5-1 Relationship between subscriber, subscriber role and number types
In Figure 5-1, subscriber role A supports number types a, b and c. Subscriber 1001 is defined as role A. In this case, subscriber 1001 can only make calls to numbers that belongs to types a, b or c, and numbers with no type.
& Note:
Subscribers that are not defined with a role explicitly belong to the default role.
Table 5-1 Configure subscriber type
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Create a subscriber type and enter subscriber type view. |
subscriber-type subscriber-type-name |
Required |
Configure regular expressions that match this type. |
type prefix |
Required |
Query all or specified subscriber types in the system. |
display location-server subscriber-type [ subscriber-type ] |
Optional |
At most 8 subscriber types can be configured.
Each type can be configured with 16 regular expressions at most.
Table 5-2 Configure roles
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Create a subscriber role and enter subscriber role view. |
subscriber-role role |
Required |
Add subscriber types that can be called by this role. |
subscriber-type subscriber-type-name |
Required |
Query all or specified subscriber roles in the system. |
display location-server subscriber-role { role | all } |
Optional |
At most 64 roles can be configured.
Table 5-3 Configure subscriber role
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-GW view. |
gateway device-id |
Required |
Enter subscriber number view. |
subscriber short-number long-number |
Required |
Enter outgoing call authority control service view. |
cba |
— |
Configure a role for the subscriber. |
subscriber-role role |
Required |
Table 5-4 Enable/disable the outgoing call authority control service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-GW view. |
gateway device-id |
Required |
Enter subscriber number view. |
subscriber short-number long-number |
Required |
Enable/disable the outgoing authority control service. |
srv-switch cba { on | off } |
Required The outgoing authority control service is enabled by default. |
l Create a subscriber type t1001, which matches the regular expression 1001. That is, all numbers beginning with 1001 belong to this type.
l Create a subscriber type t1002, which matches the regular expression 1002. That is, all numbers beginning with 1002 belong to this type.
l Create a subscriber role r1001, which can call numbers of the t1001 type.
l Create a subscriber role r1002, which can call numbers of the t1002 type.
l Set subscriber 1000 as role r1001 and enable the outgoing call authority control service for it.
& Note:
In the above case, subscriber 1000 can make calls to any number except those begin with 1002.
1) Configure basic parameters of the XE IP PBX.
2) Configure gateway basic parameters.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
# Configure subscriber types: t1001 and t1002.
[XE-ls]subscriber-type t1001
[XE-ls-ssbt-t1001]type 1001
[XE-ls-ssbt-t1001]quit
[XE-ls]subscriber-type t1002
[XE-ls-ssbt-t1002]type 1002
[XE-ls-ssbt-t1002]quit
# Configure subscriber roles: r1001 and r1002.
[XE-ls]subscriber-role r1001
[XE-ls-ssbr-r1001]subscriber-type t1001
[XE-ls-ssbr-r1001]quit
[XE-ls]subscriber-role r1002
[XE-ls-ssbr-r1002]subscriber-type t1002
[XE-ls-ssbr-r1002]quit
# Specify subscriber 1000 as role r1001.
[XE-ls]gateway gw01
[XE-ls-gw-gw01]subscriber #1 1000
[XE-ls-gw-gw01 #1 1000]cba
[XE-ls-gw-gw01 #1 1000-cba]subscriber-role r1001
[XE-ls-gw-gw01 #1 1000-cba]quit
# Enable the outgoing authority control service for subscriber 1000.
[XE-ls-gw-gw01 #1 1000]srv-switch cba on
Abbreviated dialing service uses two-digit abbreviated numbers to replace specified called numbers for easy dialing. To call a specified number, a subscriber only needs to dial “**” plus the corresponding two-digit abbreviated number. The called number can be a local number or long-distance call number.
One subscriber can configure 10 abbreviated numbers at most.
Abbreviated numbers are used in two ways:
l Common abbreviated dialing
The entire called number is represented by an abbreviated number. You only need to dial “**” plus the abbreviated number to make a call.
l Open abbreviated dialing
Part of the called number is represented by an abbreviated number. You need to dial “**” plus the abbreviated number plus the remaining digits of the called number to make a call.
& Note:
In this chapter, the character string “ABCDEFGH” represents the called number and MN the abbreviated number. Each character in the string can be a digit 0 through 9, A, B, C, D, *, or # on the telephone.
The following table describes the difference between the two abbreviated dialing methods.
Table 6-1 Difference between two abbreviated dialing methods
|
Configuration method |
Dialing method |
Common abbreviated dialing. |
Specify an abbreviated number MN to represent the called number ABCDEFGH. |
Directly dial “**” plus MN. |
Open abbreviated dialing. |
Specify an abbreviated number MN to represent ABCD, part of the called number ABCDEFGH. |
Dial “**” plus MNEFGH. |
Follow the two methods below to set the abbreviated dialing table.
l The administrator can configure the abbreviated dialing table on the XE IP PBX through command lines. Refer to 6.2 “Abbreviated Dialing Service Configuration”.
l The subscriber can configure the abbreviated dialing table on their telephone sets as follows:
The following table describes how to add an abbreviated dialing item. If the specified abbreviated number MN exists, the following operation will delete it and add a new abbreviated number item.
Table 6-2 Add an abbreviated number item
Step |
Expected result |
Pick up the phone. |
The subscriber can hear the dial tone. |
Dial *51*MN*ABCDEFGH#. |
The subscriber can hear the ringback tone or the voice prompt “You have already activated the service.” If you fail, you will hear a busy tone or the voice prompt “Sorry, your attempt to activate the service was unsuccessful.” |
Hang up the phone. |
— |
& Note:
To make services whose access codes include * or # work properly, you should not specify on the gateway these two characters to act as dialing terminators.
The following table describes how to delete an abbreviated dialing item.
Table 6-3 Delete an item from the abbreviated dialing table
Step |
Expected result |
Pick up the phone. |
The subscriber can hear the dial tone. |
Dial #51#. |
The subscriber can hear the ringback tone or the voice prompt “You have deactivated the service.” If you fail, you will hear the busy tone or the voice prompt “Sorry, your attempt to deactivate the service was unsuccessful”. |
Hang up the phone. |
— |
Caution:
Be cautious about your deletion, for all the numbers in the abbreviated dialing table will be deleted by this operation.
The following table describes how to perform common abbreviated dialing.
Table 6-4 Common abbreviated dialing
Step |
Expected result |
Pick up the phone. |
The subscriber can hear the dial tone. |
Dial “**” plus MN. |
The subscriber can hear the ringback tone. |
Wait for the callee to pick up the phone. |
— |
The following table describes how to use open abbreviated dialing.
Table 6-5 Open abbreviated dialing
Step |
Expected result |
Pick up the phone. |
The subscriber can hear the dial tone. |
Dial “**” plus MN + EFGH. |
The subscriber can hear the ringback tone. |
Wait for the callee to pick up the phone. |
— |
Table 6-6 Configure abbreviated dialing service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-GW view. |
gateway device-id |
Required |
Enter subscriber number view. |
subscriber short-number long-number |
Required |
Enter abbreviated dialing service view. |
adi |
— |
Add an item to the abbreviated dialing table. |
adi ab-number long-number |
Required |
Exit the abbreviated dialing service view |
quit |
— |
Enable/disable the abbreviated dialing service. |
srv-switch adi { on | off } |
Required The abbreviated dialing service is enabled by default. |
Configure two abbreviated dialing numbers for subscriber 8801 under GW01: number 22 representing subscriber 8802 and 33 representing subscriber 8803.
Refer to the network diagram in Network Diagram.
1) Configure basic parameters of the XE IP PBX.
2) Configure basic parameters of gateways GW01, GW02, and GW03.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
<XE>system-view
[XE]location-server
[XE-ls]gateway GW01
[XE-ls-gw-GW01]subscriber #1 8801
[XE-ls-gw-GW01 #1 8801]srv-switch adi on
[XE-ls-gw-GW01 #1 8801]adi
[XE-ls-gw-GW01 #1 8801-adi]adi 22 8802
[XE-ls-gw-GW01 #1 8801-adi]adi 33 8803
The do-not-disturb service is used to refuse incoming calls temporarily. A subscriber can register for the do-not-disturb service to deny all incoming calls while making outgoing calls freely.
To allow subscribers to register the do-not-disturb service, the administrator need enable the service on the XE IP PBX for the subscribers first.
There are two ways to set the do-not-disturb service.
l By the operator who performs configuration on the XE IP PBX through the command line. For detailed configuration, refer to the Configuring Do-not-disturb Service.
l By the phone user who sets up the service on the phone, as described in the following table.
Table 7-1 Register do-not-disturb service
Step |
Expected result |
Pick up the phone. |
The subscriber can hear the dial tone. |
Dial *56#. |
If the do-not-disturb service is enabled, the subscriber can hear ringback tone or the voice prompt “You have successfully activated the service”, indicating the service registration succeeded. If the do-not-disturb service is disabled, the subscriber can hear busy tone or the voice prompt “Sorry, you have not activated the service", which indicating the service registration failed. |
Hang up the phone. |
— |
The following table describes how to deregister the do-not-disturb service.
Table 7-2 Deregister do-not-disturb service
Step |
Expected result |
Pick up the phone. |
The subscriber can hear the dial tone. |
Dial #56#. |
If the do-not-disturb service is registered, the subscriber can hear the ringback tone or the voice prompt “You have deactivated the service”, which indicating the service deregistration succeeded. If the do-not-disturb service is not registered or is disabled, the subscriber can hear busy tone or the voice prompt “Sorry, you have not activated the service.” |
Hang up the phone. |
— |
Table 7-3 Enable/disable do-not-disturb service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-GW view. |
gateway device-id |
Required |
Enter subscriber number view. |
subscriber short-number long-number |
Required |
Enable/disable do-not-disturb service. |
srv-switch do-not-disturb { on | off } |
Required |
Enter do-not-disturb view. |
dnd |
Required |
Activate the do-not-disturb service for a subscriber. |
do-not-disturb open |
Required |
Enable the do-not-disturb service for subscriber 8801 under GW01.
& Note:
Refer to the network diagram in Network Diagram.
1) Configure basic parameters on the XE IP PBX.
2) Configure basic parameters of gateways GW01, GW02, and GW03.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
<XE>system-view
[XE]location-server
[XE-ls]gateway GW01
[XE-ls-gw-GW01 #1 8801]srv-switch do-not-disturb on
[XE-ls-gw-GW01 #1 8801]dnd
[XE-ls-gw-GW01 #1 8801-dnd]do-not-disturb open
The calling line identification control services are used to control whether to display the caller’s number on the callee’s phone set.
The services include:
l Calling line identification presentation (CLIP) service
l Calling line identification restriction (CLIR)service
l Temporary reservation for CLIR service
l CLIR override service
After a subscriber enables the CLIP service, the incoming call numbers are displayed on its phone.
By default, the CLIP service is enabled for a subscriber. But if the service is disabled, nothing or 00000000 is displayed on the telephone set of the subscriber for an incoming call.
If the callee enables the CLIP service, while the caller enables the CLIR service at the same time, still nothing or 00000000 will be displayed on the telephone set of the callee.
CLIR service can block caller numbers from being displayed on called telephone sets.
By default, the CLIR service is disabled for a subscriber.
If the caller enables and registers the CLIR service, but the callee enables the CLIR override service at the same time, the caller number will be displayed on the telephone set of the callee.
After enabling the CLIR service, a subscriber can register the service in the following two methods.
l The administrator performs the registration on the XE IP PBX through command lines. Refer to 8.2.1 “Configuring CLIP Service” for details.
l The subscriber can perform the registration on the telephone set by following the steps below.
Table 8-1 Register CLIR service on telephone sets
Step |
Expected result |
Pick up the phone. |
The subscriber can hear the dial tone. |
Dial *61#. |
If CLIR service is enabled, the subscriber will hear the ringback tone or the voice prompt “You have successfully activated the service.” If not, the subscriber will hear the busy tone or the voice prompt “Sorry, you have not activated the service.” |
Hang up the phone. |
— |
The following table describes how to use the CLIR service.
Step |
Expected result |
Pick up the phone. |
The subscriber can hear the dial tone. |
Dial the number. |
The subscriber can hear the ringback tone. The called telephone rings and does not display the caller number. |
Wait for the call to begin. |
— |
The following table describes how to deregister the CLIR service.
Table 8-3 Deregister CLIR service
Step |
Expected result |
Pick up the phone. |
The subscriber can hear the dial tone. |
Dial #61#. |
If the deregistration is successful, the subscriber can hear the ringback tone or the voice prompt “You have deactivated the service.” If not successful, the subscriber hears the busy tone or the voice prompt “Sorry, your attempt to deactivate the service was unsuccessful.” |
Hang up the phone. |
— |
Besides the CLIR service, the caller can also use the temporary reservation for CLIR service to hide its number during calls.
After enabling the temporary reservation for CLIR service, the caller can dial *62# plus the called number to hide its number to a specific callee.
By default, the temporary reservation for CLIR service is disabled.
If the caller enables the temporary reservation for CLIR service, but the callee enables the CLIR override service at the same time, the caller number will be displayed on the telephone set of the callee.
Table 8-4 Use temporary reservation for CLIR service
Step |
Expected result |
Pick up the phone. |
The subscriber can hear the dial tone. |
Dial *62# plus the called number. |
If temporary reservation for CLIR service is enabled, the subscriber will hear the ringback tone and the caller number is not displayed at the callee. If not, the subscriber will hear the busy tone or the voice prompt “Sorry, the subscriber you dial does not exist.” |
Wait for the call to begin. |
— |
After a called telephone set is enabled with the CLIR override service, caller numbers are displayed on it unconditionally.
The CLIR override service has precedence over the CLIP and temporary CLIP services.
Table 8-5 Configure CLIP service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-GW view. |
gateway device-id |
Required |
Enter subscriber number view. |
subscriber short-number long-number |
Required |
Enable/disable the CLIP service. |
srv-switch clip { on | off } |
Required |
Table 8-6 Configure CLIR service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-GW view. |
gateway device-id |
Required |
Enter subscriber number view. |
subscriber short-number long-number |
Required |
Enable/disable the CLIR service. |
srv-switch clir { on | off } |
Required |
Enter CLIR service view. |
clir |
Optional |
Register/deregister the CLIR service. |
clir { disable | enable } |
Optional The subscriber can also use their telephone sets to register/deregister the CLIR service. |
Table 8-7 Configure the temporary reservation for CLIR service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-GW view. |
gateway device-id |
Required |
Enter subscriber number view. |
subscriber short-number long-number |
Required |
Enable/disable the temporary reservation for CLIR service. |
srv-switch tcir { on | off } |
Required |
Table 8-8 Configure CLIR override service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-GW view. |
gateway device-id |
Required |
Enter subscriber number view. |
subscriber short-number long-number |
Required |
Enable/disable the CLIR override service. |
srv-switch rio { on | off } |
Required |
Enable the CLIR service for subscriber 8801 under GW01.
Enable the temporary reservation for CLIR service for subscriber 8802 under GW02.
Enable the CLIR override service for subscriber 8803 under GW03.
& Note:
Refer to the network diagram in Network Diagram.
1) Configure basic parameters on the XE IP PBX.
2) Configure basic parameters of gateways GW01, GW02, and GW03.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
<XE>system-view
[XE]location-server
[XE-ls]gateway GW01
[XE-ls-gw-GW01]subscriber #1 8801
[XE-ls-gw-GW01 #1 8801]srv-switch clir on
[XE-ls-gw-GW01 #1 8801]clir
[XE-ls-gw-GW01 #1 8801-clir]clir enable
[XE-ls-gw-GW01 #1 8801-clir]quit
[XE-ls-gw-GW01 #1 8801]quit
[XE-ls-gw-GW01]quit
[XE-ls]gateway GW02
[XE-ls-gw-GW02]subscriber #1 8802
[XE-ls-gw-GW02 #1 8802]srv-switch tcir on
[XE-ls-gw-GW02 #1 8802]quit
[XE-ls-gw-GW02]quit
[XE-ls]gateway GW03
[XE-ls-gw-GW03]subscriber #1 8803
[XE-ls-gw-GW03 #1 8803]srv-switch rio on
[XE-ls-gw-GW03 #1 8803]return
<XE>
To prevent illegal use of telephone sets, subscribers can set call passwords for their telephone sets. Anyone who uses such a telephone set must first input the correct password.
Two methods are available for call password modification.
l The administrator can modify the password on the XE through command lines. Refer to 9.2.1 “Configuration Procedure” for details.
l The subscriber can modify the password on the telephone set as follows.
Table 9-1 Modify the password on the telephone set
Step |
Expected result |
Pick up the phone. |
The subscriber can hear the dial tone. |
Dial *541*ABCD*WXYZ*WXYZ#. |
If the password call service is not enabled, the voice prompt will say: “Sorry, you have not activated the service.” If the password call service is enabled and the original password ABCD is correct, the subscriber can hear the voice prompt “You have successfully activated the service”, indicating the password is modified successfully. If the subscriber hears “Sorry, your attempt to activate the service was unsuccessful”, indicating the modification fails. ABCD stands for the original call password and WXYZ for the new one. The original password set for a subscriber is 1234. The call password is made up of a combination of 0 to 9, A, B, C and D, not more than 8 digits. |
Hang up the phone. |
— |
& Note:
If the voice prompt service is not supported by the system, you are recommended to pay attention to the rings. Busy tone indicates the failure operation, while the ringback tone indicates successful operation.
The following table describes how to make password calls.
Step |
Expected result |
Pick up the phone. |
The subscriber can hear the dial tone. |
Dial ABCD plus the called number. |
ABCD stands for the call password. If the call password is correct, the call succeeds and the subscriber can hear the ringback tone. If not, the call fails and the subscriber will hear the busy tone or the voice prompt “Sorry, the password is not correct.” |
& Note:
Some subscribers need to add dialing terminator # to the end of the called number. That is, these subscribers need to dial ABCD, the called number and # to initiate a password call.
Table 9-3 Configure password call service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-GW view. |
gateway device-id |
Required |
Enter subscriber number view. |
subscriber short-number long-number |
Required |
Enable/disable the password call service. |
srv-switch pwd-call { on | off } |
Required |
Set the call password. |
pwd-call-password password |
Optional This step can be skipped and the call password defaults to 1234. |
Enable the password call service for subscriber 8801 under GW01, with the password being 123456.
& Note:
Refer to the network diagram in Network Diagram.
1) Configure basic parameters on the XE IP PBX.
2) Configure basic parameters of gateways GW01, GW02, and GW03.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
<XE>system-view
[XE]location-server
[XE-ls]gateway GW01
[XE-ls-gw-GW01]subscriber #1 8801
[XE-ls-gw-GW01 #1 8801]srv-switch pwd-call on
[XE-ls-gw-GW01 #1 8801]pwd-call-password 123456
[XE-ls-gw-GW01 #1 8801]return
<XE>
With the call forwarding services, the XE IP PBX forwards calls to numbers (not the called number) pre-specified by the callee when specific conditions are satisfied. The forwarding process is invisible to the caller.
Call forwarding can be implemented in the following six services, listed in the sequence of priority from high to low.
l Call forwarding offline (CFO)
l Call forwarding based on the caller number (CFC)
l Call forwarding based on time range (CFT)
l Call forwarding unconditional (CFU)
l Call forwarding on busy (CFB)
l Call forwarding no reply (CFNR)
If subscriber C makes a call to subscriber A, who sets subscriber B as the call target forwarding and subscriber B enables the CLIP service, the number of subscriber C will be displayed on the telephone set of subscriber B.
If a subscriber enables the call forwarding service and do-not-disturb service at the same time, the latter enjoys the higher priority to take effect.
& Note:
l For CFO, CFC, CFT and CFU, if the subscriber sets multiple target numbers, all telephone sets that correspond to these numbers will ring in descending order of priority level when call forwarding occurs. Telephone sets whose numbers have the same priority level will ring at random if the function of random number selection is enabled, and will ring simultaneously if the function is disabled. After one of these telephone sets is picked up, the others stop ringing.
l For CFB and CFNR, if the subscriber sets multiple target numbers, the call will be forwarded to the number with the highest priority level.
l Target numbers should be of the same type with the current subscriber number. Otherwise, the call forwarding fails. The subscriber’s number itself cannot be set to the target number for direct or indirect call forwarding.
l Target numbers must not be a call notification access code, automatic operator access code, or special service number.
l By default, the XE IP PBX provides all call forwarding services for subscribers.
With the CFU service, all incoming calls are forwarded to the target number preset by the callee, and the telephone set of the callee does not ring. Up to two forwarded-to numbers can be set by the callee.
After the administrator enables the CFU service for a subscriber, target forwarding numbers can be set by the following two methods.
l The administrator can set the number on the XE IP PBX through command lines. Refer to 10.2.3 “Configuration Procedure” for details.
l The subscriber can set the number on the telephone set as follows:
The following table describes how to set the CFU target number on the telephone set.
Table 10-1 Set CFU target number on the telephone set
Step |
Expected result |
Pick up the phone. |
The subscriber can hear the dial tone. |
Dial *57*, the target forwarding number and # in sequence. |
If the setting succeeds, the subscriber can hear the ringback tone or the voice prompt “You have successfully activated the service.” If the setting fails, the subscriber will hear the busy tone or the voice prompt “Sorry, your attempt to activate the service was unsuccessful.” |
Hang up the phone. |
— |
The following table describes how to verify the CFU target number, that is, to check whether a specified number is set as the CFU target number on the telephone set.
Table 10-2 Check specified CFU target number on the telephone set
Step |
Expected result |
Pick up the phone. |
The subscriber can hear the dial tone. |
Dial *#57*. |
If the specified number is set as the target number, the subscriber can hear the ringback tone or the voice prompt “You have already activated call forwarding unconditional service. Your forward number is XXXX”. (XXXX refers to the number the subscriber set).If not target number is set, the subscriber will hear the busy tone or the voice prompt “Sorry, your attempt to activate the service was unsuccessful.” If the CFU service is not enabled, the subscriber will hear the busy tone or the voice prompt “Sorry, your attempt to activate the service was unsuccessful.” |
Hang up the phone. |
— |
The following table describes how to delete the CFU forwarding number.
Table 10-3 Delete all CFU forwarding numbers on the telephone set
Step |
Expected result |
Pick up the phone. |
The subscriber can hear the dial tone. |
Dial #57#. |
If target numbers are deleted, the subscriber can hear the ringback tone or the voice prompt “You have deactivated the service.” If no target number is available for deletion, the subscriber will hear the busy tone or the voice prompt “Sorry, the service is not available.” |
Hang up the phone. |
— |
Caution:
Be cautious about the deletion, for all the CFU forwarding numbers will be deleted by this operation.
Table 10-4 Configure CFU service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-GW view. |
gateway device-id |
Required |
Enter the subscriber number view. |
subscriber short-number long-number |
Required |
Enter CFU service view. |
cfu |
— |
Add target numbers for CFU forwarding. |
cfu-number forward-number |
Required |
Exit CFU service view. |
quit |
— |
Enable/disable the CFU service. |
srv-switch cfu {on | off } |
Required |
Enable the CFU service for subscriber 8801 under GW01, with the target number being 8802.
& Note:
Refer to the network diagram in Network Diagram.
1) Configure basic parameters on the XE IP PBX.
2) Configure basic parameters of gateways GW01, GW02, and GW03.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
<XE>system-view
[XE]location-server
[XE-ls]gateway GW01
[XE-ls-gw-GW01]subscriber #1 8801
[XE-ls-gw-GW01 #1 8801]cfu
[XE-ls-gw-GW01 #1 8801-cfu]cfu-number 8802
[XE-ls-gw-GW01 #1 8801-cfu]quit
[XE-ls-gw-GW01 #1 8801]srv-switch cfu on
[XE-ls-gw-GW01 #1 8801]return
<XE>
CFC is an extension of the CFU service. It forwards calls to different target numbers according to the caller numbers. Calls without any target number from callers will not be forwarded. Up to 5 CFC forward numbers can be set by the subscribers.
After the administrator enables the CFC service for a subscriber, two methods can be used for CFC configuration.
l The administrator can configure CFC items on the XE IP PBX through command lines. Refer to 10.3.3 “Configuration Procedure” for details.
l The subscriber can configure CFC items on their telephone sets as follows:
The following table describes how to set the CFC target number on the telephone set.
Table 10-5 Set CFC target number on the telephone set
Step |
Expected result |
Pick up the phone. |
The subscriber can hear the dial tone. |
Dial *47*, caller number, *, target number and # in sequence. |
If the setting succeeds, the subscriber can hear the ringback tone or the voice prompt “You have successfully activated the service.” If the setting fails, the subscriber will hear the busy tone or the voice prompt “Sorry, your attempt to activate the service was unsuccessfully.” If the service is not enabled, you will hear the busy tone or the voice prompt “Sorry, the service is not available.” |
Hang up the phone. |
— |
The following table describes how to verify the CFC target number on the telephone set.
Table 10-6 Verify the CFC target number on the telephone set
Step |
Expected result |
Pick up the phone. |
The subscriber can hear the dial tone. |
Dial #47#. |
If there is a target number being set, the subscriber can hear the ringback tone or the voice prompt “The CFC target number you have set is xxxxx” (xxxx is the target number being set). If there is no target number being set, the subscriber will hear the busy tone or the voice prompt “You have not set any target number.” |
Hang up the phone. |
— |
The following table describes how to delete the CFC item on the telephone set.
Table 10-7 Delete CFC items on the telephone set
Step |
Expected result |
Pick up the phone. |
The subscriber can hear the dial tone. |
Dial #47#, caller number and # in sequence. |
If the deletion succeeds, the subscriber can hear the ringback tone or the voice prompt “You have deactivated the service.” If no target forwarding item is available for deleting, the subscriber will hear the busy tone or the voice prompt “Sorry, your attempt to deactivate the service was unsuccessful.” |
Hang up the phone. |
— |
Caution:
Be cautious about the deletion, for all the CFC forwarding numbers will be deleted by the operation.
Table 10-8 Configure CFC service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-GW view. |
gateway device-id |
Required |
Enter the subscriber number view. |
subscriber short-number long-number |
Required |
Enter CFC service view. |
cfc |
— |
Add CFC forwarding items. |
cf-caller caller-number forward-number |
Required |
Exit CFC service view. |
quit |
— |
Enable/disable the CFC service. |
srv-switch cf-caller {on | off } |
Required |
Enable the CFC service for subscriber 8801 under GW01, with the target number being 8803 when the caller is 8802.
& Note:
Refer to the network diagram in Network Diagram.
1) Configure basic parameters on the XE IP PBX.
2) Configure basic parameters of gateways GW01, GW02, and GW03.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
<XE>system-view
[XE]location-server
[XE-ls]gateway GW01
[XE-ls-gw-GW01]subscriber #1 8801
[XE-ls-gw-GW01 #1 8801]cfc
[XE-ls-gw-GW01 #1 8801-cfc]cf-caller 8802 8803
[XE-ls-gw-GW01 #1 8801-cfc]quit
[XE-ls-gw-GW01 #1 8801]srv-switch cf-caller on
[XE-ls-gw-GW01 #1 8801]return
<XE>
With the CFT service, all incoming calls during specific time ranges are forwarded to the target number pre-specified by the callee. Calls that beyond the time ranges will not be forwarded.
A time range is defined by the start time and end time and cannot be across the midnight. The end time must be later than the start time. One subscriber can set 5 time ranges at most, with any one of which cannot be overlapped. Up to 5 CFT forward numbers can be set by the subscriber.
CFT service can only be set by the administrator on the XE IP PBX. Subscribers cannot set it on the telephone set.
Table 10-9 Configure CFT service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-GW view. |
gateway device-id |
Required |
Enter subscriber number view. |
subscriber short-number long-number |
Required |
Enter CFT service view. |
cft |
— |
Add CFT forwarding items. |
cft start-time stop-time forward-number |
Required The start-time and stop-time arguments are in the form of hh:mm:ss. |
Exit CFT service view. |
quit |
— |
Enable/disable the CFT service. |
srv-switch cft {on | off } |
Required |
Enable the CFT service for subscriber 8801 under GW01, with the target number being 8802 and the time range being 12:00:00 to 16:00:00.
& Note:
Refer to the network diagram in Network Diagram.
1) Configure basic parameters on the XE IP PBX.
2) Configure basic parameters of gateways GW01, GW02, and GW03.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
<XE>system-view
[XE]location-server
[XE-ls]gateway GW01
[XE-ls-gw-GW01]subscriber #1 8801
[XE-ls-gw-GW01 #1 8801]cft
[XE-ls-gw-GW01 #1 8801-cft]cft 12:00:00 16:00:00 8802
[XE-ls-gw-GW01 #1 8801-cft]quit
[XE-ls-gw-GW01 #1 8801]srv-switch cft on
[XE-ls-gw-GW01 #1 8801]return
<XE>
CFO is an extension of the CFU service. Calls to a subscriber who enables the CFO service will be forwarded to specified target numbers, if the gateway used by this subscriber is offline. However, if the gateway is online, calls will not be forwarded. Up to 2 CFO forward numbers can be set by the subscriber.
The CFO service becomes ineffective when the gateway used by the callee is set to always online. That is, the XE IP PBX will not perform CFO service no matter the gateway is actually online or not.
After the administrator enables the CFO service for a subscriber, two methods can be used to set CFO target numbers.
l The administrator can configure CFO target numbers on the XE IP PBX through command lines. Refer to 10.5.3 “Configuration Procedure" for details.
l The subscriber can configure CFO target numbers on their telephone sets as follows:
The following table describes how to set CFO target number on the telephone set.
Table 10-10 Set CFO target number on the telephone set
Step |
Expected result |
Pick up the phone. |
The subscriber can hear the dial tone. |
Dial *45*, target number and # in sequence. |
If the setting succeeds, the subscriber can hear the ringback tone or the voice prompt “You have successfully activated the service.” If the setting fails, the subscriber will hear the busy tone or the voice prompt “Sorry, your attempt to activate the service was unsuccessful.” |
Hang up the phone. |
— |
The following table describes how to verify a target number, that is, to check whether a specified number is set as the CFO target number on the telephone set.
Table 10-11 Check specified CFO target number on the telephone set
Step |
Expected result |
Pick up the phone. |
The subscriber can hear the dial tone. |
Dial *#45*. |
If the specified number is set as the target number, the subscriber can hear the ringback tone or the voice prompt “You have already activated the call forwarding offline service. Your forward number is XXXX.” (XXXX is the CFO number the subscriber sets.) If not, the subscriber will hear the busy tone or the voice prompt “Sorry, you have no forward number.” |
Hang up the phone. |
— |
The following table describes how to delete CFO target number on the telephone set.
Table 10-12 Delete all CFO target numbers on the telephone set
Step |
Expected result |
Pick up the phone. |
The subscriber can hear the dial tone. |
Dial #45#. |
If the target numbers are deleted successfully, the subscriber can hear the ringback tone or the voice prompt “You have deactivated the service.” If no target number is available for deletion, the subscriber will hear the busy tone or the voice prompt “Sorry, your attempt to deactivate the service was unsuccessful.” |
Hang up the phone. |
— |
Caution:
Be cautious about the deletion, for all the CFO forwarding numbers will be deleted by the operation.
Table 10-13 Configure CFO service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-GW view. |
gateway device-id |
Required |
Enter subscriber number view. |
subscriber short-number long-number |
Required |
Enter CFO service view. |
cfo |
— |
Add target numbers for CFO forwarding. |
cfo-number forward-number |
Required |
Exit CFO service view. |
quit |
— |
Enable/disable the CFO service. |
srv-switch cfo {on | off } |
Required |
Enable the CFO service for subscriber 8801 under GW01, with the target number being 8803.
& Note:
Refer to the network diagram in Network Diagram.
1) Configure basic parameters on the XE IP PBX.
2) Configure basic parameters of gateways GW01, GW02, and GW03.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
<XE>system-view
[XE]location-server
[XE-ls]gateway GW01
[XE-ls-gw-GW01]subscriber #1 8801
[XE-ls-gw-GW01 #1 8801]cfo
[XE-ls-gw-GW01 #1 8801-cfo]cfo-number 8803
[XE-ls-gw-GW01 #1 8801-cfo]quit
[XE-ls-gw-GW01 #1 8801]srv-switch cfo on
With the CFB service, incoming calls are forwarded to the target number pre-specified by the callee when the callee is busy. Calls will not be forwarded when the callee is idle. Up to 2 CFB forward numbers can be set by the subscriber.
After the administrator enables the CFB service for a subscriber, target forwarding numbers can be set by the following two methods.
l The administrator can set the number on the XE through command lines. Refer to 10.6.3 “Configuration Procedure” for details.
l The subscriber can set the number on the telephone set as follows.
The following table describes the CFB target number setting task made by the subscriber.
Table 10-14 Set CFB target number on the telephone set
Step |
Expected result |
Pick up the phone. |
The subscriber can hear the dial tone. |
Dial *40*, the target forwarding number and # in sequence. |
If the setting succeeds, the subscriber can hear the ringback tone or the voice prompt “You have successfully activated the service.” If the setting fails, the subscriber will hear the busy tone or the voice prompt “Sorry, your attempt to activate the service was unsuccessful.” |
Hang up the phone. |
— |
The following table describes the CFB target number verification task, which checks whether a specified number is set as the CFU target number on the telephone set.
Table 10-15 Check specified CFB target number on the telephone set
Step |
Expected result |
Pick up the phone. |
The subscriber can hear the dial tone. |
Dial *#40* |
If the specified number is set as the target number, the subscriber can hear the ringback tone or the voice prompt “You have already activated the call forwarding on busy service. Your forward number is XXXX.” (XXXX is the CFB number the subscriber sets.) If not, the subscriber will hear the busy tone or the voice prompt “Sorry, you have no forward number.” |
Hang up the phone. |
— |
The following table describes the CFB forwarding number deletion task.
Table 10-16 Delete all CFB forwarding numbers on the telephone set
Step |
Expected result |
Pick up the phone. |
The subscriber can hear the dial tone. |
Dial #40#. |
If target numbers are deleted, the subscriber can hear the ringback tone or the voice prompt “You have deactivated the service.” If no target number is available for deletion, the subscriber will hear the busy tone or the voice prompt “Sorry, your attempt to deactivate the service was unsuccessful.” |
Hang up the phone. |
— |
Caution:
Be cautious about the deletion, for all the CFB forwarding numbers will be deleted by the operation.
Table 10-17 Configure CFB service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-GW view. |
gateway device-id |
Required |
Enter subscriber number view. |
subscriber short-number long-number |
Required |
Enter CFB service view. |
cfb |
— |
Add target numbers for CFB forwarding. |
cfb-number forward-number |
Required |
Exit CFB service view. |
quit |
— |
Enable/disable the CFB service. |
srv-switch cfb {on | off } |
Required |
Enable the CFB service for subscriber 8801 under GW01, with the target number being 8802.
& Note:
Refer to the network diagram in Network Diagram.
1) Configure basic parameters on the XE IP PBX.
2) Configure basic parameters of gateways GW01, GW02, and GW03.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
<XE>system-view
[XE]location-server
[XE-ls]gateway GW01
[XE-ls-gw-GW01]subscriber #1 8801
[XE-ls-gw-GW01 #1 8801]cfb
[XE-ls-gw-GW01 #1 8801-cfb]cfb-number 8802
[XE-ls-gw-GW01 #1 8801-cfb]quit
[XE-ls-gw-GW01 #1 8801]srv-switch cfb on
With the CFNR service, an incoming call is forwarded to the target number pre-specified by the callee if the phone is not picked up after it rings for a certain time (18 seconds). The call will not be forwarded if the phone is picked up in time. Up to 2 CFNR forward numbers can be set by the subscriber.
After the administrator enables the CFNR service for a subscriber, target forwarding numbers can be set by the following two methods.
l The administrator can set the number on the XE IP PBX through command lines. Refer to 10.7.3 “Configuration Procedure” for details.
l The subscriber can set the number on the telephone set as follows:
The following table describes how to set the CFNR target number.
Table 10-18 Set CFNR target number on the telephone set
Step |
Expected result |
Pick up the phone. |
The subscriber can hear the dial tone. |
Dial *41*, the target forwarding number and # in sequence. |
If the setting succeeds, the subscriber can hear the ringback tone or the voice prompt “You have successfully activated the service.” If the setting fails, the subscriber will hear the busy tone or the voice prompt “Sorry, your attempt to activate the service was unsuccessful.” |
Hang up the phone. |
— |
The following table describes how to verify the CFNR target number, that is, to check whether a specified number is set as the CFNR target number on the telephone set.
Table 10-19 Check specified CFNR target number on the telephone set
Step |
Expected result |
Pick up the phone. |
The subscriber can hear the dial tone. |
Dial *#41*. |
If the specified number is set as the target number, the subscriber can hear the ringback tone or the voice prompt “You have already activated the call forwarding no reply service. Your forward number is XXXX.” (XXXX is the CFNR number the subscriber sets.) If not, the subscriber will hear the busy tone or the voice prompt “Sorry, you have no forward number.” |
Hang up the phone. |
— |
The following table describes how to delete the CFNR forwarding number.
Table 10-20 Delete all CFNR forwarding numbers on the telephone set
Step |
Expected result |
Pick up the phone. |
The subscriber can hear the dial tone. |
Dial #41#. |
If target numbers are deleted, the subscriber can hear the ringback tone or the voice prompt “You have deactivated the service.” If no target number is available for deletion, the subscriber will hear the busy tone or the voice prompt “Sorry, your attempt to deactivate the service was unsuccessful.” |
Hang up the phone. |
— |
Caution:
Be cautious about your deletion, for all the CFNR forwarding numbers will be deleted by the operation.
Table 10-21 Configure CFNR service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-GW view. |
gateway device-id |
Required |
Enter subscriber number view. |
subscriber short-number long-number |
Required |
Enter CFNR service view. |
cfnr |
— |
Add target numbers for CFNR forwarding. |
cfnr-number forward-number |
Required |
Exit CFNR service view. |
quit |
— |
Enable/disable the CFNR service. |
srv-switch cfnr {on | off } |
Required |
Enable the CFNR service for subscriber 8801 under GW01, with the target number being 8803.
& Note:
Refer to the network diagram in Network Diagram.
1) Configure basic parameters on the XE IP PBX.
2) Configure basic parameters of gateways GW01, GW02, and GW03.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
<XE>system-view
[XE]location-server
[XE-ls]gateway GW01
[XE-ls-gw-GW01]subscriber #1 8801
[XE-ls-gw-GW01 #1 8801]cfnr
[XE-ls-gw-GW01 #1 8801-cfnr]cfnr-number 8803
[XE-ls-gw-GW01 #1 8801-cfnr]quit
[XE-ls-gw-GW01 #1 8801]srv-switch cfnr on
Third party call termination service is used to stop ongoing calls forcibly. It can only be executed by the administrator on the XE IP PBX or related configuration interfaces.
The administrator can view the following call-related information through commands:
l Call index
l Caller number
l Called number
l Call start time
The administrator uses the call index to terminate the ongoing call forcibly.
Table 11-1 Configure third party call termination service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
View the ongoing call. |
display location-server call-list { number | all } |
Optional |
Terminate the ongoing call. |
break call-index |
Required The call index can be obtained through command display location-server call-list. |
& Note:
l It is strongly recommended that before terminating the call, the administrator first view the call-related information using the display location-server call-list command and confirm the call index is correct, which can avoid incorrect operation.
l If an active call corresponding to the call index has to be terminated, it stops no matter what state it is in and releases all the relative resources. However, if no call corresponding to the call index exists, a prompt message will be displayed by the XE IP PBX.
Subscriber 8801 is making a call with subscriber 8802. The administrator has to terminate this call forcibly for some reason.
& Note:
Refer to the network diagram in Network Diagram.
1) Configure basic parameters on the XE IP PBX.
2) Configure basic parameters of gateways GW01, GW02, and GW03.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
# The administrator queries call-related information for subscriber 8801 or 8802 on the XE.
[XE-ls]display location-server call-list 8801
Ccb index caller callee Start
13 8802 8801 11:09:17
# The administrator confirms to terminate the call forcibly and then performs the termination operation.
[XE-ls]break 13
Break the call :13
The one number link you (ONLY) service can be used to assign an ID, which uniquely identifies a subscriber. Some or all of the subscriber’s numbers can be bound with the subscriber ID. When a call is made to the subscriber ID, telephone sets bound to it will ring in the order of priority level from high to low that the subscriber’s numbers are given. Those telephone sets whose numbers have the same priority level will ring in a randomly determined order if the function of random number selection is enabled, and will ring simultaneously if that function is not enabled. The subscriber can pick up any phone to start the conversation. Meanwhile, other phones stop ringing.
One subscriber ID, a string of up to 31 characters, can be bound with 5 numbers at most.
At most 2000 subscriber IDs can be configured for the XE 2000, and 200 for the XE 200.
When the ONLY service is enabled, a subscriber can place a call by dialing the callee’s ID instead of complete numbers.
Table 12-1 Configure ONLY service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Create a subscriber ID and enter ONLY service view. |
only subscriber-id |
Required |
Bind a subscriber’s number with the ID. |
tel-number number |
Required |
& Note:
l When configuring the ONLY number, make sure that it does not conflict with the subscriber line number, the static route number, the automatic operator number and the group notification number.
l If you have configured and enabled the country code and area code on an XE IP PBX, you should configure a full number for an emergency call number including the country code and the area code.
l The ONLY number must be a number already exists on the XE IP PBX.
The home, office 1, and office 2 numbers of subscriber A are 8801, 8802, and 8803 respectively. Subscriber ID 5678 is assigned when subscriber A applies for the ONLY service. All the above numbers are bound to this ID.
& Note:
Refer to the network diagram in Network Diagram.
1) Configure basic parameters on the XE IP PBX.
2) Configure basic parameters of gateways GW01, GW02, and GW03.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
# Create subscriber ID 5678.
[XE-ls]only 5678
# Bind the three numbers with the ID.
[XE-ls-only-5678]tel-number 8801
[XE-ls-only-5678]tel-number 8802
[XE-ls-only-5678]tel-number 8803
The time limit call service is used to control the call duration within a specific period. If the time limit call service is enabled for a subscriber, all calls that this subscriber makes cannot exceed the time limit; otherwise the call will be terminated automatically.
Using of the time limit call service requires devices including gateway and terminals.
The call duration is determined by the settings of the caller and the callee. When either the caller or the callee sets the time limit call service, the call duration will be restricted. The shorter call duration limit is adopted for the call.
The following table describes the rules for the call duration.
Table 13-1 Rules for call duration limit
Call duration limit |
Callee |
||
Time limit call service enabled |
Time limit call service disabled |
||
Caller |
Time limit call service enabled |
The shorter call duration limit is adopted for the call. |
The call duration is determined by that set by the caller. |
Time limit call service disabled |
The call duration is determined by that set by the callee. |
The call duration is not restricted. |
& Note:
l If the caller ID is anonymous, since the call duration time limit of the caller is unavailable, the call duration limit of the callee will be adopted for the call.
l The call duration is not restricted by the maximum call duration limit of the recipient if either party in a time limit call uses the call transfer service.
l If a third party uses the call intervention service during a limit time call, the call duration is reset after the third party ends the call with the callee.
Table 13-2 Configure time limit call service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Set the default call duration. |
default-limit-call-time default-limited-time |
Optional |
Enter LS-GW view. |
gateway device-id |
Required |
Enter subscriber number view. |
subscriber short-number long-number |
Required |
Enter time limit call service view. |
limited-time-call |
— |
Set the call duration limit for the subscriber. |
limit-call-time limited-time |
Optional The default duration limit is adopted when this argument is not set. |
Exit time limit call service view. |
quit |
— |
Enable/disable the time limit call service. |
srv-switch limited-time-call {on | off } |
Required |
Enable the time limit call service for subscriber 8801 under GW01, with the call duration limit being 360 seconds.
& Note:
Refer to the network diagram in Network Diagram.
1) Configure basic parameters on the XE IP PBX.
2) Configure basic parameters of gateways GW01, GW02, and GW03.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
<XE>system-view
[XE]location-server
[XE-ls]gateway GW01
[XE-ls-gw-GW01]subscriber #1 8801
[XE-ls-gw-GW01 #1 8801]limited-time-call
[XE-ls-gw-GW01 #1 8801-ltc]limited-call-time 360
[XE-ls-gw-GW01 #1 8801-ltc]quit
[XE-ls-gw-GW01 #1 8801]srv-switch limited-time-call on
[XE-ls-gw-GW01 #1 8801]return
<XE>
A third party, usually an authorized administrator can preset a call task on the XE IP PBX. The XE IP PBX then will invite the call participants (A and B) to join the call at the preset time and to have a conversation. Two participants, namely, parties A and B, are supported by the third party call control service.
To use the third party call control service, the MS should be enabled on the XE IP PBX first.
The third party call control service works as follows:
1) An authorized administrator logs on to the XE IP PBX and predefines a call task as described in Third Party Call Control Service Configuration.
2) The phone of call participant A rings at the preset time.
3) Party A picks up the phone and then the phone of call participant B rings.
4) Party B picks up the phone and the conversation between party A and party B begins. The corresponding call task is deleted from the XE IP PBX at the same time.
5) Both parties hang up the phone when the conversation ends.
& Note:
If A does not pick up the receiver in time, A will stop ringing after the time expires on the server and the XE IP PBX will end and delete the call. On the other hand, if A has picked up the phone, but B has not in time, the XE IP PBX will end and delete the call as well.
Configure the third party call control service as follows:
Table 14-1 Configure the third party call control service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-SRV view. |
service |
— |
Enter 3PCC view. |
3pcc |
— |
Configure the call participants and call start time. |
participant identify num1 num2 start-time |
Required |
Display existing third party call control tasks. |
display location-server 3pcc { participant-number | active | all } |
Optional |
& Note:
The preset call start time must be later than the system time; otherwise the configuration fails. If the call start time is not specified, it defaults to the current time.
On the XE IP PBX, configure the third party call control service for subscribers 8801 and 8802, with the call start time being 17:10:00.
& Note:
Refer to the network diagram in Network Diagram.
1) Configure basic parameters on the XE IP PBX.
2) Configure basic parameters of gateways GW01, GW02, and GW03.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
<XE>system-view
[XE]location-server
[XE-ls]service
[XE-ls-srv]3pcc
[XE-ls-srv-3pcc]participant 888 8801 8802 17:10:00
[XE-ls-srv-3pcc]display location-server 3pcc all
When a subscriber using the callback-on-busy service fails to make a call because the callee is busy, the XE IP PBX records the call request and then initiates the call again after a certain interval.
A subscriber using the callback-on-busy service cannot make or answer a call before the first ringing. Otherwise, the callback-on-busy service will become ineffective automatically.
When the callback-on-busy service is enabled, the XE IP PBX will get through the called number independent of the restriction from services like do-not-disturb or call forwarding.
& Note:
To use the callback-on-busy service, you need to enable the MS on the XE IP PBX first.
Counted in minutes, call back interval refers to the interval between the successful registration of the call back service and the first call-back made by the XE IP PBX. If the retry times is set to a value larger than 1, the XE IP PBX will retry calling back after this interval if a call back attempt fails.
Call back retry times refers to the number of times that the XE IP PBX can retry calling back in case of call-back failure.
With the call back service enabled, the XE IP PBX first invites the callee to join the call after the preset call back interval. After the callee picks up the phone, the XE IP PBX invites the caller, and the conversation begins after the caller picks up the phone. If any failure occurs in inviting the callee, and if the call back retry times is set to a value larger than 1, the XE IP PBX will initiate another call invitation after the preset call back interval, till the callee picks up the phone or the retry times has been reached. If the callee has picked up the phone but the caller is busy or does not answer the phone in time when being invited, the XE IP PBX regards that the call back service is successfully finished and deletes this service.
The callback-on-busy service works as follows:
1) An authorized administrator logs on to the XE IP PBX and enables the callback-on-busy service for subscriber A. Refer to Callback-On-Busy Service Configuration for details.
2) When subscriber A calls subscriber B and finds that B is busy, subscriber A hangs up.
3) Subscriber A picks up the phone to apply for the call back on busy service. Refer to Register for callback-on-busy service for details.
4) After the preset call back interval, the XE IP PBX sends a call request to subscriber B, and the phone of subscriber B rings.
5) Subscriber B picks up the phone and hear the voice prompt “It is subscriber A (number) using callback-on-busy service. Please wait.” Later the phone of subscriber A rings.
& Note:
In the voice prompt above, characters in italic means the item can be varied according to actual situations. This principle applies throughout the manual.
6) If subscriber A picks up the phone, A can talk with subscriber B; however, if A is busy or cannot pick up the phone in the specified time, the subscriber B will hear the voice prompt “Sorry, your call is unsuccessful.” The XE IP PBX will automatically deregister the callback-on-busy service.
Table 15-1 Register for the callback-on-busy service
Step |
Expected result |
The subscriber calls and finds the callee is busy. |
The subscriber hangs up. |
The subscriber picks up the phone again. |
The subscriber hears the dial tone. |
The subscriber dials *59# to register for the callback-on-busy service. |
If the callback-on-busy service is enabled on the XE IP PBX, the subscriber hears the voice prompt “You have successfully activated the service.” If the callback-on-busy service is disabled on the XE IP PBX, the subscriber hears the voice prompt “Sorry, the service is not available.” |
The subscriber hangs up. |
— |
Table 15-2 Deregister the callback-on-busy service
Step |
Expected result |
The subscriber picks up the phone. |
The subscriber hears the dial tone. |
The subscriber dials #59# to deregister the callback-on-busy service. |
If the subscriber has registered for the callback-on-busy service, it hears the voice prompt “You have successfully deactivated the service.” If the callback-on-busy service is disabled on the XE IP PBX, the subscriber hears the voice prompt “Sorry, the service is not available.” If the subscriber has not registered for the callback-on-busy service, it hears the voice prompt “Sorry, your attempt to deactivate the service was unsuccessful.” |
The subscriber hangs up. |
— |
Authorized administrators can set the call back interval and retry times. As global parameters, the configured call back interval and retry times apply to all callback-on-busy transactions configured on the XE IP PBX.
Table 15-3 Set callback-on-busy parameters
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-SRV view. |
service |
— |
Enter call back view. |
cb |
— |
Set the call back interval (in minutes). |
interval time-length |
Optional, the default call back interval is 1 minute. |
Set the call back retry times. |
retry times |
Optional The default retry times is 10. |
Table 15-4 Enable/disable the callback-on-busy service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-GW view. |
gateway device-id |
— |
Enter subscriber number view. |
subscriber short-number long-number |
— |
Enable/disable the callback-on-busy service. |
srv-switch cb { on | off } |
Required |
Enable the callback-on-busy service for subscriber 8801 under GW01.
& Note:
Refer to the network diagram in Network Diagram.
1) Configure basic parameters on the XE IP PBX.
2) Configure basic parameters of gateways GW01, GW02, and GW03.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
<XE>>
<XE>system-view
[XE]location-server
[XE-ls]gateway GW01
[XE-ls-gw-GW01]subscriber #1 8801
[XE-ls-gw-GW01 #1 8801]
[XE-ls-gw-GW01 #1 8801]srv-switch cb on
[XE-ls-gw-GW01 #1 8801]return
<XE>
When subscriber A calls subscriber B, whose phone then rings, subscriber C using the call pickup service can answer the call by dialing the access code and subscriber B’s phone number. In this way, subscriber C can have a conversation with A. In brief, the call pickup service enables a subscriber to answer an incoming call to another subscriber.
The call pickup service falls into unilateral call pickup and bilateral call pickup.
l Unilateral call pickup service
The unilateral call pickup service enables a subscriber with the call pickup right to answer a call that the XE IP PBX makes to another subscriber. For example, subscriber B has the call pickup right and the XE IP PBX makes a call to subscriber A, whose phone then rings. B can answer the call by dialing the access code and A’s phone number. Then subscriber A’s phone stops ringing.
l Bilateral call pickup service
The bilateral call pickup service enables a subscriber with the call pickup right to answer a call that a second subscriber makes to a third subscriber. For example, subscriber C has the call pickup right and subscriber A makes a call to subscriber B, whose phone then rings. C can answer the call by dialing the access code and B’s phone number. Subscriber B’s phone stops ringing, and A can have a conversation with C.
In the above example, if subscriber A uses the outgoing call authority control service and is not allowed to call subscriber C, subscriber C is unable to answer the call originated by subscriber A to subscriber B.
For a call which has multiple callees, if the callees ring in sequence, the call pickup service is supported, and if the callees ring simultaneously, the call pickup service is not supported.
The call pickup service requires the cooperation of the media server.
The call pickup service must be enabled on the XE IP PBX before being used by a subscriber. Refer to Call Pickup Service Configuration for operation details.
Use unilateral call pickup service as follows.
Table 16-1 Use the unilateral call pickup service on the phone
Step |
Expected result |
The XE IP PBX places a call to subscriber A. |
The phone of subscriber A rings. |
Subscriber B picks up the phone. |
Subscriber B hears the dial tone. |
Subscriber B dials *11*+A’s phone number #. |
If subscriber B has the call pickup right, a call is set up between B and the XE IP PBX and A’s phone stops ringing. If B has no call pickup right, B hears the voice prompt “Sorry, the service is not available”, and A’s phone keeps ringing. |
Use the bilateral call pickup service as follows.
Table 16-2 Use the bilateral call pickup service on the phone
Step |
Expected result |
Subscriber A places a call to subscriber B. |
The phone of subscriber B rings. |
Subscriber C picks up the phone. |
Subscriber C hears the dial tone. |
C dials *11*+B’s phone number #. |
If subscriber C has the call pickup right, a call is set up between C and A, and B’s phone stops ringing. If C has no call pickup right, it hears the voice prompt “Sorry, the service is not available”, and B’s phone keeps ringing. |
Table 16-3 Configure the call pickup service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-GW view. |
gateway device-id |
— |
Enter subscriber number view. |
subscriber short-number long-number |
— |
Enable/disable the call pickup service. |
srv-switch cp { on | off } |
Required |
& Note:
This command can also be executed in LS-GW-PREFIX view.
Enable the call pickup service for subscriber 8801 under GW01.
& Note:
Refer to the network diagram in Network Diagram.
1) Configure basic parameters on the XE IP PBX.
2) Configure basic parameters of gateways GW01, GW02, and GW03.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
<XE>
<XE>system-view
[XE]location-server
[XE-ls]gateway GW01
[XE-ls-gw-GW01]subscriber #1 8801
[XE-ls-gw-GW01 #1 8801]
[XE-ls-gw-GW01 #1 8801]srv-switch cp on
[XE-ls-gw-GW01 #1 8801]return
<XE>
Using the call intervention service, a subscriber can forcibly make a call by dialing the access code and a called number, no matter whether the callee is idle or in conversation. If the callee is in conversation, the intervening subscriber can choose to restore or terminate the original call connection before ending the call.
The access code of the call intervention service is *89*.
To use the call intervention service:
l MS should be enabled on the XE IP PBX first. Otherwise, the call intervention will fail, and the ongoing call will proceed normally.
l Out-band dialing support is required.
The call intervention service does not support the following:
l Subscriber management service (for the callee)
l Inter-group call restriction service
l Outgoing call authority control service
l Call forwarding services except CFO (for the callee)
l DND service (for the callee)
Caution:
l Use the call intervention service with caution. It is recommended for specific subscribers only.
l The call intervention service does not support nesting. That is, the call intervention service is no longer applicable to a call which itself is established by using the call intervention service.
The call intervention service must be enabled before a subscriber can use it. Refer to Call Intervention Service Configuration for operation details.
Table 17-1 Use the call intervention service
Step |
Expected result |
|
A call is set up between subscribers A and B or subscriber A is idle. |
Subscribers A and B are having a conversation or subscriber A is idle. |
|
Subscriber C picks up its phone. |
Subscriber C hears dial tones. |
|
C dials *89* + subscriber A’s phone number + #. |
Subscriber C has a conversation with subscriber A, and subscriber B hears call waiting music. |
|
Subscriber C ends the call with subscriber A. |
Subscriber C dials *89#. |
The original call between subscriber A and subscriber B is resumed. |
Subscriber C hangs up. |
The original call is terminated. |
& Note:
When using the call intervention service, subscriber C, who additionally uses the password call service, needs to dial *89* + ABCD + subscriber A’s phone number or subscriber B’s.
You can configure the call intervention service in subscriber number view, the LS-GW-PREFIX view or the LS-OG-PREFIX view.
The configuration procedure is as follows:
Table 17-2 Configure the call intervention service
Operation |
Command |
Description |
Enable/disable the call intervention service. |
srv-switch ci { on | off } |
Required |
& Note:
To configure the call intervention service on different office devices, you need to enable the call intervention service for the subscriber on the peer device as well as in local subscriber number view.
l Subscribers 8801, 8802, and 8803 exist.
l Enable the call intervention service for subscriber 8801.
l After a call is set up between subscribers 8802 and 8803, subscriber 8801 intervenes into the call forcibly and has a conversation with subscriber 8802.
l The call between 8802 and 8803 is restored when 8801 exits the call.
& Note:
Refer to the network diagram in Network Diagram.
1) Configure basic parameters on the XE IP PBX.
2) Configure basic parameters of gateways GW01, GW02, and GW03.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
<XE>
<XE>system-view
[XE]location-server
[XE-ls]gateway GW01
[XE-ls-gw-GW01]subscriber #1 8801
[XE-ls-gw-GW01 #1 8801]
[XE-ls-gw-GW01 #1 8801]srv-switch ci on
[XE-ls-gw-GW01 #1 8801]return
<XE>
1) Subscriber 8802 places a call to subscriber 8803 and the call is set up successfully.
2) Subscribers 8802 and 8803 start a conversation.
3) Subscriber 8801 picks up the phone and dials *89*2000#.
4) A conversation between subscribers 8801 and 8802 is started, and subscriber 8803 hears the music on hold.
5) While listening to the music on hold, subscriber 8803 can hang up without affecting the conversation between subscribers 8801 and 8802.
6) If subscriber 8801 or 8802 hangs up during their conversation, the other two parties will hear busy tones.
7) During the conversation, subscriber 8801 can dial *89# to restore the conversation between subscribers 8802 and 8803, provided the latter did not hang up. After that, subscriber 8801 hears the busy tone
The dialing test service is a special service for administrators only. It tests the validity of subscriber numbers configured on the LS and the line status, so that the administrator can evaluate the network conditions. If enabled with the CLIP service, the tested telephone set displays the calling number as 00000000.
To use the dialing test service, you need to enable the MS on the XE IP PBX first.
1) Use the dial-test command on the XE IP PBX to start the dialing test process. Refer to Dialing Test Service Configuration for operation details.
2) The message “dialing ......” will be displayed. If the tested number does not exist, “dial failed” is displayed instead.
3) The dialing test information is displayed.
l If the callee is busy, a message “dial failed” will be displayed and the service is terminated.
l If the phone of the callee rings, a message “callee ringing!” will be displayed until the callee picks up the phone.
l If the test fails due to abnormality, a message “dial failed” will be displayed and the service is terminated.
4) If the callee does not pick up the phone, a message “dial failed” will be displayed after a certain interval and the service is terminated.
5) If the caller picks up the phone, it hears a voice prompt “Hello, this is the maintenance center. We are testing the line. Thank you for your cooperation.”
6) If the callee hangs up while the voice prompt is playing, a message “callee release, test succeed!” will be displayed and the service is terminated.
7) After the callee picks up the phone, the XE IP PBX plays the voice prompt for three times and then terminates the test. A message “test succeed!” will be displayed and the service ends successfully.
Table 18-1 Configure dialing test service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-SRV view. |
service |
— |
Enable the line dialing test process. |
dial-test number-for-test |
Required |
Perform line dialing test on the XE IP PBX for subscriber 8801.
& Note:
Refer to the network diagram in Network Diagram.
1) Configure basic parameters on the XE IP PBX.
2) Configure basic parameters of gateways GW01, GW02, and GW03.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
<XE>
<XE>system-view
[XE]location-server
[XE-ls]service
[XE-ls-srv]dial-test 8801
dialing ......
[XE-ls-srv]
callee ringing!
callee release, test succeed!
[XE-ls-srv]return
<XE>
With the time announcement service, a subscriber can dial the access code to the XE IP PBX to query the current time. The time presented by the XE IP PBX is its current system time.
& Note:
To use the time announcement service, you need to enable the MS on the XE IP PBX first. Otherwise, a subscriber will hear the busy tone when attempting to use this service.
Before the time announcement service is available for a subscriber, an authorized administrator must enable it for the subscriber first. Refer to Enabling/Disabling Time Announcement Service for operation details.
Table 19-1 Use the time announcement service
Step |
Expected result |
The subscriber picks up the phone. |
The subscriber hears dial tones. |
The subscriber dials *90*0#. |
If the service is enabled, the subscriber hears the voice prompt “The current time is XXXX”, provided the corresponding media resource is configured. If the service is not enabled, the subscriber hears the voice prompt “Sorry, the service is not available”, even if the media resource is configured. If no media resource is configured, the subscriber will hear busy tones. |
The subscriber hangs up. |
— |
Table 19-2 Enable/disable the time announcement service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-GW view. |
gateway device-id |
— |
Enter subscriber number view. |
subscriber short-number long-number |
— |
Enable/disable the time announcement service. |
srv-switch announce { on | off } |
Required |
& Note:
This command can also be executed in LS-GW-PREFIX view.
Enable the time announcement service for subscriber 8801 under GW01.
& Note:
Refer to the network diagram in Network Diagram.
1) Configure basic parameters on the XE IP PBX.
2) Configure basic parameters of gateways GW01, GW02, and GW03.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
<XE>system-view
[XE]location-server
[XE-ls]gateway GW01
[XE-ls-gw-GW01]subscriber #1 8801
[XE-ls-gw-GW01 #1 8801]srv-switch announce on
[XE-ls-gw-GW01 #1 8801]return
<XE>
The MyRing service is to set a customized ringback tone for a subscriber, so that when the subscriber is called, the caller will hear the customized ringback tone.
You can divide callers into different caller groups and assign different customized ringback tones to subscribers in different caller groups. Callers in different groups will hear different ringback tones when calling a MyRing-enabled subscriber. When a subscriber beyond the defined caller groups calls the MyRing-enabled subscriber, the caller hears the default customized ringback tone set by the called subscriber.
To use the MyRing service, you need to enable the MS on the XE IP PBX first. Otherwise, the MyRing service cannot run normally (This means the caller can hear only the normal ringback tone instead of a customized ringback tone, but the call can be set up normally).
1) Save the media files pre-recorded for the MyRing service into the Flash memory of the XE IP PBX.
3) Enable the MyRing service for the subscriber and configure the default customized ringback tone, which will be displayed for callers not in any caller group. Refer to Basic Configurations of MyRing Service for details.
4) Group callers of the subscriber as needed, and specify a ringback tone for each group. Refer to Configuring Caller Groups and Related Information for details.
Before operations listed in the following table, enable the MyRing service for subscriber A and specify a default customized ringback tone.
Table 20-1 Use the MyRing service
Step |
Expected result |
Subscriber B picks up the phone. |
Subscriber B hears the dial tone. |
Subscriber B dials the phone number of subscriber A. |
The phone of subscriber A rings, and B hears the customized ringback tone of A. |
Subscriber A picks up the phone. |
The XE IP PBX stops playing the customized ringback tone and the conversation starts. |
Table 20-2 Basic configurations of the MyRing service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-GW view. |
gateway device-id |
— |
Enter subscriber number view. |
subscriber short-number long-number |
— |
Enable/disable the MyRing Service. |
srv-switch myring { on | off } |
Required |
Enter MyRing view. |
myring |
— |
Configure the default customized ringback tone for the subscriber. |
default-ring media-id |
Required By default, the customized ringback tone is 1010.wav. |
Table 20-3 Configure caller groups and related information
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-GW view. |
gateway device-id |
— |
Enter subscriber number view. |
subscriber short-number long-number |
— |
Enter MyRing view. |
myring |
— |
Create a caller group and enter its caller group view. |
caller-group caller-group-id |
Required |
Configure a customized ringback tone for the caller group. |
ring media-id |
Required By default, the customized ringback tone is 1010.wav. |
Add caller members into the created group. |
caller-member long-number |
Required |
& Note:
If country codes and area codes are configured on the XE IP PBX and the XE IP PBX needs to use them, the number of a caller member must be a long number containing a country code and area code.
Enable the MyRing service for subscriber 8801 under GW01, so that when subscriber 8802 makes a call to subscriber 8801, the recorded ringback tone (in media resource file 1700.wav) will be played.
& Note:
Refer to the network diagram in Network Diagram.
1) Configure basic parameters on the XE IP PBX.
2) Configure basic parameters of gateways GW01, GW02, and GW03.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
# Configure the MyRing service for subscriber 8801.
<XE>system-view
[XE]location-server
[XE-ls]gateway GW01
[XE-ls-gw-GW01]subscriber #1 8801
[XE-ls-gw-GW01 #1 8801]srv-switch myring on
[XE-ls-gw-GW01 #1 8801]myring
[XE-ls-gw-GW01 #1 8801-myring]caller-group callergroup1
[XE-ls-gw-GW01 #1 8801-myring-callergroup1]ring 1700
[XE-ls-gw-GW01 #1 8801-myring-callergroup1]caller-member 8802
[XE-ls-gw-GW01 #1 8801-myring-callergroup1]return
<XE>
# Specify the file to be related to ringback tone index 1700.
<XE>system-view
[XE]media-ability
[XE-ma]language Chinese
[XE-ma-Chinese]format G711a
[XE-ma-Chinese-G711a]set-media 1700 /g711wav/1700.wav
In an ongoing call, one party using the call park and call pickup (CPCP) service can temporarily suspend the call by hanging up the phone. The other party can hold the phone and listens to the music on hold until the CPCP-initiating subscriber restores the call by dialing the connection code.
The CPCP service must be enabled on a subscriber that is to use it. After either party initiates the CPCP service, the other party cannot initiate any service, including the CPCP service.
To use the CPCP service:
l MS should be enabled on the XE IP PBX first. Otherwise, the CPCP service will fail and the call will go on normally.
l Out-band dialing support is required.
1) An authorized administrator logs on to the XE IP PBX and enables the CPCP service for subscriber A. Refer to CPCP Service Configuration for operation details.
2) A call is set up between subscribers A and B.
3) A dials the access code *91#.
4) A hears the voice prompt “The connection code to restore the call is XXXX.” and then B listens to the music on hold.
5) A can resume the call by dialing *91*xxxx# on any phone, including the one it used before, and continue the conversation with B.
Table 21-1 Use the CPCP service
Step |
Expected result |
Subscriber A dials the phone number of subscriber B. |
The call is set up and subscribers A and B start a conversation. |
A dials *91#. |
The call goes on if the CPCP service is not enabled for A. A hears the voice prompt “The connection code to restore the call is XXXX” and B hears the music on hold if the CPCP service has been enabled for subscriber A. |
A remembers the access code that the XE IP PBX assigns for it and then hangs up. |
— |
A or another subscriber dials *91*xxxx#. |
The XE IP PBX stops playing the music on hold to B and the call between A and B resumes. |
& Note:
l xxxx stands for the connection code that the XE IP PBX assigned for the call. It is used for locating the call when the call is to be restored. Therefore, the subscriber using the CPCP service must remember this number.
l After subscriber A makes the call and hangs up with the call hold and restoration service, subscriber A or other subscribers who are on the same XE IP PBX as subscriber A can restore the call by dialing *91*xxxx#.
Table 21-2 Configure the CPCP service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-GW view. |
gateway device-id |
— |
Enter subscriber number view. |
subscriber short-number long-number |
— |
Enable/disable the CPCP service. |
srv-switch cpcp { on | off } |
Required |
& Note:
This command can also be executed in LS-GW-PREFIX view.
Enable the CPCP service for subscriber 8801 under GW01.
& Note:
Refer to the network diagram in Network Diagram.
1) Configure basic parameters on the XE IP PBX.
2) Configure basic parameters of gateways GW01, GW02, and GW03.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
# Configure the CPCP service.
<XE>system-view
[XE]location-server
[XE-ls]gateway GW01
[XE-ls-gw-GW01]subscriber #1 8801
[XE-ls-gw-GW01 #1 8801]srv-switch cpcp on
[XE-ls-gw-GW01 #1 8801]return
<XE>
The automatic operator service enables a subscriber to perform two-stage dialing as needed. After dialing the access code and establishing a call connection with the XE IP PBX, the subscriber receives a voice prompt from the XE IP PBX. Then the subscriber can establish a call connection with the callee, who can provide related service.
To use the automatic operator service:
l MS should be enabled on the XE IP PBX first. Otherwise, a subscriber will hear the busy tone when attempting to use this service.
l Out-band dialing support is required.
l Only one callee is supported by the automatic operator number.
l The automatic operator number cannot act as a forwarding or forwarded-to number.
l A subscriber using the automatic operator service cannot be forwarded to the automatic operator number.
l You need to record the access the voice prompt for the automatic operator service, store it on the XE IP PBX, and configure a media ID for it.
& Note:
Voice prompts occupy media IDs 0 to 10000. Therefore, you need to set an ID greater than 10000 for the access voice prompt of the automatic operator service to avoid confliction.
1) Store the access prompt tone file recorded for the automatic operator service into the Flash memory of the XE IP PBX.
2) Configure a media ID for the file. Refer to the “Configuring a Media Resource” part in the Media Server Operation module for details.
3) Configure the automatic operator number and its basic information. Refer to Configuration Procedure for details.
4) Use the automatic operator service
Table 22-1 Use the automatic operator service
Step |
Expected result |
The subscriber picks up the phone. |
The subscriber hears the dial tone. |
The subscriber dials the automatic operator number. |
If the automatic operator number does not exist, the subscriber hears the voice prompt “Sorry, the subscriber you dialed does not exist.” If the automatic operator number is configured, the subscriber hears the administrator-configured the voice prompt, prompting for two-stage dialing. |
The subscriber dials the short number + # following the voice prompt. |
The subscriber hears the voice prompt “The call is being processed. Please hold on.” and then the waiting tone. The called phone rings. |
Table 22-2 Configure the basic information of the automatic operator service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-SRV view. |
service |
— |
Configure the automatic operator number. |
auto-operator number-of-auto-operator |
Required |
Configure the access voice prompt of the automatic operator service. |
prompt media-id |
Required |
Configure the operational code/phone number bindings. |
extension corresponding-number corresponding-number-of-extension |
Required |
& Note:
l When configuring the automatic operator number, make sure that it does not conflict with the subscriber line number, the static route number, the ONLY number and the group notification number.
l The automatic operator number must be a number already exists on the XE IP PBX.
Add the automatic operator number 8000 on the XE IP PBX. A subscriber that dials 8000 will hear the voice prompt (in media resource file 10010.wav) will be played. Then the subscriber can dial 1 to call subscriber 8802, or dial 2 to call 8803.
& Note:
Refer to the network diagram in Network Diagram.
1) Configure basic parameters on the XE IP PBX.
2) Configure basic parameters of gateways GW01, GW02, and GW03.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
# Add the automatic operator number 8000 on the XE IP PBX.
<XE>system-view
[XE]location-server
[XE-ls]service
[XE-ls-srv]auto-operator 8000
[XE-ls-srv-ao-8000]prompt 10010
[XE-ls-srv-ao-8000]extension 1 8802
[XE-ls-srv-ao-8000]extension 2 8803
# Specify the file to be related with ringback tone index 10010.
<XE>system-view
[XE]media-ability
[XE-ma]language Chinese
[XE-ma-Chinese]format G711a
[XE-ma-Chinese-G711a]set-media 10010 /g711wav/10010.wav
As a group-oriented phone broadcast notification service, the group notification service sends notification to all members in a group by phone calls. The XE IP PBX implements the group notification service through voice notification played locally or remotely.
The administrator defines a local group notification task. When the preset time comes, the XE IP PBX will automatically initiate a call to all subscribers in the specified group. The callees can pick up their phones and listen to the notification played by the XE IP PBX.
To define a task, the administrator needs to specify the following parameters:
l Media file for the task.
l Time when the notification is sent.
l Duration of the local group notification.
l Receiver group of the notification.
l Access code receivers use to hear the notification.
l Interval at which the notification is sent again if it fails.
Subscribers that miss the notification can dial the access code to listen to the notification after the task is executed.
To use the local group notification service, you need to enable the MS on the XE IP PBX.
The local group notification service allows an anonymous subscriber to be a member of the notification group, but the anonymous subscriber has no ability to use the access code to listen to the notification.
The administrator defines a remote group notification task. When the task is started, the notification deliverer can dial the access code to invite all receivers in the specified group to receive the notification. After any receiver picks up the phone, the deliverer can start sending the notification. When the notification is played, phones that are not picked up will keep ringing. The corresponding subscribers can pick up the phone to listen to the notification.
If a subscriber hangs up when listening to the notification, a subscriber can resume notification-listening by dialing the access code.
However, after the deliverer hangs up, all receivers stop receiving the notification and none of them can listen to it again by dialing the access code.
The remote group notification service allows an anonymous subscriber to be a member of the notification group, but the anonymous subscriber has no ability to use the access code to listen to the notification. The notification deliverer must not be an anonymous subscriber.
To use the group notification service, you need to enable the MS on the XE IP PBX first. Otherwise, the service will be unavailable and the deliverer will hear the busy tone after picking up the phone and dialing the access code.
1) Store the media file pre-recorded for the group notification service into the Flash memory of the XE IP PBX.
2) Configure media ID for the file. Refer to the “Configuring a Media Resource” part in the Media Server Operation module for details.
3) Configure the receiver group. Refer to Configuring Notification Receiver Group for details.
4) Set the local group notification parameters, including specifying the media file ID, notification time, receiver group, access code and notification retry interval. Then activate this notification.
5) When the notification time comes, the phone sets of all members in the specified group ring.
6) The subscribers pick up the phones and listens to the notification.
7) If a subscriber does not picks up the phone, the phone rings again after the predefined interval, so that the subscriber can pick up the phone and receive the notification. The phone rings up to 10 times if it is not picked up.
8) If a subscriber hangs up when listening to the notification, the XE IP PBX will not send invitation to that subscriber again because it considers the subscriber has completed receiving the notification.
9) After the notification is completed, subscribers can listen to it again by dialing the access code the administrator designated for the notification.
1) Configure the receiver group. Refer to Configuring Notification Receiver Group for details.
2) Set the remote group notification parameters, including specifying the receiver group, access code and notification sending interval. Then start this notification task. Refer to Configuring Remote Group Notification for details.
3) The notification deliverer picks up the phone, dials the notification-delivering access code, and listens to the music on hold until the receivers pick up their phones.
4) As any receiver picks up the phone, the music on hold stops and the deliverer can start sending the notification. Any phone set not picked up keeps ringing.
5) If a subscriber does not pick up the phone, the phone rings again after the predefined interval, provided that the notification is still being played. The subscriber can pick up the phone and receive the notification. The phone rings up to 10 times if it is not picked up.
6) If a subscriber hangs up when listening to the notification, the XE IP PBX will not send invitation to that subscriber again because it considers the subscriber has completed receiving the notification.
7) When the notification is being played, members in the receiver group can hear the notification by dialing the corresponding access code. However, once the notification sending is completed, receivers cannot listen to it again by dialing the access code..
Table 23-1 Configure a notification receiver group
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-SRV view. |
service |
— |
Enter group notification view. |
group-notify |
— |
Enter a group view, or create a group and enter its group view if the specified group does not exist. |
group-config group-id |
Required |
Add a member to the group. |
member number |
Required |
& Note:
l Only one notification can be configured for each group at the same time to avoid confliction.
l If country codes and area codes are configured on the XE IP PBX and the XE IP PBX needs to use them, the number of a group member must be a long number containing a country code and area code.
l The number of a notification group member must be a number that already exists on the XE IP PBX.
l If a subscriber has multiple numbers, the number with the first priority will be used. If these numbers are of the same priority, the number that is configured first will be used.
Table 23-2 Configure a local group notification
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-SRV view. |
service |
— |
Enter group-notify view. |
group-notify |
— |
Create a group notification and enter its notify-config view. |
notify-config notify-id |
Required |
Configure basic parameters of a local group notification. |
config local media-id callee-access-number interval-of-callee |
Required |
Specify the format of the media file used for a local group notification. |
format format |
Optional |
Add a receiver group. |
join group-id |
Required |
Exit from notify-config view. |
quit |
— |
Activate a group notification. |
start notify-id [ notify-time ] [ duration-of-notify ] |
Required |
Table 23-3 Configure a remote group notification
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-SRV view. |
service |
— |
Enter group-notify view. |
group-notify |
— |
Create a group notification and enter its group-notify view. |
notify-config notify-id |
— |
Configure a remote group notification. |
config remote caller-access-number callee-access-number interval-of-callee |
Required |
Specify the format of the media file used for a remote group notification |
format format |
Optional |
Add a receiver group for a remote group notification. |
join group-id |
Required |
Exit the group-notify view. |
quit |
— |
Activate a group notification. |
start notify-id |
Required |
& Note:
When configuring a group notification number, make sure that it does not conflict with the subscriber line number, the static route number, the ONLY number and the automatic operator number.
Enable the callback-on-busy service for subscriber 8801 under GW01.
Create a local group notification task named ntl, with the following parameters:
l Codec type: G711a.
l Receiver group of the notification: group1, which contains subscribers 8801 and 8802.
l Media file that the task plays: 1010.wav
l Access code that receivers use to hear the notification: 5555.
l Interval for resending notification if it fails: 60 seconds.
& Note:
Refer to the network diagram in Network Diagram.
1) Configure basic parameters on the XE IP PBX.
2) Configure basic parameters of gateways GW01, GW02, and GW03.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
<XE>system-view
[XE]location-server
[XE-ls]service
[XE-ls-srv]group-notify
[XE-ls-srv-gn]group-config group1
[XE-ls-srv-gn-gc-group1]member 8801
[XE-ls-srv-gn-gc-group1]member 8802
[XE-ls-srv-gn-gc-group1]return
<XE>system-view
[XE]location-server
[XE-ls]service
[XE-ls-srv]group-notify
[XE-ls-srv-gn]notify-config ntl
[XE-ls-srv-gn-nc-ntl]format G711a
[XE-ls-srv-gn-nc-ntl]join group1
[XE-ls-srv-gn-nc-ntl]config local 1010 5555 1
[XE-ls-srv-gn-nc-ntl]quit
[XE-ls-srv-gn]start ntl
[XE-ls-srv-gn]return
<XE>
If one party in an active call enjoys the call transfer right, this party can transfer the call to a specified third party, so that a new call is set up between the third party and the other party of the original call. The party who initiated the call transfer exits the call. The phone of the third party rings, and the third party can start a conversation with the other party of the original call after picking up the phone.
For example, subscriber A calls subscriber B, who has the call transfer right, and B answers the call to have a conversation with A. During the call, B dials the access code to transfer the call to subscriber C. B exits the call and hears the busy tone. Then C’s phone rings, and A hears a voice prompt and the music on hold. C picks up the phone to have a conversation with A.
If the CLIP service is enabled for subscriber C, A’s phone number will be displayed on C’s phone. If C is busy, the call transfer fails, and both A and B will hear the busy tone.
To use the call transfer service:
l MS should be enabled on the XE IP PBX first. Otherwise, call transfer will fail and the ongoing call will continue.
l Out-band dialing support is required.
By default, the call transfer service is disabled.
Before a subscriber can use the call transfer service, an administrator must enable the service for that subscriber. Refer to Call Transfer Service Configuration for operation details.
Use the call transfer service as follows:
Table 24-1 Use the call transfer service
Step |
Expected result |
Subscriber A dials the phone number of subscriber B. |
B’s phone rings. |
B picks up the phone. |
Subscribers A and B start a conversation. |
B dials *12* + subscriber C’s phone number + #. |
If B has the call transfer right, C’s phone will ring and B hears the busy tone. A hears the voice prompt “The call is being transferred, please wait.” and the music on hold. If B does not have the call transfer right, the call transfer fails and the call between A and B continues. |
Subscriber C picks up the phone. |
Subscribers A and C start a conversation. |
You can configure the call transfer service in subscriber number view, LS-GW-PREFIX view or LS-OG-PREFIX view. Configuration procedure is as follows.
Table 24-2 Enable/disable the call transfer service
Operation |
Command |
Description |
Enable/disable the call transfer service |
srv-switch ct { on | off } |
Required |
& Note:
To configure the call transfer service on different office devices, you are recommended to enable the call transfer service for the subscriber either in the local subscriber number view or on the peer device.
Enable the call transfer service for subscribers 8801, 8802 and 8803, so that they can transfer calls to each other.
& Note:
Refer to the network diagram in Network Diagram.
1) Configure basic parameters on the XE IP PBX.
2) Configure basic parameters of gateways GW01, GW02, and GW03.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
<XE>system-view
[XE]location-server
[XE-ls]gateway GW01
[XE-ls-gw-GW01]subscriber #1 8801
[XE-ls-gw-GW01 #1 8801]srv-switch ct on
[XE-ls-gw-GW01 #1 8801]return
<XE>system-view
[XE]location-server
[XE-ls]gateway GW02
[XE-ls-gw-GW02]subscriber #1 8802
[XE-ls-gw-GW02 #1 8802]srv-switch ct on
[XE-ls-gw-GW02 #1 8802]return
<XE>system-view
[XE]location-server
[XE-ls]gateway GW03
[XE-ls-gw-GW03]subscriber #1 8803
[XE-ls-gw-GW03 #1 8803]srv-switch ct on
[XE-ls-gw-GW03 #1 8803]return
<XE>
With the number query service, a subscriber can dial the corresponding access code to query its own number.
To use the number query service, you need to enable the MS on the XE IP PBX first. Otherwise, a subscriber will hear the busy tone when attempting to use this service.
1) An authorized administrator logs on to the XE IP PBX and enables the number query service for the subscriber. Refer to Number Query Service Configuration for operation details.
2) The subscriber dials the access code *92#. Refer to Use number query service for details.
3) The subscriber hears the voice prompt “Your number is XXXX”.
Table 25-1 Use the number query service on the phone
Step |
Expected result |
The subscriber picks up the phone. |
The subscriber hears the dial tone. |
The subscriber dials *92#. |
If the number query service is enabled for the subscriber, the subscriber hears the voice prompt “Your number is XXXX.” If the native number query service is disabled for the subscriber, the subscriber hears the voice prompt “Sorry, the service is not available.” |
The subscriber hangs up. |
— |
Table 25-2 Enable/disable the number query service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-GW view. |
gateway device-id |
— |
Enter subscriber number view. |
subscriber short-number long-number |
— |
Enable/disable the number query service. |
srv-switch query-self { on | off } |
Required |
& Note:
This command can also be executed in LS-GW-PREFIX view.
Enable the number query service for subscribers 8801, 8802 and 8803.
& Note:
Refer to the network diagram in Network Diagram.
1) Configure basic parameters on the XE IP PBX.
2) Configure basic parameters of gateways GW01, GW02, and GW03.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
<XE>system-view
[XE]location-server
[XE-ls]gateway GW01
[XE-ls-gw-GW01]subscriber #1 8801
[XE-ls-gw-GW01 #1 8801]srv-switch query-self on
[XE-ls-gw-GW01 #1 8801]return
<XE>system-view
[XE]location-server
[XE-ls]gateway GW02
[XE-ls-gw-GW02]subscriber #1 8802
[XE-ls-gw-GW02 #1 8802]srv-switch query-self on
[XE-ls-gw-GW02 #1 8802]return
<XE>system-view
[XE]location-server
[XE-ls]gateway GW03
[XE-ls-gw-GW03]subscriber #1 8803
[XE-ls-gw-GW03 #1 8803]srv-switch query-self on
[XE-ls-gw-GW03 #1 8803]return
<XE>
With the alarm clock service enabled, a subscriber can set an alarm clock task so that the XE IP PBX calls the subscriber at the specified time.
Each subscriber can set one alarm clock task (to minute) only.
The alarm clock task falls into two types: one-off alarm and cyclic alarm, corresponding to the parameter values “once” and “cycle” respectively.
l Once: The alarm clock goes off only once. The subscriber needs to specify the date and time. The date defaults to the current day if not specified. The specified time must be later than the current system time.
l Cycle: This type of alarm clock goes off once every day. When setting the alarm clock service, the subscriber needs to set only the time, at which the alarm clock goes off every day.
To use the alarm clock service, you need to enable the MS on the XE IP PBX first.
The alarm clock service works as follows:
1) An authorized administrator logs on to the XE IP PBX and enables the alarm clock service for the subscriber. Refer to Enabling/Disabling Alarm Clock Service for a Subscriber for operation details.
2) Set the alarm clock. The alarm clock can be set through any of the following ways:
l On the phone terminal. Refer to Set cyclic alarm clock task on subscriber’s phone set and Set one-off alarm clock task on subscriber’s phone set for details.
l On the XE IP PBX through command lines. Refer to Setting Alarm Clock Task through Command Lines on XE IP PBX for details.
l Through GUI of the XE IP PBX. Refer to H3C XE 200/2000 IP PBX G-Remote User Manual for details.
3) The subscriber’s phone rings at the set time.
4) The subscriber picks up the phone and hears the voice prompt “Hello, this is the alarm clock you set.”
5) In the case of a one-off alarm clock task, the XE IP PBX automatically deletes it. In the case of a cyclic alarm clock task, the XE IP PBX does not delete it.
A subscriber can set a cyclic alarm by dialing the access code *93*0*. Operation steps are listed in Table 26-1.
Table 26-1 Set cyclic alarm clock task on the subscriber’s phone set
Step |
Expected result |
The subscriber picks up the phone. |
The subscriber hears the dial tone. |
The subscriber dials *93*0* + alarm time + #. |
If the subscriber is enabled with the alarm service, it hears the voice prompt “You have successfully activated the service.” If the subscriber is not enabled with the alarm service, it hears the voice prompt “Sorry, the service is not available.” The alarm uses the 24-hour time format, which consists of two digits for the hour and minute respectively. For example, twenty past two o’clock p.m. is represented as 1420. To set a cyclic alarm at this time, dial *93*0*1420#. |
The subscriber hangs up. |
— |
A subscriber can set a one-off alarm by dialing the access code *93*1*. Operation steps are listed in Table 26-1.
Table 26-2 Set one-off alarm clock task on the subscriber’s phone set
Step |
Expected result |
The subscriber picks up the phone. |
The subscriber hears the dial tone. |
The subscriber dials *93*1* + alarm date + alarm time + # or *93*1* + alarm time + #. |
If the subscriber is enabled with the alarm service, it hears the voice prompt “You have successfully activated the service.” If the subscriber is not enabled with the alarm service, it hears the voice prompt “Sorry, the service is not available.” The alarm date is optional. It defaults to the current day if not specified. The date is set in the YYYYMMDD format, for example, set as 20050201 for 1st February 2005. The time must be set in the 24-hour format, with the hour and minute consisting of two digits each. For example, twenty past two o’clock p.m. is represented as 1420. |
The subscriber hangs up. |
— |
For a one-off alarm clock task, the XE IP PBX deletes it after it goes off. However, the subscriber can deletes it manually by dialing the access code before it goes off. For a cyclic alarm clock task, the subscriber always needs to delete it, but if it is not needed, manually by dialing the access code, because the XE IP PBX does not delete cyclic alarm clock tasks automatically.
Table 26-3 Delete an alarm clock task on the phone terminal
Step |
Expected result |
The subscriber picks up the phone. |
The subscriber hears the dial tone. |
The subscriber dials #93#. |
If the subscriber is not enabled with the alarm service, it hears the voice prompt “Sorry, the service is not available.” If the subscriber is enabled with the alarm service and an alarm is set, it hears the voice prompt “You have successfully deactivated the service.” If the subscriber is enabled with the alarm service but no alarm is set, it hears the voice prompt “Sorry, the service you cancel does not exist.” |
The subscriber hangs up. |
— |
Table 26-4 Enable/disable the alarm clock service
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-GW view. |
gateway device-id |
— |
Enter subscriber number view. |
subscriber short-number long-number |
— |
Enable/disable the alarm clock service. |
srv-switch alarm { on | off } |
Required |
Table 26-5 Set an alarm clock task through command lines on the XE IP PBX
Operation |
Command |
Description |
Enter system view. |
system-view |
— |
Enter LS view. |
location-server |
— |
Enter LS-GW view. |
gateway device-id |
— |
Enter subscriber number view. |
subscriber short-number long-number |
— |
Enter alarm clock view. |
alarm |
— |
Set an alarm clock task. |
alarm { { date time } | { time { once | cycle } } } |
Required |
& Note:
The alarm clock setting can not be modified once it is set. To modify an alarm clock, you need to delete it first and re-configure an alarm clock through the command line or on a phone.
Add an alarm clock task for subscriber 8801 under GW01, with the alarm time being 12:30 everyday.
Add an alarm clock task for subscriber 8802 under GW02, with the alarm date being 2006.11.20 and alarm time being 12:30.
& Note:
Refer to the network diagram in Network Diagram.
1) Configure basic parameters on the XE IP PBX.
2) Configure basic parameters of gateways GW01, GW02, and GW03.
& Note:
Refer to Configuration Example for the basic parameter settings.
3) Configure service parameters on the XE IP PBX.
<XE>system-view
[XE]location-server
[XE-ls]gateway GW01
[XE-ls-gw-GW01]subscriber #1 8801
[XE-ls-gw-GW01 #1 8801]srv-switch alarm on
[XE-ls-gw-GW01 #1 8801]alarm
[XE-ls-gw-GW01 #1 8801-alarm]alarm 12:30 cycle
[XE-ls-gw-GW01 #1 8801-alarm]return
<XE>system-view
[XE]location-server
[XE-ls]gateway GW02
[XE-ls-gw-GW01]subscriber #1 8802
[XE-ls-gw-GW02 #1 8802]srv-switch alarm on
[XE-ls-gw-GW02 #1 8802]alarm
[XE-ls-gw-GW02 #1 8802-alarm]alarm 2006/11/20 12:30
[XE-ls-gw-GW02 #1 8802-alarm]return
<XE>
Caution:
When configuring the numbers for services on the XE IP PBX, make sure they do not conflict with the call service access codes listed below. Otherwise, it may cause the malfunction of the XE IP PBX.
Table 27-1 List of call service access codes
Access code |
Access code format |
Service |
Function |
*40* |
*40*ABCD# |
CFB service |
Configures the destination number for call forwarding. |
*#40* |
*#40* |
CFB service |
Verifies the destination number of the CFB service on the phone terminal. |
#40# |
#40# |
CFB service |
Deletes all destination numbers of the CFB service. |
*41* |
*41*ABCD# |
CFNR service |
Configures the destination number of the CFNR service. |
*#41* |
*#41* |
CFNR service |
Verifies the destination number of the CFNR service. |
#41# |
#41# |
CFNR service |
Deletes all destination numbers of the CFNR service. |
*45* |
*45*ABCD# |
CFO service |
Configures the destination number of the CFO service. |
*#45* |
*#45* |
CFO service |
Verifies the destination number of the CFO service. |
#45# |
#45# |
CFO service |
Deletes all destination numbers of the CFO service. |
*47* |
*47*ABCD*EFGH# |
CFC service |
Sets the destination number of the CFC service. |
*#47* |
*#47* |
CFC service |
Verify the target number of the CFC service |
#47# |
#47# |
CFC service |
Deletes all the forward numbers of the CFC service. |
*51* |
*51*MN*ABCD# |
Abbreviated dialing service |
Adds an abbreviated dialing item. |
#51# |
#51# |
Abbreviated dialing service |
Deletes the specified abbreviated dialing item. |
*541* |
*541*PWD0*PWD1*PWD1# |
Password call service |
Modifies the password of the password call service. |
*56# |
*56# |
Do-not-disturb service |
Registers for the do-not-disturb service. |
#56# |
#56# |
Do-not-disturb service |
Deregisters the do-not-disturb service. |
*57* |
*57*ABCD# |
CFU service |
Configures the destination number of the CFU service. |
*#57* |
*#57* |
CFU service |
Verifies the specified destination number that is configured. |
#57# |
#57# |
CFU service |
Deletes all destination numbers of the CFU service. |
*61# |
*61# |
CLIR service |
Registers for the CLIR service. |
#61# |
#61# |
CLIR service |
Deregisters the CLIR service. |
*62# |
*62#ABCD |
Temporary reservation for CLIR |
Registers the temporary reservation for CLIR service. |
*59# |
*59# |
Callback-on-busy service |
Registers for the callback-on-busy service. |
#59# |
#59# |
Callback-on-busy service |
Deregisters the callback-on-busy service. |
*11* |
*11*ABCD# |
Call pickup service |
Specifies the access code for the call pickup service. |
*89* |
*89*ABCD# |
Call intervention service |
Specifies the access code for the call intervention service. |
*89# |
*89# |
Call intervention service |
Resumes the original call when ending the current call. |
*90* |
*90*0# |
Time announcement service |
Queries the current time. |
*91# |
*91# |
CPCP service |
Asks for call parking. |
*91* |
*91*ABCD# |
CPCP service |
Restores the call. |
*12* |
*12*ABCD# |
Call transfer service |
Transfers the current call. |
*92# |
*92# |
Number query service |
Queries the native number. |
*93* |
*93*0*HHMM# |
Alarm clock service |
Configures a periodic alarm clock task. |
*93* |
*93*1*YYYYMMDDHHMM# or *93*1*HHMM# |
Alarm clock service |
Configures a one-off alarm clock task. |
#93# |
#93# |
Alarm clock service |
Deletes the existing alarm clock task. |
& Note:
In the table above, ABCD and EFGH stand for the subscriber numbers, MN for the abbreviated number, PWD0 and PWD1 for the passwords, HHMM for the time and YYYYMMDDHHMM for the date and time.
Table 27-2 Media IDs reserved for voice prompts and related file names
Media ID |
Media file name |
Voice prompt |
0 |
0.wav |
"Zero" |
1 |
1.wav |
"One" |
2 |
2.wav |
"Two" |
3 |
3.wav |
"Three" |
4 |
4.wav |
"Four" |
5 |
5.wav |
"Five" |
6 |
6.wav |
"Six" |
7 |
7.wav |
"Seven" |
8 |
8.wav |
"Eight" |
9 |
9.wav |
"Nine" |
10 |
10.wav |
"Ten" |
11 |
11.wav |
"Eleven" |
12 |
12.wav |
"Twelve" |
13 |
13.wav |
"Thirteen" |
14 |
14.wav |
"Fourteen" |
15 |
15.wav |
"Fifteen" |
16 |
16.wav |
"Sixteen" |
17 |
17.wav |
"Seventeen" |
18 |
18.wav |
"Eighteen" |
19 |
19.wav |
"Nineteen" |
20 |
20.wav |
"Twenty" |
21 |
21.wav |
"Thirty" |
22 |
22.wav |
"Forty" |
23 |
23.wav |
"Fifty" |
24 |
24.wav |
"Sixty" |
25 |
25.wav |
"Seventy" |
26 |
26.wav |
"Eighty" |
27 |
27.wav |
"Ninety" |
28 |
28.wav |
"A" |
29 |
29.wav |
"B" |
30 |
30.wav |
"C" |
31 |
31.wav |
"D" |
32 |
32.wav |
"The asterisk key" |
33 |
33.wav |
"The pound key" |
34 |
34.wav |
"January" |
35 |
35.wav |
"February" |
36 |
36.wav |
"March" |
37 |
37.wav |
"April" |
38 |
38.wav |
"May" |
39 |
39.wav |
"June" |
40 |
40.wav |
"July" |
41 |
41.wav |
"August" |
42 |
42.wav |
"September" |
43 |
43.wav |
"October" |
44 |
44.wav |
"November" |
45 |
45.wav |
"December" |
46 |
46.wav |
"Hundred" |
47 |
47.wav |
"Thousand" |
48 |
48.wav |
"Year" |
49 |
49.wav |
"Month" |
50 |
50.wav |
"Date" |
51 |
51.wav |
"Hour" |
52 |
52.wav |
"Minute" |
1000 |
1000.wav |
“You have successfully activated the service.” |
1001 |
1001.wav |
“Sorry, your attempt to activate the service was unsuccessful.” |
1002 |
1002.wav |
“The service is being processed. Please wait.” |
1003 |
1003.wav |
“You have successfully deactivated the service.” |
1004 |
1004.wav |
“Sorry, your attempt to deactivate the service was unsuccessful.” |
1005 |
1005.wav |
“You have already activated the service.” |
1006 |
1006.wav |
“You have not activated the service.” |
1007 |
1007.wav |
“You have not activated the service.” |
1008 |
1008.wav |
“Sorry, the service is not available.” |
1009 |
1009.wav |
“Sorry, the operation fails.” |
1010 |
1010.wav |
Music on hold |
3800 |
3800.wav |
“The third party call control service is in operation. Please hold on.” |
3900 |
3900.wav |
“Sorry, you do not have the necessary permission to activate the service.” |
3903 |
3903.wav |
“The callback-on-busy service is in operation. Please hold on.” |
3904 |
3904.wav |
“It is subscriber” |
3905 |
3905.wav |
“With the callback-on-busy. Please wait.” |
3906 |
3906.wav |
“Sorry, your call was not successful.” |
4200 |
4200 wav |
“Sorry, your call was not successful.” |
4201 |
4220.wav |
“Sorry, your call was not successful.” |
4202 |
4220.wav |
“Sorry, your call was not successful.” |
4203 |
4220.wav |
“Sorry, your call was not successful.” |
4204 |
4220.wav |
“Sorry, your call was not successful.” |
4205 |
4220.wav |
“Sorry, your call was not successful.” |
4206 |
4220.wav |
“Sorry, your call was not successful.” |
4207 |
4220.wav |
“Sorry, your call was not successful.” |
4208 |
4220.wav |
“Sorry, your call was not successful.” |
4209 |
4209.wav |
“Sorry, the subscriber you dialed does not exist.” |
4210 |
4210.wav |
“Sorry, the subscriber you dial is using do-not disturb.” |
4211 |
4211.wav |
“Sorry, you are not allowed to call this number.” |
4212 |
4212.wav |
“Sorry, you are not allowed to make a call.” |
4213 |
4213.wav |
“Sorry, the subscriber you dialed is not allowed to answer the call.” |
4214 |
4214.wav |
“Sorry, your password is not correct.” |
4215 |
4212.wav |
“Sorry, you are not allowed to make a call.” |
4216 |
4212.wav |
“Sorry, your call was not successful.” |
4217 |
4212.wav |
“Sorry, your call was not successful.” |
4218 |
4212.wav |
“Sorry, your call was not successful.” |
4219 |
4212.wav |
“Sorry, your call was not successful.” |
4220 |
4220.wav |
“Sorry, your call was not successful.” |
4221 |
4221.wav |
“Sorry, the subscriber you dialed is busy now, please try later.” |
4222 |
4222.wav |
“Sorry, the subscriber you dialed is not reachable, please try later.” |
4223 |
4223.wav |
“Sorry, your call was not successful.” |
4224 |
4224.wav |
“Sorry, your call was not successful.” |
4225 |
4225.wav |
“Sorry, your call was not successful.” |
4300 |
4300.wav |
“Hello, this is the maintenance center. We are testing the line. Thank you for your cooperation.” |
4401 |
4401.wav |
“The connection code to restore the call is” |
4500 |
4500.wav |
“Hello, your call is being operated. Please wait.” |
4502 |
4502.wav |
“Sorry, the subscriber has hung up the phone.” |
4503 |
4503.wav |
“Sorry, the call is terminated by the administrator.” |
4600 |
4600.wav |
“The call is being transferred. Please wait.” |
4700 |
4700.wav |
“The current time is” |
4900 |
4900.wav |
“The call is being processed. Please hold on.” |
5101 |
5101.wav |
“You can talk now.” |
5200 |
5200.wav |
“Your number is” |
5300 |
5300.wav |
“Hello, this is the alarm clock you set.” |
5400 |
5400.wav |
“You have already activated” |
5401 |
5401.wav |
”Call forwarding on busy service. Your forward number is” |
5402 |
5402.wav |
“Call forwarding no reply service. Your forward number is” |
5403 |
5403.wav |
“Call forwarding offline service. Your forward number is ” |
5404 |
5404.wav |
“Call forwarding based on the caller number service. You forward number is” |
5405 |
5405.wav |
“Call forwarding unconditional service. Your forward number is” |
5406 |
5406.wav |
— |
5407 |
5407.wav |
“Your number is” |
5408 |
5408.wav |
“The connection code to restore the call is” |
5409 |
5409.wav |
“Sorry, you have no forward number.” |
This manual presents different call services the XE IP PBX supports and also introduces how to use them. In practice, subscribers may simultaneously use multiple call services. Nesting of these call services may lead to a conflict. This section describes the processing mechanism of the XE IP PBX when a subscriber simultaneously uses two call services.
Table 27-3 Nested relationship between two call services
Service 1 |
Service 2 |
Nested relationship |
Third party call control |
Multiple called parties |
Both simultaneous and orderly ringing of multiple called parties is supported. |
ONLY |
The ONLY service is supported. |
|
Subscriber management |
If either of the two parties in a conversation uses the incoming call barring service, the third party call control service will fail. |
|
Inter-group call restriction |
The inter-group call restriction service is supported. |
|
Outgoing call authority control |
The outgoing call authority control service is supported. |
|
Abbreviated dialing |
The abbreviated dialing service is supported. |
|
Do-not-disturb |
The do-not-disturb service is supported. |
|
CLIP |
The calling line identification presentation (CLIP) service is supported. If the CLIP service is enabled for both parties, “00000000” will be displayed on the phone which rings first. |
|
Time limit call |
The time limit call service is supported. |
|
Call forwarding |
All call forwarding services are supported. |
|
Callback-on-busy |
The callback-on-busy service is not supported. |
|
Call pickup |
The call pickup service is supported. |
|
Call interception |
The call interception is not supported. |
|
CPCP |
The call park and call pickup (CPCP) service is supported only after a call is established between both parties. |
|
Call intervention |
The call intervention service is not supported when the called party is being alerted or when the called party has picked up the phone but is not in a conversation. |
|
Call transfer |
The call transfer service is not supported for the connected party before the call established. |
|
MyRing |
The MyRing service is not supported. |
|
Automatic operator |
The automatic operator number must not be the number of either party who uses the third party call control service. |
|
Group notification |
The group notification number must not be the number of either party who uses the third party call control service. |
|
Callback-on-busy |
Multiple called parties |
Both simultaneous and orderly ringing of multiple called parties is supported. |
Subscriber management |
The callback-on-busy service will succeed if the incoming call barring is enabled for the calling party, and will fail if the incoming call barring is enabled for the called party. |
|
Inter-group call restriction |
The inter-group call restriction service is supported. |
|
Outgoing call authority control |
The outgoing call authority control service is supported for the calling party. |
|
Abbreviated dialing |
The abbreviated dialing service is supported. |
|
Do-not-disturb |
If both the callback-on-busy service and the do-not-disturb service are enabled for a called subscriber, attempts will not be made to call the called subscriber until the attempts are exceeded. The do-not-disturb service is not applicable to the calling subscriber. |
|
CLIP |
The CLIP service is supported. |
|
Time limit call |
The time limit call service is supported. |
|
Password call |
The password call service is applicable to the calling party. |
|
Call forwarding |
The call forwarding services are applicable to the called party, instead of the calling party. |
|
Call pickup |
The call pickup service is locally supported. |
|
Dialing test |
The dialing test service takes precedence over the callback-on-busy service. Meanwhile, the enabled callback-on-busy service will be disabled. |
|
CPCP |
The call park/call pickup (CPCP) service is supported after a call is established between both parties. |
|
Call intervention |
The call intervention service takes precedence over the callback-on-busy service. Meanwhile the enabled callback-on-busy service will be disabled. |
|
Call transfer |
The call transfer service is supported. |
|
MyRing |
The MyRing service is not supported. |
|
Call pickup |
Multiple called parties |
The multiple called parties service is supported when they are registered with the local XE IP PBX. |
Subscriber management |
The subscriber management service is supported. |
|
|
Inter-group call restriction |
The call pickup service is only restricted by the call restriction relationship in the direction from the calling party to the party with the call pickup right. |
Outgoing call authority control |
The call pickup service is restricted by the outgoing call authority from the calling party to the party with the call pickup right on the local XE IP PBX. |
|
Abbreviated dialing |
The abbreviated dialing service is supported. |
|
Do-not-disturb |
The call pickup service is not restricted by the do-not-disturb service. |
|
Time limit call |
The time limit call service is supported. |
|
Password call |
The call pickup service is not restricted by the password call service. |
|
Call forwarding |
The call pickup service is applicable to the forwarded-to number of all call forwarding services. |
|
Third party call control |
The call pickup service is applicable to a call locally originated by using the 3PCC service. |
|
Callback-on-busy |
The call pickup service is applicable to a call originated by using the callback-on-busy service only on the local XE IP PBX. |
|
Dialing test |
The dialing test service is supported. |
|
CPCP |
The CPCP service is supported. |
|
Call intervention |
The call intervention service takes precedence over the call pickup service. That is, the alerted party involved in the call intervention service does not support the call pickup service. |
|
Call transfer |
The call pickup service is applicable to an ordinary call locally originated by using the call transfer service. |
|
MyRing |
The MyRing service is supported. |
|
Automatic operator |
The call pickup service is applicable to a call locally originated by using the automatic operator service. |
|
Group notification |
The call pickup service is not applicable to a call originated by using the group notification service. |
|
Alarm clock |
The alarm clock service is supported. |
|
Dialing test |
Multiple called parties |
The multiple called parties service is supported. |
Subscriber management |
The dialing test service is not restricted by the subscriber user management service. |
|
Do-not-disturb |
The dialing test service is not restricted by the do-not-disturb service. |
|
CLIP |
“00000000” is displayed when the administrator performs a dialing test. |
|
Call forwarding |
None of the call forwarding services is supported. |
|
Call pickup |
The call pickup service is supported. |
|
CPCP |
The CPCP service is not supported. |
|
Call intervention |
The call intervention service is not supported when a subscriber hears the prompt in a dialing test by the administrator. |
|
Call transfer |
The call transfer service is not supported. |
|
Automatic operator |
The dialing test service is not applicable to an automatic operator number. |
|
Group notification |
The dialing test service is not applicable to the access code of the group notification service. |
|
CPCP |
Multiple called parties |
Orderly ringing of multiple ordinary called parties is supported. |
Subscriber management |
The subscriber management service is supported. (Note: If suspended in terms of call origination, a subscriber can put a call on hold by on-hook, but cannot resume the call.) |
|
Inter-group call restriction |
The inter-group call restriction service is not supported. |
|
Outgoing call authority control |
The outgoing call authority control service is not supported. |
|
Time limit call |
The time limit call service is supported. The time is counted once the call is originally connected. |
|
Password call |
The password call service is supported. It is necessary for the subscriber to dial *91* + password + connection number to resume the call. |
|
Call forwarding |
A forwarded-to number must not be the access code of the CPCP service. |
|
Third party call control |
The CPCP service is supported after a call is established between both parties. |
|
Callback-on-busy |
The CPCP service is supported after a call is established between both parties. |
|
Dialing test |
The CPCP is not supported when the administrator performs a dialing test. |
|
Call intervention |
The CPCP service is not applicable to a call established by using the call intervention service. |
|
Time announcement |
The time announcement service takes precedence over the CPCP service. That is, the CPCP service is not supported during time announcement. |
|
MyRing |
The MyRing service is supported. |
|
Automatic operator |
The CPCP service is not supported when a subscriber dials an automatic operator number to hear the system play announcements. |
|
Group notification |
The CPCP service is not supported. |
|
Number query |
The CPCP service is not supported. |
|
Alarm clock |
The CPCP service is not supported. |
|
Call intervention |
Multiple called parties |
The multiple called parties service is supported. The idle subscriber, or the subscriber with the lowest priority if all subscribers are in a conversation, is selected for the call intervention service. |
Subscriber management |
The subscriber management service is not applicable to the called subscriber. |
|
Inter-group call restriction |
The inter-group call restriction service is not supported. |
|
Outgoing call authority control |
The outgoing call authority control service is not supported. |
|
Abbreviated dialing |
The abbreviated dialing service is supported. |
|
Do-not-disturb |
The do-not-disturb service is not supported. |
|
CLIP |
The temporary reservation for CLIR service is not supported. |
|
Time limit call |
The time limit call service is not supported. |
|
Password call |
The password call service is supported. |
|
Call forwarding |
Only the CFO service is supported. |
|
Third party call control |
The call intervention service is not supported when the called party is being alerted or when the called party has picked up the phone but is not in a conversation. |
|
Callback-on-busy |
The call intervention service takes precedence over the callback-on-busy service. However, the call intervention service is not supported when the called party is being alerted or when the called party has picked up the phone but is not in a conversation. |
|
Call pickup |
The call intervention service takes precedence over the call pickup service. That is, the alerted party involved in the call intervention service does not support the call pickup service. |
|
Dialing test |
The dialing test service is not supported. |
|
CPCP |
The CPCP service is not supported. |
|
Call intervention |
The call intervention service does not support nesting. That is, the call intervention service is no longer applicable to a call which itself is established by using the call intervention service. |
|
Call transfer |
The call transfer service is not supported. |
|
Time announcement |
The time announcement service is not supported. |
|
MyRing |
The MyRing service is not supported. |
|
Automatic operator |
The call intervention service is not supported when a subscriber dials an automatic operator number to hear the system play announcements. |
|
Group notification |
The group notification service takes precedence over the call intervention service. That is, the call intervention service is not applicable to a call originated by using the group notification service. |
|
Number query |
The call intervention service is not supported when the XE IP PBX plays announcements. |
|
Alarm clock |
The call intervention service is not supported when the XE IP PBX plays announcements. |
|
Forwarded-to number query |
The call intervention service is not supported when the XE IP PBX plays announcements. |
|
Call transfer |
Multiple called parties |
The call transfer service is applicable to an ordinary call established in the case of orderly ringing of multiple called parties. The call transfer service is also applicable to a multiple-called-parties call established by using a service. |
Subscriber management |
The subscriber management service is supported. |
|
Inter-group call restriction |
The inter-group call restriction service is locally supported. |
|
Outgoing call authority control |
The outgoing call authority control service is locally supported. |
|
Abbreviated dialing |
The abbreviated dialing service is supported. |
|
Do-not-disturb |
The do-not-disturb service is supported. |
|
CLIP |
The CLIP service is supported. |
|
Time limit call |
The time limit call service is supported. |
|
Password call |
The password call service is supported, but no password is required for the call transfer service. |
|
Call forwarding |
All call forwarding services are supported. |
|
Third party call control |
The call transfer service is applicable to a call established by using the 3PCC service. |
|
Callback-on-busy |
The callback-on-busy service is not supported. |
|
Call pickup |
The call pickup service is locally supported. |
|
Call interception function |
The call interception function is not supported. |
|
CPCP |
The CPCP service is supported. |
|
Call intervention |
The call intervention service is applicable to a call established by using the call transfer service. |
|
Call transfer |
The call transfer service is applicable to a call established by using the call transfer service itself. |
|
MyRing |
The MyRing service is not supported. |
|
Automatic operator |
The call transfer service is not applicable to the final-recipient number which is an automatic operator number. |
|
Group notification |
The call transfer service is not applicable to the final-recipient number which is group notification number. |
|
Time announcement |
Subscriber management |
The subscriber management service is supported. |
Outgoing call authority control |
The outgoing call authority control service is supported. |
|
Abbreviated dialing |
The abbreviated dialing service is not supported. |
|
Password call |
No password is required for the time announcement service. |
|
MyRing |
Multiple called parties |
The MyRing service is not supported. |
Abbreviated dialing |
The abbreviated dialing service is supported. |
|
Do-not-disturb |
The do-not-disturb service takes precedence over the MyRing service and the MyRing service fails. |
|
Password call |
The password call service supports the MyRing service. |
|
CFU |
The ringback tone is subjected to the one set for the forwarded-to number. |
|
CFNR |
The ringback tone is subjected to the one set for the original called number. That is, the ringback tone remains unchanged after the call is forwarded. |
|
CFC |
The ringback tone is subjected to the one set for the forwarded-to number. |
|
CFT |
The ringback tone is subjected to the one set for the forwarded-to number. |
|
CFB |
The ringback tones set for the original called number and forwarded-to number both fail and the ordinary ringback tone is played after the call is forwarded. |
|
CFO |
The ringback tone is subjected to the one set for the forwarded-to number. |
|
Call intervention |
The MyRing service is not supported. |
|
Automatic operator |
Multiple called parties |
The multiple called parties service is supported. |
Subscriber management |
Extensions of an automatic operator number support the subscriber management service. |
|
Inter-group call restriction |
Extensions of a calling number and an automatic operator number support the inter-group call restriction service. |
|
Outgoing call authority control |
The outgoing call authority control service is supported. |
|
Abbreviated dialing |
The abbreviated dialing service is applicable to an automatic operator number, but not to extensions. |
|
Do-not-disturb |
Extensions of an automatic operator number support the do-not-disturb service. |
|
CLIP |
The CLIP service is supported. |
|
Time limit call |
The time limit call service is supported. |
|
Password call |
No password is required when a subscriber who uses the password call service dials an extension. |
|
Call forwarding |
All call forwarding services are supported. |
|
Callback-on-busy |
The callback-on-busy service is not supported. |
|
Call pickup |
The call pickup service is supported only when a calling number and extensions of an automatic operator number are registered on the same XE IP PBX. |
|
CPCP |
The CPCP service is supported after a call is established between both parties. |
|
Call intervention |
The call intervention service is not supported when the calling subscriber hears the XE IP PBX play announcements. |
|
Call transfer |
The call transfer service is not supported when the calling subscriber hears the XE IP PBX play announcements. |
|
Time announcement |
The time announcement number cannot be any extension of an automatic operator number. |
|
MyRing |
The MyRing service is not supported. |
|
Automatic operator |
Extensions of one automatic operator number cannot serve as another automatic operator number. |
|
Group notification |
Extensions of an automatic operator number cannot serve as a group notification number. |
|
Number query |
Extensions of an automatic operator number cannot serve as the access code of the local number query service. |
|
Alarm clock |
Extensions of an automatic operator number cannot serve as the access code of the alarm clock service. |
|
Forwarded-to number query |
Extensions of an automatic operator number cannot serve as the access code of the forwarded-to number query service. |
|
Group notification |
Multiple called parties |
The multiple called parties service is supported. |
Subscriber management |
The subscriber management service is not supported when a group notification is sent to called parties. The subscriber management service is supported when a group notification member dials the access code to listen to the notification. |
|
Inter-group call restriction |
The inter-group call restriction service is not supported. |
|
Outgoing call authority control |
The outgoing call authority control service is not supported. |
|
Abbreviated dialing |
The remote group notification service supports the abbreviated dialing service. The subscriber of an abbreviated number is, however, unable to listen to the notification by dialing the access code of the group notification service. |
|
Do-not-disturb |
The do-not-disturb service is not supported. |
|
CLIP |
“00000000” is displayed for the local group notification service. |
|
Time limit call |
The time limit call service is not supported. |
|
Password call |
The password call service is supported. |
|
Call forwarding |
All call forwarding services are supported. The access code of the local group notification service must not be a forwarded-to number. |
|
Call pickup |
The call pickup service is not supported. |
|
CPCP |
The CPCP service is not supported. |
|
Call intervention |
The call intervention service is not applicable to a subscriber who is listening to a group notification played by the XE IP PBX. |
|
Call transfer |
The call transfer service is not supported. |
|
Automatic operator |
An automatic operator number must not be a group notification number. |
|
Number query |
Subscriber management |
The subscriber management service is supported. |
Abbreviated dialing |
The abbreviated dialing service is not supported. |
|
Password call |
No password is required for the local number query service. |
|
CPCP |
The CPCP service is not supported. |
|
Call intervention |
The call intervention service is not supported when the calling subscriber hears the XE IP PBX play announcements. |
|
Call transfer |
The call transfer service is not supported when the calling subscriber hears the XE IP PBX play announcements. |
|
Automatic operator |
The automatic operator service does not support the local number query service. |
|
Alarm clock |
Multiple called parties |
The multiple called parties service is supported. That is, if the alarm clock service is set for one called subscriber, all the other subscribers with the same number on the local XE IP PBX will be alerted. |
Subscriber management |
The subscriber management service is supported. |
|
Do-not-disturb |
The alarm clock service takes precedence over the do-not-disturb service and the do-not-disturb service fails. |
|
CLIP |
“00000000” will be displayed if the CLIP service is enabled for the called subscriber. |
|
Password call |
No password is required for the alarm clock service. |
|
Call forwarding |
None of call forwarding services are supported. |
|
Callback-on-busy |
The callback-on-busy service is not supported. The callback-on-busy service fails. |
|
Call pickup |
The call pickup service is supported. |
|
CPCP |
The CPCP service is not supported. |
|
Call intervention |
The call intervention service is not supported when the calling subscriber hears the XE IP PBX play announcements. |
|
Call transfer |
The call transfer service is not supported when the calling subscriber hears the XE IP PBX play announcements. |
|
Automatic operator |
The alarm clock service is not supported. |