Registration to Open-IMS fails with 401

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Register to Open-IMS with the same settings as Mercuro
(Tried both with MD5 and AKAv1-MD5 set in Open-IMS side) 
2. After the second REGISTER (response to challenge), 401 Unauthorized - 
Challenging the UE is received 

What is the expected output? What do you see instead?
401 Unauthorized - Challenging the UE instead of 200 OK

What version of the product are you using? On what operating system?
ImsDroid Rev. 28, Android emulator, v 2.1, Open-IMS on Ubuntu

Wireshark flow attached

Original issue reported on code.google.com by darva...@gmail.com on 16 Jun 2010 at 9:23

Attachments:

• register_imsdroid_401.pcap

[GoogleCodeExporter]

Resolved in revision 29.

Original comment by boss...@yahoo.fr on 16 Jun 2010 at 2:20

• Changed state: Fixed
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

Hi,

I am facing exactly the same issue.

Using Imsdroid Version v2.548.870 (Latest version I believe)
Handset - Motorola Moto G
Server - OpenIMS Server on Ubuntu.

After the second REGISTER, 401 Unauthorised is received again.
Please help to fix this issue.

Wireshark Captures attached.

Original comment by saurabhm...@gmail.com on 22 May 2014 at 10:57

Attachments:

• Reg_issue