VoiceGuide IVR Software Main Page
Jump to content

Register Multiple SIP extension

Recommended Posts

In your Config.xml you should have only one <VoIP_Registrations> section, with all individual <VoIP_Registration>  entries in that one <VoIP_Registrations> section.

Similarly, you should have only one <VoIP_Authentications> section, with all individual <VoIP_Authentication>  entries in that one <VoIP_Authentications> section.

Notice the plural "s" on the end of the sections that hold multiple individual registration/authentication sections.

see: https://www.voiceguide.com/vghelp/source/html/config_voip_register.htm

 

A simpler approach that usually requires less configuration may be to just create a SIP trunk on the PBX at 10.94.41.50 (which looks to be an NEC PBX) and point that SIP trunk to VoiceGuide's IP. VoiceGuide will automatically answer all SIP calls arriving to the system (need to set firewall to let them through of course).

But if you need to have VoiceGuide to register the individual extensions then that's fine as well.

 

Your Config.xml should look something like this:

<VoIP_Registrations>

<VoIP_Registration>
  <Display>MTA</Display>
  <Protocol>SIP</Protocol>
  <RegServer>10.94.41.50</RegServer>
  <RegClient>3232@10.94.41.50</RegClient>
  <LocalAlias>3232@10.92.102.85</LocalAlias>
</VoIP_Registration>


<VoIP_Registration>
  <Display>MTA</Display>
  <Protocol>SIP</Protocol>
  <RegServer>10.94.41.50</RegServer>
  <RegClient>3233@10.94.41.50</RegClient>
  <LocalAlias>3233@10.92.102.85</LocalAlias>
</VoIP_Registration>

... etc etc ...

</VoIP_Registrations>


<VoIP_Authentications>

<VoIP_Authentication>
  <Display>IVR</Display>
  <Realm></Realm>
  <Identity></Identity>
  <AuthUsername>3232</AuthUsername>
  <AuthPassword>3232</AuthPassword>
</VoIP_Authentication>


<VoIP_Authentication>
  <Display>IVR</Display>
  <Realm></Realm>
  <Identity></Identity>
  <AuthUsername>3233</AuthUsername>
  <AuthPassword>3233</AuthPassword>
</VoIP_Authentication>

... etc etc ...

</VoIP_Authentications>

 

 

Share this post


Link to post

After I modified the configuration file, I didn't see the same errors in the log file. Even though there is no same error in log file, why I can only see one port got registered in Wireshark log?

MTALog03242022_2.zip

Share this post


Link to post

This trace looks odd.

Can you please try fully stopping both the VoiceGuide service and the Dialogic service - make sure to wait till the Dialogic service has fully stopped - and then start the Dialogic service and the VoiceGuide service.

Please post the vgEngine and ktTel and WireShark traces as before.

Share this post


Link to post

Still has some strange errors in it. Can you please try using this latest version:

https://www.voiceguide.com/release/VoiceGuide_7.6.42.exe

Please ensure that you stop the Dialogic service after stopping the VoiceGuide service.

Dialogic service can be stopped using the the Dialogic Configuration Manager (DCM), or Windows' Services Applet.

As before, please post the vgEngine and ktTel and WireShark traces when using this latest version.

 

To change to a different version of VoiceGuide:

  1. Stop VoiceGuide Service. VoiceGuide can be stopped by clicking on the VoiceGuide Service Monitor in the Windows's Icon Tray on bottom right of the taskbar and selecting "Stop".
  2. Exit all VoiceGuide programs. This  includes the Service Monitor applet in the Icon Tray area in bottom right of the screen,  as well as the Script Designer, Line Status Monitor, etc.
  3. Do NOT uninstall the previous VoiceGuide installation.
  4. Stop the Dialogic service using the the Dialogic Configuration Manager (DCM), or Windows' Services Applet.
  5. Run the VoiceGuide install and install into same directory as existing installation.
  6. Start VoiceGuide service.

Note: Running a VoiceGuide install over the top of an existing install will NOT overwrite existing configuration or license files (Config.xml, ConfigLine.xml, VG.INI, etc) and will not remove any of users script or sound files, and will not remove any log files etc.

Share this post


Link to post

After I installed version 7.6.42, Wireshark log looks good. I am going to verify with PBX.

Thanks

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×