Page History

Get Calling Name

The Get Calling Name function attempts to retreive retrieve a name for the caller. The calling number is searched using the AD attributes of msRTCSIP-Line, mobile, and telephoneNumber. Of course, you may modify this search to suit your requirements.

1. Add a Transformation Table.

   Image Removed

   Transformation Table: Get Calling Name
   Add a Transformation Table as above. In the example,

   For details, refer to Creating and Modifying Entries to Transformation Tables. Use the configuration details below. 
   
   For example, using the configuration below, the AD attributes mobile, msRTCSIP-Line, and telephoneNumber are searched using the calling number. If a match is found, the displayName is retrieved and stored in the Calling Name IE.

   Caption
   0 Table 1 Add Transformation Table
   InputField Type Input Field Value Output Field Type Output Field Value Match Type Calling Address/Number =msRTCSIP-line=|=mobile=|=telephonenumber= Calling Name =displayName= Mandatory

2. Create an Entry in the Action Set Table.

   Image Removed

   Calling Name Action Set Entry
   Add an entry to the main Action Set using the Calling Name Translation Table you just created

   For details, refer to Managing Action Configurations. Include the Transformation table included above.

   Important Notes

   Tip

   There are several methods which can be utilized to perform this AD search: A simple lookup (=msRTCSIP-Line=) will work well if you want to search a single AD attribute. A complex lookup using regex, like the lookup in Step 1, can search multiple entries simultaneously. Beginning in UX Version 2.2, a new double-equal AD lookup function is supported (e.g. ==msRTCSIP-Line==). A new request to the AD server is made for each double-equal AD lookup contain in a Transformation Table.

   Pagebreak

   Info
   For single-equal AD Lookups: Remember that the first valid AD lookup in a Translation Table returns all the AD attributes for that user. Any subsequent AD lookup within that same Translation Table will internally query the attributes returned in the first lookup--it will not make another request to the AD itself.

   Note
   For double-equal AD Lookups: Avoid using this functionality liberally. Requests to the AD server are time-consuming. A heavy load of AD queries will negatively impact call processing time. You should only use this function if, within a Translation Table, you need to perform an AD lookup of two or more user's AD records.