If you set a phone number at the tenant level and create an extension that number will be listed as the assign default to that extension BUT if you change the number on the tenant level the system "should" update the extension file to reflect that change.
PROBLEM the old number will remain the assigned default until you go into each extension and save the settings NOTE: no changed need to be made just edit and save.
At this point the extension file "users.txt" is updated and the new outbound number is displayed.
George
Erik, yes we agree and VOTE
Erik,
yes we agree and VOTE #2 : 2) a much simpler solution is TL should not be setting a DB value at the extension level if the default is to be used. There should be no key called TL/tenant-extension/callerid forcing the outbound script to instead use the TL/TENANT/tenantname/callerid as its been programmed to do.
it's the ONLY accessible salutation.. As it is the edit and reload time of getting to the point you can take a smoke break for each mouse click..
As for your temp fix for us.. that's not going to work. The customer needs to have control of out bound caller ID that's what started all this in the first place..
As a result we had two choices 1 go into each extension (32 of them) and simply re-save them OR edit the txt file and reload asterisk.
It all working just thought the powers that be should know about this as i'm sure others will have the same problem..
George
well the txt file wont affect
well the txt file wont affect the running asterisk at all. As for a cleanup I am thinking of a script that goes through users.txt and identify callerid_option=1 and for each of those execute a database delete on the TL/tenant-extension/callerid .
i think i'm understanding what you're saying..
you're saying that the DB entry for the tenant callerid gets changed...
TL/TENANT/tenantname/callerid
and by default if the dialplan cannot find TL/tenant-extension/callerid it would be more than happy using TL/TENANT/tenantname/callerid because thats the first value it gets set to anyway.
but because, for whatever reason, the extension screen decides to set
TL/tenant-extension/callerid = to TL/TENANT/tenantname/callerid whenever you select 'assign default' that now you have a case where updating TL/TENANT/tenantname/callerid has no effect. You are now forced to update each and every extension manually. Now, because TL/tenant-extension/callerid is set to a wrong value, that gets used in the outbound dialing macro.
There are 2 ways to fix this...
1) have the system update each and every DB entry for every extension, this requires recursively going through users.txt for each and every extension and updating the DB values only for the extensions set to assign default.
2) a much simpler solution is TL should not be setting a DB value at the extension level if the default is to be used. There should be no key called TL/tenant-extension/callerid forcing the outbound script to instead use the TL/TENANT/tenantname/callerid as its been programmed to do.
My vote is on #2, as the 'default' value should be set in ONE place, as opposed to several :)
now, as a temporary fix for you, for tenants that are all using this one default, you can select under tenant settings to not allow them to manage callerid settings which will mean that the callerid of the call stops getting set right after its set to TL/TENANT/tenantname/callerid
if #2 gets adopted it will still require a 1 time action of removing those DB keys set to the default value.