CharlieParker Posted April 30, 2012 Report Share Posted April 30, 2012 I have an IVR node with a SOAP URL that works fine with 4.2.1.4025 but when I use 4.5.0.1050 I see this in the log. [5] 2012/04/30 11:09:25: Could not send 555 bytes to 10.2.3.4, error code 57 and a minute later [4] 2012/04/30 11:10:25: HTTP client: Timeout on 10.2.3.4:8080 On the webserver I only see the request several minutes later and if I call the IVR 3 times in a row on the webserver the 3 request all come at the same time. Ideas? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted April 30, 2012 Report Share Posted April 30, 2012 Try to whitelist 10.2.3.4, maybe we are in trouble with the automatic blacklisting here. Quote Link to comment Share on other sites More sharing options...
pbx support Posted April 30, 2012 Report Share Posted April 30, 2012 The timeout means PBX could not connect to the server on 10.2.3.4:8080. Set the log level to 8 (Web Client) and you should see bit more information that can help us see what is going on. Quote Link to comment Share on other sites More sharing options...
CharlieParker Posted April 30, 2012 Author Report Share Posted April 30, 2012 The timeout means PBX could not connect to the server on 10.2.3.4:8080. Set the log level to 8 (Web Client) and you should see bit more information that can help us see what is going on. 1 more line: [8] 2012/04/30 12:56:53: HTTP client: Connect to 10.2.3.4:8080, pending requests 0 [5] 2012/04/30 12:56:53: Could not send 555 bytes to 10.2.3.4, error code 57 [4] 2012/04/30 12:57:53: HTTP client: Timeout on 10.2.3.4:8080 [3] 2012/04/30 12:57:53: IVR Node: Received http code 0 Whitelist, Settings/Access and add an allow entry? Did that, same results. Also same results when trying a different URL on different server, which also worked with 4.2. Messing around with the time out and different lengths of the message I just had it working but a few minutes later I can't recreate. This is what I have/want: No wav file DTMF Match List:!T!310! Timeout: 0 Quote Link to comment Share on other sites More sharing options...
pbx support Posted April 30, 2012 Report Share Posted April 30, 2012 Not sure which OS you are on. But sometimes the firewalls, do not like it when the executable is changed. May be some issue with the outbound rules? Quote Link to comment Share on other sites More sharing options...
CharlieParker Posted May 1, 2012 Author Report Share Posted May 1, 2012 Not sure which OS you are on. But sometimes the firewalls, do not like it when the executable is changed. May be some issue with the outbound rules? I'm on OS X with no software firewall. I'm not seeing any TCP traffic on port 8080 on the snomONE machine or the web server (different machines). It seems to me that the PBX is timing out because it never made the http request. It works occasionally, usually 3 times in a row but I can't reliably reproduce it. When it does work I see the TCP traffic as expected. Quote Link to comment Share on other sites More sharing options...
pbx support Posted May 1, 2012 Report Share Posted May 1, 2012 Error code seems to be related to "Socket is not connected". PBX tries to connect to 10.2.3.4:8080 first before sending the data. Possibly, it is taking more time to connect to 10.2.3.4:8080. Does the server on the 10.2.3.4:8080 accept connections without any delay? Quote Link to comment Share on other sites More sharing options...
CharlieParker Posted May 1, 2012 Author Report Share Posted May 1, 2012 Error code seems to be related to "Socket is not connected". PBX tries to connect to 10.2.3.4:8080 first before sending the data. Possibly, it is taking more time to connect to 10.2.3.4:8080. Does the server on the 10.2.3.4:8080 accept connections without any delay? As far as I call tell there is no delay. I'm suspecting something went wrong with the update, now 2 users mentioned transfers disconecting calls. Going from 4.2 to 4.5 nothing other than the binary needs to be changed, right? Quote Link to comment Share on other sites More sharing options...
CharlieParker Posted May 1, 2012 Author Report Share Posted May 1, 2012 As far as I call tell there is no delay. I'm suspecting something went wrong with the update, now 2 users mentioned transfers disconecting calls. Going from 4.2 to 4.5 nothing other than the binary needs to be changed, right? It (IVR/SOAP) works fine with pbxctrl-darwin9.0-2011-4.5.0.1016 but not with 1030 or 1050. I got more reports of 4.5.0.1050 disconnecting transfers, I've reverted to 4.2.1.4025. Quote Link to comment Share on other sites More sharing options...
CharlieParker Posted May 3, 2012 Author Report Share Posted May 3, 2012 I created 2 test installations of snomONE under OS X and 1 under Linux. Both OS X installs exhibited the behavior eventually (anywhere from 3 to 10 calls to the IVR after starting up). I couldn't make it happen with Linux. Good, come right back with the destination [8] 20120503160559: Call from an user 509 [8] 20120503160559: To user 500 [8] 20120503160559: Call state for call object 51: idle [8] 20120503160559: Call state for call object 51: connected [5] 20120503160559: set codec: codec pcmu/8000 is set to call-leg 50 [5] 20120503160559: Last message repeated 3 times [8] 20120503160559: HTTP client: Connect to 10.89.20.90:80, pending requests 0 [8] 20120503160559: Received response code 200 with destination 512 Bad, comes right back with the error 57, also note the error 60, doesn't always happen right before a 57 [8] 20120503160614: Call from an user 509 [8] 20120503160614: To user 500 [8] 20120503160614: Call state for call object 52: idle [8] 20120503160615: Call state for call object 52: connected [4] 20120503160615: select returns error 60 (rtp) [5] 20120503160615: set codec: codec pcmu/8000 is set to call-leg 51 [5] 20120503160615: Last message repeated 3 times [8] 20120503160615: HTTP client: Connect to 10.89.20.90:80, pending requests 0 [5] 20120503160615: Could not send 535 bytes to 10.89.20.90, error code 57 Quote Link to comment Share on other sites More sharing options...
pbx support Posted May 4, 2012 Report Share Posted May 4, 2012 Looking at the error codes from http://developer.apple.com/library/ios/#DOCUMENTATION/System/Conceptual/ManPages_iPhoneOS/man2/intro.2.html, the 60 is for timeout. I assume, because of that the send is failing. May be something else is happening (something with RTP). We will check it out. Quote Link to comment Share on other sites More sharing options...
CharlieParker Posted May 21, 2012 Author Report Share Posted May 21, 2012 I'm no longer seeing the error 57 when using 4.5.0.1075 Delta Aurigids (MacOS). I still frequently see error 60 but it doesn't seem to be causing any troubles. (I've had one blind transfer fail that I think should not have, I monitor that.) Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.