automate mac.cfg encryption

[olivier]

Hi,

I need to automate the provisioning file encryption. is it possible to use the openssl CLI to do that ?

is somebody have the correct syntax ?

regards,
Olivier

[VOIP]

You can Use this one if you have linux-

http://www.yealink.com/Upload/T2X/201311...20Tool.zip

Unfortantly Yealink does not offer a command line version for Windows users.

I wish they would.

[olivier]

thanks for your answer.

regards,
Olivier

(12-13-2014 12:40 AM)VOIP Wrote:  You can Use this one if you have linux-

http://www.yealink.com/Upload/T2X/201311...20Tool.zip

Unfortantly Yealink does not offer a command line version for Windows users.

I wish they would.

[VOIP]

Any one who has windows ideas chime in :-)

As Polycom Aastra Panasonic Cisco all offer "automated" command line/prompt options.

[James_Yealink]

Hi All,

Please try attached AES encryption tool.

Regards,
James

[VOIP]

(01-02-2015 01:57 PM)Yealink_James Wrote:  Hi All,

Please try attached AES encryption tool.

Regards,
James

James,

Can we create y000000000000_Security.enc with this tool?

[James_Yealink]

No, it can only be used to encrypt or decrypt a cfg file but create a .enc file.
May I know why do you need it?

James

[kapetrosyan]

Why you want to encrypt y0000000000.cfg file?
If you need it to hide the provisioning server information, you can simply remove them from y000000000000.cfg, and add to {MAC}.cfg and then encrypt {MAC}.cfg

---

(01-03-2015 04:36 AM)VOIP Wrote:  

(01-02-2015 01:57 PM)Yealink_James Wrote:  Hi All,

Please try attached AES encryption tool.

Regards,
James

James,

Can we create y000000000000_Security.enc with this tool?

VOIP,
Why you want to encrypt y0000000000.cfg file?
If you need it to hide the provisioning server information, you can simply remove them from y000000000000.cfg, and add to {MAC}.cfg and then encrypt {MAC}.cfg

[VOIP]

kapetrosyan and Yealink_James,

I have a thousand phones deployed.
I can add and then remove the y0000000000.cfg every time anew phone gets plugged in.

The purpose Yealink created the .enc is to allow you to remotely provision a phone with out much effort.
For starters if you have RPS and an .enc you in short can deploy phones with out any effort. (Meaning you set it up and the ned user can plug it in at anytime you do not need to collaborate the first plug in).

In reality the point of .enc is for the "big boys" and yet its created in a way only the smaller ones can use. (except if you have a linux server).

Yealink_James your thoughts?

[VOIP]

Yealink_James?