Maintenance and Troubleshooting Commands for SPLs

This section provides information about how to troubleshoot and collect information about your SPL.

show SPL

The ACLI show spl command displays:

The version of the SPL engine.
The filenames and version of the SPLs currently loaded on the Oracle® Enterprise Session Border Controller (E-SBC).
The signature state of each SPL
The system tasks for which each loaded SPL interacts, enclosed in brackets.

ACMEPACKET# show spl
SPL Version: C2.0.0
[sipd] File: LyncEmergencyCall.1.0.spl version: 1.0 signature: signed and valid
ACMEPACKET# show spl sipd
SPL Version: C2.0.0
[sipd] File: LyncEmergencyCall.1.0.spl version: 1.0 signature: signed and valid

SPL Signature State

All SPLs must be signed by Acme Packet for authenticity.

show running-config spl-config

The ACLI show running-config spl-config displays SPL specific configuration information on the system.

ACMEPACKET# show running-config spl-config
spl-config
        spl-options
        plugins
                name                           LyncEmergencyCall.1.0.spl
        last-modified-by               admin@216.41.24.2
        last-modified-date             2012-10-12 15:31:05

show directory code spl

The ACLI show /code/spl command displays the SPLs stored in the /code/spl directory.

ACMEPACKET# show directory /code/spl
Listing Directory /code/spl:
drwxrwxrwx  1 0       0                 4096 Aug 13 10:07 ./
drwxrwxrwx  1 0       0                 4096 Aug 19 22:25 ../
-rwxrwxrwx  1 0       0                 3163 Aug 13 10:07 LyncEmergencyCall.1.0.spl

show spl-options

The ACLI show spl-options command displays SPL-specific options registered by an SPL.

ACMEPACKET# show spl-options
   1. return_183_initial_invite: Returns a 183 provisional response when a
emergency call is placed through Lync [LyncEmergencyCall.1.0.spl,config]

SPL File Deletion

You must delete SPL files from /code/spl by way of SFTP. There is no means to delete SPL files by way of the ACLI.

SPL Log Types

SPL log messages can often be found in the log file for the system task to which the SPL applies when that task is set to DEBUG level. You can find the output specific to SPL by the identifying prefix [SPL].

Aug 30 15:06:07.454 [SPC] Executing SPL callback from file: SipHeaderExtensionMetadata.1.2.spl
Aug 30 15:06:07.454 [SPL] Checking for LRE-Identifier to match triggered session-recording-server
Aug 30 15:06:07.454 [SPC] Creating table of name 'AcmeSipServerTransDataTable' with key [0x34522878]
Aug 30 15:06:07.454 [SPC] Creating new temporary session table of key [_SESSION_0x34522878]
Aug 30 15:06:07.454 [SPL] SIP Interface ingressSIP has option
Aug 30 15:06:07.454 [SPL] Storing data from message to insert into metadata