Administering Verizon ANI feature

Last Updated : Sep 07, 2016 |

Procedure

  1. On the Adaptation Details page, administer the Module name field as VerizonAdapter so that the adaptation can be associated with the Verizon Adapter.
  2. In the Digit Conversion for Outgoing Calls from SM section,
    1. Enter one or more Matching Patterns that are to be used to identify which origination numbers (PAI) are associated with a given physical location.
    2. Enter the Screened Telephone Number (STN) that corresponds with that location in the Adaptation Data field.

    When the Verizon Adapter processes an egress call, the PAI number associated with the call is compared with the various Matching Patterns administered in the Digit Conversion for Outgoing Calls from SM section. In addition, the domain of the PAI should be an SM authoritative domain.

    • If there is a match, the data administered in the Adaptation Data field is incorporated into the Diversion header for that call and the call continues with its normal routing procedures.

    • If there is no match, the system continues to function as per design.

    Note:

    • If a match occurs on a row with STN filled-in then the History-Info to Diversion header conversion is not done by VerizonAdapter since either a STN or the converted History-Info can be inserted into the Diversion header. So effectively the STN takes precedence in such cases.

    • Address to modify field must be set to origination or both for STN feature to work. Session Manager does not populate STN into the Diversion header on a destination address match.

    • If no digit conversion is to be done (that is, matching pattern is there only to specify the STN), then the user should set Delete Digits field to 0 and leave Insert Digits field as blank.