RTP support channels - Revision history

Dana: /* Section [timeouts] */

2014-01-10T14:12:36Z

‎Section [timeouts]

Dana: /* Section [timeouts] */

2014-01-10T14:11:31Z

‎Section [timeouts]

Dana: /* Section [general] */

2014-01-10T14:08:01Z

‎Section [general]

Dana: /* Section [general] */

2014-01-10T14:07:04Z

‎Section [general]

Dana: /* Configuration */

2014-01-10T13:59:51Z

‎Configuration

Monica: /* RTCP usage */

2013-11-04T10:09:27Z

‎RTCP usage

Dana: /* RTCP usage */

2013-04-03T11:03:30Z

‎RTCP usage

Dana: /* RTCP usage */

2013-04-03T11:03:14Z

‎RTCP usage

Dana: /* Configuration */

2013-04-02T13:22:15Z

‎Configuration

Dana: /* How to drop calls if RTP is lost */

2012-10-09T13:43:34Z

‎How to drop calls if RTP is lost

@@ Line 93: / Line 93: @@
 ====Section [timeouts]====
-This section controls the behaviour when RTP and RTCP data is missing
+This section controls the behavior when RTP and RTCP data is missing.
-* '''timeout''': int: Receiver timeout in ms (500-60000), zero disables
+* '''timeout''': int: Receiver timeout in ms (500-60000), zero disables.
 :timeout=3000
-* '''udptl_timeout''': int: UDPTL receiver timeout in ms (500-60000), zero disables
+* '''udptl_timeout''': int: UDPTL receiver timeout in ms (500-60000), zero disables.
 : udptl_timeout=25000
-* '''notifymsg''': string: Name of the notification message sent on timeout
+* '''notifymsg''': string: Name of the notification message sent on timeout.
-: Usually it should be chan.notify or call.drop, empty disables the message
+: Usually it should be [[chan.notify]] or [[call.drop]], empty disables the message.
-* '''warnfirst''': bool: Emit timeout warnings if no RTP packet was received
+* '''warnfirst''': bool: Emit timeout warnings if no RTP packet was received.
-: Once a packet is received further timeouts are controlled by warnlater
+: Once a packet is received further timeouts are controlled by warnlater.
 : warnfirst=yes
-* '''warnlater''': bool: Emit timeout warnings even if there was initially some RTP
+* '''warnlater''': bool: Emit timeout warnings even if there was initially some RTP.
 : warnlater=no

@@ Line 97: / Line 97: @@
 * '''timeout''': int: Receiver timeout in ms (500-60000), zero disables
 :timeout=3000
-−
 * '''notifymsg''': string: Name of the notification message sent on timeout
 : Usually it should be chan.notify or call.drop, empty disables the message
-−
 * '''warnlater''': bool: Emit timeout warnings even if there was initially some RTP
- ;warnlater=no
+: warnlater=no
 ==== Example ====

@@ Line 29: / Line 29: @@
 * '''tos''': keyword: Type Of Service or DiffServ to set in outgoing UDP packets.
 :  Numeric TOS / DiffServ value or:
-::  lowdelay, throughput, reliability, mincost
+:: - lowdelay, throughput, reliability, mincost
-::  cs0, ... cs7, af11, af12, af13, af21, ... af43, expedited, voice
+:: - cs0, ... cs7, af11, af12, af13, af21, ... af43, expedited, voice
 :Default value:
 :tos=0

@@ Line 39: / Line 39: @@
 * '''buffer''': int: Maximum buffer size - used to fragment octet (G.711) audio streams.
- ;buffer=240
+: buffer=240
 * '''autoaddr''': bool: Auto change outgoing RTP address:port to match incoming.
@@ Line 71: / Line 71: @@
 : You will also need to set '''monitor=yes''' in section '''[rtp]''' of monitoring.conf
 : monitoring=no
 * '''thread''': keyword: Default priority of the data service threads

@@ Line 4: / Line 4: @@
 ===Configuration===
-The config file is yrtpchan.conf:
+The configuration file is yrtpchan.conf. Below you can see the sections and their description.
- [general]
+==== Section [general]====
- ; This section sets global network level variables
+This section sets global network level variables.
- ; minport: int: Minimum port range to allocate
- ;minport=16384
+*'''ipv6_support''': boolean: Enable or disable IPv6 support.
+: This parameter is applied on reload.
- ; maxport: int: Maximum port range to allocate
+: This parameter is ignored if yate was not built with IPv6 support.
- ;maxport=32768
+: It can be overridden in [[chan.rtp]] messages.
- ; tos: keyword: Type Of Service to set in outgoing UDP packets
+* '''maxport''': int: Maximum port range to allocate. Default value is:
-  ; numeric TOS value or: lowdelay, throughput, reliability, mincost
+: maxport=32768
-  ;tos=0
+* '''localip''': ipaddress: Local IP address to use instead of guessing.
- ; buffer: int: Maximum buffer size - used to fragment octet (G.711) audio streams
+: IPv6: An interface name can be added at the end of the address to bind on a specific interface.
   ;buffer=240
- ; autoaddr: bool: Auto change outgoing RTP address:port to match incoming
+* '''autoaddr''': bool: Auto change outgoing RTP address:port to match incoming.
- ;autoaddr=enable
+: autoaddr=enable
- ; anyssrc: bool: Accept any incoming SSRC, even if it changes frequently
+* '''anyssrc''': bool: Accept any incoming SSRC, even if it changes frequently.
- ;anyssrc=disable
+: anyssrc=disable
- ; rtcp: bool: Allocate socket for the RTCP protocol by default
+* '''padding''': int: Pad the RTP payload to a multiple of this setting.
- ;rtcp=enable
+: Supported values are between 2 and 128.
- ; drillhole: bool: Attempt to drill a hole through a firewall or NAT
+* '''thread''': keyword: Default priority of the data service threads
- ;drillhole=disable in server mode, enable in client mode
+: Can be one of: lowest, low, normal, high, highest
- ; thread: keyword: Default priority of the data service threads
+* '''defsleep''': int: Default in-loop sleep time for new RTP sessions in milliseconds
- ; Can be one of: lowest, low, normal, high, highest
+: defsleep=5
- ; It is a bad idea to set a low priority for anything but testing
- ;thread=normal
- ; defsleep: int: Default in-loop sleep time for new RTP sessions in milliseconds
+* '''minsleep''': int: Minimum allowed in-loop sleep time in milliseconds
- ;defsleep=5
+:minsleep=1
-−
- ; minsleep: int: Minimum allowed in-loop sleep time in milliseconds
+* '''rtp_warn_seq''': bool: Warn on receiving invalid RTP sequence number
- ;minsleep=1
+: If disabled the log message will be put at level 9
-  [timeouts]
+  '''Note:''' The "tos" and "thread" settings requires IP and process level privileges - usually you need to run Yate as root (on *NIX), Administrator or Windows service.
- ; This section controls the behaviour when RTP and RTCP data is missing
- ; timeout: int: Receiver timeout in ms (500-60000), zero disables
+* '''timeout''': int: Receiver timeout in ms (500-60000), zero disables
- ;timeout=3000
+:timeout=3000
- ; notifymsg: string: Name of the notification message sent on timeout
+* '''notifymsg''': string: Name of the notification message sent on timeout
- ; Usually it should be chan.notify or call.drop, empty disables the message
+: Usually it should be chan.notify or call.drop, empty disables the message
- ;notifymsg=
- ; warnlater: bool: Emit timeout warnings even if there was initially some RTP
+* '''warnlater''': bool: Emit timeout warnings even if there was initially some RTP
   ;warnlater=no
-  '''Note:''' The "tos" and "thread" settings requires IP and process level privileges - usually you need to run Yate as root (on *NIX), Administrator or Windows service.
-−
 ==== Example ====

← Older revision		Revision as of 10:09, 4 November 2013
Line 90:		Line 90:

	* [[RTP Forwarding]]		* [[RTP Forwarding]]
		+
		+	[[Category:RTP]]

← Older revision		Revision as of 11:03, 3 April 2013
Line 89:		Line 89:
	'''See also'''		'''See also'''

−	* [[RTP ~~forwarding~~]]	+	* [[RTP Forwarding]]

← Older revision		Revision as of 11:03, 3 April 2013
Line 85:		Line 85:

	Very few application make use of RTCP. You can improve the performance of the system by disabling it. This also reduces the number of UDP ports used, potentially doubling the maximum number of voice streams.		Very few application make use of RTCP. You can improve the performance of the system by disabling it. This also reduces the number of UDP ports used, potentially doubling the maximum number of voice streams.
		+
		+
		+	'''See also'''
		+
		+	* [[RTP forwarding]]

@@ Line 60: / Line 60: @@
 '''Note:''' The "tos" and "thread" settings requires IP and process level privileges - usually you need to run Yate as root (on *NIX), Administrator or Windows service.
-=== How to drop calls if RTP is lost===
+==== Example ====
 Because the signalling protocol may not detect promptly (or at all) a network failure it is common to drop calls shortly after RTP data is lost. This can be easily accomplished by setting:
@@ Line 70: / Line 71: @@
 This will drop the call with reason ''nomedia'' 6.5 seconds after no RTP or RTCP packets were received. The 6.5 seconds is set to accomodate the typical 5s with 20% variation interval of RTCP reports.
 ===SSRC problems===