Cause 0

[Lukas]

Hi,

we have a problem with 1 serwer the calls are sometimes rejected with cause 0. In log of VG are no trace.

After restarting VG, connections will be accepted for some time

[SupportTeam]

What device/system is this trace from?

Does this trace show on which E1 ISDN trunk and which channels of that trunk the call was attempted to be sent ?

Can you also please post ktTel trace for that day. Please .ZIP up any traces before posting.

 

[Lukas]

The device is Dinstar MTG2000 in the 3rd column is port to which connected the serwer VG. In the 4th column is the port number to which the connection entered

The log in attach

1104_ktTel.rar

[SupportTeam]

This system is using an older version of VoiceGuide v7.6

Can you please update your system to latest v7.6 version which is available for download from our WWW Downloads page.

If you still encounter issues then please post ktTel trace and Dinstar trace as before.

Also, please ensure that the system time on Dinstar closely matches the system time on VoiceGuide system. Right now they seem a bit off.

 

You can quickly change between the  different versions of VoiceGuide v7 by just running the VoiceGuide installer. See below for changing from one version to another:

1. Stop VoiceGuide Service and exit all VoiceGuide programs. (eg Script Designer, Line Status Monitor, etc) and all other programs.

2. Run the VoiceGuide installer and install into same directory as existing installation. (Do NOT uninstall the previous VoiceGuide installation).

3. Start VoiceGuide service.

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.

[SupportTeam]

You will require a new license code for the latest v7.6. The license code has now been forwarded to your email address.

[Lukas]

We update VG i 2020.

[SupportTeam]

Can you please expand or post your question/comment again? I assume that updating to latest version has resolved the issue that you encountered?

[Lukas]

we will do the update in 2020 because now we have a lot of traffic and we cannot afford one server not working

[SupportTeam]

The issue that is showing up on this server is a known bug that was present in the version currently installed on your system, and was fixed in later releases.

Installing the latest release (current release version is v7.6.15) will fix this issue.