Home > Useful Information > Outbound ANI Requirements

Outbound ANI Requirements

Flowroute provides customers with the option to purchase and use international local and toll-free inbound numbers (ITL, ITFS) in addition to domestic local and toll-free numbers. Flowroute has relationships with carriers to connect origination calls to the destination while following industry standards of operation.

When a customer makes an outbound call to an international destination, they are required to utilize a valid, legitimately-assigned domestic North American billing Automatic Number Identification (ANI) (local, not toll-free). This guideline would remain in place even if a DID purchased from Flowroute is an international local/toll-free.

The use of any invalid, inaccurate, or incorrectly formatted US billing number ANI may prevent outbound calls from connecting to their intended destination. Complaints from receiving carriers are communicated back to the originating carrier which affects origination carrier's reputation. This may impact a repeat offender's future call completion rates.

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.

The ANI will need to pass validation before the calls are connected with the intended destination number. Using good dialing practices will allow for calls to consistently reach the intended destination. Information contained in the P-Charge-info header is restricted to the needs of the carrier, and unavailable to the receiving party.

A properly configured PBX will pass the ANI found in the 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.

How to identify correct outbound ANI numbers (examples):

  • A National Number which is no less than 10 digits and prepended with the country code "1"
  • Properly formatted NPA (area code) or NXX (telephone exchange) number without a 0 or 1 as the 1st or 4th digit.
  • 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. (ie. 411, 311, 911 e.t.c.)

 

To responsibly prepare outbound calls, take some time to review the above guidelines. For a complete verification of outbound calls, check the internal logs to confirm the provided ANI is adhering to the guidelines above.

Efforts must be made to avoid blocking calls from public safety entities. Ensuring the company's adherence to these practices may help agencies, including PSAPs, emergency operations centers, and law enforcement from encountering a block.

If a business need is required to pass an international ANI on outbound calls, please contact Flowroute Customer Support, and provide that use-case. Flowroute will work with customers to verify if this is permissible and within Flowroute's control.

(if a P-Charge-info header is not found, or unable to be changed, please contact a local IT Professional to assist with specific configurations. Flowroute Customer Support is unable to directly assist in configuring any new or established PBX instances.)

Follow up Resources:

How to identify proper DID formatting:

Formatting Definitions:

SIP Understanding of ANI Formats:

ANI Definitions:

ANI Configure Example: Avaya

(third party content is not endorsed by Flowroute and does not reflect any ethics or viewpoints of F