Hi Steve!
Thanks for the feedback! Our .NET API is not ready yet, its too early to be able to give details but in a nutshell, all stuff that can be done from the interface and all things that can be monitored from the interface will be possible from the .NET api. Furthermore, a .NET call control API, similar in functionality to the VOIP client will also be available. In regards to your questions:
Can the dial plan be customised so that you can set the options for pickup?
Yes you can, it can be done from the ini file. See Configuration section of our wiki at wiki.3cx.com
Are there multiple pick-up groups for department or group or is it a global feature?
Its a global feature at present
What is the max number of users you have seen / server specification? As it appears from the configuration RTP is point to point and with an E1 gateway I am assuming it would be direct to the gateway so the loading should be pretty minimal on the CPU.
We have seen hundreds of calls on one machine. Yes, with the gateway doing the work its very scaleable. Thats what we try to explain why we think gatewys are better and more scaleable then using add in cards which are tied to the OS and take a lot of processor usage
DotNet is what I do, along with 20+years of telephony + cti in the contact centre so I would be very interested in the new API, perhaps even to discuss the content from a developer point of view which features really sell?
With your experience we would of cousre be very keen to hear you feedback, you can email me at ng at 3cx.com if you prefer
I am very keen to see the Vega integration as I have worked with those guys quite a few times and find their equipment and service to be first class.
Its already available in beta - you can download the beta config templates from wiki.3cx.com
Or if you are familiar with vega you can simple configure the device directly