Printer FriendlyEmail Article Link

Abacus: SIP Supplementary Services (MLPP and RFC 5359) be used with a single physical port on ICG3 or Abacus50Eth configured for both Originate and Terminate Channels?


Yes, SIP Supplementary Services scripts can be configured with both the originate and terminate channels on the same physical interface on Abacus50Eth and ICG3, but only with a proxy server configured in SUT settings to prevent SIP Signaling from looping back internally on the ICG3 or Abacus50Eth.

SIP supplementary services are intended to provide you with complex calling scenarios per RFC 5359 (Session Initiation Protocol Service Examples) and MLPP (Multilevel Precedence and Preemption).  Default scripts are included for approximately 20 scenarios listed by function and RFC section, and users may configure new scripts for supplementary services using the predefined action templates.

SIP Supplementary Services scripts can be accessed and configured using the Script Management window / Supplementary tab, accessible via the CALL SEQUENCE Menu on the Abacus GUI. 

 Abacus SIP Supplementary Services / Script Management Window

SIP Supplementary Services scripts are added the same as standard A calls B (SIP) scripts, by selecting a script in the PARTITION and TIMING window / Scripts tab.  The SCRIPT Management window can be opened using the EDIT button next to the selected script.

Partition and Timing Window / Scripts Tab

By default, all channels assigned to a SIP Supplementary Services script are set as "Originate" channels and cannot be changed.  The number of channels assigned to a supplementary services script must be divisible the the number of channels actually used by the script.  For example, a call forwarding script uses 3 channels, A, B, and C, therefore the number of channels assigned to the set must be divisible by 3. By default, the links are set to "Own" which takes the phone numbers for all channels used from the OWN phone book.

Abacus Partition and Timing window / Association Tab

When all channels used in a SIP Supplementary Services test are configured on the same physical interface (using the ICG Tab of the PROTOCOL SELECTION window), it is necessary to configure a SIP Proxy to ensure SIP signaling is not looped back internally on the ICG3 or Abacus50Eth.

Abacus Protocol Selection Window / ICG Tab

To configure a SIP Proxy Server globally, the SUT Settings window can be accessed from the CONFIGURE Menu by selecting "SUT Settings" or by clicking the SUT button on the navigation bar.

Abacus accessing SUT Settings Window

SUT Settings may be configured per card (ICG3 or Abacus50Eth) by clicking the EDIT button next to SUT Config profile on the PROTOCOL SELECTION window / SUT Tab.

Abacus SUT Settings per Card / Protocol Selection / SUT

On the SYSTEM UNDER TEST SETTINGS window / NETWORK SETTINGS / PROXY, enable "Use Proxy Server" and then configure the NAME and IP ADDRESS of the SIP Proxy server through which SIP Signaling will be directed.

Abacus SUT Settings / Proxy Configuration

Once a test has started, you can verify that signaling is not looping back internally on the Abacus by configuring the Call Tracer to monitor multiple channels involved in the same call script.  The Call Tracer can be accessed from the MONITOR Menu by selecting CALL TRACER. 

Abacus Call Tracer / SIP Supplementary Services call signaling

If SIP Signaling is looping back internally for SIP Supplementary Services, no call signaling will be visible on the Call Tracer.

Product : Abacus,Voice,6.20,6.11 and below,SIP