Hi Douglas,
    Please check my inline comments...

Regards,
Kumaran T


On 10/4/2011 2:53 PM, Douglas Hubler wrote:
> On Tue, Oct 4, 2011 at 2:18 AM, Kumaran T
> <[email protected]>  wrote:
>>    I have CSV file which contain users and phones.So after installing  the
>> new build 4.5.2 I imported the CSV file and data is replicated to config UI
>> with the warning message(Please check the screenshot and attached CSV
>> file)Whether its a valid behavior?
> CSV export does not (can not) export pin so it sticks in an off
> message into the CSV file in that field.  If you turn around and try
> to import that, you'll get that message.  Best we can do is add help
> text, explaining this, if it's not already on the page.
        CSV exports pin in encrypted form like  
"stresstest.ttplservices.com#8e1d355565a3b0960c7b03fe304efd8e" clear 
text will be 1234 because for testing purpose we should to give 1234 as 
pin.So while import it displays the warning message"unable to import 
pin.VM pin had been reset" but I can access the user portal or 101 with 
pin 1234.So I just wonder why its displays the warning message..
>> Then I made a call from user 200 to 201
>> without any problem.When I trying to login to bria,that time bria throwed a
>> error message.So I checked the
>> "/var/sipxdata/configserver/phone/profile/tftproot" but there is no phones
>> present..Then I send profiles to some phones then the files was  replicated
>> and present in tftp root only for sent profiles phones.
>>    So if we import a CSV file then the phones will not be present in the Tftp
>> root until we send profiles?
> correct.  you're not the first person to be surprised sending profiles
> is not automatic after making edits.  we kicked around some idea on
> how to balance explicit control of when to update phones v.s.
> automatic and i don't recall anything jumping out as good idea.
        Thanks.So we can add a help text that once import is done then 
phones should send profiles manually...

_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/

Reply via email to