- Joined
- Dec 10, 2022
- Messages
- 2
- Reaction score
- 0
Hello,
I’m listening to real-time call events over WebSocket and then calling the Call Control API endpoint that matches:
/callcontrol\/([^/]+)\/participants\/([^/]+)$/
and the result is
{
id: 907,
status: 'Connected',
dn: '361',
party_caller_name: '',
party_dn: '10001',
party_caller_id: '88888',
party_did: '',
device_id: 'sip:[email protected]:5483',
party_dn_type: 'Wexternalline',
direct_control: false,
originated_by_dn: '',
originated_by_type: 'None',
referred_by_dn: '',
referred_by_type: 'None',
on_behalf_of_dn: '',
on_behalf_of_type: 'None',
callid: 251,
legid: 3
}
For inbound calls, dn and party_dn don’t reflect the actual DID that was called (they show the trunk internal routing/DN like 10001).
Question: What is the correct way to retrieve the real DID (the called number) for the called party?
Thank you.
I’m listening to real-time call events over WebSocket and then calling the Call Control API endpoint that matches:
/callcontrol\/([^/]+)\/participants\/([^/]+)$/
and the result is
{
id: 907,
status: 'Connected',
dn: '361',
party_caller_name: '',
party_dn: '10001',
party_caller_id: '88888',
party_did: '',
device_id: 'sip:[email protected]:5483',
party_dn_type: 'Wexternalline',
direct_control: false,
originated_by_dn: '',
originated_by_type: 'None',
referred_by_dn: '',
referred_by_type: 'None',
on_behalf_of_dn: '',
on_behalf_of_type: 'None',
callid: 251,
legid: 3
}
For inbound calls, dn and party_dn don’t reflect the actual DID that was called (they show the trunk internal routing/DN like 10001).
Question: What is the correct way to retrieve the real DID (the called number) for the called party?
- Is it exposed in a different field or endpoint (e.g., /callcontrol/{callId} or a call history record)?
- Do I need to map trunk DN → DID via another API?
Thank you.