Changing Screening Indicator on CM (sending CID problems)

[chippowell9]

My problem: Avaya CM 6.3 CID data will not show up on several models of Verizon mobile phones. CM is reliably sending the digits.

Avaya product notice PSN020177u says this:

Name of problem:
The CID displays as “Unknown” on some calls over trunks for a specific Service Provider.

Resolution
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.

In other words, Avaya is pointing the finger at the service provider - in my case, Verizon Wireless on some models of cell phones. However, I can't replicate issue with any other PBX (Nortel, Siemens, etc.)

I don't believe I have access to modify the Screening Indicator in CM. Thoughts?

Please see attached Avaya product notice (or click here for PDF from Avaya Support).

 

[chippowell9]

Avaya product notice above did not have to do with this issue, although some symptoms were the same.

I posted this issue to a number of forums, and after several weeks with Avaya Tier 4, we found a resolution. Problem was unique to the integration of CM to CS1K, and the fix was found by a Tier 4 Avaya blue/Nortel engineer.

To recap, the CLID=Unknown issue was outbound calls from all CM phones, via CS1K PRI to PSTN, and only to Verizon cell phones, and only certain models of iOS and Android phones. For example, all Verizon iPhone 6 and 6S’s, but not 6S Plus’s. All Verizon Samsung Galaxy S6’s, but not S5’s.
Here was the fix:

• Built a CMDB table
• Added RLNO 1 (rule)
• In the RLNO: RNPI = E164 (and RTON should default to NCHG)
• In the RLB, changed CTBL to 1 in RLI 1 ENTR 0
• Add CTBL 1 to all other RLI’s and their ENTR’s.

The engineer was surprised that neither DMI nor any trunk settings failed to fix the issue. He also said that in 30 years of working on CS1K/Meridian, he’s never had to mess with CMDB tables.