Hello,
On 2/11/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Does it make sense to use SipPimClient at all? Given the problems that
> Adrzej described I think it's more reasonable to find a library for icq,
> aim, jabber, msn in C or C++ and use that instead of the code in
> sipxstacklib. How many softphones will understand your messages?
All softphones compliant to RFC 3428.
> If you use icq your softphone can connect to icq server and users that have
> plain icq client without a phone will be able to see you and chat with you.
1) ICQ is proprietary protocol. Alternate clients are not supported and may
get brocken in a sec. As an active icq user I remember a bunch of such
incidents.
2) It require internet connection. There is no intranet icq version (icqcorp
stop its progress in '98).
3) Ok, you've said jabber. Yes, it solve 1) and 2). But why should I maintain
jabber server in addition to SIP server, if SIP fulfil all my requirements?
Moreover if it could be done with one library.
What I want to say - do not forgot about corporate users, and do not forget
that if something could be done easy way, it have to be done this way.
--
Regards,
Alexander Chemeris.
_______________________________________________
sipxtapi-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
