diff options
| author | russell <russell@f38db490-d61c-443f-a65b-d21fe96a405b> | 2006-07-25 19:51:31 +0000 |
|---|---|---|
| committer | russell <russell@f38db490-d61c-443f-a65b-d21fe96a405b> | 2006-07-25 19:51:31 +0000 |
| commit | ea73c30141baf0a943bce84b9002e7d606e2d08e (patch) | |
| tree | ca901bec7b5af2b9ed8df4886434c0dc38ac6aa3 /cli.c | |
| parent | 81146a9f92693f7c11989e4c4f865c94b1b9deb6 (diff) | |
This exact deadlock situation that I observed can't happen in trunk due to the
recent hold changes so that MOH is not started on the bridged channel directly.
However, the change is still not a bad idea.
Merged revisions 38200 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.2
........
r38200 | russell | 2006-07-25 15:43:38 -0400 (Tue, 25 Jul 2006) | 6 lines
This resolves a deadlock that a tech support customer was getting frequently
when his users would answer call waiting. If another thread is currently
holding the zt_pvt lock for the first channel, unlock both channels and let
asterisk retry the native bridge, just like what is done for the second channel
directly below these changes.
........
git-svn-id: http://svn.digium.com/svn/asterisk/trunk@38201 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'cli.c')
0 files changed, 0 insertions, 0 deletions