OutgoingIAXTrunk (IOA0)

Description

An outgoing IAX trunk allows you to send calls over a LAN, private or public IP network towards another asterisk system.

Release notes

Resource configuration interface

Resource configuration parameters

In order to place calls on an outgoing interface, use the action Goto.INTERFACE in the routing table or use the CallInterface action in a call flow. This action takes as argument an outgoing interface.

• Provider: free text field, allowing you to describe the peer system
• Remote host: IP address of the remote SOP or IAX gateway.
  • Indicate a SOP key if you want to use the IP address of a SOP within your SOP network.
  • Indicate 'dynamic' if you want to dynamically let the remote host dynamically register his IP address.
• User: username to be used when connecting to another IAX interface located on another SOP or gateway. If you interconnect 2 escaux's SOP, please use the resource ID of the interface (eg: IOA000XX). Do the same for the remote host: same resource ID on both systems.
• Secret: password to be used when connecting to another IAX interface located on another SOP or gateway
• Restriction Group: this is the Restriction Group in which you want to redirect incoming IAX calls .
  • Typically, use 'incoming' in order to redirect calls to incoming numbers
  • Typically, use 'NoRestrict' in order to redirect calls to another numbers (For example internal extensions).
• Remote host qualification:
  • Qualify remote host: enable to periodically try the remote host for a response. If there is no response, it will be marked as UNREACHABLE.
  • Qualify frequency when reachable: configure the frequency to try the host when it is reachable.
  • Qualify frequency when reachable: configure the frequency to try the host when it is unreachable.
  • Qualify response timeout: configure the interval within which the remote host has to respond. This value is only taken into account when the "Qualify remote host" parameter is explicitely set to "yes".
• First,Second and Third Codec To Use: prefered ordered list of codecs which must be used.
• Trunking Mode:
  • Default:Use the trunking mode configured in the asterisk module.
  • no: Do not use trunking mode
  • yes: Use trunking mode: IAX headers will be optimized in order to save bandwidth when there are several simultaneous call through an IAX trunk.
• Advanced trunking settings:
  • Trunk maximum size: The default value is 128000 bytes. The total size of payload which can be carried simultaneously over the trunk. This parameter need to be increase if a lots of calls is needed.
  • Trunk mtu: The default value is 1240 bytes. The size of the data on the network.
  • Trunk frequency: The frequency of sending data in the trunk. The possible value ranges from 10ms to 1000 ms. The default value is 20 ms. If the size of the buffer reaches the mtu size, the data will be sent.
• RSA authentication: Authenticate the call through a RSA public and private key. RSA authentication generates 2 keys:
  • 1 public key readable through the file manager. (http://[SOP-IP]/fileman/index.php?fm_dir=keys, choose the [RESOURCE ID].pub file) This public key must be indicated in the RSA accepted public key field of the IAX trunk of the remote IAX host in order to let this remote IAX trunk accept incoming calls from this trunk.
  • 1 private keys.
• Encryption: Encrypt calls or not. (Disabled if RSA authentication is selected.)
• RSA accepted public key: Public RSA key which is accepted for incoming calls.
• Registration: if yes, register the current IP address in the Registrar (see infra.)
• Registrar: IP address or SOP of the remote peer to register the current IP address.
• Require calltokens: Usefull for example to interconnect SOP based on Asterisk 1.2 with Communication server 2+. It will avoid new IAX2 system to ask a security call token that was not implemented on older system.

Restriction:

• RSA authentication is disabled if either encryption,registration or dynamic remote IAX host is selected.