[cisco-voip] 2xBRI vs 4xFXO at remote site

[Lelio Fulgenzi]

i'm hoping if PRI's are available, BRI's are as well. but i could be reaching on that one. worse comes to worse, i can keep the PRI there and just have 4 PSTN connectivities. 

and you're talking disconnect issues on the FXO side, right? 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Cooking with unix is easy. You just sed it and forget it. 
- LFJ (with apologies to Mr. Popeil) 


----- Original Message -----
From: "Scott Voll" <svoll.voip at gmail.com> 
To: "Lelio Fulgenzi" <lelio at uoguelph.ca> 
Cc: "Cisco VoIP List" <cisco-voip at puck.nether.net> 
Sent: Thursday, March 21, 2013 3:00:33 PM 
Subject: Re: [cisco-voip] 2xBRI vs 4xFXO at remote site 


For Caller ID alone I would take the BRI over FXO. then factor in the Disconnect issues. 


Not sure if BRI is available everywhere. Might check with local Telco. 


YMMV 


Scott 



On Thu, Mar 21, 2013 at 9:45 AM, Lelio Fulgenzi < lelio at uoguelph.ca > wrote: 





Any thoughts on 2xBRI vs 4xFXO at a remote site? I'm road mapping our telephony infrastructure and would like to propose a scenario whereby we remove our PRI connectivity at the remote sites and have a few lines for emergency inbound/outbound calling. I like the simplicity of the digital PRI interfaces and I'm assuming the same would be of the BRI options. 

Experiences, good or bad, would be great to hear. 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Cooking with unix is easy. You just sed it and forget it. 
- LFJ (with apologies to Mr. Popeil) 



_______________________________________________ 
cisco-voip mailing list 
cisco-voip at puck.nether.net 
https://puck.nether.net/mailman/listinfo/cisco-voip 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130321/2320a793/attachment.html>