diff options
| author | Matthew Jordan <mjordan@digium.com> | 2014-02-16 03:25:15 +0000 |
|---|---|---|
| committer | Matthew Jordan <mjordan@digium.com> | 2014-02-16 03:25:15 +0000 |
| commit | 438a7abc279bbcd6e0e770b72d5023555a86c7fd (patch) | |
| tree | 7f31c113b180abf806c3516f47c2e7df410d0021 /res/res_pjsip_registrar.c | |
| parent | 7e506c185ccbe8203e6e7ed21dec3db82c37c89d (diff) | |
pbx: Handle a completely empty dialplan during a context merge
It is highly unlikely, but - at least in Asterisk 12 - theoretically possible
to load Asterisk with no dialplan whatsoever. If that occurs, and some other
module (that is not a pbx module) attempts to merge its contexts into the
dialplan, the existing merge routine will crash. This is because it is not
insane, and rightly believes that you provided some sort of dialplan,
somewhere.
This patch will gracefully merge the contexts in such a case. Note that this
is highly unlikely to occur in 1.8/11, as features will most likely provide
some dialplan via parking. However, in Asterisk 12, parking is now provided
by res_parking, and hence may create its dialplan later.
(closes issue ASTERISK-23297)
Reported by: CJ Oster
Review: https://reviewboard.asterisk.org/r/3222
........
Merged revisions 408200 from http://svn.asterisk.org/svn/asterisk/branches/1.8
........
Merged revisions 408201 from http://svn.asterisk.org/svn/asterisk/branches/11
........
Merged revisions 408220 from http://svn.asterisk.org/svn/asterisk/branches/12
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@408227 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'res/res_pjsip_registrar.c')
0 files changed, 0 insertions, 0 deletions