Voip Lines Section In Config.xml File Is Not Found

[Guest LordMark]

Hello Guys I am Trying to make Voice Guide Register itself as an Extension on a 3cx PBX Server. i found out That you would have to configure The Voip Line section of the Config.xml File. i located the file where it was installed in the directory:("D:\Program Files\VoiceGuide\conf\Config.xml". I Opened to Edit The Entries and found out that there were no Voip Lines Section in the Config.Xml. Below is a copy of the Config.xml file for you to see. i am using the evaluation edition of voice guide v7. and my Operating system is windows Xp Pro and it is installed on the D Partition of the Hard Drive.

 

<?xml version="1.0"?>

 

<VoiceGuideConfig>

 

<Devices_Dialogic>

 

<Channels>

 

<Channel>

<Name>dxxxB1C1</Name>

<NetworkIf>dxxxB1C1</NetworkIf>

<Protocol>pdk_na_an_io</Protocol>

<RingsBeforeAnswer>2</RingsBeforeAnswer>

<script>C:\Program Files\VoiceGuide\Scripts\Credit Card Payment\Credit Card Payment.vgs</Script>

<ConfigLine></ConfigLine>

<AllowDialOut>1</AllowDialOut>

<RV></RV>

</Channel>

 

 

<Channel>

<Name>dxxxB1C2</Name>

<NetworkIf>dxxxB1C2</NetworkIf>

<Protocol>pdk_na_an_io</Protocol>

<RingsBeforeAnswer>2</RingsBeforeAnswer>

<script>C:\Program Files\VoiceGuide\Scripts\Credit Card Payment\Credit Card Payment.vgs</Script>

<ConfigLine></ConfigLine>

<AllowDialOut>1</AllowDialOut>

<RV></RV>

</Channel>

 

 

<Channel>

<Name>dxxxB1C3</Name>

<NetworkIf>dxxxB1C3</NetworkIf>

<Protocol>pdk_na_an_io</Protocol>

<RingsBeforeAnswer>2</RingsBeforeAnswer>

<script>C:\Program Files\VoiceGuide\Scripts\Credit Card Payment\Credit Card Payment.vgs</Script>

<ConfigLine></ConfigLine>

<AllowDialOut>1</AllowDialOut>

<RV></RV>

</Channel>

 

 

<Channel>

<Name>dxxxB1C4</Name>

<NetworkIf>dxxxB1C4</NetworkIf>

<Protocol>pdk_na_an_io</Protocol>

<RingsBeforeAnswer>2</RingsBeforeAnswer>

<script>C:\Program Files\VoiceGuide\Scripts\Credit Card Payment\Credit Card Payment.vgs</Script>

<ConfigLine></ConfigLine>

<AllowDialOut>1</AllowDialOut>

<RV></RV>

</Channel>

 

</Channels>

 

 

 

<Parameters_DxBd>

 

<Notes>

**********************************************************************************************************

**********************************************************************************************************

 

DXBD_ (voice board) parameters

 

Parameters specified here will be set for every DX (voice)

board found to be started by the DCM in the system.

 

**********************************************************************************************************

**********************************************************************************************************

</Notes>

 

 

<Parameter>

<Description>Flash time during dialing (10ms units)</Description>

<Key>DXBD_FLASHTM</Key>

<Value>10</Value>

<Default>10</Default>

</Parameter>

 

<NotUsedByDefault>

 

<Notes>

MF param setting causes long delays on some boards.

Remove NotUsedByDefault tags if the MF param setting is desired.

</Notes>

 

<Parameter>

<Description>MF Interdigit Delay (10 ms units)</Description>

<Key>DXBD_MFDELAY</Key>

<Value>6</Value>

<Default>6</Default>

</Parameter>

 

<Parameter>

<Description>MF Length of LKP Tone Maximum value: 15 (10 ms units)</Description>

<Key>DXBD_MFLKPTONE</Key>

<Value>10</Value>

<Default>10</Default>

</Parameter>

 

<Parameter>

<Description>Minimum MF On. Added to the standard MF tone duration before the tone is detected. (10 ms units)

The minimum detection duration is 65 ms for KP tones and 40 ms for all other tones.</Description>

<Key>DXBD_MFMINON</Key>

<Value>0</Value>

<Default>0</Default>

</Parameter>

 

<Parameter>

<Description>MF Minimum Tone Duration (10 ms units)</Description>

<Key>DXBD_MFTONE</Key>

<Value>6</Value>

<Default>6</Default>

</Parameter>

 

</NotUsedByDefault>

 

 

<Parameter>

<Description>Minimum Loop Current off time before it is reported</Description>

<Key>DXBD_MINLCOFF</Key>

<Value>50</Value>

<Default>50</Default>

</Parameter>

 

 

<Parameter>

<Description>Minimum offhook time</Description>

<Key>DXBD_MINOFFHKTM</Key>

<Value>250</Value>

<Default>250</Default>

</Parameter>

 

<Parameter>

<Description>Minimum Silence Off</Description>

<Key>DXBD_MINSLOFF</Key>

<Value>2</Value>

<Default>2</Default>

</Parameter>

 

<Parameter>

<Description>Minimum Silence On</Description>

<Key>DXBD_MINSLON</Key>

<Value>1</Value>

<Default>1</Default>

</Parameter>

 

<Parameter>

<Description>Minimum DTI Off - minimum time required between rings-received events</Description>

<Key>DXBD_MINTIOFF</Key>

<Value>5</Value>

<Default>5</Default>

</Parameter>

 

<Parameter>

<Description>Minimum DTI On - minimum time required for rings received event</Description>

<Key>DXBD_MINTION</Key>

<Value>5</Value>

<Default>5</Default>

</Parameter>

 

<Parameter>

<Description>Offhook Delay - period after offhook, during which no events are generated

e.g., no DTMF digits will be detected during this period.</Description>

<Key>DXBD_OFFHDLY</Key>

<Value>50</Value>

<Default>50</Default>

</Parameter>

 

<Parameter>

<Description>Pause Time. Delay caused by a comma in the dialing string (10ms units)</Description>

<Key>DXBD_PAUSETM</Key>

<Value>100</Value>

<Default>100</Default>

</Parameter>

 

<Parameter>

<Description>Silence and Non-silence Debounce</Description>

<Key>DXBD_S_BNC</Key>

<Value>4</Value>

<Default>4</Default>

</Parameter>

 

<Parameter>

<Description>DTMF Interdigit Delay. Time between digits in DTMF dialing (10ms units)</Description>

<Key>DXBD_T_IDD</Key>

<Value>15</Value>

<Default>10</Default>

</Parameter>

 

<Parameter>

<Description>DTMF length (duration) for dialing (10ms units)</Description>

<Key>DXBD_TTDATA</Key>

<Value>10</Value>

<Default>10</Default>

</Parameter>

 

<Parameter>

<Description>Silence on and off debounce time (10ms units)</Description>

<Notes>debunce length should be really small so that

we can easily tell when the transition happens</Notes>

<Key>DXBD_S_BNC</Key>

<Value>4</Value>

<Default>4</Default>

</Parameter>

 

</Parameters_DxBd>

 

</Devices_Dialogic>

 

 

 

<Dialer>

 

<OutDialQue_ADODB_Provider>VistaDB.NET20</OutDialQue_ADODB_Provider>

<OutDialQue_Database>vgDb.vdb3</OutDialQue_Database>

<OutDialQue_ConnectString>Data Source='$DATABASE';Open Mode=NonexclusiveReadWrite</OutDialQue_ConnectString>

<OutDialQue_SqlPrefix></OutDialQue_SqlPrefix>

<OutDialQue_SqlSuffix>ORDER BY Priority ASC</OutDialQue_SqlSuffix>

 

</Dialer>

 

 

 

 

</VoiceGuideConfig>

[SupportTeam]

When installing VoiceGuide you need to ensure that you select the "VoIP" option, and not the default "Dialogic cards" option. Then VoiceGuide will be installed to function in VoIP mode and the VoIP config files will be installed.

 

Please uninstall VG and then install it again, this time selecting the VoIP option.

[Guest LordMark]

Thank you very Much. I did Just That and it worked. Thanks Again. Now i Have Another Problem. I cant Get Voice Guide to Register with 3CX SIP Srver. Bellow is the Config.xml i Edited, Please I dont Know if i Did it wrong. and if you Guys can Help wit a Config that works with 3CX, i would Be Highly Indebted. Thank you for your Promt Responses. Please Note Voice Guide is Installed on The Same Server where 3CX is Installed. The Servers IP Address is: 96.0.0.243 and The Extension Created for Voiceguide is 1003, The ID = 1003, Password = 1003.

 

Thank you

 

<?xml version="1.0"?>

 

<VoiceGuideConfig>

 

<Devices_Dialogic>

 

<Channels>

 

<Channel>

<Device_Voice>dxxxB1C1</Device_Voice>

<Device_Network>iptB1T1</Device_Network>

<Device_Media>ipmB1C1</Device_Media>

<Protocol>IP</Protocol>

<script>C:\Program Files\VoiceGuide\Scripts\Credit Card Payment\Credit Card Payment.vgs</Script>

<AllowDialOut>1</AllowDialOut>

</Channel>

 

<Channel>

<Device_Voice>dxxxB1C2</Device_Voice>

<Device_Network>iptB1T2</Device_Network>

<Device_Media>ipmB1C2</Device_Media>

<Protocol>IP</Protocol>

<script>C:\Program Files\VoiceGuide\Scripts\Credit Card Payment\Credit Card Payment.vgs</Script>

<AllowDialOut>1</AllowDialOut>

</Channel>

 

</Channels>

 

<Parms>

</Parms>

 

</Devices_Dialogic>

 

 

<VoIP_Lines>

 

<Notes>

Pretty much any VoIP line can be registered for use with VoiceGuide.

This includes extensions from internal VoIP PBXs or lines from VoIP providers.

 

For a list of VoIP service providers please see:

www.voipproviderslist.com

www.myvoipprovider.com

 

Here is a description of Registration and Authentication fields:

 

-------------------------------------------------------------------

VoIP_Registration

 

Protocol : "SIP" or "H323"

RegServer : Name or IP address of the SIP server. eg: "101.102.103.104" or "sip.examplevoipservice.com"

RegClient : VoIP Username. eg: "bob" or "bob@10.20.30.40"

LocalAlias : Local Alias for this line/extension. eg: "someone@someplace.com"

-------------------------------------------------------------------

VoIP_Authentication

 

Realm : For which VoIP server this registration applies. eg: "example.com"

Identity : Full VoIP address for this login. eg: "sip:bob@example.com"

AuthUsername : Autnetication Username. eg: "bob"

AuthPassword : Autnetication Password. eg: "password1"

-------------------------------------------------------------------

</Notes>

 

<VoIP_Registrations>

 

<VoIP_Registration>

<Display></Display>

<Protocol>SIP</Protocol>

<RegServer1></RegServer1>

<RegServer>96.0.0.243</RegServer>

<RegClient>1003@96.0.0.243</RegClient>

<LocalAlias>sip:1003@96.0.0.243:5060</LocalAlias>

</VoIP_Registration>

 

</VoIP_Registrations>

 

<VoIP_Authentications>

 

<VoIP_Authentication>

<Display></Display>

<Realm>3cx</Realm>

<Identity></Identity>

<AuthUsername>1003</AuthUsername>

<AuthPassword>1003</AuthPassword>

</VoIP_Authentication>

 

</VoIP_Authentications>

 

 

<Examples>

 

<Notes>

The following examples were taken from:

http://www.voiceguide.com/vghelp/source/html/config_VoIP_Register.htm

Please read the Help file page above for more information on configuring

VoIP Registration and Authentication.

</Notes>

 

 

<VoIP_Registrations>

<VoIP_Registration>

<Display>FWD Free World Dialup (www.freeworlddialup.com)</Display>

<Protocol>SIP</Protocol>

<RegServer>fwd.pulver.com</RegServer>

<RegClient>123456@fwd.pulver.com</RegClient>

<LocalAlias>123456@10.1.1.9</LocalAlias>

</VoIP_Registration>

</VoIP_Registrations>

<VoIP_Authentications>

<VoIP_Authentication>

<Display>FWD</Display>

<Realm>fwd.pulver.com</Realm>

<Identity>sip:123456@fwd.pulver.com</Identity>

<AuthUsername>123456</AuthUsername>

<AuthPassword>abcd1234</AuthPassword>

</VoIP_Authentication>

</VoIP_Authentications>

 

 

 

<VoIP_Registrations>

<VoIP_Registration>

<Display>iptel iptel.org (www.iptel.org) </Display>

<Protocol>SIP</Protocol>

<RegServer>iptel.org</RegServer>

<RegClient>MyIptelAccountName@iptel.org</RegClient>

<LocalAlias>MyIptelAccountName@10.1.1.9</LocalAlias>

</VoIP_Registration>

</VoIP_Registrations>

<VoIP_Authentications>

<VoIP_Authentication>

<Display>iptel</Display>

<Realm>iptel.org</Realm>

<Identity>sip:MyIptelAccountName@iptel.org</Identity>

<AuthUsername>MyIptelAccountName</AuthUsername>

<AuthPassword>abcd1234</AuthPassword>

</VoIP_Authentication>

</VoIP_Authentications>

 

 

<VoIP_Registrations>

<VoIP_Registration>

<Display>voxalot voxalot (www.voxalot.com) </Display>

<Protocol>SIP</Protocol>

<RegServer>voxalot.com</RegServer>

<RegClient>123456@voxalot.com</RegClient>

<LocalAlias>123456@10.1.1.9</LocalAlias>

</VoIP_Registration>

</VoIP_Registrations>

<VoIP_Authentications>

<VoIP_Authentication>

<Display>voxalot</Display>

<Realm>voxalot.com</Realm>

<Identity>sip:123456@voxalot.com</Identity>

<AuthUsername>123456</AuthUsername>

<AuthPassword>abcd1234</AuthPassword>

</VoIP_Authentication>

</VoIP_Authentications>

 

 

<VoIP_Registrations>

<VoIP_Registration>

<Display>CallCentric (www.callcentric.com) </Display>

<Protocol>SIP</Protocol>

<RegServer>callcentric.com</RegServer>

<RegClient>177711111111@callcentric.com</RegClient>

<LocalAlias>177711111111@10.1.1.9</LocalAlias>

</VoIP_Registration>

</VoIP_Registrations>

<VoIP_Authentications>

<VoIP_Authentication>

<Display>CallCentric</Display>

<Realm>callcentric.com</Realm>

<Identity>sip:177711111111@callcentric.com</Identity>

<AuthUsername>177711111111</AuthUsername>

<AuthPassword>abcd1234</AuthPassword>

</VoIP_Authentication>

</VoIP_Authentications>

 

 

<VoIP_Registrations>

<VoIP_Registration>

<Display>iiNet - BroadSoft BroadWorks platform (www.broadsoft.com) : iinet.net </Display>

<Protocol>SIP</Protocol>

<RegServer>sip.NSW.iinet.net.au</RegServer>

<RegClient>0299998888@sip.NSW.iinet.net.au</RegClient>

<LocalAlias>0299998888@10.1.1.9</LocalAlias>

</VoIP_Registration>

</VoIP_Registrations>

<VoIP_Authentications>

<VoIP_Authentication>

<Display>iiNet</Display>

<Realm>iinetphone.iinet.net.au</Realm>

<Identity>sip:0299998888@sip.NSW.iinet.net.au</Identity>

<AuthUsername>0299998888</AuthUsername>

<AuthPassword>abcd1234</AuthPassword>

</VoIP_Authentication>

</VoIP_Authentications>

 

 

</Examples>

 

</VoIP_Lines>

 

 

<Dialer>

 

<OutDialQue_ADODB_Provider>VistaDB.NET20</OutDialQue_ADODB_Provider>

<OutDialQue_Database>vgDb.vdb3</OutDialQue_Database>

<OutDialQue_ConnectString>Data Source='$DATABASE';Open Mode=NonexclusiveReadWrite</OutDialQue_ConnectString>

<OutDialQue_SqlPrefix></OutDialQue_SqlPrefix>

<OutDialQue_SqlSuffix>ORDER BY Priority ASC</OutDialQue_SqlSuffix>

 

</Dialer>

 

 

</VoiceGuideConfig>

[SupportTeam]

Not sure that you'd be able to have VoIP server on same machine. Both systems would want to use the 5060 SIP port...

 

Are you able to set the VoIP Server to use a different port?

 

Please start a new topic on this, as this is a different question.

[Guest LordMark]

Ok i will Do Just That. Thank You Very Much