Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2010-08-18 | doc: Proposed Set Up Call api | Andrzej Zaborowski | 1 | -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-11 | doc: update voice call API documentation | Marcel Holtmann | 1 | -0/+8 | |
Reflect required changes to simplify the voice call API usage. | |||||
2010-07-21 | doc: cleanup voicecall api formatting | Denis Kenzior | 1 | -4/+5 | |
2009-11-12 | Remove Voicecall.Busy method | Denis Kenzior | 1 | -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-16 | API: Documentation fixes | Marko Saukko | 1 | -1/+1 | |
2009-08-12 | Add API documentation for voice call interfaces | Marcel Holtmann | 1 | -0/+106 | |