|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
Default TLS Port Assignment
|
Medium |
|
|
|
|
Default bind port for CHAN_PJSIP is: %s, CHAN_SIP is: %s
|
Medium |
|
|
|
|
Default context for incoming calls if not specified. FreePBX sets this to from-sip-external which is used in conjunction with the Allow Anonymous SIP calls. If you change this you will effect that behavior. It is recommended to leave this blank.
|
Medium |
|
|
|
|
Default length of incoming and outgoing registrations.
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
Domain the transport comes from
|
Medium |
|
|
|
|
Don't Require verification of server certificate (TLS ONLY).
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
Dynamic Host can not be blank
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
Enable server for incoming TLS (secure) connections.
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
Enables jitter buffer frame logging.
|
Medium |
|
|
|
|
Enables the use of a jitterbuffer on the receiving side of a SIP channel. An enabled jitterbuffer will be used only if the sending side can create and the receiving side can not accept jitter. The SIP channel can accept jitter, thus a jitterbuffer on the receive SIP side will be used only if it is forced and enabled. An example is if receiving from a jittery channel to voicemail, the jitter buffer will be used if enabled. However, it will not be used when sending to a SIP endpoint since they usually have their own jitter buffers. See jbforce to force its use always.
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
Endpoint Identifier Order
|
Medium |
|
|
|
|
Endpoint Identifier Order . The Default order is as follows:<ul><li>ip</li><li>username</li><li>anonymous</li><li>header</li><li>auth_username</li></ul><ul>Note : Changing this to get affected may require asterisk restart</ul>
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
External FQDN as seen on the WAN side of the router and updated dynamically, e.g. mydomain.example.com. (asterisk: externhost)
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
External IP can not be blank when NAT Mode is set to Static and no default IP address provided on the main page
|
Medium |
|
|
|
|
External Static IP or FQDN as seen on the WAN side of the router. (asterisk: externip)
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
Forces the use of a jitterbuffer on the receive side of a SIP channel. Normally the jitter buffer will not be used if receiving a jittery channel but sending it off to another channel such as another SIP channel to an endpoint, since there is typically a jitter buffer at the far end. This will force the use of the jitter buffer before sending the stream on. This is not typically desired as it adds additional latency into the stream.
|
Medium |
|
|
|
|
Frequency in seconds to check if MWI state has changed and inform peers.
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
Generate manager events when sip ua performs events (e.g. hold).
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
Hostname or address for the STUN server used when determining the external IP address and port an RTP session can be reached at. The port number is optional. If omitted the default value of 3478 will be used. This option is blank by default. (A list of STUN servers: http://wiki.freepbx.org/x/YQCUAg)
|
Medium |
|
|
|
|
Hostname or address for the TURN server to be used as a relay. The port number is optional. If omitted the default value of 3478 will be used. This option is blank by default.
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
IMPORTANT: Only use this functionality when your Asterisk server is behind a one-to-one NAT and you know what you're doing. If you do define anything here, you almost certainly will NOT want to specify 'stunaddr' or 'turnaddr' above.
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
|
Medium |
|
|
|
|
If blank, will use the default settings
|
Medium |
|
|
|