UPDATE after 183 Progres

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Call to IMSDroid
2.
3.

What is the expected output? What do you see instead?
Why IMSdroid answers with 183 Session in Progress where SDP has
all enabled codecs. Some Call Servers (including our Iskratel IMS core) in this 
case generates UPDATE request to the called party with only one (most prefered) 
codec in each media line.

IMSdroid do not answers such UPDATE request and the call is droped. I think 
IMSDroid do not handle UPDATE before 180 Ringing.

If terminating IMSDroid wants to publish all his capabilities, it would be 
beter to use RFC3407 sollution.  

What version of the product are you using? On what operating system?
imsdroid-1.2.353, Samsung Galaxy I9000, Android 2.2

Please provide any additional information below.

Regards

Ales

Original issue reported on code.google.com by ales.st...@gmail.com on 7 Jan 2011 at 1:31

[GoogleCodeExporter]

IMSDroid will only send 183 response if the incoming INVITE require QoS 
negotiation (preconditions) or 100rel is enabled (this is an issue). The client 
will respond to UPDATE only if QoS negotiation is enabled. Could you please 
send the network trace (wireshark)?

Original comment by boss...@yahoo.fr on 7 Jan 2011 at 4:10

• Changed state: Accepted
• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Fixed by revision 448

Original comment by boss...@yahoo.fr on 7 Aug 2011 at 4:09

• Changed state: Fixed
• Added labels: ****
• Removed labels: ****