diff options
author | jpeeler <jpeeler@f38db490-d61c-443f-a65b-d21fe96a405b> | 2008-06-17 18:08:09 +0000 |
---|---|---|
committer | jpeeler <jpeeler@f38db490-d61c-443f-a65b-d21fe96a405b> | 2008-06-17 18:08:09 +0000 |
commit | 2f30a3a6e7ae5721ed086155a63f22c33c495382 (patch) | |
tree | f7eb76f243ca169acc08d6d90b25b1c191e421e3 /apps/app_dial.c | |
parent | 2ee27fd87f55632e832d749c5fe6739a68aeb913 (diff) |
Goodbye Zaptel, hello DAHDI. Removes Zaptel driver support with DAHDI. Configuration file and dialplan backwards compatability has been put in place where appropiate. Release announcement to follow.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.6.0@123332 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'apps/app_dial.c')
-rw-r--r-- | apps/app_dial.c | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/apps/app_dial.c b/apps/app_dial.c index 5dd160217..d7b21f6cb 100644 --- a/apps/app_dial.c +++ b/apps/app_dial.c @@ -168,8 +168,8 @@ static char *descrip = " o - Specify that the CallerID that was present on the *calling* channel\n" " be set as the CallerID on the *called* channel. This was the\n" " behavior of Asterisk 1.0 and earlier.\n" -" O([x]) - \"Operator Services\" mode (Zaptel channel to Zaptel channel\n" -" only, if specified on non-Zaptel interface, it will be ignored).\n" +" O([x]) - \"Operator Services\" mode (DAHDI channel to DAHDI channel\n" +" only, if specified on non-DAHDI interface, it will be ignored).\n" " When the destination answers (presumably an operator services\n" " station), the originator no longer has control of their line.\n" " They may hang up, but the switch will not release their line\n" @@ -1873,9 +1873,9 @@ static int dial_exec_full(struct ast_channel *chan, void *data, struct ast_flags res = -1; goto done; } - if (opermode && !strncmp(chan->name, "Zap", 3) && !strncmp(peer->name, "Zap", 3)) { - /* what's this special handling for Zap <-> Zap ? - * A: Zap to Zap calls are natively bridged at the kernel driver + if (opermode && !strncmp(chan->tech->type, "DAHDI", 3) && !strncmp(peer->name, "DAHDI", 3)) { + /* 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 * all the way down. */ struct oprmode oprmode; |