chrispopp Posted February 25, 2014 Report Share Posted February 25, 2014 I’m currently testing with a Vodia pbx version 5.2.0 (CentOS32) I’m having an issue where none of my auto-attendants’ Extension input option “When extension matches” does not work correctly. It provides the message “this extension does not exist” after the second digit is entered, even though all my extensions are 3 digits. Changing it to “3 digits” works correctly. [7] 9:22:03.321 APP: Received call from cell phone 4169459999, but VPA is turned off for extension 205@officetest.testinternal.com [8] 9:22:03.321 APP: Call state for call object 22: connected [8] 9:22:03.323 APP: Play audio_moh/noise.wav, caching true [8] 9:22:04.328 APP: Attendant: Timeout (wait) [8] 9:22:04.328 APP: Play recordings/att680.wav space20, caching false [6] 9:22:08.348 APP: Received DTMF 2, call type attendant [6] 9:22:08.868 APP: Received DTMF 0, call type attendant [8] 9:22:08.868 APP: Play audio_en/aa_not_existing.wav space20, caching false [8] 9:22:08.869 APP: Attendant: Ignoring the DTMF 0 in the state not_existing [6] 9:22:09.428 APP: Received DTMF 5, call type attendant [8] 9:22:09.429 APP: Play audio_en/aa_not_existing.wav space20, caching false [8] 9:22:09.429 APP: Attendant: Ignoring the DTMF 5 in the state not_existing Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted February 25, 2014 Report Share Posted February 25, 2014 Is there an overlap of extensions? For example, if you have an extension 20, then you will not be able to reach extensions with number 201, 202 and so on. Quote Link to comment Share on other sites More sharing options...
chrispopp Posted February 25, 2014 Author Report Share Posted February 25, 2014 Absolutely not, this was working correctly in version 5.1, decided to upgrade, and now I'm getting this. All extensions are either in alpha or 3 digit numeric. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted February 26, 2014 Report Share Posted February 26, 2014 Hmmm. We did not change anything in that area AFAICT. I guess we need to test this. Quote Link to comment Share on other sites More sharing options...
chrispopp Posted February 26, 2014 Author Report Share Posted February 26, 2014 Can you inform me asap. This is quite a severe bug IMO. I may roll back to 5.1 if this doesn't work. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted February 26, 2014 Report Share Posted February 26, 2014 ACK. This was caused by some internal "optimizations" for the database. Will be fixed in the next release. We'll try to make a build later today for Centos32. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.