The current plasma-pa KCM is not really suitable for a phone. It exposes too much implementation details, such as the PA profile used for calling, which is something that needs to be dealt with automatically without the user needing to do something manually.
Instead of trying to 'fix' the desktop KCM for mobile usage I propose to create a new KCM based upon mobile use cases. The PulseAudio bindings are extacted into their own library anyway, so there won't be much code duplication.
The new KCM could also host other sound related settings such as the notification/call sound.
Before I start hacking I'd like to collect some use cases and ideas on how to lay out the UI