The only one command I know for "Auto Answer", that will reliably work on all phones, is setting register "S0" (by ATS0=x). BTW: My document has some T610 specific commands on page 318. This one I have is from August 2003. What date is yours?Originally Posted by wizardPC
But this one has nothing to do with the auto answer from the BT.
Cause: When a call is pending, the phone looks, if configured that way, for a appropriate headset device and if there is one, it does all the identification stuff. If this passes, it waits for the headset to connect. This connect usually is done by the user by pressing the button on the headset. One the user presses this button, the phone is accepting this as a "hookup" and the caller will be connected.
The major difference to the Widcomm Software (for the Headset Profile) is, this "Button press" is raised automatically, as soon as the software recognizes an connection request and the initialization / authentication stuff passed. There is no way to have the Widcomm Stack waitng for any user interaction (except the SDK... I guess ).
There is another thing. As soon as one routes a call to a headset, there is no such function like "take it back". This sure depends on what phone you use (but I don't know any phone that's capable doing this - correct me if I'm wrong). At least, there is nothing that can be controlled remotely via AT-Commands.
BTW: Making settings to the mobile that are static (means: they can be done once i a session and the phone will keep it at least during the session) can be accomplished via the <AdditionalInit> and <AdditionalDeinit> tags within the configuration file.
So you can play around and try many things without having the need waiting for me to change the application.