X-Lite 5 drops call when music on hold applied

[scottsimcock]

When I'm using X-Lite, and I'm getting the same problem on X-Lite 3, 4 and 5, if I apply music on hold from the remote end X-Lite doesn't respond to the re-INVITEs sent to it to apply the music after repsonding to the re-INVITE to apply hold (silence). Using another ip endpoint, or when hold is applied in X-Lite directly, call flow works perfectly.

X-Lite on 5060, Proxy A - 5050, Proxy B - 5065, Media Server - 5095

Here's the INVITE the SIP Proxy is forwarding to X-Lite:
INVITE sip:5551212@192.168.1.199:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.199:5050;branch=z9hG4bK-A415E2453FFCD01;rport
Via: SIP/2.0/UDP 192.168.1.199:5065;branch=z9hG4bKA34F1F5C-DE02-415F-B6E2-EE2F97ADE0E2-76;received=192.168.1.199
From: "x6001"<sip:6001@192.168.1.199:5050>;tag=05ED4CFD-DE23-4FF7-AF75-7088FEE67EF0-20
To: "Bob Duck"<sip:5551212@192.168.1.199:5050>;tag=f286dedd
Call-ID: NzdkYjZjYTFlMTdmMmJkMmI5MTVhNjM3OWRlNzU0Njk.
CSeq: 2 INVITE
Contact: <sip:192.168.1.199:5065>
Allow: INVITE, ACK, PRACK, CANCEL, BYE, REFER, INFO, UPDATE, MESSAGE, NOTIFY, OPTIONS
X-Genesys-CallUUID: RKGATJUQM93UD37T4QDT3D0MSK000006
Max-Forwards: 68
Session-Expires: 1800;refresher=uac
Min-SE: 90
Supported: timer
Record-Route: <sip:192.168.1.199:5050;lr>
Content-Type: application/sdp
Content-Length: 1324

v=0
o=- 1342488105 3 IN IP4 192.168.1.199
s=phone-call
c=IN IP4 192.168.1.199
t=0 0
m=audio 20024 RTP/AVP 0 8 2 3 101
a=sendrecv
a=rtpmap:0 pcmu/8000
a=rtpmap:8 pcma/8000
a=rtpmap:2 g726-32/8000
a=rtpmap:3 gsm/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
m=video 20026 RTP/AVP 34 99 113 114 115 116 117 118 119 120
a=sendrecv
a=rtpmap:34 h263/90000
a=rtpmap:99 h263-1998/90000
a=rtpmap:113 h264/90000
a=fmtp:113 profile-level-id=42000B; packetization-mode=0; use-level-src-parameter-sets=0
a=rtpmap:114 h264/90000
a=fmtp:114 profile-level-id=42000B; packetization-mode=1; use-level-src-parameter-sets=0
a=rtpmap:115 h264/90000
a=fmtp:115 profile-level-id=42400B; packetization-mode=0; use-level-src-parameter-sets=0
a=rtpmap:116 h264/90000
a=fmtp:116 profile-level-id=42400B; packetization-mode=1; use-level-src-parameter-sets=0
a=rtpmap:117 h264/90000
a=fmtp:117 profile-level-id=4D000B; packetization-mode=0; use-level-src-parameter-sets=0
a=rtpmap:118 h264/90000
a=fmtp:118 profile-level-id=4D000B; packetization-mode=1; use-level-src-parameter-sets=0
a=rtpmap:119 h264/90000
a=fmtp:119 profile-level-id=58000B; packetization-mode=0; use-level-src-parameter-sets=0
a=rtpmap:120 h264/90000
a=fmtp:120 profile-level-id=58000B; packetization-mode=1; use-level-src-parameter-sets=0

The only thing at the same time in the X-Lite log is this:
[12-07-16]18:38:00.282 | 832 | Debug | Resip | "RESIP:TRANSPORT:incoming from: [ V4 192.168.1.199:5050 UDP target domain=unspecified mFlowKey=1732 ]" |

Which is normally followed by the details of the SIP message, but in this case, no other messages. Which looks to me like X-Lite is getting the INVITE, but not processing it.

[CPBob]

Hello,

Please post the SIP invite and the corresponding SIP 200OK response for the call setup, as well as, for the call holds (both Invites and 200 OKs). It will help us in our investigation.

Thank you.

[News4la]

Try getting rid of SIP keep alive