TMSXE + TCS questions

[Julien CHEVALIER]

Hi,

I installed the following components (all updated with the last software):

• VCS C
  
• VCS E
  
• TMS
  
• TMSXE
  
• TCS
  
• MCU 45**
  

We have an exchange 2010 server

The TMSXE Cisco form is deployed in outlook client.

The TMSXE configuration returns no errors and i can add my 2 endpoints in the tool

Communication between TMSXE and TMS is ok

Communication between TMSXE and the CAS server is ok

Call routing is ok between my endpoints and my MCU/TCS is ok

TMSXE services are started

When i am scheduling with TMS: ok

Now, when i am trying to schedule with my Cisco form 2 endpoints, i got the calendar reservation but no confirmation or reject message from tmsxe.

Is it normal? Do you have any idea of the problem?

Must i receive the same email as if i had scheduled with the TMS scheduler? if no, how can i reveive this email too?

The TMSXE logs in INFO mode doesn't show any error, logs in DEBUG mode will come later

How can i force to record a scheduled conference with the cisco form? No option allows it like in the TMS Scheduler?

Thanks you for your help

Regards,

Julien C

[Paul Woelfel]

Hi suppose you have set the MCU routing on the TMS conference settings page to "only if needed". So TMS will establish an point to point call and won't send you a confirmation.

[Julien CHEVALIER]

No, it is actually in always because we don't want multipoint endpoints to host scheduled conferences. But i don't understand the impact.

With the TMS Scheduler, we can have only if needed, always, never parameter and receive the email.

Are you saying we can receive the email only if "only if needed" parameter is configured with the Cisco form?

Regards,

Julien

[Saurabh Gupta]

Hi Julien,

When you have 2 or more than 2 participants, you would always get the email notification of the conference booking, provided proper email address is used in TMS and TMSXE for booking confirmation.

If you are getting the room acceptance from Exchange Server and not booking confirmation, then there is something wrong between TMS and TMSXE, you need to check that.

Simplest troubleshooting would be to check TMSXE service is started . For more further troubleshooting, I would advise to open TAC Case with Cisco.

And for recording to work with Cisco form, you would need to create one recording SIP alias ( Just like Room Mailbox alias) and have that added into exchange server and TMSXE , just like you have added room mailboxes with all those permissions.

Once you do it, you can easily add recording server into the VC booking along with rooms , that would work with/Without Cisco form.

[Julien CHEVALIER]

Hi,

Indeed, i am waiting for the system team confirmation about the room auto acceptance.

TMSXE service is started.

If i have to create a recording SIP alias, it is a big problem because the streaming and VOD URL will not be generated in the email so we have less functionality than with the TMS Scheduler.

Thanks for your help

Regards,

Julien

[daleritc]

Hi Julien,

As you say your using the custom form along with Exchange 2010, you could be running into a known issue that is documented in the TMSXE Install Guide (see page 44):

http://www.cisco.com/en/US/docs/telepresence/infrastructure/tmsxe/install_guide/Cisco_TMSXE_install_guide_3-0.pdf

Now with that said, Microsoft as released Exchange Server 2010 SP2 RU3 (released in June) that appears to fix the old problem with the Resource Booking Attendant in Exchange 2010 not processing meeting requests containing custom code. We've tested this internally and we are now able to book both normal resources and resources added to TMSXE while using the Cisco form. Therefore, and rather than the work around that is suggested in the above documentation, I'd recommend upgrading your Exchange Server with this RU. If you can't do that, then you can utilize the work around as discussed in the above documentation.

And as far as the recording thing, the option to add a recording along with a specific alias (e.g. like you can do in the TMS Scheduler) is currently not supported in the Cisco Form. However, and as Saurabh suggests, you can can create it as he describes and simply include it as a participant when creating the conf in Outlook...albeit it will only be that one recording alias type.

Hope this helps.

rgds

Dale

[Julien CHEVALIER]

Hi Dale,

Thanks you for your help

I already did this workaround but it doesn't works.

Unfortunately, we can not install the Exchance 2010 SP2 RU3

You will find now the debug log in the TMSXE and we don't see any booking request coming:

2012-11-08 17:10:16,392 [R] INFO  ReplicationEngine - ReplicationEngine shut down.

2012-11-08 17:10:16,392 [17] INFO  SubscriptionWorkItemProducer - Shutdown of SubscriptionWorkItemProducer started...

2012-11-08 17:10:16,392 [15] DEBUG SubscriptionWorkItemProducer - Shutdown in blocking state.

2012-11-08 17:10:16,392 [15] DEBUG SubscriptionWorkItemProducer - Shutdown in running state.

2012-11-08 17:10:16,408 [16] DEBUG SubscriptionWorkItemProducer - Shutdown in blocking state.

2012-11-08 17:10:16,408 [16] DEBUG SubscriptionWorkItemProducer - Shutdown in running state.

2012-11-08 17:10:16,408 [17] INFO  SubscriptionWorkItemProcessor - Shutdown of SubscriptionWorkItemProcessor started...

2012-11-08 17:10:16,408 [17] INFO  SubscriptionWorkItemProcessor - SubscriptionWorkItem Processing stopped...

2012-11-08 17:10:16,408 [12] DEBUG SubscriptionWorkItemProcessor - Subscription Work Item processing completed...

2012-11-08 17:10:16,408 [17] INFO  SubscriptionWorkItemErrorHandler - Shutdown of SubscriptionWorkItemErrorHandler started...

2012-11-08 17:10:16,408 [13] DEBUG SubscriptionWorkItemProcessor - Subscription Work Item processing completed...

2012-11-08 17:10:16,408 [14] DEBUG SubscriptionWorkItemProcessor - Subscription Work Item processing completed...

2012-11-08 17:10:16,408 [17] DEBUG SubscriptionWorkItemProducer - Waiting for processor to finish...

2012-11-08 17:10:16,408 [17] INFO  SubscriptionWorkItemProducer - Shutdown of subscription event argument processor completed...

2012-11-08 17:10:16,408 [10] DEBUG SubscriptionWorkItemErrorHandler - Completed shutdown of Failure Resolve Processor...

2012-11-08 17:10:16,424 [17] DEBUG SubscriptionWorkItemProcessor - Waiting for Processing to finish...

2012-11-08 17:10:16,424 [17] INFO  SubscriptionWorkItemProcessor - Shutdown of subscription work item processor completed...

2012-11-08 17:10:16,424 [17] DEBUG SubscriptionWorkItemErrorHandler - Waiting for processor to finish...

2012-11-08 17:10:16,424 [17] INFO  SubscriptionWorkItemErrorHandler - Shutdown of subscription event error handler completed...

2012-11-08 17:10:16,424 [17] DEBUG ConferenceNursery - Shutdown of ConferenceNursery started...

2012-11-08 17:10:16,455 [NurseryShutdown] INFO  ConferenceNursery - Received shutdown message. Closing event admission. Shutting down Conference Nursery...

2012-11-08 17:10:16,455 [5] DEBUG ConferenceNursery - Processing completed...

2012-11-08 17:10:16,455 [17] DEBUG ConferenceNursery - Waiting for ConferenceEvents to finish...

2012-11-08 17:10:16,455 [3] DEBUG ConferenceNursery - Processing completed...

2012-11-08 17:10:16,455 [4] DEBUG ConferenceNursery - Processing completed...

2012-11-08 17:10:16,455 [17] INFO  ConferenceNursery - ConferenceNursery stopped...

2012-11-08 17:10:16,455 [17] INFO  TMSXE - TMSXE completed shutdown procedure...

2012-11-08 17:10:32,930 [4] INFO  Log4NetUtils - The location of the log config file is: C:\ProgramData\Cisco\TMSXE\Config\Log4Net.config

2012-11-08 17:10:32,969 [4] INFO  Log4NetUtils - Logging module initialized successfully

2012-11-08 17:10:32,999 [4] INFO  TMSXE - Cisco TMSXE 3.0.2 Build 767 is starting...

2012-11-08 17:10:33,020 [4] DEBUG TMSXEApp`2 - The Config Connection string is C:\ProgramData\Cisco\TMSXE\Config, and the Storage Connection string is C:\ProgramData\Cisco\TMSXE\Storage

2012-11-08 17:10:33,042 [4] INFO  XmlStorage - File Loaded:AppSettings

2012-11-08 17:10:33,062 [4] INFO  TMSXE - The location of XML storage files is C:\ProgramData\Cisco\TMSXE\Storage

2012-11-08 17:10:37,696 [Startup] INFO  ExchangeConnection - Connected to Exchange server srv-cht1 (version 8.03.0279.001) as LOGIN (DOMAIN).

2012-11-08 17:10:37,696 [Startup] INFO  ExchangeConnection - The version of the Exchange Server API is Exchange 2007 Service Pack 1. Creating connection specific to this Exchange version.

2012-11-08 17:10:37,696 [Startup] INFO  XmlStorage - File Loaded:MonitoredSystems

2012-11-08 17:10:37,696 [Startup] DEBUG EWSAdapter - Found 2 enabled systems.

2012-11-08 17:10:37,883 [Startup] DEBUG MonitoredFolders - Adding mailbox

endpoint1@DOMAIN

with ID 4 as monitored system.

2012-11-08 17:10:38,305 [Startup] INFO  MonitoredFolders - Adding

endpoint1@DOMAIN:AQMkAGQ3YWNlNmUxLWI1MGMtNGYyOS1hMDE0LWU5NWJmNDJjZDdiMQAuAAADgN1GqQ6q/0OzNJL3OXrF5wEAuG7E5ulyOE67Xb7fzMm59AANJazQ9wAAAA

==

2012-11-08 17:10:38,321 [Startup] DEBUG MonitoredFolders - Adding mailbox

endpoint2@DOMAIN

with ID 7 as monitored system.

2012-11-08 17:10:38,446 [Startup] INFO  MonitoredFolders - Adding

endpoint2@DOMAIN:AAMkAGVlNGQ0OTdhLWU0NWMtNDU1MS04OTk5LWRlZDlhNWMwNDc3YQAuAAAAAADzxY9UQ7OUQaV+TEl/hMNtAQC4bsTm6XI4Trtdvt/Mybn0AA0lrND+AAA

=

2012-11-08 17:10:38,461 [Startup] DEBUG TMSXE - Trying to start TMSXE...

2012-11-08 17:10:38,477 [Startup] INFO  XmlStorage - File Loaded:CTMS4

2012-11-08 17:10:39,196 [Startup] WARN  ErrorCentral - TMS connection interrupted.

2012-11-08 17:10:39,211 [Startup] WARN  TMSXEApp`2 - Starting up with TMS connection down.

2012-11-08 17:10:39,258 [Startup] DEBUG ConferenceNursery - Starting ConferenceNursery with 3 ConferenceEvent processors

2012-11-08 17:10:39,274 [Startup] INFO  ConferenceNursery - ConferenceNursery started, enabled event processing.

2012-11-08 17:10:39,305 [R] INFO  ReplicationEngine - ReplicationEngine starting.

2012-11-08 17:10:39,336 [Startup] DEBUG EWSAdapter - Creating Subscription for system id 4

2012-11-08 17:10:39,540 [Startup] INFO  SyncThenPullWorkLeader - System ID 4: Starting with existing syncFolder subscription.

2012-11-08 17:10:39,540 [Startup] DEBUG SyncFolderItemsWorker4 - Starting SyncFolderItemsWorker from scratch.

2012-11-08 17:10:39,540 [Startup] DEBUG EWSAdapter - Successfully created subscription for system ID 4.

2012-11-08 17:10:39,555 [Startup] INFO  SubscriptionWorkItemProducer - Added new subscription with sys id 4 as part of startup

2012-11-08 17:10:39,555 [Startup] DEBUG EWSAdapter - Creating Subscription for system id 7

2012-11-08 17:10:39,555 [Startup] INFO  XmlStorage - File Loaded:CTMS7

2012-11-08 17:10:39,555 [Startup] INFO  SyncThenPullWorkLeader - System ID 7: Starting with existing syncFolder subscription.

2012-11-08 17:10:39,555 [Startup] DEBUG SyncFolderItemsWorker7 - Starting SyncFolderItemsWorker from scratch.

2012-11-08 17:10:39,555 [Startup] DEBUG EWSAdapter - Successfully created subscription for system ID 7.

2012-11-08 17:10:39,555 [Startup] INFO  SubscriptionWorkItemProducer - Added new subscription with sys id 7 as part of startup

2012-11-08 17:10:39,555 [Startup] INFO  SubscriptionWorkItemProducer - SubscriptionWorkItemProducer started. Grace time between each subscription pull is 00:00:05. Queue polling interval is 00:00:00.3000000.

2012-11-08 17:10:39,555 [Startup] INFO  SubscriptionScheduler - SubscriptionScheduler started...

2012-11-08 17:10:39,555 [Startup] INFO  TMSXE - TMSXE completed startup procedure...

2012-11-08 17:10:49,305 [R] WARN  TransactionRetryDelayController - The Cisco TMS Server is not responding. Halting.

Do you have any idea?

Thanks you for your help

Regards,

Julien