After just getting back from my holidays I was really really chuffed with this review of Power Meter Plus which appeared in the Bangkok Post. If anyone has a copy of the paper edition which they can scan in and email me then I’d really appreciate seeing it :-D
During a conversation with USRobotics tech support they noticed that the Initialisation String I was trying was wrong.
The string they asked me to try instead was &S1. After using that, the modem carries detecting caller ID between calls. This now appears in the modem log:
– Interpreted response: Ring
– DSR state changed, But is currently high, Ignoring.
– Recv: <cr><lf>RING<cr><lf>
– Interpreted response: Ring
I’m waiting for confirmation from someone else who was experiencing the same issue before I close the support call with USR, but the results from my side are really promising :-)
[Update – Hmmm, this is still causing me (and others) problems. There’s a thread at Hexus discussing the attempts at making it work. I need to get my a.ss in gear and start posting the debug logs :-o ]
This is useful if you’d like to be notified of new mail in a POP3 account that you either don’t want to monitor manually, or you can’t monitor because of restricted access to your home email.
Since doing an RSS feed of Caller Id was so easy I thought I’d code this up too, but Ryan Grove has already coded MailFeed. It took me a little while to get it all working, mainly because of PEAR for PHP.
Here are the steps I went throug to get it working:
- Prerequisite: LAMP/WAMP (with PHP) up and working
- Install PEAR.. there’s a great guide on this by Harry Fuecks
- Once PEAR is working, install the Mail_Mime package (using the command ‘pear install Mail_Mime’)
- Copy over the MailFeed script and modify it’s parameters to connect to your POP3/IMAP/NNTP mailbox. The syntax of the imap_open method was useful to me when I was wondering what parameters to set for my POP3 account.
That’s your lot.. you should now be able to connect to your home server remotely and view an RSS feed of your POP3 inbox.
After a few people reported problems with the app I took a look at the code which deals with generating the suffixes and have (hopefully) fixed everything. Give it a try and let me know how you get on! :-)
After a bit of testing with the Caller ID RSS feed I found that a bit later, the modem wasn’t responding to incoming calls. The modem log had a line in it reporting:
“DSR drop while monitoring for calls”
This has been mentioned before on the net on some forums, but no resolution was found. There were a few suggestions…
Hopefully adding the following initialisation string to the modem’s extra settings will do the trick:
AT&S0 (0=zero) [this should force DSR to remain on]
If anyone knows of another solution, please get in touch.
[Update 1 – using this initialisation string made no difference.. after taking a voice call & hanging up, the modem stops monitoring for calls. I’ve raised this with US Robotics tech support so I’ll see what they say]
[Update 2 – Hats off to USR tech support; they got back to me straight away saying that the initialisation string should be AT&S0=0 .. I’ll be giving that a try tonight! :-)]
[Update 3 – That setting didn’t make any difference and the issue has been escallated to USR’s 2nd line support. I’ve yet to hear anything back from them]
[Update 4 – 2nd line support noticed that the initialisation string was incorrect. It should read &S0. That did the trick for me & I’ll post a full description in a new blog entry]
[Update 5 – Ooops! I posted the wrong value.. it should read &S1 ]
After the success of getting YAC to distribute the phone number of incoming calls to devices on my network (including my Xbox via XMBC) I wondered how I could get notification on my desktop at work. YAC broadcasts on a port, and that doesn’t gel with corporate firewalls.. but it does create a log:
YAC 0.16 Started: 25 June 2006 – 10:13:57
Running in Server mode.
***** INCOMING CALL: 25 June 2006 – 18:04:28 *****
NAME: YAC Test Call
NUMBER: (425) 555-1212
***** INCOMING CALL: 25 June 2006 – 18:07:58 *****
NAME: YAC Test Call
NUMBER: (425) 555-1212
Since I have a webserver running at home, putting this log into the public folder of the web server made it available wherever I was in the world. This still isn’t ideal; I’d rather not have to check whether I’ve missed any important calls.
RSS feeds seemed the logical progression. I have a few RSS readers installed, and they’ll poll at whatever duration you specify. YAC doesn’t output an RSS feed and I was pulling my hair out trying to compile the YAC source even without modifications!
Instead of modifying YAC, I simply wrote a small PHP script to parse the log file and strip out what I needed. Feed Creator can then be used to create a quick RSS feed from the data.
Here’s the finished script. Enjoy!! :-D
If you find it useful, a small donation via PayPal (no matter how small) would really make my day!
When I moved home a couple of weeks ago everything went really smoothly. Taking over and transferring the phone number from the old line went alright, although it did take 3-4 days for our old number to be transferred to the new address.
However when it came to ordering broadband, the ISP I chose phoned me a week and a half later to say there was a conflicting product on the line. It was likely that the previous owner had broadband, and it hadn't been cancelled & removed from the line. The ISP said BT would be able to sort this out.
It took a couple of hours to find someone at BT who knew what I was on about and could sort it out. The route they took me down was:
- Initial call to 0800 500 150 – hopeless IVR system which I found terminated at various points with an unknown number error. Went through a different route a number of times (attempting to avoid these dead ends) and eventually spoke with someone who said that 151 would know what to do.
- 0800 500 151 – routed to India. They hadn't a clue and kept me on hold a number of times whilst they talked to a supervisor. Eventually said to raise it with broadband technical help.
- 0845 600 7030 – the broadband tech guy said there was little they could do since they didn't know which ISP the previous product was held with. He said to ring Ofcom who would tell me & could progress it further.
- 0845 456 3000 (Ofcom) – After navigating through the IVR an automated message said that they have nothing to do with Conflicting Product / Marker problems. BT Wholesale are the people to speak to, and gave their number.
- 0800 169 0934 – Despite waiting in a queue for 20 minutes BT Wholesale were actually helpful & could see the problem straight away. The order to remove the old product off the line was in progress and would take a few more days to be resolved.
So eventually I got the answer I was after. The thing that really bugs me is that it took me 5 different phone numbers to get to the right people. And that it was Ofcom who told me the right number to ring.. not BT.
Overall, I must have wasted a couple of hours chasing this problem up. Rubbish!