Add MMTel/IMS config option

[GoogleCodeExporter]

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

I suggest adding a configuration option for MMTel flavor under advanced 
settings. When the MMTel option is active, you can also configure a q 
value. At registration the q value and the MMTel feature tag is added to 
the Contact header. In the INVITE the MMTel feature tag is added in the 
Contact and Accept-Contact headers. 

I did this code already but have not had time to test it properly.

There are probably a few other things that could be added also to make 
sipdroid work perfectly in an MMTel/IMS network but this would make a good 
start. (Examples on other additions: P-Preferred-Service header, subscribe 
to regevent, handling of tel url, ...)

         / mandrajg

Original issue reported on code.google.com by mandrajg@gmail.com on 18 May 2010 at 2:07

[GoogleCodeExporter]

Partly implemented in r555.

Original comment by mandrajg@gmail.com on 8 Jul 2010 at 7:11

• Changed state: Started

[GoogleCodeExporter]

One mandatory feature in IMS is IMS-AKA authentication and I think SipDroid 
only support Digest MD5 authentication (not sure). I can help to implement 
IMS-AKA and subscription to reg event package. Could you give me more info. on 
how to contribute to the project.

Original comment by boss...@yahoo.fr on 3 Aug 2010 at 8:38

[GoogleCodeExporter]

Sipdroid also needs support for the Service-Route header for proper IMS support.

i guess, when you attach a patch, somebody may commit it ;-)

Original comment by thilo.ba...@gmail.com on 3 Aug 2010 at 9:37

[GoogleCodeExporter]

Not sure

Original comment by boss...@yahoo.fr on 3 Aug 2010 at 11:21

[GoogleCodeExporter]

I would love to see IMS AKA as an option under MMTel. However most live IMS 
systems still use Digest so don't remove that. I might be able to assist with 
some verification but the rest is up to you. Maybe you can start a new issue 
for this though, so I can close this one when I think I have done what I intend 
to do.

Original comment by mandrajg@gmail.com on 9 Aug 2010 at 11:08

[GoogleCodeExporter]

I don't need to change the Digest MD5. It will be up to the Proxy-CSCF to 
choose which algorithm to use to challenge the UE (Digest MD5, AKAv1/AKAv2). 
The UE also need two additional information (OperatorId(16hex) and AMF(2hex)) 
to be able to generate the response.

Original comment by boss...@yahoo.fr on 9 Aug 2010 at 9:09

[GoogleCodeExporter]

Sounds great bossiel.

Thilo, regarding the Service-Route I think that will most likely be hidden for 
the client due to topology hiding and the P-CSCF will handle that part.

Original comment by mandrajg@gmail.com on 19 Aug 2010 at 12:40