MeshSipTrunk (SOA2)

Description

This type of interface allows the system to easily create a mesh network by creating a sip interface on each sop of a network which point to a specific sop destination.

Release notes

Show release notes
Version 1.16.0 - Early deployment
  • Feature: Distributed device state over SIP (PC-2600)

Version 1.15.0 - Early deployment
  • Feature: Meshed route will be automatically created (M15803)

Version 1.14.0 - General deployment
  • Improvement: Added extra video codecs (M9035)

Version 1.13.1 - General deployment
  • Bugfix: The trunk was not propagating the 180 SIP Ringing transparently

Version 1.13.0 - General deployment
  • Bugfix: Support for G729

Version 1.12.1 - General deployment
  • Bugfix: T.38 gateway was always started on the SIP trunk channel causing failing reinvites.

Version 1.12.0 - General deployment
  • Feature: Support for T.38. (M0005496)

Version 1.11 - General deployment
  • Improvement: Compatibility with the Communication Server module

Version 1.10 - General deployment
  • Improvement: Ensure proper SIP interface identification
  • Improvement: If no codec specified, use any of the supported codec
  • Feature: Configurable Restriction Group
  • Feature: use Remote-Party-ID SIP header to transmit Caller ID and Caller Privacy Policy
  • Feature: added possibility to specify qualify-settings on trunk level

Version 1.03 - General deployment
  • Improvement: sip qualify always enabled

Version 1.02 - General deployment
  • Feature: Use remote party id to carry caller id, caller presentation and call screening information
  • Bug fix: SIP peer not identified properly when several interface with same source ip are created
  • Improvement: if no codec are indicated use default ones

Version 1.01 - General deployment
  • Bug fix: Ringing indication not forwarded by the meshed SIP trunk (M0002701)

Version 1.00 - General deployment

Version 0.0 - Deprecated

Resource configuration interface

GUI unavailable.

Description

This interface enables to interconnect SOPs of a same cluster in SIP.

Parameters

  • Target SOP: SOP that will be reachable from any other SOP of the cluster
  • DTMF mode: Format of be used to exchange DTMF
  • Codecs: Codecs to allow when using this interface in order of preference
  • SIP can reinvite: Set this option to 'yes'
  • Use Remote Party ID: Transport Caller Id and Caller Privacy Policy in a dedicated SIP header. Set 'Remote Party ID' to yes if several SIP interfaces are configured on the same SOP or if the Caller Privacy Policy need to be carried from one SOP to another.
  • Restriction Group: Restriction Group which will be applied to any incoming call from Target SOP
Copyright © Escaux SA