summaryrefslogtreecommitdiffstats
path: root/doc/voicecall-api.txt
AgeCommit message (Collapse)AuthorFilesLines
2010-08-18doc: Proposed Set Up Call apiAndrzej Zaborowski1-0/+11
The normal sequence for call setup is: * Modem asks user for confirmation using icon1 / alphaId1 * User confirms * Modem starts dialling, screen displays icon2 / alphaId2 * Call is connected, modem replies to the proactive command, screen keeps displaying icon2 / alphaId2 until the phone call is over
2010-08-11doc: update voice call API documentationMarcel Holtmann1-0/+8
Reflect required changes to simplify the voice call API usage.
2010-07-21doc: cleanup voicecall api formattingDenis Kenzior1-4/+5
2009-11-12Remove Voicecall.Busy methodDenis Kenzior1-13/+14
According to 22.030, UDUB or CHLD=0 can only be invoked on waiting calls. Most AT command based modems do not support using CHLD=0 on an incoming call. So we remove the Busy method and invoke set_udub on a call that is in the waiting state.
2009-10-16API: Documentation fixesMarko Saukko1-1/+1
2009-08-12Add API documentation for voice call interfacesMarcel Holtmann1-0/+106