Outbound Calling Integration Guide

Follow

Susan Martinez

Updated

Bandwidth has multiple geographically redundant signaling proxy facilities in the United States. The specifications below provide detail as to what should be expected.

 

SBC (Session Border Controller) IP Information

Bandwidth employs mated pairs of SBC's for signaling redundancy.  For termination services, please ensure that both IP addresses provided are configured for inbound traffic in the event that one SBC is offline.  The implementation specialist assisting with your onboarding will be providing these IP addresses during the onboarding kick-­‐off call, or via the welcome email.

 

LRN Billing

The onboarding CAM will provide a termination rate deck which will rate each termination call based on the LRN (Local Routing Number) of the dialed number. This provides a LCR (Least Cost Routing) scenario to the customer, which is only possible by the customer having the ability to perform an LRN 'dip' on each call. If this is not an option in your internal setup, please contact the onboarding CAM for assistance.

 

SIP (Session Initiation Protocol)

Bandwidth SIP signaling protocol is designed for RFC3261.  If any other method is used, calls will fail to set up.

 

Allowed Ports for Media/Audio

If a customer PBX is protected by a firewall, manufacturer compliance will need to be verified that the firewall has the ability to act as either a SIP ALG or a Back-­‐to-­‐Back User Agent (B2BUA).  The following ports are required to allow for full 2-­‐way audio:

  • UDP port 5060 – must be opened to support SIP signaling
  • UDP ports 1024-­‐64,000 – must be opened either statically or dynamically (ALG) to allow for audio path.
  • Bandwidth uses multiple IP addresses to allow media from its gateways

 

Attributes

The following attributes are allowed within Bandwidth SIP trunks:

  • DTMF
  • Dial Plans
  • Codecs
  • Signaling Protocol
  • IP Protocol
  • Media Anchoring

 

Supported DTMF

Bandwidth supports both in-­‐band and out-­‐of-­‐band DTMF outlined in RFC2833.

 

Dial Plans

Bandwidth supports E.164 for outbound calling only. This is an international recognized standard characterized by a "+" followed by the country code, then phone number.  For example:

Local & Long Distance: +19192971000

International: +4402074942020

 

IP Protocols

Bandwidth requires that all SIP and audio be delivered via UDP, in packets no larger than 1350 bytes. TCP is not supported.

 

Supported Codecs

The following codecs are supported by Bandwidth:

  • G711ulaw, G729a, ILBC (will default to ptime 30)
  • G711ulaw, G729a  (will default to ptime 20)

 

Call Concurrency Limits

Please contact the CAM to determine what the appropriate call concurrency limits are.  This will be calculated by type of traffic and expected MOU.  If a customer's call concurrency limit is reached, a 503-­‐Service Unavailable or 486-­‐Busy Here Signal message will be provided to the customer.

Redundant Capacity: Bandwidth will allocate capacity on the following Outbound Calling rate decks to allow the following decks to be capacity redundant during scheduled maintenance events: Flat Rate, Priority, Hybrid, On-Net, and Local.

Non-Redundant Capacity: Bandwidth will allocate non-redundant capacity on the following Outbound Calling rate decks: Wholesale, Carrier, and Select. (In the event of Schedule Maintenance or a service impacting event, Customer should anticipate and expect decreased capacity and route advance to other vendors).

 

Supported Caller ID / Privacy Types

  • FROM field – default option for caller ID name, number and rating.
  • RPID (Remote Party ID) – secondary option
  • P-­‐Asserted ID – supported option
  • Privacy Headers – supported option

 

 

Article is closed for comments.