What steps will reproduce the problem?
1. Enable IPsec Choose Algorithm: hmac-md5-96, Encrypt-Algorithm: des-ede3-cbc
, Mode: trans, protocol: esp
2. do SignIn - Client sends REGISTER but there is no Security-Client header
included in REGISTER
3.
REGISTER sip:open-ims.test SIP/2.0
Via: SIP/2.0/UDP x.x.x.x:53167;branch=z9hG4bK-90990848;rport
From: <sip:prakash@open-ims.test>;tag=90968727
To: <sip:prakash@open-ims.test>
Contact:
<sip:prakash@x.x.x.x:53167;transport=udp>;expires=600000;+g.oma.sip-im;language=
"en,fr";+g.3gpp.smsip;+g.oma.sip-im.large-message;audio;+g.3gpp.icsi-ref="urn%3A
urn-7%3A3gpp-application.ims.iari.gsma-vs";+g.3gpp.cs-voice
Call-ID: 6345bb7b-9e98-1320-b8a3-5c9817167ec8
CSeq: 10932 REGISTER
Content-Length: 0
Max-Forwards: 70
Authorization: Digest
username="prakash@open-ims.test",realm="open-ims.test",nonce="",uri="sip:open-im
s.test",response=""
Allow: INVITE, ACK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFER
Privacy: none
P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000
User-Agent: IM-client/OMA1.0 Boghe-Win32/v2.0.186.1013
P-Preferred-Identity: <sip:prakash@open-ims.test>
Supported: path
What is the expected output? What do you see instead?
In REGISTER client should include Security-Client Header ,
No Security Client header is sent
What version of the product are you using? On what operating system?
IM-client/OMA1.0 Boghe-Win32/v2.0.186.1013
Please provide any additional information below.
Original issue reported on code.google.com by
prakash1...@gmail.comon 29 Jan 2015 at 5:24