2021-04-14 | Migrating Phonon to Cloud

Summary

We are moving from Data Centre model to Cloud Compute model to reduce risks, enable flexibility and scalability in technical operations.
Calling has been migrated to cloud. No actions or attention is required.
SMSs are yet to be migrated. We are recommending usage of sms.phonon.in instead of c4c.phonon.in to send SMSs.

Does it impact me?

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

Why are we making these changes?

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.
Using this opportunity, we are accelerating our plan to move from data centre model to cloud compute model
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.
We are 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?

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.
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).

Further Details:

Why is the domain change impacted?

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.
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

For any more information or any query, you can reply to this email and we will get back to you as soon as possible.