The Xima UCaaS Admin Portal covers general phone system administration independently of CCaaS. The recommendations below collect the conventions and easy-to-miss details called out across the individual UC topics, in one place.

Users and Scope

Assigning a user's Scope correctly up front avoids having to revisit access later — see UC Users. A Site Manager scope only functions if the user is also assigned a Site; without one, there is nothing for that scope to be limited to. Extensions are fixed once a user is created and cannot be changed afterward, so it is worth confirming the extension before saving rather than after.

Always Configure a Catch-All Time Frame

Any destination that uses time frames — a DID, an Auto Attendant, a Call Queue — should have an Always time frame configured somewhere in its routing, so a call that does not match a more specific time frame still has somewhere to go rather than failing silently. See UC Time Frames.

Conferences Have a Platform-Wide Participant Limit

Conference sessions are capped at 15 participants by default at the platform level, and there is no field on an individual conference bridge to raise this. If a bridge needs to support more participants, the NetSapiens partner responsible for the deployment should be contacted about raising the platform-level limit — see UC Conferences.

Tagging Calls for CCaaS with a Caller ID Prefix

Auto Attendants and DIDs both use the same convention to hand a call off to CCaaS: set the destination to the virtual handset extension registered to CCaaS, then enter the destination skill's name followed by a trailing slash in Caller ID Prefix (for example, Sales/). The trailing slash is what marks the value as a routing tag rather than a literal caller ID, and a matching routing rule must exist in CCaaS for the tag to resolve anywhere — see UC Auto Attendants and UC Inventory.

Call Queues Are Not CCaaS Skills

A native UC Call Queue and a CCaaS skill are separate constructs with separate agent pools and reporting. Calls intended for Contact Center agents should generally be tagged into a CCaaS skill using the Caller ID Prefix method above, rather than pointed at a UC Call Queue — see UC Call Queues.

Hover the Info Icons for the Full Picture

Several settings across the portal — a Call Queue's routing Type, its Pre Queue and In Queue Options — carry more nuance in their i-icon tooltips than is practical to fully enumerate in written documentation. When a setting's exact behavior matters, hovering the icon in the portal itself is the most reliable source.