I just got my account provisioned. Incoming works because it is sent to my IP address. I can't get outgoing to work. If someone can help and tell me exactly how it was done, please let me know.
Thanks
 
Bandwidth.com outgoing trunk help
Submitted by jades on Tue, 01/29/2008 - 10:02am.
Bandwidth.com needs "+1" + ten digits
Tue, 01/29/2008 - 11:08am
So my dial rules look like:
1408+NXXXXXX
1+NXXNXXXXXX
with an outbound dial prefix of: +
My peer details (set your own codec preferences, obviously):
allow=ulaw
disallow=g729
dtmfmode=rfc2833
host=216.82.224.202
nat=no
port=5060
type=peer
The USER context and details are blank.
I have a second trunk definition pointing to their backup server.
For my outbound routes, here are my dial patterns:
311
411
911
1800NXXXXXX
1866NXXXXXX
1877NXXXXXX
1888NXXXXXX
9011|.
9|1NXXNXXXXXX
9|NXXXXXX
NXXNXXXXXX
Rich
 
I still get all circuits are
Tue, 01/29/2008 - 11:54am
I still get all circuits are busy. Is there something else needed to be done on my end?
Thanks
 
Is it Allison who is saying
Tue, 01/29/2008 - 12:54pm
Is it Allison who is saying 'all circuits are busy' or a bandwidth.com recording?
If it's Allison perhaps the problem is in your dialplan (does debug suggest that the right trunk is being used?)
If it's a bwc recording, you should call them and make sure they are accepting calls from your tb's IP address. They should have set that up automatically when you told them where to send your calls though.
 
Allyison. I'll look into it.
Tue, 01/29/2008 - 1:37pm
Allyison. I'll look into it. Please note, I use asterisk 1.2.26 with this client. Does this mean anything?
 
Definitely tell BWC support
Tue, 01/29/2008 - 1:43pm
Definitely tell BWC support that you are using *1.2 because their default servers will have trouble with DTMF using *1.2.
However, you should still get beyond Allison's circuits busy message.
 
My sales rep told me they
Tue, 01/29/2008 - 1:48pm
My sales rep told me they captured the dtmf issue. I hope they did. One of the reasons we are switching is because of Vitelity's dtmf issues. Sometimes it works, sometimes they sound like clicks. When it works, RFC2833 works perfectly. I hope this will work with bandwidth.com
 
My sales rep told me they
Tue, 01/29/2008 - 1:50pm
My sales rep told me they captured the dtmf issue. I hope they did. One of the reasons we are switching is because of Vitelity's dtmf issues. Sometimes it works, sometimes they sound like clicks. When it works, RFC2833 works perfectly. I hope this will work with bandwidth.com
 
This blog entry sums up the
Tue, 01/29/2008 - 6:06pm
This blog entry sums up the configuration quite well.
http://mark.recek.com/2007/03/06/trixbox-sip-trunk-configuration-...
-Rick
 
Member Since:
2006-11-26