2021-04-15 | Migrating Phonon Core to Cloud

Summary

• We are moving from Data Centre model to Cloud Compute model to reduce operating, technical and business risks, enable flexibility and scalability in technical operations.

• All data circuits and access of portals is being migrated to AWS Cloud Operating from AWS Mumbai.

• Partial calling has been migrated through our cloud infrastructure located at AWS Mumbai.

• Please review the below changes. These changes are being deployed progressively between 15-Apr-21 to 28-Apr-21; therefore we request you to review and adapt to the below changes at earliest.

Does it impact me?

If you’re receiving this email, we need your attention and action for a minor change. There are no major impact on any services.

Why are we making these changes?

1. We have a business risk with our existing data centre belonging to Reliance Communications DAKC. NCLT has begun bankruptcy process for Reliance Communications^[1] and therefore we are proactively moving our operations out.

2. Using this opportunity, we are accelerating our plan to move from data centre model to cloud compute model

3. By being a complete cloud solution, it enables us to:

   1. Scale up rapidly as we need

   2. Improve the processing power of our applications

   3. Have a more reliable, flexible and secure infrastructure

What are the changes?

• We are transitioning our services from Data Centre model to Cloud Computing model and therefore moving our services from the Mumbai DAKC Data Centre to AWS Cloud Compute, at Asia Pacific - Mumbai (ap-south-1) location.

How does it impact me? What do I need to do?

1. Change In Domains and IP Addresses:

2. Change SMS gateway access domain:

• Now with the calling applications going online if you use c4c.phonon.in the operations will be delivered from AWS Cloud and SMS services are yet to be migrated. And therefore to disambiguate between the two we are recommending usage of sms.phonon.in instead of c4c.phonon.in to send SMSs. So replace https://c4c.phonon.in/BulkSMS with https://sms.phonon.in/BulkSMS

3. Change PhononUC access domain:

• Same as Sr. 2 above, we are recommending usage of uc.phonon.in for PhononUC application. Replace https://c4c.phonon.in/PhononUC with https://uc.phonon.in/PhononUC.

4. Change Email gateway access domain:

• Same as Sr. 2 above, we are recommending usage of email.phonon.in for BulkEmail application. Replace https://c4c.phonon.in/BulkEmail with https://email.phonon.in/BulkEmail.

5. Use Single Domain for OBD calls:

• Same as Sr. 2 above, we are recommending usage of obd.phonon.in for Auto OBD application. Replace https://c4c.ponon.in/obd with https://obd.phonon.in/obd.

6. Append new IPs for whitelisting:

• If you have done any whitelisting at your end of IP addresses for accessing our applications from your network, please change them to domain level whitelisting, as the IPs will be dynamic:

• If any of our Applications access your network, and you have whitelisted our IP addresses, then for our application to access your network please make the following changes:

5. Change DID / Mobile numbers:

• Your relationship manager will reach out to you soon for any changes required on your end.

What about Data Security?

• Data security is always our prime focus, and we ensure that your data remains completely secure with our cloud providers.

• In order to provide Security of the Cloud, AWS environments are continuously audited, and the

  infrastructure and services are approved to operate under several compliance standards and

  industry certifications across geographies and verticals.

• Customers can use these certifications to validate the implementation and effectiveness of AWS security controls, including internationally recognised security best practices and certifications including ISO 27001, ISO 27017, ISO 27018, ISO 9001, PCI DSS Level 1 and SOC.

• Further, Amazon Internet Services Private Limited, an Indian subsidiary of the Amazon Group which undertakes the resale and marketing of AWS services in India, has achieved full Cloud Service Provider (CSP) empanelment, and successfully completed the STQC (Standardisation Testing and Quality Certification) audit from the Indian Ministry of Electronics and Information Technology (MeitY) for cloud services delivered from the AWS Asia Pacific (Mumbai) Region. For more information about AWS certifications and attestations, see the AWS Assurance Programs webpage. For information about general AWS security controls and service-specific security, see the Amazon Web Services: Overview of Security Processes white-paper.

• You can read more about the security & compliance of AWS here: https://d1.awsstatic.com/whitepapers/compliance/AWS_User_Guide_for_Banks_in_India.pdf

Who shall reach out to for any query?

Please reach out to your relationship manager for any further query. You can also reach out to help@phonon.io for any support as well.

More Details:

Why is the domain change impacted?

1. Our instant call connect services are accessed through c4c.phonon.in domain. For sms services the domain name has always been sms.phonon.in. Since there was no material impact in accessing the servers from any of the URL, we continued using c4c.phonon.in.

2. Now with the calling applications going online if you use c4c.phonon.in the operations will be delivered from AWS Cloud and SMS services are yet to be migrated. And therefore to disambiguate between the two we are recommending usage of sms.phonon.in. For your reference please see the output of dig command. This shows both c4c.phonon.in and sms.phonon.in at the moment terminate at same IP 220.225.53.130 (which is our existing data centre location).

When will SMS services be migrated to cloud compute environments?

• We intend moving the SMS services to the cloud compute environment in the next 2-3 weeks after this migration of calling is completed.

Output of dig c4c.phonon.in

$ dig c4c.phonon.in

; <<>> DiG 9.10.6 <<>> c4c.phonon.in
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18513
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280

;; QUESTION SECTION:
;c4c.phonon.in.			IN	A

;; ANSWER SECTION:
c4c.phonon.in.		48	IN	CNAME	bom.phonon.in.
bom.phonon.in.		299	IN	A	220.225.53.130

Output of dig sms.phonon.in

$ dig sms.phonon.in

; <<>> DiG 9.10.6 <<>> sms.phonon.in
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52451
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280

;; QUESTION SECTION:
;sms.phonon.in.			IN	A

;; ANSWER SECTION:
sms.phonon.in.		144	IN	CNAME	bom.phonon.in.
bom.phonon.in.		293	IN	A	220.225.53.130