From: Sean Bright <sean@malleable.com>
Date: Tue, 7 Oct 2008 12:01:36 +0000 (+0000)
Subject: Make sure to compare the correct number of characters when special-casing
X-Git-Tag: 1.6.2.0-beta1~1185
X-Git-Url: http://git.asterisk.org/gitweb/?p=asterisk%2Fasterisk.git;a=commitdiff_plain;h=61664ec58bbd7094a629ce490a5dac63ec687449;hp=c2d9b9c009b35f830a5a7e9aa671dd7e8a44b226

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: https://origsvn.digium.com/svn/asterisk/trunk@147050 65c4cc65-6c06-0410-ace0-fbb531ad65f3
---

diff --git a/apps/app_dial.c b/apps/app_dial.c
index 6a1022a..df2dd5f 100644
--- a/apps/app_dial.c
+++ b/apps/app_dial.c
@@ -1926,7 +1926,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