There was a subtle logical difference between 1.4 and trunk with regards to how timeouts
authorMark Michelson <mmichelson@digium.com>
Wed, 9 Apr 2008 17:48:33 +0000 (17:48 +0000)
committerMark Michelson <mmichelson@digium.com>
Wed, 9 Apr 2008 17:48:33 +0000 (17:48 +0000)
commit28bd5d88c15627cbc1856489b1ee2db171e49042
tree7b73a93c13bae697d6280737fe71dd6b17c462e8
parentd314fd5336cdb43e05c8eb8dfad509d50c5d6d6f
There was a subtle logical difference between 1.4 and trunk with regards to how timeouts
were handled. In 1.4, if the absolute timeout were reached on a call, no matter what
the return value of ast_spawn_extension was, the pbx would attempt to go to the 'T'
extension or hangup otherwise. The rearrangement of this function in trunk made this check
only happen in the case that ast_spawn_extension returned 0. If ast_spawn_extension returned
1, then the fact that the timeout expired resulted in a no-op, and would cause an infinite
loop to occur in __ast_pbx_run. This change fixes this problem. Now timeouts will
behave as they did in 1.4

(closes issue #11550)
Reported by: pj
Tested by: putnopvut

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@113836 65c4cc65-6c06-0410-ace0-fbb531ad65f3
main/pbx.c