I wonder how your MCU is dialing out via H.323, as it should be SIP if you're using Conductor with B2BUA, unless somewhere along the line, you're installation isn't configured correctly.
I'm using B2BUA with VCS. I have configured my alias@IP_Address endpoints as H323, MCU calls out via SIP and VCS does the H.323-SIP interworking. One thing I noticed was when we added our Conductors into TMS, TMS set the booking options for it to allow H.323 inbound and outbound dialing, we just never changed it because that was what TMS had done when it was added.
If the MCU should only be using SIP that may make inefficient use of licensing as local H.323 MCU participants will eat up a traversal license. Not a huge issue, but something to take note of. Realizing my locals endpoints should all be SIP. (not entirely my choice :)
Up to now our setup is using Outlook integration where Conductor fires up the MCU conference. I believe Conductor is using it's CPL methods for that, and I also have Multiway working that way, as well as a few Rendezvous VMRs to test with.
From my reading it looks like the B2BUA is the new method to configure Rendezvous and Multiway.
I may turn off the MCUs H.323 registration and hopefully SIP calling will take over entirely for all MCU calls. Wish me luck !
Thank you for your valuable input on this subject so far :)
If your MCU is dialing out via H323, than it's using the old CPL (call policy) method. I'd suggest you make the switch to B2BUA which is SIP only, since CPL will be going away sometime in the future for Conductor.
When you say MCU's H323 registration, is it registered to a VCS? I've never used CPL method, but I beleive it's the same setup as B2BUA where the MCU must not be registered to anything, and all calls are routed through Conductor.
I will agree, Conductor can be a handful, but what you can do with it pays off I believe.
I did check the configuration guides for Conductor using call policy and I see the configuration is different than B2BUA, in where you actually register it to a VCS or CUCM, unlike B2BUA where you don't.
I think there was one discussion or two here in the forums about the move from CPL to B2BUA, but that was some time ago when I recall seeing it.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...