Removed confusing warning message "Got Busy in Connected State"

If an incoming mISDN call is answered with the Answer application and a
subsequent Dial gets a busy endpoint then it is valid for that already
connected channel to get the busy indication.  Asterisk will play the busy
tones until the dialplan plays something else or hangs up the call.

(closes issue #11974)
Reported by: fvdb

git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.4@204834 65c4cc65-6c06-0410-ace0-fbb531ad65f3

diff --git a/channels/chan_misdn.c b/channels/chan_misdn.c
index 34070fd35aaa303c4b500c8f8bf8732ebaefcf21..24d043a46de5912f830d420272c8db8a3c55d85b 100644 (file)
--- a/channels/chan_misdn.c
+++ b/channels/chan_misdn.c
@@ -2431,8 +2431,6 @@ static int misdn_indication(struct ast_channel *ast, int cond, const void *data,
                if (p->state != MISDN_CONNECTED) {
                        start_bc_tones(p);
                        misdn_lib_send_event( p->bc, EVENT_DISCONNECT);
-               } else {
-                       chan_misdn_log(-1, p->bc->port, " --> !! Got Busy in Connected State !?! ast:%s\n", ast->name);
                }
                return -1;
        case AST_CONTROL_RING: