From the RFC:
http://www.ietf.org/rfc/rfc3261.txt20.4 Alert-Info
When present in an INVITE request, the Alert-Info header field
specifies an alternative ring tone to the UAS. When present in a 180
(Ringing) response, the Alert-Info header field specifies an
alternative ringback tone to the UAC. A typical usage is for a proxy
to insert this header field to provide a distinctive ring feature.
The Alert-Info header field can introduce security risks. These
risks and the ways to handle them are discussed in Section 20.9,
which discusses the Call-Info header field since the risks are
identical.
In addition, a user SHOULD be able to disable this feature
selectively.
This helps prevent disruptions that could result from the use of
this header field by untrusted elements.
Example:
Alert-Info: <http://www.example.com/sounds/moo.wav>
There are 2 options for integration
1: Simple: only differance between internal and external calls, so somwhere in the options you should be able to choose for "Alert-info value internal calls" and "Alert-info value external calls"
2: Advanced: Per ringgroup, so per ringgroup it should be possible to choose an 'Alert-info value'.
Then an admin can specify the value of the alert-info and they can learn the value to their phones, or 3cx should add the defaults in the phone provisioning templates.