We were about to implement 3CX with Vitelity trunking to replace our Switchvox with Vitelity trunking. We use account based authentication with multiple trunks. Call routing allows us to send different Caller ID which is particularly important for e911 with multiple sites. I want to make sure no one else is burned by this bug (looks like I'm out my non refundable license and the extra support I just paid for). According to support, Kindly note that the system routes the call to the vitelity network and vitelity is responding back with an error message causing the calls not to be successful, we can only comment on the 3CX server. As per the configuration instructions the template is made for IP-based trunks for vitelity They are correct when after reviewing the configuration guide. https://www.3cx.com/docs/vitelity-usa-sip-trunk/ I tested Vitelity with a single trunk (free evaluation license) and it worked great using the template. 3CX has a great product, but unfortunately, it is not usable for our needs. Maybe in the future as they have some amazing features.