Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Anchor
_mh7de4v59u1o
_mh7de4v59u1o
Overview

This article explains the different use cases for assigning SMS numbers to configurations within the Curbside, Send, and Ugent Notify Sangoma apps.

Note: When an SMS Number is removed from all configuration the number becomes available for use in a different application. Before using the number in a different application it must be re-registered in the SMS campaign Registry using the Sangoma’ SMS Campaign Registration App. Re–registering an SMS Number requires you to delete the original campaign registry and submit a new registry. For more campaign registry instruction reference the SMS Campaign Registration App User Guide.

Anchor
_w5ww59wjp1y2
_w5ww59wjp1y2
Use Cases

Anchor
_gumgfzxvk9zp
_gumgfzxvk9zp
New config

  1. Create a new config with no other existing configs:

    1. Select SMS number from list

    2. Complete and save changes

    3. Expected result:

      1. SMS number is assigned to the application

  2. Create a new config in addition to existing configs:

    1. Select same SMS number as existing config(s)

    2. Complete and save changes

    3. Expected result:

      1. SMS number is still assigned to the application

  3. Create a new config in addition to existing configs and use diff SMS:

    1. Select a different SMS number from existing config(s)

    2. Complete and save changes

    3. Expected result:

      1. SMS number is assigned to application

      2. SMS from other configs is still assigned to the application

Anchor
_xr82wlac97pu
_xr82wlac97pu
Edit existing config

  1. Edit config with no other existing configs:

    1. Select different SMS number from list than previously assigned

    2. Complete and save changes

    3. Expected result:

      1. New SMS number assigned to the application

      2. Old SMS number is unassigned

  2. Edit config with multiple configs assigned to the same number:

    1. Edit one of the configs and select different SMS number

    2. Complete and save changes

    3. Expected result:

      1. New SMS number assigned to the application

      2. Old SMS is still assigned to the application (used by other configs)

Anchor
_y772bocwxa79
_y772bocwxa79
Delete config

  1. Delete config (SMS number is only used in a single config):

    1. Expected result:

      1. SMS number is unassigned

  2. Delete config (multiple configs using the same SMS number):

    1. Expected result:

      1. SMS number is still assigned to the application (used by other configs)

  3. Delete config (multiple configs using the same SMS number):

    1. Setup

      1. Create 4 configs, two with SMS xxx and two with SMS yyy

    2. Delete one of the configs that is using SMS xxx

    3. Expected result:

      1. Both sms xxx and yyy are still assigned to the application

    4. Delete the other config that is using SMS xxx

    5. Expected result:

      1. SMS xxx is unassigned and is now available for use in this and other apps.

      2. SMS yyy is still assigned to the application


Page Properties
hiddentrue

Click here ( https://sangoma.atlassian.net/wiki/spaces/PMGMT/overview ) to locate this Product Manager.

Source Document URL:

https://docs.google.com/document/d/1EjQCDhwulL2m32Tr3GeEJhO1szG-XeGeUsjVd9OEcuE/edit

Original KB URL:

https://knowledge.star2star.com/kb/3419

Access level (Everyone, Partners, Internal)