| 
									
										
										
										
											2000-01-06 13:24:57 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; Inter-Asterisk eXchange v2 (IAX2) Channel Driver configuration | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; This configuration is read when the chan_iax2.so module is loaded, and is | 
					
						
							| 
									
										
										
										
											2012-03-05 11:20:00 +00:00
										 |  |  | ; re-read when the module is reloaded, such as when invoking the CLI command: | 
					
						
							| 
									
										
										
										
											2000-01-06 13:24:57 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ;     *CLI> iax2 reload | 
					
						
							| 
									
										
										
										
											2000-01-06 13:24:57 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  | ; General settings, like port number to bind to, and an option address (the | 
					
						
							|  |  |  | ; default is to bind to all local addresses). | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2000-01-06 13:24:57 +00:00
										 |  |  | [general] | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  | ; Listener Addresses | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; Use the 'bindaddr' and 'bindport' options to specify on which address and port | 
					
						
							|  |  |  | ; the IAX2 channel driver will listen for incoming requests. | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | ;bindport=4569           ; The default port to listen on | 
					
						
							|  |  |  |                          ; NOTE: bindport must be specified BEFORE bindaddr or | 
					
						
							|  |  |  |                          ; may be specified on a specific bindaddr if followed by | 
					
						
							| 
									
										
										
										
											2013-10-23 02:36:01 +00:00
										 |  |  |                          ; colon and port (e.g. bindaddr=192.168.0.1:4569) or for | 
					
						
							|  |  |  |                          ; IPv6 the address needs to be in brackets then colon | 
					
						
							|  |  |  |                          ; and port (e.g. bindaddr=[2001:db8::1]:4569). | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  | ;bindaddr=192.168.0.1    ; You can specify 'bindaddr' more than once to bind to | 
					
						
							|  |  |  |                          ; multiple addresses, but the first will be the | 
					
						
							| 
									
										
										
										
											2013-10-23 02:36:01 +00:00
										 |  |  |                          ; default. IPv6 addresses are accepted. | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; Set 'iaxcompat' to yes if you plan to use layered switches or some other | 
					
						
							|  |  |  | ; scenario which may cause some delay when doing a lookup in the dialplan. It | 
					
						
							|  |  |  | ; incurs a small performance hit to enable it. This option causes Asterisk to | 
					
						
							|  |  |  | ; spawn a separate thread when it receives an IAX2 DPREQ (Dialplan Request) | 
					
						
							|  |  |  | ; instead of blocking while it waits for a response. | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; Accepted values: yes, no | 
					
						
							|  |  |  | ; Default value:   no | 
					
						
							| 
									
										
										
										
											2004-02-01 20:08:36 +00:00
										 |  |  | ; | 
					
						
							|  |  |  | ;iaxcompat=yes | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2004-02-01 20:08:36 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2005-03-29 23:20:31 +00:00
										 |  |  | ; Disable UDP checksums (if nochecksums is set, then no checkums will | 
					
						
							|  |  |  | ; be calculated/checked on systems supporting this feature) | 
					
						
							|  |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; Accepted values: yes, no | 
					
						
							|  |  |  | ; Default value:   no | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ;nochecksums=yes | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2005-03-29 23:20:31 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; For increased security against brute force password attacks enable | 
					
						
							|  |  |  | ; 'delayreject' which will delay the sending of authentication reject for REGREQ | 
					
						
							|  |  |  | ; or AUTHREP if there is a password. | 
					
						
							| 
									
										
										
										
											2005-03-29 23:20:31 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; Accepted values: yes, no | 
					
						
							|  |  |  | ; Default value:   no | 
					
						
							| 
									
										
										
										
											2004-06-26 14:19:38 +00:00
										 |  |  | ; | 
					
						
							|  |  |  | ;delayreject=yes | 
					
						
							|  |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; You may specify a global default AMA flag for iaxtel calls.  These flags are | 
					
						
							|  |  |  | ; used in the generation of call detail records. | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; Accepted values: default, omit, billing, documentation | 
					
						
							|  |  |  | ; Default value:   default | 
					
						
							| 
									
										
										
										
											2002-01-07 02:01:04 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ;amaflags=billing | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2002-01-07 02:01:04 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; ADSI (Analog Display Services Interface) can be enabled if you have (or may | 
					
						
							|  |  |  | ; have) ADSI compatible CPE equipment. | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; Accepted values: yes, no | 
					
						
							|  |  |  | ; Default value:   no | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ;adsi=yes | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2006-07-14 21:49:40 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; Whether or not to perform an SRV lookup on outbound calls. | 
					
						
							| 
									
										
										
										
											2006-07-14 21:49:40 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; Accepted values: yes, no | 
					
						
							|  |  |  | ; Default value:   no | 
					
						
							| 
									
										
										
										
											2007-01-23 03:15:04 +00:00
										 |  |  | ; | 
					
						
							|  |  |  | ;srvlookup=yes | 
					
						
							|  |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; You may specify a default account for Call Detail Records (CDRs) in addition to | 
					
						
							|  |  |  | ; specifying on a per-user basis. | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; Accepted values: Any string value up to 19 characters in length | 
					
						
							|  |  |  | ; Default value:   <empty> | 
					
						
							| 
									
										
										
										
											2002-01-07 02:01:04 +00:00
										 |  |  | ; | 
					
						
							|  |  |  | ;accountcode=lss0101 | 
					
						
							|  |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; You may specify a global default language for users.  This can be specified | 
					
						
							|  |  |  | ; also on a per-user basis.  If omitted, will fallback to English (en). | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; Accepted values: A language tag such as 'en' or 'es' | 
					
						
							|  |  |  | ; Default value:   en | 
					
						
							| 
									
										
										
										
											2004-05-02 06:36:31 +00:00
										 |  |  | ; | 
					
						
							|  |  |  | ;language=en | 
					
						
							|  |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; This option specifies a preference for which music-on-hold class this channel | 
					
						
							| 
									
										
										
										
											2006-07-19 20:44:39 +00:00
										 |  |  | ; should listen to when put on hold if the music class has not been set on the | 
					
						
							|  |  |  | ; channel with Set(CHANNEL(musicclass)=whatever) in the dialplan, and the peer | 
					
						
							|  |  |  | ; channel putting this one on hold did not suggest a music class. | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; If this option is set to "passthrough", then the hold message will always be | 
					
						
							|  |  |  | ; passed through as signalling instead of generating hold music locally. | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; This option may be specified globally, or on a per-user or per-peer basis. | 
					
						
							|  |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; Accepted values: passthrough, or any music-on-hold class name | 
					
						
							|  |  |  | ; Default value:   <empty> | 
					
						
							|  |  |  | ; | 
					
						
							| 
									
										
										
										
											2006-07-19 20:44:39 +00:00
										 |  |  | ;mohinterpret=default | 
					
						
							|  |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; The 'mohsuggest' option specifies which music on hold class to suggest to the | 
					
						
							|  |  |  | ; peer channel when this channel places the peer on hold. It may be specified | 
					
						
							|  |  |  | ; globally or on a per-user or per-peer basis. | 
					
						
							| 
									
										
										
										
											2006-07-19 20:44:39 +00:00
										 |  |  | ; | 
					
						
							|  |  |  | ;mohsuggest=default | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2006-07-19 20:44:39 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2000-01-06 13:24:57 +00:00
										 |  |  | ; Specify bandwidth of low, medium, or high to control which codecs are used | 
					
						
							|  |  |  | ; in general. | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | bandwidth=low | 
					
						
							|  |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2000-01-06 13:24:57 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; You can also fine tune codecs here using "allow" and "disallow" clauses with | 
					
						
							|  |  |  | ; specific codecs.  Use "all" to represent all formats. | 
					
						
							| 
									
										
										
										
											2000-01-06 13:24:57 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ;allow=all | 
					
						
							|  |  |  | ;disallow=g723.1 | 
					
						
							|  |  |  | disallow=lpc10 | 
					
						
							|  |  |  | ;allow=gsm | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; | 
					
						
							|  |  |  | ; Jitter Buffer | 
					
						
							|  |  |  | ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; | 
					
						
							| 
									
										
										
										
											2004-07-01 21:55:06 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2004-07-12 15:33:40 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; You can adjust several parameters relating to the jitter buffer.  The jitter | 
					
						
							|  |  |  | ; buffer's function is to compensate for varying network delay. | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; All of the jitter buffer settings are in milliseconds.  The jitter buffer | 
					
						
							|  |  |  | ; works for INCOMING audio only - the outbound audio will be dejittered by the | 
					
						
							|  |  |  | ; jitter buffer at the other end. | 
					
						
							| 
									
										
										
										
											2004-07-01 21:55:06 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2004-09-17 12:45:03 +00:00
										 |  |  | ; jitterbuffer=yes|no: global default as to whether you want | 
					
						
							|  |  |  | ; the jitter buffer at all. | 
					
						
							| 
									
										
										
										
											2004-07-12 15:33:40 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2004-07-01 21:55:06 +00:00
										 |  |  | ; maxjitterbuffer: a maximum size for the jitter buffer. | 
					
						
							|  |  |  | ; Setting a reasonable maximum here will prevent the call delay | 
					
						
							| 
									
										
										
										
											2004-09-17 12:45:03 +00:00
										 |  |  | ; from rising to silly values in extreme situations; you'll hear | 
					
						
							|  |  |  | ; SOMETHING, even though it will be jittery. | 
					
						
							| 
									
										
										
										
											2004-07-01 21:55:06 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2005-05-19 00:34:28 +00:00
										 |  |  | ; resyncthreshold: when the jitterbuffer notices a significant change in delay | 
					
						
							|  |  |  | ; that continues over a few frames, it will resync, assuming that the change in | 
					
						
							| 
									
										
										
										
											2005-10-04 22:51:59 +00:00
										 |  |  | ; delay was caused by a timestamping mix-up. The threshold for noticing a | 
					
						
							|  |  |  | ; change in delay is measured as twice the measured jitter plus this resync | 
					
						
							|  |  |  | ; threshold. | 
					
						
							|  |  |  | ; Resyncing can be disabled by setting this parameter to -1. | 
					
						
							| 
									
										
										
										
											2005-05-19 00:34:28 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2005-10-04 22:51:59 +00:00
										 |  |  | ; maxjitterinterps: the maximum number of interpolation frames the jitterbuffer | 
					
						
							|  |  |  | ; should return in a row. Since some clients do not send CNG/DTX frames to | 
					
						
							|  |  |  | ; indicate silence, the jitterbuffer will assume silence has begun after | 
					
						
							|  |  |  | ; returning this many interpolations. This prevents interpolating throughout | 
					
						
							|  |  |  | ; a long silence. | 
					
						
							| 
									
										
										
										
											2006-05-10 16:14:26 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2006-12-21 00:24:08 +00:00
										 |  |  | ; jittertargetextra: number of milliseconds by which the new jitter buffer | 
					
						
							|  |  |  | ; will pad its size. the default is 40, so without modification, the new | 
					
						
							|  |  |  | ; jitter buffer will set its size to the jitter value plus 40 milliseconds. | 
					
						
							|  |  |  | ; increasing this value may help if your network normally has low jitter, | 
					
						
							|  |  |  | ; but occasionally has spikes. | 
					
						
							|  |  |  | ; | 
					
						
							| 
									
										
										
										
											2004-07-01 21:55:06 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2003-09-28 20:06:31 +00:00
										 |  |  | jitterbuffer=no | 
					
						
							| 
									
										
										
										
											2005-05-19 00:34:28 +00:00
										 |  |  | ;maxjitterbuffer=1000 | 
					
						
							| 
									
										
										
										
											2005-06-21 01:20:14 +00:00
										 |  |  | ;maxjitterinterps=10 | 
					
						
							| 
									
										
										
										
											2005-05-19 00:34:28 +00:00
										 |  |  | ;resyncthreshold=1000 | 
					
						
							| 
									
										
										
										
											2006-12-21 00:24:08 +00:00
										 |  |  | ;jittertargetextra=40 | 
					
						
							| 
									
										
										
										
											2004-07-01 21:55:06 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; | 
					
						
							|  |  |  | ; IAX2 Encryption | 
					
						
							|  |  |  | ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2003-03-16 06:00:11 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2008-08-01 18:16:24 +00:00
										 |  |  | ; Enable IAX2 encryption.  The default is no. | 
					
						
							|  |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ;encryption=yes | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2008-08-01 18:16:24 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; Force encryption insures no connection is established unless both sides | 
					
						
							|  |  |  | ; support encryption.  By turning this option on, encryption is automatically | 
					
						
							|  |  |  | ; turned on as well.  The default is no. | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ;forceencryption=yes | 
					
						
							| 
									
										
										
										
											2009-02-12 21:27:11 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2007-01-13 03:26:04 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; This option defines the maximum payload in bytes an IAX2 trunk can support at | 
					
						
							|  |  |  | ; a given time.  The best way to explain this is to provide an example.  If the | 
					
						
							|  |  |  | ; maximum number of calls to be supported is 800, and each call transmits 20ms | 
					
						
							|  |  |  | ; frames of audio using ulaw: | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ;     (8000hz / 1000ms) * 20ms * 1 byte per sample = 160 bytes per frame | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; The maximum load in bytes is: | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ;     (160 bytes per frame) * (800 calls) = 128000 bytes | 
					
						
							| 
									
										
										
										
											2009-10-12 20:58:27 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; Once this limit is reached, calls may be dropped or begin to lose audio. | 
					
						
							|  |  |  | ; Depending on the codec in use and number of channels to be supported this value | 
					
						
							|  |  |  | ; may need to be raised, but in most cases the default value is large enough. | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; trunkmaxsize = 128000 ; defaults to 128000 bytes, which supports up to 800 | 
					
						
							|  |  |  |                         ; calls of ulaw at 20ms a frame. | 
					
						
							| 
									
										
										
										
											2009-10-12 20:58:27 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; With a large amount of traffic on IAX2 trunks, there is a risk of bad voice | 
					
						
							|  |  |  | ; quality when allowing the Linux system to handle fragmentation of UDP packets. | 
					
						
							|  |  |  | ; Depending on the size of each payload, allowing the OS to handle fragmentation | 
					
						
							|  |  |  | ; may not be very efficient. This setting sets the maximum transmission unit for | 
					
						
							|  |  |  | ; IAX2 UDP trunking. The default is 1240 bytes which means if a trunk's payload | 
					
						
							|  |  |  | ; is over 1240 bytes for every 20ms it will be broken into multiple 1240 byte | 
					
						
							|  |  |  | ; messages.  Zero disables this functionality and let's the OS handle | 
					
						
							| 
									
										
										
										
											2009-10-12 20:58:27 +00:00
										 |  |  | ; fragmentation. | 
					
						
							|  |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; trunkmtu = 1240    ; trunk data will be sent in 1240 byte messages. | 
					
						
							| 
									
										
										
										
											2009-10-12 20:58:27 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; trunkfreq sets how frequently trunk messages are sent in milliseconds. This | 
					
						
							|  |  |  | ; value is 20ms by default, which means the trunk will send all the data queued | 
					
						
							|  |  |  | ; to it in the past 20ms.  By increasing the time between sending trunk messages, | 
					
						
							|  |  |  | ; the trunk's payload size will increase as well.  Note, depending on the size | 
					
						
							|  |  |  | ; set by trunkmtu, messages may be sent more often than specified.  For example | 
					
						
							|  |  |  | ; if a trunk's message size grows to the trunkmtu size before 20ms is reached | 
					
						
							|  |  |  | ; that message will be sent immediately.  Acceptable values are between 10ms and | 
					
						
							| 
									
										
										
										
											2012-02-17 22:03:56 +00:00
										 |  |  | ; 1000ms. | 
					
						
							| 
									
										
										
										
											2009-10-12 20:58:27 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; trunkfreq=20    ; How frequently to send trunk msgs (in ms). This is 20ms by | 
					
						
							|  |  |  |                   ; default. | 
					
						
							| 
									
										
										
										
											2009-10-12 20:58:27 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  | ; Should we send timestamps for the individual sub-frames within trunk frames? | 
					
						
							|  |  |  | ; There is a small bandwidth use for these (less than 1kbps/call), but they | 
					
						
							|  |  |  | ; ensure that frame timestamps get sent end-to-end properly.  If both ends of | 
					
						
							|  |  |  | ; all your trunks go directly to TDM, _and_ your trunkfreq equals the frame | 
					
						
							|  |  |  | ; length for your codecs, you can probably suppress these.  The receiver must | 
					
						
							|  |  |  | ; also support this feature, although they do not also need to have it enabled. | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; trunktimestamps=yes | 
					
						
							| 
									
										
										
										
											2007-01-13 03:26:04 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; Minimum and maximum amounts of time that IAX2 peers can request as a | 
					
						
							|  |  |  | ; registration expiration interval (in seconds). | 
					
						
							|  |  |  | ; minregexpire = 60 | 
					
						
							|  |  |  | ; maxregexpire = 60 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | ; IAX2 helper threads | 
					
						
							| 
									
										
										
										
											2006-10-25 14:26:22 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2006-02-26 20:27:14 +00:00
										 |  |  | ; Establishes the number of iax helper threads to handle I/O. | 
					
						
							|  |  |  | ; iaxthreadcount = 10 | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2006-04-11 16:44:10 +00:00
										 |  |  | ; Establishes the number of extra dynamic threads that may be spawned to handle I/O | 
					
						
							|  |  |  | ; iaxmaxthreadcount = 100 | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2006-02-26 20:27:14 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; We can register with another IAX2 server to let him know where we are | 
					
						
							| 
									
										
										
										
											2001-05-07 20:53:39 +00:00
										 |  |  | ; in case we have a dynamic IP address for example | 
					
						
							|  |  |  | ; | 
					
						
							| 
									
										
										
										
											2002-01-07 02:01:04 +00:00
										 |  |  | ; Register with tormenta using username marko and password secretpass | 
					
						
							|  |  |  | ; | 
					
						
							| 
									
										
										
										
											2001-05-07 20:53:39 +00:00
										 |  |  | ;register => marko:secretpass@tormenta.linux-support.net | 
					
						
							| 
									
										
										
										
											2002-01-07 02:01:04 +00:00
										 |  |  | ; | 
					
						
							|  |  |  | ; Register joe at remote host with no password | 
					
						
							|  |  |  | ; | 
					
						
							| 
									
										
										
										
											2001-05-07 20:53:39 +00:00
										 |  |  | ;register => joe@remotehost:5656 | 
					
						
							|  |  |  | ; | 
					
						
							| 
									
										
										
										
											2002-01-07 02:01:04 +00:00
										 |  |  | ; Register marko at tormenta.linux-support.net using RSA key "torkey" | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ;register => marko:[torkey]@tormenta.linux-support.net | 
					
						
							|  |  |  | ; | 
					
						
							| 
									
										
										
										
											2004-06-02 23:19:36 +00:00
										 |  |  | ; Sample Registration for iaxtel | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; Visit http://www.iaxtel.com to register with iaxtel.  Replace "user" | 
					
						
							| 
									
										
										
										
											2009-05-28 14:39:21 +00:00
										 |  |  | ; and "pass" with your username and password for iaxtel.  Incoming | 
					
						
							| 
									
										
										
										
											2004-06-02 23:19:36 +00:00
										 |  |  | ; calls arrive at the "s" extension of "default" context. | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ;register => user:pass@iaxtel.com | 
					
						
							|  |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; Sample Registration for IAX2 + FWD | 
					
						
							| 
									
										
										
										
											2004-06-02 23:19:36 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; To register using IAX2 with FWD, it must be enabled by visiting the URL | 
					
						
							| 
									
										
										
										
											2004-06-02 23:19:36 +00:00
										 |  |  | ; http://www.fwdnet.net/index.php?section_id=112 | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; Note that you need an extension in you default context which matches | 
					
						
							|  |  |  | ; your free world dialup number.  Please replace "FWDNumber" with your | 
					
						
							|  |  |  | ; FWD number and "passwd" with your password. | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ;register => FWDNumber:passwd@iax.fwdnet.net | 
					
						
							|  |  |  | ; | 
					
						
							| 
									
										
										
										
											2010-08-13 20:05:44 +00:00
										 |  |  | ; Through the use of the res_stun_monitor module, Asterisk has the ability to detect when the | 
					
						
							|  |  |  | ; perceived external network address has changed.  When the stun_monitor is installed and | 
					
						
							|  |  |  | ; configured, chan_iax will renew all outbound registrations when the monitor detects any sort | 
					
						
							|  |  |  | ; of network change has occurred. By default this option is enabled, but only takes effect once | 
					
						
							|  |  |  | ; res_stun_monitor is configured.  If res_stun_monitor is enabled and you wish to not | 
					
						
							|  |  |  | ; generate all outbound registrations on a network change, use the option below to disable | 
					
						
							|  |  |  | ; this feature. | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; subscribe_network_change_event = yes ; on by default | 
					
						
							| 
									
										
										
										
											2003-12-04 03:41:22 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2011-09-06 16:08:10 +00:00
										 |  |  | ; You can enable authentication debugging to increase the amount of | 
					
						
							| 
									
										
										
										
											2003-12-04 03:41:22 +00:00
										 |  |  | ; debugging traffic. | 
					
						
							|  |  |  | ; | 
					
						
							| 
									
										
										
										
											2011-09-06 16:08:10 +00:00
										 |  |  | ;authdebug = yes | 
					
						
							| 
									
										
										
										
											2003-12-04 03:41:22 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2011-02-02 19:30:49 +00:00
										 |  |  | ; See https://wiki.asterisk.org/wiki/display/AST/IP+Quality+of+Service for a description of these parameters. | 
					
						
							| 
									
										
										
										
											2006-03-28 03:28:52 +00:00
										 |  |  | ;tos=ef | 
					
						
							| 
									
										
										
										
											2007-04-30 16:16:26 +00:00
										 |  |  | ;cos=5 | 
					
						
							| 
									
										
										
										
											2002-05-11 17:26:19 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2005-10-04 22:51:59 +00:00
										 |  |  | ; If regcontext is specified, Asterisk will dynamically create and destroy | 
					
						
							|  |  |  | ; a NoOp priority 1 extension for a given peer who registers or unregisters | 
					
						
							|  |  |  | ; with us.  The actual extension is the 'regexten' parameter of the registering | 
					
						
							|  |  |  | ; peer or its name if 'regexten' is not provided.  More than one regexten | 
					
						
							|  |  |  | ; may be supplied if they are separated by '&'.  Patterns may be used in | 
					
						
							|  |  |  | ; regexten. | 
					
						
							| 
									
										
										
										
											2004-09-07 23:45:34 +00:00
										 |  |  | ; | 
					
						
							|  |  |  | ;regcontext=iaxregistrations | 
					
						
							|  |  |  | ; | 
					
						
							| 
									
										
										
										
											2005-10-04 22:51:59 +00:00
										 |  |  | ; If we don't get ACK to our NEW within 2000ms, and autokill is set to yes, | 
					
						
							|  |  |  | ; then we cancel the whole thing (that's enough time for one retransmission | 
					
						
							|  |  |  | ; only).  This is used to keep things from stalling for a long time for a host | 
					
						
							|  |  |  | ; that is not available, but would be ill advised for bad connections.  In | 
					
						
							|  |  |  | ; addition to 'yes' or 'no' you can also specify a number of milliseconds. | 
					
						
							|  |  |  | ; See 'qualify' for individual peers to turn on for just a specific peer. | 
					
						
							| 
									
										
										
										
											2004-10-10 01:42:46 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2005-03-26 15:22:15 +00:00
										 |  |  | autokill=yes | 
					
						
							| 
									
										
										
										
											2005-01-20 23:42:06 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; codecpriority controls the codec negotiation of an inbound IAX2 call. | 
					
						
							| 
									
										
										
										
											2009-05-28 14:39:21 +00:00
										 |  |  | ; This option is inherited to all user entities.  It can also be defined | 
					
						
							| 
									
										
										
										
											2005-02-16 02:58:18 +00:00
										 |  |  | ; in each user entity separately which will override the setting in general. | 
					
						
							| 
									
										
										
										
											2005-01-20 23:42:06 +00:00
										 |  |  | ; | 
					
						
							|  |  |  | ; The valid values are: | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; caller   - Consider the callers preferred order ahead of the host's. | 
					
						
							|  |  |  | ; host     - Consider the host's preferred order ahead of the caller's. | 
					
						
							| 
									
										
										
										
											2006-09-11 16:41:49 +00:00
										 |  |  | ; disabled - Disable the consideration of codec preference altogether. | 
					
						
							| 
									
										
										
										
											2005-01-20 23:42:06 +00:00
										 |  |  | ;            (this is the original behaviour before preferences were added) | 
					
						
							|  |  |  | ; reqonly  - Same as disabled, only do not consider capabilities if | 
					
						
							|  |  |  | ;            the requested format is not available the call will only | 
					
						
							|  |  |  | ;            be accepted if the requested format is available. | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; The default value is 'host' | 
					
						
							|  |  |  | ; | 
					
						
							| 
									
										
										
										
											2005-03-26 15:22:15 +00:00
										 |  |  | ;codecpriority=host | 
					
						
							| 
									
										
										
										
											2008-07-22 21:53:40 +00:00
										 |  |  | ; | 
					
						
							|  |  |  | ; allowfwdownload controls whether this host will serve out firmware to | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; IAX2 clients which request it.  This has only been used for the IAXy, | 
					
						
							| 
									
										
										
										
											2008-07-22 21:53:40 +00:00
										 |  |  | ; and it has been recently proven that this firmware distribution method | 
					
						
							|  |  |  | ; can be used as a source of traffic amplification attacks.  Also, the | 
					
						
							|  |  |  | ; IAXy firmware has not been updated for at least 18 months, so unless | 
					
						
							|  |  |  | ; you are provisioning IAXys in a secure network, we recommend that you | 
					
						
							|  |  |  | ; leave this option to the default, off. | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ;allowfwdownload=yes | 
					
						
							| 
									
										
										
										
											2005-02-10 20:04:42 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2012-03-05 11:20:00 +00:00
										 |  |  | ;rtcachefriends=yes ; Cache realtime friends by adding them to the internal list | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  |                     ; just like friends added from the config file only on a | 
					
						
							|  |  |  |                     ; as-needed basis? (yes|no) | 
					
						
							| 
									
										
										
										
											2005-09-02 14:19:36 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ;rtsavesysname=yes  ; Save systemname in realtime database at registration | 
					
						
							|  |  |  |                     ; Default = no | 
					
						
							| 
									
										
										
										
											2009-06-17 21:56:42 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ;rtupdate=yes       ; Send registry updates to database using realtime? (yes|no) | 
					
						
							|  |  |  |                     ; If set to yes, when a IAX2 peer registers successfully, | 
					
						
							|  |  |  |                     ; the IP address, the origination port, the registration period, | 
					
						
							|  |  |  |                     ; and the username of the peer will be set to database via realtime. | 
					
						
							|  |  |  |                     ; If not present, defaults to 'yes'. | 
					
						
							| 
									
										
										
										
											2005-09-02 14:19:36 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ;rtautoclear=yes    ; Auto-Expire friends created on the fly on the same schedule | 
					
						
							|  |  |  |                     ; as if it had just registered? (yes|no|<seconds>) | 
					
						
							|  |  |  |                     ; If set to yes, when the registration expires, the friend will | 
					
						
							|  |  |  |                     ; vanish from the configuration until requested again. | 
					
						
							|  |  |  |                     ; If set to an integer, friends expire within this number of | 
					
						
							|  |  |  |                     ; seconds instead of the registration interval. | 
					
						
							| 
									
										
										
										
											2005-09-02 14:19:36 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ;rtignoreregexpire=yes ; When reading a peer from Realtime, if the peer's registration | 
					
						
							|  |  |  |                        ; has expired based on its registration interval, used the stored | 
					
						
							|  |  |  |                        ; address information regardless. (yes|no) | 
					
						
							| 
									
										
										
										
											2008-04-21 23:42:45 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ;parkinglot=edvina     ; Default parkinglot for IAX2 peers and users | 
					
						
							|  |  |  |                        ; This can also be configured per device | 
					
						
							|  |  |  |                        ; Parkinglots are defined in features.conf | 
					
						
							| 
									
										
										
										
											2009-09-03 16:31:54 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; The following two options are used to disable call token validation for the | 
					
						
							|  |  |  | ; purposes of interoperability with IAX2 endpoints that do not yet support it. | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; Call token validation can be set as optional for a single IP address or IP | 
					
						
							|  |  |  | ; address range by using the 'calltokenoptional' option. 'calltokenoptional' is | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; only a global option. | 
					
						
							| 
									
										
										
										
											2009-09-03 16:31:54 +00:00
										 |  |  | ; | 
					
						
							|  |  |  | ;calltokenoptional=209.16.236.73/255.255.255.0 | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; By setting 'requirecalltoken=no', call token validation becomes optional for | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; that peer/user.  By setting 'requirecalltoken=auto', call token validation | 
					
						
							| 
									
										
										
										
											2009-09-03 16:31:54 +00:00
										 |  |  | ; is optional until a call token supporting peer registers successfully using | 
					
						
							|  |  |  | ; call token validation.  This is used as an indication that from now on, we | 
					
						
							|  |  |  | ; can require it from this peer.  So, requirecalltoken is internally set to yes. | 
					
						
							| 
									
										
										
										
											2009-12-04 21:54:44 +00:00
										 |  |  | ; requirecalltoken may only be used in peer/user/friend definitions, | 
					
						
							|  |  |  | ; not in the global scope. | 
					
						
							| 
									
										
										
										
											2009-09-03 16:31:54 +00:00
										 |  |  | ; By default, 'requirecalltoken=yes'. | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ;requirecalltoken=no | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; These options are used to limit the amount of call numbers allocated to a | 
					
						
							|  |  |  | ; single IP address.  Before changing any of these values, it is highly encouraged | 
					
						
							|  |  |  | ; to read the user guide associated with these options first.  In most cases, the | 
					
						
							|  |  |  | ; default values for these options are sufficient. | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; The 'maxcallnumbers' option limits the amount of call numbers allowed for each | 
					
						
							|  |  |  | ; individual remote IP address.  Once an IP address reaches it's call number | 
					
						
							|  |  |  | ; limit, no more new connections are allowed until the previous ones close.  This | 
					
						
							|  |  |  | ; option can be used in a peer definition as well, but only takes effect for | 
					
						
							|  |  |  | ; the IP of a dynamic peer after it completes registration. | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ;maxcallnumbers=512 | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; The 'maxcallnumbers_nonvalidated' is used to set the combined number of call | 
					
						
							|  |  |  | ; numbers that can be allocated for connections where call token  validation | 
					
						
							|  |  |  | ; has been disabled.  Unlike the 'maxcallnumbers' option, this limit is not | 
					
						
							|  |  |  | ; separate for each individual IP address.  Any connection resulting in a | 
					
						
							|  |  |  | ; non-call token validated call number being allocated contributes to this | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; limit.  For use cases, see the call token user guide.  This option's | 
					
						
							| 
									
										
										
										
											2009-09-03 16:31:54 +00:00
										 |  |  | ; default value of 8192 should be sufficient in most cases. | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ;maxcallnumbers_nonvalidated=1024 | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; The [callnumberlimits] section allows custom call number limits to be set | 
					
						
							|  |  |  | ; for specific IP addresses and IP address ranges.  These limits take precedence | 
					
						
							|  |  |  | ; over the global 'maxcallnumbers' option, but may still be overridden by a | 
					
						
							|  |  |  | ; peer defined 'maxcallnumbers' entry.  Note that these limits take effect | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; for every individual address within the range, not the range as a whole. | 
					
						
							| 
									
										
										
										
											2009-09-03 16:31:54 +00:00
										 |  |  | ; | 
					
						
							|  |  |  | ;[callnumberlimits] | 
					
						
							|  |  |  | ;10.1.1.0/255.255.255.0 = 24 | 
					
						
							|  |  |  | ;10.1.2.0/255.255.255.0 = 32 | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2009-10-21 14:39:10 +00:00
										 |  |  | ; The shrinkcallerid function removes '(', ' ', ')', non-trailing '.', and '-' not | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; in square brackets.  For example, the Caller*ID value 555.5555 becomes 5555555 | 
					
						
							| 
									
										
										
										
											2009-10-21 14:39:10 +00:00
										 |  |  | ; when this option is enabled.  Disabling this option results in no modification | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; of the Caller*ID value, which is necessary when the Caller*ID represents something | 
					
						
							| 
									
										
										
										
											2009-10-21 14:39:10 +00:00
										 |  |  | ; that must be preserved.  This option can only be used in the [general] section. | 
					
						
							|  |  |  | ; By default this option is on. | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ;shrinkcallerid=yes     ; on by default | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2005-10-04 22:51:59 +00:00
										 |  |  | ; Guest sections for unauthenticated connection attempts.  Just specify an | 
					
						
							|  |  |  | ; empty secret, or provide no secret section. | 
					
						
							| 
									
										
										
										
											2002-05-11 17:26:19 +00:00
										 |  |  | ; | 
					
						
							|  |  |  | [guest] | 
					
						
							|  |  |  | type=user | 
					
						
							| 
									
										
										
										
											2011-12-12 17:34:39 +00:00
										 |  |  | context=public | 
					
						
							| 
									
										
										
										
											2002-05-11 17:26:19 +00:00
										 |  |  | callerid="Guest IAX User" | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2001-10-04 20:02:12 +00:00
										 |  |  | ; | 
					
						
							|  |  |  | ; Trust Caller*ID Coming from iaxtel.com | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | [iaxtel] | 
					
						
							|  |  |  | type=user | 
					
						
							|  |  |  | context=default | 
					
						
							| 
									
										
										
										
											2002-01-07 02:01:04 +00:00
										 |  |  | auth=rsa | 
					
						
							|  |  |  | inkeys=iaxtel | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | ; | 
					
						
							| 
									
										
										
										
											2004-06-02 23:19:36 +00:00
										 |  |  | ; Trust Caller*ID Coming from iax.fwdnet.net | 
					
						
							| 
									
										
										
										
											2002-01-07 02:01:04 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2004-06-02 23:19:36 +00:00
										 |  |  | [iaxfwd] | 
					
						
							| 
									
										
										
										
											2002-01-07 02:01:04 +00:00
										 |  |  | type=user | 
					
						
							|  |  |  | context=default | 
					
						
							| 
									
										
										
										
											2004-06-02 23:19:36 +00:00
										 |  |  | auth=rsa | 
					
						
							|  |  |  | inkeys=freeworlddialup | 
					
						
							| 
									
										
										
										
											2001-05-07 20:53:39 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2004-10-18 21:45:13 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; Trust Caller*ID delivered over DUNDi/e164 | 
					
						
							| 
									
										
										
										
											2004-10-18 21:45:13 +00:00
										 |  |  | ; | 
					
						
							|  |  |  | ;[dundi] | 
					
						
							|  |  |  | ;type=user | 
					
						
							|  |  |  | ;dbsecret=dundi/secret | 
					
						
							|  |  |  | ;context=dundi-e164-local | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2000-01-06 13:24:57 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2005-10-04 22:51:59 +00:00
										 |  |  | ; Further user sections may be added, specifying a context and a secret used | 
					
						
							|  |  |  | ; for connections with that given authentication name.  Limited IP based | 
					
						
							| 
									
										
										
										
											2012-07-11 18:33:36 +00:00
										 |  |  | ; access control is allowed by use of "permit", "deny", and "acl" keywords. | 
					
						
							|  |  |  | ; Multiple rules are permitted. Multiple permitted contexts may be specified, | 
					
						
							|  |  |  | ; in which case the first will be the default.  You can also override | 
					
						
							|  |  |  | ; Caller*ID so that when you receive a call you set the Caller*ID to be what | 
					
						
							|  |  |  | ; you want instead of trusting what the remote user provides | 
					
						
							| 
									
										
										
										
											2000-01-06 13:24:57 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2002-01-07 02:01:04 +00:00
										 |  |  | ; There are three authentication methods that are supported:  md5, plaintext, | 
					
						
							|  |  |  | ; and rsa.  The least secure is "plaintext", which sends passwords cleartext | 
					
						
							|  |  |  | ; across the net.  "md5" uses a challenge/response md5 sum arrangement, but | 
					
						
							|  |  |  | ; still requires both ends have plain text access to the secret.  "rsa" allows | 
					
						
							|  |  |  | ; unidirectional secret knowledge through public/private keys.  If "rsa" | 
					
						
							| 
									
										
										
										
											2009-05-28 14:39:21 +00:00
										 |  |  | ; authentication is used, "inkeys" is a list of acceptable public keys on the | 
					
						
							| 
									
										
										
										
											2002-01-07 02:01:04 +00:00
										 |  |  | ; local system that can be used to authenticate the remote peer, separated by | 
					
						
							|  |  |  | ; the ":" character.  "outkey" is a single, private key to use to authenticate | 
					
						
							|  |  |  | ; to the other side.  Public keys are named /var/lib/asterisk/keys/<name>.pub | 
					
						
							|  |  |  | ; while private keys are named /var/lib/asterisk/keys/<name>.key.  Private | 
					
						
							|  |  |  | ; keys should always be 3DES encrypted. | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ; | 
					
						
							| 
									
										
										
										
											2006-02-22 17:33:38 +00:00
										 |  |  | ; NOTE: All hostnames and IP addresses in this file are for example purposes | 
					
						
							|  |  |  | ;       only; you should not expect any of them to actually be available for | 
					
						
							|  |  |  | ;       your use. | 
					
						
							|  |  |  | ; | 
					
						
							| 
									
										
										
										
											2000-01-06 13:24:57 +00:00
										 |  |  | ;[markster] | 
					
						
							|  |  |  | ;type=user | 
					
						
							|  |  |  | ;context=default | 
					
						
							|  |  |  | ;context=local | 
					
						
							| 
									
										
										
										
											2002-01-07 02:01:04 +00:00
										 |  |  | ;auth=md5,plaintext,rsa | 
					
						
							| 
									
										
										
										
											2000-01-06 13:24:57 +00:00
										 |  |  | ;secret=markpasswd | 
					
						
							| 
									
										
										
										
											2008-07-30 16:40:43 +00:00
										 |  |  | ;setvar=ATTENDED_TRANSFER_COMPLETE_SOUND=beep   ; This channel variable will | 
					
						
							| 
									
										
										
										
											2009-05-28 14:39:21 +00:00
										 |  |  |                                                 ; cause the given audio file to | 
					
						
							|  |  |  |                                                 ; be played upon completion of | 
					
						
							| 
									
										
										
										
											2013-06-06 22:46:54 +00:00
										 |  |  |                                                 ; an attended transfer to the | 
					
						
							|  |  |  |                                                 ; target of the transfer. | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ;dbsecret=mysecrets/place    ; Secrets can be stored in astdb, too | 
					
						
							|  |  |  | ;transfer=no                 ; Disable IAX2 native transfer | 
					
						
							|  |  |  | ;transfer=mediaonly          ; When doing IAX2 native transfers, transfer only | 
					
						
							|  |  |  |                              ; the media stream | 
					
						
							|  |  |  | ;jitterbuffer=yes            ; Override the global setting and enable the jitter | 
					
						
							|  |  |  |                              ; buffer for this user | 
					
						
							|  |  |  | ;maxauthreq=10               ; Set the maximum number of outstanding AUTHREQs | 
					
						
							|  |  |  |                              ; waiting for replies. If this limit is reached, | 
					
						
							|  |  |  |                              ; any further authentication will be blocked, until | 
					
						
							|  |  |  |                              ; the pending requests expire or a reply is | 
					
						
							|  |  |  |                              ; received. | 
					
						
							| 
									
										
										
										
											2001-10-04 20:02:12 +00:00
										 |  |  | ;callerid="Mark Spencer" <(256) 428-6275> | 
					
						
							| 
									
										
										
										
											2000-01-06 13:24:57 +00:00
										 |  |  | ;deny=0.0.0.0/0.0.0.0 | 
					
						
							| 
									
										
										
										
											2002-01-07 02:01:04 +00:00
										 |  |  | ;accountcode=markster0101 | 
					
						
							| 
									
										
										
										
											2001-10-04 20:02:12 +00:00
										 |  |  | ;permit=209.16.236.73/255.255.255.0 | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ;language=en                 ; Use english as default language | 
					
						
							|  |  |  | ;encryption=yes              ; Enable IAX2 encryption.  The default is no. | 
					
						
							|  |  |  | ;keyrotate=off               ; This is a compatibility option for older versions | 
					
						
							|  |  |  |                              ; of IAX2 that do not support key rotation with | 
					
						
							|  |  |  |                              ; encryption.  This option will disable the | 
					
						
							|  |  |  |                              ; IAX_COMMAND_RTENC message.  The default is on. | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2000-01-06 13:24:57 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; Peers may also be specified, with a secret and a remote hostname. | 
					
						
							| 
									
										
										
										
											2000-01-06 13:24:57 +00:00
										 |  |  | ; | 
					
						
							|  |  |  | [demo] | 
					
						
							|  |  |  | type=peer | 
					
						
							| 
									
										
										
										
											2003-10-08 00:09:59 +00:00
										 |  |  | username=asterisk | 
					
						
							| 
									
										
										
										
											2000-01-06 13:24:57 +00:00
										 |  |  | secret=supersecret | 
					
						
							| 
									
										
										
										
											2002-11-29 05:30:52 +00:00
										 |  |  | host=216.207.245.47 | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | description=Demo System At Digium    ; Description of this peer, as listed by | 
					
						
							|  |  |  |                                      ; 'iax2 show peers' | 
					
						
							| 
									
										
										
										
											2002-02-18 20:25:25 +00:00
										 |  |  | ;sendani=no | 
					
						
							| 
									
										
										
										
											2000-01-06 13:24:57 +00:00
										 |  |  | ;host=asterisk.linux-support.net | 
					
						
							|  |  |  | ;port=5036 | 
					
						
							|  |  |  | ;mask=255.255.255.255 | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ;qualify=yes                ; Make sure this peer is alive. | 
					
						
							|  |  |  | ;qualifysmoothing = yes     ; Use an average of the last two PONG results to | 
					
						
							|  |  |  |                             ; reduce falsely detected LAGGED hosts.  The default | 
					
						
							|  |  |  |                             ; is 'no.' | 
					
						
							|  |  |  | ;qualifyfreqok = 60000      ; How frequently to ping the peer when everything | 
					
						
							|  |  |  |                             ; seems to be OK, in milliseconds. | 
					
						
							|  |  |  | ;qualifyfreqnotok = 10000   ; How frequently to ping the peer when it's either | 
					
						
							|  |  |  |                             ; LAGGED or UNAVAILABLE, in milliseconds. | 
					
						
							|  |  |  | ;jitterbuffer=no            ; Turn off jitter buffer for this peer | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ;encryption=yes             ; Enable IAX2 encryption.  The default is no. | 
					
						
							|  |  |  | ;keyrotate=off              ; This is a compatibility option for older versions | 
					
						
							|  |  |  |                             ; of IAX2 that do not support key rotation with | 
					
						
							|  |  |  |                             ; encryption.  This option will disable the | 
					
						
							|  |  |  |                             ; IAX_COMMAND_RTENC message.  The default is 'on.' | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2005-10-04 22:51:59 +00:00
										 |  |  | ; Peers can remotely register as well, so that they can be mobile.  Default | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; IPs can also optionally be given but are not required.  Caller*ID can be | 
					
						
							| 
									
										
										
										
											2005-10-04 22:51:59 +00:00
										 |  |  | ; suggested to the other side as well if it is for example a phone instead of | 
					
						
							|  |  |  | ; another PBX. | 
					
						
							| 
									
										
										
										
											2014-02-07 18:29:49 +00:00
										 |  |  | ;connectedline=yes ; Set if connected line and redirecting information updates | 
					
						
							|  |  |  | ;                  ; are passed between Asterisk servers for this peer. | 
					
						
							|  |  |  | ;                  ; yes - Sending and receiving updates are enabled. | 
					
						
							|  |  |  | ;                  ; send - Only send updates. | 
					
						
							|  |  |  | ;                  ; receive - Only process received updates. | 
					
						
							|  |  |  | ;                  ; no - Sending and receiving updates are disabled. | 
					
						
							|  |  |  | ;                  ; Default is "no". | 
					
						
							|  |  |  | ;                  ; | 
					
						
							|  |  |  | ;                  ; Note: Because of an incompatibility between Asterisk v1.4 | 
					
						
							|  |  |  | ;                  ; and Asterisk v1.8 or later, this option must be set | 
					
						
							|  |  |  | ;                  ; to "no" toward the Asterisk v1.4 peer.  A symptom of the | 
					
						
							|  |  |  | ;                  ; incompatibility is the call gets disconnected unexpectedly. | 
					
						
							| 
									
										
										
										
											2013-07-21 02:26:31 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2001-10-04 20:02:12 +00:00
										 |  |  | 
 | 
					
						
							|  |  |  | ;[dynamichost] | 
					
						
							|  |  |  | ;host=dynamic | 
					
						
							|  |  |  | ;secret=mysecret | 
					
						
							| 
									
										
										
										
											2013-12-19 16:52:43 +00:00
										 |  |  | ; Note: app_voicemail mailboxes must be in the form of mailbox@context. | 
					
						
							| 
									
										
										
										
											2003-03-14 06:00:20 +00:00
										 |  |  | ;mailbox=1234		; Notify about mailbox 1234 | 
					
						
							| 
									
										
										
										
											2002-01-07 02:01:04 +00:00
										 |  |  | ;inkeys=key1:key2 | 
					
						
							| 
									
										
										
										
											2004-06-26 15:48:30 +00:00
										 |  |  | ;peercontext=local	; Default context to request for calls to peer | 
					
						
							| 
									
										
										
										
											2001-10-04 20:02:12 +00:00
										 |  |  | ;defaultip=216.207.245.34 | 
					
						
							|  |  |  | ;callerid="Some Host" <(256) 428-6011> | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2003-03-14 06:00:20 +00:00
										 |  |  | ;[biggateway] | 
					
						
							|  |  |  | ;type=peer | 
					
						
							|  |  |  | ;host=192.168.0.1 | 
					
						
							| 
									
										
										
										
											2011-04-13 15:49:33 +00:00
										 |  |  | ;description=Gateway to PSTN | 
					
						
							| 
									
										
										
										
											2004-08-31 14:59:58 +00:00
										 |  |  | ;context=* | 
					
						
							| 
									
										
										
										
											2003-03-14 06:00:20 +00:00
										 |  |  | ;secret=myscret | 
					
						
							| 
									
										
										
										
											2004-11-09 05:05:07 +00:00
										 |  |  | ;trunk=yes			; Use IAX2 trunking with this host | 
					
						
							|  |  |  | ;timezone=America/New_York	; Set a timezone for the date/time IE | 
					
						
							| 
									
										
										
										
											2003-03-14 06:00:20 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2001-10-04 20:02:12 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; Friends are a shortcut for creating a user and a peer with the same values. | 
					
						
							| 
									
										
										
										
											2001-10-04 20:02:12 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2001-10-04 20:02:12 +00:00
										 |  |  | ;[marko] | 
					
						
							|  |  |  | ;type=friend | 
					
						
							|  |  |  | ;host=dynamic | 
					
						
							| 
									
										
										
										
											2004-09-07 23:45:34 +00:00
										 |  |  | ;regexten=1234 | 
					
						
							| 
									
										
										
										
											2006-06-18 20:18:41 +00:00
										 |  |  | ;secret=moofoo   ; Multiple secrets may be specified. For a "user", all | 
					
						
							|  |  |  | ;secret=foomoo   ; specified entries will be accepted as valid. For a "peer", | 
					
						
							|  |  |  | ;secret=shazbot  ; only the last specified secret will be used. | 
					
						
							| 
									
										
										
										
											2001-10-04 20:02:12 +00:00
										 |  |  | ;context=default | 
					
						
							| 
									
										
										
										
											2002-01-07 02:01:04 +00:00
										 |  |  | ;permit=0.0.0.0/0.0.0.0 | 
					
						
							| 
									
										
										
										
											2012-07-11 18:33:36 +00:00
										 |  |  | ;acl=example_named_acl | 
					
						
							| 
									
										
										
										
											2005-10-04 22:51:59 +00:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2009-02-06 20:12:33 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2012-03-02 16:19:53 +00:00
										 |  |  | ; With immediate=yes, an IAX2 phone or a phone on an IAXy acts as a hot-line | 
					
						
							| 
									
										
										
										
											2009-02-06 20:12:33 +00:00
										 |  |  | ; which goes immediately to the s extension when picked up.  Useful for | 
					
						
							|  |  |  | ; elevator phones, manual service, or other similar applications. | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ;[manual] | 
					
						
							|  |  |  | ;type=friend | 
					
						
							|  |  |  | ;host=dynamic | 
					
						
							|  |  |  | ;immediate=yes  ; go immediately to s extension when picked up | 
					
						
							|  |  |  | ;secret=moofoo	; when immediate=yes is specified, secret is required | 
					
						
							|  |  |  | ;context=number-please ; we start at the s extension in this context | 
					
						
							|  |  |  | ; |