Hi all. We are getting our first PRI line to use with Asterisk and one of the technical specifications is about framing, structured or unstructured. The main difference about them is almost clear for me: ckp.made-it.com/g704.html says: "G.704 is the framing specification for G.703. A carrier can 'steal' a 64kbps time slot (TS0) from a 2.048 Mbps line and use this to provide timing. The result is that 31 time slots are left for data, which equals in a bandwidth of 1.984 Mbps. Normally G.703 lines with G.704 framing is called Structured G.703. Carriers offer G.704 when their network is built up on a cross-connect basis, and will offer unstructured G.703 when their infrastructure is based upon multiplexers." But, what about Asterisk and Digium TDM interface TE405/TE410 ? Does it support Structured and Unstructured framing? Which one do you recommend? Thanks in advance -- Alex G Robertson NOC - Microlink
On Tue, 11 Jan 2005, Alex G Robertson wrote:> ckp.made-it.com/g704.html says: > "G.704 is the framing specification for G.703. A carrier can 'steal' a 64kbps > time slot (TS0) from a 2.048 Mbps line and use this to provide timing. The > result is that 31 time slots are left for data, which equals in a bandwidth of > 1.984 Mbps. > > Normally G.703 lines with G.704 framing is called Structured G.703. Carriers > offer G.704 when their network is built up on a cross-connect basis, and will > offer unstructured G.703 when their infrastructure is based upon multiplexers." > > But, what about Asterisk and Digium TDM interface TE405/TE410 ? > Does it support Structured and Unstructured framing?If you ask your telco to set up an ISDN PRI they should have most of the information they need. A PRI is carried over a structured T1/E1. I don't think the Digium cards can be operated as a raw (unstructured, non-channelized) T1/E1. Peter
Possibly Parallel Threads
- [PATCH] libvirt: read disk paths from pools (RHBZ#1366049)
- [PATCH v2] libvirt: read disk paths from pools (RHBZ#1366049)
- [LLVMdev] Make LoopBase inherit from "RegionBase"?
- [PATCH 0/7] Fix SELinux security contexts so we can access shared disks (RHBZ#912499).
- [RFC] A New Divergence Analysis for LLVM