audiocodecsvoicesecret
, and it’s value should be some unique secret string - a UUID is a good candidate here. Save both the created secret SRN, and the value of the secret - we’ll use both later.yourorg
with your organization name, voicebot
with the name of your bot, and Secret
with the SRN of the secret we just created){
"Address": "yourorg-audiocodecsvoiceadapter",
"OutboundBotReference": "voicebot",
"InboundBotReference": "voicebot",
"Organization": "yourorg",
"EngagementType": "AudioCodesVoice",
"Status": "online",
"AllowedDomains": ["*"],
"EngagementConfig": {
"Secret": "srn:vault:eu-private-1:yourorg:secret:audiocodecsvoicesecret",
"ContextParameters": [
]
},
"Useragent": "useragent",
"TargetBotReference": "voicebot",
"Name": "yourorg voicebot adapter endpoint"
}
AudioCodes Bot API
. Give the bot some name.https://conversation.$REGION.servisbot.com/v1/$ORG/$ENDPOINTADDRESS
eu1
, us1
)caller
, callee
- note this may collect PII in the form of a phone number. These properties will be available at root level in context, e.g. msg.payload.context.caller
Now, wire your AudioCodes bot to a purchased phone number, and try dialling it. You should be able to interact with your bot over voice.