The SignalingSessiontype exposes the following members.
Events
Name | Description | |
---|---|---|
InvitationAccepted |
Raised when the remote has accepted the
invite. Typically, this happens when a successful response is
received. This event is optional for an application. Applications
that want to send headers in the acknowledgement can register for
this event.
|
|
InvitationCompleted |
Raised when the invite process completes.
Typically, this happens when the inviter acknowledges a successful
response. This event is optional for an application. Applications
that want to access headers in the acknowledgement can register for
this event. Note that EndParticipate for the incoming side also
exposes the Ack message. This event is provided for
convenience.
|
|
MessageReceived |
Raised when a message is received.
|
|
ProvisionalResponseReceived |
Raised when the session received any
provisional response (101-199).
|
|
Redirecting |
Raised when a redirect request is
received.
|
|
ReferReceived |
Raised when a new Refer is received.
|
|
ReInviteReceived |
Raised when the remote sends a re-invite. This
event is optional for an application. Applications that want to
access headers in the re-invite can register for this event.
|
|
RenegotiationToRefreshNeeded |
Raised when the session is enabled for a
session timer, the local endpoint is the refresher, and the remote
does not support the UPDATE method. The application is responsible
for calling BeginRenegotiateDescription to keep the session
alive.
|
|
RequestOrResponseReceived |
Raised when a request or response is
received.
|
|
StateChanged |
Raised when the state of the session
changes.
|
|
TerminatedByRemote |
Raised when the remote side terminates the
session by sending a Bye or Cancel message. This event is optional
for an application. This event is useful only if the application is
interested in accessing the headers in the Bye or Cancel message
for custom scenarios.
|