Forum Discussion
Some users not obeying CsCallingLineIdentity setting
In the midst of a PBX migration to SfB Online (pure online deployment with CloudPBX); running into an odd issue;
some users (for whatever reason it seems specific to a single site currently) are not obeying outbound caller ID as defined by the CallingLineIdentity policy. Same policy (using a servicenumber substitution) is applied to approximately 80 users; 4 so far are still displaying their LineURI regardless of what CID policy is applied to the user.
I've created new policies for this site, those make no difference; I've applied CallingLineIdentity policies from other sites to these users (known good, in use policies), with no affect as well.
23 Replies
We are experience this as well. Currently have a ticket open #6721919 and are awaiting a response/escalation.
Did anyone find a resolution?
Jonas Vachal Just got a technician assigned to our ticket last night, trying to coordinate at this point.
Nicholas Semenkovich We've got 20 sites in play, so we're not doing anything CID-related at the tenant level, so curious how this plays out.
We had this exact problem as well, and could only get it resolved with a support ticket.
Were these numbers ported in? (My speculation is that this only occurs on ported numbers.)
FYI: One huge issue we ran into was ~48 hours after setting a (non-working) CsCallingLineIdentity policy -- 100% of outbound calls were rejected (until we removed the CsCallingLineIdentity).
Can you share your case number? We've spent another hour working on this with no resolution yet.
Our case was #6477472 (resolved only with escalation to the Skype for Business team)
Nicholas Semenkovich Still waiting to get this ticket in, but curious if the fix was tenant-wide or just specific to those affected users?
I think it was actually number (DID) specific (we'd applied the CID policy tenant-wide).
Service number was ported in, TNs assigned to the problem users (that I know of) are MS-native TNs.
Our other 16 sites have ported-in Service numbers with operational CID policies though, nothing different on this run than any others. I'll get a ticket going after some larger pressing issues get addressed.
