diff options
| author | Sean Bright <sean.bright@gmail.com> | 2017-04-19 16:08:39 -0400 |
|---|---|---|
| committer | Sean Bright <sean.bright@gmail.com> | 2017-04-19 16:43:55 -0500 |
| commit | c47b3e74d232820b79aa53c61a8fca112d128d20 (patch) | |
| tree | 050a815071dfd8e50ee23c875fcb7f950764c602 /sample.call | |
| parent | b84abac1449c56d6c9f781525a533691b326ad8c (diff) | |
pbx: Use same thread if AST_OUTGOING_WAIT_COMPLETE specified
Both ast_pbx_outgoing_app() and ast_pbx_outgoing_exten() cause the core
to spawn a new thread to perform the dial. When AST_OUTGOING_WAIT_COMPLETE
is passed to these functions, the calling thread will be blocked until
the newly created channel has been hung up.
After this patch, we run the dial on the current thread rather than
spawning a new one. The only in-tree code that passes
AST_OUTGOING_WAIT_COMPLETE is pbx_spool, so you should see reduced
thread usage if you are using .call files.
Change-Id: I512735d243f0a9da2bcc128f7a96dece71f2d913
Diffstat (limited to 'sample.call')
0 files changed, 0 insertions, 0 deletions