Skip to content

NethVoice CTI: Parameterized URL uses wrong UniqueID (should use LinkedID) #7887

@andrea-marchionni

Description

@andrea-marchionni

Description:

When configuring a parameterized URL, the uniqueid parameter currently refers to the receiving SIP channel instead of the original call unique ID.
As a result, the value does not match the UniqueID used by Asterisk for the original call, which is needed for tasks such as retrieving the call recording file.

The CTI server already provides the linkedid, which correctly identifies the original call and should be used instead of the current uniqueid.

Image

Parameterized URL create

http://10.10.3.184:9080/call?unique_id=1771495918.9593&caller_id=0721405516

CDR entry

+---------------------+---------------------------+------------+-----+-----------------+---------------------------+--------------------+---------+----------------------------------------------------------------------+----------+---------+-------------+----------+-------------+-----------------+-----------+------------+--------------------------------------------------------------+------------+------------+---------------+---------------+----------+-----------------+-------------+----------+----------+--------------+ | calldate | clid | src | dst | dcontext | channel | dstchannel | lastapp | lastdata | duration | billsec | disposition | amaflags | accountcode | uniqueid | userfield | did | recordingfile | cnum | cnam | outbound_cnum | outbound_cnam | dst_cnam | linkedid | peeraccount | sequence | ccompany | dst_ccompany | +---------------------+---------------------------+------------+-----+-----------------+---------------------------+--------------------+---------+----------------------------------------------------------------------+----------+---------+-------------+----------+-------------+-----------------+-----------+------------+--------------------------------------------------------------+------------+------------+---------------+---------------+----------+-----------------+-------------+----------+----------+--------------+ | 2026-02-19 11:11:58 | "0721405516" <0721405516> | 0721405516 | 230 | from-did-direct | PJSIP/Protocolli-00000503 | PJSIP/230-00000504 | Dial | PJSIP/230/sip:230@10.10.3.2:60200,,HhtrIb(func-apply-sipheaders^s^1) | 23 | 17 | ANSWERED | 3 | | 1771495918.9589 | | 0733974921 | in-0733974921-0721405516-20260219-111158-1771495918.9589.wav | 0721405516 | 0721405516 | | | Nethesis | 1771495918.9589 | 230 | 1974 | | |

Expected behavior:

  • The parameterized URL should use linkedid (or alternatively expose both values explicitly).
  • This would allow reliable correlation with call recordings and CDR data.

Current behavior:

  • uniqueid refers to the receiving SIP channel and does not match the call’s original UniqueID.

Suggested fix:

  • Replace uniqueid with linkedid in the parameterized URL, or add linkedid as a dedicated parameter.

Metadata

Metadata

Assignees

Labels

nethvoiceBug or features releted to the NethVoice projectnethvoice-ctiThe issue is related to NethLink (NethVoice Web client)

Type

Projects

Status

In Progress

Relationships

None yet

Development

No branches or pull requests

Issue actions