CTMS "Insufficient Resources" problem

Answered Question
Mar 29th, 2010

We have had several multipoint meetings recently where a user will try to dial their scheduled meeting, however they will get an "insufficient resources" error.  They may then try again and be able to dial in OK.  Note that this only happens sometimes, usually people are able to dial in OK.

Checking the CTMS system errors will show "There is not sufficient resources.  Availible segments: 0" even though there are only around 25 - 30 of the availble 48 segments being used (usually 4 -5 CTS-3000s and 1 - 2 CTS-1000s, all with presentation codecs) and all 48 segments are allocated to scheduled meetings on CTMS.

Any ideas?

We are running CTMS 1.60

I have this problem too.
0 votes
Correct Answer by gogasca about 6 years 9 months ago

If we have segments available as you stated take a look at:

 CSCtf55004 scheduled MP meeting gets rejected due to inaccurate resource calculation 
Will be fixed in 1.6.4 available in the next 2 weeks I think

Workaround:
1.      Migrate some of the meetings to other CTMS if there are multiple schedulable CTMS servers.

2.      Reduce the number of segments if meetings can’t be migrated.

HTH

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
gogasca Wed, 03/31/2010 - 01:52

If we have segments available as you stated take a look at:

 CSCtf55004 scheduled MP meeting gets rejected due to inaccurate resource calculation 
Will be fixed in 1.6.4 available in the next 2 weeks I think

Workaround:
1.      Migrate some of the meetings to other CTMS if there are multiple schedulable CTMS servers.

2.      Reduce the number of segments if meetings can’t be migrated.

HTH

Nick Halbert-Li... Wed, 03/31/2010 - 15:01

Thanks for the resonse.  These are usually a single, large meeting rather than a number of smaller meetings, meaning it won't do anything for us to migrate meetings over, but at least we now know it's an issue that's being addressed so for now we'll just live with it and wait for the patch.

Thanks,

- Nick

Actions

This Discussion