Our team is trying to use AudioHookMonitor on Genesys Cloud to receive messages via WebSocket.
But on outbound calls, We are receiving something like below on participant.ani.
By our understanding, we should receive something in E.164 format, but what we are receiving is something starting with sip:
{
"type": "open",
"version": "2",
"id": "02e311b0-cbfe-4e8c-a8c5-08cac35e4890",
"seq": 1,
"serverseq": 0,
"position": "PT0.0S",
"parameters": {
"organizationId": "5bb1b63e-d60d-4e12-a8eb-df5c3fd4e6f4",
"conversationId": "7688df2a-67fd-4d2f-a236-56b5e77e590a",
"participant": {
"id": "d39fe0d1-717e-4489-8909-bc729230edd8",
"ani": "sip:E9968BE799BAE381BFE381AAE38197E794A8_E98791E6BEA4E690BAE5B8AFE99BBBE8A9B1_E382B3E3838DE382AFE38…",
"aniName": "",
"dnis": "tel:+810987654321"
},
"media": [
{
"type": "audio",
"format": "PCMU",
"channels": ["external", "internal"],
"rate": 8000
}
],
"language": "ja-JP",
"startTime": "2026-07-03T08:53:38.802495Z",
"customConfig": {}
}
}
Can anyone please explain us what's happening? Or any idea would be appreciated.
- What is the exact IF specification of participant.ani on AudioHookMonitor/WebSocket open message?
- Should we consider participant.ani as a text string? Or is this should be in E.164 format by spec and something wrong is happening.
- When and why participant.ani would output sip: (or something that is not a phone number) instead of E.164?
- Is there any way we can stop participant.ani to output something that is not E.164?
#API/Integrations#ArchitectandDesign#Implementation#Outbound------------------------------
Saika Kure
N/A
------------------------------