cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1497
Views
0
Helpful
5
Replies

TMS Conference Control Center logs - Inconsistent

RAMEEZ RAHIM
Level 1
Level 1

We have a strange observation with our TMS 14.

We could see conference activity logs in the Conference Control Logs, even for conferences that are deleted.

Conference1: Test1

Start Time: 6/4/2013 02:00PM

End Time: 6/4/2013 03:00PM

Status: Deleted

Dialin Number: 8778120

6/3/2013 9:15:26 PM          BAPI                     Conference Created

6/3/2013 9:16:03 PM          BAPI                     Conference Deleted

6/4/2013 2:46:17 PM          network service network service          MCU1          Call Connected: 123456789

6/4/2013 2:46:17 PM          network service network service          MCU1          Call Connected: 234567891

6/4/2013 2:46:17 PM          network service network service          MCU1          Call Connected: 634567891

6/4/2013 2:50:00 PM          network service network service                     Display 10 minute message left of conference

6/4/2013 2:55:00 PM          network service network service                     Your meeting was not automatically extended because no meeting participants are connected

6/4/2013 2:55:00 PM          network service network service                     Display 5 minute message left of conference

6/4/2013 2:55:00 PM          network service network service                     Conference ends in five minutes

6/4/2013 2:59:00 PM          network service network service                     Display 1 minute message left of conference

When we further checked, we found something weird here.

The call connected logs seen on this conference actually belong to a conference Test2 that was active from 02:00 PM to 04:00PM on the same day with same dialin Number 8778120

Conference1: Test2

Start Time: 6/4/2013 02:00PM

End Time: 6/4/2013 04:00PM

Status: Finished

Dialin Number: 8778120

6/3/2013 9:16:59 PM          BAPI                     Conference Created

6/4/2013 1:55:00 PM          network service network service                     Display 4 minute message

6/4/2013 1:59:00 PM          network service network service                     Display 1 minute message

6/4/2013 2:00:00 PM          network service network service                     Conference Started

6/4/2013 2:00:00 PM          network service network service                     Non-secure conference. Original value of the setting was 'if possible' and not all participants support encryption

6/4/2013 2:00:06 PM          network service network service          MCU1          Meeting allocated on port: 3

6/4/2013 2:00:36 PM          network service network service          MCU1          Call Connected: 123456789

6/4/2013 2:05:20 PM          network service network service          MCU1          Call Connected: 234567891

6/4/2013 2:07:44 PM          network service network service          MCU1          Critical packet loss reported for participant: Conferenceroom1

6/4/2013 2:10:08 PM          network service network service          MCU1          Call Connected: 345678912

6/4/2013 2:14:55 PM          network service network service          MCU1          Duo video opened. Source: Conferenceroom3

6/4/2013 2:26:52 PM          network service network service          MCU1          Critical packet loss reported for participant: Conferenceroom1

6/4/2013 2:28:38 PM          network service network service          MCU1          Critical packet loss reported for participant: Conferenceroom1

6/4/2013 2:28:38 PM          network service network service          MCU1          Critical packet loss reported for participant: Conferenceroom2

6/4/2013 2:30:22 PM          network service network service          MCU1          Critical packet loss reported for participant: Conferenceroom1

6/4/2013 2:33:53 PM          network service network service          MCU1          Critical packet loss reported for participant: Conferenceroom1

6/4/2013 2:37:24 PM          network service network service          MCU1          Critical packet loss reported for participant: Conferenceroom1

6/4/2013 2:38:35 PM          network service network service          MCU1          Critical packet loss reported for participant: Conferenceroom1

6/4/2013 2:45:02 PM          network service network service          MCU1          Critical packet loss reported for participant: Conferenceroom1

6/4/2013 2:47:43 PM          network service network service          MCU1          Call Connected: 123456789

6/4/2013 2:47:43 PM          network service network service          MCU1          Call Connected: 234567891

6/4/2013 2:47:43 PM          network service network service          MCU1          Call Connected: 345678912

6/4/2013 2:48:54 PM          network service network service          MCU1          Critical packet loss reported for participant: Conferenceroom1

6/4/2013 2:56:03 PM          network service network service          MCU1          Critical packet loss reported for participant: Conferenceroom1

6/4/2013 3:14:42 PM          network service network service          MCU1          Duo video closed. Source: Conferenceroom3

6/4/2013 3:14:42 PM          network service network service          MCU1          Critical packet loss reported for participant: Conferenceroom3

6/4/2013 3:32:49 PM          network service network service          MCU1          Critical packet loss reported for participant: Conferenceroom1

6/4/2013 3:33:59 PM          network service network service          MCU1          Critical packet loss reported for participant: Conferenceroom1

6/4/2013 3:48:58 PM          network service network service          MCU1          Critical packet loss reported for participant: Conferenceroom1

6/4/2013 3:50:00 PM          network service network service                     Display 10 minute message left of conference

6/4/2013 3:55:05 PM          network service network service                     Resources unavailable to extend

6/4/2013 3:55:05 PM          network service network service                     Display 4 minute message left of conference

6/4/2013 3:55:05 PM          network service network service                     Conference ends in five minutes

6/4/2013 3:56:49 PM          network service network service          MCU1          Call disconnected: 234567891, Conferenceroom2. Normal, unspecified

6/4/2013 3:57:28 PM          network service network service          MCU1          Call Connected: 456789123

6/4/2013 3:57:46 PM          network service network service          MCU1          Call disconnected: 456789123, Conferenceroom4. Normal, unspecified

6/4/2013 3:57:46 PM          network service network service          MCU1          Critical packet loss reported for participant: Conferenceroom1

6/4/2013 3:58:22 PM          network service network service          MCU1          Critical packet loss reported for participant: Conferenceroom3

6/4/2013 3:59:00 PM          network service network service                     Display 1 minute message left of conference

6/4/2013 3:59:58 PM          network service network service          MCU1          Meeting released on port 3

We tried validating the behavior for similar deleted conferences and see all of them have inherited the logs from other active conferences.

Regards

Rameez

5 Replies 5

daleritc
Cisco Employee
Cisco Employee

What is the specific TMS version? Simply saying TMS 14 is too broad

Hi

It's TMS 14.1

Do you have possibly more than one TMS in the mix here? TMS Redundant setup?

And when you say the following:

We tried validating the behavior for similar deleted conferences and see  all of them have inherited the logs from other active conferences.

Were the deleted conferences also using the same dial-in number as the active confs?

Have you configured your MCU appropriately in TMS wrt to numeric id base, i.e. go to MCU in the TMS and select Settings > Extended Settings?

Hi Dale,

yes, Logs are inherited by a deleted conference only if they find an active confernece in their time frame with the same numeric id.

MCU Numeric id configurations are configured properly, enough numbers as required by port capacity is configured.

Hi,

I am unable to reproduce the problem (testing with the latest TMS code).

Could you give step by step details about what you do to trigger the problem?

Regards,

Kjetil