Jeffrey C. Miller dot Com

Hello All,

This is just a real quick tutorial on how to simulate a T1 connection between two Cisco routers in a lab Environment.

The fist thing you will need besides two Cisco routers is a wic-1dsu-t1. You are going to need two of these, one for each router.  Next you will need to construct a t1 crossover cable.  Below is the specs for creating one.  After you have obtained those, you will need to configure them.  There is how you do that.  Make sure that when you are making you cables that you leave that 3rd channel empty.  I have had a few occasions where the cards where triggering an alert and after about 20 min of looking over my config it turned out that I accidentally left the 3rd and 4th channel empty, so make sure you double check your cable.  Green lights on the cards mean all is good.  You should also check your config with a SHOW INT command to make sure the interface is communicating with the network.

Router A (or R1)
R1(config)# int s0/0 (this is where you plug in the location of your wic-1dsu-t1 card)
R1(config-if)#ip address 192.168.1.1 255.255.255.0 (This could be what ever you want the IP address to be)
R1(config-if)#service-module t1 framing esf (I chose ESF)
R1(config-if)#service-module t1 clock source internal
R1(config-if)#service-module t1 linecode b8zs
R1(config-if)#encapsulation ppp (I am going to use PPP)
R1(config-if)#fair-que
R1(config-if)#no shut

Router B (R2)
R2(config)# int s0/0 (this is where you plug in the location of your wic-1dsu-t1 card)
R2(config-if)#ip address 192.168.1.2 255.255.255.0 (This could be what ever you want the IP address to be)
R2(config-if)#service-module t1 framing esf
R2(config-if)#service-module t1 clock source line (notice that is is changed to line instead of internal)
R2(config-if)#service-module t1 linecode b8zs
R2(config-if)#encapsulation ppp
R2(config-if)#fair-que
R2(config-if)#no shut

Hope that helps

-Jeff

Hello All,
Before I begin this post I first want to point out that this is just my opinion.  I am not an expert on Broadvoice and by no means an expert on Trixbox.  I am just offering a few suggestions after countless attempts at trial and error on getting Trixbox to work successfully with Broadvoice, or should I say getting Broadvoice to work successfully with Trixbox.

I want to first commend Broadvoice for letting it’s customers bring their own equipment (BYOD).  I was a broadvoice customer from 2006 to 2008 (I had to get rid of them because my internet provider was constantly going out and making it unable to use).   Before going to them I was able to find very few providers that would let you user your own equipment.  I chose Broadovice because they were very reasonably priced, and if you are just looking to do some experimental VoIP in your home lab, you can get plans as cheap as $6.00 a month.  Since you are reading my post you obviously know that I chose to bring my own device, I.e. Trixbox.

I have read dozens and doznes of post, all of which offer different configurations for getting Broadvoice to work, and I have no doubt that these configs are working for some people.  It just seems to be hit or miss with most of the configs.  However, if you were like me, very few successfully worked.  With all of that being said, It is my opinion that it is not just the registration configuration needed to connect, but it is also a combination of the hardware.  I know this sounds cooky for lack of a better word, but this was my thought also.  I didn’t see why the heck hardware should play a part in a successful registration, but after countless weeks and months I finally got it working using a combination of what you would call “the right equipment.”

The configuration example I offer below has successfully registered with Broadvoice using the following; Shuttle bare bones, Dell and eMachine computers, using network cards with Realtech and Via chipsets.  I have always used a Motorola Surf Board modem, and a variety of Netgear routers.  This config has also been tested with the Linksys WRT54G router, and established a successful connection.

I understand that dozens upon dozens of people have went through countless hours trying to get a successful registration and everybody has their own configs that work for them.  I am just offering my own two cents so to speak.  This config has successfully worked for me since 2007.

So here goes.  I first want to outline some characters in the registration code.  This will act as a legend if you will.  When you see NNNNNN this is where you will insert your Broadvoice telephone number.  Just remove all the N’s and type your phone number.  PPPPP will be your password.  Just do the same.  Remove all the P’s and type your password.
Keep in mind that this is not the same password you use to access your account on the Broadvoice.com page.  This password can be found if you login to the Broadvoice portal page, go to the account link at the top of the page, and then click on “SHOW SETTINGS” link under “MY DEVICES.”  There will be a line that says auth_password.  This is the password you enter in my config in place of the P’s.

I also want to point out that I have tested this on Trixbox ver 2.6.x and 2.8.x. You should also keep in mind that if you need to change or tweak something in the registration string and you are unable to get a successful registration, try waiting a few minutes between registration tries.  I believe that Broadvoice will only allow a certain number of unsuccessful tries before they place the account is a temporary limbo.  I have had to wait a few hours in the past after a number of unsuccessful tries. Also, don’t jump the gun at changing something if it comes back unregistered, like I stated, just wait a few minutes and then go back and check the status.  This can be a tricky process for some, including myself.

Here is my Config

Outbound Caller ID: <YOURNAME>

Trunk Name: sip.broadvoice.com

PEER Details:
username=NNNNN
user=phone
type=peer
secret=PPPPP
qualify=yes
nat=yes
insecure=very
host=sip.broadvoice.com
fromuser=NNNNN
fromdomain=sip.broadvoice.com
dtmfmode=rfc2833
context=from-pstn
canreinvite=no
authname=NNNNN

Register String:

NNNNN@sip.broadvoice.com:PPPPP:NNNNN@sip.broadvoice.com

I hope this helped at least one person, and I highly encourage people to post their successful registration settings along with a list of the hardware they are using.

Thanks
-Jeff

Hello All,
Just recently as of March 10, 2012 it was brought to my attention that Broadvoice has been “re-arranging” their network for lack of a better word. I believe it entails changing some DNS servers around, so registration using Trixbox may be a little cooky. You may want to ensure that you can perform a successful NSLOOKUP for sip.broadvoice.com. If it is successful it should look like this:

[linux-box] nslookup sip.broadvoice.com
Server: 8.8.8.8
Address: 8.8.8.8#53

Non-authoritative answer:
sip.broadvoice.com canonical name = proxy.cor.broadvoice.com.
Name: proxy.cor.broadvoice.com
Address: 206.15.148.221

NOTE: the server / address will either be your ISP’s DNS server address or if you choose to use Google’s public DNS like I am.

If you still are experiencing registration issues you may want to shoot Broadvoice an email explaining in detail your situation.