javier.delolmo | 2019-10-22 06:08:58 UTC | #1
Why in the front of Purecloud we only can use a E164 calling party number and in the API PUT /api/v2/routing/queues/{queueId} we can change calling party number with a non E164 identifier?
javier.delolmo | 2019-10-22 06:13:29 UTC | #2
We have a problem when we set the queue calling party number with API and later we do a change of these queue in Purecloud front because in this last change the front convert the calling party number in a E164 number.
tim.smith | 2019-10-22 14:40:31 UTC | #3
Questions about the PureCloud base product and UI are better suited for the PureCloud Community Forum or opening a case with PureCloud Care.
javier.delolmo | 2019-10-25 06:32:41 UTC | #4
Thanks Tim. I'm going to post this in Community Forum.
system | 2019-11-25 06:32:41 UTC | #5
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 6315