search

fonoempresa / boghe

Automatically exported from code.google.com/p/boghe
0 stars 0 forks source link

Boghe always send the ipsec protocol as "AH" though we set it to esp #212

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.enable the ipsec , choose the Algorithm=hmac-md5-96, 
encrypt-Algorithm=aes-cbc, mode=trans, protocol=esp
2. Try to Signin
3. Boghe always sends prot=ah irresepctive whether we set protocol as ah or esp

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

Boghe should send the protocol as esp.

What version of the product are you using? On what operating system?

v.2.0.186.1013
Please provide any additional information below.

REGISTER sip:open-ims.test SIP/2.0
Via: SIP/2.0/UDP 10.70.54.55:50921;branch=z9hG4bK-90987126;rport
From: <sip:bob@open-ims.test>;tag=90966547
To: <sip:bob@open-ims.test>
Contact: 
<sip:bob@10.70.54.55:50921;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: d089a8be-a250-4546-f9fd-a6563254bdbf
CSeq: 6961 REGISTER
Content-Length: 0
Max-Forwards: 70
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:bob@open-ims.test>
Supported: path
Security-Client: 
ipsec-3gpp;alg=hmac-md5-96;ealg=aes-cbc;prot=ah;mod=trans;spi-c=1616392923;spi-s
=2585580308;port-c=50923;port-s=50922
Require: sec-agree
Proxy-Require: sec-agree

Original issue reported on code.google.com by prakash1...@gmail.com on 19 Mar 2015 at 10:32

GoogleCodeExporter commented 9 years ago 
this issue already fixed fixed. Please build Boghe by yourself using latest 
Doubango and Boghe source.

Original comment by boss...@yahoo.fr on 19 Mar 2015 at 12:17

GoogleCodeExporter commented 9 years ago 
Hi prakash , 

please let me know how you are able to get the security-clinet header .

as I am using the same version but not getting the security-clinet header when 
message reached to p-cscf .

any special setting required for the same let me know ??

REGISTER sip:techma.com SIP/2.0
Via: SIP/2.0/UDP 10.193.30.12:59996;branch=z9hG4bK-2477976;rport
From: <sip:userAKA00@techma.com>;tag=2485811
To: <sip:userAKA00@techma.com>
Contact: 
<sip:userAKA00@10.193.30.12:59996;transport=udp>;expires=600000;+g.oma.sip-im;la
nguage="en,fr";+g.3gpp.smsip;+g.oma.sip-im.large-message;audio;+g.3gpp.icsi-ref=
"urn%3Aurn-7%3A3gpp-application.ims.iari.gsma-vs";+g.3gpp.cs-voice
Call-ID: f8adcf3f-5d07-2d42-5204-a48b4575cccc
CSeq: 6579 REGISTER
Content-Length: 0
Max-Forwards: 70
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:userAKA00@techma.com>
Supported: path

Original comment by saroj...@gmail.com on 22 Jul 2015 at 12:53