- Joined
- Jun 26, 2007
- Messages
- 7
- Reaction score
- 0
hi,
we are currently intensivly testing 3cx and have some problems after all:
1) the wedamin is not accurate at all. there are lot's of missunderstandings where you currently are, and where you are jumping to.
2) the use of terms is different in webadmin and 3cx softphone. i really would recommend that finally both products use the same terms in the gui ...
3) why do i get the voicemail in wave format and e.g. not mp3? smaller and faster ...
4) why you are not support complex passwords for the admin account?
5) the authentication id of an extension should always be numbers otherwise it wont work. have you ever thought about connecting to user database of an windows server ads oder manually importing them? most user logins are "s.lastname" or "surname.lastname". so if i would be able to import accounts to add or simple a passwort connection method to the ads server (like mdaemon mailserver does), it would save me and my customers a lot of time managing ...
6) if you still insist of numbers for the authentication id, so simply write this in the manual! because i tried a few minutes and gave up till i tried only numbers and it worked ... very funny!
7) why is the cti/tapi client is only available for the enterprise package? there are lots of normal phonesystems which deliver that for FREE with their phonesystem and the price difference is not really bigger to your 3cx ...
8) if i want to use extension lines form outside via voipprovider by a number e.g. "0720 123456 100" (sipgate.at) NO provider in austria and germany is capeable of delivering such extensions and it will still take more months to have them. what 3cx thinks about that?
9) furthermore i REALLY do miss an exact manuall which ports are to be opened form external to internal if i want to call out and get calles in via voip-provider, and which ports are to be open if my employee is outside (not by vpn). all this stuff has to be tested for yourself.
what i think is that you let support and testing be done by customers ... and that is not business for communication!
any answer would be nice, thank you so far!
sincerly
marty
[/list]
we are currently intensivly testing 3cx and have some problems after all:
1) the wedamin is not accurate at all. there are lot's of missunderstandings where you currently are, and where you are jumping to.
2) the use of terms is different in webadmin and 3cx softphone. i really would recommend that finally both products use the same terms in the gui ...
3) why do i get the voicemail in wave format and e.g. not mp3? smaller and faster ...
4) why you are not support complex passwords for the admin account?
5) the authentication id of an extension should always be numbers otherwise it wont work. have you ever thought about connecting to user database of an windows server ads oder manually importing them? most user logins are "s.lastname" or "surname.lastname". so if i would be able to import accounts to add or simple a passwort connection method to the ads server (like mdaemon mailserver does), it would save me and my customers a lot of time managing ...
6) if you still insist of numbers for the authentication id, so simply write this in the manual! because i tried a few minutes and gave up till i tried only numbers and it worked ... very funny!
7) why is the cti/tapi client is only available for the enterprise package? there are lots of normal phonesystems which deliver that for FREE with their phonesystem and the price difference is not really bigger to your 3cx ...
8) if i want to use extension lines form outside via voipprovider by a number e.g. "0720 123456 100" (sipgate.at) NO provider in austria and germany is capeable of delivering such extensions and it will still take more months to have them. what 3cx thinks about that?
9) furthermore i REALLY do miss an exact manuall which ports are to be opened form external to internal if i want to call out and get calles in via voip-provider, and which ports are to be open if my employee is outside (not by vpn). all this stuff has to be tested for yourself.
what i think is that you let support and testing be done by customers ... and that is not business for communication!
any answer would be nice, thank you so far!
sincerly
marty
[/list]