Likewise, if a document is shared during
the Webinar, yet another session is established. Each session then would carry its own
SDP describing that portion of the session.
This means that for a complex session such as a conference call or Webinar, one
could not see every aspect of the session by capturing just one SDP. It would require
capturing all of the INVITES for each portion of the session and correlating these all
together.
The SDP for each of the sessions would then be correlated to provide a complete view
of the overall session. This becomes a complex task in itself for troubleshooting, since
technicians will need to be able to determine what session they need to troubleshoot.
Simply tracing by the end-user identity will produce many sessions in progress, each
session being used for different purposes.
The SDP could be used to determine what each session is for, and the type of each
of the sessions. This should be a capability provided in the OSS/BSS. From there the
technician could troubleshoot each individual session to determine if there was an error
with a part of a session or with the overall call.
Remember that the SDP is not required for all sessions. It is required only for sessions
where two endpoints are going to enter into a dialog with one another. A simple
example of this is a voice call.
If there is no SDP in the message body of a SIP request/response, other content could
be present.
Pages:
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194