Tim,
Your etiquette on this is perfect.
Since you are using VS 2005 and .Net 2.0, I would STRONGLY recommend looking at the SipXTapiDotNet wrapper I pointed you to earlier. I was able to get farther in two days than I was in about 3 months of trying to figure out the core and wrap it myself. I now have a fully operational application that took a total of a week to bring together. It uses sipXtapi at the core and the guys that worked on it did end up doing a few contributions to the media library of the core to resolve some issues. As long as you don't need to make any changes to the wrapper, you won't have to spend time developing in the core.
Since it will be in a stationary location, your development overall will be MUCH simplified. I applaud your idea regarding limiting the amount of space for the interface. I think it may be a bit overkill, but it might be better, giving them some feedback to the edges of the interface. I'm sure you have done your research on this end, so I will yield to you on this design aspect.
1) do you know anything about what Microsoft has done with SIP in Windows Messenger? Have they documented the API's required to allow me to use my GUI? I have spent a little time investigating the answer to this question but haven't found any discussion of an SDK that would expose the functionality I need.
I personally have no knowledge regarding the WM SDK.
2) How stable/reliable is sipXtapi?
In my experience (although limited) and based on the posts I have seen in the dev group, I would say it is very close to 99% reliable assuming everything is set up and implemented properly.
3) How well documented is the API?
The API is reasonably well-documented, but the most lacking is complete examples and usage examples. They clearly state what each function should do, but they don't really show how to use each function properly. This is mainly due to lack of manpower/time. It is an ever-evolving project, so it hasn't been a high priority. It's better to get it working properly than properly document it.
4) If you were starting from scratch (as I am) with sipXtapi (and tapi in general for that matter), do you have any feel for how long it would take you to dig through documentation (and source code?) to figure out how to implement a reliable SIP communication environment?
I would NOT recommend starting from scratch. It would take a team of developers with experience several weeks to come up with something equivalent.
5) Is Broadvoice a reasonable choice for access to POTS? Would you recommend something different?
-Unknown-
I am a stickler to design interface. If you would like to discuss what should be on your interface, I would be happy to.
 Radeco Solutions D2M Technologies |
_______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
