Troubleshooting Tip: FortiVoice is not ending a SIP trunk call

[JHelio]

Description	This article describes what to do when FortiVoice is not ending a call due to a wrong route entry.
Scope	FortiVoice 6.0.9 version.
Solution	Network topology example: Ext AVAYA - trunk Avaya (10.99.95.10) <-> (10.83.0.2) FVC 500F (10.11.65.110) <-> (10.11.100.7) SIP ISP In this scenario, the call is ended by Avaya ext, but FortiVoice is not sending the BYE SIP message back to that Avaya ext. The packets show the BYE SIP message for such a call is sent out using a different destination IP and interface. Such IP 10.64.10.10 belong to FortiVoice port2 interface: config system interface     edit port2         set ip 10.64.10.10/28         set allowaccess https ping         set webaccess admin     next A route configured, that is not in use, appears: config system route     edit 1         set gateway 10.64.10.2         set interface port2     next Since the route is not in use but is installed in the routing table, it is recommended to reboot FortiVoice to clear routes in the cache. This error is caused by a wrong entry in the routing table.