ckleea

Another difference in this firmware is logger. You can see once can click on notice, error, warnings ...
ckleea 發表於 2010-8-17 21:23

This is an interesting feature. If I can enable or disable the logger.

ckleea

I have flashed the latest 350 firmware. My SSH connection is much faster now. Almost the same as I connect to centos server.

CPU utilization is low when idle.

角色

I have two questions about the Switchfin as follows:

1) How about the performance of G729 codec?

2) How about the FXO module in IP-01, does it function after using Switchfin firmware?

YH

ckleea

FXO port is IP01 is of no problem.

For G729, I have not checked in details. Try some time later as my HGC network seems to have problem (the ethernet modem).

ckleea

An update, the new firmware supports dynamic DNS client update. So it can use as a standalone product if you can prevent hacker to log in and disable all paid phone services.

角色

You means the WAN port of IP-01 has a PPPoE Dialler to the ADSL modem?

YH

ckleea

No, if you set your IP01 to obtain IP from DHCP, or given a static IP, you can directly connect the box to ISP. The built in dynamic DNS client will help you to update your IP and point to a host name for easy access.

ckleea

Other information about IP01 firmware:

http://switchvoice.com/index.php ... 5:news&Itemid=2

IP01/IP01p major release           PDF           Print           E-mail
Monday, 30 August 2010 00:00

New firmware (uImage-ip01-v358.img) for IP01/IP01p has been released.

This is a major release so we recommend it. It is equipped with GUI 4.0 which is going to become our default GUI.
Keep in mind that the users manual from the site describe GUI 3.0. We will update them soon.

In this release fax2email is not based on Spandsp but Attrafax

From this release we are changing the revision numbering. The new numbering represents directly Switchfin SVN   
revisions so it easier to be tracked.


It is always a good idea to BACKUP your configuration files and custom voice prompts (if any) before upgrading!
Firmware you can find at the download section of the site

--------------------
I have compiled a copy on hand but don't have time to test the Attrafax functions. Other issues I encounter before have been resolved.
Slow SSH connection, a workaround is available.
High CPU utilization, resolved for no other reason.


The GUI will be going to have multi-language.

ckleea

I have installed a copy of the latest firmware.

角色

Have you test the function of cron if it works or not? Also the stability of the new firmware?

YH

ckleea

回復 55# 角色


    Please suggest a script to test.

ckleea

Please also note that my switchfin has VPN built in as well.

n2n VPN           PDF           Print           E-mail
Monday, 14 September 2009 00:00

New package for Layer 2 Peer-to-Peer VPN was added in Switchfin. It opens series of new features of an encrypted (twofish based) speech communication. In addition it can simplify the network configuration in case the PBX is behind symmetric or asymmetric NAT. To confirm the basic functionality I have done a simple test. Let me describe it here.



For establishing of the simplest possible VPN tunnel apart of the two communicating Edge Nodes one extra Super Node is needed.

Initial tests was done using three BR4-Appliances manufactured by SwitchVoice Ltd . An example is shown below. The prompts of the BR4-Appliane devices was annotated so it is clear where the specific command is executed.

[More...]

Let’s start the Supernode service on one of the BR4-Appliance. The IP of this Appliance is 192.168.1.99 and the Supernode service is listening on TCP/UDP port 20. For this simple test all of the Appliances are in the local network. In reality Edge Nodes should have connectivity to the listening port of the Supernode

root@br4_supernode:~> supernode -l 20
06/Sep/2009 11:33:15 [supernode.c: 477] Supernode ready: listening on port 20 [TCP/UDP]

Let’s start creating the VPN network.

root@br4_edgenode1:~> edge -a 10.1.2.1 -c mynetwork -k encryptme -l 192.168.1.99:20 &
06/Sep/2009 07:35:20 [ edge.c:1138] Using supernode 192.168.1.99:20
06/Sep/2009 07:35:20 [tuntap_linux.c: 38] Interface edge0 has MAC 667:A3:3E:BE:94
06/Sep/2009 07:35:20 [ edge.c: 670] Registering with supernode
06/Sep/2009 07:35:20 [ edge.c:1370]
06/Sep/2009 07:35:20 [ edge.c:1371] Ready
06/Sep/2009 07:35:20 [ edge.c:1037] Received REGISTER_ACK from remote peer [ip=192.168.1.99:20]
06/Sep/2009 07:35:20 [ edge.c:1437] STATUS: pending=0, operational=0

In the edge command above mynetwork is the name of the created VPN nethwork and encryptme is the encryption key associated with this Edge Node.

New virtual Ethernet interface edge0 is created.

root@br4_edgenode1:~> ifconfig
edge0 Link encap:Ethernet HWaddr 5A:9C:0C:2B:ED:08
inet addr:10.1.2.1 Bcast:10.1.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1400 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500

eth0 Link encap:Ethernet HWaddr 00:09:45:56:21:A0
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:86 errors:0 dropped:0 overruns:0 frame:0
TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000

lo Link encapocal Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0

Lets do the same for the second Edge Node but this time will give different VPN IP address 10.1.2.2
root@br4_edgenode2:~> edge -a 10.1.2.2 -c mynetwork -k encryptme -l 192.168.1.99:20 &

Now we can ping one of the Edge Node from the other through the new VPN tunnel, and vice versa.

root@br4_edgenode1:~> ping 10.1.2.2
PING 10.1.2.2 (10.1.2.2): 56 data bytes
64 bytes from 10.1.2.2: seq=0 ttl=64 time=3.237 ms
64 bytes from 10.1.2.2: seq=1 ttl=64 time=3.010 ms
64 bytes from 10.1.2.2: seq=2 ttl=64 time=2.980 ms
…

root@br4_edgenode2:~> ping 10.1.2.1
PING 10.1.2.2 (10.1.2.1): 56 data bytes
64 bytes from 10.1.2.1: seq=0 ttl=64 time=3.237 ms
64 bytes from 10.1.2.1: seq=1 ttl=64 time=3.010 ms
…

The new package can be used for easy creation of a secure voice channels.
For more information about the actual VPN implementation please take a look at n2n

Dimitar Penev

ckleea

回復 51# 角色

Inadyn - DynDNS client for Switchfin           PDF           Print           E-mail
Written by Administrator   
Monday, 30 August 2010 09:38

Hi Guys,

Inadyn is included in Switchfin. Now you can use DynDNS services to get personal URL assigned to the PBX's static or dynamic IP
GUI support will be added very soon.

If you would like to play with the configurations manually you need to edit to addjust /etc/inadyn.conf with your account information form DynDNS

Then you can load the dns client like this

/etc/init.d/inadyn start

Your feedback is welcome.
Dimitar

角色

Good news! It looks more feature is coming for Switchfin.

YH

角色

回復  角色


    Please suggest a script to test.
ckleea 發表於 2010-9-4 15:15

I shall let you know later since I have to find out.

YH