i'm supposed to have moved my focus from the SMS part of my employer's business to IVR. i've had to deal with a flowchart-based development environment i find very annoying. plus, since i had no prior experience with telephony systems, quite a bit is lost on me. i've mostly been fumbling around in the dark.
this morning, my boss called me and asked me if i could develop a voice broadcast application using that environment. since i'd been having problems with it, i said i'd try. since then, i have failed in trying to get the application to make outbound calls. the alternative was to call in a consultant who's very good with Asterisk. i called him, but not after i discovered Asterisk.NET. before long, i had learned a little about the Asterisk Manager Interface and AGI, both of which i never knew existed before today, even though i've played around with Asterisk as part of my job. i also found the Sipek VoIP projects site. hopefully, i'll be able to build the application needed either by using Asterisk.NET or the Sipek SDK. either way, things should work out now.
Python 3.0 is out (i'm a couple days late on this one), and it isn't backward compatible with the 2.X series. looks like they really gave some thought as to where Python should go. i guess that means development of the 2.X series will basically be mostly bugfixes from now on. still, there seems to be a lot to like about the new Python, even though it's slower than 2.6 on the pystone benchmark (i cannot believe they actually took a line from Basic and added the <> operator in Python. thank goodness it's been removed in 3.0!). let's see how things go, especially with open-source projects that use Python. i'm personally wondering where IronPython goes (yes, they did it - got me sold on .NET. doesn't mean i now despise C++ though. i still plan on using it from time to time).
and thanks to Segun who gave me a ride yesterday when i forgot my wallet at home. you're the best, bro!
No comments:
Post a Comment