Resolved issues
The following issues have been fixed in the FortiVoice 6.4.9 release. For inquiries about a particular bug, contact Fortinet Customer Service and Support.
Bug ID |
Description |
---|---|
712648 | The FortiVoice system is unable to send emails when the relay server name is using FQDN. |
898904 | The packet capture (.pcap) file from the FortiVoice system is showing inaccurate RTP packet losses. |
919062 | The auto attendant plays the default French message instead of the English audio file. |
932319 | For an inbound call from an external caller, the Call history on the phone is showing a different caller ID number than on the FortiVoice admin and user portals. |
934797 | The FortiVoice system fails to create call recordings when users perform attended transfers of outgoing external calls. |
934813 | The FortiVoice system generates empty call detail records (CDR) when users perform attended transfers of external outgoing calls. |
957614 |
When the configuration of a virtual number with an auto-attendant key includes Hang Up as the Follow action, the FortiVoice system can play the announcement when the caller presses the auto-attendant key but does not end the call. |
979654 | The FortiVoice system is showing a high-memory usage after upgrading to 7.0.1 GA. |
980891, 1014934 |
When a call is sent to a ring group and not answered, the FON-x80 phones do not show the notification of a missed call and the call entry is missing from the History menu. |
981730 | Using Reset Voice Messages (Extension > Extension > Preference > Select extension > Maintenance) does not delete the listened voicemails. |
984489 | Call center survey reports do not provide the name and extension of the agent who answered the call. |
985079 | When the FortiVoice administrator changes the SIP phone registration/subscription interval on survivability branch settings, 7 out of 84 branches show an Unsupported device type! error. |
986406 | A duplicate DID number on the secondary FortiVoice system is not reported as an error and causing the primary FortiVoice system to be out of synchronization. |
986540 | The PRI trunk stops working after upgrading the FortiVoice GT02 gateway from 6.4.7 to 6.4.8. |
986772 | Voice processes keep crashing after upgrading the FortiVoice system from 6.4.7 from 6.4.8 on Amazon Web Services (AWS). |
988063 | FortiVoice gateway GS16 ports allow the use of TLS versions 1.0 and 1.1 only. |
990422 | When the FortiVoice system routes calls to an office peer, they are treated as From (internal) > To (internal), instead of From (internal) > To (external). Call reports do not include the calls. |
992324 | When an inbound call is routed to the auto-attendant and then to the extension, the FortiVoice system sends out two UPDATE packets at the same time and then drops the call. |
993381 | When the administrator uses the override schedule feature, the FortiVoice system continues to use the same schedule. |
998240 |
When the user dials a remote extension, the FortiVoice system sends out the internal extension caller ID. |
1003774, 1005150 |
When the administrator creates a new group in Auto Dialer > Contact > Contact Group and expands the Members list, the sorting is random and the total count is unavailable. |
1007171 |
The FortiVoice system does not show CDRs for incoming and outgoing faxes that are processed by a fax machine connected to a FortiVoice Gateway GS16. |
1016694 |
The FortiVoice system does not allow the edit of Room condition descriptions (Hotel Management > Room Status > Edit > Guest Setting). |
1019798 |
The anytime schedule does not work when the override schedule is enabled. |