Register VG SIP

[Lars Golze]

Hello VG Support Team,

i try to start the VG Service and it stopts directly.

Can you see any issue?

Attached the VG Log, WireShark trace and VG Config.

Thanks!!!

2024-12-13.zip

[SupportTeam]

ktTel trace shows that Dialogic HMP drivers returned error when VoiceGuide called the initial 'gc_start' function in those drivers.

It looks like you are using a Windows 10 based system, and the Dialogic HMP drivers installed on this system are release 548.

Release 548 should not be used on Windows 10.

Please see our Downloads page and download the version of Dialogic HMP intended for use with Windows 10. (currently that is release 540).

 

To change to a different version of Dialogic HMP:

1.    Stop the Dialogic service. You can use the Dialogic Configuration Manager (DCM) to stop the service.
2.    Uninstall Dialogic HMP drivers fully (do not save configuration).
3.    Reboot machine.
4.    Install the new version of Dialogic HMP. (You need to run the installer "As Administrator". Right click on the installer .exe to bring up menu that has that option).
5.    Reboot machine.
6.    Open the Dialogic Configuration Manager (DCM) and start the Dialogic service.

 

078 103708.694  1944         ERROR gc_start hmp
079 103708.694  1944         ERROR StartDialogicGlobalCall returned -1

[SupportTeam]

Also, is this system running a physical hardware, or on some sort of virtual machine?

Dialogic HMP only supports ESXi based virtual machines.

[Lars Golze]

Hello, I have tried to register the line via Microsip. In WireShark you can see that it works.

What am I doing wrong with VoiceGuide?

Attached are the logs!

Thank you very much!!!

 

Edited 02/04/2025 11:44 PM by SupportTeam
logs removed

[SupportTeam]

The <AuthUsername> in <VoIP_Authentication> should be the number that you are registering. Otherwise HMP does not know which <VoIP_Authentication> entry to use to respond to the '407 Proxy Authentication Required'.

Please try with this in your Config.xml:

<VoIP_Registrations>
<VoIP_Registration>
<Display>112</Display>
<Protocol>SIP</Protocol>
<RegServer>bdlgmbh.my3cx.de</RegServer>
<RegClient>054@bdlgmbh.my3cx.de</RegClient>
<LocalAlias>054@192.168.2.172</LocalAlias>
<Expires></Expires>
</VoIP_Registration>
</VoIP_Registrations>


<VoIP_Authentications>
<VoIP_Authentication>
<Display></Display>
<Realm></Realm>
<Identity></Identity>
<AuthUsername>054</AuthUsername>
<AuthPassword>enter_the_password_here</AuthPassword>
</VoIP_Authentication>
</VoIP_Authentications>

with the "enter_the_password_here" replaced with the password that is set on your 3CX PBX to authenticate the 054 extension.

Also, please note below:

SECURITY_NOTE: Please change the password used on SIP accounts after posting any configuration files for those accounts.

SECURITY_NOTE: Please change the password used on the SIP account after posting any WireShark traces that capture SIP registrations or call authentications. Otherwise, if password is too simple, it can be cracked from the posted WireShark trace. If other parties crack your password then they can start making calls through your account, which can result in large call charges on your SIP account.