403 Forbidden in response to invite launches new registration cycle

[GoogleCodeExporter]

Steps:
1. A and B in a GC
2. A leaves the GC
3. B tries to rejoin the GC

Expected output:
AS replies 403-Forbidden with text "Forbidden user has explicitly quit the 
conference".
The client application is notified of the invitation failure with explicit 
error (indication that cause is 403-forbidden).

What we see instead:
The client application is notified of the invitation failure with error=1 
(unexpected exception).
The core initiates a new registration cycle.

Note 1: reproducible
Note 2: also occurs in case of Refer

Original issue reported on code.google.com by lemordan...@gmail.com on 7 Mar 2014 at 1:51

Attachments:

• shark_dump_1394039249.pcap