Recently I was asked by a customer to deliver .wav files to the inbox of their mail server from a Unity Connection server. Well, by asked I mean that the salesperson promised it to them and I had to find a way to deliver it.
I came up with an idea to do this… it didn’t work. But the idea was sound, it just needed a little tuning to make it work right.
I used a Linux server with PHP and Postfix to make all the magic work. It also helped that none of the customers used Unity Connection’s web client.
I created aliases on the Postfix server redirecting users to a custom script. The script then logs into the Unity Connection system and retrieves the .wav file and retransmits it as a new message to a specified email address.
I’m still polishing it up a bit, but it’s fully functional and delivering .wav files to our inboxes as expected. When I get it to a more flexible format I’ll release it on this site. For now, if you are interested and don’t mind a ‘beta’ version of the software, let me know and I can provide you with a copy and instructions for use.
I am rarely very impressed with 3rd Party software, but Agito Networks has impressed me. I spent most of my day working with their team to integrate and test their Mobile Router with our IP Telephony platform.  Their solution integrates with most IP Telephony systems and wireless platforms to create a nearly seamless roaming functionality between the corporate environment and wifi enabled cell phones.
Their system allows your cell phone to ring as if it shared a line with your desk phone. You can pick up calls on either cell or desk phones. When you’re within range of a wifi access point, the phone will connect using IP Telephony rather than cellular service. When you’re out of range, it uses cellular. This saves minutes and LD costs on your cellular account. The really cool thing is that the platform can switch from wifi to cellular without dropping your call! In most cases you may not even be aware of the transition.
There are also several other features like corporate directory integration which would allow your cell phone access to the corporate directory stored on your office telephone system.
For anyone interested in taking a closer look, you can find more information about Agito Networks Mobile Router here
.
If you’ve worked with Cisco IP Telephony products, you’re probably familiar with their Attendant Console software. The software allows receptionists to manage incoming calls from their PC. This allows them to transfer calls with simple drag and drop functions. It also provides a quick list of user line status, whether they are on the phone or available. There are a number of additional features in this software but it is outside the scope of my rant. Using standard Cisco software, this software doesn’t exist for Callmanager Express (CME) patforms. The reccomended replacement is to use an expansion module which gives a phone “switchboard like” functionality.
ArcSolutions provides software that has similar functionality to Cisco’s Attendant console. This software is, in my opinion, one of the worst add-on technologies I have ever seen. I’ll explain and let you make up your own mind though.
ArcExpress requires that a “server” installation be configured on a single PC. That PC houses a SQL database for all other clients to attatch to. This PC has to remain on at all times, or the ArcExpress users all lose functionality. The “server” software is configured using the CME Configuration utility. This utility logs into the CME system and reads the configuration. At this point it attempts to make several configuration changes. Some of these changes include :
- Adding virtual phone configurations
- Adding virtual extension numbers for ArcExpress feature support
This was my first issue. In order to complete the CME Configuration, you must have at least 2 free phone licenses available. It also requires several available directory numbers for feature support. If your licensing does not allow for the recommended changes, the configuration will not continue.
At least the configuration utility gave me a list of the changes it was going to make. From that list I was able to adjust the changes to fit within the licensing constraints of the system.
At this point however, even though the ArcExpress virtual phone showed registered in the CME system, it did not function. Attempting to call Tech Support resulted in sitting on hold for an eternity. But I understand that problem. When you have a product as shoddy as this, one must expect a lot of tech-support calls. Their techs were probably all just very busy.
After many hours of work trying to get ArcExpress to function I have decided that it is not worth the effort. I will never work on another project using this software if I can at all help it.