<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">On Thu, Feb 7, 2013 at 7:36 PM, Mimiko <span dir="ltr"><<a href="mailto:vbvbrj@gmail.com" target="_blank">vbvbrj@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
One line PRI will be connected to phone provider. Some calls to certain<br>
numbers thru this connection must be routed to FS via IP. Other<br>
destination numbers must be routed to second PRI connection for legacy<br>
PBX for analog phones. So the VoIP gateway must have two PRI (T1/E1)<br>
connections and two LAN connection for failover.<br>
<br>
After a while this VoIP gateway will be as a tehnology converter from IP<br>
to PRI. So LAN connectors will be used for connection to FS in a<br>
failover manner. And two PRI connectors will be used to connect to<br>
legacy PBX which have two PRI inputs to handle 60 concurrent connection.<br>
<br>
I've spotted three models:<br>
1) Patton SN4951/4E60V2GS/EUI 4T1/E1/PRI 60 VoIP Channels G.SHDSL for $5,000<br>
<br>
2) Audiocodes Mediant 1000 M1K-D2 2T1/E1 for $3,800<br>
<br>
3) Sangoma Vega 400 2 T1/E1 Digital Gateway for $4,437<br>
<br>
Which of this is a better working solution with failover and extended<br>
call routing plans?<br>
<br>
Thansk.<br></blockquote><div><br></div><div style>Some time ago (~2007) I used a Vega unit to connect to a Telco PRI, a PRI file transfer unit (predates broadband and FTP) and a PRI connection on a PaBX, a total of 3 PRI connections.</div>
<div style><br></div><div style>The (very basic) dialplan sent 6 DDI numbers to the ISDN file transfer box, and the rest to the PaBX, it had the capability (with an extra licence) to also add IP destinations to the dialplan, but this was of no use to us.</div>
<div style><br></div><div style>I found the UK support to be very good.</div><div style><br></div><div style>Cheers</div><div><br></div><div> </div></div></div></div>