diff options
author | seanbright <seanbright@f38db490-d61c-443f-a65b-d21fe96a405b> | 2008-10-07 12:03:07 +0000 |
---|---|---|
committer | seanbright <seanbright@f38db490-d61c-443f-a65b-d21fe96a405b> | 2008-10-07 12:03:07 +0000 |
commit | 4e57fdeb0004d975e7901f4d3dc7ae2bbc874623 (patch) | |
tree | 45f352f82291df927e37cc7e14588dc6b1abf11b /apps | |
parent | 075f2a4a01f3e9287456e209a301e6a9aa90f702 (diff) |
Merged revisions 147050 via svnmerge from
https://origsvn.digium.com/svn/asterisk/trunk
........
r147050 | seanbright | 2008-10-07 08:01:36 -0400 (Tue, 07 Oct 2008) | 8 lines
Make sure to compare the correct number of characters when special-casing
our DAHDI operator mode stuff. Technically, it would work fine, as 'DAH'
is currently unique amongst our channel technologies, but as Jared points
out:
<@jsmith> Sure... as long as the technology starts whith DAH.... but
it could be DAHDOO!
........
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.6.0@147051 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'apps')
-rw-r--r-- | apps/app_dial.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/apps/app_dial.c b/apps/app_dial.c index d3ba0522c..eec675427 100644 --- a/apps/app_dial.c +++ b/apps/app_dial.c @@ -1882,7 +1882,7 @@ static int dial_exec_full(struct ast_channel *chan, void *data, struct ast_flags res = -1; goto done; } - if (opermode && !strncmp(chan->tech->type, "DAHDI", 3) && !strncmp(peer->name, "DAHDI", 3)) { + if (opermode && !strncmp(chan->tech->type, "DAHDI", 5) && !strncmp(peer->name, "DAHDI", 5)) { /* what's this special handling for dahdi <-> dahdi ? * A: dahdi to dahdi calls are natively bridged at the kernel driver * level, so we need to ensure that this mode gets propagated |