ggm Report post Posted 01/31/2008 07:51 PM c:\program files\voiceguide\vgmulti.exe COULD NOT BE FOUND i have been trying do establish a basic setup of the chatline script with no luck, any help would be appreciated . please help! i am also trying to configure this for voip. any help on that aspect would be great also. thanks in advance I HAVE EDITED THE FILE CONFIG.XML <?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:\chatline\scripts\login.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:\chatline\scripts\login.vgs</Script> <AllowDialOut>1</AllowDialOut> </Channel> - <Channel> <Device_Voice>dxxxB1C3</Device_Voice> <Device_Network>iptB1T3</Device_Network> <Device_Media>ipmB1C3</Device_Media> <Protocol>IP</Protocol> <script>C:\chatline\scripts\login.vgs</Script> <AllowDialOut>1</AllowDialOut> </Channel> - <Channel> <Device_Voice>dxxxB1C4</Device_Voice> <Device_Network>iptB1T4</Device_Network> <Device_Media>ipmB1C4</Device_Media> <Protocol>IP</Protocol> <script>C:\chatline\scripts\login.vgs</Script> <AllowDialOut>1</AllowDialOut> </Channel> </Channels> <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 Display : Description 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 Display : Description. 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 /> <Protocol /> <RegServer1 /> <RegServer /> <RegClient /> <LocalAlias /> </VoIP_Registration> </VoIP_Registrations> - <VoIP_Authentications> - <VoIP_Authentication> <Display /> <Domain /> <Username /> <AuthUsername /> <AuthPassword /> </VoIP_Authentication> </VoIP_Authentications> - <Examples> <Notes>The following examples were taken from: http://www.voiceguide.com/vghelp/source/ht...IP_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> <Domain>fwd.pulver.com</Domain> <Username>sip:123456@fwd.pulver.com</Username> <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> <Domain>iptel.org</Domain> <Username>sip:MyIptelAccountName@iptel.org</Username> <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> <Domain>voxalot.com</Domain> <Username>sip:123456@voxalot.com</Username> <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> <Domain>callcentric.com</Domain> <Username>sip:177711111111@callcentric.com</Username> <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> <Domain>iinetphone.iinet.net.au</Domain> <Username>sip:0299998888@sip.NSW.iinet.net.au</Username> <AuthUsername>0299998888</AuthUsername> <AuthPassword>abcd1234</AuthPassword> </VoIP_Authentication> </VoIP_Authentications> </Examples> </VoIP_Lines> </VoiceGuideConfig> Share this post Link to post
SupportTeam Report post Posted 01/31/2008 10:32 PM The "Set Current Script" button is only used in v6 of VoiceGuide, not in v7. In v7 the script needs to be set in Config.xml file, which we can see is what you have done already. The latest versions of v7 do not have this button on the Script Designer. Share this post Link to post
