| Patrick Mowry 2007-02-28, 7:11 pm |
| Thanks,
I was registered to the wrong gatekeeper, the Authorization policy was set to authorize per the MeetingPlace 4.5 documentation, and the Video administration was using the wrong port number to talk to the internal gatekeeper for authorization.
Once I got a callback from TAC things progressed quickly with some issues being documentation errors, and others cleared up with a reboot.
Thanks to everyone for the replies.
-Patrick
-----Original Message-----
From: Timur Bayazitov [mailto:timurik@gmail.com]
Sent: Wed 2/28/2007 5:39 AM
To: Patrick Mowry
Subject: RE: [cisco-voip] MeetingPlace 5.4 video integration with anIPVC-3545-MCU
1. Read MeetingPlace section in Unified Communication SRND for ccm 5.0, all
MCUs _must_ register with Video Administration internal gatekeeper.
2. Check that External conference authorization policy is set to "none" in
MCU settings->advanced tab.
3 You need to select IPVC-36XX v5.x.
Best regards, Timur Bayazitov
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Patrick Mowry
Sent: Tuesday, February 27, 2007 11:03 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] MeetingPlace 5.4 video integration with
anIPVC-3545-MCU
Hello,
Anyone using the MeetingPlace video integrtation? I'm having no luck
getting it going and I figured I'd try the list while I wait on TAC.
Whenever I try to schedule a meeting from the Meetingplace Video
Administration page, a telnet session to the MCU gives me the following
errors:
1034619 ERROR Ec Manager |Can't find. Type is Conference Authorizer
1034619 DEBUG2 GCC Control|CONF (0)0xd9d1b00: Conference not
authorized
Part of the problem may be that the Video administration resource management
will let me define the MCM gatekeeper I have, but it will only allow me to
define the MCU as attached to the default local_gatekeeper. And along those
lines the options I have for MCU are IPVC-36XX v5.x or the IPVC3540 v4.x
when what I have is a 3545 MCU running 5.1.
Thanks for any suggestions,
-Patrick
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
|