cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1717
Views
0
Helpful
11
Replies

What is the retry count for "Automatic connect" in TMS.

RAMEEZ RAHIM
Level 1
Level 1

Hi,

I would like to know, how many times a TMS would try an Endpoint/MCU while trying to send call out information - before saying

"Allocate failed, conference is not automatically connected".

The conference type is Automatic connect

Automatic connect: Cisco TMS will automatically connect all the participants at the specified time and date.

2 Accepted Solutions

Accepted Solutions

Hi

Seems more like it's one initial try and then 3 re-tries after the initial try and it seems to be the same for the TCS and for the MCU.

So 1 initial + 3 retries before it states it cannot automatically connect it.

/Magnus

View solution in original post

I just checked: There indeed is such a setting, "Connection Attemps for Scheduled Calls", which defaults to three.

View solution in original post

11 Replies 11

Magnus Ohm
Cisco Employee
Cisco Employee

Hi

3 times as far as I know.

/Magnus

Hi Magnus,

It looks like 3 for MCU and 5 for Content server from my Conf control center logs.

9/1/2012 9:00:42 AM System User MCU1 Allocation failed: hostAddress:10.10.10.1, description:Getting XML document 'https://10.10.10.1//system.xml' failed.. URL: https://10.10.10.1//system.xml, base exception:Unable to connect to the remote server

9/1/2012 9:00:42 AM System User   Non-secure conference. Original value of the setting was 'if possible' and not all participants support encryption

9/1/2012 9:01:03 AM System User RECORDER Allocation failed: Unable to connect to the remote server

9/1/2012 9:01:24 AM System User MCU1 No response from main system

9/1/2012 9:02:06 AM System User RECORDER  Allocation failed: Unable to connect to the remote server

9/1/2012 9:02:06 AM System User MCU1 Allocation failed: hostAddress:10.10.10.1, description:Getting XML document 'https://10.10.10.1//system.xml' failed.. URL: https://10.10.10.1//system.xml, base exception:Unable to connect to the remote server

9/1/2012 9:02:06 AM System User   Non-secure conference. Original value of the setting was 'if possible' and not all participants support encryption

9/1/2012 9:02:48 AM System User MCU1 No response from main system

9/1/2012 9:03:09 AM System User RECORDER Allocation failed: Unable to connect to the remote server

9/1/2012 9:03:30 AM System User MCU1 Allocation failed: hostAddress:10.10.10.1, description:Getting XML document 'https://10.10.10.1//system.xml' failed.. URL: https://10.10.10.1//system.xml, base exception:Unable to connect to the remote server

9/1/2012 9:03:30 AM System User   Non-secure conference. Original value of the setting was 'if possible' and not all participants support encryption

9/1/2012 9:04:12 AM System User RECORDER Allocation failed: Unable to connect to the remote server

9/1/2012 9:04:12 AM System User MCU1 No response from main system

9/1/2012 9:04:12 AM System User MCU1 No contact with master system, 3 successive polls failed.

9/1/2012 9:04:54 AM System User MCU1 Allocation failed: hostAddress:10.10.10.1, description:Getting XML document 'https://10.10.10.1//system.xml' failed.. URL: https://10.10.10.1//system.xml, base exception:Unable to connect to the remote server

9/1/2012 9:04:54 AM System User RECORDER Allocate failed, the participant is not automatically called

9/1/2012 9:04:54 AM System User MCU1 Allocate failed, conference is not automatically connected

Wont TMS try this Endpoint at all after this?

Hi

Seems more like it's one initial try and then 3 re-tries after the initial try and it seems to be the same for the TCS and for the MCU.

So 1 initial + 3 retries before it states it cannot automatically connect it.

/Magnus

What does this error mean though?

Does it mean that there was not enough ports to allocate for the scheduled calls?

I received this error "Allocate failed, conference is not automatically connected" for a scheduled conference of 5 enpoints and we have an MCU with 20 port availability resource and at the time was only 12 total being used so not sure why it would fail.

Anyone have any idea?

Also can the MCU and TMS be configured that once the resources have been scheduled can the adhoc be restricted in making calls if the resources are booked?

Kjetil Ree
Cisco Employee
Cisco Employee

I'm not in front of a TMS right now, but can't you configure this value from Administrative Tools > Conference settings?

-Kjetil

Sent from Cisco Technical Support iPad App

I just checked: There indeed is such a setting, "Connection Attemps for Scheduled Calls", which defaults to three.

What does this error mean though?

Does it mean that there was not enough ports to allocate for the scheduled calls?

I received this error "Allocate failed, conference is not automatically connected" for a scheduled conference of 5 enpoints and we have an MCU with 20 port availability resource and at the time was only 12 total being used so not sure why it would fail.

Anyone have any idea?

Also can the MCU and TMS be configured that once the resources have been scheduled can the adhoc be restricted in making calls if the resources are booked?

Hugh Rivera
Level 1
Level 1

What does this error mean though?

Does it mean that there was not enough ports to allocate for the scheduled calls?

I received this error "Allocate failed, conference is not automatically connected" for a scheduled conference of 5 enpoints and we have an MCU with 20 port availability resource and at the time was only 12 total being used so not sure why it would fail.

Anyone have any idea?

Also can the MCU and TMS be configured that once the resources have been scheduled can the adhoc be restricted in making calls if the resources are booked?

Hugh,

What specific sw versions are you running here, i.e. TMS, MCU, TCS, etc? In particular what type of MCU is involved here? Are all the EPs and TCS on an available before the scheduled conference begins?

rgds,

Dale

Hi Dale,

TMS:  13.2.1

MCU:4.2(1.46) and it is an 4510 Codian MCU

We don't have a TCS.

Just TMS, MCU, ISDN GW Codian, VCS, Border Express and an Entrypoint.

Sorry, I was looking at Rameez's logs above that contained a TCS But if your CCC logs look like Rameez's, then it could be that TMS cannot connect to the system, either because of connectivity issues or it could be actually not turned on (?). In Rameez's case, that looks like what it is with regards to his TCS.

cheers,

Dale

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: