ECAM provides wrong call status after the held call becomes active

11 thoughts on “ECAM provides wrong call status after the held call becomes active

  1. Hi, there!

    Consider situation in which I get this bug.

    When receiver place incoming call on hold caller receives #ECAM urc with state hold (#ECAM: 0,4,1,,,). And there is nothing wrong. But when receiver releases held incoming call and it becomes active again, caller should receive  #ECAM with call status active (#ECAM: 0,3,1,,,), but caller receives  #ECAM with call status hold again.

    It seems to be a bug…

      1.  

        atd8093XXXXXXX;
        #ECAM: 0,1,1,,,"8093XXXXXXX",129
        #ECAM: 0,2,1,,,
        OK
         
         
        #ECAM: 0,3,1,,,
         
         
        #ECAM: 0,4,1,,,
         
        at+clcc
        +CLCC: 1,0,1,0,0,"8093XXXXXXX",129,""
        OK
         
         
        #ECAM: 0,4,1,,,
        at+clcc
        +CLCC: 1,0,0,0,0,"8093XXXXXXX",129,""
        OK

         

          1. But AT+CLCC shows that in fact state of the current call is active (and that is really true) and #ECAM provides wrong information.

            If it was related to operator, AT+CLCC would provide us the same information about state of the call as #ECAM.

            I don’t get why you need such a log. It is easy to reproduce this bug. Or when you are reproducing it you don’t get such a problem?