Dialogic 'off-hook' Events

[Guest Buzby]

Hi there,

 

Is it possible for VoiceGuide to automatically 'Off-Hook' each of the lines it is controlling when the application quits, or the line is ended. The reason I ask is because our PBX's hunt group avoids putting calls through to off-hook lines and therefore means that I can stop VoiceGuide tidyily without loosing any calls.

 

I know you can set the Dialogic card itself to Off-hook lines when the DCM isn't running, but I just wondered if VoiceGuide can do the same sort of thing?

 

Cheers!

[SupportTeam]

When the application quits then VoiceGuide relinquishes control of Dialogic lines.

 

[incorrect statement about hookstate behavior removed]

 

If your PBX/Service supports it, you could dial a "Make Set Busy" sequence to take the line out of service (or can you program the call distribution lists or huntgroups on your PBX dynamically?)

Edited 08/07/2005 08:32 AM by SupportTeam

[Guest Buzby]

Interesting - but your point about the state of hook when no application is using the card is not necessarily true - on our D/120JCT-LS cards there is a switch which configures the hookstate of the lines when power is on, but the board is not initialized. We have found that the word 'initialized' seems to mean when a DX_OPEN call is made to the board, not just when the DCM is running.

 

Therefore, when we boot our server, the lines are all off-hook, which prevents calls being sent to the board. Only when we start VG do the lines all go on-hook and the calls start coming in. However, it would be really nice to have them all off-hook again when quitting VG.

 

See http://resource.intel.com/telecom/support/...LS/1215-002.pdf for details of the switch I'm referring to.

 

Note that this isn't a massive problem for us - so I'm not looking for an urgent fix or anything like that - but I just wondered how other VoiceGuide users cope with this, particularly in redundant multi-server setups.

 

Surely, if VG was to automatically off-hook the lines whilst quitting, this would save having to reprogram the switch to prevent the calls going through to that hunt group?

 

Could VG examine the hookstate in Dialogic (ATDX_HOOKST) when it starts up, then return the lines to the same state (DX_SETHOOK) when quitting?

[SupportTeam]

We've had a look at the operation of this switch on our test systems here and confirmed that it functions as you describe

 

The just released v6.0.2086 of VoiceGuide for Dialogic looks the hookstate of each analog line at startup and returns that line to the original hookstate upon exit.

 

Please update your system with the .EXEs and .OCXs from this new release.

 

If you encounter any problems with it or have any further questions/issues/suggestions please let us know.

[Guest Buzby]

Hi there,

 

Many thanks for your reply - very helpful.

 

Just one thing about VG for Dialogic. At the moment, we are still evaluating the functionality and performance of VG using a 4-port licence and the standard version of VG that we purchased a couple of months ago. And so far everything seems good!

 

We do intend to move to VG for Dialogic when we purchase a higher-port licence of VG soon. However, the current version of VG we are using is 5.2.4029 because it contains a number of fixes and features that are very helpful to our application. These include:

 

- Ability to set min/max digits in Get Numbers modules using $RV fields (5.2.4001)

- Using 'on {*}' memorizes keypresses in Get Numbers modules (5.2.4003)

- Ability to switch of log files on/off (5.2.4029)

 

Can you confirm whether or not VG for Dialogic contains and maintains the same fixes as the standard version of VG?

 

Many thanks again.

[SupportTeam]

Not all of the updates were in VG for Dialogic.

 

We've now uploaded v6.0.2088 patch which has into it added in all the updates you mention.

[MannyTC]

Quicky question related to message above. Why are the feature sets of both versions of VoiceGuide not being kept in sync?

[SupportTeam]

Features are synced up for major releases. Minor feature additions like ones listed above are made as required and initially only released in whichever version they are required, but they do get put into the other version of VG eventually.