We have had a Norstar Modular ICS 6.1 for nearly 20 years, with roughly the same setup.
We use loop start lines for outside connectivity, and a number of Nortel T7000 series phones on premises. For puposes of this question, we are in particular providing the POTS connectivity from a Cisco SPA 8000 analog terminal adapter, and are currently using T7316E digital telephones. But for the specific issue raised here, this exact setup has worked without issue for at least 4 or 5 years.
The problem is arising with carier/service provider implementation of STIR/SHAKEN. Our service provider is inserting a bracketed V into various SIP headers, and truncating the field to 15 characters if necessary. For example,
would become
to signal that the call is validated under the STIR/SHAKEN implementation.
For calling parties that ARE NOT validated, the Caller ID presentation at the T7316E is perfectly fine. For a calling party that IS validated, however, the caller name is presented at the T7316E as follows:
and on a further line the caller number is generally presented as normal.
My first suspicion was the ATA ... until I finally dug up a Bell JB-700 caller ID unit from the dawn of caller ID. Placing the Bell caller ID unit in parallel with the loop start line establishes that the SPA 8000 ATA is passing the entire validated caller name, i.e. [V]GREAT COMPAN between the first and second rings per standard Bell 202 protocol.
Has anyone else experienced this issue? Is there a workaround, if not a solution?
Thank you for any insight you may provide.
We use loop start lines for outside connectivity, and a number of Nortel T7000 series phones on premises. For puposes of this question, we are in particular providing the POTS connectivity from a Cisco SPA 8000 analog terminal adapter, and are currently using T7316E digital telephones. But for the specific issue raised here, this exact setup has worked without issue for at least 4 or 5 years.
The problem is arising with carier/service provider implementation of STIR/SHAKEN. Our service provider is inserting a bracketed V into various SIP headers, and truncating the field to 15 characters if necessary. For example,
GREAT COMPANY
would become
[V]GREAT COMPAN
to signal that the call is validated under the STIR/SHAKEN implementation.
For calling parties that ARE NOT validated, the Caller ID presentation at the T7316E is perfectly fine. For a calling party that IS validated, however, the caller name is presented at the T7316E as follows:
[V
and on a further line the caller number is generally presented as normal.
My first suspicion was the ATA ... until I finally dug up a Bell JB-700 caller ID unit from the dawn of caller ID. Placing the Bell caller ID unit in parallel with the loop start line establishes that the SPA 8000 ATA is passing the entire validated caller name, i.e. [V]GREAT COMPAN between the first and second rings per standard Bell 202 protocol.
Has anyone else experienced this issue? Is there a workaround, if not a solution?
Thank you for any insight you may provide.