Troubleshooting Tip: Configuration changes on an extensions does not take effect or unable to register an extension.
| Description | This article describes a way to fix 2 issues that can happen in the FortiVoice System.
|
| Scope | FortiVoice v6.0.8 & v6.4.9. |
| Solution | Example with issues registering a new extension configured in FortiFone 380B (v3.0.19 GA) A capture done in FortiFone and FortiVoice displays that FortiVoice replies with '401 Unauthorized' for those SIP-REGISTER packets sent from FortiFone that contain the authentication header information. Note: The issue is reproducible in the lab on FortiVoice v6.4.9 GA.
Both scenarios described as issues with FortiVoice require a regeneration of the extension configuration.
Solution: A newly introduced command, 'execute db reset voice-runtime', will address the issues, and it will be ready from 6.0.8 GA. |


