How To Make Voice Guide Register On 3Cx Server

[Guest LordMark]

I have a Problem. I cant Get Voice Guide to Register with 3CX SIP Server. 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 or a Good Hint That would Help, 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.voiceguid...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>

<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]

Please Note Voice Guide is Installed on The Same Server where 3CX is Installed.

Not sure if you would be able to make this work.

Both apps would want to open same SIP port (5060) so you would need to change one of the apps to use a different SIP port to handle it's incoming SIP requests.

Not sure offhand how this can be changed on HMP side (you would need to read HMP manuals to find out). Perhaps the SIP PBX's setup can be easily changed?

Even if you were able to change one of the app's SIP port then you would then need to have all calls directed to this app be directed to its custom SIP port. In practice this would make system cumbersome to use.

 

Usually VoiceGuide would be installed on a different system to the SIP PBX.