caller_id_name variables question

16 Jan 2017

      Hello.

This is a snippet:

<extension name="set_caller_name_db" continue="true">
  <condition field="${user_exists(id ${caller_id_number} $${domain})" 
expression="^false$"/>
  <condition field="${effective_caller_id_number}" expression="^$">
   <action application="set" inline="true" 
data="effective_caller_id_name=${lua(get_name_from_db.lua 
${caller_id_number})}"/>
   <action application="set" inline="true" 
data="origination_caller_id_name=${effective_caller_id_name}"/>
   <action application="set" inline="true" 
data="caller_id_name=${effective_caller_id_name}"/>
   <anti-action application="set" inline="true" 
data="effective_caller_id_name=${lua(get_name_from_db.lua 
${effective_caller_id_number})}"/>
   <anti-action application="set" inline="true" 
data="origination_caller_id_name=${effective_caller_id_name}"/>
   <anti-action application="set" inline="true" 
data="caller_id_name=${effective_caller_id_name}"/>
  </condition>
</extension>

If the caller is not in local users, then try to set caller_id_name from 
database. Script works ok.

My question is which of this three actions setting vars is redundant:
effective_caller_id_name, origination_caller_id_name, caller_id_name

Thank you

Mimiko

Antonio Silva

tags

participants (2)