summaryrefslogtreecommitdiff
path: root/ztmonitor.c
diff options
context:
space:
mode:
authorqwell <qwell@5390a7c7-147a-4af0-8ec9-7488f05a26cb>2007-04-13 23:17:28 +0000
committerqwell <qwell@5390a7c7-147a-4af0-8ec9-7488f05a26cb>2007-04-13 23:17:28 +0000
commitdada4a9ae08e61724182a524fd4bb25b6188181d (patch)
tree09f7b4a234a2871c3c9d6b2f47537b41bc41bf71 /ztmonitor.c
parentb31c3e9ddacabb934b736b3ea3e9917babb1343f (diff)
Merged revisions 2423 via svnmerge from
https://origsvn.digium.com/svn/zaptel/branches/1.4 ................ r2423 | qwell | 2007-04-13 18:14:33 -0500 (Fri, 13 Apr 2007) | 22 lines Merged revisions 2422 via svnmerge from https://origsvn.digium.com/svn/zaptel/branches/1.2 ........ r2422 | qwell | 2007-04-13 18:12:23 -0500 (Fri, 13 Apr 2007) | 14 lines Fix several places where we treat confmode as a bitmask. It is a bitmask...sort of.. I'll explain.. confmode is used for 2 different things. It defines both the "mode" and the "flags" of the conference. The "mode" part is in 0x00FF and is NOT bitwise. The "flag" part is in 0xFF00 and *IS* bitwise. Confused yet? Good. So, when we want to check the "mode" of the conference, we need to check only within 0xFF. There were several places where this was not happening - but due to luck, it worked (...sort of). That's what this patch fixes. ........ ................ git-svn-id: http://svn.digium.com/svn/zaptel/trunk@2424 5390a7c7-147a-4af0-8ec9-7488f05a26cb
Diffstat (limited to 'ztmonitor.c')
0 files changed, 0 insertions, 0 deletions