Troubleshooting Tip: How to solve issue of FortiFone no establish call voice due to codec mismatch '488 (No codecs approved)'

[JHelio]

Description	This article describes how to detect and solve the issue when a call voice is established due to codec mismatch.
Scope	FortiVoice v7.0.2.
Solution	In packet capture of the call, inside the SIP field, it is possible to find below the error message: SIP-INVITE info: response from: 'IT-BE Ricardo XXXX' <sip:8686XXXXX@172.29.0.5> to: <sip:705XXXX@172.29.0.5>, response: 488 (No codecs approved). Under extension configuration settings, find the codec order used at the profile extension: For example, here we modified the mobile phone G711u law codec as the first option. Call is established using G711u law, which can be confirmed by the CDR log record: Adjust the correct voice codec order supported for mobile phones for correct codec negotiation.