[cisco-voip] Anti-Tromboning Tie Lines to PBX

[Anthony Holloway]

I think I just found a road block to using this feature in an environment
with UCCX.

According to the UCCX Release Notes, you cannot enable QSIG Path
Replacement.

*Signaling (QSIG) Path Replacement (PR).*

*This feature must be disabled when Unified CCX is deployed. To disable
this feature, set the Unified Communications Manager service parameters
Path Replacement Enabled and Path Replacement on Tromboned Calls to
False.  *

On Tue, Mar 7, 2017 at 4:54 PM Anthony Holloway <
avholloway+cisco-voip at gmail.com> wrote:

> I'm not sure how often this gets configured out in the wild, but I do know
> that there are few different flavors of this feature, depending on your
> scenario.  E.g., CUBE Media Anti-Tromboning
> <http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube/configuration/cube-book/media-path.html#concept_674530029296875008039300537109374>
>
> The one I'm interested in would involve a tie line to a legacy PBX, and
> I'm not married to the IP technology: SIP, H323, MGCP, whichever will get
> the job done.
>
> CUCM ---IP---> VGW ---T1/PRI---> PBX
>
> The call scenario I'd like to see if we can avoid is when a call is
> established from CUCM to the other PBX, and then a phone on the far side
> transfers the call to an IP Phone on the CUCM side, I'd like the PRI usage
> to drop to 0 trunks in use, instead of nailing up 2 trunks for the duration
> of that call.
>
> I'm looking for your experience and feedback in configuring
> anti-tromboning in this scenario.  One of the hardest parts in researching
> this, is knowing what terms to search for.  I think I've narrowed down the
> terminology to QSIG Path Replacement, as described in the CUCM SRND
> <http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/8_5_1/ccmsys/accm-851-cm/a08procl.html#wp1156114>
> .
>
> Though, without real-world working experience, it's hard to know if I'm
> right or not.
>
> So, I know there's some good legacy telco knowledge out on this list.
> What do you know?  Thanks!
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170321/0b9e14e6/attachment.html>