-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New API proposal-Verified Caller #27
Comments
PR available in camaraproject/WorkingGroups#410 |
Question: If a fraudulent call is initiated while also sending a fraudulent SMS/RCS message in the format used by the operator, how can the called user identify it? |
Hello. Could you please provide more details about the technical implementation of this API, including the underlying technologies used? Additionally, we would like to better understand how this API differs from other approaches, such as the eCNAM-based branded calls API, which may also come within the OGW drop#4. |
Supporting material available here |
Hello @DanXu-ChinaTelecom, @Jason-ZTE As for 16-05 TSC Minutes the API is approved and I need you to provide the initial maintainers and codeowners from your side for the upcoiming Verified Caller GitHub Repository |
thx @TEF-RicardoSerr ,we proposed initial codeowners: DanXu-ChinaTelecom and Jason-ZTE @Jason-ZTE , and initial maintainers as follows:
|
Subproject have been created here. Closing this issue |
This API allows accurate operator-certified "Verified Caller" information, including SMS and video clips, to be displayed on the phone screen of the called user before they answer the call. This API enables enterprise customers to vividly present their multimedia business cards and reduces the incidence of malicious calls.
It is applicable to customers in industries such as government, finance, express delivery, healthcare, education, etc., who have outbound call requirements.
For instance, when a hospital arranges follow-ups and communication between customer service and rehabilitation patients, patients might doubt the hospital's identity and typically refuse the calls. By utilizing this API, the hospital's identity can be displayed, thereby improving connection rates and significantly enhancing customer service satisfaction.
The text was updated successfully, but these errors were encountered: