Page 381 - Asterisk™: The Future of Telephony
P. 381

externip=216.239.39.104
               externrefresh
                   If externhost is used, externrefresh configures how long, in seconds, should pass
                   between DNS lookups:
                       externrefresh=30
               g726nonstandard
                   This parameter can be set when dealing with peers that incorrectly use the wrong
                   encoding for the G.726 codec. This setting tells Asterisk to use AAL2 packing order
                   instead of RFC3551 packing order if the peer negotiates G726-32 audio. Ordina-
                   rily, that would be contrary to the RFC3551 specification, as the peer should be
                   negotiating AAL2-G726-32 instead. You may need to set this option if you’re using
                   a Sipura or Grandstream device:

                       g726nonstandard=yes
               ignoreregexpire (global)
                   If ignoreregexpire is set to yes, Asterisk could do one of two things, for:
                   Non-realtime peers
                       When their registration expires, the information will not be removed from
                       memory or the Asterisk database. If you attempt to place a call to the peer, the
                       existing information will be used in spite of it having expired.
                   Realtime peers
                       When the peer is retrieved from realtime storage, the registration information
                       will be used regardless of whether it has expired or not; if it expires while the
                       realtime peer is still in memory (due to caching or other reasons), the infor-
                       mation will not be removed from realtime storage:
                          ignoreregexpire=yes|no
               jbenable
                   Enables the use of an RTP jitter buffer on the receiving side of a SIP channel. De-
                   faults to no. An enabled jitter buffer will be used only if the sending side can create
                   and the receiving side cannot accept jitter. The SIP channel can accept jitter; thus
                   a jitter buffer on the receiving side will be used only if it is forced and enabled:
                       jbenable=yes|no
               jbforce
                   Forces the use of the RTP jitter buffer on the receiving side of a SIP channel. Defaults
                   to no:
                       jbforce=yes|no

               jbimpl
                   This  setting  is  used  to  specify  which  jitter  buffer  implementation  to  use,  the
                   fixed jitter buffer or the adaptive jitter buffer. If the fixed jitter buffer is used, it
                   will always be the size defined by jbmaxsize. If the adaptive jitter buffer is specified,


                                                                                 SIP | 353
   376   377   378   379   380   381   382   383   384   385   386