User send a Refer with Refer-To:tel:+33 header after INVITE reception

vinayseasia / android-rcs-ims-stack

Automatically exported from code.google.com/p/android-rcs-ims-stack

0 stars 0 forks source link

User send a Refer with Refer-To:tel:+33 header after INVITE reception #191

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
1. A create a group chat with B and C
2. C loose connection (A and B store messages for C)
3. C become online, receive a INVITE to the conference
4. C accept the conference, and automatically send a REFER with Refer-To: 
<tel:+33>

What is the expected output? What do you see instead?
No REFER request sent

What version of the product are you using? On what operating system?
2.5.14

Please provide any additional information below.
Please contact me if you want more informations.

Original issue reported on code.google.com by rcs.capg...@gmail.com on 19 Dec 2013 at 3:46

GoogleCodeExporter commented 8 years ago

I cannot reproduce the issue.
Could you please send us some detailled traces ?

Original comment by lemordan...@gmail.com on 20 Dec 2013 at 4:24

GoogleCodeExporter commented 8 years ago

Hello,

the problem is that RI does a REFER of the user in HederFrom in the reinvite.

in trace 191_from_is_contact.pcap packet 2948 the from is : From: 
<sip:pfcf-imas-orange@g2r1as1.sims2.net>;tag=39404821_T_517d0788_T_c4a365c7-b929
-4338-a6ef-536e6643e149

its seem that the RI extract MSISDN from INVITE and REFER it if the Full Notify 
does not contains this MSISDN. In this case no MSISND so the REFER contains +33

We modify or AS in order to validate this and it has confirmed that if we put 
any msisdn in from header, the RI will try to add it with a REFER.

in

Original comment by rcs.capg...@gmail.com on 7 Jan 2014 at 2:23

Attachments:

191_from_is_contact.pcap

GoogleCodeExporter commented 8 years ago

Why do the stack send a REFER when receiving the NOTIFY full, in order to add 
the value from Header From of the ReINVITE ?

Original comment by rcs.capg...@gmail.com on 7 Jan 2014 at 2:41

GoogleCodeExporter commented 8 years ago

We cannot reproduce the issue because the store and forward feature in GC is 
not available on our platform. We will fix the issue once the SF will be 
available.

Original comment by lemordan...@gmail.com on 9 Jan 2014 at 4:26

GoogleCodeExporter commented 8 years ago

Could you please send us the logcat of the device ?

Original comment by lemordan...@gmail.com on 10 Jan 2014 at 10:06

Changed state: Accepted

GoogleCodeExporter commented 8 years ago

Here it is

on the INVITE reception
01-10 14:58:46.482: V/[RCS][ListOfParticipant](605): Add participant 
+33611223300 to the list
01-10 14:58:46.482: V/[RCS][ListOfParticipant](605): Add participant 
+33611223313 to the list
01-10 14:58:46.482: V/[RCS][ListOfParticipant](605): Add participant +33p to 
the list

Original comment by rcs.capg...@gmail.com on 10 Jan 2014 at 2:10

Attachments:

refer+33-android.txt

GoogleCodeExporter commented 8 years ago

The bug location is identified ! The RCS client is expecting a « Referred-By 
» field in the header of the SIP Re-Invite message.
I add a check to avoid adding a wrong number to the participant list.
As I cannot reproduce the test case, could you please download the sdk.zip 
available in the SVN repository and let me know if it works ?

Original comment by lemordan...@gmail.com on 10 Jan 2014 at 5:12

GoogleCodeExporter commented 8 years ago

Current SDK release is available for test purposes on the download page of the 
project site "RCS-e stack for Android platform"

Original comment by lemordan...@gmail.com on 11 Jan 2014 at 2:10

GoogleCodeExporter commented 8 years ago

Hello, with current SDK(from svn fri 13/01 18h20), no more REFER is sent.
Thank you

Original comment by rcs.capg...@gmail.com on 13 Jan 2014 at 8:11

GoogleCodeExporter commented 8 years ago

Original comment by lemordan...@gmail.com on 13 Jan 2014 at 8:13

Changed state: Verified