Premature LINECALLSTATE_CONNECTED when phone not in cradle

[V�is�nen@discussions.microsoft.com Jari Väisänen]

i have developed a phone software, that allows user to make and receive
calls. I use initialize tapi to use event handler and lineGetMessage() to
loop throught the events. Everything works fine while smart phone is in
cradle. Problem rises when I detach the phone and try to make a call.

In cradle, the messages go as follows: Dialing, Processing then wait for
connected, and some callinfo message inbetween. When off cradle, messages go
all the way to connected, as if the second part had answered the call, and
becuase this happens, there is no change in callstate when the call is
actually answered. Disconnected message is returned normally in both cases.

using Tapi 2.0, windows mobile 5.0 and phone is Pidion 5000.

[fdecker]

You are using a PDA/phone and if I understand you, it has a charging
cradle. This cradle is probably connected to the PC with a USB
cable? Does your application run on the smart phone or does it run on
the computer? If you have your phone attached to a cradle, the cradle
is attached to the computer and you are controlling the phone from an
application on the computer, this may be the intended behavior. When
your phone is in the cradle, it is "on hook". When you take it out of
the cradle, it is "off hook". You can check the phone device
properties instead of the line device properties to see what you see.
You could use the free trial version of our TeleScope utility to
activate your device in our etLine window and etPhone window and watch
everything that happens in the log windows.

Some devices do not go connected, they show the handset hookswitch
change and then perhaps the dialtone message. This could be a
limitation of the TSP for the device. Does it have its own TAPI TSP
you installed or does it use UnimodemV?

You can get TeleScope from www.exceletel.com/download. Look for
TeleScope37.

Fred
www.exceletel.com
"Analog, Digital and VoIP Telephony tools"

[Jari Väisänen]

The device is a PDA, with charging cradle connected to computer with USB, but
the application runs on the device. I have the full compiled application on
the device.

I can tun the app from a exe on the PDA. When on cradle, there are no
callstate_connected unless called party answers the call, but when taken off
cradle, after a moment there is a sequence of appnewcall, offering, process,
connected and disconnected. I tracked it to be ASYNCMAC that does this. Thou
it's weird that even after the ASYNCMAC has done it's thing, TAPI still
returns callstate_connected blindly (as mentioned in several posts I've
found).

Now trying if I can use the phone device to check for on/off hook messages.

"fdecker" wrote:

> .
>