WoomeraTrunk (WOA1)


This interface enable routing through the ISDN protocol using a PRI or BRI over the Woomera protocol

Release notes

Version 1.33.1 - Early deployment
  • Bugfix: Configuration generation could fail
  • Dependency:
    • Sangoma Card Support 1.2.0

Version 1.33 - General deployment
  • Feature: Possibility to enable debugging on the interfaces
  • Feature: Possibility to configure multiple advanced parameters
  • Dependency:
    • Sangoma Card Support 1.2.0

Version 1.32 - General deployment
  • Feature: Enabled overlap receiving configuration options (M0003884)
  • Dependency:
    • Sangoma Card Support 1.2.0

Version 1.31 - General deployment
  • Bugfix: Following configuration options Connection Type, Service Type, Local Number (MSN), Number of incoming digits, Prefixes, are taken in account while generating configuration files, in previous versions of the resource default values were used.
  • Dependency:
    • Sangoma Card Support 1.2.0

Version 1.30 - General deployment
  • Improvement: Allow more than 4 spans
  • Dependency:
    • Sangoma Card Support 1.2.0

Version 1.21 - General deployment
  • Fix configuration of first span
  • Dependency:
    • Sangoma Card Support 1.1.2

Version 1.20 - Deprecated
  • Improvement: Do not use by default woomera profile in order to fix a sangoma bug
  • Deprecated: Significant improvements have been done in a higher version
  • Dependency:
    • Sangoma Support module 1.1.2

Version 1.10 - General deployment
  • Remove the 'multiselect' interface by a text field, which must be filled in by the options indicated in the documentation. (1 field at a time supported)

Version 1.00 - General deployment
  • Initial version

Resource configuration interface

GUI unavailable.

Resource configuration parameters

This resource allows the configuration of a BRI port on a Woomera compatible interface card such as the Sangoma card.

  • Country: Set this to your local country (Recommended: "Europe" in order to set it to EuroISDN)
  • Dialplan: Certain ISDN switches require the "type of number" network specific facility IE to be set.
  • Numbering Plan: Certain ISDN switches require the "number plan" network specific facility IE to be set.
  • Signaling: Select TE if your BRI is connected a standard ISDN line of your ISDN service provider (operator). Select NT if the BRI should behave like an operator's ISDN line (for example when you interconnect your system with another PBX system)
  • Group: Set it to the BRI id you want to configure
  • Span: Set it to the BRI id you want to configure. The group and the span should be the same.
  • Context: Optional context in which an incoming call on the PRI must enter. (restart asterisk after changing this value!)
    • Set to 'Incoming' (default value if left empty) in order to route incoming calls to the External Number Mapping.
    • Set to 'NoRestrict' if you want to redirect the calls to any configured route as indicated in the route plan.
  • Connection Type: This should match the parameter configured by your operator. By default this would be "point-to-point".
  • Service Type: ISDN media. By default this would be "voice".
  • Local Number (MSN): Call filtering number. On incoming calls, any number that does not match the local_number string will not be answered. This feature is used for Multiple Subscriber Numbering. An incoming call will be answered if the shortest string between the received called number and the programmed called number matches.
  • Number of incoming digits: Minimum number of digits for called number on an incoming call. Incoming calls with called number less than this value will be rejected with cause: Invalid number format.
  • Prefixes: Prefix the incoming Caller ID Number based on the "type of number" network specific facility IE.
  • Advanced options:
    • Incoming call behavior:
      • SEND_CALL_PROC_RQ (default = enabled for NT mode, disabled for TE mode). A call proceeding message will be sent before the call alert message is sent. The call proceeding message is optional, but some switches require it.
      • TRUNCATE_NB (default = disabled). When using overlap receive mode (usually used then ISDN BRI phones are connected to a bri_nt port), the called number will be truncated to the number of digits specified in num_digits.
      • TRANSPARENT_OVERLAP_RCV (default = disabled). Only used in overlap receiving mode. On incoming calls, the call is forwarded to the "s" extension in Asterisk and incoming out of band digits are forwarded as DTMF digits to Asterisk.
      • CALLED_NB_ABSENT_MATCH (default = disabled). Incoming calls without a called numbed number specified will not be rejected with "Invalid Number", but instead get forwarded to the "s" extension in Asterisk".
    • Outgoing call behavior:
      • USER_SENDING COMPLETE (default = enabled). The sending-complete information element is send when requesting an outgoing call.
      • SEND_CONN_CO_ON_PROGRESS (default = disabled). The call will be answered when after a call progress message is received. Otherwise, the call is answered when a Connect message is received.
      • SEND_DIGIT_CO_ON_PROGRESS (default = disabled). When this is enabled, a call progress message will be sent when a call proceeding message is received. Otherwise, BRI stack will wait for a Setup ACK message.
      • REJECT_IF_NO_FREE_CHAN (default = disabled). Outgoing calls will be rejected locally if no b-channels are available. Otherwise, outgoing calls will still be requested, and the remote side is expected to reject the call.
      • STORE_CHAN_ID_IN_SETUP (default = disabled). The channel-id is always specified in an outgoing call setup message, even if it is not required (i.e optional only).
      • ACCEPT_IA5_NB (default = disabled). If enabled, outgoing calls with calling number, and called number containing IA5 characters will not be rejected. Otherwise, only extended digits are allowed (0-9, *, #)
    • General call behavior:
      • CHAN_ALLOC_LOWEST. allocates the b-channels by starting with the lowest available B-channel.
      • CHAN_ALLOC_HIGHEST. allocates the b-channels by starting with the highest available B-channel.

ALERT! If you want to use multiple of these parameters, you need to enter them separated by semicolons (e.g. TRANSPARENT_OVERLAP_RCV;SEND_CALL_PROC_RQ).

  • Receiving Mode
    • 'Mode' Select whether to use block receiving or overlap receiving
    • 'Answer' Answer the call before waiting for following digits in case of overlap receiving. This is ignored in block receiving.
    • 'Wait (seconds)' Number of seconds between each digit in case of overlap receiving. This is ignored in block receiving.
  • Debug mode
    • Select whether to enable debugging or not.

Remark: In case, one of these parameter change, you must reboot the SOP.
Copyright © Escaux SA