TMS Smart Scheduler Error

[davidtreadwell]

I am getting an error message when trying to use smart scheduler to book a conference with 'Video Dial In:' participants only.

The error message is:

"Could not set up conference with the following participants(s): Video Dial In."

TMS 14.3.1

Cisco VCSc Cluster (2 x peers running X8.1.0)

Cisco MCU 5320 (2 x MCUs connected with stacking cable, both running software version 4.4(3.57))

There is also a link to an instance of CUCM (9.x) from the VCSc cluster, which has been deployed as per this guide......

http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/vcs/config_guide/Cisco_VCS_Cisco_Unified_Communications_Manager_Deployment_Guide_CUCM_8_9_and_X7-2.pdf

[Florian Kroessbacher]

Hy,

we have actualy set up a tac case with the same problem. we are Running a mse with an mvu 8420 will update on any news cheers floh

[martin1.plank]

Hi Michael,

Using "IP / H323" instead of SIP works fine for External Participants.

Both are using the same MCU.

The MCU is registered to VCS Cluster with H323 and SIP.

The Users, Endpoints, VCS, MCU are all located within the same IP-Zone.

So can you tell me the way to analyse the scheduling procedure?

kind regards

Martin

[martin1.plank]

Hi outthere,

Now I changed the MCU Setting in TMS an set Parameter "Numeric ID Quantity" from 80 to 200.

After "Save" the parameter didn't change, but the scheduling Process did work agian.

kind regards

Martin

[Michael McGary]

David,

Cisco TMS Smart Scheduler Video Call-in Participants adds a SIP Video Dial-in on the Booking API call to TMS.

To simulate what the Smart Scheduler does, go directly to TMS Web UI:  Booking -> New Conference, Add Participants -> External tab -> change protocol to SIP and quantity to 4 or 5. Click Ok. Click Save.

Look at the top yellow banner to see what error message is generated. As this is a SIP Video Dial-in, that means you either need to have a conferencing host (Cisco TP MCU, TelePresence Server, Conductor or TANDBERG MPS) with SIP enabled and properly registered (e.g. SIP Proxy/Registrar or trunked to CUCM) or a Cisco VCS or Expressway registered in TMS. TMS understands that the VCS can interwork SIP to H.323 and allows that to be used in the resource routing logic.

This is likely a Resource Routing logic issue and you need to solve that issue first before you can schedule with other interfaces like Smart Scheduler or Microsoft Exchange.

Michael McGary, Product Manager