• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2860
  • Last Modified:

AdTran 924E - Configuring to support a PRI from my carrier and breaking it up into a SIP trunk to my PBX


I have an AdTran 924E Total Access Integrated Access Device (IAD).  I want to use it to take the PRI from my carrier (voice T1) and break it up into SIP trunks for my IP-PBX.  I have been able to find many example configurations of taking in a SIP trunk from a SIP provider and delivering PRI connections to the PBX on the customer side, but I need to do the reverse:

PRI from carrier --> AdTran 924E --> Local LAN --> SIP Trunks to IP-PBX

Can anyone help with this device?  I can't find any example configurations.

  • 9
  • 6
1 Solution
I think the SIP is broken up in the DSX1 port rather than on the LAN side.(PRI handoff)
T1 type of a connection between the adtran and the IPPBX.

What timing, encapsulation does your IP-PBX support? What IP PBX is in use?
jkeegan123Author Commented:
It's an Allworx, and for PRI it is:  NI-2, B8ZS, ESF, Network for timing.

The Ad-Tran will have to accept those settings inbound.  We have a 100 number DID block that is available through the PRI as well.

I know that on PRI handoff from carrier, I have read that we need to specify USER on the T1/PRI.  Other than this, I am really not sure how to set this up.
WAN setup

interface t1 0/1
  description WAN T1
  tdm-group 1 timeslots 1-24 speed 64
  no shutdown

eth0 is your LAN port.

PRI in your case it will likely be the fifth t1 interface Four Inbound T1 and the (DSX1) the notation might not be correct.

interface t1 0/5
  description PRI T1
  tdm-group 1 timeslots 1-24 speed 64
  no shutdown
interface pri 1
  isdn name-delivery setup
  calling-party name-facility-timeout 0
  connect t1 0/5 tdm-group 1
  role network b-channel-restarts disable
  no shutdown
The below deals with establishing a channel
interface fr 1 point-to-point
  frame-relay lmi-type ansi
  max-reserved-bandwidth 90
  qos-policy out VoIP
  no shutdown
  cross-connect 1 t1 0/1 1 frame-relay 1
interface fr 1.Z point-to-point
  frame-relay interface-dlci Z
  ip address  X.X.x.x  255.255.255.X
  access-policy WAN
  crypto map sip
  media-gateway ip primary
  no lldp send-and-receive
isdn-group 1
  connect pri 1

The rest you need to get from your Data channel and then the VOIP provider.
Presumably the authentication that you need to provide deals with the SIP/Frame rather than the inbound
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

jkeegan123Author Commented:
Do I need the point-to-point in my configuration if I want to take the PRI from the provider and just let my PBX connect to the IAD for SIP trunks locally?
You have to check with your VOIP provider how the VOIPdata gets from them to the 924e
The dsx1(t1 5) is a point to point to your T1 interface on your IP PBX.

If your SIP connection established between the allworx and the remote, that all you need is the T1 for WAN and then the T1 to allworks.
PRI handoff to me means that the 924e handles everything with the provider it is terminating the WAN and the SIP trunk.
The DSX1 PRI handoff will mean that you will have 24 d channel interfaces that will be brought up as neede when calls comng in or going out.
Which allworx product do you have?
Is. The 924e part of the provider's required equipment?
jkeegan123Author Commented:
No the provider just gives me a pri framed as :ni 2, esf, b8zs, 24 channels with a 100 range did group. I want to change handoff to sip with the adtran
You need the T1 and the frame interface on the adtran as illustrated in my example.
The connection between the adtran dsx1 and a t1 port on the allworks will use the ni sip.
Check what dlci the frame has and whether you need IPSec tunnels through which the frame will go.
Do you have any support option from adtran or allworx to see whether you really need the adtran?
Usually the provider of the T1 will have the T1 frame configured.
jkeegan123Author Commented:
I don't need the adtran at all, I want to get the adtran to accept my pri so that I can break sip trunks off of the pri so that I can give sip trunks to my other pbx and the allworx. My original thought was to get the adtran to accept the pri and break it into sip trunks for both pbx's, but now I'm thinking maybe just accept the pri from the provider, give a pri to the allworx sourced from the adtran, and make sip trunks available for the second pbx... What do you think?

What's better, giving pri to the allworx or giving sip to the allworx and the other pbx? Does  the delivery options change anything?
The 924e has four incoming T1s with only one DSX1.

Not sure whether you can use one of the four T1s as a PRI handoff to the other PBX.

You do not need to split the SIP trunk.  You can split DID.
and then on the PBX's you will limit how many connection each can handle.

The 1-24 rule deals with how many SIP channels you are allocating on the connection.
You possible can use one of the four T1 to setup a PRI 2 to the second PBX

Why have multiple PBXs? you run into complexity of cross PBX communication.
jkeegan123Author Commented:
We are an integrator and we always have some kind of PBX either in the lab or on the bench getting prepped to go out.  

It would be great to be able to hand-off to the PSTN on the bench, and that's what we're aiming for.  For our own office, we only have one production PBX, the Allworx.

I think it would be best to have the incoming PRI hand off to the AdTran 924e.  I want to configure it to serve SIP TRUNKS to the local LAN and allow the Allworx to use them.  I'd also like OTHER PBX's on the LAN to be able to use the SIP trunks as well...and possibly, since it has come up, plug the DSX1 into the bench/lab PBX to test, if that PBX has PRI going into it.  We usually can't test this until we're onsite at the customer premis.

Will this device be able to have that kind of configuration?

- Accept PRI in
- Create SIP trunks for use by misc. devices
- Create DSX1 port for PBX use (probably NOT the Allworx, but being able to use it would be great)

With this configuration, would I be able to :

- Set the Allworx to use the SIP trunks for outbound and set inbound calls to go here as well?
- Set the other PBXs in the office to use the SIP trunks for outbound calling?  Would I also be able to map DID's to the other PBX that uses the SIP trunks?

I'd love an "A-Z manual" for the 924e but what I've found is how to configure it for certain situations without explanation.  I guess I really want an "AdTran 924e unleashed" guide or something...in absence of that, a config to do what I'm asking would also be great!

As for support from AdTran, their gear is supposedly lifetime warranty, so I'm sure they'll talk to me if I called during business hours, but I haven't tried that yet.
DSX1 is a T1 interface dedicated for the PRI handoff to a PBX.

You have many options.  The 924e has 4 T1 inbound DSX1 (voice Port T1 to T1 on PBX) and 24 Analog ports

You need to check with them whether one of the four T1's can be used in a similar capacity as a DSX1 which seems possible.
You can provide them with a scenario and see what they say.

The difficulty I see in your situation is that you do not have all the necessary information from the current provider.

The example I provided for the interface configuration only deal with an integrated T1 from a Provider using esf, b8zs 24 channel.
The Eth0 port is the LAN side.
The DSX1 is the PRI handoff to a PBX
the first T1 and the Frame deal with Data channel on the T1 and VOIP/SIP trunk within the frame

The frame might have to go through an IPSEC tunnel.

On site, you may have to first establish/configure the T1 WAN /eth0 LAN.
You would then need to establish the ipsec connections if any.
You would then need to configure/setup the frame interface to establish the SIP trunk.
At this point you will handoff the PRI to the PBX.
Configure the PBX to handle the DIDs
and then see whether the calls flow through and back.
jkeegan123Author Commented:
sounds like an amazingly flexible device....is there any manual that has EVERYTHING it's capable of?  I know from perusing the AdTran forums that it IS capable of handing off DSX1 to a PBX, in fact many example configs show an on-network SIP solution delivering data and SIP trunks via a T1 port over a data point-to-point connection to the provider and turning those SIP trunks into a PRI handoff to a legacy PBX.  Amazing...I think I can take my requirements to AdTran for some support, but I have this question:  Where does IPSec come into play?  Since I'm terminating on my LAN, I'd think that the PBX could connect to SIP trunks through the Ethernet interface on the LAN side, behind my firewall, since I will not be using this on the WAN except for the PRI, which is voice only.

The Frame might have to go through an ipsec channel.  It depends on your Provider's requirements.
not sure how you would overlay the T1 data with a frame otherwise.
The SIP data could be flowing through the IPSEC tunnel/s

the DSX1 is just another T1 interface.
in your case you should have a total of 5 T1 interfaces with the last one being the DSX1
You can use one of the four to be a PRI handoff to another PBX

You then should also have 24 fxs ports. (plenum to a patch block)

If you have the equipment in house to mimic a provider T1/SIP channel you can configure the backend PRI handoff to PBX.

The provider to WAN side, I think has to be done on site.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

  • 9
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now