We are using HMP 3.0 on a Windows server with an Avaya PBX. We are using SIP over TCP. The thing that we are experiencing is that it looks like HMP is dropping the TCP connection after a little over a minute into the call. The impact that this is having is that we cannot do a transfer (REFER) after this connection is dropped. The drop appears to be related to timing rather than anything that is going on in the call.
Here is a look at the trace. HMP is running on 10.252.42.108. What we consistently see is a keep-alive coming from the PBX after a minute into the call. Then 4 or 5 seconds later we send a FIN, ACK, which looks like it causes the connection to close. Any ideas?
No. Time Source Destination Protocol Info |
5060 2017-02-08 17:09:09.570362 172.16.223.6 10.252.42.108 TCP 15023→5060 [SYN] Seq=0 Win=8320 Len=0 MSS=1456 WS=1 TSval=1987100114 TSecr=0 74 1 |
15023 2017-02-08 17:09:09.570596 10.252.42.108 172.16.223.6 TCP 5060→15023 [SYN, ACK] Seq=0 Ack=1 Win=8192 Len=0 MSS=1460 WS=1 TSval=623057235 TSecr=1987100114 74 2 |
5060 2017-02-08 17:09:09.573693 172.16.223.6 10.252.42.108 TCP 15023→5060 [ACK] Seq=1 Ack=1 Win=8664 Len=0 TSval=1987100115 TSecr=623057235 66 3 |
5060 2017-02-08 17:09:09.594776 172.16.223.6 10.252.42.108 TCP [TCP segment of a reassembled PDU] 314 4 |
5060 2017-02-08 17:09:09.597966 172.16.223.6 10.252.42.108 TCP [TCP segment of a reassembled PDU] 314 5 |
15023 2017-02-08 17:09:09.598013 10.252.42.108 172.16.223.6 TCP 5060→15023 [ACK] Seq=1 Ack=497 Win=32272 Len=0 TSval=623057237 TSecr=1987100119 66 6 |
5060 2017-02-08 17:09:09.601906 172.16.223.6 10.252.42.108 TCP [TCP segment of a reassembled PDU] 314 7 |
5060 2017-02-08 17:09:09.606835 172.16.223.6 10.252.42.108 TCP [TCP segment of a reassembled PDU] 314 8 |
15023 2017-02-08 17:09:09.606878 10.252.42.108 172.16.223.6 TCP 5060→15023 [ACK] Seq=1 Ack=993 Win=31776 Len=0 TSval=623057238 TSecr=1987100121 66 9 |
5060 2017-02-08 17:09:09.609806 172.16.223.6 10.252.42.108 TCP [TCP segment of a reassembled PDU] 314 10 |
5060 2017-02-08 17:09:09.612150 172.16.223.6 10.252.42.108 TCP [TCP segment of a reassembled PDU] 314 11 |
15023 2017-02-08 17:09:09.612200 10.252.42.108 172.16.223.6 TCP 5060→15023 [ACK] Seq=1 Ack=1489 Win=32768 Len=0 TSval=623057239 TSecr=1987100122 66 12 |
5060 2017-02-08 17:09:09.613508 172.16.223.6 10.252.42.108 SIP/SDP Request: INVITE sip:10259@10.252.42.108;user=phone | 178 13 |
15023 2017-02-08 17:09:09.615397 10.252.42.108 172.16.223.6 SIP Status: 180 Ringing | 611 14 |
15023 2017-02-08 17:09:09.616351 10.252.42.108 172.16.223.6 SIP/SDP Status: 200 OK | 931 15 |
5060 2017-02-08 17:09:09.622362 172.16.223.6 10.252.42.108 TCP 15023→5060 [ACK] Seq=1601 Ack=1411 Win=8047 Len=0 TSval=1987100125 TSecr=623057239 66 16 |
5060 2017-02-08 17:09:09.654144 172.16.223.6 10.252.42.108 TCP [TCP segment of a reassembled PDU] 314 17 |
5060 2017-02-08 17:09:09.656671 172.16.223.6 10.252.42.108 SIP Request: ACK sip:10259@10.252.42.108;user=phone | 258 18 |
15023 2017-02-08 17:09:09.656693 10.252.42.108 172.16.223.6 TCP 5060→15023 [ACK] Seq=1411 Ack=2041 Win=32216 Len=0 TSval=623057243 TSecr=1987100131 66 19 |
5060 2017-02-08 17:10:09.610593 172.16.223.6 10.252.42.108 TCP [TCP Keep-Alive] 15023→5060 [ACK] Seq=2040 Ack=1411 Win=8664 Len=0 60 22 |
15023 2017-02-08 17:10:09.610642 10.252.42.108 172.16.223.6 TCP [TCP Keep-Alive ACK] 5060→15023 [ACK] Seq=1411 Ack=2041 Win=32216 Len=0 TSval=623063239 TSecr=1987100131 66 23 |
15023 2017-02-08 17:10:13.658101 10.252.42.108 172.16.223.6 TCP 5060→15023 [FIN, ACK] Seq=1411 Ack=2041 Win=32216 Len=0 TSval=623063643 TSecr=1987100131 66 24 |
5060 2017-02-08 17:10:13.659248 172.16.223.6 10.252.42.108 TCP 15023→5060 [ACK] Seq=2041 Ack=1412 Win=8664 Len=0 TSval=1987112932 TSecr=623063643 66 25 |
5060 2017-02-08 17:10:13.687960 172.16.223.6 10.252.42.108 TCP 15023→5060 [FIN, ACK] Seq=2041 Ack=1412 Win=8664 Len=0 TSval=1987112938 TSecr=623063643 66 26 |
15023 2017-02-08 17:10:13.688024 10.252.42.108 172.16.223.6 TCP 5060→15023 [ACK] Seq=1412 Ack=2042 Win=32216 Len=0 TSval=623063646 TSecr=1987112938 66 27 |