-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Outbound connection write timeout after capturing DTMF digits #20
Comments
[Update] I've tried commenting out these lines of code: Lines 123 to 125 in 6999297
and that removed the the TCP write Obviously I'm not claiming this to be a fix, so I still wonder if there is something I have done wrong that makes the code hit the deadline. |
With some further debugging I realised that I'm reusing the same context provided to the I do wonder though what is the semantical meaning of the context passed to This is where a more detailed example could really help newcommers. I wonder if this is also what caused the other issue #13 |
Hi @IvanRibakov Thanks for the report! Are you able to post your entire The 5 second timeout is for sending the Line 81 in 6999297
|
Sure, here it is: handleConnection source
The control is then passed to the CallHandler source
I understand the intention there, but I don't know how else to explain the behaviour I've been seeing. |
Thanks for sending over this additional information, I'll see if I can spot the issue going on. It may take me a bit to actually troubleshoot since I'm not with Percipia anymore but I do keep an eye on this library and help them out from time to time. If you want to help test faster, you can try this branch that disables closing on failure/no-response of the |
Hi, thanks for sharing this neat library with the community.
I've used it to create a small PoC that generates IVR menu dynamically instead of using fixed XML files, but when I got to the part where I needed to capture callers menu response I ran into an issue with the underlying TCP connection:
Here is how DTMF digit is captured:
Timeout happens on the next ESL command I try to executed after receiving the digit. Not sure if it matters, but the next command is this:
The
deflect
commmand works as expected if I comment out the "capture DTMF digits" logic, which makes me think that capturing the DTMF digit somehow affects the connection.Any ideas what might be going wrong here or if I'm missing something important?
The text was updated successfully, but these errors were encountered: