cc/td/doc/product/voice/uone/entrpris/41e
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Advanced Functions

Advanced Functions

This chapter discusses a few advanced topics related to working with uOne.

Customizing uOne - Dialmap

The Dialmap is used:

Address Conversion

uOne uses telephone numbers to which we are accustomed in the PSTN world (e.g., 8047625600) and follows ITU e164 standard addressing. Telephone numbers in the IP telephony world may not look the same (e.g., 172.24.167.198:,8047625629 or support, 8047625600). In order to enable mapping of IP telephone numbers to ITU e164 addressing, the H225SetupMapping parameter must be configured in the h323.ini file and the customization rules must be defined in the Dialmap.ini file.

Routing

When a call comes into uOne, the telephone call (based on the caller number or called number) must be routed to an application. The Dialmap.ini file is used to route the appropriate calls to the appropriate application.

Step 1 Edit h323.ini (e.g.,C:\CiscoSystems\uOne\parms\h323.ini). It must have the following parameter for address conversion:

H225SetupMapping=<value>


Table 3-1: The SSMW.ini file parameters
Field Description Valid Values

H225SetupMapping

Enables remapping of the H225 SETUP CalledParty/CallingParty fields via regexp/Dial Map functionality. Note that the DialMap.ini configuration file should contain H225CALLEDPARTY / H225CALLINGPARTY configuration sections, as appropriate, to use this feature.

Multiple values can be listed consecutively and delimited by spaces.

Default: None

CalledParty

CallingParty

Step 2 Edit DialMap.ini (e.g., C:\CiscoSystems\uOne\parms\DialMap.ini).

[PhoneFormat]
Format1
Format2


[Format1]
Rule1
Rule2


[Format1:Rule1]
FromRegExp=
ToRegExp=
Constraint=
Return=


[Format2:Rule2]
FromRegExp=
ToRegExp=
Constraint=
Return=



Table 3-2: The DialMap.ini File Parameters
Field Description Valid Values

Format

This is a label for the Format section.

It should not be edited.

Rule

Listed immediately below the [Format] label is a listing of all rules that will be defined for a given Format section.

USDOMESTIC is required for uOne to operate properly.

USDOMESTIC

H225CALLINGPARTY

H225CALLEDPARTY

ROUTING

[Format:Rule]

This is a section label that defines a specific rule for a given format.

For example:

[USDOMESTIC:Rule1]

FromRegExp

It is a regular expression corresponding to the phone number of a phone line from which a number would be dialed.

It is the same as the Token DNIS in the DlgAttrib.<hostname> file.

See the regex UNIX man-page for detailed information about what is valid for this attribute.

Maximum length is 63 characters.

ToRegExp

This is the DNIS or dialed number. It is a regular expression corresponding to the phone number to be converted.

See the regex UNIX man-page for detailed information about what is valid for this attribute.

Note: SmsiMap rules do not use ToRegExp.

Maximum length is 63 characters.

Constraint

Specifies a constraint for the rule. That is, the rule will not apply unless the expression evaluates to non-zero, or is "None".

The common relational operators include:

< less than

<= less than or equal to

== equal to (true)

> greater than

>= greater than or equal to

!= not equal to

Follows the syntax of the Tcl expr command, or may be "None", if no constraint should be applied.

Maximum length is 127 characters.

Return

Contains the syntax for building the converted string from matched FromRegExp and ToRegExp substrings, and other literal changes.

There are valid non-numeric return values as well:

"*,#,a,b,c,d" (DTMF digits)
"," (1 second pause)

Maximum length is 63 characters.


Table 3-3: Example for dial map

[USDOMESTIC]

OfficePBX

The Format is USDOMESTIC and it will have one rule called OfficePBX

[USDOMESTIC:OfficePBX]
FromRegExp=^(804)$0(762)$1([0-9]{4})$2$
ToRegExp=^(804)$0(762)$1([0-9]{4})$2$
Constraint=(5500 < $t2) & ($t2 < 5688)
Return=$t2

The OfficePBX rule for USDOMESTIC says to dial a four digit number if the called number is between 5500 and 5688.

Caller Number (ANI) FromRegExpression variables are: $0= 804, $1=762, $2=four digit number.

Called Number (DNIS) ToRegExpression variables are: $0= 804, $1=762, $2=four digit number

The Constraint says if variable $2 of the ToRegExp is between 5500 and 5688 then...

The system should return variable$2 of the ToRegExp (4 digit dialing).

[H225CALLINGPARTY]

4Digits

10Digits

The Format is H225CALLINGPARTY and it will have two rules called 4Digits and 10Digits.

[H225CALLINGPARTY:4Digits]

FromRegExp=^([A-Za-z0-9:]*,)$0([0-9]{4})$1$
Constraint=None
Return=$f1

The 4Digits rule for H225CALLINGPARTY says if the number has only four digits following the comma, then return the four digits.

Caller Number (ANI) FromRegExpression variables are: $0= all characters before the comma (can be any letter or number or a colon), $1=a four digit number.

There are no constraints.

The system should return variable $1 of the FromRegExp.

[H225CALLINGPARTY:10Digits]

FromRegExp=^([A-Za-z0-9:]*,)$0([0-9]{10})$1$
Constraint=None
Return=$f1

The 10Digits rule for H225CALLINGPARTY says if the number has only four digits following the comma, then return the ten digits.

Caller Number (ANI) FromRegExpression variables are: $0= all characters before the comma (can be any letter or number or a colon), $1=a ten digit number.

There are no constraints.

The system should return variable $1 of the FromRegExp.

[ROUTING]

4Digits

10Digits

The Format is Routing and it will have two rules, 4Digits and 10Digits

[ROUTING:4Digits]

FromRegExp=^000000([0-9]{4})$0$
Constraint=None
Return=804762$f0

The 4Digit rule for Routing says to return 804762<4 digits> when dialing a four digit number.

Caller Number (ANI) FromRegExpression variables are: 4 digit number.

There are no constraints.

The system should return 804762<4 digits>

[ROUTING:10Digits]

FromRegExp=^([0-9]{10})$0$
Constraint=None
Return=$f0

The 10Digit rule for Routing says to return the <10 digits> when dialing a ten digit number.

Caller Number (ANI) FromRegExpression variables are: 10 digit number.

There are no constraints.

The system should return the <10 digits>

H323.ini

DTMF Detection

There are two parameters (FFTSMRThreshold and FFDurationThreshold) that can be used to customize the accuracy of DTMF detection depending on the device you are using (IP phone, Cellular phone, speaker phone, etc.).


Table 3-4: The DTMF Parameters
Field Name Description Valid Values

FFTSNRThreshold

The Signal to noise ratio threshold for DTMF detection (only used when DTMFDetect=FFT)

10-30

Default = 17

FFTDurationThreshold

Duration threshold for DTMF detection (milliseconds) (only used when DTMFDetect=FFT).

32, 64

Default=64


hometocprevnextglossaryfeedbacksearchhelp
Posted: Wed Jun 21 03:54:32 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.