API Reference | developer.brewmp.com API Reference | developer.brewmp.com

Developer

API Reference

Telephony



Telephony functionality of a mobile device, SMS messaging, and TAPI.

TAPI

Brew MP includes everything needed to write a standards-compliant telephony app that can control the device's operating mode (online, offline, low power mode), manage system preferences (network type, band, roaming), select the active radio stack (e.g. UMTS, CDMA) on multi-mode devices and select the active NAM. The TAPI implementation gets the number of available networks (CDMA, EVDO, UMTS, GSM, WLAN, etc.); the system mode, serving status and unique network id of all available networks; and detailed, network-specific information using network id. Call Manager provides all the access the phone needs for originating calls of different types (voice, CS & PS data, provisioning, emergency calls), answering/rejecting incoming calls, supporting multi-party calls, sending notification of call-related events (e.g., incoming, connected, ended, call waiting), sending in-call DTMF tones, forwarding/barring/holding/transferring calls, and accessing detailed call information (caller ID, call duration, call type).

SMS

Brew MP's SMS interfaces provide access to the mobile device's SMS stack for sending and receiving messages, and providing access to card-based SMS storage. In Standard SMS multiple apps can register for notification of incoming messages and receive messages so that different apps may handle them differently. Apps can configure Broadcast SMS to enable or disable support, or limit to services in the device service table (enable, priority threshold, alert type). They can also register for notifications of broadcast SMS messages with specific service IDs and receive messages. Directed SMS allows a server to send an SMS message directly to a Brew MP app by its class ID or a URL-lookup in the registry (e.g., to wake the app).