We're reclaiming inactive PDIs to keep them available for active builders. Learn what's changing, who's affected, and how to protect your work. Read More

Getting An error - AWS connect - Voice agent

Paulsylo
Tera Sage

HI All -

 

I trying to connect AWS connect for my voice agent as communication channels. As per the guide , i see we need to share these three information to AWS side to be configured. 

 

Paulsylo_0-1783969524212.png

while i got other information, i got stuck here up on these one information,

 

1. ssm_oauth_path, as it is given " The base path for OAuth credentials in AWS Parameter Store: /com.servicenow.cti/<sn-instance-id>/<voice-service-id>. Set after completing the Parameter Store setup in the following steps "

 

now , what is this <voice-service-id>,to be taken. 

Paulsylo_1-1783969885909.png

do i need to take the sys_id from the url ? if so, i am getting this error below,

 

{     "level": "ERROR",     "message": "Failed to obtain access token",     "error": "OAuth token request failed: HTTP 401 for POST tataamericaintlcorpdemo2.service-now.com/oauth_token.do"}

 

any help will be appreciated .

 

 

Regards,
PaulSylo

To be is to do. To do is to be.
1 REPLY 1

Vikram Reddy
Tera Guru

Hello @Paulsylo,

 

The voice-service-id piece is exactly what your own second screenshot already spells out, so trust it:

/com.servicenow.cti/<sn-instance-id>/<voice-service-id>

sn-instance-id  = value of the instance_id system property (sys_properties.list, NOT your instance name)
voice-service-id = sys_id of the Voice Service record

That part's fine, taking it from the URL is correct as long as it's the Voice Service record's sys_id. The 401 on oauth_token.do is a separate problem: it means what's sitting in Parameter Store doesn't match the OAuth Application Registry entry on the ServiceNow side. Ninety percent of the time that's someone pasting the client secret's sys_id instead of the actual secret value, or the application registry record itself being inactive. Check both, and while you're in there confirm the value under that path still points at the right voice-service-id, not a leftover from an earlier attempt.

 

Thank you,
Vikram Karety
Octigo Solutions INC