- Joined
- Mar 6, 2020
- Messages
- 68
- Reaction score
- 18
We’re seeing an audio delay issue in our Windows Server 2019 v20 U6 environment that looks like a hairpin routing problem, and I’d like to confirm if others are experiencing the same.
Scenario:
Problem:
At this point, the call is connected, but there’s a ~2.5 second audio delay in both directions. It appears the RTP stream is being hairpinned through the Remote Office instead of re-anchoring locally at HQ.
Observations:
Scenario:
- A local caller dials into our HQ office (3CX server on-premise).
- The call is diverted over a 3CX Tunnel to our Remote Office (also running 3CX on prem), where the call is answered. Both are v20U6.
- The caller then asks to be transferred back to someone at HQ.
- The Remote Office transfers the call back to HQ (same 3CX server that originally received the inbound call).
Problem:
At this point, the call is connected, but there’s a ~2.5 second audio delay in both directions. It appears the RTP stream is being hairpinned through the Remote Office instead of re-anchoring locally at HQ.
Observations:
- In older versions of 3CX, there were SIP trunk and extension options such as Supports Re-Invite, Supports Replaces, and Allow direct media over tunnel that could be toggled to resolve these kinds of media path issues.
- In v20 U6, those options no longer exist in the Management Console, at least I can't find them
- "PBX Delivers Audio" is set on all extensions as we record calls.
- Is this expected behavior with v20 U6?
- Without the direct media / re-invite settings, what is the recommended way to prevent HQ ↔ Remote Office ↔ HQ audio hairpinning that introduces this delay?