Bandwidth.com

From Taridium

(Difference between revisions)
Jump to: navigation, search
(→Prerequisites)
Line 78: Line 78:
Enter your DIDs as specified by bandwidth.com e.g. +12125552200 and select a local destination for your DID.
Enter your DIDs as specified by bandwidth.com e.g. +12125552200 and select a local destination for your DID.
 +
 +
== Testing ==
 +
 +
Remember that Bandwidth.com wants to see a '''+''' and a '''1''' on all outgoing calls, so this must be planned for in the Trunk and Outbound Routing and Transformations. Also, we will be sending you a '''+''' and a '''1''' on every call, so make sure to plan for this when setting up your ipbx system.
 +
 +
* Operator must be sent as a plain 0 (no 1)
 +
* 911 must be sent as 911
 +
* 411 must be sent as 411
 +
* International calls are to be sent without 011. Example: +442151245
 +
* Local and Long Distance Calls; Example: +19192971100
 +
 +
'''Test Plans'''
 +
 +
If you run into an issue with any of these tests, consult the troubleshooting chart bellow:
 +
 +
# Test an Outbound call to a Local Number. Check for Ringback, 2-way Audio, and Quality.
 +
# Test an Outbound call to a Long Distance Number. Check for Ringback, 2-way Audio, and Quality.
 +
# Test an Outbound call to an International Number. Check for Ringback, 2-way Audio, and Quality.
 +
# Test a Long Outbound call past 15 minutes.
 +
# Test multiple call concurrencies on Outbound calls. Setup multiple calls to [[wikipedia:PSTN|PSTN]]
 +
# Test an Outbound Call to Operator '''0'''
 +
# Test an Outbound Call to Directory Assistance '''411'''
 +
# Test a 911 Call ([[Image:warning.gif]] PLEASE IDENTIFY TO THE OPERATOR THAT THIS IS A TEST!)
 +
# Test an Inbound call to one of your DIDs. Check for Ringback, 2-way Audio, and Quality.
 +
# Test an Inbound call to an IVR. Check [[wikipedia:DTMF|DTMF]] and Audio Quality.
 +
# Test Transferring calls off-site.
 +
# Test an Outbound call to an Auto-Attendant and verify [[wikipedia:DTMF|DTMF]].

Revision as of 15:39, 25 February 2009

Bandwidth.gif

This page describes how to configure your Taridium ipbx system with Bandwidth.com SIP Trunking Service.

Contents

Prerequisites

Completely installed ipbx System

If you have obtained your ipbx system directly from Taridium and have a valid maintenance or managed VoIP service contract, you can ask Taridium to perform this configuration for you. In order for you to configure your trunk you should have your phones, IVRs, call groups, queues etc. already setup. See Installing ipbx and Initial_Configuration|Initial Configuration]].

Version Check

Warning.gif Bandwidth.com trunks require ipbx v. 2.0.1 or higher for proper operation.

SIP trunking information provided by Bandwidth.com

Trunk Configuration

Navigate and login to the ipbx administrator interface (you will need admin class permissions). E.g.

http://[ip address of your pbx]/ipbx/

Click on Configuration → VoIP Trunks → add SIP Trunk

Enter the following details:

  1. Trunk Name → bandwidth-1
  2. Type → friend
  3. Host → 216.82.225.202
  4. Context → incoming (default)
  5. Can Re-Invite → no
  6. Insecure → very
  7. Disallow → all (enter or select all)
  8. Allow → ulaw (enter or select ulaw)

Leave all other configuration details as per default.

Bw-trunk.gif

Click on add trunk to add your trunk to the configuration.

Click on Configuration → Routing → Outbound Routing

Enter your destination patterns and select the newly created SIP/bandwidth-1 trunk to terminate your calls.

Examples destination pattern:

_+ZXXXXXX. This will accept any numbers that match the E.164 pattern and send them to bandwidth.com

Bw-outbound.gif

Transformation Configuration

Since bandwidth.com requires numbers to be dialed as fully qualified E.164 numbers you will need to add number transformations before sending your calls out.

Click on Configuration → Routing → Transformations

Add a new rule of type before outbound routing with Pattern _1NXXNXXXXXX and Output +${EXTEN} - This rule will transform any North American numbers to E.164.

Add a new rule of type before outbound routing with Pattern _011ZXXXXX. and Output +${EXTEN:3} - This rule will transform any international prefix numbers to an E.164 pattern.

Bw-transform.gif

If desired you can also add inbound transformations before inbound routing which for example could strip the + sign for further matching in your inbound routes.

DID Configuration

In order for ipbx to know about your DIDs, you will have to add inbound routes:

Click on Configuration → Routing → Inbound Routing

Bw-inbound.gif

Enter your DIDs as specified by bandwidth.com e.g. +12125552200 and select a local destination for your DID.

Testing

Remember that Bandwidth.com wants to see a + and a 1 on all outgoing calls, so this must be planned for in the Trunk and Outbound Routing and Transformations. Also, we will be sending you a + and a 1 on every call, so make sure to plan for this when setting up your ipbx system.

Test Plans

If you run into an issue with any of these tests, consult the troubleshooting chart bellow:

  1. Test an Outbound call to a Local Number. Check for Ringback, 2-way Audio, and Quality.
  2. Test an Outbound call to a Long Distance Number. Check for Ringback, 2-way Audio, and Quality.
  3. Test an Outbound call to an International Number. Check for Ringback, 2-way Audio, and Quality.
  4. Test a Long Outbound call past 15 minutes.
  5. Test multiple call concurrencies on Outbound calls. Setup multiple calls to PSTN
  6. Test an Outbound Call to Operator 0
  7. Test an Outbound Call to Directory Assistance 411
  8. Test a 911 Call (Warning.gif PLEASE IDENTIFY TO THE OPERATOR THAT THIS IS A TEST!)
  9. Test an Inbound call to one of your DIDs. Check for Ringback, 2-way Audio, and Quality.
  10. Test an Inbound call to an IVR. Check DTMF and Audio Quality.
  11. Test Transferring calls off-site.
  12. Test an Outbound call to an Auto-Attendant and verify DTMF.
Retrieved from "https://wiki.taridium.com/Bandwidth.com"
Personal tools
Namespaces
Variants
Actions
Toolbox