cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1006
Views
0
Helpful
3
Replies

Cannot connect conference bridge to Telepresence MCU?

samhopealpha
Level 1
Level 1

Hi everybody

I would like to create a video conference by using the Telepresence Server

Here is the background

A.
CUCM 10.5

B.
Telepresence conductor x3.0.3

C.
Telepresence server 4.1(2.33) - VM

- Enabled: Virtual machine activation
- Enabled: Encryption
- 5: Screen Licenses
 
D.
Telepresence server 4.1(2.33) - MCU Media 310
- Enabled: Media 310 activation
- Enabled: Encryption
- 0: Screen Licenses
 
Scenario #1 (work perfectly):
If using the TP conductor + TPS (VM) + CUCM, the video conference work perfectly
 
Scenario #2 (problem):
If using the TP conductor + TPS (MCU) + CUCM, I got problem on adding conference bridge in TP conductor.
 
The status shows 
Unusable, Waiting for conference bridge to be verified
 
After restart TP conductor and TPC(MCU)
The status shows 
Unusable, Error communicating with bridge: error="Method not supported"
 
Conference bridge configuration in Conductor
Name: CFB-MCU
State: Enabled
IP: x.x.x.x
Protocol: HTTPS
Port: 443
Username: xxxxxx
password: xxxxxx
Conference bridge type: TelePresence MCU
Conference bridge pool: CFB_Pool3
Dedicated content ports: 0
SIP port: 5061
 
Those configuration are same as Scenario #1, except the conference bridge type is "TelePresence Server"
 
Do I have any mistake here?
 
Thanks in advance
 
Sam
3 Replies 3

James Hodgson
Level 1
Level 1

Hi,

 

It sounds like both of the machines listed here are actually TelePresence Servers (the VM definitely is, and the Media 310 is a model name for a TS, the 5310 would be the codename for the equivalent MCU.) I'd recommend you delete the 310 and re-add it as a TelePresence Server bridge, assuming that it really is a TS too. :)

With XC3.0.3, you require screen licenses to be installed on all bridges, both VM or hardware in order for them to be used by the Conductor. It's also worth checking that you have encryption keys installed on both the HM and the hardware TS to allow for HTTPS communication.

 

Regards,

James

Can you provide a screenshot of the "Telepresence server 4.1(2.33) - MCU Media 310" status page as you have it listed?

jvalderrama
Level 1
Level 1

the same thing happened to me and I changed Conference bridge type to: TelePresence Server