Enabling Queue_log DNI event

[services_cdev]

Hi again!

So, we’ve encountered something we had not seen before regarding queue_log and how it gets filled with information about the inbound call being received.

This is from the older PBX before migrating to VitalPBX 4

1683532666|1683532666.940655|q-outbound|PJSIP/SBC_trunk|CALLOUTBOUND||+18XX8XXNNNN
1683532666|1683532666.940655|q-outbound|PJSIP/SBC_trunk|CONNECT|0|
1683532672|1683532666.940655|NONE|NONE|INFO|IVRAPPEND|3|ivr-3
1683532673|1683532666.940655|100|NONE|DID|+18XX8XXNNNN
1683532674|1683532666.940655|100|NONE|ENTERQUEUE||+1803NXXXXXX|1
1683532674|1683532666.940655|q-outbound|NONE|CALLERONHOLD|MYB-MoH-16122022
1683532683|1683532666.940655|q-outbound|NONE|CALLEROFFHOLD|
1683532683|1683532666.940655|100|PJSIP/1153|CONNECT|10|1683532674.940656|9

As you can see, there is a DID event being generated in queue_log;

1683532673|1683532666.940655|100|NONE|DID|+18XX8XXNNNN

This has happened for a very long time, across different flavours and even Asterisk vanilla, I understand that there may be a change, however we need this DID event to somehow happen so that our reporting suite works correctly displaying the DNIS being dialed and we can perform brand separation on the dialed number.

What can we do? is there a dialplan we can create that will be persistent across updates and that will create this entry in queue_log? Can we add anything persistent to a custom dialplan?

thanks a lot!

[miguel]

In the link below, you can see the NATIVE events provided by Asterisk.
https://wiki.asterisk.org/wiki/display/AST/Queue+Logs

Those events in your example are custom events configured in your old dial-plan as customizations.

[services_cdev]

Hey there,

So thanks a lot for the quick response, ok, so was confused, anyhow, have you got any experience as to how to make any of the changes mentioned above, permanent?

I have no problem customizing myself, however, making it permanent is the key matter here.

regards,