ramblings…

If you are trying to load firmware on a Blackberry 7230 or 7290 with a recent version of the Blackberry Desktop Manager, it will consistently fail. I encountered such a problem this morning. Tried using JL_Cmder, but still no luck. It would would quit with the error “COM error during open”.  It had no problems connecting to the 8700 and 8310 Blackberrys.

I decided to downgrade the Blackberry Desktop Manager to v3.6 which I had laying around on a memory stick. Installed the v3.6 after a quick uninstall of  v4.7. Tried the firmware load on the 7230  and it went through without a hitch. JL_Cmder also works fine now with both the 7230 and 7290.

Issue discussed in  GSMForums.

The Draytek 2820Vn is a great device for home and small-offices. It has two WAN ports; ADSL and Ethernet. Excellent VPN capabilities 32 simultaneous VPN tunnels (IPSec, PPTP, L2TP and L2TP over IPSec.)

In order to get point to point voice working either on VPN or LAN you need to ensure that

1. the “External IP :” under VoIP -> SIP Accounts is the private IP of the router itself
2. the SIP account in use is configured with  “Register via  LAN/VPN”
3. “NAT Traversal Support” is set to “None”

Troy was trying in vain to get voice calls working. We hit on this combination after quite a bit of messing the parameters. The predecessor of the Draytek 2820Vn (the Draytek 2800VG) does not need these fiddly parameters configured and works just fine without these settings. This coupled with the fact that he’s bought 5 of these devices to internetwork the branch offices of a relative’s company, caused this networking boffin a lot of frustration.

Troy has since gone back to meddling with his favourites Cisco and HP ProCurve, thankful to your truly for having helped put this ordeal behind him!

Some info I posted on ChipOverclock’s blog:

Thot i’d post my experiences with the AVAYA SIP phones.

• The current version of the firmware for the 46xx phones still doesn’t seem to support the message waiting indicator (MWI) light. And as a side-effect of pending voice mail, these phones seem to think they are not registered after a seeming random period of time, refusing to allow outgoing calls. I had to disable voice mail on all extensions with AVAYA phones. Wasn’t too bad, I could live without the MWI.
• The 1.xx version of SIP firmware for the 9620/9630/9640 series of phones would register fine on Asterisk, allow outgoing calls but refuse to accept incoming calls.
• AVAYA have recently release version 2 of the SIP firmware for the 96xx phones. Thought I’d give it a try the other day. I was pleasantly surprised to find that it worked perfectly, including the MWI!! Excellent speaker-phone, and great voice quality.

I’ve been testing it for about 4 days now and am totally happy with the results.

Original post

Quick glance
A power strip with 8 power outlet sockets and 2 power inlets. Each power port can be turned on or off individually over the network. Support for this product on Infratec’s website appears poor at best with documentation being equally sketchy. e.g., the firmware revision on my PM 8-IP is 2.02, whereas the latest available download on the website is v1.26a.
Details
One would be misled into believing that the dual power inlets ensures power redundancy. Unfortunately not, each power inlet can power its own set of 4 power outlets. Hence not entirely useful for critical datacentre operations.
On the networking front, it runs Ubicom’s IP2022 network processor. The network is up and running in about 2 seconds after power up. Pretty impressive. Power to the network processor/controller is supplied only from one of the power sources.
The console serial port (RJ-9 4P4C socket) running at 9600-N-8-1 can be used to configure the IP address and also for performing a factory reset (highly recommended after a firmware up/downgrade.) The unit can be factory reset by pressing “F” (case sensitive) when at the console menu. In some cases the web server becomes in accessible after a firmware upgrade, and a factory reset is required to bring things back in order.

I constructed a console cable from an old RJ-9 jack and a DE9-F connector. Use the table below to wire up the two connectors: