<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Hi all<br>
<br>
Experiencing a commonly reported issue where calls drop out after 30 seconds or so. Mainly because the provider hangs up after not recognising/receiving ACK in response to 200 OK.<br>
<br>
Unfortunately (or maybe fortunately), I haven't had much experience with Enswitch so was hoping someone in the community might help guide me as to which rules Enswitch might be using to match ACKs to calls in progress. Maybe there is another avenue I should
be investigating.<br>
<br>
<br>
Here's a sample of the 200 OK and ACK that repeats.<br>
<br>
13:44:04.155646 IP PROVIDERIP.5060 > 172.21.0.226.5060: SIP, length: 1058<br>
E..>.M..?..Ug.v..........*J.SIP/2.0 200 OK^M<br>
Via: SIP/2.0/UDP 172.21.0.226;rport=5060;branch=z9hG4bKfe94.efbf7fbcaf8bd15243a61fdc9d6d1e78.0^M<br>
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK65f00a0c;rport=5080^M<br>
Record-Route: <sip:PROVIDERIP;lr=on>^M<br>
Record-Route: <sip:172.21.0.226;r2=on;lr=on;ftag=as65919d92;nat=yes>^M<br>
Record-Route: <sip:127.0.0.1;r2=on;lr=on;ftag=as65919d92;nat=yes>^M<br>
From: "asterisk" <sip:PROVIDERUSER@PROVIDERIP:5080>;tag=as65919d92^M<br>
To: <sip:PHONENUMBER@PROVIDERIP>;tag=as260fefaa^M<br>
Call-ID: 271ac7a174d613cd0b94504353733a2c@PROVIDERIP^M<br>
CSeq: 103 INVITE^M<br>
Server: Enswitch^M<br>
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH^M<br>
Supported: replaces^M<br>
Contact: <sip:PHONENUMBER@PROVIDERMEDIAIP:5060>^M<br>
Content-Type: application/sdp^M<br>
Content-Length: 286^M<br>
^M<br>
v=0^M<br>
o=root 2110894460 2110894461 IN IP4 PROVIDERMEDIAIP^M<br>
s=Asterisk PBX 11.3.0^M<br>
c=IN IP4 PROVIDERMEDIAIP^M<br>
t=0 0^M<br>
m=audio 15594 RTP/AVP 0 8 3 101^M<br>
a=rtpmap:0 PCMU/8000^M<br>
a=rtpmap:8 PCMA/8000^M<br>
a=rtpmap:3 GSM/8000^M<br>
a=rtpmap:101 telephone-event/8000^M<br>
a=fmtp:101 0-16^M<br>
a=ptime:20^M<br>
a=sendrecv^M<br>
<br>
13:44:04.164519 IP 172.21.0.226.5060 > PROVIDERIP.5060: SIP, length: 525<br>
E..)!A..@..v....g.v.......T.ACK sip:PHONENUMBER@PROVIDERIP:5060 SIP/2.0^M<br>
Via: SIP/2.0/UDP 172.21.0.226;branch=z9hG4bKfe94.472e9fc0479de79b4f176cc9585d8880.0^M<br>
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK752b5264;rport=5080^M<br>
Route: <sip:PROVIDERIP;lr=on>^M<br>
Max-Forwards: 69^M<br>
From: "asterisk" <sip:PROVIDERUSER@PROVIDERIP:5080>;tag=as65919d92^M<br>
To: <sip:PHONENUMBER@PROVIDERIP>;tag=as260fefaa^M<br>
Contact: <sip:PROVIDERUSER@127.0.0.1:5080>^M<br>
Call-ID: 271ac7a174d613cd0b94504353733a2c@PROVIDERIP^M<br>
CSeq: 103 ACK^M<br>
User-Agent: Elastix 3.0^M<br>
Content-Length: 0^M<br>
<br>
</div>
</body>
</html>