Hi James, I've trimmed the thread down, well, completely. ^_^
From looking at your information and reading the code it looks as though there is a case where this may occur if certain NAT options are enabled. This is certainly a bug as the code should just not execute when WebSocket is involved. For an immediate fix you can set nat=no in the entry in sip.conf. This should change the result and would also explain why this has not been seen by others.
-- Joshua Colp Digium, Inc. | Software Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: www.digium.com & www.asterisk.org -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
