Tail-End-Hop-Off

[Douglas Crane]

Is it possible to get someone to round out my knowledge of this a bit?

I am looking to switch from a TSP to an ITSP. This will reduce the phone traffic costs of our company potentially by thousands of dollars a month.

I am moving from CUCM 6.1 to CUCM 8.1 on UCS. Once this is complete I plan to have AT&T switch us to their IP Flex plan.

Three questions:

1. Will it be required to have CUBE installed on my VGW in order to facilitate this switch? Also what are the requirements of the VGW for this to occur?

2. Is it possible to bind Local to my field users DID numbers to the AT&T SIP trunk? Someone mentioned to make sure they bind the current DID's I have not forward them. What does that mean exactly?

3. Is it possible to do TEHO for all calls to anywhere even if I do not have a call manger in that location given that I am technically using AT&T's call manager per say inside their network? I understand that AT&T does not have equipment in all locations so that may be a limiting factor but maybe a close proximity?

Thank you for your advice..

Sent from Cisco Technical Support iPad App

[Chris Deren]

Douglas,

Are you asking about Tail End Hop-off or centralized trunking with SIP trunks?  Those are completely different concepts. First is about routing long distance calls across voip network out of local GW as Local calls and the second basically centralizes all calls very common with SIP trunking.

Now to your questions:

1. Yes, CUBE is recommended and something required for all SIP trunk deployments

2. Yes, the buty of SIP trunks is that you are no longer tied to central office DID, you can have any area code delivered to anywhere

3. Please elaborate, if you are asking about TEHO or centralized SIP trunking and what exactly would be the requirement here.

HTH, please rate all useful posts!

Chris

[Douglas Crane]

Douglas,

Are you asking about Tail End Hop-off or centralized trunking with SIP trunks? Those are completely different concepts. First is about routing long distance calls across voip network out of local GW as Local calls and the second basically centralizes all calls very common with SIP trunking.

Now to your questions:

1. Yes, CUBE is recommended and something required for all SIP trunk deployments

2. Yes, the buty of SIP trunks is that you are no longer tied to central office DID, you can have any area code delivered to anywhere

3. Please elaborate, if you are asking about TEHO or centralized SIP trunking and what exactly would be the requirement here.

HTH, please rate all useful posts!

Chris

Thank you for your reply Chris..

I have been trying to get my hands around this concept ever since I found out about it.. I have only been into telephony for few months now so please excuse my ignorance..

1. Ok so CUBE is required as I suspected... However what if anything do I need to my VGW to prepare for that or is It simply adding a license?

2. Fantastic news!!! Exactly what I need for my field users with iPhones and a mobile app.

3. I guess I am talking about using the ip flex service or what I think you are calling centralized trunking as a means of doing TEHO to all locations that AT&T has a CO. Basically making the long distance call into a local call. Am I wrong in my thinking?

Thank you again for your help with this I have a meeting with AT&T this Tuesday about this project and you are providing valuable info for me.. Telephony service provider sales people will tell you anything to sell you something.. Although this has the potential of loosing money in this project I would imagine..

Sent from Cisco Technical Support iPad App

[Chris Deren · Accepted solution]

Douglas,

No problem, thanks for good rating. 

1. CUBE is the same hardware as VGW and can run on the same physical router, CUBE is simply configuration. It does as you point out require licenses from Cisco.

3. Well, with SIP trunking you dont get charged for long distance as with traditional circuits as the rate is typically flat. Are you planning on putting SIP trunk at 1 or 2 data centers or distributed trunking at many locations?  The first method is the more common one, but it depends on your requirements.

Agree on the Sales people, insist on talking with systems engineer who are the technical resrouces that should be able to explain to you everyting in great detail as that is their job.

HTH,

Chris