From 61664ec58bbd7094a629ce490a5dac63ec687449 Mon Sep 17 00:00:00 2001 From: Sean Bright Date: Tue, 7 Oct 2008 12:01:36 +0000 Subject: [PATCH 1/1] 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 --- apps/app_dial.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 -- 1.7.9.5