From: Rusty Newton <rnewton@digium.com>
Date: Mon, 20 Jul 2015 22:16:36 +0000 (-0500)
Subject: Documentation: chan_sip doesn't support WS or WSS in outbound register.
X-Git-Tag: 11.19.0-rc1~7
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=43a52df20d92de81604ce3c0dc9231d0e75eef03;p=thirdparty%2Fasterisk.git

Documentation: chan_sip doesn't support WS or WSS in outbound register.

 * In sip.conf.sample fix sentence where we said that WS or WSS are supported
   transports for use in an outbound register definition. They are not
   supported in that case.

ASTERISK-24853 #close
Reported by: PSDK

Change-Id: I3d698bc6302b9d00a0a995b5c4ad9a42d69b48ca
---

diff --git a/configs/sip.conf.sample b/configs/sip.conf.sample
index b2489dc202..1ac849c03b 100644
--- a/configs/sip.conf.sample
+++ b/configs/sip.conf.sample
@@ -789,7 +789,7 @@ srvlookup=yes                   ; Enable DNS SRV lookups on outbound calls
 ;
 ;register => tls://username:xxxxxx@sip-tls-proxy.example.org
 ;
-;    The 'transport' part defaults to 'udp' but may also be 'tcp', 'tls', 'ws', or 'wss'.
+;    The 'transport' part defaults to 'udp' but may also be 'tcp' or 'tls'.
 ;    Using 'udp://' explicitly is also useful in case the username part
 ;    contains a '/' ('user/name').