Hi @bogdan-iancu,
Yes, there was a connection attempt in both the failure and success cases. So
more information:
a) Curl makes a webrequest. Webservice will block until a timeout say 4s. Hence
we used async for scalability.
**Success Case:**
```
osips[6987]: RequestRoute[RT_HANDLE_PSTN_REDIRECT]: Submitting web service get
osips[6987]: NOTICE:core:io_wait_loop_epoll: EPOLLIN(read) event: epollwait()
set event EPOLLHUP - connection closed by the remote peer!
osips[6987]: ResumeRoute[RT_RESUME_AFTER_RESPONSE]: Async web service request
returned
```
**Failure Case:**
```
osips[6611]: RequestRoute[RT_HANDLE_PSTN_REDIRECT]: Submitting web service get
request
osips[6611]: NOTICE:core:io_wait_loop_epoll: connection closed by the remote
peer!
osips[6611]: ERROR:core:io_wait_loop_epoll: [UDP_worker] unexpected event 10 on
1/1, data=0x7f8bce9f3b50
osips[6611]: NOTICE:core:io_wait_loop_epoll: connection closed by the remote
peer!
osips[6611]: ERROR:core:io_wait_loop_epoll: [UDP_worker] unexpected event 10 on
1/1, data=0x7f8bce9f3b50
```
In both the cases, I verified using wireshark that the tcp connection was made
with the server and server replied back with a response:
`{"result":"timeout"}`
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/829#issuecomment-197551622_______________________________________________
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
