login | register
Mon 12 of May, 2008 [04:35 UTC]

voip-info.org

Search with Google
Search this site with Google. Results may not include recent changes.
 
Google Ads
Shoutbox
  • joe, Mon 12 of May, 2008 [04:27 UTC]: Is there an opensource browser based softphone, or a system like Busta where everything is not manages through their website?
  • Nick Barnes, Fri 09 of May, 2008 [11:36 UTC]: Christopher - yesterday I tried an Asterisk install on a CentOS 5.1 box with stock GUI and it all worked fine. Sorry I can't help.
  • aero, Fri 09 of May, 2008 [08:20 UTC]: can someone help me out on this, i tried to play some sound files on my asterisk box and this is the error message i got. WARNING[4429]: format_wav.c:169 check_header: Unexpected freqency 22050 May 8 11:17:39 WARNING[4433]: codec_gsm.c:194 gsmtolin_fra
  • Christopher Faust, Thu 08 of May, 2008 [14:15 UTC]: I beleive that I may have to change something in the xserver configuration. Please advise
  • Christopher Faust, Thu 08 of May, 2008 [14:14 UTC]: Everything was perfect. In the bios I have increased the memory allocated Still receive input not supported on my display.
  • Christopher Faust, Thu 08 of May, 2008 [14:13 UTC]: This would not be my main box. I am doing some testing to see if I can install zaptel and asterisk 1.4 on a full centos 5.1 box with development software Its bizzare, because before I went through the asterisk and zaptel installation everything was perfe
  • Nick Barnes, Thu 08 of May, 2008 [13:44 UTC]: Christopher - I can't see any way in which an Asterisk installation would muck your GUI, but remember that it is advised not to use a GUI on an Asterisk box anyway.
  • Christopher Faust, Wed 07 of May, 2008 [15:28 UTC]: When I try to startx I ge input not supported. Though before installing asterisk I had no video issue to start the GUI
  • Christopher Faust, Wed 07 of May, 2008 [15:26 UTC]: Hi Nick, I got centos 5.1 and asterisk up But now I cannot start startx I have set the depth from 24 to 16 for the video i810 driver for the i845 on my netvista machine but I cannot start GNOME. Please advise
  • Nick Barnes, Wed 07 of May, 2008 [10:01 UTC]: Howard - You'll need to provide a lot more information if you really want help.
Server Stats
  • Execution time: 0.21s
  • Memory usage: 2.21MB
  • Database queries: 29
  • GZIP: Disabled
  • Server load: 0.52

PRI

ISDN connections are delivered in two variants, PRI - Primary Rate Interface and BRI - Basic Rate Interface.

PRI is the standard for connections to offices. It's based on a T1 line in the US,
and E1 line in Europe. The T1 PRI consists of 24 channels, the E1 PRI of 32.

PRI has varying number of channels depending on the country.
In North American and Japan it's 23xB + 1xD (23 64Kbps digital channels + 1 64Kbps signalling/control channel) on a T1 1.544 Mbps
In Europe and Australia it's 30xB + 2xD on an E1 2.048 Mbps
(One timeslot on the E1 is not available for the user since it is used for internal synchronization purposes.)

PRI is also available in partial variants - ie 10xB + D.

  • Question: What about outside US and Europe - what's being used?
  • Answer: Most of the rest of the world use E1. Japan uses a variant of T1.

NFAS (Non Facility Associated Signalling) allows sharing one D channel accross multiple PRI.

As well as 'standard' signalling there are vendor specific extentions to PRI. The relevant standards include:
  • National ISDN v1 aka. NI-1
  • National ISDN v2 aka. NI-2 (see SR-4994)
  • Nortel DMS100, DMS250 (see NIS-A211-1)
  • Lucent 4ESS, 5ESS (see TR 41459)
    • some recent versions of the 5ESS support protocol extensions that Lucent recers to as Natianal ISDN v3 aka. NI-3

Troubleshooting

If you are experiencing the "0x84" problem, here is why:

If you have run into the error of: "Do not handle argument of type 0x84"

Notify your Carrier immediately that they are not correctly or that they are not currently posting CALL NAME to your PRI.

Please see: Digium Lists-Ast-2004-Oct-003790 and look for "0x84" being referred to as: #define ROSE_NAME_NOT_AVAIL

This will show that your carrier is not providing inbound Caller Name to your PRI.

This will interfere with caller name display and asterisk.

CARRIER INTER-CONNECTIONS


ISDN in the United States is a "RETAIL" tariffed service. When you go back up the food chain to the ILEC and IXC level, carriers do not inteconnect with a PRI. They use DS0 (analog trunk), DS1 (T1), DS3 (28 T1's), OC-n, and Ethernet (VOIP).

They will "sell" you a PRI, but this product is not in any of their interconnection agreements that take place between "carriers".

James Taylor
MetroTel

With many ILECs and CLECs, the same circuit is often available under multiple names and tarrifs. Many carriers charge a base rate for the DS1 circuit and additional charges per B channel or PSTN interconnect). When you order a PRI circuit, very carefully examine the different tarrifs that are available to ensure that you are getting the best circuit for your needs. It is not uncommon for a partial PRI to cost significantly more than a full PRI because of the tarrif that the provider has chosen to market agressively.


See also

Created by oej, Last modification by Jon Evans on Sun 10 of Feb, 2008 [17:25 UTC]

Comments Filter

by DS3, OC3, T1 Line on Wednesday 02 of April, 2008 [05:14:26 UTC]

by DS3, OC3, T1 Line on Wednesday 02 of April, 2008 [05:13:37 UTC]
T1 Provider, T1 Pri solutions.

by DS3, OC3, T1 Line on Wednesday 02 of April, 2008 [05:13:22 UTC]

by Jon Evans on Sunday 10 of February, 2008 [17:27:10 UTC]
I sell Voice T1' and PRI's - call me at 415-283-8613 for a price quote

Support on PRI and Bri Services

by Steve Miller on Thursday 18 of May, 2006 [18:40:24 UTC]
please go through htttp://www.astcode.com for configuration issues and support .

Please update this page with new information, just login and click on the "Edit" or "Add Comment" button above. Get a free login here: Register Thanks! - support@voip-info.org

Page Changes | Comments

Sponsored by:

Terms of Service Privacy Policy
© 2003-2008 VOIP-Info.org LLC

Powered by bitweaver