How to Configure the CMA & RMX to use Simplified Dialing
What is Simplified Dialing
Simplified dialing is a service offered by the CMA application (and the legacy applications
PathNavigator and SE200). This service allows an H.323 endpoint to place a call using the gateway
services of the Polycom MCU, to reach an ISDN location. Simplified dialing eliminates the need to know
a multitude of bandwidth dependent gateway prefixes. Instead, the user dials a simple prefix (by
default this prefix is the digit 9) and the CMA determines which of its configured gateway services to
employ. Simplified Dialing also allows an administrator to avoid the difficulty and cost of installing ISDN
lines for use by individual endpoints, by extending the MCU’s centralized ISDN lines to be utilized by IPonly video endpoints.
Step 1: Configuring gateway services on the Polycom RMX
Simplified dialing has no real impact on how gateway services are configured on the RMX. This topic is
covered in detail elsewhere. This document will focus on the aspects of the configuration that are
important to note.
Please note the Gateway Profile IDs defined in the RMX under the section: Rarely Used > Gateway
Profiles. In this example, 3131, is used as the gateway profile ID.
Please note- this functionality requires that the RMX MPM/ IP Card be registered successfully with the
CMA call processing server. The CMA server must also be in Routed Mode.
To confirm the registration setting
Go to Rarely Used > IP Network Services, right click on the IP Network Service, and select Properties.
Make sure the option for Register as Gateway is not checked and note the MCU Prefix in Gatekeeper
setting. In this example, 2060 is used.
Step 2: Configuring the CMA
A number of changes must be made to CMA to assure proper functionality for simplified dialing.
Simplified dialing must be an enabled service in the CMA. This is enabled by default, and uses the digit
9.
Verify the following in the CMA application
Go to Admin > Dial Plan and Sites > Services
1) The Edit Service screen for simplified dialing should look like below. The only possible
exception would be the Service Prefix used to invoke simplified dialing.
2) In the same Services window, the alias entered in the RMX for the MCU Prefix in
Gatekeeper setting (2060 in this example) appears in the list of services as a MCU and
enabled is set to True.
3) Add a Gateway Service for each of the gateway profiles on the RMX. In this example, 3131
was added.
4) In the same Services window, select ADD under the Actions list
General Info section
a.
b.
c.
d.
Select the Service Type of Gateway
Select the Enabled and Available for New Groups checkboxes
Enter a description of the service
Most important, for the Service Prefix option, enter the Gateway Profile ID from the
matching gateway profile on the RMX. In this example, 3131 was used.
Simplified Dialing section
e. Select the H.320 (required) Voice (optional) checkboxes for Endpoint Capability
f. Select the Bit Rate speed which matches to the Line rate used for the matching gateway
profile on the RMX.
g. Enter an asterisk - * - for the Insert between Prefix & First number option
h. Select the OK button
i. Repeat for each Gateway Profile listed on the RMX.
Please note- Multiple gateway profiles are used on the RMX to differentiate the line rates used in the
profile. In this example, 384k was selected. However in a typical customer deployment, several
bandwidth options would be created, like 512K and 128K.
Verify the RMX device records appear correctly
Go to Network Device > Monitor View
1) A device record appears using the alias in the IP network service in with the same alias entered
in the RMX for the MCU Prefix in Gatekeeper setting (2060 in this example).
2) A device record for the Management interface of the RMX should also appear in the list. This
device record is entered manually and does not appear automatically after registering to IP
network service to the CMA. If it is missing, please create a new device entry set to RMX type.
T2RMX is listed as this device in the screen shot below.
Add the Gateway Profile ID as an E.164 Alias for the IP network service
In order to associate the gateway profile to the IP network Service on the RMX, the gateway profile IDs
need to be entered as aliases. This will allow the CMA to search and find the correct gateway service
according to the bandwidth.
Go to Network Device > Monitor View
1) Select the device record which represents the IP Network service from the RMX, usually
GW/MCU type.
2) Select Edit under the Actions on the left hand side
3) Add all of the Gateway Profile IDs from the RMX as E.164 aliases
a. The alias 3131 was added as indicated by the screen shot below
At this point simplified dialing is properly configured and should function as follows in the example:
1. User places outbound H.323 call from an endpoint using the following dial string, 97705551212,
where 9 is the simplified dialing prefix and 7705551212 is the numbering format that the RMX uses
to place outbound ISDN calls.
2. Embedded in the Setup message for this call is a request for bandwidth (call rate) from the
endpoint (128K, 384K, etc)
3. CMA queries this bandwidth value and compares it to the values that have been defined in the
Services section.
4. When a service with a matching call rate is found, CMA determines which RMX should receive the
gateway request and formats the message to reflect the actual gateway prefix the selected RMX
needs to receive.
5. The RMX then establishes a normal gateway conference between the H.323 and the H.320
endpoints.
If you are experiencing problems, you can try the following:
1. Make a H.323 call using the following dial string: [service prefix of the IP card in the RMX]
[gateway service prefix] * [ISDN number]
For our example, this would be: 20603131*7702380064
2060 = RMX IP network service prefix
3131 = Gateway service prefix
7702380064 = ISDN number to dial
2. Verifying the gateway call functions correctly without a gatekeeper would be:
[RMX Signaling IP Address] ## [gateway prefix] * [ISDN number]
For this example: 10.224.2.62##3131*7702380064
10.224.2.62 = RMX Signaling IP Address
3131 = Gateway service prefix
7702380064 = ISDN number to dial
If the call completes, then there is a problem with the Simplified Dialing service. Check to see if the
gateway services have been added to the CMA. Also check to see if the gateway profile ID has been
added to the IP Network service device record in the CMA.
3. Make sure the RMX is not set to register as a gateway. In order to verify this not the issue, go to
Admin > Dial Plan and Sites > Services. The service entry which represents the IP network
service from the RMX should be set to MCU and not to Gateway.
Step 4. Success – Gateway Conference Created
[ From the CMA Gatekeeper Message Log – Normal ARQ (Successful Gateway Call) ]
Note that the string 3131*7702380064 is actually sent to the RMX. Simplified Dialing permits the user
to dial simply 9 in place of 3131*.
============================ <08:10:10 16:24:04> ============================
ARQ Received
'requestSeqNum' 28695
'callType' 14495
'pointToPoint' 0
'callModel' 9638
'gatekeeperRouted' 0
'endpointIdentifier' 8 '21208875'
'destinationInfo' 1
'1' 8635
'e164' 11 '97702380064'
'srcInfo' 2
'1' 10219
'h323-ID' 13 'SimonsVSX7000'
'2' 8635
'e164' 4 '4408'
'bandWidth' 7680
'callReferenceValue' 25345
'conferenceID' 16 '02 31 6B 4A 82 80 6C 1F 05 B5 28 41 E6 27 D4 7D '
'activeMC' 0
'answerCall' 0
'canMapAlias' 1
'callIdentifier' -111
'guid' 16 '02 31 6B 4A 82 80 6C 1F 05 B4 28 41 E6 27 D4 7D '
'gatekeeperIdentifier' 7 'PN:PLCM'
'willSupplyUUIEs' 0
'featureSet' -111
'replacementFeatureSet' 0
'supportedFeatures' 1
'1' -111
'id' 17656
'standard' 9
Process ARQ
HRAS hsRas 0xcec1e4c, HCALL hsCall 0xb8b59dc, HAPPCALL haCall 0x10000b9
Source of Msg is 172.22.3.180:1719 ARQ from Originator
CallType is 0
DestInfo[0] = 97702380064
DestCallSignal is 0.0.0.0:0
SrcInfo[0] = SimonsVSX7000
SrcInfo[1] = 4408
Total Bandwidth is 768000 : per side BW is 384000
ConferenceID is 02316b4a-8280-6c1f-05b5-2841e627d47d
CallID is 02316b4a-8280-6c1f-05b4-2841e627d47d ActiveMC is 0
CallReferenceValue is 0x6301
Processing ARQ Processing Dialrule: Name 'Alias' Type 'LocalDS'
List of GW/MCU found:
10.224.2.45
10.224.2.60
10.224.2.62
10.224.2.71
10.224.6.162
10.224.6.190
Add Endpoint's IP address list to resolve Address List
TransportAddress: 10.224.2.45:1720 type 0 'IP' distribution 2 'Unknown' length 0
Add Endpoint's IP address list to resolve Address List
TransportAddress: 10.224.2.60:1720 type 0 'IP' distribution 2 'Unknown' length 0
Add Endpoint's IP address list to resolve Address List
TransportAddress: 10.224.2.62:1720 type 0 'IP' distribution 2 'Unknown' length 0
Add Endpoint's IP address list to resolve Address List
TransportAddress: 10.224.2.71:1720 type 0 'IP' distribution 2 'Unknown' length 0
Add Endpoint's IP address list to resolve Address List
TransportAddress: 10.224.6.162:1720 type 0 'IP' distribution 2 'Unknown' length 0
Add Endpoint's IP address list to resolve Address List
TransportAddress: 10.224.6.190:1720 type 0 'IP' distribution 2 'Unknown' length 0
Service(Access Simplified Dialing (default)): Removing 10.224.2.60:1720 because it is offline.
Resolved 97702380064 to a list of possibles contacts.
ParseListResolvedAddress(): OUTPUT Service: String is 97702380064, (prefix:9) IP is 10.224.2.45
**Warning**: Can't find GW '10.224.2.45' Area Code, dial verbatim '7702380064'
Gateway 10.224.2.45 is getting dialStr 7702380064
**Warning**: Can't find GW '10.224.2.62' Area Code, dial verbatim '7702380064'
Gateway 10.224.2.62 is getting dialStr 7702380064
**Warning**: Can't find GW '10.224.2.71' Area Code, dial verbatim '7702380064'
Gateway 10.224.2.71 is getting dialStr 7702380064
**Warning**: Can't find GW '10.224.6.162' Area Code, dial verbatim '7702380064'
Gateway 10.224.6.162 is getting dialStr 7702380064
**Warning**: Can't find GW '10.224.6.190' Area Code, dial verbatim '7702380064'
Gateway 10.224.6.190 is getting dialStr 7702380064
+Simplified Dialing: Choose service from GW 10.224.2.45
+Simplified Dialing: NO only_match_with_voice
+Simplified Dialing: H320 Capability Unchecked for the service 8888
+Simplified Dialing: Go to the next Service
+Simplified Dialing: Didn't find any service rate on GW 10.224.2.45 matches requested bw = 384
+Simplified Dialing: Choose service from GW 10.224.2.62
+Simplified Dialing: NO only_match_with_voice
+Simplified Dialing: H320 Capability Unchecked for the service 2060
+Simplified Dialing: Go to the next Service
+Simplified Dialing: Selected GW 10.224.2.62 service 3131 : bitrate 384000 per side
FindNetPath(): 384000 requested per side
FindNetPath(): IP path found. Acquired Per Side BW = Requested Per Side BW = 384000
Local BW Approved
No server : Going with Local BW Approved
Setup Info: TO: 10.224.2.62:1720 VIA: 10.224.2.62:1720 (3131*7702380064) Per side BW: 384000
ACF sent. The source is Originator
Sending ACF
'requestSeqNum' 28695
'bandWidth' 7680
'callModel' 0
'gatekeeperRouted' 0
'destCallSignalAddress' 0
'ipAddress' 0
'ip' 4 '10.224.2.50'
'port' 1720
'destinationInfo' 0
'1' 0
'e164' 15 '3131*7702380064'
'destinationType' 0
'gateway' 0
'mc' 0
'undefinedNode' 0
'willRespondToIRR' 0
'uuiesRequested' 0
'setup' 0
'callProceeding' 0
'connect' 0
'alerting' 0
'information' 0
'releaseComplete' 0
'facility' 0
'progress' 0
'empty' 0
'status' 0
'statusInquiry' 0
'setupAcknowledge' 0
'notify' 0