Personally, I like to continue to use PRI for customers when I can. Many PRI quotes today compete well with SIP trunks. And, many PRI's today are delivered with SIP between the IAD and the carrier. However, they manage the voice quality, and it is no longer an issue for you to have to deal with. Big Bonus from my perspective!
Patton, Audiocodes, Epygi, etc. all have Gateways that will convert that PRI to SIP reliably. As Matt states, the sipxbridge can handle that number of calls fine. You can provide some diverse routes with some SIP trunks as well. VOIP.ms, since it is a prepaid service serves nicely for International calling, and provides loss mitigation in case of being hacked. It also works well for your conference bridge for when you need a bunch of extra trunks. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Tommy Laino Sent: Tuesday, July 03, 2012 9:20 AM To: [email protected] Subject: [sipx-users] SIP Trunking Gateway I am recommending a SipX to a customer. They are going to be converting from PRI to SIP trunking. They want to have 24 trunks available for calls. I am assuming that the internal SipX bridge is not going to be sufficient for the amount of calls that they are looking to handle. I am looking for recommendations from the forum for the best way to handle all 24 SIP trunks including best hardware and SIP providers for this deployment(I have used VoIP.ms and DIDLogic in the past). Any help is greatly appreciated. -- Tommy Laino Dome Technologies _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
