CDR - DID Tracking

[Futureweb]

For CDR - please add a Field "to-did" - would be important for Tracking Marketing effectiveness.
As described here: post175796.html

Feature Description:
We need to track DIDs for Marketing Effectiveness Tracking.
Every Advertisement we do got its own DID.
Within 3CX incoming Rules are configured 012345678* (Number + *) - so all of those Marketing DIDs are Routed to the same Queue.
Now my Problem is that I don't see the called DID (called Number) within the CDR nor within the LOGs ... it just shows me the Extension of the reached Queue/Phone which picked the call - but never the *called number* / *called DID*
We can't create an incoming Rule/Extension for every DID used for Marketing as they change to often / are way too much / often are not known outside Marketing Dept. (Thousands/Ten Thousands of Numbers ...)


Thank you
Andreas Schnederle-Wagner

 

[Futureweb]

to be a bit more specific - we would need "Request Line URI : User Part" somewhere in the CDRs ...

 

[Hellkeeper]

We would also need this Feature to track the success of our Google AdWord Campaigns ... different Campaigns got different Phone Numbers + unique DIDs ... but now with 3CX we are not able to log those calls anymore ... which was no Problem with out old PBX ... would all be solved if "Request Line URI : User Part" could be added to CDRs.

 

[Cadonline]

Would be a welcome Extension! Right now we get a List of called (inbound) Numbers from our SIP Provider for this - Once a month.

 

[ManuelR]

Hello,
we use this kind of functionality within our current hardware-based PBX.
As we evaluate 3CX for replacement to our old PBX this is a Feature which is crucial if we want to Switch!
Manuel

 

[Futureweb]

For now we "emulate" this Behaviour ... on Trunk Settings Page - Parameters for incoming Connections --> "CallerName" caller's name (default: From->display name) set to "Request Line URI: User Part"
Then the Number called can be found within CDR Logs ...
But it would be better to have an own Field for that Information ...

Andreas

 

[ManuelR]

@Futureweb: tried your workaround and it's working like a charm!
Just had to reprovision all Yealink Phones so they don't show the called number that big (that's the downside of this workaround)

But I still hope they will add "Request Line URI : User Part" Field to CDR.

Manuel

 

[dig1234]

The other way to gather this information currently is thru the API with your own logging system..

 

[Futureweb]

@dig1234: How would you do this in V14? Could you post some Details?

Andreas

 

[dig1234]

@dig1234: How would you do this in V14? Could you post some Details?

Andreas

I believe we are using this API:
http://www.3cx.com/blog/docs/call-control-api/

 

[Futureweb]

alright - thx for information ... but way to complicated ...
I hope they add it to CDR Output .... guess this is a matter of minutes to implement ...

Andreas

 

[dig1234]

Agreed! That and the call log ID would be huge...
call-reports-o-show-log-call-id-44023.html

 

[ManuelR]

I believe we are using this API: http://www.3cx.com/blog/docs/call-control-api/

This would require a whole .NET/C# Project - that's way to complicated for a requirement like this - none of our customers would pay for that!
It's really a shame there is no way to do this with 3cx! (without workarounds like the one Futureweb posted)

 

[Futureweb]

For now we "emulate" this Behaviour ... on Trunk Settings Page - Parameters for incoming Connections --> "CallerName" caller's name (default: From->display name) set to "Request Line URI: User Part"
Then the Number called can be found within CDR Logs ...
But it would be better to have an own Field for that Information ...

Just noticed a major Problem with this workaround ... if the caller number is already within 3CX phonebook - CDR won't show the called number - but instead it will show the name from the phonebook ...
This renders this workaround useless for already known numbers ...

Andreas

 

[ManuelR]

Did you find any solution for this problem?

 

[Futureweb]

Unfortunately no really Solution on this Problem! We just stopped using the 3CX Phonebook ...
Only using the Yealink Phonebooks anymore ...

I'm still hoping 3CX will implement "Request Line URI : User Part" within CDR Output ... guess it would be a matter of Minutes for them ...

Andreas

 

[3CXusername]

i'm still on 12.5 but looking to upgrade to v14 shortly. Could someone post a sample v14.x CDR output so I could compare?

 

[Futureweb]

You can find all information about CDR in V14 here: http://www.3cx.com/docs/cdr-call-data-records/
It's simply a CSV File or Stream you can use

Sample Output: Call 18982,00000BE960FE3D85_12261,0.00:00:23,2016.01.11 10:42:40,2016.01.11 10:42:48,2016.01.11 10:43:12,TerminatedBySrc,Ext.7400,06601010101,7400,10000,06601010101,,,,,0,1,0,04,ÖSTERREICH-Mob,Chain: Ext.7400;06601010101;,Extension,Line,,Andreas,06601010101,

Unfortunately not all needed informations are included ... that's why this Ticket exists ...

Andreas

 

[Futureweb]

any chances "to-did" will be added to CDR?!?

 

[kbx81x]

^^^ I second (third? fourth?) all this. We are also looking for this information in the CDRs. Similar to the others, the information is needed for marketing data tracking purposes...