SIP-packets should not contain a _preloaded_ Route-header with that address

[GoogleCodeExporter]

What steps will reproduce the problem?
1.When using an outbound proxy, the SIP-packets should not contain a 
_preloaded_ Route-header with that address. 

Route: <sip:proxy name>

What is the expected output? What do you see instead?
the SIP-packets should not contain a _preloaded_ Route-header with that address.

..from the packets, for example initial INVITE from the client. Outbound proxy 
means that the client should send all initial packets to the outbound proxy 
address, but there should be no references of the outbound proxy address within 
the SIP-packets themselves.

Don’t confuse this with normal routing headers that may be populated from 
Record-route headers (loose-routing) during the first stages of SIP-signaling. 
What I’m talking about is the initial _preloaded_ Route-header.

What version of the product are you using? On what operating system?
IMSdroid 2.x

Please provide any additional information below.

how i can remove this initial _preloaded_ Route-header from classes and API's 
and where , please advice ?

Original issue reported on code.google.com by wmas...@gmail.com on 9 Aug 2011 at 7:08

[GoogleCodeExporter]

Thanks for your explanation ...but this is valid in both IETF and 3GPP context.

3GPP TS 24.229 section 5.1.2A [Generic procedures applicable to all methods 
excluding the REGISTER method]:
                                        The UE shall build a proper preloaded Route header field value for all new dialogs and standalone transactions. The UE
                                        shall build a list of Route header field values made out of the following, in this order:
                                        a) the P-CSCF URI containing the IP address or the FQDN learnt through the P-CSCF discovery procedures; and
                                        b) the P-CSCF port based on the security mechanism in use:
                                                - if IMS AKA or SIP digest with TLS is in use as a security mechanism, the protected server port learnt during
                                                the registration procedure;
                                                - if SIP digest without TLS, NASS-IMS bundled authentciation or GPRS-IMS-Bundled authentication is in
                                                use as a security mechanism, the unprotected server port used during the registration procedure;
                                        c) and the values received in the Service-Route header field saved from the 200 (OK) response to the last
                                        registration or re-registration of the public user identity with associated contact address.

The only way to remote this header is to comment tsip_dialog.c line 
358(http://code.google.com/p/doubango/source/browse/branches/2.0/doubango/tinySI
P/src/dialogs/tsip_dialog.c#358) and rebuild Doubango

Original comment by boss...@yahoo.fr on 9 Aug 2011 at 8:16

• Changed state: Invalid

[GoogleCodeExporter]

thanks 

you mean i need to rebuild all dobango to re generate 

1- armeabi/libtinyWRAP.so
2- armeabi-v7a/libtinyWRAP.so

if yes , is there any simple tutorial to re build the dobango project to 
regenerate these libraries , please advice ?

thanks

Original comment by wmas...@gmail.com on 9 Aug 2011 at 8:28