| Summary: | ASTERISK-09522: distinctivering context isn't getting set | ||
| Reporter: | Brett Thorson (thor101) | Labels: | |
| Date Opened: | 2007-05-25 13:53:58 | Date Closed: | 2007-05-26 23:15:14 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/Configuration |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | When a distinctive ring is detected, it is supposed to send the call to one of the contexts defined by dringNcontext= That isn't happening. An error appears that says this: -- Detected ring pattern: 389,336,149 -- Checking 0,0,3 -- Checking 388,337,148 -- Distinctive Ring matched context == Starting Zap/1-1 at ,s,1 failed so falling back to exten 's' == Starting Zap/1-1 at ,s,1 still failed so falling back to context 'default' -- Executing [s@default:1] Wait("Zap/1-1", "15") in new stack the context for this dring is set to "incoming" which is defined in extensions.conf However, it never gets there. Instead the call is routed to the hardcoded oops context of "default". | ||
| Comments: | By: Jason Parker (jparker) 2007-05-26 23:15:00 Fixed in svn branch 1.4 in revision 66244 (same patch also fixes issue 9808). Should not be an issue in trunk. | ||