Posted in June 14, 2009 ¬ 6:41 pmh.
mick
After the Bill and Ben’s departure from the protective environment of the green tent it was time for Huey Dewey and Louie to venture out into the garden. To allow me to monitor these plants it was necessary to install cabling from my work room and up to the end of the garden. After initially putting the guys on the top shelf (their place of preference) I moved them down to the bottom one. This was primarily because I couldn’t get them all into the camera frame.
Due to the mistakes not potting up earlier in the year I am not anticipating fruit this year from these guys. That being said I am as ever an eternal optimist so fingers crossed.
I am desperately trying to get back to the associated projects I was planning. Also I since Bill and Ben are still being attacked by the mystery jaws (you can just see the leaves have holes in them). So I have also considered retrofiting one of the cameras to be infra-red so I can watch over the guys at night.
Posted in June 13, 2009 ¬ 6:17 pmh.
admin
Earlier this week I was offered tomato plants from my father in law. I couldn’t resist my chilli plants bill and ben would have company !!!
So this afternoon with help from my son and :
3 x 72cm (or 28″) green pots
4 x Large Tomato Grow bags
1 x water sprinkler
We started the process of potting potting up nine tomato plants.
Well I’m sure the pictures speak for themselves but whilst arranging the front garden I noticed that bill who is now a staggering 22 inches high. Is too too big for the small green house he was living in. For this reason I have moved both Bill and Ben out of the housing. The housing has been moved to the back garden and the plans are to move Huey Dewey and Louie into it as soon as they’re big enough.
Posted in June 10, 2009 ¬ 8:45 pmh.
admin

Important news
Just a quick note to say Dewey has done me proud and put on a spurt of approximately one centimetre in the last two days !
Careful examination of the dowel I installed in the pot and marked shows the increase in hight.
Which is excellent since this implies little or no trauma caused by the potting up.
A hearty congratulations are required for such a resiliant plant – well done Dewey !
Posted in June 9, 2009 ¬ 11:55 amh.
mick
We have two CME’s and a single shared CUE.
Dialplan
CME1:
3002 – Phone 1
3003 – Phone 2
3200 – AA Script (outside scope)
3600 – Voicemail
3998 – MWI off
3999 – MWI on
CME2:
3004 – Phone 1
3005 – Phone 2
3998 – MWI off
3999 – MWI on
on CME1 (Central)
voice service voip
allow-connections sip to h323
allow-connections h323 to sip
allow-connections h323 to h323
interface FastEthernet 0/0
ip address 192.168.n.1 255.255.255.0
h323-gateway voip interface
h323-gateway voip bind srcaddr 192.168.n.1
interface service-engine 1/0
ip unnumbered FastEthernet0/0
service-module ip address 192.168.n.2 255.255.255.0
service-module ip default-gateway 192.168.n.1
ip route 192.168.n.2 255.255.255.255 Service-Engine 1/0
dial-peer voice 3600 voip
destination-pattern 3[126]00
session protocol sipv2
session target ipv4:192.168.n.2
incoming called-number 399[89]....
codec g711ulaw
no vad
dial-peer voice 3004 voip
destination-pattern 300[45]
voice-class h323 1
session target ipv4:cme2_ipaddress
dfmf-relay h245-alphanumberic
ip qos dscp cs3 signalling
no vad
dial-peer voice 3998 voip
destination-pattern 399[89]300[45]
session target ipv4:cme2_ipaddress
telephony-service
voicemail 3600
ephone-dn 1 dual-line
number 3002
ephone-dn 2 dual-line
number 3003
ephone-dn 3
number 3998....
mwi off
ephone-dn 4
number 3999....
mwi on
on CME2 (remote)
dial-peer voice 3002 voip
destination-pattern 300[23]
voice-class h323 1
session target ipv4:cme1_ipaddress
dfmf-relay h245-alphanumberic
ip qos dscp cs3 signalling
no vad
dial-peer voice 3998 voip
incoming called-number 399[89]....
telephony-service
voicemail 3600
mwi relay
ephone_dn 1
number 3004
ephone_dn 2
number 3005
ephone-dn 3
number 3998....
mwi off
ephone-dn 4
number 3999....
mwi on
Notes:
1. The scope of this post only includes enough info to show CUE integration.
2. It is essential to control the codecs used to inbound and outbound calls. For this reason both the “destination-pattern” as well as the “incoming called-number” is defined on dial-peer 3600 on CME1. This is to ensure that calls coming from and going to CUE use codec g711ulaw.
3. For MWI to be passed between CME1 and CME2 you need to ensure that:
a) “allow-connections sip to h323” is configured inside “voice service voip” on CME1
b) “mwi relay” is configured in “telephony-service” on CME2
Posted in June 8, 2009 ¬ 11:19 amh.
mick
As mentioned in previous posting my plans are to pot up Huey Dewey and Louie from their existing 4″ pots up to 10″.
I have also added dowel sticks from Huey and Dewey’s pots and marked with a line to show how high these guys are.
Posted in June 8, 2009 ¬ 9:38 amh.
mick
To restore factory defaults on Cisco Unity Express firstly take the module offline by typing “offline“, then when confirmed issue the “restore factory defaults” command.
An example follows :
Router# service-mode service-engine 1/0
Trying 192.168.n.3, 2006 ... Open
se-192-168-n-3# offline
!!!WARNING!!!: If you are going offline to do a backup, it is recommended
that you save the current running configuration using the 'write' command,
prior to going to the offline state.
Putting the system offline will terminate all end user sessions.
Are you sure you want to go offline[n]? : y
se-192-168-n-3(offline)# restore factory default
!!!WARNING!!!: This operation will cause all configuration and data
on the system to be erased. This operation is not reversible.
Do you wish to continue[n]? : y
Restoring the system. Please wait .....done
System will be restored to factory default when it reloads.
Press any key to reload:
System reloading ....
se-192-168-n-3(offline)#
MONITOR SHUTDOWN...
INIT: Sending processes the TERRestarting system.
-- SNIP --
INIT: Entering runlevel: 2
********** rc.post_install ****************
IMPORTANT::
IMPORTANT:: Welcome to Cisco Systems Service Engine
IMPORTANT:: post installation configuration tool.
IMPORTANT::
IMPORTANT:: This is a one time process which will guide
IMPORTANT:: you through initial setup of your Service Engine.
IMPORTANT:: Once run, this process will have configured
IMPORTANT:: the system for your location.
IMPORTANT::
IMPORTANT:: If you do not wish to continue, the system will be halted
IMPORTANT:: so it can be safely removed from the router.
IMPORTANT::
Do you wish to start configuration now (y,n)?
Once this has completed you proceed to setup the hostname, whether to use dns and ntp settings. After this configuration the booting process can take quite some time !
Posted in June 7, 2009 ¬ 11:43 amh.
mick
Of the five chilli plants I own the two biggest guys have now outgrown their 6″ pots. I have decided to bite the bullet and upgrade both of these guys to 13″ pots.
A conversation I had with a colleague he suggested that plants have what appears to be echo sounders. In this way they will grow to the size of the pot you have planted them in. Well if my guys northern cousins are anything to got by there must be something in this (even though the science is a little questionable).
-
-
-
-
-
Huey
-
-
Dewey
-
-
Louie
-
-
Bill
-
-
Ben
-
Also because of the lack of room in the outside gowing tent, I have brought a third plant in doors. What is interesting now comparing the guy that have outside with the guys that were brought in a week ago. Is that whilst not as big the guys from outside is almost as tall as the biggest plant.
To give some perspective on the sizes of the plants I should really have put rulers or something in the pots.
Whilst it’s not obvious from the pictures Bill and Ben are in 13 inch pots and stand 15 and 13 inches high respectively.
Huey is in a 5 inch pot and stands 3 inches high.
Dewey is in a 4 inch pot and stands 4 inches high
Louie is also in a 4 inch pot and stands three inches high.
I am planning on replanting Huey Dewey and Louie into 10 inch pots later this week. Whilst I am not anticipating any fruit this year I would like to see them increase in size to at least what the guys outside are doing.
Posted in June 6, 2009 ¬ 10:44 amh.
mick
After initial delays because of receiving a faulty unit.
My 4 Port USB extender has now arrived !
These devices are a godsend if you want to place USB devices more than (the official) 5 metres away from the PC. The solution consists of two parts :
1. A receiver which plugs into the PC
2. A transmitter which you connect your USB devices to.
Then you connect a piece of CAT5e or CAT6 cable between the two units. I have tested these units reliably up to 35 metres which is more than enough if you want to put that webcam in the greenhouse!
A word of caution though. Since they are only USB 1.1 and a camera will utilise approximately 9Mb/s (of the available 12Mb/s). Then you will not be able to connect more than one webcam per device. I have successfully managed to connect a webcam alongside a controller board (pictures).
The Plug
The usb extender was purchased via eBay over the Internet from CDL Micro. The product I purchased was their “USB 4 Port Extender Hub over Cat5e / Cat 6 Network” at a cost of £44.85 (free P&P). I cannot recommend these guys enough. Even though the first device I received was DOA. They responded promptly arrange for an RMA and replaced the faulty unit without a quibble.
Posted in June 5, 2009 ¬ 8:05 pmh.
mick
After almost a year without a dog in the house now is the time for us to get one.
My wife spotted a litter in Charde coming up to three weeks old so we decided to got and view them. These guys were a little too young to see any character forming so we have returned one week later and we’ve picked a little guy.
Presently the jury is out on what we call him these names range from Toffee (my youngest’s favorate name), through to Monty.
These are the pictures we took at 4 weeks old.
-
-
Having a cuddle
-
-
My first collar
-
-
Not happy about that collar
-
-
Back to sleep
Our plans are to collect him after he is six weeks old. Some time week commencing 21st June probably mid week so the traffic isn’t too bad.
Posted in June 5, 2009 ¬ 2:54 amh.
mick
Here follows the ISDN2e specific config for a gateway connected in the Uk with DDI. An assuption is made that the DDI range is : 03333 567890 – 03333 567899 and that the internal extensions would be 3000 – 3009. In addition to this calls to the PSTN will be presented with full DDI of the calling extension.
Two very important things to be aware of when connecting ISDN2e in the Uk.
1. BT by default only present that last 6 digits on inbound DDI
2. The default companding type is u-law so you need to set it to a-law manually.
Translation-rule 1 is used to convert from the inbound DDI presentation to the internal extension number.
Translation-rule 2 is used to re-write the calling number to add a leading 9 (and the missing 0). So that a user can return the call directly from a list without editing the number.
Translation-rule 3 is used to map back from the extension to the full external DDI number.
Dial-peer 10 is used to control incoming calls (we don’t like defaults dialpeer zero).
I Have split up the outbound dial-peers so that COR (class of restriction) can be applied if we wish to.
isdn switch-type basic-net3
voice service pots
supported-language UK
voice translation-rule 1
rule 1 /^56789\(.\)$/ /300\1/
voice translation-rule 2
rule 1 /^0/ /900/
rule 2 /^1/ /901/
rule 3 /^2/ /902/
rule 4 /^3/ /903/
rule 5 /^4/ /904/
rule 6 /^5/ /905/
rule 7 /^6/ /906/
rule 8 /^7/ /907/
rule 9 /^8/ /908/
rule 10 /^9/ /909/
voice translation-rule 3
rule 1 /300\(.\)$/ /0333356789\1/
voice translation-profile FROM_PSTN
translate calling 2
translate called 1
voice translation-profile TO_PSTN
translate calling 3
interface BRI0/2/0
description ** ISDN - DDI RANGE 03333 567890 - 9 **
no ip address
isdn switch-type basic-net3
isdn point-to-point-setup
isdn incoming-voice voice
isdn static-tei 0
voice-port 0/2/0
compand-type a-law
cptone GB
dial-peer voice 10 pots
description *** For inbound calls from PSTN ***
translation-profile incoming FROM_PSTN
preference 1
incoming called-number .
direct-inward-dial
port 0/2/0
forward-digits all
!
dial-peer voice 9 pots
description *** Local Calls ***
translation-profile outgoing TO_PSTN
preference 1
destination-pattern 9[1-9]T
port 0/2/0
!
dial-peer voice 9011 pots
description *** National Calls ***
translation-profile outgoing TO_PSTN
preference 1
destination-pattern 90[1-6]T
port 0/2/0
prefix 0
!
dial-peer voice 907 pots
description *** Calls to Mobiles ***
translation-profile outgoing TO_PSTN
preference 1
destination-pattern 907T
port 0/2/0
prefix 07
!
dial-peer voice 907 pots
description *** Calls to None Geographical Numbers ***
translation-profile outgoing TO_PSTN
preference 1
destination-pattern 908T
port 0/2/0
prefix 08
!
dial-peer voice 909 pots
description *** Premium Rate Calls ***
translation-profile outgoing TO_PSTN
preference 1
destination-pattern 909T
port 0/2/0
prefix 09
!
dial-peer voice 900 pots
description *** Internation Calls ***
translation-profile outgoing TO_PSTN
preference 1
destination-pattern 900T
port 0/2/0
prefix 00
!
A combination of either CME or Call Manager/SRST configuration needs to be added to make more use of this configuration.