Ryan Cavanaugh
2005-Jan-28 19:16 UTC
[Asterisk-Users] Nortel --> Asterisk-------->Asterisk
I am looking at setting up the following configuration and any help/input/comments before signing the PRI contracts will be greatly appreciated. PRI Tampa PRI Sarasota PRI <--> Nortel BCM-->Asterisk<------------------>Asterisk<---> I would like to link the Nortel BCM to * using the a digital trunk card. The BCM will continue to service the Tampa location, the * box would simply be used to pass extensions over the PRI to another * server in Sarasota and for a few SIP clients in other locations. Both servers will require two T100P cards. The Tampa server requiring one for communication with the BCM and one for the PRI to Sarasota. The Sarasota server will have one for communicating with the PRI to Tampa and one for accessing the PRI for local lines. I really could do away with the * server in Tampa but I figured with an * solution being so much cheaper then another proprietary system the added redundancy for any SIP clients would be worth the extra money, plus Tampa has twice the data rate capacity of Sarasota already. I am really looking to achieve the following: 1. Reliability 2. Call quality 3. Cost effectiveness 4. Redundancy Thank you in advance for your input. Best Regards, Ryan
Jim Van Meggelen
2005-Jan-29 08:51 UTC
[Asterisk-Users] Nortel --> Asterisk-------->Asterisk
asterisk-users-bounces@lists.digium.com wrote:> I am looking at setting up the following configuration and any > help/input/comments before signing the PRI contracts will be greatly > appreciated. > > PRI Tampa PRI > Sarasota PRI > <--> Nortel BCM-->Asterisk<------------------>Asterisk<---> > > I would like to link the Nortel BCM to * using the a digital > trunk card.Your diagram is a bit confusing to me. Still, the use of PRI in the BCM is a good plan. You've avoided using the highly unstable VoIP functions in the BCM. PRI support on the BCM is based on the Norstar architecture, which is very stable. So that basic design philosophy should serve you well.> The BCM will continue to service the Tampa location, the * box would > simply be used to pass extensions over the PRI to another * server in > Sarasota and for a few SIP clients in other locations. Both > servers will > require two T100P cards. The Tampa server requiring one for > communication with the BCM and one for the PRI to Sarasota. > The Sarasota > server will have one for communicating with the PRI to Tampa > and one for > accessing the PRI for local lines.That should work well. One thing you may want to consider is fronting the BCM with the Asterisk, as the Asterisk dial plan is far more flexible.> I really could do away with the * server in Tampa but I > figured with an > * solution being so much cheaper then another proprietary system the > added redundancy for any SIP clients would be worth the extra money,Never mind the money, Asterisk is technically superior to the BCM in every way on the VoIP and OS side of things. The only place the BCM might be able to argue a slight advantage is the wealth of key system features it offers on its sets. Whatever you do, avoid using the BCM for VoIP - you *will* regret it. Bottom line? The BCM has a limited future, whereas Asterisk *is* the future!> plus Tampa has twice the data rate capacity of Sarasota already. > > I am really looking to achieve the following: > 1. ReliabilityAsterisk - BCM is famously unstable (as is its operating system - Windows NT4.0).> 2. Call qualityThe BCM may offer a slight advantage on the legacy links, but Asterisk is no slouch in this regard.> 3. Cost effectivenessAsterisk - The BCM is closed, obsolete and expensive> 4. RedundancyAsterisk - Linux has far more redundancy options than BCM ever will.> Thank you in advance for your input.Good luck. -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.2 - Release Date: 28/01/2005
Andrew Kohlsmith
2005-Jan-29 09:01 UTC
[Asterisk-Users] Nortel --> Asterisk-------->Asterisk
On January 28, 2005 09:16 pm, Ryan Cavanaugh wrote:> I would like to link the Nortel BCM to * using the a digital trunk card. > The BCM will continue to service the Tampa location, the * box would > simply be used to pass extensions over the PRI to another * server in > Sarasota and for a few SIP clients in other locations. Both servers will > require two T100P cards. The Tampa server requiring one for > communication with the BCM and one for the PRI to Sarasota. The Sarasota > server will have one for communicating with the PRI to Tampa and one for > accessing the PRI for local lines.I don't use a BCM, but I have a Norstar MICS interfaced to * through a DTI card + PRI enabler. I'm currently gearing up to reverse engineer the MCDN (SL1) protocol that Norstar uses to communicate between Norstar boxes and do things such as centralized voicemail and the like. Every call we have goes through Asterisk -- it's been this way for the past year and, barring stupid mistakes of my own doing, it has worked flawlessly.> I am really looking to achieve the following: > 1. Reliability > 2. Call quality > 3. Cost effectiveness > 4. RedundancyOne through three are serviced famously by asterisk. All my voice calls use the GSM codec and I've not had one complaint. Whenever I try to use iLBC I get call quality complaints, even though the system is more than powerful enough to handle our call volumes with iLBC. I'd like to give g729 a shot and see how that works, too. Number four can only be handled as well as you set it up -- By this I mean you can certainly have a decent asterisk box with redundant power supplies, RAID1 (software RAID1 on IDE works just fine here, no need to use a proprietary hardware SCSI RAID1 implementation), multiple ethernet links and the like but remember that the BCM has only one power supply and only one T1 -- let's not go crazy with the redundancy here. :-) -A.