NewLC - Telephony - Comments

Re: CTelephony Methods under one class

Yotamix — Mon, 18 Aug 2008 12:31:59 +0200

Just making sure i follow your string of thought . thanx.

Re: CTelephony Methods under one class

lvsti — Mon, 18 Aug 2008 12:30:30 +0200

Look, I cannot write the code instead of you. You know what processing you want and in what manner. Think a bit, try, and you'll certainly find a solution.

Re: CTelephony Methods under one class

Yotamix — Mon, 18 Aug 2008 12:26:37 +0200

so i should stop the AO which handles the Listening and Hanging up , and only then create AO for DialNewCall . am i correct ?

Re: CTelephony Methods under one class

lvsti — Mon, 18 Aug 2008 10:56:27 +0200

At least you can put line status monitoring in a separate AO and pass it an observer which it can then notify about status changes. You can also consider creating an AO for dialling as well (again, with an observer) if there is a chance that some other operation will overlap dialling. The state machine can be in the original/main AO which acts as the observer for the status monitor, and this should be the one which dials, sets the DTMF, etc. depending on the state.

Re: CTelephony Methods under one class

Yotamix — Mon, 18 Aug 2008 10:29:54 +0200

so devide and conquer is the best solution ?
AO for calls , AO for DTMF and the state machine will sit outside ?

Re: CTelephony Methods under one class

lvsti — Mon, 18 Aug 2008 10:05:55 +0200

Ok, it seems that either of us misunderstood the other

You MUSTN'T call NotifyChange() there for the *same* iStatus because that would result in nice AO panics. In this case you would need separate active objects for dialling and monitoring the line status. What I previously meant was that you could use the same active object for asynchronous calls which follow each other without overlapping in time.

Re: CTelephony Methods under one class

Yotamix — Mon, 18 Aug 2008 09:57:57 +0200

I Will Rephrase my question :

When i Switch to the second stage , after hanging up , Calling DialNewCall() will execute RunL() of the AO if a Call is successful . will it also change iLineStatus automatically or should i call RequestNotifucation as well before the SetActive() ?

Code Snippet is here :

switch (iState)
    {
     case EIdle:
     {
    if( iLineStatus.iStatus == CTelephony::EStatusDialling )  
             {
                   .
                     .
                     .  
         iNotifier->NotifyOutgoingCall(iLineStatus.iStatus, CallerNumber);
         this->SetStateCallServer();
         /* Request the next notification */
         iTelephony->NotifyChange( iStatus,CTelephony::EVoiceLineStatusChange,iLineStatusPckg );
         SetActive();
         }
      break;
     }
     case ECallingServer:
      {
         if( iLineStatus.iStatus == CTelephony::EStatusIdle )  
         {
          CTelephony::TTelNumber telNumber(DomesticCallBack);
         CTelephony::TCallParamsV1 callParams;
        callParams.iIdRestrict = CTelephony::ESendMyId;
       CTelephony::TCallParamsV1Pckg callParamsPckg(callParams);
                                          
       this->SetStateInSession();            
       iTelephony->DialNewCall(iStatus, callParamsPckg, telNumber, iCallId);
       //Should i Request Notify Here ?
      SetActive();
    }
     break;
  } 

Re: CTelephony Methods under one class

Yotamix — Mon, 18 Aug 2008 08:57:56 +0200

Do I need to Trigger that change in the State Machine , or basically the nest call of RequestNotify will do the trick ?
I will use the ELineStatusChange

Re: CTelephony Methods under one class

lvsti — Mon, 18 Aug 2008 08:44:01 +0200

Afaik hangup is an asynchronous call so you'd need a state for it. When it completes (call is hung up) execution enters RunL again. If you got to RunL from the framework (that is, you didn't do RunL(); manually), you can start any asynchronous request from there without calling Cancel() because the active object is not active at that time.

void CFooBar::RunL()
{
    switch (iState)
    {
    case EFooHangingUp:
        {
        // call is hung up, start new dialling
        iState = EFooDialling;
        iTelephony->DialNewCall( ... );
        SetActive();
        break;
        }
    ...
    }
}

Re: CTelephony Methods under one class

Yotamix — Mon, 18 Aug 2008 08:34:13 +0200

So Suppose i have a RequestNotify() for EDialling . I Capture it , RunL() starts and i hangup the call . from here i need to make a new call - so should first call Cancel() and than start a DialNewCall() + Switch the State MAchine to the next phase?

Re: CTelephony Methods under one class

lvsti — Mon, 18 Aug 2008 08:32:40 +0200

For CTelephony it is easier if you just store the current TCancellationRequest value in a member variable so in DoCancel() you won't need any checks but can call CancelAsync() directly with that value. Naturally, if you make asynchronous calls to classes other than CTelephony, in that case you would need the same switch as in RunL.

Re: CTelephony Methods under one class

Yotamix — Mon, 18 Aug 2008 08:24:44 +0200

oh , one last question - regarding the state machine : should i in DoCancel() check each state for the proper AsyncCancel of is there a general Cancellation?

Re: CTelephony Methods under one class

Yotamix — Mon, 18 Aug 2008 08:21:52 +0200

Thank you very much , i shall do that excatly . i have a great solution for that

Re: CTelephony Methods under one class

lvsti — Mon, 18 Aug 2008 08:20:11 +0200

Of course. You just need to maintain a state machine in the active object. When you issue an asynchronous request, you set a state variable accordingly, then when you enter RunL, you can decide what type of request has been completed by switching between the possible values of that variable.

Re: Overriding Incoming Call Dialog

kkrish — Mon, 11 Aug 2008 07:06:31 +0200

Hi Willi,

is it possible to display any kind of window/app behind the incoming call window??