Forum Discussion
Some users not obeying CsCallingLineIdentity setting
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).
- Jonas VachalNov 07, 2017Copper Contributor
Can you share your case number? We've spent another hour working on this with no resolution yet.
- Nicholas SemenkovichNov 07, 2017Brass Contributor
Our case was #6477472 (resolved only with escalation to the Skype for Business team)
- Marcel KorbeeNov 08, 2017Copper Contributor
Having the same issue but only when connecting to CellPhone numbers.... so calling to another landline works, but calling to a Cell phone number (+316********) shows the users LineUri.
- Justin KingstonNov 06, 2017Iron Contributor
Nicholas Semenkovich Still waiting to get this ticket in, but curious if the fix was tenant-wide or just specific to those affected users?
- Nicholas SemenkovichNov 06, 2017Brass Contributor
I think it was actually number (DID) specific (we'd applied the CID policy tenant-wide).
- Justin KingstonNov 01, 2017Iron Contributor
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.