RMobileCall::HangUp does not disconnect the Video Call when it is in progress(connected state) (Known Issue)

From Nokia Developer Wiki
Jump to: navigation, search

RMobileCall::HangUp() API does not work when the call is in progress, though it works when the call is in ringing state but not answered.

Article Metadata
Tested with
Devices(s): N8, E7
Platform(s): Symbian^3
Platform Security
Signing Required: DevCert
Capabilities: SwEvent
Created: debjit.roy (14 Mar 2012)
Last edited: hamishwillee (15 Mar 2012)


Opening a new call:

RMobileCall     iCall;
iCall.OpenNewCall( iLine ); // RMobileLine iLine
iCall.Dial( iStatus, iDataPckg, iNumber ); //RMobileCall::TMobileHscsdCallParamsV1Pckg iDataPckg;

The code snippet used to hang up a video call:

void CVtEngTestCall::EndVideoCallL()
if ( iCall.SubSessionHandle() == 0 )
User::Leave( KErrBadHandle );
if ( iState == EDialling )
iCall.HangUp( iStatus );
iState = EHangingUp;

Closing the call:


This snippet should actually hang up the call, and it does in the following scenario:

  1. Make video call through application.
  2. Call is in ringing state.
  3. Hang the call from the application using RMobileCall::HangUp() API.

But once the call is connected, hang up from the application using RMobileCall::HangUp() API does not work.

  1. Make video call through application
  2. Answer the call (now call is Connected)
  3. Hang the call from the application using RMobileCall::HangUp() API.


One workaround could be simulating the red key to hang up the call. Snippet is as follows:

RWsSession ws; 
TRawEvent ev1;
ev1.Set(TRawEvent::EKeyDown, EStdKeyNo); // Simulating red key
ws.SimulateRawEvent(ev1); // CAPABILITY Req. SwEvent

Defect tracking

This defect can be tracked on Nokia Developer Defect tracking system: 863

This page was last modified on 15 March 2012, at 05:47.
21 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.


Thank you!

We appreciate your feedback.