[asterisk-bugs] [Asterisk 0015925]: New sounds for sounds-extras
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed May 26 10:32:11 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=15925
======================================================================
Reported By: jtodd
Assigned To: twilson
======================================================================
Project: Asterisk
Issue ID: 15925
Category: Sounds
Reproducibility: N/A
Severity: feature
Priority: low
Status: feedback
Asterisk Version: SVN
JIRA: SWP-1501
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-09-21 14:55 CDT
Last Modified: 2010-05-26 10:32 CDT
======================================================================
Summary: New sounds for sounds-extras
Description:
New sounds for sounds-extras, somewhat talking about cert issues since TLS
is done and SRTP is on the horizon. Discussed briefly with oej and
kpfleming in loop.
%cert-expired%The certificate provided by this server has expired.
%cert-auth-unknown%The certificate provided by this server is signed by an
unknown certificate authority.
%cert-revoked%The certificate provided by this server has been revoked.
%cert-valid%The certificate provided by this server is valid.
%cert-mismatch%The certificate provided by this server does not match the
host name of the server.
%cert-rejected%Your server or client should have rejected this
certificate.
%cert-should-accept%Your server or client should have accepted this
certificate.
%your-public-ip%Your public IP address is…
%SSIP-success%You have successfully established a Secure SIP Session.
%SRTP-success%You have successfully established a Secure RTP Session.
======================================================================
----------------------------------------------------------------------
(0122484) twilson (administrator) - 2010-05-26 10:32
https://issues.asterisk.org/view.php?id=15925#c122484
----------------------------------------------------------------------
Secure is a good word to use, in my opinion, since we will be allowing the
end user themselves to define what secure means--it isn't something that we
are handing down to them.
I don't think the prompts should be protocol specific. The same methods
for checking secure signaling/media exist for both SIP and IAX2 already.
I think it is important to make the prompts as generic as possible so they
can get the widest use. It would seem odd for the average user of a PBX to
hear a bunch of tecno-babble about protocols and certificates I would
think.
Not that it hurts to have those prompts as options, just that I think we
need something like:
"Your call is/is not secure"
"The other party's call is/is not secure"
If you really wanted you could break "secure" into:
"has/does not have secure media"
"has/does not have secure signaling"
"has/does not have secure media and signaling"
etc., but I think that might be overkill for must users.
Issue History
Date Modified Username Field Change
======================================================================
2010-05-26 10:32 twilson Note Added: 0122484
======================================================================
More information about the asterisk-bugs
mailing list