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.

 

[Lars Golze]

After changing the Conifg.xml, it reports invalid credentials.

[SupportTeam]

Can you please post the WireShark trace capturing the SIP registration attempt. We can then see what is happening on the system and advise.

[Lars Golze]

now i attached the WireShark trace.

2025-02-10.pcapng

[SupportTeam]

Trace shows that in response to the '407 Proxy Authentication Required' VoiceGuide/HMP is now sending  a new REGISTER response with the 'Proxy-Authorization' header in it. 

So VoiceGuide/HMP is finding the <VoIP_Authentication> section for the number/username 054, and is now using the password set in that entry's <AuthPassword> field to send a response to that '407 Proxy Auth Required' - 

The PBX however is now replying to that second register with "403 Invalid Credentials" :

 

Looking back at your successful MicroSIP register we can see that you have the Digest Username set to a different value then the extension number:

"kQIBTJNyb5" instead of "054" :

 

So looks like you have an 'Auth ID' / 'Auth Username' set on your configuration for this 3CX extension that is different to the extension number, and 3CX expects the 'Digest username' send in the second REGISTER to match that  'Auth ID', however VoiceGuide/HMP just sends the extension number again as the username. (Most PBXs use the telephone number as the 'username' in the Authentication - which is why VoiceGuide/HMP uses the number as the username again)

so to resolve your registration issue please do this:

In the 3CX configuration please set the 'Auth ID' / 'Auth Username' for the extension to be thee same as the extension number itself (054),

 

Note: The "403 Invalid Credentials" would also be returned by the 3CX if the Auth Password is incorrect, so if you still have issues after changing the 'Auth ID' then please confirm that password is correct.

 

Also: This probably will not apply to your system but going to include just in case:

Sometimes the PBXs are set to only accept registrations form certain phones, and in those cases the SIP 'User-Agent' header is checked by the PBX.

VoiceGuide allows changing the 'User-Agent' header it sends. This is done by editing the "UserAgent" entry in the [SIP] section of the VG.INI file and restarting the VoiceGuide service.

Your MicroSIP was sending UserAgent value of: 

MicroSIP/3.21.2

so if you ever need to, you can have VoiceGuide send out that that value for the UserAgent header to pretend that it's actually MicroSIP phone(s)

MicroSIP also has an option to change UserAgent value, so you can also use that to confirm if your PBX uses UserAgent to only allow certain devices to register with certain extensions.

 

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.

[Lars Golze]

I have replaced the Auth ID with the number "054". Now it looks better. Could you please take one more look?

2025-02-11.pcapng

[SupportTeam]

Registration looks ok. 3CX is responding with OK to the second REGISTER that contains the Proxy Authorization:

 

For other readers of this thread, this is the setting that needs to be changed in 3CX config to match the extension number:

[SupportTeam]

Attaching VoiceGuide to 3CX using as SIP trunk with IP based Authentication:

A fast way to create a connection from any IP-PBX to VoiceGuide IVR is to set up a SIP Trunk that points to the IP of the system where VoiceGuide IVR is installed, and then setup an Outbound Rule that sends calls to that SIP trunk.

Then any calls on the PBX that match that Outbound Rule will be sent by the PBX to VoiceGuide's IP address, and VoiceGuide will answer those calls - as VoiceGuide will just answer any calls that arrive at its IP address.

 

On 3CX PBX the SIP Trunk is set up by going to:

Admin -> Voice & Chat and pressing the + Add Trunk button

And filling out the details for the new trunk, eg:

 

For "Type of Authentication" select "Do not require - IP based".

In this case any number can be set for "Main Trunk Number".

The "Default Route" is what to do with calls that are made from VoiceGuide. If you want VoiceGuide to only handle inbound calls from 3CX then you can just set this to 'End Call'.

Then go to: Admin -> Outbond Rules and click on + Add button.

In the "Calls to numbers starting with" field set the number (or prefix), that, when dialed or transferred to, is to send calls to VoiceGuide. In example screenshot below we specified "300" - so any calls to "300" or "3001234" etc. will match.

Then in the "Route 1" dropdown box select the VoiceGuide SIP trunk that you have just created:

That's it.

Save the configuration and make a call from any PBX extension to the route number ("300" in our case) and you will see that call routed by 3CX to the IP of the VoiceGuide IVR system, and VoiceGuide will answer the call.

 

Note that using the SIP Trunk approach will usually let you set the maximum number of simultaneous calls that are allowed to be made over that trunk.

On 3CX this maximum number of calls is set here:

 

Please let us know if any questions