- Posted by jfarrar on October 30, 2007
CallControl.NET has had it's first official sale to an undisclosed entity. It's exciting to see it's potential and I'm excited to see how it gets integrated into different solutions. Only time will tell whether or not this is a needed solution in the voip industry. In my personal opinion I feel that it has great potential to take off for several reasons.
- CallControl.NET allows you to integrate the call control functionality of Broadsoft™ into any existing or new .NET windows application.
- Broadsoft™ continues to rank as one of the top fastest growing technology company Here and Here.
Basically, this component will allow a quicker time to market for new applications with the added call control functionality. Additionally, it provides an easy ability to enhance existing applications.
It's really been a busy month and I'm sure as the holiday's approach it won't slow down. However, I'm excited to see what kind of applications will be developed with this component.
0 comments
- Posted by jfarrar on September 1, 2007
Well I've been working hard lately on quite a few things. Mostly I've been focusing my attention on CallControl.NET. I've just finished the initial version of the actual component and I'm pretty happy with it. Heres a little run down on what it does:
Name: JoeDeveloper.CallControl.dll
Description: Integration into the call control API exposed by the broadsoft™ softswitch.
Features:
► Receive incoming call notifications
► Monitor incoming and outgoing calls
► Handle multiple calls at once.
► Dial out
► Answer incoming calls
► Transfer to phone number
► Transfer with consultation
► Transfer to voicemail
► Place call on hold
► Call hang-up
There is so much more that I will be working on to implement more features exposed by the broadsoft™ api. Just some background information regarding the component, it's developed to work on the .NET 1.1 or 2.0 Framework but only for Windows Forms applications. I'm going to be trying to develop a web version of the product, but this will prove to be more challenging for a couple of reasons. #1 There is the neccesity to keep an open TCP connection in a typical client - server model. #2 HTTP doesn't currently support this nor will it ever. I have a few ideas how to get around this so we will see. Until then I'm going to be starting to release more information about the component so that people can purchase it.
If you want more information about it leave a comment and I will get back to you.
In other news I've also developed a .NET Assembly to integrate into the LinksysOne service node API. It provides all of the features available as well as a few custom ones that I developed onto it. I'll post more about that later. Until then stay tuned for more information.
0 comments