[asterisk-bugs] [Asterisk 0017612]: [patch] wrong SRV query for TLS connection
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Jul 26 10:00:24 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17612
======================================================================
Reported By: marcelloceschia
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 17612
Category: Channels/chan_sip/TCP-TLS
Reproducibility: always
Severity: trivial
Priority: normal
Status: feedback
Asterisk Version: SVN
JIRA: SWP-1832
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 273980
Request Review:
======================================================================
Date Submitted: 2010-07-09 02:01 CDT
Last Modified: 2010-07-26 10:00 CDT
======================================================================
Summary: [patch] wrong SRV query for TLS connection
Description:
chan_sip generates wrong service records queries to dns.
it queries to _sip._TLS.example.com, instead of _sips._tcp.example.com
======================================================================
----------------------------------------------------------------------
(0125027) marcelloceschia (reporter) - 2010-07-26 10:00
https://issues.asterisk.org/view.php?id=17612#c125027
----------------------------------------------------------------------
@pabelanger it does not duplicate the functionality of get_transport.
get_transport is used for debug output and for sip header (transport
part). In all these parts the get_transport is correct.
But transport != protocoll and tls is not a valide protocol for srv
wuery.
How can we fix this?
Issue History
Date Modified Username Field Change
======================================================================
2010-07-26 10:00 marcelloceschiaNote Added: 0125027
======================================================================
More information about the asterisk-bugs
mailing list