Had this problem too with CWMS 2.0. In my case, the problem was with a SIP Route Pattern Configuration as I used Domain Routing as a Pattern Usage. After I changed it to IPAddress Routing everything works like a charm (most likely I got some issues with DNS configuration).
Personally, I never really use the null partition but before we go there. You have a couple different route patterns. The first is an inbound call pattern(s) that are going to be standard route patterns (i.e. numeric) and you'll have some outbound PSTN patterns for the actual outdialing that CWMS does. You then have some SIP route patterns that can either be defined as IP or FQDN for each media server. After you connect and then want to join a meeting, those SIP route patterns are used to redirect you to the appropriate server where a meeting is hosted. For those patterns, are you using IP or FQDN and what partition are they in? If you are using FQDN then you may need to change to IP depending on your DNS configuration on CUCM.
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...