Skip to content

Releases: 2600hz/monster-ui-voip

5.3.9.2

08 Mar 20:56
Compare
Choose a tag to compare

Generic badge

Changes for 5.3.9.2

Changes to branch fix-5.3.9 after version 5.3.9.1.

Commits

5.1.26.1

08 Mar 17:25
Compare
Choose a tag to compare

Generic badge

Changes for 5.1.26.1

Changes to branch fix-5.1.26 after version 5.1.26.

Commits

5.3.9.1

06 Mar 23:23
Compare
Choose a tag to compare

Generic badge

Changes for 5.3.9.1

Changes to branch fix-5.3.9 after version 5.3.9.

Commits

5.3.9

29 Dec 21:27
4c6a2f6
Compare
Choose a tag to compare

Generic badge

Changes for 5.3.9

Changes to branch 5.3 after version 5.3.8.

Commits
  • MSTR-275: do not require sub module, let core handle it - by Hesaam Farhang

    If the app assets is loading from external source_url, if the app tries to require its sub modules directly it will fail and the app won't load at all.

    Changing the module name to its external source_url as what Monster UI core was previously doing won't always work in case the sub modules were small enough and optimized away in a single file as app.js. This has been observed with branding and call-recording apps so far.

    Instead we can explicitly config the paths for sub module and its external source url for requirejs to load it, if it is not already optimized in the app.js.

    Without this change, because app.js is requiring the submodules, this URL will be used instead of external source_url:

    
    http://{monster_ui_url}/apps/:appname/submodules/{submodule}/{submodule}.js
    
    

    requireSubModule from monster.apps.js will require all submodules defined on the app and can adds external source_url of the sub module in requirejs config so the correct URL will be used for fetch if it is needed:

    
    http://{app_metadata.source_url}/submodules/{submodule}/{submodule}.js
    
    

    Read more: https://requirejs.org/docs/jquery.html#modulename

  • MSPB-253: Implement 'Always On, Busy, and No Answer' Call Forwarding Feature - by Ramen Romana

    Introduced enhancements to the Call Forwarding feature, integrating 'Always On, Busy, and No Answer' modes and changes to Call Failover.

    1. Feature Extension: Expanded Call Forwarding functionality to include 'Always On', 'Busy', and 'No Answer'.

    2. Decoupled Call Failover: Segregated 'Call Failover' into an independent feature module, for structural clarity in feature configuration and call management.

    3. Object Structure Overhaul and Backward Compatibility: Implemented the new call_forward object schema and ensured backward compatibility with legacy/no-strategy structures.

    Please refer original/master branch PR #493 for additional information.

  • MSPB-315: Updated cross-site message based routing - by Ramen Romana

    Moved from flag/bindEvents based cross-site message routing to event subscribe.

  • MSPB-344: Fix Duplicate TTS Generation in SmartPBX with Timestamp Versioning - by Ramen Romana

    Implement timestamp versioning for TTS updates in SmartPBX to prevent duplicates. Now, each TTS update appends new Date().getTime() for uniqueness.

5.1.23.2

12 Dec 19:41
Compare
Choose a tag to compare

Generic badge

Changes for 5.1.23.2

Changes to branch fix-5.1.23 after version 5.1.23.1.

Commits

5.2.3

20 Nov 03:32
d1e75bf
Compare
Choose a tag to compare

Generic badge

Changes for 5.2.3

Changes to branch 5.2 after version 5.2.2.

Commits

5.1.26

08 Nov 01:58
3af0dd3
Compare
Choose a tag to compare

Generic badge

Changes for 5.1.26

Changes to branch 5.1 after version 5.1.25.

Commits

5.3.8

01 Nov 15:33
0fc49ea
Compare
Choose a tag to compare

Generic badge

Changes for 5.3.8

Changes to branch 5.3 after version 5.3.7.

Commits

5.1.25

01 Nov 15:26
f782007
Compare
Choose a tag to compare

Generic badge

Changes for 5.1.25

Changes to branch 5.1 after version 5.1.24.

Commits

5.1.24

30 Oct 22:54
f782007
Compare
Choose a tag to compare

Generic badge

Changes for 5.1.24

Changes to branch 5.1 after version 5.1.23.

Commits