| Summary: | ASTERISK-07344: Forced bypass switch problem | ||
| Reporter: | Adam Simpson (asimpson) | Labels: | |
| Date Opened: | 2006-07-15 10:49:48 | Date Closed: | 2011-06-07 14:03:18 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | When using the forced bypass switch patch (Bug ASTERISK-5956019) the dial plan seems to stop functioning as expected whereas whereas if you use a regular switch statement such as: [mycontext] switch => Realtime/mycontext@extensions with the exact same dialplan, the dialplan works fine. In fact there are odd delays when using WaitExten and the 'i' invalid extension does not function at all. My dialplan is very simple (which is in my mysql database): [menu-1] s,1,Background(mygreeting) s,2,WaitExten 1,1,Playback(pls-hold-while-try) 1,2,Hangup i,1,Playback(invalid) i,2,Hangup When using the bypass switch, if I press 5 on my phone the CLI reports that it tries to goto extension 5 with a priority of 1 rather than the invalid extension. If I press 1 asterisk waits like 4 seconds before going to extension 1. If instead I just use a regular switch statement the menu-1 context rather than the bypass patch, everything works as expected without delays. | ||
| Comments: | By: Russell Bryant (russell) 2006-07-15 10:51:40 If you're having a problem with a patch that is from another report, please post your issues there, not in a new report. | ||