troubleshooting voiceguide registration

[TomP]

Hello Voiceguide team,

We're currently experiencing issues with the configuration of our client's login.

 

Enclosed for your analysis are the hmp log, the voiceguide log, the config, and a Wireshark capture file, which documented our failed logins.

 

We hope you can help us here and perhaps give us a clue as to the possible causes. Unfortunately, we don't get any error messages or anything like that. Currently, you can reach the stored phone number, but you will receive a "Busy" signal right after the ringing tone and the call will be terminated.

 

In parallel, we tested with the MikroSIP software. Here, a login works as desired and so does the telephony. The software (MikroSIP) was of course properly terminated before the dial-in attempt. 

 

Best regards

Tom Pasler

 

vg.zip

[SupportTeam]

WireShark trace shows that the REGISTER messages sent from HMP are not even replied to.

What is the device at 192.168.178.1 ?

Can you please post a WireShark capture of a working MicroSIP registration and the subsequent call connection?

[TomP]

the device at 192.168.178.1 is a normal isp router "AVM FritzBox7490"  

In this capture file you should see a successful registration with two phone calls, one in and one out. 

mikrosip.pcapng

[SupportTeam]

You would need to ask makers of "AVM FritzBox7490" as to why their device does not respond to SIP REGISTER messages issued to them from Dialogic HMP.

Maybe that device is configured to only accept SIP REGISTER from certain extension names/numbers? (sip-dienst@192.168.178.1 ?)

Can you try modifying the  <VoIP_Registration> section in VoiceGuide's Config.xml to be:

<VoIP_Registration>
  <Protocol>SIP</Protocol>
  <RegServer>192.168.178.1</RegServer>
  <RegClient>sip-dienst@192.168.178.1</RegClient>
  <LocalAlias>sip-dienst@192.168.178.50</LocalAlias>
</VoIP_Registration>

and then restart the Dialogic HMP and VoiceGuide series and make a WireShark capture again?

 

Another possibility is that your SIP PBX/Router restricts what device types they allow to Register with them:

Sometimes the PBXs are set to only accept registrations form certain phones, and in those cases often just the SIP 'User-Agent' header is checked by the PBX to confirm what device type is trying to connect.

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.

You can try setting it to:

MicroSIP

or

MicroSIP/3.22.3

and VoiceGuide will then send out that that value in the UserAgent header.

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 device types to register.