cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
506
Views
0
Helpful
3
Replies
Highlighted
VIP Mentor

Auto Dialled Participant, TPS, Conductor and TMS

Hi all,

I just wanted to know how the telepresence server/MCU calls the auto dialled participant in a conference. Is the call sent directly to the endpoint or is the call sent to the call control system that is managing the endpoint.

Supposing I have an endpoint that is managed by VCS and another that is managed by CUCM and these are both configured as auto dialled for a conference. Does the TPS/MCU send the call to VCS or directly to the endpoint once the conductor has forwarded the auto dialled participants to the MCU/TPS

Please rate all useful posts
2 ACCEPTED SOLUTIONS

Accepted Solutions
Highlighted

The VCS or CUCM as call controls in Conductor controlled conferences will always be a part in the call flow for any type of conference (adhoc, rendezvous, auto dialled participants). In the case of auto dialled participants, the TPS/MCU will send an INVITE request to the CUCM/VCS that are responsible for initiating a session to the endpoint.  Once call setup is complete, the media flows directly between endpoint and the conference bridge.

The Conductor and its conference bridges use SIP to call auto-dialed participants, H.323 endpoints can be called into a conference through the VCS’s inter-working feature.

regards,

Acevirgil

View solution in original post

Highlighted
Beginner

Hi,

This depends significantly on whether you are using TelePresence Conductor in B2BUA mode or in policy service mode. For now I will assume B2BUA mode as this is the deployment model for CMR Premise/Hybrid:

In TelePresence Conductor you have the concept of a 'Location' which is generally the remote destination for a call control device such as a VCS or UCM. All bridge pools must be associated with a location for outbound calls.

When a conference is created on a given bridge, the TS/MCU will be told by the Conductor to dial a randomly generated URI containing the Conductor's IP address. This call will reach the Condutor and be forwarded on (with the correct ADP URI) to the location for that corresponding bridge/pool. If the call control device for that location cannot find the correct endpoint then the call will fail. At all points will the SIP signalling traverse the Conductor.

In policy mode, the bridges are configured to talk directly to their VCS/UCM trunks. As such the calls will be placed directly with those devices for routing to the endpoint.

Regards,

James

View solution in original post

3 REPLIES 3
Highlighted

The VCS or CUCM as call controls in Conductor controlled conferences will always be a part in the call flow for any type of conference (adhoc, rendezvous, auto dialled participants). In the case of auto dialled participants, the TPS/MCU will send an INVITE request to the CUCM/VCS that are responsible for initiating a session to the endpoint.  Once call setup is complete, the media flows directly between endpoint and the conference bridge.

The Conductor and its conference bridges use SIP to call auto-dialed participants, H.323 endpoints can be called into a conference through the VCS’s inter-working feature.

regards,

Acevirgil

View solution in original post

Highlighted
Beginner

Hi,

This depends significantly on whether you are using TelePresence Conductor in B2BUA mode or in policy service mode. For now I will assume B2BUA mode as this is the deployment model for CMR Premise/Hybrid:

In TelePresence Conductor you have the concept of a 'Location' which is generally the remote destination for a call control device such as a VCS or UCM. All bridge pools must be associated with a location for outbound calls.

When a conference is created on a given bridge, the TS/MCU will be told by the Conductor to dial a randomly generated URI containing the Conductor's IP address. This call will reach the Condutor and be forwarded on (with the correct ADP URI) to the location for that corresponding bridge/pool. If the call control device for that location cannot find the correct endpoint then the call will fail. At all points will the SIP signalling traverse the Conductor.

In policy mode, the bridges are configured to talk directly to their VCS/UCM trunks. As such the calls will be placed directly with those devices for routing to the endpoint.

Regards,

James

View solution in original post

Highlighted

Thank you james, getting clearer now..

Few questions

When a conference is created on a given bridge, the TS/MCU will be told by the Conductor to dial a randomly generated URI containing the Conductor's IP address.

I assume this URI is based on the alias that is configured on the conductor??...

Next question

This call will reach the Condutor and be forwarded on (with the correct ADP URI) to the location for that corresponding bridge/pool. If the call control device for that location cannot find the correct endpoint then the call will fail. At all points will the SIP signalling traverse the Conductor

So the conductor creates the bridge on the TS/MCU using the randonly generate alias, then the coductor forwards the call to the location that is assigned to the bridgepool for the conference alias.??

So its the conductor that sends INVITE out to the VCS/CUCM for the ADP? or is it the TS/MCU that does this?

Please rate all useful posts