I have run unset ike policy-checking command. Result :
"2016-05-17 15:36:00 info IKE 85.96.xx.xx Phase 2 msg ID 7944be28: Completed negotiations with SPI 87c3914b, tunnel ID 443, and lifetime 3600 seconds/0 KB.
2016-05-17 15:36:00 info IKE 85.96.xx.xx phase 2:The symmetric crypto key has been generated successfully.
2016-05-17 15:36:00 info IKE 85.96.xx.xx Phase 2 msg ID 7944be28: Responded to the peer's first message.
2016-05-17 15:35:59 info IKE 85.96.xx.xx: XAuth login was passed for gateway AydinPR_Engineering_GW, username AydinPRTest_1, retry: 0, Client IP Addr 192.168.173.4, IPPool name: XAuthIPPool2, Session-Timeout: 0s, Idle-Timeout: 0s.
2016-05-17 15:35:59 info IKE 85.96.xx.xx: XAuth login was refreshed for username AydinPRTest_1 at 192.168.173.4/255.255.255.255.
2016-05-17 15:35:59 info Rejected an IKE packet on ethernet0/2 from 85.96.xx.xx:4500 to 178.22.xx.xx:4500 with cookies 91ba9815e76ee28e and 7e1caf84ccaae23a because A Phase 2 packet arrived while XAuth was still pending.
2016-05-17 15:35:59 info IKE 85.96.xx.xx Phase 1: Completed Aggressive mode negotiations with a 28800-second lifetime.
2016-05-17 15:35:59 info IKE 85.96.xx.xx Phase 1: Completed for user AydinPR_Engineering_VPN.
2016-05-17 15:35:59 info IKE<85.96.xx.xx> Phase 1: IKE responder has detected NAT in front of the remote device.
2016-05-17 15:35:59 info IKE<85.96.xx.xx> Phase 1: IKE responder has detected NAT in front of the local device.
2016-05-17 15:35:59 info IKE 85.96.xx.xx phase 1:The symmetric crypto key has been generated successfully.
2016-05-17 15:35:59 info IKE 85.96.xx.xx Phase 1: Responder starts AGGRESSIVE mode negotiations.
2016-05-17 15:35:57 info IKE 182.176.88.205: Added Phase 2 session tasks to the task list.
2016-05-17 15:35:47 info IKE 182.176.88.205: Added Phase 2 session tasks to the task list.
2016-05-17 15:35:45 info IKE178.22.xx.xx 182.176.88.205 Phase 1: Initiated negotiations in main mode.
2016-05-17 15:35:36 info IKE 85.96.xx.xx Phase 2 msg ID 6e28c44d: Completed negotiations with SPI 87c3914a, tunnel ID 443, and lifetime 3600 seconds/0 KB.
2016-05-17 15:35:36 info IKE 85.96.xx.xx phase 2:The symmetric crypto key has been generated successfully.
2016-05-17 15:35:36 info IKE 85.96.xx.xx Phase 2: Received a message but did not check a policy because id-mode was set to IP or policy-checking was disabled.
2016-05-17 15:35:36 info IKE 85.96.xx.xx Phase 2: Received a message but did not check a policy because id-mode was set to IP or policy-checking was disabled.
2016-05-17 15:35:36 info IKE 85.96.xx.xx Phase 2: Received a message but did not check a policy because id-mode was set to IP or policy-checking was disabled.
2016-05-17 15:35:36 info IKE 85.96.xx.xx Phase 2 msg ID 6e28c44d: Responded to the peer's first message.
2016-05-17 15:35:34 info IKE 85.96.xx.xx: XAuth login was passed for gateway AydinPR_Engineering_GW, username AydinPRTest_1, retry: 0, Client IP Addr 192.168.173.4, IPPool name: XAuthIPPool2, Session-Timeout: 0s, Idle-Timeout: 0s.
2016-05-17 15:35:34 info IKE 85.96.xx.xx: XAuth login was refreshed for username AydinPRTest_1 at 192.168.173.4/255.255.255.255.
2016-05-17 15:35:34 info Rejected an IKE packet on ethernet0/2 from 85.96.xx.xx:4500 to 178.22.xx.xx:4500 with cookies 9dc1f1a90d3ed140 and 9d66f82563a90635 because A Phase 2 packet arrived while XAuth was still pending.
2016-05-17 15:35:34 info IKE 85.96.xx.xx Phase 1: Completed Aggressive mode negotiations with a 28800-second lifetime.
2016-05-17 15:35:34 info IKE 85.96.xx.xx Phase 1: Completed for user AydinPR_Engineering_VPN.
2016-05-17 15:35:34 info IKE<85.96.xx.xx> Phase 1: IKE responder has detected NAT in front of the remote device.
2016-05-17 15:35:34 info IKE<85.96.xx.xx> Phase 1: IKE responder has detected NAT in front of the local device.
2016-05-17 15:35:34 info IKE 85.96.xx.xx phase 1:The symmetric crypto key has been generated successfully.
2016-05-17 15:35:34 info IKE 85.96.xx.xx Phase 1: Responder starts AGGRESSIVE mode negotiations."
It seems connected but VPN didnt work. I have enabled policy-checking again but now "ANY" service rule also not working.
Firewall-> get ike policy-checking
IKE Phase 2 ID payload checking is enabled