Hi there,
I've been trying to use the shiny new 3GPP Early IMS Security feature on Boghe but have been running into some issues. Was wondering if there's an easy work around.
The situation:
- Using Boghe v2.0.186.1013 on Windows 7.
- Configured Boghe to use IPSec (MD5, DES-EDE3, Trans, ESP) and ticked the Enable 3GPP Early IMS Security option.
- Attempted to set up an IPSec connection to my P-CSCF by Signing In.
- Found that the REGISTER sent by the client did not contain the expected Security-Client header mandated by RFC 3329 and consequently no IPSec connections were created.
I had a look in the logging output and found the following errors in Boghe.log:
2014-01-21 17:41:52,338 ERROR [1] BogheCore.Services.Impl.SipService:0 - ***ERROR: function: "_vista_createLocalSA()"
file: ".\plugin_win_ipsec_vista.c"
line: "340"
MSG: FwpmFilterAdd0 (inbound) failed with error code [5]
2014-01-21 17:41:52,338 ERROR [1] BogheCore.Services.Impl.SipService:0 - ***ERROR: function: "tsip_ipsec_association_ctor()"
file: ".\src\transports\tsip_transport_ipsec.c"
line: "480"
MSG: Failed to set IPSec local info:172.18.41.109,10.23.42.10,50032,50031
2014-01-21 17:41:52,339 ERROR [1] BogheCore.Services.Impl.SipService:0 - ***ERROR: function: "tsip_dialog_request_send()"
file: ".\src\dialogs\tsip_dialog.c"
line: "477"
MSG: Failed to find a valid default transport [2]
2014-01-21 17:41:52,339 ERROR [1] BogheCore.Services.Impl.SipService:0 - ***ERROR: function: "tsip_transport_ipsec_updateMSG()"
file: ".\src\transports\tsip_transport_ipsec.c"
line: "257"
MSG: No IPSec association found.
So it looks as though there's a problem setting up the local SA and this causes the client to skip the Early IMS Security feature. Is this a known issue? Perhaps there is an extra setting somewhere I need to tweak? Any debugging expertise would be appreciated :).
I attach the full Boghe.log in case there's some extra details inside that are useful.
Cheers,
Rob