There needs to be an IPsec proposal matching what the remote end is offering. Typically we use proposals such as:
crypto ipsec ikev1 transform-set ESP-AES-128-SHA-256 esp-aes esp-sha-hmac
If the other end needs different parameters for encryption or integrity, then they would need to be modified according on the ASA configuration to match.
If you have the option to have the other end change their parameters, it would be a good idea to change ISAKMP over to IKEv2 with more secure parameters. For Cisco ASA devices, NSA recommends IKEv2, since the IKEv1 implementation only supports SHA1. For instance:
IKEv2:
crypto ikev2 policy 1
encryption [aes-256|aes-gcm-256]
integrity [sha384|sha512]
group [16|20]
IPsec:
crypto ipsec ikev2 ipsec-proposal <proposal name>
protocol esp encryption [aes-256|aes-gcm-256]
protocol esp integrity [sha-384|sha512]