Table of Contents
Advertisement
Table 26: chdbased.reg Attribute Settings (continued)
Attribute
Connections
Test
Validation Requests
When the chdbased.reg configuration information is accurate and the specified EPV server is
available, then the system establishes the specified number of connections to the EPV server.
Each passcode and PIN code validation request is sent to the EPV server using the HTTP GET
command. The passcode, the PIN code, and several other parameters, are sent in the GET
request as arguments in the URI.
Table 27: GET Request Arguments
Argument
pc
V
Bn
Pt
Description
The number of connections to open to the EPV server. Each
connection handles a single EPV request. Requests are
asynchronous , therefore several requests may be made
without blocking call processing.
The attribute setting depends on the EPV server's capacity. For
instance, if the EPV server can only process one request at a
time, connections should be set to 1. However, if it can process
multiple requests simultaneously, connections should be set to
more the 1.
Used for testing with a dumb HTTP server. When test is set to
True, the passcode being verified is used as the name of an htm
file. For example, to validate a passcode of 97979 on a test
HTTP server, place a file with the name 97979.htm in the /
epvtest directory.
Table 27
describes information sent to the EPV server.
Description
The passcode to validate.
Version of the protocol
Bridge name
The port or channel on which
the call resides.
Using External Passcode Validation
Default Value
none
Setting for the version attribute
in the epdv.reg file. The default
is 1.0.
Setting for the bridgeid attribute
in chdbased.reg. Default is
spectel700
none
Issue 1
2 of 2
1 of 2
August 2007
143
Advertisement
Table of Contents
