Location:
sipconnectionobserver.h
class MSIPConnectionObserver;
An interface to be implemented by users of CSIPConnection
. Interface allows to be able to receive requests, responses, connection state notifications and error notifications from
sip stack.
Note: The client must not delete related CSIPConnection
object during the execution of the interface function.
n/a
Defined in MSIPConnectionObserver
:
ConnectionStateChanged()
, ErrorOccured()
, ErrorOccured()
, ErrorOccured()
, ErrorOccured()
, ErrorOccured()
, ErrorOccured()
, IncomingRequest()
, IncomingRequest()
, IncomingResponse()
, IncomingResponse()
, IncomingResponse()
, IncomingResponse()
, InviteCanceled()
, InviteCompleted()
virtual void IncomingRequest(CSIPServerTransaction *aTransaction)=0;
aTransaction != 0
A SIP request outside a dialog has been received from the network.
|
virtual void IncomingRequest(CSIPServerTransaction *aTransaction, CSIPDialog &aDialog)=0;
aTransaction != 0
A SIP request within a dialog has been received from the network. The client must resolve the actual dialog association to which this request belongs.
|
virtual void IncomingResponse(CSIPClientTransaction &aTransaction)=0;
A SIP response received from the network.
|
virtual void IncomingResponse(CSIPClientTransaction &aTransaction, CSIPDialogAssocBase &aDialogAssoc)=0;
A SIP response received from the network that is within a dialog association or creates a dialog association.
|
virtual void IncomingResponse(CSIPClientTransaction &aTransaction, CSIPInviteDialogAssoc *aDialogAssoc)=0;
Multiple SIP responses have been received to the single INVITE due to the forking proxy. Note that each response creates a separate INVITE dialog association. Multiple responses can arrive until SIP stack completes UAC core INVITE transaction. If clients deletes INVITE transaction after first SIP response other possible responses will be consumed by the implementation.
|
virtual void IncomingResponse(CSIPClientTransaction &aTransaction, CSIPRegistrationBinding &aRegistration)=0;
A SIP response related a registration binding or an error response that is related to registration binding has been received from the network.
|
virtual void ErrorOccured(TInt aError, CSIPTransactionBase &aTransaction)=0;
An asynchronous error has occurred in the stack related to the request indicated by the given transaction.
|
virtual void ErrorOccured(TInt aError, CSIPClientTransaction &aTransaction, CSIPRegistrationBinding &aRegistration)=0;
An asynchronous error has occurred in the stack related to the request indicated by the given transaction.
|
virtual void ErrorOccured(TInt aError, CSIPTransactionBase &aTransaction, CSIPDialogAssocBase &aDialogAssoc)=0;
An asynchronous error has occured related to a request within an existing dialog.
|
virtual void ErrorOccured(TInt aError, CSIPRefresh &aSIPRefresh)=0;
An asynchronous error has occured related to a refresh
|
virtual void ErrorOccured(TInt aError, CSIPRegistrationBinding &aRegistration)=0;
An asynchronous error has occured related to a periodical refresh that relates to a registration.
|
virtual void ErrorOccured(TInt aError, CSIPDialogAssocBase &aDialogAssoc)=0;
An asynchronous error has occured related to a periodical refresh that belongs to SIP dialog association.
|
virtual void InviteCompleted(CSIPClientTransaction &aTransaction)=0;
SIP stack has completed UAC core INVITE transaction 64*T1 seconds after the reception of the first 2xx response. No more 2xx responses can be received to the issued single INVITE.
If the INVITE transaction does not create a dialog, or the INVITE transaction encounters an error, this event will not be sent.
|
virtual void InviteCanceled(CSIPServerTransaction &aTransaction)=0;
Invite was canceled with the CANCEL
|
virtual void ConnectionStateChanged(CSIPConnection::TState aState)=0;
Connection state has changed. If connection state has changed to EInactive or EUnavailable, SIP stack has removed all stand-alone SIP refreshes, registrations and dialog associations that client requested to refresh. Client may re-issue refresh requests (stand-alone, registration or dialog association related) when connection becomes EActive again. SIP stack also terminates all pending SIP client transactions and no errors are reported back to the client about the terminated transactions nor about removed refreshes in order to avoid event flood.
|