07-04-2013, 06:43 AM
Update:
The key to this issue is the paths used in the vpn.cnf file. You may get a successful upload but unless you accurately reference the location of the files things are not going to work and an examination of the phones log will indicate that it can't find the files. The previous T28 or early t38 path format will not work!
The correct paths for the T4XG are:
ca /config/openvpn/keys/ca.crt
cert /config/openvpn/keys/client.crt
key /config/openvpn/keys/client.key
The exportable T38G (2) style client.tar files in the Pfsense OPENVPN package match what is needed for the T4XG.
Also key to getting RTP audio to work is by adding your VPN subnet to the localnet entry in Asterisk.
Example localnet=192.168.2.0/255.255.255.0
Read up on multiple localnet entries in SIP config.
You may find this Yealink guide helpful except for the path information:
ftp://ailsa:6br6pcyl@ftp.yealink.com/OPEN-VPN.rar
------------------------------------------------
Is the OPENVPN tar file structure on the T46G the same as the 38? 28? Any OPENVPN docs specific to the T46G available? I already have the existing Yealink OPENVPN doc which is now a bit out of date and does not address the T4X series.
Update: The phones log indicates that it can't find the clients1.crt file which I've specified (including path) even though it is in the uploaded tar file which is in the proper format. The tar file is accepted during the upload.
So this may be a path issue, unique to the T46G that Yealink needs to clarify. The crt file is being placed somewhere in the phone file system the question is where.
I did notice a /factory/openvpn directory in the log files but that didn't seem to be it.
The key to this issue is the paths used in the vpn.cnf file. You may get a successful upload but unless you accurately reference the location of the files things are not going to work and an examination of the phones log will indicate that it can't find the files. The previous T28 or early t38 path format will not work!
The correct paths for the T4XG are:
ca /config/openvpn/keys/ca.crt
cert /config/openvpn/keys/client.crt
key /config/openvpn/keys/client.key
The exportable T38G (2) style client.tar files in the Pfsense OPENVPN package match what is needed for the T4XG.
Also key to getting RTP audio to work is by adding your VPN subnet to the localnet entry in Asterisk.
Example localnet=192.168.2.0/255.255.255.0
Read up on multiple localnet entries in SIP config.
You may find this Yealink guide helpful except for the path information:
ftp://ailsa:6br6pcyl@ftp.yealink.com/OPEN-VPN.rar
------------------------------------------------
Is the OPENVPN tar file structure on the T46G the same as the 38? 28? Any OPENVPN docs specific to the T46G available? I already have the existing Yealink OPENVPN doc which is now a bit out of date and does not address the T4X series.
Update: The phones log indicates that it can't find the clients1.crt file which I've specified (including path) even though it is in the uploaded tar file which is in the proper format. The tar file is accepted during the upload.
So this may be a path issue, unique to the T46G that Yealink needs to clarify. The crt file is being placed somewhere in the phone file system the question is where.
I did notice a /factory/openvpn directory in the log files but that didn't seem to be it.