The CUCM is waiting for the far end to initiate TCS because that is how it is configured by default. As the document you reference noted, you can uncheck a box to modify this behavior.
When you insert a CUBE in the call path then you either need to: 1. Disable the wait for far end TCS option OR 2. Leverage Fast Start by forcing MTP (and adding a MRGL and choosing your fast start codec option) The CUBE doesn't initiate TCS. So, you have to leverage the CM config to accommodate the call scenario. HTH. -Bill -- William Bell, CCIE #38914 blog: http://ucguerrilla.com twitter: @ucguerrilla On Apr 14, 2013, at 8:03 PM, Barrera, Hugo wrote: > Hi Guy’s, > > Regarding the attached link, why does CUCM have to wait for the far end TCS > before it can send it’s own TCS what is the reason for this? ALSO what are > the best debugs to run when troubleshooting this?? > > https://supportforums.cisco.com/docs/DOC-2529 > > Hugo > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > Are you a CCNP or CCIE and looking for a job? Check out > www.PlatinumPlacement.com
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
