h.323 inter-cluster trunk and RTP stream on hairpin call
The scenario: h.323 trunk between CM clusters in different states. PRI/MGCP Call arrives in cluster A, is transfered to phone in cluster B, and is then transfered back to phone in cluster A. What is the behaviour or the RTP stream between clusters? We are trying to avoid a "hairpinned" (or tromboned) call over the WAN, or at least limit the bandwidth impact.
Re: h.323 inter-cluster trunk and RTP stream on hairpin call
Is the last call flow supposed to be --> RTP Stream is from GW to Phone "A in cluster A" (If you are not using MTP in ICT in Cluster A) since the call is transfered back to phone A in cluster A from phone B in cluster B.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...