General V7 Voip Version Questions

[SupportTeam]

Ralph wrote:

 

Since I am back on the development trail to complete the development and release of our outbound campaign solution, I would like to go over with you on the following questions which I cannot answer by reviewing your site:

 

Is HMP supported via the SIP and H.323? I am sure that HMP is supported but want your confirmation.

 

Is there a specific HMP provider (Gridborg or Dialogic)? And is there a specific version of HMP required (i.e.: Dialogic HMP 3.0 or Dialogic HMP 2.0)

 

During your testing is there a significant system degradation when using a TTS engine (i.e.: Loquendo's) and HMP (no boards)? As oppose to using a TTS engine (i.e.: Loquendo's) and a Dialogic board.

 

Dialogic's HMP 3.0 supports up to 500 lines/channels per server, Does VoiceGuide 7 support that many lines as well? Or is it limited to 300 lines.

 

Would VG 7 do DTMF detection and TTS delivery via HMP without issues?

 

I noticed that VG 7 supports Dialogic's DIN and Traditional boards, but, since HMP is supported, under which scenario would I need a dialogic board (i.e.: DIN or JCT)? Could I not develop and outbound campaign tool or an IVR solution strictly using HMP?

 

If we opt to implement HMP with VG 7, and later switch to a board solution - Is the support for Dialogic's DIN and Traditional boards native to VG 7 (or are they separate versions)?

 

If we go HMP 100% without any hardware, besides a hefty server, there are no other hardware/software requirements to run VG 7 Voip (besides VG, the TTS eng, and HMP), correct?

 

Could you please expand on the Web Services interface for SOA integrations as implemented in VG7?

 

Is the outbound call loader bundled with VG 7? Does it support any ODBC source? or is it limited to MS Access and MS SQL

 

Since VG 7 uses a .NET based database for Outbound Calls Queue can I work directly with the DB without the need of the old VoiceGuide Dialer?

 

Is the db table taxonomy found on the new outbound call loader identical to the taxonomy found on the older OutDialQue.mdb table: CallQue?

 

Is the VG 7 development environment separate from the production tool? For example if I buy 4 - VG 7 licenses for an outbound production server, if I want to continue to develop new services I prefer not to use/commit a license from the production server for development. What is the best solution for this scenario?

 

If we purchase a number of VG 7 for Voip with HMP, and decide to add more lines at a later time, could the additional lines (licenses) be added to production without taking the production server down?

 

Do you sell the HMP licenses? If yes, what is the cost per line?

 

Did you retain the cool workflow development interface as found in the VG 5.x? Are there any additional development tools with VG 7?

 

There are no minimum orders for VG7 Voip, correct? Your site does not have a limitation but I want to confirm that there are no issues if I buy one license and add the remaining once my development cycle is completed.

 

Is there a fully functional demo version of VG 7 Voip available for download? Would you know if there is a demo version of the HMP driver that is compatible with VG 7?

 

[SupportTeam]

Is HMP supported via the SIP and H.323? I am sure that HMP is supported but want your confirmation.

VoIP version of VoiceGuide v7 uses the Dialogic HMP drivers. HMP supports both SIP and H.323 connectivity.

 

Is there a specific HMP provider (Gridborg or Dialogic)? And is there a specific version of HMP required (i.e.: Dialogic HMP 3.0 or Dialogic HMP 2.0)

Dialogic's HMP drivers are used.

 

During your testing is there a significant system degradation when using a TTS engine (i.e.: Loquendo's) and HMP (no boards)? As oppose to using a TTS engine (i.e.: Loquendo's) and a Dialogic board.

The VoIP G.711 codec gives same sound quality as the PSTN network and ISDN lines, since it uses no compression, but any lost packets will basically translate into a silence/dropout.

So to get good quality with VoIP you need to setup the network VoIP connectivity in such a way that there is a guarantee of no dropouts occurring... basically the means not using any public IP network.

See: http://www.voip-info.org/wiki/view/ITU+G.711

Codecs which are resistant to packet dropouts do not give as good sound quality as G.711.

 

Dialogic's HMP 3.0 supports up to 500 lines/channels per server, Does VoiceGuide 7 support that many lines as well? Or is it limited to 300 lines.

In theory yes. Upper line limit depends more on what other tasks the script is asked to perform during the call.

 

Would VG 7 do DTMF detection and TTS delivery via HMP without issues?

If there are no packet drop-outs then it is no issue.

 

I noticed that VG 7 supports Dialogic's DIN and Traditional boards, but, since HMP is supported, under which scenario would I need a dialogic board (i.e.: DIN or JCT)? Could I not develop and outbound campaign tool or an IVR solution strictly using HMP?

DNI boards would be used if you need one server to connect to T1/E1 lines as well. If you do not need T1/E1 then you can just use HMP to handle VoIP calls.

 

If we opt to implement HMP with VG 7, and later switch to a board solution - Is the support for Dialogic's DIN and Traditional boards native to VG 7 (or are they separate versions)?

Yes. Both DNI and traditional boards are supported in v7. You can only use DNI on a HMP system. The traditional boards (JCT/DMV etc) cannot be used under HMP.

 

If we go HMP 100% without any hardware, besides a hefty server, there are no other hardware/software requirements to run VG 7 VoIP (besides VG, the TTS eng, and HMP), correct?

Correct.

 

Could you please expand on the Web Services interface for SOA integrations as implemented in VG7?

In the beginning all the COM functions have been made available. Easiest way is to use SOAP to access them

Use this http connect string in any web browser to obtain WSDL for VoiceGuide's service:

http://localhost:7131/vgIvrRemoting/vgServices?WSDL

 

Is the outbound call loader bundled with VG 7? Does it support any ODBC source? or is it limited to MS Access and MS SQL

Outbound call loader is bundled with VG 7. The VoiceGuide outbound call loader loads calls into VG's own DB. (VG uses Vista DB internally see http://www.vistadb.net/ )

VG can also load calls from other call sources. ODBC source can be used as additional sources.

 

Since VG 7 uses a .NET based database for Outbound Calls Queue can I work directly with the DB without the need of the old VoiceGuide Dialer?

Yes. Just load the calls into the Vista DB. The database file is in VoiceGuide's \data\ subdirectory.

 

Is the db table taxonomy found on the new outbound call loader identical to the taxonomy found on the older OutDialQue.mdb table: CallQue?

Yes.

No, it is slightly different. Please see: http://www.voiceguide.com/vghelp/source/ht...ialque_odbc.htm

 

Is the VG 7 development environment separate from the production tool? For example if I buy 4 - VG 7 licenses for an outbound production server, if I want to continue to develop new services I prefer not to use/commit a license from the production server for development. What is the best solution for this scenario?

The script designer is provided free with the evaluation download. You do not need to buy any licenses for the script designer. The development system can just use the evaluation install of VoiceGuide.

 

If we purchase a number of VG 7 for Voip with HMP, and decide to add more lines at a later time, could the additional lines (licenses) be added to production without taking the production server down?

HMP license increase requires a Dialogic service restart. Changing the VoiceGuide license also requires the VoiceGuide service restart.

 

Do you sell the HMP licenses? If yes, what is the cost per line?

Yes. WE can sell those as well. Please contact sales@voiceguide.com

 

Did you retain the cool workflow development interface as found in the VG 5.x? Are there any additional development tools with VG 7?

The script designer is the same. (you can download the evaluation version and see).

 

There are no minimum orders for VG7 Voip, correct? Your site does not have a limitation but I want to confirm that there are no issues if I buy one license and add the remaining once my development cycle is completed.

v7 has a minimum order of 4 lines.

 

Is there a fully functional demo version of VG 7 Voip available for download? Would you know if there is a demo version of the HMP driver that is compatible with VG 7?

Yes on both counts. Please go to our WWW Downloads page and download v7 and HMP. HMP Downloads page lets you download the 4 line evaluation license as well. Make sure to download and apply that license as well.

Edited 10/04/2007 07:21 AM by SupportTeam

[Guest BlackBird]

Thanks for the prompt reply.

 

After reading your response, at the moment, the only concern I have would be with the VistaDB design change, could you please shed light into the following questions:

 

The outbound call solution I am working on relies on MS SQL DTC to pump data on daily bases from customer tables into the CallQue table used by the older versions of VG, thus, VG would proceed to make the calls once they are queued. This would have worked fine if VG 7 relied on MS SQL (as found in the VG version for Dialogic). Since VistaDB is used in conjuction with VG7, Would you know if the VistaDB shipped with VG 7 supports automated data exhanges from other DBs (such as MS DTC inserts)?

 

On your response you mentioned that "VG can also load calls from other call sources". Does this mean that I can have the outbound call loader use MS SQL instead of the VistaDB?

 

In the event I need to inspect or change an element on the VistaDB that shipped with VG7, would I need to purchase a development client from Vista Software Inc.? or Did VG7 shipped with a db ide tool for VistaDB?

 

Txs,

Ralph

[SupportTeam]

The outbound call solution I am working on relies on MS SQL DTC to pump data on daily bases from customer tables into the CallQue table used by the older versions of VG, thus, VG would proceed to make the calls once they are queued. This would have worked fine if VG 7 relied on MS SQL (as found in the VG version for Dialogic). Since VistaDB is used in conjuction with VG7, Would you know if the VistaDB shipped with VG 7 supports automated data exhanges from other DBs (such as MS DTC inserts)?

v5/v6 of VG itself accesses the external datasources, it does not rely on any 'automated data exhange' mechanism to have data automatically imported into MSAccess.

Similar with v7 of VoiceGuide. The external datasources are accessed directly.

Not sure if VistaDB would let you setup any 'automated data exchange' with MSSQL. Suspect not.

VG v7 is has the option of using a secondary ADO.NET or ODBC datasource (as well as using VistaDB).

Basically if no call can be found in the local VistaDB then VG will check the specified ADO.NET / ODBC datasource.

 

On your response you mentioned that "VG can also load calls from other call sources". Does this mean that I can have the outbound call loader use MS SQL instead of the VistaDB?

Yes. As outlined above VG can load calls from another DB. This does not mean that VG's Outbound Call Loader can load calls into another DB. The Outbound Call Loader loads calls into VG's internal DB (VistaDB). If you would like to obtain a modified version of the Outbound Call Loader which can load calls into another DB please contact sales@voiceguide.com to obtain a quote.

 

In the event I need to inspect or change an element on the VistaDB that shipped with VG7, would I need to purchase a development client from Vista Software Inc.? or Did VG7 shipped with a db ide tool for VistaDB?

Suggest you got to www.vistadb.net and download their install. In there you will find the Data Builder and Data Migraton Tools with their full C# source code. This should show you how to work with Vista databases from within .NET

[SupportTeam]

Please see this Help file entry for information on how to setup an external database to be an additional source for outgong calls.

 

http://www.voiceguide.com/vghelp/.....ialque_odbc.htm

 

Note that the OutDialQue.CallQue database structure is slightly different in v7

 

[Guest BlackBird]

Hi Team, first of all, the new help file/site, is looks pretty sharp! A definite improvement. Oh and thank you for making the distinctions between VG 7 and VG 6.x, VG5.x.

 

While seeking information on the help file I noticed the following:

http://www.voiceguide.com/vghelp/source/ht...iallistinto.htm there are no XML input (OutDial_New.xml) instructions specific to VG 7. It seems that the OutDial_New.xml supported under VG7, but the xml schema listed as an example at diallistinto.htm does not match the VG 7 fields, would it be possible to add a VG7 specific section into the diallistinto.htm?

 

I noticed that the table creation script and OutDialQue_ODBC_ConnectString examples listed at http://www.voiceguide.com/vghelp/source/ht...ialque_odbc.htm are MySQL centric. Could you please post an MS SQL specific example for table creation script and as well as the OutDialQue_ODBC_ConnectString?

 

Would this be the correct MS SQL connection string under VG 7 (please note that in my environment VG and the MS SQL server live on the same box)? OutDialQue_ODBC_ConnectString=Driver=SQL Server;Server=xbox\SQLExpress;Database=c:\dbdump\MyOutCall.MDF;User=MyConnection;PassWord=MyPassword;

 

Also, should MS SQL users replicate the VistaDb:CallQue table taxonomy as shown at http://www.voiceguide.com/vghelp/source/ht...ialque_odbc.htm ?

 

Say, in the event I decide to use the built in VistaDB:CallQue table (instead of using MS SQL) From the online help file, I noticed that I could use the following two programmatic methods to add outbound calls to the VistaDB:CallQue table; Dialer_OutDialQueAdd or OutDial_New.xml. If I opt to add multiple phone numbers to the VistaDB:CallQue table is there a preferred method (performance, scalability, stability) between the Dialer_OutDialQueAdd or OutDial_New.xml? Which one would you recommend in order to add multple phones into the VistaDB:CallQue table?

 

When using the OutDial_Newfile.xml how frequently does VG checks the \data subdirectory to pick up an updated XML file? Could the frequency of the xml import process into the CallQue table be initiated programmatically?

 

Lastly, if I want to flush the VistaDB:CallQue table so that I can pump a new collection of phone numbers to be called. Is there a programmatic method to clean/flush the VistaDB:CallQue table so that is ready for a new batch of phone numbers?

 

Regards,

Ralph

 

[SupportTeam]

there are no XML input (OutDial_New.xml) instructions specific to VG 7. It seems that the OutDial_New.xml supported under VG7, but the xml schema listed as an example at diallistinto.htm does not match the VG 7 fields.

The v7 fields will soon be supported in the OutDial_New.xml file. We'll provide more information on this when available.

 

Could you please post an MS SQL specific example for table creation script and as well as the OutDialQue_ODBC_ConnectString?

Have not prepared MSSQL Server specific samples at this stage. The table creation script should be fairly similar. For the connection string to use please see: http://connectionstrings.com/

Pretty sure that when connecting to MSSQL Server the OutDialQue_ODBC_SqlPrefix and OutDialQue_ODBC_SqlSuffix entries should be left blank.

 

Would this be the correct MS SQL connection string under VG 7 (please note that in my environment VG and the MS SQL server live on the same box)? OutDialQue_ODBC_ConnectString=Driver=SQL Server;Server=xbox\SQLExpress;Database=c:\dbdump\MyOutCall.MDF;User=MyConnection;PassWord=MyPassword;

http://connectionstrings.com/ suggests that the connection string should be more like this:

 

Driver={SQL Server};Server=localhost;Database=myDataBase;Uid=myUsername;Pwd=myPassword;

 

where myDataBase is the name of the database in SQL Server, not the filename.

 

Also, should MS SQL users replicate the VistaDb:CallQue table taxonomy as shown at http://www.voiceguide.com/vghelp/source/ht...ialque_odbc.htm ?

Yes. Just like the sample MySQL table creation script replicates it.

 

If I opt to add multiple phone numbers to the VistaDB:CallQue table is there a preferred method (performance, scalability, stability) between the Dialer_OutDialQueAdd or OutDial_New.xml? Which one would you recommend in order to add multple phones into the VistaDB:CallQue table?

I'd probably recommend using the Dialer_OutDialQueAdd. This way your loading program will get instant feedback on whether the call load was successful or not.

Another approach is to write direct into the VistaDB as well. For .NET drivers/tools to do this see www.VistaDB.com

 

When using the OutDial_Newfile.xml how frequently does VG checks the \data subdirectory to pick up an updated XML file? Could the frequency of the xml import process into the CallQue table be initiated programmatically?

The check is made every second. In v7 any file matching these templates is loaded: OutDial_*.xml or OutDialInput_*.xml - so you can create multiple files at same time to avoid a situation where an existing file that was not yet read in is overwritten by the new write. eg you can create files called OutDialInput_1.xml, OutDialInput_2.xml, OutDialInput_AnotherOne.xml etc. at the same time and all these files will be read in next time VoiceGuide checks for input file presence.

 

Lastly, if I want to flush the VistaDB:CallQue table so that I can pump a new collection of phone numbers to be called. Is there a programmatic method to clean/flush the VistaDB:CallQue table so that is ready for a new batch of phone numbers?

Right now there is no way to flush it programmatically. You can manually flush it by running a DELETE FROM CallQue SQL command in the Telephone Number Loader's SQL Command Window (text box at bottom of call data display grid).

[Guest BlackBird]

As always thank you very much for your clear & concise replies, VG Support rocks!