VoLTE Caller ID Fail

[rickpeay]

Call to, and forwarded to Mobile devices with advanced features (VoLTE, VoIP, etc.) see CPN (Incoming caller ID) as Unknown. Carrier's are insisting that outbound calls must have:
Address Presentation Restriction. Indicator: Presentation Allowed
and
Screening Indicator: User provided (Screen Pass) OR Network Provide.
How do I confirm this on outgoing calls?

CM R016x.03.0.124.0

[rickpeay]

Updating myself...

AT&T did ask us to set Address Pres. Restriction. Indicator: Presentation Allowed and Screening Indicator: User provided (Screen Pass) OR Network Provide... But, Avaya Product Support Notice PSN020177u sez...

"The Service Provider might claim that the Screening Indicator on CM should be changed. However, this cannot be done because it would open a security vulnerability and allow CPN (Calling Party Number) spoofing.
The Service Provider should have an element in the network that maps the Screening Indicator from the CM value to a value that the network expects.
For the iPhone 6 CID display problem, the Service Provider can disable the VoLTE service on the line as a short term fix when they are contacted. Service Providers are working on a long term fix as well."

This is a little dated (from 9-Feb-2015) so I am still looking for a fix from someone...

[zakabog]

There is no fix yet, the same thing happens on the IP Office and it's really quite frustrating. I spent hours doing ISDN traces. The carriers are getting stricter with allowing any caller ID through so now the PBX needs to set the screening indicator flag. Avaya's response is incorrect because the PBX needs to alert the carrier that the caller ID has been verified at least by the PBX, the carrier should not assume that all numbers it's being sent by the PBX are correct especially when the PBX itself is sending a flag that basically means "Here's my caller ID, I haven't confirmed this to be accurate, good luck!"

[chippowell999]

Any resolution on this?

[rickpeay]

Forwarded CPN "Unknown"

We are still experiencing this. We are in the process of moving to 100% SIP (AT&T IPflex). See attached diagram of what we were/are experiencing in the Avaya TDM Trunk environment: