IncomingIAXTrunk (IIA0)

Description

An IAX Incoming Interface defines an IAX interface which can receive calls from another IAX gateway. In order for a remote IAX system to send calls to an IAX Incoming Interface, it must be able to identify itself using the correct login and password

Release notes

Show release notes
Version 2.02 - General deployment
  • Improvement: Change default value of Untransferable to yes (M0)

Version 2.01 - General deployment
  • Added the possibility to disable the authentication of incoming calls.

Version 2.1.0 - Early deployment
  • Feature: Configurable use of calltokens. (M0)

Version 2.00 - General deployment
  • Potential update impact level 2 DONE: in the event this update contains a bug, it might have critical impact. Respect dependencies and retest your most important callflows and applicative integrations. asterisk-1.2x module version 1.2 or higher required

Version 1.00 - General deployment

Resource configuration interface

GUI unavailable.

Resource configuration parameters

  • Description: Free text field allowing you to describe the interface, for example 'From GW1' or 'From netPBX.1'
  • Gateway: IP address of the VoIP gateway to which you want to register. This option is only used when the register option is set to 'yes'. In most cases you will only use this option when your Escaux UCS is sitting behind a corporate firewall and you want to accept incoming VoIP calls from your VoIP provider
  • User: Username to be used by another Escaux UCS system trying to connect to this Escaux UCS system
  • Secret: Password to be used by another Escaux UCS system trying to connect to this Escaux UCS system
  • Incoming context: this is the Restriction Group in which you let the incoming IAX trunk terminate.
    • Typically, for a Escaux UCS server, use 'incoming' in order to accept only numbers indicated in 'External Number Mapping' interface.
    • Typically, for a Gateway server, use 'NoRestrict' in order to accept all calls and route them according to gateway routes.
  • First codec: during the establishment of an IAX trunk between Escaux UCS systems, the codec will be negociated. If your Escaux UCS systems are interconnected over a VPN network, use 'ilbc'. If your Escaux UCS systems are located on the same LAN network, use an uncompressed G.711 'ulaw' codec.
  • Second codec: Codec used in case the first codec is not accepted during codec negotiation
  • Third codec: Codec used in case the second codec is not accepted during codec negotiation
  • Register: If set to 'yes' the Escaux UCS will establish a persistent IAX trunk with its peer. This is useful for example if your Escaux UCS does not have a fixed IP address and would like to receive incoming calls from its peer.
  • Host: If blank, all hosts are permitted to connect. Otherwise only the defined host's IP address is permitted to connect
  • Untransferable: To maintain control of the IAX trunk at this Escaux UCS, set the value to 'yes' (preferred)
  • Authenticate Incoming Calls: If set to no, do not authenticate incoming calls. (Registration to remote server still needs an authentication)
Copyright © Escaux SA