topic Webex and MeetingPlace 8.0 issue in Collaboration Applications

Webex and MeetingPlace 8.0 issue

Daniel Gomez — Sun, 17 Mar 2019 22:27:30 GMT

Hello,

There is a webex - meetingplace 8.0 deployment that is having audio issues when some users create a webex meeting.

1. User access his webex profile, creates a webex meeting and process completes as expected.

2. User tries to access audio bridge calling meetingplace extension (8202), meetingplace successfully replies: welcome to meetingplace, enter the meeting ID number followed by the # key.

3. User enters meeting ID and receives a message indicating meeting ID is not recognized. No one can connect to the audio meeting.

On the computer screen, Webex successfully shows the extension that has to be called to access the meeting. In fact, webex should also give user the option to be called to his extension or even to an external number but this is not happening. We do see an error message saying the following:

" You are experiencing a connection issue. Wait a few moments and try again". Picture is attached.

Does anybody know what could we try in order to get this issue resolved?

An important thing to mention is that this behaviour is happening for some users on the system. Configuration for users with and with no problems seem to be the same on either CUCM and MP.

Thanks.

Webex and MeetingPlace 8.0 issue

dpetrovi — Fri, 09 Aug 2013 15:04:09 GMT

Hi Daniel,

You have some sort of TSP connectivity issue between MP8.0 App server and the WebEx cloud. Without reviewing the configuration of your system and the logs, we cannot say what exactly is happening. You can try restarting Cisco WebEx Adapter and resetting TSP Connection on MP Application Server > Administration Center > System Configuration > Cisco WebEx Configuration > Cisco WebEx Site and Server.

Also, ensure the time on the MP Application Server is in sync with the current time. You can SSH to MP Application server, log in as 'mpxadmin', and run 'date' command to check the time. If time is not correct, you will need to stop the services and adjust the time on the server, and then restart the system. For that, and further troubleshooting, I would advise you to open a ticket with TAC.

-Dejan

Webex and MeetingPlace 8.0 issue

Daniel Gomez — Fri, 09 Aug 2013 15:22:40 GMT

Hello Dejan,

I'll try to check that, but, what I'm concerned about is that webex is working for some users and it is not for some others...

If it was a TSP connection issue, wouldn't it be happening for all of the users?

Webex and MeetingPlace 8.0 issue

jdedell12 — Fri, 09 Aug 2013 15:27:35 GMT

Have you checked the logs for errors? I have seen this when the TSP link drops then reconnects a couple of minutes laters. Some people can get in while others see this type of error.

Webex and MeetingPlace 8.0 issue

Daniel Gomez — Fri, 09 Aug 2013 15:36:44 GMT

I see the following messages in the logs:

DATETIME	SEVERITY	EX	FILE	LINE	SCODES	DESCRIPTION
08/09 09:54:52:00	WARN	2097198	mp_calls.cc	2559	(5165,0,0,0)	Call failed in ConfSched, error=5165
08/09 09:42:31:00	WARN	2097154	mp_calls.cc	4757	(5165,0,0,0)	Call failed, error = 5165
08/09 09:42:31:00	WARN	2097198	mp_calls.cc	2559	(5165,0,0,0)	Call failed in ConfSched, error=5165
08/09 09:42:30:00	WARN	2097154	mp_calls.cc	4757	(5165,0,0,0)	Call failed, error = 5165
08/09 09:42:30:00	WARN	2097198	mp_calls.cc	2559	(5165,0,0,0)	Call failed in ConfSched, error=5165
08/09 09:34:44:00	INFO	131322	csconfrec.cc	27933	(1490,4,0,0)	Meeting termination note
08/09 09:34:26:00	WARN	0	csconfrec.cc	27916	(5153,1490,0,0)	(5153, 1490, 0, 0)
08/09 09:34:17:00	WARN	0	csconfrec.cc	18241	(1,0,0,0)	(1, 0, 0, 0)
08/09 09:34:17:00	WARN	2097154	mp_calls.cc	4757	(5283,0,0,0)	Call failed, error = 5283
08/09 09:34:17:00	WARN	2097198	mp_calls.cc	2559	(5283,0,0,0)	Call failed in ConfSched, error=5283
08/09 09:31:42:00	WARN	2097154	mp_calls.cc	4757	(5165,0,0,0)	Call failed, error = 5165
08/09 09:31:42:00	WARN	2097198	mp_calls.cc	2559	(5165,0,0,0)	Call failed in ConfSched, error=5165
08/09 09:31:42:00	WARN	2097154	mp_calls.cc	4757	(5165,0,0,0)	Call failed, error = 5165
08/09 09:31:42:00	WARN	2097198	mp_calls.cc	2559	(5165,0,0,0)	Call failed in ConfSched, error=5165
08/09 09:28:40:00	WARN	851969	rvsip_call.cc	1065	(0,0,0,0)	Debug message 0 0 0 0

We had this today. TAC

richb1971 — Tue, 21 Apr 2015 13:58:14 GMT

We had this today. TAC advised the server had been up a long time! (177 days). Reboot server=all good.

Check via CLI (SSH-root): tspp.py -t

This shows if the TSP are connected or not - a reboot fixed ours

HTH

Rich