bettybop68 / android-rcs-ims-stack

Automatically exported from code.google.com/p/android-rcs-ims-stack
0 stars 1 forks source link

When a client accepts a INVITE of forward, it does not indicate if it supports FToHTTP or GeolocPush #136

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.A stores messages for B
2.B registers
3.B receives a INVITE of forward with a GeolocPush or FToHTTP content.
4.B accepts the first. 

What is the expected output?
The 200 OK response must indicate if the client supports FToHTTP and/or 
GeolocPush through its header Contact and its SDP answer

What do you see instead?
The 200 OK response does not contains IARI tags in Contact header or 
AccpetWrappedTypes for FToHTTP, even if the client does support it.
It only indicates support for GeolocPush content in the AcceptWrappedTypes of 
SDP answer

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

Please provide any additional information below.
The .pcap file in attachment shows a INVITE forward containing a GeolocPush and 
accepted by a BlackBird user supporting FToHTTP and GeolocPush. The 200 OK 
response shows the lacks indicated before.
Filter with sip.Call-ID == "f418b882be5d54ba720cd949a13758bd@172.20.65.50"

Original issue reported on code.google.com by brochard...@gmail.com on 13 Aug 2013 at 3:28

Attachments:

GoogleCodeExporter commented 8 years ago

Original comment by jmauffret@gmail.com on 19 Aug 2013 at 12:04

GoogleCodeExporter commented 8 years ago
Correction under validation

Original comment by jmauffret@gmail.com on 27 Aug 2013 at 8:20