Polycom Version 2.0.3B manual Dial Plan in Per-Phone Configuration File

Page 26

Technical Bulletin

SoundPoint ® IP, SIP 2.1

The following guidelines should be noted:

You must use only *, #, or 0-9 between second and third R

If a digit map does not comply, it is not included in the digit plan as a valid one. That is, no matching is done against it.

There is no limitation on the number of R triplet sets in a digit map. However, a digitmap that contains less than full number of triplet sets (for example, a total of 2Rs or 5Rs) is considered an invalid digit map.

Using T in the left part of RRR syntax is not recommended. For example, R0TR322R should be avoided.

This configuration attribute is defined as follows:

Attribute

Permitted Values

Default

Interpretation

 

 

 

 

dialplan.digitmap

string compatible with

[2-9]110T

When this attribute is present,

 

the digit map feature of

+011xxx.T

number-only dialing during the

 

MGCP described in

setup phase of new calls will be

 

0[2-9]xxxxxxxxx

 

2.1.5 of RFC 3435.

compared against the patterns

 

+1[2-9]xxxxxxxx

 

String is limited to 768

therein and if a match is found, the

 

characters and 30

[2-9]xxxxxxxxx

call will be initiated automatically

 

segments; a comma is

[2-9]xxxT

eliminating the need to press Send.

 

also allowed; when

Attributes

 

 

 

reached in the digit

 

 

 

dialplan.applyToCallListDial,

 

map, a comma will

 

 

 

dialplan.applyToDirectoryDial,

 

turn dial tone back

 

 

 

dialplan.applyToUserDial, and

 

on;’+’ is allowed as a

 

 

 

dialplan.applyToUserSend

 

valid digit; extension

 

 

 

control the use of match and

 

letter ‘R’ is used as

 

 

 

replace in the dialed number in the

 

defined above.

 

 

 

different scenarios. Refer to page 2.

 

 

 

 

 

 

 

dialplan.digitmap.timeOut

string of positive

3 3 3 3 3 3 3

Timeout in seconds for each

 

integers separated by

 

segment of digitmap.

 

‘’

 

Note: If there are more digit maps

 

 

 

than timeout values, the default

 

 

 

value of 3 will be used. If there are

 

 

 

more timeout values than digit

 

 

 

maps, the extra timeout values are

 

 

 

ignored.

 

 

 

 

Dial Plan in Per-Phone Configuration File

Per-registration dial plan configuration is supported.

The <dialplan/> attribute is described below and also includes:

Digit Map <digitmap/> on page 3.

4

Image 26
Contents SIP 2.0 Administrator’s Guide SoundPoint/SoundStation IP SIP Polycom, Inc Handset, Headset, and Speakerphone Configurable Feature KeysAttribute Default Attribute Permitted Default Interpretation Values LCD BacklightExpanded Memory and Expanded Flash Memory Permitted Attribute Values Default InterpretationDefault RAM Disk ramdisk Permitted Values Default InterpretationMicroBrowser 6 G.722 Audio Codec Attribute ValuesAttribute Default Receive rxEq USB Diagnostics Administrator’s Guide SoundPoint IP / SoundStation IP Syslog Digit MapBilling Code Server Redundancy Supported Platforms Unsupported PlatformsDisable Message Waiting Indicator by Registration Daylight Saving Time Changes forDST Platform Key IDs Miscellaneous Configuration File Changes 9.1 sip.cfgPorted on SoundPoint IP Attribute Permitted Default Interpretation Values Phone1.cfg Device Parameter Introduction Configuration File ChangesBoot server Sip.cfg CentralLocal Dial Plan in Application Configuration FileAttribute Permitted Default Interpretation Values Permitted Attribute Values Default Interpretation Dial Plan in Per-Phone Configuration File Attribute Permitted Values Default InterpretationDial Plan in Application To Digit Map digitmap/ on Trademark Information Dialplan.x.digitmap isBilling Code Entry Billing Code Entry on SoundPoint IP Phones with SylantroTrademark Information Syslog on SoundPoint IP Phones Network Configuration Changes Name Possible Values DescriptionFlash Parameter Configuration Name Possible Values DescriptionSIP Server Fallback Enhancements on SoundPoint IP Phones SIP 2.0 Administrators Guide TerminologySIP 2.1 Server Fallback Implementation Example DeploymentReg.1.server.2.address=172.23.0.1 Behavior When the Primary Server Connection Fails Before SIP Recommended Practices for Server Fallback DeploymentsChanges From Previous Phone Behavior Releases Before SIP Protocol in Application Configuration File Boot serverRegistration in Per-Phone Configuration File References Trademark Information