Hallo everybody, I have problem implementing this sequence. Working with smartphone WM6. Using TAPI 2.0 (InitializeEx ->ok, version is required one) lineSetupTransfer -> Ok call becomes LINECALLSTATE_OHOLDPENDTRANSFER -> First problem wm6 do not recognize this call as call OnHold (so I can't unhold using device buttons) wait for states -> Ok lineDial() ->Ok wait for states-> Ok lineCompleteTransfer(MODE_TRANSFER) -> ok wait for states -> fail - calls are not ended and left active, dropping them drops all calls , but system still "see" active call. By the way lineBlindTransfer works fine (worst thing I must be sure call was transfered) Does anybody has / had such problems. Any ideas welcome. Thank's and execuse me for my English. Romualdas
Romualdas, which TSP are you using, the cell TSP? I didn't know that it supports call transfer... Did you try to lineDeallocateCall on both calls instead of dropping them? Best regards, Matthias Moetje ------------------------------------- TAPI WIKI: http://www.tapi.info ------------------------------------- TERASENS GmbH Augustenstraße 24 80333 Munich, GERMANY ------------------------------------- e-mail: moetje at terasens dot com www: www.terasens.com ------------------------------------- wrote in message news:9017aaee-58a1-47ec-afab-c6a681894a08@79g2000hsk.googlegroups.com... > Hallo everybody, > > I have problem implementing this sequence. > Working with smartphone WM6. > Using TAPI 2.0 (InitializeEx ->ok, version is required one) > > lineSetupTransfer -> Ok > call becomes LINECALLSTATE_OHOLDPENDTRANSFER -> First problem wm6 do > not recognize this call as call OnHold (so I can't unhold using device > buttons) > wait for states -> Ok > lineDial() ->Ok > wait for states-> Ok > lineCompleteTransfer(MODE_TRANSFER) -> ok > wait for states -> fail - calls are not ended and left active, > dropping them drops all calls , but system still "see" active call. > > By the way lineBlindTransfer works fine (worst thing I must be sure > call was transfered) > Does anybody has / had such problems. Any ideas welcome. > > Thank's and execuse me for my English. > Romualdas
Hallo Matthias, I am not sure about TSP, I'am developing for GSM phones. For tests I use HTC smartphone device (S620) running WM6 and pocketPc with GSM (P3300) running WM5. Deallocating calls seems do nothing at all, they left valid. If this functionality (I mean call transfer) depends on TSPI would it be any reason to use TSPI functions instead of TAPI ? Be not so angry, I am newbie in TAPI, so maybe asking some childish questions. Regards, Romualdas
schrieb im Newsbeitrag news:0cb2e2ac-67ab-4f35-9e4e-53e01b5c07ae@m45g2000hsb.googlegroups.com... > If this functionality (I mean call transfer) depends on TSPI would it > be any reason to use TSPI functions instead of TAPI ? Romualdas, no, TSPI_functions are solely called by the OS. Apps use TAPI functions. -- Best Regards Andreas Marschall Microsoft MVP for TAPI / Windows SDK / Visual C++ TAPI / TSP Developer and Tester My TAPI and TSPI FAQ: http://www.I-B-A-M.de/Andreas_Marschall's_TAPI_and_TSPI_FAQ.htm My Toto® Tools (a collection of free, mostly TAPI related tools): http://www.i-b-a-m.de/Andreas_Marschall's_Toto_Tools.htm TAPI development around the world (Frappr! map): http://www.frappr.com/TAPIaroundTheWorld * Please post all messages and replies to the newsgroup so all may * benefit from the discussion. Private mail is usually not replied to. * This posting is provided "AS IS" with no warranties, and confers no rights.
