login | register
Wed 01 of Aug, 2007 [09:23 UTC]

voip-info.org

Search with Google
Search this site with Google. Results may not include recent changes.

Web www.voip-info.org
Shoutbox
  • Aykut, Wed 01 of Aug, 2007 [07:53 UTC]: Hi all, does anybody know about Thomson ST2030 SIP phone. I have upgraded it to latest version (1.56) but "Hold" and "Conf" features are not working after the upgrade ?? Do you know any solution or do you have Ver. 1.52 ?? Where can I find it?
  • Edward J Brown, Tue 31 of Jul, 2007 [23:33 UTC]: Has anybody experienced Choppy voice quality when using a Linksys SPA942 in an Asterisk Conference bridge? It works fine with my polycom and Cisco, but sucks with my Linksys.
  • www.astawerks.com, Fri 27 of Jul, 2007 [18:00 UTC]: does anyone use asterisk on top of clark connect? does it work good?
  • simon, Fri 27 of Jul, 2007 [14:16 UTC]: Hi All, Has anyone here managed to get the Cisco79x1 to successfully fail over to the backup proxy. I have 2 asterisk servers , handsets all register and function, except that backup proxy function doesn't work. Any working example would be very apprecia
  • Matthew Richmond, Thu 26 of Jul, 2007 [03:40 UTC]: using the page() application to page across our building...often the meetme conferences don't disconnect after the caller hangs up. Anyone else having this problem. (using Polycom phones)
  • Matthew Richmond, Wed 25 of Jul, 2007 [02:58 UTC]: thanks Nicholas Blasgen! I haven't worked with AGI before, but there's always a first! Thanks again!
  • Nicholas Blasgen, Tue 24 of Jul, 2007 [19:18 UTC]: Matthew Richmond, AGI will handle all that for you.
  • sam, Mon 23 of Jul, 2007 [16:39 UTC]: need help - certain voicemail extension will stop working and recording voicemail on asterisk - anyone know why and how to fix it? Thanks
  • john haji, Mon 23 of Jul, 2007 [14:55 UTC]: free calls to pakistan
  • bong, Sat 21 of Jul, 2007 [19:09 UTC]: hi good day to all can anyone help me how to configured the nortel sip to the signaling server and how to activate in mobile w/ sip compatible without mcs
Server Stats
  • Execution time: 0.40s
  • Memory usage: 2.20MB
  • Database queries: 33
  • GZIP: Disabled
  • Server load: 3.12

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 Paul Gillman on Fri 25 of May, 2007 [13:32 UTC]

Comments Filter

by Jon Evans on Monday 19 of June, 2006 [20:29:33 UTC]
XO offers T1/PRI and a Flex integrated PRI circuit -no charge for local/long distance/Toll free- http://www.voip-info.org/users/index.php?home=lejoneric

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-2007 Arte Marketing, Inc.

Powered by bitweaver