First of all I'm very happy this product is being developed, as it fills a big gap that exists right now in the field of unified communications / web telephony. Keep up the good work guys, I'm patiently waiting for the next release.
In the meantime here are some bugs. I'm sure as I continue to develop my application I'll find more but here are some of the most annoying that I've found so far:
I'd also like to add that FMG doesn't appear to support SIP call transfer events at the moment either.
All the above make any kind of serious application that integrates into common SIP infrastructure difficult. I read in another thread that the FMG dev team doesn't consider call transfer a priority feature. Are you serious? If FMG isn't going to support extremely basic SIP events such as call transfer then it might as well be toy; I don't think anyone, including myself, would waste time developing for it.
#1. Acknowledged. Next build update on Lab will have feature to supplement SIP Profile with AuthUserName instead of username so that dynamic callerIDs can be passed on from FMS in all cases.
#2. Acknowledged. FMG doesn't provide updates of remote-party-ID. And we do plan to support it in future.
#3 New release of Flash Player 11.2 has already been fixed for H.264 playback.
Call transfer is something which fits well with FMG's roadmap.
Thanks for the info. I have one more question: I noticed that the sample sip phone application includes support for receiving video but does not appear to have any support for sending video (say, from a webcam). Is this is a limitation of FMG/FMS, or is it possible but would need to be written in?
Europe, Middle East and Africa