Cool!

Is there a time/pause between these two pieces of output?

SSP CONFIRM a0:56:b2:4c:66:30 593250
NO CARRIER 0 ERROR 9003 L2CAP_CONNECTION_REJ_SECURITY

According to section 7.21 of the docs, I'll bet that you have to respond to SSP CONFIRM with a command something like this:

SSP CONFIRM a0:56:b2:4c:66:30 12345678
(where 12345678 is the passkey shown on the car stereo screen)

If true, this is a pain in the ass because it requires that you enter the passkey shown on the car stereo's screen. But it's worth trying that, just typing the command into the debug console.

In the long term, you have the opportunity, with your setup, to create a UI on the empeg for entering that passkey. And the user would only have to do it as often as they reset the bluetooth module.

Perhaps there is a way to configure the security settings, either on the stereo or in the bluetooth commands, to switch to a different security model that doesn't require the passkey. Some way to configure the module to respond to the stereo with "I don't have the capability to enter a passkey so just drop back to a less secure method please". Dunno if that's possible.
_________________________
Tony Fabris