When receiving a call the BYE never gets a 200 OK

atsakiridis commented 6 years ago

Which then seems to cause the RCDevice service to stay in the foreground forever. Investigated this and isn’t push related; it happens even if the App is in the foreground when receiving the call. Notice that this is only reproducible in cloud, not in locally installed RC

Let's ask the #support-cloud guys on this one as it's only reproducible in cloud and I don't see anything wrong with the SDK

ognjenns commented 6 years ago

I will need a help from you. Will move the ticket. and we can talk about it when you are back.

ognjenns commented 6 years ago

Disregard previous comment, I will spent more time on it and try to doit my self. Will raise a flag if I am lost again:)

atsakiridis commented 6 years ago

Ok @ognjenns, just to remind you scenario in case it helps:

Open Android Olympus
While on the foreground (remember this is not a background issue) make a call to +1235 (for example)
Before the announcement is over hang up the call from Android Olympus side Call Screen
You will see in the logs that a BYE goes out at that point, but no 200 OK response comes back from cloud for that BYE (remember this is reproducible in cloud). So right there is the issue. Although this seems harmless it causes state issues as the signaling facilities don't figure out that the call is really over.

That being said I don't think there's much you can fix on the client side as it seems like a server side issue. So this issue is more about reporting this to the support folks in #support-cloud and helping them reproduce and potentially fix it.

Let me know if it's still not clear.

ognjenns commented 6 years ago

Thats I want to discuss with you. I tried the scenario but it works now;) I have reopen it to try different scenarios to confirm. Anyhow will try and ask cloud support. Thanks for the heads up.

ognjenns commented 6 years ago

I have checked out the web version and android version and it looks ok. I will leave the ticket opened and in review state so we can check it out together. Web version:

INFO SIP message sent: BYE sip:52.55.231.191:5060;transport=tcp SIP/2.0
Via: SIP/2.0/WSS X5wNS1gWTkpK.invalid;branch=z9hG4bK-363533-a720752effbaa286ccf5c255e85a7a9c;rport
From: "ogi" <sip:ogi@cloud.restcomm.com>;tag=1514389245017
To: <sip:+1235@cloud.restcomm.com>;tag=49153067_3007639b_57a5b08a_2bab7eaa
CSeq: 3 BYE
Call-ID: 1514389243867
Max-Forwards: 70
Route: <sip:52.55.231.191:5063;transport=wss;lr;node_host=10.0.0.8;node_port=5080;version=0>,<sip:10.0.0.12:5080;transport=tcp;lr;node_host=10.0.0.8;node_port=5080;version=0>
Contact: <sip:ogi@X5wNS1gWTkpK.invalid;transport=wss>
Content-Length: 0
                                                                                    INFO SIP message received: SIP/2.0 200 OK
To: <sip:+1235@cloud.restcomm.com>;tag=49153067_3007639b_57a5b08a_2bab7eaa
Via: SIP/2.0/WSS 212.200.26.38:57521;branch=z9hG4bK-363533-a720752effbaa286ccf5c255e85a7a9c;rport=57521;received=212.200.26.38
CSeq: 3 BYE
Call-ID: 1514389243867
From: "ogi" <sip:ogi@cloud.restcomm.com>;tag=1514389245017
Server: Restcomm 8.3.0-60
Content-Length: 0

Android version:

Sending SIP request: 
BYE sip:52.55.231.191:5060;transport=tcp SIP/2.0
Via: SIP/2.0/TLS 192.168.1.31:5090
CSeq: 3 BYE
From: "ognjen.manevski" <sip:ognjen.manevski@cloud.restcomm.com>;tag=1514386401334
To: <sip:+1235@cloud.restcomm.com>;tag=43259903_426be68f_57a5b08a_3d4b3a57
Call-ID: 91ded872b7473745fa837d0f206b8d6f@192.168.1.31
Max-Forwards: 70
Route: <sip:52.55.231.191:5061;transport=tls;lr;node_host=10.0.0.17;node_port=5080;version=0>,<sip:10.0.0.12:5080;transport=tcp;lr;node_host=10.0.0.17;node_port=5080;version=0>
User-Agent: TelScale Restcomm Android Client 1.0.0-BETA6#1
Reason: SIP;cause=0;text="Normal-Hangup"
Content-Length: 0
Received SIP response: 
SIP/2.0 200 OK
To: <sip:+1235@cloud.restcomm.com>;tag=43259903_426be68f_57a5b08a_3d4b3a57
Via: SIP/2.0/TLS 192.168.1.31:5090;branch=z9hG4bK-383735-08404615b1822a0146916acff25b3f44;received=212.200.26.38;rport=44169
CSeq: 3 BYE
Call-ID: 91ded872b7473745fa837d0f206b8d6f@192.168.1.31
From: "ognjen.manevski" <sip:ognjen.manevski@cloud.restcomm.com>;tag=1514386401334
Server: Restcomm 8.3.0-60
Content-Length: 0

atsakiridis commented 6 years ago

Wow this is weird indeed; seems to be working fine. Maybe last cloud updated fixed it. Cool, will try to repro myself when I get back and we can discuss further when you get back

atsakiridis commented 6 years ago

Verified that this works fine in latest version of cloud: Restcomm 8.3.0-64 👍

Closing issue

RestComm / restcomm-android-sdk

When receiving a call the BYE never gets a 200 OK #785