Author’s note: This article supports our legacy products. At Inventive Labs, after two decades of providing telephony tools, we never stop supporting those who rely on our products to run their businesses. We no longer recommend Dialogic. This article is for our customers who are using legacy equipment. For more information about these legacy products and where we are today, read Ditch Dialogic & Convert to Voice Elements.
When using Global Call, it is necessary to specify the protocol you will be using in your configuration file.
T1/CAS
For T1-CAS you specify the name of the cdp file that defines the configuration of your T1-CAS. The standard US template for T1-CAS is pdk_us_mf_io.cdp.
When specifying the protocol, just specify the root portion of the filename. IE “pdk_us_mf_io”
It is advisable to make a copy of the pdk file before you make chages to the file for your specific T1-CAS configuration.
ISDN/PRI
For Springware boards the protocol is “ISDN”
For DM3 boards the protocol is “DM3”
For SIP the protocol is “SIP”
Analog
For Analog specify the appropriate cdp file similar to the T1, however in this case the standard US file is: pdk_na_an_io
For more information, see the following Dialogic Technology Guides:
When Dialogic Can’t Resolve your Domain Name (FQDN)
Normally the system will find the correct DNS servers by looking though the NIC Adapters you have configured.
For some reason Global Call occasionally has trouble resolving names. This is particularly important when using SIP.
If you have this trouble, you can manually add the ip addresses of your name servers to:
HKLM/System/Currentcontrolset/Services/TCPIP/Parameters/NameServer
Separate additional name servers by a comma.
See also Global Call for IP HMP v11 for more information.