| Summary: | ASTERISK-22486: ARI: TCP Reset after 204 response | ||||
| Reporter: | David M. Lee (dlee) | Labels: | |||
| Date Opened: | 2013-09-09 14:24:40 | Date Closed: | 2013-12-24 10:45:01.000-0600 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | Resources/res_ari | ||
| Versions: | 12.0.0-alpha1 | Frequency of Occurrence | |||
| Related Issues: |
| ||||
| Environment: | Attachments: | ||||
| Description: | Here's an odd bug report regarding using the origination API (i.e. {{POST /ari/channels?endpoint=SIP%2F1000&context=internal&extension=6000&priority=1&app=test&appArgs=foobar&callerId=queuething&timeout=20}}):
bq. Another thing I noticed is that after sending back the 204/no content response, my TCP stack sends an ACK packet back, and asterisk responds with a RST, so I get an ECONNRESET error on the socket, which is weird. He's right. That's just plain weird. | ||||
| Comments: | By: David M. Lee (dlee) 2013-10-28 11:52:44.048-0500 I haven't seen this, and haven't been able to make it happen. If anyone else can reproduce with further details, please reopen. By: Matt Jordan (mjordan) 2013-12-19 13:58:25.024-0600 Reopened! | ||||