Issue with Ad-hoc Conference in Cisco Meeting Server 3.9

[m.soleimani]

Hi Dear friends,
I have Cisco Meeting Server (CMS) 3.9 and Cisco Meeting Management (CMM) 3.9. When I create an ad-hoc conference from an IP phone, the calling number is correctly displayed as the Directory Number (DN), and everything works fine.

However, when I create an ad-hoc conference using Cisco Jabber, the calling number for adding participants appears as the Meeting ID instead of the expected DN. Additionally, when adding a mobile number as a participant, the call disconnects after a few seconds.

Has anyone encountered this issue before or knows how to resolve it? Any insights would be appreciated!

[m.soleimani]

I configured a new Calling Search Space (CSS) for the trunk between Cisco Meeting Server (CMS) and Cisco Call Manager (CUCM) and applied it to inbound calls.

To ensure a specific Calling Party number for outbound calls, I set the Calling Party Transform Mask in all Route Patterns of the CSS to a predefined Directory Number (DN) (the Cisco Meeting Server IVR number).

With this configuration, when I add a participant to an ad-hoc conference, the calling number is correctly displayed as the specific DN, and everything works as expected.

Just wanted to share this setup in case anyone encounters a similar scenario. Let me know if you have any feedback or suggestions!