A321
Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance
Aircraft
My concern here is the time it took to be transferred to MX Control after speaking with dispatch. I would like to report what an outstanding job [the] First Officer did in support during the situation we had!Towards the top of climb we received multiple Cargo Smoke ECAMs; which would come on and almost immediately disappear. The first one happened so fast we did not even see what it was. The duration of the second one was long enough to read and then it disappeared. We called the FA's (Flight Attendants) to ask if they smelled anything in the back and sent an ACARS to MX advising of our issue and asking for troubleshooting/reset advice. The response from MX took longer than expected and we did not get the answer appropriate to our situation so we established a phone patch with dispatch to be connected to MX Control. At that point the FA's reported that they did not smell anything in the aft cabin. We were still waiting for the connection to MX Control when an ACARS message was received stating; 'failed system is smoke detection function has failed. In the cids'.Shortly after that we FINALLY were able to speak to MX control and confirmed the ACARS that they had sent.Mike and I discussed the situation agreeing that if the ECAM returned; even temporarily; we would land. We requested a reroute over the coast with dispatch as we were going to be heading out over the water. We coordinated with ATC and continued the flight to ZZZ without incident. After we parked the aircraft; we checked the status message which read; Maintenance Smoke.
The biggest concern I have was the amount of time it took to be connected with MX Control. Even through ACARS; the delay ate away at precious time; had this been an actual emergency.I believe the professionalism and impeccable CRM skills of [the] Captain directly resulted in the safe continuation of [the flight].At top of climb; we received multiple Cargo Smoke ECAM messages; which would subsequently disappear within a matter of seconds. The first one did not last long enough to read the message; only long enough to set off the master warning triple-chime. The second and subsequent ones lasted long enough to read the condition; however not long enough to read the corrective actions. We contacted the lead flight attendant to see if there was any indications of things not being normal; to which they informed us all to be normal. In this time we had already sent an ACARS message to dispatch/MX and had not had a response. We decided to patch through via ARINC (Aeronautical Radio); which was immediately connected to dispatch. However; it took multiple attempts and approximately 10-15 minutes for dispatch to get MX connected. At this point we had now received an ACARS message from MX stating 'failed system is smoke detection function has failed. In the cids' We spoke with MX as well via the patch and requested a reroute over land; as we were filed over the [water]. We had the fuel; so this was approved and coordinated with ATC. [The] Captain and I decided that if the messages were to come back; that we would divert. The condition did not return and we continued to land in ZZZ. Upon arrival and completing the parking checklist; we checked the status message which read; Maintenance Smoke.
A321 flight crew reported false Cargo Smoke Detector alerts in flight.