-
Type:
New Feature
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: VQ Plus (Commercial)
-
Labels:None
-
ToDo:
At present, queue callback calls originate to PSTN users with the outbound CID as set in the module settings. It relies on the trunk supporting rpid so that the channel CONNECTEDLINE gets updated with the remote user's CallerID prior to the channel being sent to the queue.
If the trunk doesn't support rpid, the CONNECTEDLINE is never updated, and the callback call goes back into the queue carrying the original CID of the call as set in the Queue Callback parameters.
I believe (but haven't tested) that if the queue callback is originated using a CID the same as the outbound dialed digits, the lack of rpid support can be overcome, and the call will enter the queue with the correct CID. Unfortunately, with this setting, the caller receiving a callback call will see their own CID, but I don't see how that is avoidable. When defining a Queue Callback, there is already a field for outbound CID, perhaps a toggle that allows outbound calls to carry remote CID.