In [1], you can read about CDR values. Among them, you have src and dst values, respectively defined as “the Caller ID Number” and “the destination extension”.
Are these src and dst values natively equal to Dialplan variables (respectively CALLERID(num) or EXTEN) to some protocol-dependant headers (“user part of From header” or SIP request URI for PJSIP, …) ?
Is there a way to log in CDR some SIP header values Asterisk computes ? Here, I’m thinking here about P-Asserted-Identity or Identity as having them along billing data would be very convenient.
In [1], you can read about CDR values. Among them, you have src and
dst values, respectively defined as “the Caller ID Number” and “the
destination extension”.
Are these src and dst values natively equal to Dialplan variables
(respectively CALLERID(num) or EXTEN) to some protocol-dependant
headers (“user part of From header” or SIP request URI for PJSIP, …) ?
Is there a way to log in CDR some SIP header values Asterisk
computes ? Here, I’m thinking here about P-Asserted-Identity or
Identity as having them along billing data would be very convenient.
From recent testing, I think values in CDR tables are much more closely aligned with Dialplan variables (EXTEN, CALLERID(num) than with SIP headers themselves.
If one wants to log SIP headers, it seems quite easy to do for inbound calls, thanks to PJSIP_HEADER existence, but for outbound call, this seems quite difficult.
They would be, because Asterisk is an ISDN PABX to which SIP has been added, so there aren’t always going to be any SIP headers, and the core coded does not know about SIP.