CUCM SIP Trunks and XO

[libellis]

Looking at SIP Trunks (delivered via T1) from XO Communications for a new CUCM installation. Are there any technical or operational caveats or "gotchas" that we should be aware of from this particular provider? Any useful or important features they don't support that we should know about?

 

[whykap]

You are going to use a cube right?
Here's a link. havent done it with XO but this should get you 80% there if not closer

http://www.cisco.com/en/US/solutions/collateral/ns340/ns414/ns728/ns833/1169295.pdf

 

[libellis]

CUBE for sure - already in the purchase bundle - wouldn't let the Carrier handle session border control!! Thanks for the tip on the Cisco-XO application note. Our interest was in things about XO SIP Trunks that might not be immediately obvious. As an example, on a transferred Single Number Reach call that rings to a cellphone, does XO support seeing the original calling party's Caller ID, or only the transferring party's Caller ID, and things like that (we'll certainly ask about things we can think of).

I'm also curious about XO itself (we've done some homework), although I'm wary of asking because any telecom service provider will have horror stories and it's difficult to tell if that's the norm (unfortunately, it is for the big Carriers), or if I'll end up turning this post into a long venting session (whether deserved or not).