I don't think these lines are the actual problem. I tried to get to the code that actually invokes the function in res_http_websocket to write an event to the application but couldn't exactly find it. Any ideas which `.c` files I should be looking at? -----Original Message----- From: asterisk-app-dev-bounces@xxxxxxxxxxxxxxxx [mailto:asterisk-app-dev-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Gaurav Khurana Sent: Thursday, February 22, 2018 1:29 PM To: Asterisk Application Development discussion <asterisk-app-dev@xxxxxxxxxxxxxxxx> Subject: Re: WebSockets don't work properly after upgrading from 14.7.5 to 15.2.1 [This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing] I don't see any errors as such in the two cases (1. Asterisk writes websokcet events, 2. Asterisk doesn't write any events) other than : devicestate.c: No provider found, checking channel drivers for SIP - 67.231.5.176 chan_sip.c: Checking device state for peer 67.231.5.176 devicestate.c: Changing state for SIP/67.231.5.176 - state 4 (Invalid) These are common in both the scenarios, so I don't think this should be an issue unless when in the flow this happens is a problem. I have not looked into the code yet to see what these log lines actually mean. Doing that now. -----Original Message----- From: asterisk-app-dev-bounces@xxxxxxxxxxxxxxxx [mailto:asterisk-app-dev-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Joshua Colp Sent: Thursday, February 22, 2018 10:04 AM To: asterisk-app-dev@xxxxxxxxxxxxxxxx Subject: Re: WebSockets don't work properly after upgrading from 14.7.5 to 15.2.1 On Thu, Feb 22, 2018, at 1:52 PM, Gaurav Khurana wrote: > Thanks! I tried using tcpdump and found that in the case when things > are stuck, i.e. I don’t see any requests reaching my application there > are actually no packets being issued from Asterisk. > In one of my attempts, I observed that the first call went through fine. > And, then suddenly Asterisk stopped sending any more events over the > web socket. Seems like Asterisk is getting into some weird state. I haven't seen any reports for this. One thing substantial that was changed is the underlying TCP/TLS layer went through a rewrite contributed by a community member. It's possible there's a bug in there causing it. I'd suggest turning up debug (debug in logger.conf and core set debug 9) and seeing if the messages about putting the events out appear. If so then it's likely the TCP/TLS layer. -- Joshua Colp Digium, Inc. | Senior Software Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - US Check us out at: www.digium.com & www.asterisk.org _______________________________________________ asterisk-app-dev mailing list asterisk-app-dev@xxxxxxxxxxxxxxxx http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev _______________________________________________ asterisk-app-dev mailing list asterisk-app-dev@xxxxxxxxxxxxxxxx http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev
