SUBSCRIBE request fails \failing to find dialog

[GoogleCodeExporter]

a) Before posting your issue you MUST answer to the questions otherwise it
will be rejected (invalid status) by us
b) Please check the issue tacker to avoid duplication
c) Please provide network capture (Wireshark) or Javascript console log
if you want quick response

What steps will reproduce the problem?
1.A calls B. after 90 sec of active conversation, the status of A changes and 
from this point on, only B can terminate the call.

2. another (maybe) related phenomenon: during an ongoing conversation, A (the 
caller) is unable to terminate the call.

3. In fact, even if the caller A terminates the call, it still rings on B's end.

What is the expected output? What do you see instead?
Attached Console log file

What version of the product are you using? On what operating system?
SIPML5 API version = 1.4.217 SIPml-api.js:1
User-Agent= Chrome/37.0.2062.120
Have WebRTC = yes SIPml-api.js:1
Have GUM = yes SIPml-api.js:1
OS: linux Debian 64 (Wheezy)
Server: kamailio (4.1.5 (x86_64/linux))
WSS

Please provide any additional information below.

1. The transport method indicates = ws while should be a wss instead. does this
make any significance?
Record-Route: <sips:192.99.32.50:5061;transport=ws;r2=on;lr>

2. SUBSCRIBE request gets: recv=SIP/2.0 404 Not Found (line 700)

Does this look like a logic \ application problem, maybe? Thank you.

Original issue reported on code.google.com by kobie.re...@gmail.com on 12 Sep 2014 at 11:48

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

You may close this issue. (missing listening port. needs two tls ports) 

Original comment by kobie.re...@gmail.com on 16 Sep 2014 at 3:49