cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

465
Views
0
Helpful
3
Replies
jeremy smith
Beginner

TMS hangs up in the middle of adhoc call after a prior Scheduled call

Hello, Cisco Friends!

 

Perhaps you can help me discover what is causing this behavior in TMS, and advise how we might fix it..

 

Most of our connections are scheduled in advance in TMS, but there will be some times when we will connect or disconnect our rooms manually from a touch panel in the room, and it’s not scheduled in TMS. The panel is a control system, not a Cisco touch interface.

 

Pasted below is a log of what happened yesterday. This is the Event Log from the conference ID of the Class. The first call we see, scheduled in TMS, is a Class, and the 2nd one is a Meeting.  The meeting was not scheduled in TMS and we connected by using the touch panel in the room to dial the other room after hanging up the Class connection via the touch panel.

 

I think what is happening is that the Class gets an Extension on it’s conference 5 minutes before the TMS scheduled end time of 11:55AM. Then when I hang up the Class call with the touch panel at 11:53AM, and manually connect the Kerr 1001 room to a different room, Kerr 1001 codec thinks it is still inside the TMS conference instead of making a real Ad Hoc conference and the ‘extensions’ on the 10:25AM conference ‘run out’ in the background, and so at 12:25PM, the call (Meeting) that we manually dialed at 11:54AM that goes until 12:50PM, all the sudden gets disconnected by TMS and everyone in the classrooms (and us) are confused and caught off guard by that so we have to interrupt the meeting to reconnect the 2 rooms. Therein lies the problem.

 

Is there any setting in TMS or a VCS that we can change so that when we hang up a call directly on the Codec (via room control system or it’s web UI) and then dial another endpoint, that the (scheduled) TMS Conference gets ended? Or… is this just a bug in TMS? You can see in the log at 11:54AM that TMS recognizes that the different room we connected to for the Meeting was an ‘Ad hoc call’ but there is no separate Conference ID for it. Once the unwelcomed disconnect came from TMS at 12:24:53PM, and I manually redialed the connection for the Meeting, it created an actual Ad hoc ‘Conference’ with it’s own Event Log and CID in the TMS system.  I pasted that just below the other log. That Conference’s “ConferenceEnded’ at 12:55PM happened because there was a Scheduled TMS call for one or both of the rooms to begin at 12:55 PM, and I would like to preserve that behavior in making any changes.

 

 

Date                           Type               User   System                      Description

 

1/9/18 12:24:53 PM         CallInfo                      Kerr 1001     Instance: Meeting released on port 1

1/9/18 12:24:00 PM         CallInfo                                              Instance: Displayed 1 minutes left of conference message

1/9/18 12:20:00 PM         CallInfo                                              Instance: Displayed 5 minutes left of conference message

1/9/18 12:19:30 PM         CallInfo                      Kerr 1001     Instance: Sent message to participant Kerr 1001: Your meeting was not automatically extended because you have reached the maximum number of extensions

1/9/18 12:19:30 PM         ConferenceInfo                                          Instance: Your meeting was not automatically extended because you have reached the maximum number of extensions

1/9/18 12:04:30 PM         CallInfo                      Kerr 1001     Instance: Sent message to participant Kerr 1001: The conference was extended, the new endtime is: 12:25 PM

1/9/18 12:04:30 PM         ConferenceInfo                                          Instance: Extended by 15 minutes

1/9/18 11:54:25 AM         CallConnected                     Kerr 1001     Instance: Call connected: karpen106@vc.unc.edu

1/9/18 11:54:16 AM         ConferenceInfo                  Kerr 1001     Instance: Ad hoc call added: sip:karpen106@vc.unc.edu

1/9/18 11:53:51 AM         CallDisconnect                    Kerr 1001     Instance: Call disconnected: karpen011@vc.unc.edu, Karpen 011. Unknown

1/9/18 11:49:30 AM         CallInfo                      Karpen 011  Instance: Sent message to participant Karpen 011: The conference was extended, the new endtime is: 12:10 PM

1/9/18 11:49:30 AM         CallInfo                      Kerr 1001     Instance: Sent message to participant Kerr 1001: The conference was extended, the new endtime is: 12:10 PM

1/9/18 11:49:30 AM         ConferenceInfo                                          Instance: Extended by 15 minutes

1/9/18 10:25:34 AM         CallInfo                      Kerr 1001     Instance: Duo video opened. Source: Kerr 1001

1/9/18 10:25:06 AM         CallConnected                     Kerr 1001     Instance: Call connected: karpen011@vc.unc.edu

1/9/18 10:25:04 AM         CallInfo                      Kerr 1001     Instance: SIP Dial => karpen011@vc.unc.edu

1/9/18 10:25:01 AM         CallInfo                      Kerr 1001     Instance: Sent message to participant Kerr 1001: Scheduled call being connected

1/9/18 10:25:01 AM         CallInfo                      Kerr 1001     Instance: Meeting allocated on port: 1

1/9/18 10:25:00 AM         CallInfo                      Karpen 011  Instance: Sent message to participant Karpen 011: Scheduled call being connected

1/9/18 10:25:00 AM         CallInfo                      Karpen 011  Instance: Meeting allocated on port: 1

1/9/18 10:25:00 AM         ConferenceActive                                      Instance: Started

1/9/18 10:24:00 AM         CallInfo                                              Instance: Display 1 minute message

1/9/18 10:20:00 AM         CallInfo                                              Instance: Display 4 minute message

1/9/18 10:10:01 AM         ConferenceInfo                                          Instance: Registered

12/20/17 9:48:29 AM       ConferenceInfo      Steve Kiesa               Instance: Created, start time 01/09/2018 10:25:00 -05:00

12/20/17 9:48:29 AM       ConferenceInfo      Steve Kiesa               Conference: 2 exceptions

12/20/17 9:48:29 AM       ConferenceInfo      Steve Kiesa               Conference: Recurrent series created, Occurs every Tuesday and Thursday effective Jan 9, 2018 until Apr 13, 2018.

 

 

Date                           Type               User   System                      Description

 

1/9/18 12:55:00 PM         ConferenceEnded                                      Instance: Ended

1/9/18 12:27:55 PM         CallInfo                      Kerr 1001     Instance: Duo video opened. Source: Kerr 1001

1/9/18 12:27:22 PM         CallConnected                     Kerr 1001     Instance: Call connected: karpen106@vc.unc.edu

1/9/18 12:27:21 PM         ConferenceInfo                  Kerr 1001     Instance: Ad hoc call added: sip:karpen106@vc.unc.edu

1/9/18 12:27:21 PM         ConferenceInfo                                          Instance: Created, start time 01/09/2018 17:27:21 +00:00

1/9/18 12:27:21 PM         ConferenceInfo                                          Conference: Created

 

 

3 REPLIES 3
Wayne DeNardi
VIP Advisor

What version of TMS are you running?  There are some bugs in some of the older releases which affect some call scenarios where ad-hoc and scheduled calls are occurring on the one endpoint.

Are the scheduled calls set up to auto-connect the endpoints, or are they set up as OBTP?

Another thing to check would be that all the endpoints have the correct time and, preferably, are all set to get the current time from the same local NTP server.

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.

Hello, Wayne!
We are running TMS 14.6.2.
The Scheduled calls are set to dial automatically and auto-answer.
The time servers are all local and current for all codecs and TMS.

Just reading your description and what I see in the conference logs, you could end the conference in TMS so it doesn't override any ad-hoc conferences the endpoints might be in. Another idea might be to set the conference extension to Endpoint Prompt, instead of Automatic Best Effort. In later releases of TMS, they've added additional conference extension features, one of them might help in this situation.
Create
Recognize Your Peers
Content for Community-Ad