SIP Configuration File - Revision history

Marian: /* Parameters */

2018-07-06T10:09:12Z

‎Parameters

2016-06-08T13:07:54Z

Updated conf options from SVN rev. 6117-6119

2014-03-13T18:32:06Z

‎Extending SIP functionalities: linked to SIP Methods

2013-11-04T08:46:13Z

‎Parameters

2013-10-21T07:52:38Z

Updated configuration

2013-08-28T12:18:45Z

‎Parameters

2013-08-19T19:40:09Z

‎Parameters: formatting correction on ISUP parameter

2013-08-19T19:39:02Z

Warning on SIP-T and bogus clients

2013-06-11T13:20:00Z

2013-06-11T11:21:04Z

@@ Line 608: / Line 608: @@
 '''See also'''
 * [[SIP IPv6 Support]]
 * [[SIP Features Module]]

@@ Line 76: / Line 76: @@
   ; ipv6: boolean: Listen on IPv6 address(es)
   ; Listen will fail if IPv6 support is not enabled or not supported
-  ; Defaults to no
+  ; Defaults to 'yes' if IP address is an IPv6 one or 'no' otherwise
   ;ipv6=no
@@ Line 132: / Line 132: @@
   ; Low priorities are not recommended except for debugging
   ;thread=normal
   ; floodevents: int: How many SIP events retrieved in a row trigger a flood warning and the drop mechanism
@@ Line 282: / Line 286: @@
   ; This parameter is applied on reload
   ;auth_foreign=disable
   ; body_encoding: keyword: Encoding used for received generic binary bodies
@@ Line 527: / Line 535: @@
   ; ipv6: boolean: Listen on IPv6 address(es)
   ; Listen will fail if IPv6 support is not enabled or not supported
-  ; Defaults to no
+  ; Defaults to 'yes' if IP address is an IPv6 one or 'no' otherwise
   ;ipv6=no
@@ Line 555: / Line 563: @@
   ;thread=normal
 == Parameters ==

@@ Line 17: / Line 17: @@
 ==Extending SIP functionalities==
-You can allow handling of SIP method requests that are not handled by default by setting them in '''[methods]''' section.
+You can allow handling of [[SIP Methods|SIP method]] requests that are not handled by default by setting them in '''[methods]''' section.
 Example: SUBSCRIBE, MESSAGE. For method SUBSCRIBE, you can then set in [[SIP Features Module|sipfeatures.conf]] the allowed events, and in [[Subscriptions|subscriptions.conf]] the actual logic for sending subscribe/notify.

← Older revision		Revision as of 08:46, 4 November 2013
Line 602:		Line 602:
	* [[Regfile]]		* [[Regfile]]
	* [[Telephony]]		* [[Telephony]]
		+
		+	[[Category:SIP]] [[Category:Listeners]]

@@ Line 493: / Line 493: @@
 * The usage of media formats is controlled by the '''[codecs]''' section. If ''default'' is set to false every codec will need to be enabled manually in the section. If ''default'' is set to true then the codecs for which Yate has a translator will be enabled by default. Every default codec setting can be overriden by explicitly setting it to true or false.
-* Subscribe allow SIP clients to subscribe to specific events. To use this feature in [default] section enable parameter '''generate'''.
+* Subscribe allows SIP clients to subscribe to specific events. To use this feature in [default] section enable parameter '''generate'''.
 * Yate can handle or generate SIP MESSAGE requests through '''sip.message''' and '''xsip.generate''' messages.

@@ Line 511: / Line 511: @@
 * '''isup'''
-ISUP signalling can be encapsulated in SIP using 2 protocols: SIP-T and SIP-I. Only SIP-T is supported by Yate.
+:- ISUP signalling can be encapsulated in SIP using 2 protocols: SIP-T and SIP-I. Only SIP-T is supported by Yate.
-To enable SIP-T support, enable the '''isup''' parameter in section '''[sip-t]'''.
+:- To enable SIP-T support, enable the '''isup''' parameter in section '''[sip-t]'''.
-'''Warning:''' Watch out for bogus SIP implementations. Some SIP clients will reply the MIME formatted SDP with a "488 Not Acceptable Here". Eg: X-Lite, Intelbras TIP-100
+:- '''Warning:''' Watch out for bogus SIP implementations. Some SIP clients will reply the MIME formatted SDP with a "488 Not Acceptable Here". Eg: X-Lite, Intelbras TIP-100
 * A set of listeners can be set so that Yate will listen to that interfaces. In a routing module: parameter ''oconnection_id'' it can be used to set on which IP to send outbound call legs for routing, and you can call an sip channel like this: extension=sip/sip:user@ip:port.

@@ Line 510: / Line 510: @@
 :- number of times to transmit a final response (parameter to set '''sip_rsp_trans_count''')
-* The way ISUP signalling is incapsulated in SIP it is done through 2 protocols: SIP-T and SIP-I. Only SIP-T is supported by Yate. Enable isup parameter in section '''[sip-t]'''.
+* '''isup'''
 * A set of listeners can be set so that Yate will listen to that interfaces. In a routing module: parameter ''oconnection_id'' it can be used to set on which IP to send outbound call legs for routing, and you can call an sip channel like this: extension=sip/sip:user@ip:port.

@@ Line 491: / Line 491: @@
 * The '''nat''' setting will try to replace nonroutable IP addresses of the RTP media stream with the address the SIP signalling was received from. This significantly improves chances that clients behind a dumb NAT get normal voice. This option is also enabled by default.
-* The usage of media formats is controlled by the '''[codecs]''' section. If ''default'' is set to false every codec will need to be enabled manually in the section. If ''default'' is set to true then the codecs for which Yate has a translator will be enabled by default. Every default codec setting can be overriden by explicitely setting it to true or false.
+* The usage of media formats is controlled by the '''[codecs]''' section. If ''default'' is set to false every codec will need to be enabled manually in the section. If ''default'' is set to true then the codecs for which Yate has a translator will be enabled by default. Every default codec setting can be overriden by explicitly setting it to true or false.
 * Subscribe allow SIP clients to subscribe to specific events. To use this feature in [default] section enable parameter '''generate'''.

@@ Line 4: / Line 4: @@
 This module is a VoIP SIP driver based on [[YASS]] library.
-By using the default configuration of this file, Yate will act as a SIP server that listens on all interfaces.
+By using the default configuration file, Yate will act as a SIP server that listens on all interfaces.
 ==Main functions==