1050132 - [Loop] The other party is not notified when the loop call is rejected

Status: VERIFIED FIXED

(Firefox OS Graveyard :: Gaia::Loop, defect)

Description

[mbarone]

Device: Flame
Mobile ID: c0243a0

As per US (https://bugzilla.mozilla.org/show_bug.cgi?id=1009886), the AC says "In case the call is rejected, the other party is notified about the rejection"

STR
1. Device B, open contact app 
2. Make a Loop call from Device A to Device B
2. Device B reject the call

ACTUAL RESULT
Device A is not notified that the call was rejected

EXPECTED RESULT
Device A should be notified that the call was rejected

Comment 1

[mbarone]

This will be also be the case if I don't answer the call during the configured answering time.

Comment 2

[Jayme Mercado [:JMercado] (Inactive 3/4/2016)]

This issue still occurs on the latest 2.0 build with the v165 KK base.  The call is ended abruptly without a notification when the call is rejected or not answered.

Environmental Variables:
Device: Flame 2.0
BuildID: 20140819030000
Gaia: 287a2c725a5c14e5dc1d48e3158ffc79c7d1ea33
Gecko: 6329352ca531b977979451e77e5862af485388b2
Version: 32.0 (2.0) 
Firmware Version: v165
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Loop version: 32219a2

Comment 3

[José Antonio Olivera Ortega [:jaoo]]

Attachment: Pointer to Github PR https://github.com/mozilla-b2g/firefoxos-loop-client/pull/105

Comment 4

[Maria Angeles Oteo (:oteo)]

Pending confirmation from Rafa about the string showed. "Call Declined", "Declined" or other...

Comment 5

[Rafael Rebolleda]

I think "Declined" is the best one; it's polite and informative, and keeping it as short as possible helps with space on localizations.

Comment 6

[José Antonio Olivera Ortega [:jaoo]]

Thanks for your massive help on debugging this.

Landed at:

https://github.com/mozilla-b2g/firefoxos-loop-client/commit/15aa2b176172af234fef38a62d41efc999612956