Empty default constructor.

Constructs an empty RPhone object, and is present only to support virtual function table export.

Gets the number of lines associated with the phone.

Gets the phone's capabilities.

Gets a snapshot of the current phone information.

This function is expected to complete quickly. Consequently, an asynchronous variant has not been provided.

Returns a RPhone::TLineInfo containing information about a line. Select the line by passing RPhone::GetLineInfo() a number from zero to (number of lines-1). RPhone::EnumerateLines() returns the number of lines. A line's information is enough to differentiate it from the other lines associated with the phone.

Included in the line information is the line's name, RPhone::TLineInfo::iName . Pass this to RLine::Open() to open the line and hence to control the line's calls.

Typically, line zero is the phone's voice line. However, you should not presume this. Instead, RPhone::TLineInfo::iLineCapsFlags contains a flag that describes the type of line.

Gets information about the status of the phone.

Initialises, or re-initialises, a phone - synchronous. If the function is called during the automatic initialisation, the function completes when the phone is initialised. If the function is called after the automatic initialisation has finished, the phone is re-initialised.

Initialisation may take significant time to complete.

The phone hardware is usually automatically initialised before the first command is sent.

Functions which retrieve information about the modem should be used once this function has completed - such information may be incorrect before initialisation is complete.

Provides notification of changes in phone capabilities.

Provides notification when the local modem is detected, or when a previously connected modem can no longer be contacted.

Clearly, this function has no use if the modem (DCE) is permanently attached to the computing device (DTE).

This method allows the client to instruct the ETel server and the TSY to preallocate extra memory for any potential emergency request handling from this client. It allows other, non-priority, clients who operate under emergency conditions, to have memory preallocated for them in the ETel server. The request gets passed down to the TSY, so that the TSY can also proceed with the necessary memory pre-allocation. The client specifies the type of emergency requests that it wishes to handle in the aEmergencyRequest parameter. aEmergencyRequest is a bit-mask where each bit-flag represents the emergency request type that the client wishes to handle. See definition of TEmergencyRequest for the emergency request types bit-flag positions.

The memory required is calculated by the server and the TSY according to the aEmergencyRequest parameter. If the pre-allocation of memory within this method fails, the method returns KErrNoMemory. If the same emergency client calls this method multiple times, the ETel server will return the KErrAlreadyExists error. KErrAlreadyExists will also be returned if another RPhone client created using the same RTelServer session also calls this method.

Note that the ETel allocates emergency heap per client or more precisely per client's RTelServer session. The client is expected to use only one emergency sub-session of the same type at a time. If the client has a requirement to use multiple, concurrent subsessions that handle the same emergency functionality, then it needs to open separate RTelServer sessions, otherwise ETel might run out of the preallocated emergency memory.

If the API is called after the call to RTelServer::SetPriorityClient from the same session then the function returns KErrAlreadyExists.

Phone capability flags.

Phone mode status flags.

Modem connection status flags.