Is this a feature or a bug? So if I SEND a call to a ring group that is an external number it SENDS it and I can see the CID. But if i want all the juicy goodness of a queue the PBX HOLDS the call and offers a call to the external number. Thus sending the PBX CID information. Then when it is answered it bridges the call. Thus NO CID for QUE
I assume you mean if you send a call to a ring group that includes a destination which is an external, number (and the provider allows arbitrary caller ID and the destination doesn’t suppress numbers marked attestation B, for STIR/SHAKEN) that destination sees the original caller ID.
Asterisk queues don’t really put the call on hold, although, if you use the music on hold option on an answered call, they do use some of the mechanism. The call is originated in essentially the same way as for the Dial used for ring groups, and the default is to pass it through.
There may be something funny about how FreePBX handles it, but I suspect this is more likely a configuration problem. (I think FreePBX always interposes a local channel and Dial for queue members, to support agents logging in, whereas Asterisk can directly access the outgoing channel driver, but that shouldn’t impact the caller ID, and if the caller ID works for an internal destination, you are beyond that point.)
I think Igor’s question is about the provider not allowing arbitrary caller ID.
I’d look at this from an Asterisk point of view, for which I would need the fully log, at verbosity 3, for complete calls for both methods, to understand what was happening to the caller ID. Others might recognize more in terms of the FreePBX abstraction.
As I notice you are in the USA, your provider should be putting an attestation type B on these numbers, as they are not your numbers, and some recipient systems may choose to suppress them. In some countries (one unnamed one came up in the last couple of days), you simply cannot present anything other than your approved numbers.
