NethVoice CTI: Deepgram call transcription does not work for outgoing external calls

[mgarra]

Description:
We are experiencing an issue with call transcription using Deepgram.

The transcription does not work for outgoing external calls.
In contrast:

• Transcription works correctly for incoming external calls
• Transcription works correctly for internal calls (extension to extension)

The problem seems to affect only external outbound calls.

Expected behavior:
Call transcription via Deepgram should work consistently for all call directions, including outgoing external calls.

Actual behavior:
Outgoing external calls are not transcribed, while all other call types are handled correctly.

[Stell0]

Real time call transcription doesn't work for call to external numbers because of two distinct issues:

1. dial in macro-dialout-trunk has a U(sub-send-obroute-email) function that prevent U(satellite) to be called because only one U function is considered by asterisk

exten => s,n,Set(DIAL_TRUNK_OPTIONS=${DIAL_TRUNK_OPTIONS}U(satellite^s^1))
exten => s,n,Dial(${OUT_${DIAL_TRUNK}}/${OUTNUM}${OUT_${DIAL_TRUNK}_SUFFIX},${TRUNK_RING_TIMER},${DIAL_TRUNK_OPTIONS}b(func-apply-sipheaders^s^1,(${DIAL_TRUNK}))U(sub-send-obroute-email^${DIAL_NUMBER}^${MACRO_EXTEN}^${DIAL_TRUNK}^${NOW}^${CALLERID(name)}^${CALLERID(number)}))

    -- Executing [s@macro-dialout-trunk:30] Dial("PJSIP/225-000001de", "PJSIP/3497866537@NethesisTWT,300,TU(satellite^s^1)b(func-apply-sipheaders^s^1,(9))U(sub-send-obroute-email^3497866537^3497866537^9^1766152468^^0721405516)") in new stack

see also https://docs.asterisk.org/Certified-Asterisk_18.9_Documentation/API_Documentation/Dialplan_Applications/Dial/#arguments

2. when Satellite retrieve speakers name, see the trunk number instead of extension, so nethcti-middleware isn't able to associate the call with the user

proposed solution:

1. attach satellite to sub-send-obroute-email instead of DIAL_TRUNK_OPTIONS

2. Save extension in a channel variable, then make Satellite able to read users.json and send user information on mqtt