You didn’t offend anyone.
Once you explained your tasks and goals (quoted):
“I have 28 branch offices that need to transmit fax and my goal was to abandon the old fax machines cutting costs through FoIP. I state that I am the only one person working in the IT department. I have to take care of a rather complex infrastructure and I have an absolute need of solutions that operate with little or no maintenance”
it was quite clear that you hadn’t time (nor internal IT resources) to get involved into this particular FreePBX Commercial Module development (I write that from a FreePBX user/FreePBX Administrator perspectives).
Said so it’s also evident that you wasn’t ready to improve the FAX Pro module by issuing new specific tickets (just to ask for one or more new features/improvements) or by just signalling new software bugs you eventually discovered during the its deployment.
It’s also clear now why you discarded the FAX Pro solution: it’s because, among your various other specific requirements (Mass FAXing, as example), there was a most stringent one, the one we can generally summarize with this statement/approach to problem solving:
“I’ve no time to investigate, the solution I need should work as I expect in no time with no issue at all, if it doesn’t I must discard it and look for another one, no matter the price I’ll pay for, I need it works as I want”.
It’s impossible to not agree with this vision once you explained your scenario.
Without your personal involvement (that requires your time, your user’s patience), improving such solution will last longer but, in the end, that solution will be improved in any case because other users will ask about new features or will find some time to open new Tickets or will speak (write) to Developers about solution’s improvement.
It’s a matter of to be (or not to be) part of something and try to find time to be actively part of that.
IMHO it’s not that FAX Pro is not generically an “Enterprise Ready” module (remember: it’s just a little part of larger software solution involving FreePBX Distro), it’s that probably your specific deployment wasn’t ready (or right) for FAX Pro deployment.
Couldn’t be that?