Fortinet white logo
Fortinet white logo

Resolved issues

Resolved issues

The following issues have been fixed in the FortiVoice 7.0.5 release. For inquiries about a particular bug, contact Fortinet Customer Service and Support.

Bug ID

Description

980364

FortiVoice shows logs with voicemail-related errors.

1046732 The cloning of an auto-dialer campaign and some other actions, causes the campaign to fail and the CPU usage to go to 100%.

1051614

FortiVoice replaces the acute accent (é) with a question mark (?) in imported extensions.

1051616

FortiVoice does not assign a default emergency zone type to imported extensions that have unspecified emergency zone types.

1051628 The QR code of the FortiFone mobile app uses an internal IP address but with an external provisioned HTTPS port.

1051635

The incoming call does not ring the analog extension when that extension is configured as a secondary account.

1053360 When a call queue extension has the do not disturb (DND) setting enabled, the extension rings when it receives an incoming call.

1057411

FortiVoice shows a delay when connecting internal and external calls.

1058874

When the administrator selects Download > All in Monitor > Storage > Recorded Call, Download > All, FortiVoice generates an empty .tgz file.

1059956

Uppercase letters in the schedule name (Phone System > Profile > Schedule) causes FortiVoice to ignore the schedule.

1064095 When using the call me option to record a voicemail greeting, the FortiVoice user portal and admin portal are experiencing issues.
1067434 When an interface port (System > Network > Network, Port) has DHCP enabled and FortiVoice has SIPPnP enabled (System > Advanced > Auto Provisioning), FortiVoice fails to register phones.

1071777

The Remote cache quota (Call Feature > Call Recording > Archive) cannot exceed 20 GB.

1071921 When updating an analog trunk, FortiVoice shows an incorrect error message.

1074141

FortiFone softclient for Android is unable to receive incoming calls.

Resolved issues

Resolved issues

The following issues have been fixed in the FortiVoice 7.0.5 release. For inquiries about a particular bug, contact Fortinet Customer Service and Support.

Bug ID

Description

980364

FortiVoice shows logs with voicemail-related errors.

1046732 The cloning of an auto-dialer campaign and some other actions, causes the campaign to fail and the CPU usage to go to 100%.

1051614

FortiVoice replaces the acute accent (é) with a question mark (?) in imported extensions.

1051616

FortiVoice does not assign a default emergency zone type to imported extensions that have unspecified emergency zone types.

1051628 The QR code of the FortiFone mobile app uses an internal IP address but with an external provisioned HTTPS port.

1051635

The incoming call does not ring the analog extension when that extension is configured as a secondary account.

1053360 When a call queue extension has the do not disturb (DND) setting enabled, the extension rings when it receives an incoming call.

1057411

FortiVoice shows a delay when connecting internal and external calls.

1058874

When the administrator selects Download > All in Monitor > Storage > Recorded Call, Download > All, FortiVoice generates an empty .tgz file.

1059956

Uppercase letters in the schedule name (Phone System > Profile > Schedule) causes FortiVoice to ignore the schedule.

1064095 When using the call me option to record a voicemail greeting, the FortiVoice user portal and admin portal are experiencing issues.
1067434 When an interface port (System > Network > Network, Port) has DHCP enabled and FortiVoice has SIPPnP enabled (System > Advanced > Auto Provisioning), FortiVoice fails to register phones.

1071777

The Remote cache quota (Call Feature > Call Recording > Archive) cannot exceed 20 GB.

1071921 When updating an analog trunk, FortiVoice shows an incorrect error message.

1074141

FortiFone softclient for Android is unable to receive incoming calls.