Detect dialed Prefix in outbound Call Log.

[elited]

There seems to be an inherent function in the PBX to mask any dialed prefix on outbound numbers once the call terminates.
For instance, if I dial 888-555-9999 with the prefix *1, and the call is not terminated by the receiving end, the dialed number (*1888-555-9999) shows up correctly in the call log.
On the contrary, should the receiving party answer the call, the *1 prefix ends up not being included in the call log.

This is a major setback for organizations attempting to track outbound calls that utilized a prefix. Is there any other way to bypass this limitation or perhaps an alternative route?

Thanks in advance!

 

[NicholasP_3CX]

Is there any specific reason you need to do the prefix?

If it is for billing purposes you can use the billing code prefix available in 3CX.

https://www.3cx.com/docs/pbx-dial-codes/

So for example if you want to bill project/custom 1234 you will dial NUMBER**1234

You can then create a billing code report for each project/customer.

 

[elited]

The prefix would be so that our CSRs can opt to dial out with a different CID. We need to be able to detect when a given call is dialed accordingly.

 

[elited]

Unless there's any way to retain the dialed prefix in the call log for the scenarios described above, is there a way to determine the outbound CID that a specific call was made with?

 

[elited]

No one capable of shedding some light on this? Thanks!

 

[elited]

Reaching out again to see if there are any 3CX "experts" out there capable of assisting me with this issue. Much appreciated in advance!

 

[SweetAction]

If your issue is solely the CallerID of outbound calls, perhaps a 3rd party solution like VOIPTools might solve this for you. I don't think there is a native way in 3CX to accomplish tracking by agent by outbound rule, but I can't see why ingesting CDRs and building your own reports won't work.

 

[elited]

Let me try another way that would achieve the same outcome - Is there a way to detect which outbound rule a specific call used?

 

[elited]

If your issue is solely the CallerID of outbound calls, perhaps a 3rd party solution like VOIPTools might solve this for you. I don't think there is a native way in 3CX to accomplish tracking by agent by outbound rule, but I can't see why ingesting CDRs and building your own reports won't work.

Could you please elaborate on "I can't see why ingesting CDRs and building your own reports won't work" ? Please describe a scenario in where using CDR's would accomplish my request. Thanks!

 

[SweetAction]

Could you please elaborate on "I can't see why ingesting CDRs and building your own reports won't work" ? Please describe a scenario in where using CDR's would accomplish my request. Thanks!

Without looking at one right this second, CDR shows dialed number (as well as to number) and I think that includes the prefix. You want to see/sort by prefix, no?

If not the CDR, for sure the system log shows this info (in verbose mode - I think it's called ManagementConsole, but again I'm not checking right now) so you could ingest this log instead and build your own reports, although it's far more unsupported and complicated to do so.

 

[elited]

Ended up using CDR by including the necessary fields for the prefix. Went on to create automation rules to parse the data on a local workstation and then created subsequent detection rules to post to Slack - works brilliantly!