Cisco Cisco Unified MeetingPlace Web Conferencing Manuale Di Manutenzione
238
Chapter 11 Troubleshooting
A: MeetingPlace Web keeps session information about each
connected user. This information is kept for a minimum of one
hour from the time a user last logged on to MeetingPlace Web, up
to a maximum of 24 hours. If a user logs on to MeetingPlace Web
from a different location than the one they used originally, then
the first browser’s connection is lost. If the end user goes back to
the first browser, they will receive a notification that their session
is stale. This can also happen if MeetingPlace Web needs to free
some room for new users and one of the current end users has not
used MeetingPlace Web for over an hour.
connected user. This information is kept for a minimum of one
hour from the time a user last logged on to MeetingPlace Web, up
to a maximum of 24 hours. If a user logs on to MeetingPlace Web
from a different location than the one they used originally, then
the first browser’s connection is lost. If the end user goes back to
the first browser, they will receive a notification that their session
is stale. This can also happen if MeetingPlace Web needs to free
some room for new users and one of the current end users has not
used MeetingPlace Web for over an hour.
Q: When trying to schedule a meeting, why do I receive the error
“the meeting being scheduled is different than the one in
MeetingPlace Web?”
“the meeting being scheduled is different than the one in
MeetingPlace Web?”
A: Most likely the Schedule Now button was pressed twice
before MeetingPlace Web had a chance to respond. This resulted
in MeetingPlace Web scheduling a meeting on the first press of
the button, but before it had a chance to respond it received
another scheduling request. Check to see if the meeting was
scheduled (using the browse meeting feature) before scheduling
the meeting again.
before MeetingPlace Web had a chance to respond. This resulted
in MeetingPlace Web scheduling a meeting on the first press of
the button, but before it had a chance to respond it received
another scheduling request. Check to see if the meeting was
scheduled (using the browse meeting feature) before scheduling
the meeting again.
Q: I’m in a web conference while trying to schedule a new
meeting via the Cisco IP phone interface. Why do I get a “Session
is Stale” message?
meeting via the Cisco IP phone interface. Why do I get a “Session
is Stale” message?
A: When you log on to MeetingPlace for Cisco IP Phones while
you are already logged onto a web conference, your web session
may become stale. This will happen if MeetingPlace for Cisco IP
Phones is utilizing the same MeetingPlace Web (version 4.2.5)
that is also being used for web conferencing. Your current voice
and web conference will be uninterrupted, but you will have to
log in again to the interface you want to use.
you are already logged onto a web conference, your web session
may become stale. This will happen if MeetingPlace for Cisco IP
Phones is utilizing the same MeetingPlace Web (version 4.2.5)
that is also being used for web conferencing. Your current voice
and web conference will be uninterrupted, but you will have to
log in again to the interface you want to use.
A workaround is to install the MeetingPlace Web intended for
web conferencing on a separate Windows server.
web conferencing on a separate Windows server.
Q: What does the message “No more sessions available” mean?
Cisco MeetingPlace Web 3.0 System Manager's Guide OL-6033-01