Sent wrong message to clear a call we started if the other end has not responed yet.

In the state MISDN_CALLING (i.e. SETUP was sent but no answer has arrived yet),
it is not allowed to clear the call with RELEASE_COMPLETE.  It must be
cleared with DISCONNECT.  A RELEASE_COMPLETE is only allowed as an answer
to a SETUP.  (See Q.931 ch. 5.3.2, 5.3.2.a, 5.3.2.b)

Patches:
    chan-misdn-ccstate7.patch uploaded by customer.

JIRA ABE-1862

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

diff --git a/channels/chan_misdn.c b/channels/chan_misdn.c
index 9bf11b4ca3f87ead89e06875276774d8c2a8b662..0ed15a5d75d1b329e00feff9841477577c28536b 100644 (file)
--- a/channels/chan_misdn.c
+++ b/channels/chan_misdn.c
@@ -2610,11 +2610,10 @@ static int misdn_hangup(struct ast_channel *ast)
 
        switch (p->state) {
        case MISDN_INCOMING_SETUP:
-       case MISDN_CALLING:
                /* This is the only place in misdn_hangup, where we 
                 * can call release_chan, else it might create lot's of trouble
                 * */
-               ast_log(LOG_NOTICE, "release channel, in CALLING/INCOMING_SETUP state.. no other events happened\n");
+               ast_log(LOG_NOTICE, "release channel, in INCOMING_SETUP state.. no other events happened\n");
                release_chan(bc);
 
                p->state = MISDN_CLEANING;
@@ -2637,6 +2636,7 @@ static int misdn_hangup(struct ast_channel *ast)
                        misdn_lib_send_event( bc, EVENT_DISCONNECT);
                break;
 
+       case MISDN_CALLING:
        case MISDN_ALERTING:
        case MISDN_PROGRESS:
        case MISDN_PROCEEDING: