[cisco-voip] SIP Trunk Provider PRI Handoff or CUBE?

[Heim, Dennis]

As long as you don't need the SIP specific features, such as some of the redundancy, etc. The telco is giving you a PRI, if a PRI is all you need, old fashion old school, then you would be fine.

Dennis Heim
Sr. UC Engineer
World Wide Technology
Office: 314.212.1814
Email: dennis.heim at wwt.com<mailto:dennis.heim at wwt.com>
www.wwt.com<http://www.wwt.com/>

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ted Nugent
Sent: Thursday, July 26, 2012 11:57 AM
To: Cisco VoIPoE List
Subject: [cisco-voip] SIP Trunk Provider PRI Handoff or CUBE?

I received a call from a former client (I switched partners) that is migrating sites over from PRI to SIP and has an arrangement with his provider that they will provide PRI handoffs via Adtran gateways so that he does not need to purchase additional hardware or licencing. Apparently, His Cisco account team caught wind of this and told him this was against "Cisco Best Practice", that he will experience nothing but problems and needs to have CUBE in place and take SIP directly to CUBE, then proceeded to quote him $50k in upgraded routers and licensing.... This is where I got called and figured before I start up the bus and start tossing people under it I would ask you folks to see if there was anything I might be missing here? Using the PRI handofffs sound reasonable to me since there does not seem to be any compelling reason I can think of to go to CUBE in his situation.
I've seen many clients running SIP trunks with PRI handoffs for the same reasons and to my knowledge have had zero problems.... It sounds to me like it's Cisco's Year End and someone is embellishing the truth to sell unnecessary gear.... Anyone else know of any issues of terminating the SIP trunk on an Adtran and providing a PRI handoff, assuming you don't need more than the 23 channels....?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120726/a0667596/attachment.html>