> ok, so how is this different from not using CUSAY at all and just having
> a SIP number in the contact vcard?
Sacrificing Jingle interop is one such recommendation. You asked how
not to sacrifice it, and the answer is that you are not required to
but you lose in usability if you don't.
In any case, does CUSAX mean "better use SIP for calling because it
won't ever work with XMPP anyway"?
It is not up to an IETF document to predict the future and CUSAX
certainly doesn't try to do this.
I would not hope that ... what are the chances of having real orking
call features with just XMPP?
Why are you asking this question here? With videobridge conferencing,
Jitsi currently has more calling features through XMPP than SIP.
The reason for CUSAX to exist is mostly the state of existing server
implementations. So you may want to ask the implementers of your
favourite XMPP server what their plans are about implementing
voicemail, voice2mail, call park, call pickup, busy line feed,
conference rooms, a PSTN gateway, inband DTMF, resource allocation,
audio transcoding, CDR, billing, SLA and MWI.
This is what you question above is actually about. Not Jitsi.
On Tue, Oct 22, 2013 at 11:48 PM, Dominik George <email@example.com> wrote:
<burny> Ein Jabber-Account, sie alle zu finden; ins Dunkel zu treiben
und ewig zu binden; im NaturalNet, wo die Schatten droh'n ;)!
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296
users mailing list
Unsubscribe instructions and other list options:
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
firstname.lastname@example.org PHONE: +22.214.171.124.43.30
https://jitsi.org FAX: +126.96.36.199.47.31