Dialogic D/240jct-t1 Pci

[jbanciu]

Got the card without software/documentation on ebay. Need to connect to Avaya Definity PBX in loop-start mode.

Installed the card on win2k with Dialogic® System Release Version 5.1.1 and is passing all the tests in udd. The firmware is set to "default".

 

I don't know the file name for the .fcd (config) I need to edit to reflect the loop-start mode in the CHP section.

[SupportTeam]

You would need to speak with the Dialogic card supplier. They are responsible for getting the product that you purchased from them working on your system and communicating with other hardware. They need to get it to the stage of working with demo applications which ship with the Dialogic drivers.

 

Once the card is working and the demo applications can answer calls you are then ready to install VoiceGuide for Dialogic.

 

With loop-start (Robbed Bit) T1 lines you often you need to change individual parameters within the configuration files to match up the A/B/C/D bit behavior between the switch and the Dialogic card.

 

Do you know what are the paramters of the Robbed Bit protocol the PBX is using?

 

You could try just starting VoiceGuide with the protocol set to pdk_us_mf_io in the Config.xml file (make sure to use the correct Config.xml template) and see if it works, but if it does not then you will have a fair bit of work ahead of you researching the PBX's protocol parameters and getting the configuration on Dialogic's side to match.

 

 

It's usually simplest to setup an ISDN link between switch and Dialogic - that way you will also receive CallerID/DNIS information as well, rather then trying to setup Inband Signaling to receive that information.

 

If you have purchased the 24 line VoiceGuide license we offer an installation service - you will need to provide a PCAnywhere or WinVNC access to your machine though. Please contact sales@voiceguide.com for more details.

[jbanciu]

With loop-start (Robbed Bit) T1 lines you often you need to change individual parameters within the configuration files to match up the A/B/C/D bit behavior between the switch and the Dialogic card.

 

Do you know what are the paramters of the Robbed Bit protocol the PBX is using?

 

Thank you for your reply. The Definity is set to T1 CAS, loop-start, B8ZS, and D4.

 

I need to know what is the configuration file set for this card, so that I can edit and regenerate it.

For example CPI2F2401T1PCIU is using gdk_t1_em.fcd (for E&M), gdk_t1_gs.fcd (ground start) and gdk_t1_ls.fcd (loop start) with the associated .config files.

 

I searched the Intel, Dialogic and the net to find out, but I couldn't find it. The DCM urtility is starting the board fine, but I could not find something in there to set this parameters.

[SupportTeam]

Have you tried using the "24 line T1" version of the Config.xml file and specifying pdk_us_mf_io for the protocol?

[jbanciu]

Have you tried using the "24 line T1" version of the Config.xml file and specifying pdk_us_mf_io for the protocol?

 

We are using pdk_us_ls_fxs_io. The config.xml looks like this for one channel:

 

<Channel>

<Name>dxxxB1C1</Name>

<NetworkIf>dtiB1T1</NetworkIf>

<Protocol>pdk_us_ls_fxs_io</Protocol>

<RingsBeforeAnswer>2</RingsBeforeAnswer>

<script>e:\Program Files\VoiceGuide\Scripts\HHAR IVR.vgs</Script>

<AllowDialOut>1</AllowDialOut>

<PopupCallerId>1</PopupCallerId>

</Channel>

 

We have one last item to resolve. We connect to the PBX but VoiceGuide is answering on the first ring, even if the setting is to answer in 2 rings. As a result we cannot capture the caller id data (which is beeing sent between the first and second ring).

 

Don't know what else to change to make it answer in 2 or more rings?

[SupportTeam]

On T1 lines the Caller ID does not get sent between first and second ring. Sending of caller ID between first and second ring only happens on analog lines.

 

On T1 lines information like CallerID is usually done using DTMF tones after the call is answered (as Inband Signaling).

 

Can you please re-confirm with the E1 supplier when the CallerID is sent and in what format that CallerID is sent.

 

 

Could you please also post a copy of VoiceGuide's Trace Logs which captures the startup/initialization and an incoming call, this will allow us to see what is happening oin the system.

 

Enable logging by setting the log levels to 10 in VG.INI as per below:

[Log]

 

VoiceGuide=10

 

ktTel=10

Then restart VG and make a test call.

 

Trace files will be created in VG's \log\ subdirectory.

 

Please post the traces.

 

When posting traces/scripts please .ZIP them up and post them as attachments.

[jbanciu]

Thank you for your reply.

 

I did not attach the log files because I know now that first thing I have to resolve is to take care of the inband signaling parameter file.

 

We are connecting to Avaya Definity G3 switch and so far I was unsuccessful on getting the info for this switch. I saw your model file for the Siemens switch but could not find on the net what the parameters are for our switch.

 

I tried the Get Numbers as the start of the VoiceGuide but I am not successful in collecting anything in the log. How should Get numbers be setup to collect the caller id?

 

 

Before we switched to this T1 card we used a Dialogic 4 port analog card and we could get the caller id with no problem, so we know that the switch is sending it. Or is it that on T1 card the "inband" signaling needs to be set up differently on the switch, and we did not do that?

 

Do you have an inband parameter file for Avaya Definity G3?

[SupportTeam]

I tried the Get Numbers as the start of the VoiceGuide but I am not successful in collecting anything in the log.

Which means that no inband signaling is sent. You should look at the PBX and configure it so that it sends CallerID on this link.

 

Or is it that on T1 card the "inband" signaling needs to be set up differently on the switch, and we did not do that?

Correct. This configuration would be different then for Analog Lines. You will need to consult the PBX documentation or speak with your PBX technician.

 

There are many different ways in which the Inband Signaling can be sent - depending on the options selected in the PBX, so it’s easiest to just to see what is being sent and adjust the Inband Signaling file accordingly. Do you have documentation form the PBX on what Inband Signaling information can be sent by the version of the PBX that you are using?

 

As mentioned before, it is usually simpler to setup an ISDN type link rather then configuring a Robbed Bit type connection. CallerID/DNIS is automatically provided on ISDN lines, there is no need to configure anything to receive CallerID/DNIS.