GetExtensions

Description (v1.41)

INFO This action gets all extensions from the directory where the following logical expression is met:
INFO If (Key1 Operation1 Value1) [AND/OR] [(Key2 Operation2 Value2)]
INFO The result is stored as a comma separated list of extensions in the variable: Result
INFO Note: use double quote to indicate strings value.
INFO Key1: [key1]
INFO Operation1: [operator1]
INFO Value1: [value1]
INFO AND/OR? : [coordination1]
INFO Key2 : [key2]
INFO Operation2 : [operator2]
INFO Value2 : [value2]
INFO Order : [order]
INFO Result : [result]
INFO Max : [max]

Release notes

Show release notes
Version 1.41 - Deprecated
  • Feature: result can be ordered by internal directory field 'group' (M000000)
  • Deprecated: Empty the result before collecting the result (M7130)

Version 1.8.0 - Early deployment
  • Feature: Added the possibility to search for an extension whose home_number or mobile_number match a route defined in the corresponding field (M8972)
  • Dependency:
    • Database Schema module 2.2.0 or higher

Version 1.7.0 - Early deployment
  • Feature: Added the possibility to search on profile parameter value
  • Feature: Added the possibility to search on primary or secondary phone
  • Bugfix: Empty the result before collecting the result (M7130)
  • Dependency:
    • Database Schema module 1.23.0+

Version 1.6.1 - Deprecated
  • Improvement: Compatibility with Communication Server 3 (M7654)
  • Deprecated: Empty the result before collecting the result (M7130)
  • Dependency:
    • Database Schema module 1.23.0+

Version 1.6.0 - Deprecated
  • Feature: added the possibility to look up imported contacts (M0)
  • Deprecated: Empty the result before collecting the result (M7130)
  • Dependency:
    • Database Schema module 1.23.0+

Version 1.5.1 - Deprecated
  • Bugfix: When a limit of 1 result was set, no result was ever returned when used with the Communication Server module (M6085)
  • Deprecated: Empty the result before collecting the result (M7130)

Version 1.5 - Deprecated
  • Improvement: Compatibility with the Communication Server module
  • Deprecated: Empty the result before collecting the result (M7130)

Version 1.4 - Deprecated
  • Bugfix: fixed loop if there is no resultset.
  • Deprecated: Empty the result before collecting the result (M7130)

Version 1.3 - Deprecated
  • Feature: added option to randomize the resulting list
  • Deprecated: CPU load might increase due to loop in asterisk if extension not found.

Version 1.2 - Deprecated

Version 1.1 - Deprecated
  • Deprecated: A loop can cause stability issue

Version 1.0 - Deprecated
  • Deprecated: A loop can cause stability issue

Version 0.0 - Deprecated
  • Deprecated: A loop can cause stability issue

Action parameters

This action retrieves a comma separated list of extensions based on the following logical expression:

  • If (Key1 Operation1 Value1) [AND/OR] [(Key2 Operation2 Value2)] then add the corresponding extension in the list.

ALERT! Limitations and known issues:
  • In version 1.3 and lower, quotes had to be added while specifying value1 or value2. These one must be removed when migrating to a version 1.4 or higher.
  • When looking up for extension in the imported contacts, you cannot use the login key.
  • The match operator can only be used with keys home_number and mobile_number
  • If the match operator is used for both the operator 1 and the operator 2, the coordinator 1 must be OR

Example of use

This action can for example be used to retrieve all extensions of an office and put all devices of the office in a specific queue.

Example (version lower or equal to 1.3):
  • (Office = "Dev") AND (Department = "Engineering")
  • (First name = "John") OR (Last name = "Smith")

Example (version 1.4 or higher):
  • (Office = Dev) AND (Department = Engineering)
  • (First name = John) OR (Last name = Smith)

Example (version 1.8 or higher): If a entry contains a route in the home_number such as "_328879.", the match operator can be used.
  • home_number match "32887954"
Copyright © Escaux SA