It’s looking like a bug 
Bug ID CSCum92449

Its not an exact match but using an mx300 G2 as the 3rd party it looks the same

Andy
[email protected]



> On 4 Feb 2015, at 16:13, Andy <[email protected]> wrote:
> 
> Hi Brian, 
> Yes the MCU is in the same Device Pool
> 
> I’ll pull some new logs and have a look through them again 
> 
> Andy
> [email protected] <mailto:[email protected]>
> 
> 
> 
>> On 4 Feb 2015, at 16:08, Brian Meade <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>> Might want to pull CallManager traces and see what happens when it tries to 
>> allocate the video conference bridge.  Do you have the MCU in the same 
>> device pool as the rest of the devices?
>> 
>> On Wed, Feb 4, 2015 at 8:25 AM, Andy <[email protected] 
>> <mailto:[email protected]>> wrote:
>> Hi,
>> I’m in the process of deploying DX80 and 70 endpoints that are registered to 
>> CUCM, that piece is ok.
>> I can place calls between them and audio conferencing is fine, my issue is 
>> with a conference with video…….
>> 
>> I have an MCU5310 running version 4.5(1.45) which I have registered with 
>> CUCM 9.1.2.11900-12 as a Cisco Telepresence MCU.
>> That seems to be fine.
>> 
>> So I have created a new device pool and MRGL which all participants from an 
>> end point perspective are in (1x dx80, 1x dx70, 1x8941, 1x Jabber Client)
>> They are all in the same region.
>> 
>> But if I try and create a conference from Jabber when I try to merge the 
>> participants it says Waiting to Join and the DX plays MOH
>> I get the same effect if I try to start the con on one of the DX endpoints.
>> 
>> Do I need to setup a SIP connection between the MCU and the CUCM?
>> in the 4.4 guide its gives some config settings on SIP but in the 4.5 code 
>> they are not available.
>> 
>> I don’t have access to the 4.4 code to downgrade at the moment.
>> 
>> Any pointers would be gratefully received.
>> 
>> 
>> Andy
>> [email protected] <mailto:[email protected]>
>> 
>> 
>> 
>> 
>> _______________________________________________
>> cisco-voip mailing list
>> [email protected] <mailto:[email protected]>
>> https://puck.nether.net/mailman/listinfo/cisco-voip 
>> <https://puck.nether.net/mailman/listinfo/cisco-voip>
>> 
> 

_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip

Reply via email to