Phone line events are sent to an application to indicate that the state of a phone line has changed. The design of your application will focus on what capabilities you require from the telephony engine. Depending on what capabilities you need to employ will dictate what phone line events your application will need to respond to.
Many of the telephony events are designed to allow an application to track various SIP session initiation states. If your application is not concerned about specific SIP session states, most of the phone line event notifications can be ignored. Ignoring SIP specific event notifications is typical of most applications.
There is a minimal set of phone line events you will have to handle for a basic telephony experience. The primary events that are important deal with detecting call start and call termination. Other operations such as call hold, transfer and conferencing are optional.
The telephony engine can send any of the following phone line events to application software:
SipCallStartFailed
SipCallNetworkError
SipInviteSendFailed
SipInviteAckSendFailed
SipLineInitialized
SipReceivedByeAck
SipReceivedByeErrorAck
SipReceivedInviteAck
SipReceivedProvisionalResponse
SipReceived181CallBeingForwarded
SipReceivedUnsupportedProvisionalResponse
SipRouterPortTranslationError
SipRtpSocketOpenError
SipRtpFatalStartError
SipOutgoingCallBasicAuthenticationRequired
SipOutgoingCallDigestAuthenticationRequired
SipOutgoingCallUnsupportedAuthentication
SipComputeAuthenticationCredentialsFailed
SipMemoryError
SipThreadCreationError
For Further information regarding how events are presented to application software, see the following:
Phone Line Events - Initiating Calls
Phone Line Events - Receiving Calls
Phone Line Events - Local Call Termination
Phone Line Events - Far End Call Termination