Aurora teleQ Azure Migration FAQ
Introduction
Aurora teleQ (www5.teleqone.com / nl.teleqone.com) is being migrated to Microsoft Azure to provide a modern, secure, and scalable platform for future service development.
This FAQ answers the most common questions about the migration and explains what users and administrators need to do before and after migration.
After your migration, Aurora teleQ will be accessed using a new login URL:
https://eu.aurorateleq.com.
All users must use this URL after their migration has been completed.
https://eu.aurorateleq.com.
All users must use this URL after their migration has been completed.
Only after your migration date.
Do NOT start using the new URL before your migration date.
Until your migration has been completed, continue using your current Aurora teleQ login URL.
Do NOT start using the new URL before your migration date.
Until your migration has been completed, continue using your current Aurora teleQ login URL.
The new Azure environment is activated for each customer as part of the migration process.
Before your migration date, your Aurora teleQ instance is still running on the current platform and is not yet available through the new URL.
Before your migration date, your Aurora teleQ instance is still running on the current platform and is not yet available through the new URL.
1. Open Aurora teleQ using: https://eu.aurorateleq.com
2. Update any browser bookmarks or favorites that point to the old login URL.
3. Update any desktop shortcuts that open Aurora teleQ.
4. Update any internal documentation or user guides that reference the old login URL.
2. Update any browser bookmarks or favorites that point to the old login URL.
3. Update any desktop shortcuts that open Aurora teleQ.
4. Update any internal documentation or user guides that reference the old login URL.
Bookmarks and browser favorites that point to the old login URL will continue to open the old address.
After migration, update any saved bookmarks to:
https://eu.aurorateleq.com
Example
Before migration:
https://nl.teleqone.com
After migration:
https://eu.aurorateleq.com
After migration, update any saved bookmarks to:
https://eu.aurorateleq.com
Example
Before migration:
https://nl.teleqone.com
After migration:
https://eu.aurorateleq.com
If you have a desktop shortcut that opens Aurora teleQ, it may still point to the old login URL.
After migration, create a new shortcut or update the existing shortcut so that it opens:
https://eu.aurorateleq.com
After migration, create a new shortcut or update the existing shortcut so that it opens:
https://eu.aurorateleq.com
Many web browsers store usernames and passwords separately for each website address.
Because Aurora teleQ will be accessed using a different URL after migration, your browser may not automatically offer the username and password that were saved for the previous login URL.
This is expected behavior and does not indicate a problem with your account.
Because Aurora teleQ will be accessed using a different URL after migration, your browser may not automatically offer the username and password that were saved for the previous login URL.
This is expected behavior and does not indicate a problem with your account.
No.
Your Aurora teleQ username remains the same.
Your Aurora teleQ username remains the same.
Simply enter your Aurora teleQ username and password manually.
Once you have successfully logged in, your browser can save the credentials again for the new login URL if desired.
Once you have successfully logged in, your browser can save the credentials again for the new login URL if desired.
Before migration, users should verify that they know their Aurora teleQ username and password.
If you do not know your password, you can use:
Forgot Password
on the Aurora teleQ login page.
If you do not know your password, you can use:
Forgot Password
on the Aurora teleQ login page.
No.
The migration moves the service to a new platform but does not change your Aurora teleQ configuration, users, queues, reports, or customer data.
The migration moves the service to a new platform but does not change your Aurora teleQ configuration, users, queues, reports, or customer data.
Possibly.
If your organization uses:
Aurora teleQ API integrations
Web Entrance
External Chat
Other custom integrations
then some URLs may need to be updated as part of the migration.
Organizations affected by these changes will receive migration-specific information before the migration date.
If your organization uses:
Aurora teleQ API integrations
Web Entrance
External Chat
Other custom integrations
then some URLs may need to be updated as part of the migration.
Organizations affected by these changes will receive migration-specific information before the migration date.
IT administrators should review the following network requirements.
HTTP/HTTPS Timeouts
Aurora teleQ uses long-held HTTP/HTTPS requests for:
eu.aurorateleq.com
Network devices must not terminate connections that remain open for up to:
60 seconds
This includes:
Firewalls
Proxy servers
Security gateways
Traffic inspection solutions
HTTP/HTTPS Timeouts
Aurora teleQ uses long-held HTTP/HTTPS requests for:
eu.aurorateleq.com
Network devices must not terminate connections that remain open for up to:
60 seconds
This includes:
Firewalls
Proxy servers
Security gateways
Traffic inspection solutions
Communication with:
eu.aurorateleq.com
must not be cached by proxy infrastructure.
eu.aurorateleq.com
must not be cached by proxy infrastructure.
Any migration-related service interruption will be communicated separately as part of the migration planning process.