 |
|
||||||||||||||||||
Selecting ISDN ProtocolAll that is required to configure a T1 ISDN or E1 ISDN system to receive calls is to select the appropriate ISDN protocol in the Dialogic Configuration Manager (DCM) system. After selecting the appropriate ISDN protocol, and starting the Dialogic service the system should now be able to receive calls. Screenshot below shows where in the DCM the ISDN protocol is set:
The telephone company which supplies the ISDN line will inform you what ISDN protocol is used on the lines they supply. Local Dialogic distributor will usually also know which protocols are used by the various telephone companies in your local area and would also be usually able to advise if any special options need to be set on the Dialogic configuration level to make the Dialogic cards work with those lines.
Setting Config.xml and ConfigLine.xmlThe channels which VoiceGuide is to use are specified in Config.xml file. Sample Config.xml files are provided, and cover the most common deployment scenarios. In the Config.xml file the Protocol just needs to be set to ISDN It is recommended that all channels get opened: 23 on a T1 ISDN line, and 30 on an E1 ISDN line. Some PBXs and Switches will not properly initialize the T1/E1 link and will not properly handle calls on it unless all channels on the line are opened. A sample ConfigLine.xml file for use with ISDN systems is also provided. Analog system related settings have been removed from that file, and ISDN related settings have been added in.
Testing ISDN LineWhen using the "JCT" and "SC" family cards. eg: D/240JCT, D/300JCT, D/480JCT, D/600JCT, D/240SC, D/300SC etc.. the Dialogic ISDIAG application can be used to test the T1/E1 lines and obtain ISDN traces. When using the "DMV" family cards. eg: DMV480, DMV600, DMV/240JCT, D/300JCT, D/480JCT, D/600JCT, D/240SC, D/300SC etc.. the Dialogic ISDNTRACE application can be used obtain ISDN traces.
ISDIAGDialogic provides the isdiag.exe command line application which will allow you to test if the ISDN connection is functioning and can capture the ISDN layer trace as well. Isdiag.exe will only work on 'Springware' Dialogic cards, eg: D/240JCT, D/480JCT, D/300JCT. D/600JCT and their predecessors. Isdiag.exe is located in directory C:\Program Files\Dialogic\bin To test an E1 connection the isdiag tool would usually be started like this at the DOS Command Prompt: isdiag 1 1 e s v To test a T1 connection the isdiag tool would usually be started like this at the DOS command prompt: isdiag 1 1 t s v The examples above would allow user to receive and make calls on that first channel of first T1/E1 interface only. You will need to confirm with the Telco that they will send a call on that channel after the ISDN D channel is restarted. D channel is restarted when isdiag VoiceGuide should not be started when using isdiag, as isdiag itself opens the channel on the ISDN line. If you are unable to receive/make calls and play/record sound files with isdiag then you will need to contact your local Dialogic supplier to establish why the hardware they provided does not work on the T1/E1 lines from your telephone company. It is unlikely that VoiceGuide will work if isdiag cannot receive and make calls. Your local Dialogic supplier should be familiar with all the local telephone companies' ISDN protocols and know what should be done in order for the Dialogic cards to be able to work with the ISDN lines in your local area. isdiag can be used to capture traces of the ISDN messages as well. The log files produced by isdiag need to be converted into human-readable form by using the isdtrace.exe application. Note that isdtrace.exe application is different to the isdntrace.exe application. ISDNTRACEDialogic provides the isdntrace.exe application which can capture a trace of the ISDN messages. Isdntrace.exe will only work on DM3/DMV type Dialogic cards. Isdntrace.exe is located in directory C:\Program Files\Dialogic\bin The ISDN traces are used to confirm what ISDN parameters are sent by the Telco on that ISDN line, and to confirm what parameters are being sent out by VoiceGuide when an outbound call is made. The outgoing parameters should usually match what is sent by the Telco's switch. To use isdntrace to obtain the trace of the ISDN layer messages please follow the following steps.
ISDN Outgoing Calls Setting the ISDN protocol to the correct value is usually sufficient for outgoing calls to function as well. Some telephone companies however have specific non-standard requirements for outgoing calls. This section outlines the configuration options available within VoiceGuide to allow the user to explicitly specify the individual settings on outgoing calls. Most of these requirements relate to the structure and the information contained within the "Setup" message sent to the switch when a new call is made. VoiceGuide for Dialogic offers the use extensive control over the information sent within the Setup message, allowing easy configuration of the system to match requirements of the Telco switch or PBX.The configration of the ISDN's SETUP message can be made by specifying the following in the ConfigLine.xml file, in section <ConfigLine><isdn><msgSetup>. Below is an
example of what this section looks like, with the default values
set. <isdn>
The DM3/DMV series cards can only use the "GC" setting parameters. If the default settings do not work please post your system's configuration details on the Support Forum and and a member of staff will then be able to assist in setting the correct configuration. Settings used
for individual fields within the <ConfigLine><isdn><msgSetup>
section are
detailed below: Valid Settings
VoiceGuide ISDN Tracing VoiceGuide v6 can also trace the ISDN D-channel messages. A file titled ktTelControl_TraceSelect.txt needs to be placed in "C:\" with the contents of the file indicating which Dialogic's board D-channel is to be traced. Example contents should be: isdn_trace_dtiB1 which indicates which interface board should have it's D-channel traced. VoiceGuide will create the traces in "C:\", with the traces named something like this: isdn_trace_dtiB1_0325_203334.log Traces can be converted into readable format using Dialogic's ISDTRACE.EXE utility. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
