Hi
Vaun,
Thanks for your reply, yes the service provide uses a prefixe in order to block call ID by call basis, but when we use this prefix, it is not reconized by Purecloud due that it uses only E164 format
For example, the prefix to block the number is 361 and when I dial the number prefix + number, the Purecloud add "+" in the from of the number:
Prefix: 361
Number: +33012534789
We dial 361 0123456789 => Purelcoud displays +3610123456789
Any idea ?
Thank you.
------------------------------
Mostafa Oudderhem
Coverage-Communication
------------------------------
Original Message:
Sent: 07-03-2020 20:59
From: Vaun McCarthy
Subject: How to block outgoing caller ID for a user in Purecloud ?
HI Mostafa
That may depend on your SIP trunk provider as there are several ways of them handling this and their own setup will control what you can/can't do. First step would be asking your provider what method they support and can handle. Some can take a prefix passed through with the call, others need the privacy header set which would need to be done globally.
------------------------------
Vaun McCarthy
NTT New Zealand Limited
Original Message:
Sent: 07-03-2020 09:53
From: Mostafa Oudderhem
Subject: How to block outgoing caller ID for a user in Purecloud ?
Hi,
I have a question regarding the outbound caller ID for an agent, how to block it and show "unkown number" for called customers ?
Is there any configuration to do on Purecloud ? it is applied globaly (system wide) ? or we can apply it per user or per call ?
Thank you in advance for your answers.
Regards.
#Outbound
#Routing(ACD/IVR)
#SIP/VolP
#SystemAdministration