Custom Voiceguide V7 Config.xml File Missing <Dialer> Section

[Tony Mazza]

We upgraded this spring to VG7 with a custom Config.xml file. The file doesn't contain a section for the Dialer, so it has not been making outgoing calls. What needs to be added to our Config.xml to provide this functionality for our users?

 

Will be happy to submit a copy of the VG.ini and Config.Xml files via email, but won't post unless advised to do so by support as this was custom work done by Katalina on our behalf.

 

Thanks!

[SupportTeam]

Please ensure that each <Channel> section in Config.xml has this entry:

 

<AllowDialOut>1</AllowDialOut>

 

If this entry is present then please post the vgEngine trace capturing system startup and the loading of the outbound call.

[Tony Mazza]

All channels allowed to dial out do have allowDialout=1 set.

Restarted system and attached vgEngine log as requested.

 

Line 60 of engine log doesn't have any info regarding OutDial CallQue:

 

[VGDialer]:OutDialQue_ODBC_ConnectString =

 

There is no variable for a value in the vg.ini file:

 

[VGDialer]

 

;uncomment the line below for VG to retrieve (poll) calls from OUTVIP database

DbConnectString_ADO=DSN=OUTVIP;Uid=OUTVIP;Pwd=OUTVIP;

 

;Dialout announcement replay maximum count.

AnnReplay=10

 

;How long system waits after end of call before doing any outbound calls on the same line (sec)

AfterIdleWaitBeforeDial=3

 

;Silence detection is used to judge when the answering machine

;message has stopped talking:

 

;Dialogic cards can detect if an answering machine answers the call.

;To Enable Dialogic's answering machine detection set AM_DetectionMode to "Enabled"

;To Disable Dialogic's answering machine detection set AM_DetectionMode to "Disabled"

AM_DetectionMode=Enabled

 

;AnswerMachine Silence detect length. In 100ms units (eg: 20 = 2 seconds)

AM_SilenceDetectLength=20

 

;AnswerMachine SilenceDetectLevel: range: 0-100.

;0 - don't detect silence, 100 - detect loud background noise as silence.

AM_SilenceDetectLevel=10

 

;Minimum length the answering machine message must be.

;Anything less then that will be regarded as a live answer.

;In 100ms units. 20 = 2 seconds

AM_WelcMsgMinLen=20

 

;This prefix will be added to all numbers dialed on all calls made on all lines in the system.

;This prefix is used in additon to any prefix set for calls loaded into the outbound calls database.

GlobalDialPrefix=

0709_0826_vgEngine.txt

[Tony Mazza]

What do we need to do to correct this issue?

Our internal customers are getting frustrated that we have not made progress on resolving their issue, which we cannot do without your guidance and assistance.

[SupportTeam]

The attached traces shows that a "Dial and Conference" call is being made, and the 'Two B Channel' (2BCT/TBCT) transfer option is used in this T1 ISDN trunk.

( <calltype>TBCT_ONCONNECTED</calltype> is specified in the Options field ).

 

After the number is dialed the Telco reports that is had began dialing the number:

 

082804.696 17 13 5 ev CallState GCEV_DIALING, crn=28802e5, iEvent=2 ,16,0,16,,,]. vgEngine v7.1.3757.32895 (2010-04-15 17:16:29.99)

 

 

 

Can you please .ZIP and post the ktTel trace capturing the attempted 2BCT transfer. We the ktTel trace to be able to see what is happening on system on ISDN message level.

 

(Please .ZIP up traces before posting them)

 

 

Do single outbound calls that you would just load into the Dialer work?

Edited 07/17/2010 09:43 AM by SupportTeam

[SupportTeam]

We have been advised by customer that TBCT / 2BCT transfers work fine on this system.

 

The issue is the standard dialer outbound calls. They are not being made.

 

Customer is using an external database (Oracle) as the Dialer database. As per customers question in first post:

The file doesn't contain a section for the Dialer, so it has not been making outgoing calls. What needs to be added to our Config.xml to provide this functionality for our users?

Attached vgEngine trace shows:

 

082638.803 5 db config SelectNodes(/VoiceGuideConfig/Dialer) returned no nodes

 

This indicates that the VoiceGuide has not been supplied connection information to customer's external database and has defaulted to using own internal database (as customer indicated in original post).

 

 

The Config.xml Dialer section requirements in this custiomer's customized version of VoiceGuide would be the same as main release. As per: http://www.voiceguide.com/vghelp/source/html/dial_vgdb_external_config.htm

 

Customer will need to install ADO.NET connector for database (or setup access over ODBC) and the add the <Dialer> section after the </Devices_Dialogic>

section.

 

 

Below shows where the <Dialer> section goes in the Config.xml file:

 

 

 

<VoiceGuideConfig>

<Devices_Dialogic>

.....

</Devices_Dialogic>

 

<Dialer>

 

<OutDialQue_ADODB_Provider>.....

....

....</OutDialQue_SqlSuffix>

 

</Dialer>

 

</VoiceGuideConfig>