AC:
* align config approach with AUI application
* apply the standard way of injecting configuration through boot files.
* removed some files which are already part of RTC CDK and not used in CSC anymore
Note: you have to move your personal "src/config.js" to "src/config/app.js" manually in your working folder.
Change-Id: If5a615f0691631e4410e6780a025fed54133147b
NOTE:
To trigger rule rewriting on CF destinations, you need to create a Rewrite Rule in v1 and assign it to the domain you are using
Change-Id: I0c8f426398014478c01d739a6def240c243efcbf
AC:
Can see the already existing SIP-password in plain text in the dialog
Can input new SIP-password
Can generate new SIP-password
Can save the new SIP-password
Can see a QNotification after successful save action
Can input only a restricted set of characters as in CSCv1 (NOTE: actually it's very strange and I'm not sure that it works properly in V1. For example it does not react on cyrilyc symbols but requires at least one lowercase english character)
TAC:
Reuse the already existing password input dialog that is used for the webpassword
Change-Id: I2cf3af4a330a9efa4102637b59e8a71ec962bd0e
Note: to test it you can add some JS code with translations in commented block. That translation should not apper in en.json file if you execute "yarn run i18n:extract" command
Change-Id: I79f6a8358f3a52578b58044eb02169aaccf62123
- If token is valid the related user is logged in automatically
- Existing user (JWT) in the same browser context gets overwritten
- If token is invalid user lands on login page
- Token is removed from URL after it was processed
Change-Id: Ied1266178281bd10420594ceca3cbd4b84e1490d
Steps to reproduce:
* open broser settings and set any language which is not supported by CSC yet. You can chech that it was applied by executing "navigator.language" in the browser console.
* clean session storage for the CSC
* refresh the page.
** result before the fix: language selector are not displayed
** Expected result: language selector is present and language set to Englist (because it is defined as default language in CSC)
Change-Id: I2d53e649e14e3d82e2a5c1be4f99168971cd258c
NOTE
Affected routes/modules:
- /call-blocking/incoming by 'block_in_clir', 'block_in_mode', 'block_in_list'
- /call-blocking/outgoing by 'block_out_mode', 'block_out_list'
- /call-blocking/privacy by 'clir'
- /call-settings by 'music_on_hold', 'language'
- /pbx-settings by 'clir_intrapbx'
When the controlling profile attribute(s) are all unchecked, the module should disappear from CSC main menu and the route should not be reachable.
For AR, in AUI you need to create a Subscriber Profile with at least one Profile, and assign the newly created profile to the subscriber via Details > Master Data.
Change-Id: Idadcc096643fe58419682042814d3508c015b464
AC:
Can see only used translation keys in en.json
Can see unused Vue.js components removed
Note: here you can see bunch of removed files, all of them were part of unsued routes and were belong to deprecated versions of CallForwarding UI implementation. It was a preparation step to re-collect all used translation keys by i18n:extract tool.
Change-Id: I100896ed1791a766aaf1dbd0e95d61e351b65935
TAC:
Parallelise requests in the user load function which do not depend on each other
Note: it can be optimized better if we lazyload RTCengine and initialize it in a lazy way. But it should be implemented as a separate ticket.
Change-Id: I911cd29b880ab8027b341d7953c6c8337390e19b
AC:
Can click on a main menu point to open Subscriber management
Can see a page opening and loading the page from v1 within v2
Note, to test it locally:
1. you need to create the "quasar.conf.dev.js" file with content like
module.exports = {
public: '',
publicPath: '/v2/',
proxyAPI2localhost: true,
proxyAPIFromURL: 'https://dev-web3-trunk.mgm.sipwise.com'
}
2. "src/config.js" should have
baseHttpUrl: '',
3. to login into system you have to use "username@domain" login !!!
Change-Id: I3af7caeb242a52e573d87c50fe05c9462f95bfb3
- TT#128156 Add QR-Code button to the header
- TT#128157 Add QR-Code render library
- TT#128158 Implement QR-Code generation
- TT#129205 Render QR-Code in the popup
- TT#129224 Create store test and api test (including endpoint mockup)
NOTE
You need to enable sip_phone.show_qr_csc in /etc/ngcp-config/config.yml of your environment to be able to see the QR code icon
Change-Id: Ifa065ef057549696387026c5a62cf0f5297ffb05
Historically the i18n label 'English' is not really a languare but
a label to search the localisation name, which should be 'Русский' for Russian.
Change-Id: I404a06a90c582f999d0226e8d6fd6882f741f7b4
Fixed:
* translations for the first item in main menu "Start new call"
* fixed not translated page titles and back button in browser history
* fixed route for 404 page
* fixed intermittent issues with history by switching to Meta plugin instead of direc "document.title" call (bug was next: sometimes you can see current page in the history list as a previous route). It's the same solution that we have in AUI
Change-Id: Iea95e11911a76a5778fefe8320fc39f1934f8a6d
Add new translations to French.
Untranslated strings are skipped now (instead of being kept with empty
values).
Change-Id: If306e414fdf873d494718cb96f22dad5e798e04f
Primary color: Interactive elements (Buttons, MenuItems, Icons, etc. ...)
Secondary color: Background
Important: The color scheme is dark, therefore the primary
colour must be a light color and the secondary must be darker one.
Change-Id: Id499930dd56757416ec027cb36adfe0aeb31e74d
Carlo Venusino
Hugo Zigha
Sergii Leonenko
Hans-Peter Herzog
Victor Tsvetov
Alexander Lutay