Closed GoogleCodeExporter closed 9 years ago
Yes, I'm currently doing that.
I'm currently integrating the application the new (clean) way as introduced
recently thanks to the new pjsip callback.
I'm also trying to fix something more annoying about the fact the second call
crash now with this new method... just leave me time :) (and do not hesitate to
contribute ;) source code ).
Also, issue 262 is still open... it means that zrtp is not yet fully
implemented, you can follow your questions, remark on issue 262 thread.
More users have stared this issue and for example werner will be able to reply
(while he do not track each new issue of csipsimple project ;) ).
Original comment by r3gis...@gmail.com
on 15 Jul 2011 at 2:25
Just my 2 Euro cents (as long as they are worth something :-) )
Other clients, for example Twinkle (outdated, no maintenance anymore) and Jitsi
(former SIP Communicator) implement several ways to support users to detect
success
or failure during ZRTP:
On success:
- play a short "Acknowledge sound" as soon as key exchange is OK and SRTP was
established. Thus a user don't need to check the display. If the sound was not
played 2-3s after the call was established - then check the display.
Both sounds are available as wav files in the Jitsi project and are not
copyright protected :-) .
- Obviously a nice informative SAS field and a verify check box (as requested
above)
On problems/failure:
- play a nasty sound, simliar to a ploice car sirene to warn the user that ZRTP
detected something odd. In that case the user shall check the display and the GUI
implementation shall display the error/warning message.
The ZRTP implementation uses callback to inform the GUI about these states and
the
GUI may display/act accordingly and may trigger playing sounds. The GUI may have
an option to close the call if ZRTP reports an error.
Maybe you can check this info that I wrote for the Jitsi project:
http://www.jitsi.org/index.php/Documentation/ZRTP4JMessageCodes
Original comment by werner...@googlemail.com
on 17 Jul 2011 at 1:07
Original issue reported on code.google.com by
d...@dmit.lv
on 15 Jul 2011 at 1:44