| Summary: | ASTERISK-19749: Calendar EWS can't force event trigger to execute dialplan context without adding channel to calendar.conf | ||
| Reporter: | Eric Person (eperson) | Labels: | |
| Date Opened: | 2012-04-17 16:26:10 | Date Closed: | 2012-04-24 12:32:06 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Resources/res_calendar_ews |
| Versions: | 1.8.11.0 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Linux asteriskcolo1.hitachi-hta.com 2.6.32-220.7.1.el6.x86_64 #1 SMP Wed Mar 7 00:52:02 GMT 2012 x86_64 x86_64 x86_64 GNU/Linux | Attachments: | |
| Description: | When calendar event is pulled from Exchange EWS, the only way I can get the context and extension execution is by adding a channel value in the calendar.conf. I need to execute the dialplan context once the event is pulled from EWS without dialing a channel. Thanks in advance. | ||
| Comments: | By: Eric Person (eperson) 2012-04-19 12:55:22.447-0500 Found a workaround by using a local channel in calendar.conf to just answer call in dialplan and immediately hangup. Seems a bit quirky but it works. I'm not sure if this is the intended design but it seems to me it would make more sense to allow the calendar in asterisk to function like a trigger regardless of whether or not a call is required. Feel free to close this if this is not a bug. Thanks By: Matt Jordan (mjordan) 2012-04-24 12:32:00.692-0500 I'm not sure how context/extension could be used without having a channel. Something executing in the dialplan *requires* a channel of some sort. In your case, as you realized, if all you need is an internal channel then Local channels are a good choice for this. | ||