| Table of Contents |
|---|
...
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.
...
1. Change In Domains and IP Addresses:
Services | Existing Domains | Sample OLD URL | Action | New Domains | Sample New URL | |
|---|---|---|---|---|---|---|
| 1 | Click-to-Call | No change | ||||
| 2 | Replace with |
| 3 | Bulk SMSs | Replace with |
| 4 | Phonon UC | Replace with |
No Change
| 5 | Bulk Email |
No Change
Replace with | ||||||
| 6 | Agent Login | No Change | ||||
| 7 | Auto OBD | No Change | ||||
| 8 | Replace with | |||||
| 9 | URL Shortner | No Change | ||||
| 10 | Test site for Click 2 Call, Phonon UC, Auto OBD, Agent Login, Bulk SMS, Bulk Email | No Change |
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.into send SMSs. So replacehttps://c4c.phonon.in/BulkSMSwith 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/PhononUCwith 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/BulkEmailwith 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/obdwith 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:
Services | Existing IPs / Domains | Action | New IPs / Domains | |
|---|---|---|---|---|
| 1 | Click 2 Call, Phonon UC, Auto OBD, Agent Login, Bulk SMS, Bulk Email | 220.225.53.130 | Append with: | 13.248.189.77, 76.223.43.236 |
...
Replace IP whitelisting with domain level whitelisting. See table 1 for all domains. |
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:
Service | Purpose | Previous whitelisted IP | New IP IPs to be whitelisted APPENDED | |
|---|---|---|---|---|
| 1 | Phonon’s Egress | Our application to access your resource, you have whitelisted our IPs at your systems. | 220.225.53.130 | 3.6.119.170 |
| 2 | BDQ-1 (Vodafone) | Subnet | 123.63.40.168/29 | |
| 3 | Production Environment IPs | 123.63.40.170 | ||
| 4 | Test Environment IPs | 123.63.40.171 | ||
| 5 | BDQ-2 (UCOM) | Subnet | 202.160.171.56/29 | |
| 6 | Production Environment IPs | 202.160.171.58 202.160.171.61 202.160.171.62 | ||
| 7 | Test Environment IPs | 202.160.171.59 202.160.171.60 | ||
| 8 | BOM-1 (RCOM) | Subnet | 220.225.53.128/29 | |
| 9 | Production Environment IPs | 220.225.53.130 220.225.53.131 220.225.53.132 | ||
| 10 | Test Environment IPs | 220.225.53.133 220.225.53.134 | ||
| 11 | BOM-2 (Vodafone) | Subnet | 123.63.92.128/29 | |
| 12 | Production Environment IPs | 123.63.92.130 123.63.92.131 123.63.92.132 | ||
| 13 | Test Environment IPs | 123.63.92.133 123.63.92.134 |
5. Change DID / Mobile numbers:
Our support team Your relationship manager will reach out to you soon for any changes required on your end.
...
Data security is always our prime focus, and we have reviewed and ensured ensure that your data remains completely secure with Amazon Web Servicesour 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 recognized 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
...