Outbound ANI (Caller ID) Requirements

Quoted on this wiki

Every place a page here uses this source, in the order the words come in it.

1. A valid and in-service 10-digit number. This guideline does not include NPAs without an NXX assigned, such as those operating as a 3-digit service number (711, 911 etc.). “For a complete verification of outbound calls, check the internal logs to confirm the provided ANI adheres to the guidelines above.” Ensuring the company's adherence to these practices may help agencies, including PSAPs, emergency operations centers, and law enforcement, from encountering a block.

   In Dialer compliance controls

2. When a customer sends an outbound call INVITE, they must advertise a valid ANI (caller ID) they are calling from. Flowroute has an agreement with carriers to connect origination calls to the destination while following industry standards of operation. “A customer must utilize a valid, legitimately assigned domestic North American billing Automatic Number Identification (ANI) that’s local, and not Toll-Free.” The ANI will need to pass validation before the calls are connected with the intended destination number. Good dialing practices will allow calls to consistently reach the intended destination.

   In Local presence dialing

3. When a customer sends an outbound call INVITE, they must advertise a valid ANI (caller ID) they are calling from. Flowroute has an agreement with carriers to connect origination calls to the destination while following industry standards of operation. “The use of any invalid, inaccurate, or incorrectly formatted US billing number ANI may prevent outbound calls from connecting to the intended destination.” The ANI will need to pass validation before the calls are connected with the intended destination number. Good dialing practices will allow calls to consistently reach the intended destination.

   In Phone number validation

4. A customer must utilize a valid, legitimately assigned domestic North American billing Automatic Number Identification (ANI) that’s local, and not Toll-Free. The use of any invalid, inaccurate, or incorrectly formatted US billing number ANI may prevent outbound calls from connecting to the intended destination. Carrier involvement is due to telecommunication regulations that allow carriers to block improperly formatted or invalid ANI’s. An incorrectly formatted outbound ANI may be in a misconfigured PBX or an intentional change of the outbound ANI used to mask the call's originator. Complaints from receiving carriers are communicated back to the originating carrier which affects the origination carrier's reputation. This may impact a repeat offender's future call completion rates. “The ANI will need to pass validation before the calls are connected with the intended destination number.” A properly configured PBX will pass the ANI found in the FROM, PAI, or P-Charge-info header. The information provided in that header is confirmed with the outbound call's carrier, where the correct billing data is collected. The below guidelines should be used to help assign and properly format an ANI.

   In Phone number validation