Professional Documents
Culture Documents
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: (86) 755 26771900
Fax: (86) 755 26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2010 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution of
this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATION
or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on the
information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subject
matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,
the user of this document shall not acquire any license to the subject matter herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No.
Revision Date
Revision Reason
R1.0
201007-30
First edition
Contents
DigitMap Configuration......................................9
DigitMap Template Planning ............................................. 9
DigitMap Configuration ...................................................10
Configuring a DigitMap Template .................................10
Configuring a DigitMap ...............................................13
Cases of DigitMap Configuration ......................................15
DigitMap Configuration in an IMS Project of Company
M ....................................................................15
DigitMap Configuration in an NGN Project of Company
T .....................................................................16
Figures ............................................................ 19
Tables ............................................................. 21
Glossary .......................................................... 23
II
Intended
Audience
Prerequisite Skill
and Knowledge
What Is in This
Manual
Conventions
Maintenance engineers;
Data engineers
To use this document effectively, users should have a general understanding of SoftSwitch system.
This manual contains the following chapters:
Chapter
Summary
Chapter 2, DigitMap
Configuration
Meaning
Italics
Quotes
Links on screens.
Bold
CAPS
Typeface
Meaning
Note: Provides additional information about a certain
topic.
Checkpoint: Indicates that a particular step needs to
be checked before proceeding further.
Tip: Indicates a suggestion or hint to make things
easier or more productive for the reader.
II
Typeface
Meaning
Click
Doubleclick
Right-click
Declaration of RoHS
Compliance
To minimize the environmental impact and take more responsibility to the earth we live, this document shall serve as formal declaration that ZXSS10 SS1b manufactured by ZTE CORPORATION
are in compliance with the Directive 2002/95/EC of the European
Parliament - RoHS (Restriction of Hazardous Substances) with respect to the following substances:
Lead (Pb)
Mercury (Hg)
Cadmium (Cd)
II
Chapter
DigitMap Overview
Table of Contents
Overview...........................................................................
DigitMap Grammar .............................................................
DigitMap Flow ....................................................................
DigitMap Cases ..................................................................
1
1
3
5
Overview
DigitMap, or digit collection rule discriptor, is a dialing scheme in a
media gateway. It is used to detect and report the dialing events
received by terminals. The purpose of using DigitMap is to promote
the media gateway's efficiency in sending the number of the called
party. That is to say, if the numbers dialed by users conform to one
of the dialing schemes defined by DigitMap, the media gateway will
send them by one message; If they do not, the media getaway will
release the call directly and play busy tone to the caller.
The format of DigitMap is defined strictly by H.248 and MGCP. It
consists of series of character strings which represent different
meanings. As long as the received digit sequence matches one of
the character strings, the number is considered to be complete.
Generally, SS delivers the configured DigitMaps to specific gateways instead of resoluting them. It is the gateway that resolutes
the DigitMaps and then collects the digits.
DigitMap Grammar
DigitMap can be defined by character strings and character string
lists. The character strings in a character string list are all optional
schemes. They can be groups of numbers, characters, timers or
the combination of any of them. They are used to comprise a
shortest expression that the gateway can match.
It is necessary for DigitMap grammar to support the basic DigitMap
characters but not necessary to support the extended ones.
DigitMap of H.248
The following are the allowed characters contained in H.248 and
their implications.
Digits: From 0 to 9.
Timer:
DTMF: A digit, a timer, or any letter among "A", "B", "C", "D",
"E" and "F". Extended symbols can also be defined.
Caution:
"E" and "F" represent "*" and "#" in DTMF respectively.
Duration symbol: "Z" represents a dialing event which requires longer time. Placed before the symbol(s) designating
the event(s) which satisfy a given digit position, it indicates
that the position is satisfied only if the duration of the event
exceeds the long duration threshold.
Sub-range: Two digits separated by "-". It represents the digits between them (including themselves). A sub-range can only
be applied within a range. In other words, it can only exist in
"[]".
Seprator: "|". It means that every character string is an optional dialing scheme.
DigitMap of MGCP
The following are the allowed characters contained in MGCP and
their implications.
Digits: From 0 to 9.
DTMF: A digit, a timer, or any symbol among "A", "B", "C", "D",
"#" and "*". Extended symbols can also be defined.
Sub-range: Two digits separated by "-". It represents the digits between them (including themselves). A sub-range can only
be applied within a range. In other words, it can only exist in
"[]".
Seprator: "|". It means that every character string is an optional dialing scheme.
DigitMap Flow
H.248 Flow
Before the end of a consecutive dialing event, the processing will
be performed based on the following rules according to H.248.
1. The "current dialing string" is an internal variable which does
not have values initially. The candidate dialing event set includes all the candidate dialing events in a DigitMap.
2. In every step, a timer is set waiting for the next event. The
timer can use the default timing principle, or use the specific
timers in an event or several events. If the set time runs out
and the received digits can fully match a dialing event, the
system will report "Timeout, Full Match (FM in short)". If the
set time runs out and the received digits cannot match a dialing
event, the system will report "Timeout, Partial Match (PM in
short)".
3. If the system detects a dialing event before timeout, this event
will be mapped into a digit characters and be added to the
back of the dialing character string. Only when the duration
time is related to the digit position (because there is at least
one candidate event with a Z at this position), the time will be
recorded.
4. By matching the current dialing character string to the candidate events, only when one dialing event which has the long
duration time can match a candidate event, the other candidate events can be ignored. If the dialing event which has the
long duration time cannot match any candidate events, this dialing event will be ignored. If the dialing event sequence does
not define a long time duration dialing event at a given position, and it remains in the candidate set after the above rules
are applied, this duration of the dialing event will be ignored.
5. If only one candidate event can match the collected digits,
a DigitMap Completion event which features UnambiguousMatch, or UM in short, can be generated. If there are no candidate events matching the collected digits, the latest event
will be removed from the current character string. If there is
one candidate event which can fully match the collected digits
before detecting a dialing event, a Full Match DigitMap Complete event will be generated; If there is no candidate sequence
which can match the collected digits, a Partial Match DigitMap
Complete event will be generated. The dialing events removed
from the character string will be reported according to the activated event processing mechanism. In DigitMap, UM, PM and
FM are explaned in details in DigitMap.
6. If a DigitMap Complete event has not been reported after these
five steps, go back to the second step.
Note:
The flow above is a general flow defined by H.248 protocol. It
is also the gateway processing flow. Since the implementation
details of different gateways can be different, consult the gateway
providers for the details.
MGCP Flow
A gateway follows the following steps to detect and match events
according to digit lists.
1. Add a tag which is represented by an event code to the tail of
"current dial string".
2. Compare the current dialing character string with the digit lists,
trying to match every item in the digit lists.
3. If the matching fails, there will be no further operation.
If one item is matched, or over-qualified, the system will send the
collected digits to the call proxy. The matching in this regulation
involves two conditions, namely "Full Match", which means one
item in the digit list has been matched; "No Match", which means
the collected digits fail to match any of the items in the digit lists.
The unexpected timer events can lead to "No Match". Both "Full
Match" and "Partial Match" can result in the reporting of the collected digits.
Note:
The flow above is a general flow of MGCP. It is also the gateway processing flow. Since the implementation details of different
gateways can be different, consult the gateway providers for the
details.
DigitMap Cases
A Case of H.248 DigitMap
Case One
Service Type
11X
6XXXXXXX
Local number
00
*xx
Supplementary Services
Note
In order to make them easy to understand, here explains the format rules, especially the conditions of using symbols like space
and enter, of all sections by taking the two cases as the examples.
Let us take the second case as an example. "DigitMap =" is a key
word. It can also be written as "DM =". The scheme is named
as Diaplan0. This scheme is a list which consists of 7 character
strings. Each string is separated by "|". Spaces and line feeds are
allowed before or after "|". Therefore, the scheme can be:
DigitMap = Dialplan0{ (0|00|[1-7]xxx|8xxxxxxx|Fxxxxxxx|Exx|9
1xxxxxxxxxx|9011x.)}
Spaces and line feeds are also allowed before or after "()", so are
"[]" and "-". In a character string, spaces and line feeds are not
allowed except at the beginning and end part of it.
The following two DigitMap are incorrect.
DigitMap = Dialplan0{ (0| 00|[1-7]xxx|8xxxxxxx|Fxxxxxxx|Exx|9
1xxxx xxxxxx|9011x.)}. Spaces should be free from the character
string.
DigitMap = Dialplan0{ (0| 00|[1-7]xxx|8xxxxxxx|Fxxxxxxx|Exx|
91xxxxx
xxxxx|9011x.)}. Line feeds are not allowed in a character string.
Cases of UM, PM
and FM
Note:
UM: UnambiguousMatch.
Service Type
Local operator
00
xxxx
8xxxxxxx
Local number
#xxxxxxx
*xx
Asterisk service
91xxxxxxxxxx
Assume
the
DigitMap
is
Chapter
DigitMap Configuration
Table of Contents
DigitMap Template Planning ................................................. 9
DigitMap Configuration .......................................................10
Cases of DigitMap Configuration ..........................................15
Note:
In the H.248 grammar, "E" and "F" represent "*" and "#" in
DTMF respectively.
The following DigitMap templates are some references for you. Before the configuration, modify the templates according to the real
conditions of the region.
Special service
10xxS.|11[02479]|11[13568]Sx.|12[026789]|121xx|12[35]Sx.|168xxxxx|1[79]xSx.|18xSx|200|201|20[29]xSx|400xS.|444S.|600x|800xxxxxxx|9xxxxSx.
New service
[*#][0-9][0-9*].#|**xx|*#xx#|##
DigitMap Configuration
Configuring a DigitMap Template
Prerequisites
Context
Steps
10
11
THE
PARAMETERS
IN
ADDING DIGITMAP
Parameter
Description
Module No.
Remark
Digitmap
String
12
4. Click the OK button to return to the Digitmap Model Configuration page. Then click the Exit button on the Digitmap
Model Configuration page to finish the configuration.
END OF STEPS
Configuring a DigitMap
Prerequisites
Context
Steps
1. Through both of the following two ways, you can enter the
Digit Number Analysis interface, as shown in Figure 4. Table
4 lists the descriptions of the parameters.
On the Configure Management interface, select Service
Manage > Digit Analysis Configuration > DigitMap Configuration to enter the DigitMap Configuration page. Then
click the Add(A) button.
13
select Service
Digit Analysis
Configuration
select > Add
Note:
Please get to the digit analysis page before carrying out this
operation.
TABLE 4 DESCRIPTION
14
OF THE
PARAMETERS
IN
ADDING DIGITMAP
Parameter
Description
Digit
Number
Analysis
Protocol
Type
1MGCP
2H248
9MGCP OverLop
10H248 OverLop
Model 1 to 5
Special
DigitMap
String
Parameter
Description
configured the special DigitMap string, the final
DigitMap is a combination of template character
string and the special DigitMap string. The
template can be used by several DigitMaps. When
configuring the DigitMap corresponds to a DAS, you
can modify, add and delete the DigitMap strings
without modifying the template. In this way, other
Digit Number Analysis will not be affected.
Cases of DigitMap
Configuration
DigitMap Configuration in an IMS
Project of Company M
In an IMS project of company M, SS mainly provides the extended
functions. DigitMaps are delivered to MG by SS when an extranet
user calls the central office. Therefore, the DigitMaps are relatively
simple, which mainly involve fax, conference, extension number
and the extended functions. The following are the DigitMaps.
15
Note:
The numbers used in province J are special. They only have 6
digits.
When a user dials 9xxx, if he or she adds xx to the original
number within the set time S, the 9xxxSxx service will be triggered; If it is timeout, the 9xxx service will be triggered.
16
Chapter
Description of Symbols
in DigitMap
Table of Contents
DigitMap Defined by H.248 Protocol .....................................17
DigitMap Defined by MGCP Protocol......................................18
Function
0~9
A~D
17
Character
Function
[ ]
18
Character
Function
0~9
A~D
[ ]
Figures
19
20
Tables
21
22
Glossary
DTMF
- Dual-ToneMulti-Frequency
H.248
- ITU-T Rec. H.248 Gateway Control Protocol
IMS
- IP Multimedia Subsystem
MGCP
- Media Gateway Control Protocol
NGN
- Next Generation Network
SS
- Soft Switch
23