Skip to main content
https://img.shields.io/github/actions/workflow/status/amateja/acmepcap/python-test.yml https://img.shields.io/coveralls/amateja/acmepcap.svg https://img.shields.io/pypi/v/acmepcap https://img.shields.io/pypi/format/acmepcap https://img.shields.io/pypi/pyversions/acmepcap https://img.shields.io/pypi/status/acmepcap https://img.shields.io/pypi/l/acmepcap

acmepcap

Acme Packet sipmsg.log to packet capture converter.

This project is intended for users and administrators of Oracle (formerly Acme Packet) Communications Session Border Controller (SBC) software. It converts an Acme Packet sipmsg.log file into a packet capture (PCAP) file. Originally inspired by apktlog2pcap.

installation

pip install acmepcap

usage

Command-line help:

acmepcap --help

usage: acmepcap [-h] -f FILE [-c] -o OUTPUT [-t TIMEZONE] [--summary]

options:

-h, --help            show this help message and exit
-f FILE, --file FILE  sipmsg.log file
-c, --compress        compress the output packet capture file
-o OUTPUT, --output OUTPUT
                      output packet capture file
-t TIMEZONE, --timezone TIMEZONE
                      SBC timezone as a tz database identifier (default: UTC)
--summary             print conversion summary to stderr

Minimal set of parameters (UTC assumed):

acmepcap -f sipmsg.log -o my.pcap

All parameters in use:

acmepcap -f sipmsg.log -o my.pcap.gz -c -t Europe/Warsaw --summary

Sensitive data warning

sipmsg.log files and generated PCAP files may expose phone numbers, SIP URIs, IP addresses, authentication-related values, call metadata, and network topology. They may also contain personal, customer, or regulated data. Treat both input logs and converted captures as confidential support artifacts.

Questions & Answers

  1. Why convert sipmsg.log to a packet capture format?

    Although SIP was designed to be human-readable, working through a file with hundreds of SIP messages often belonging to different sessions is not easy. Converting to PCAP enables powerful filtering and analysis with standard tools. Additionally, when a call is encrypted, capturing traffic on the wire may not help, while sipmsg.log still provides the signaling you can analyze.

  2. How can I obtain the sipmsg.log file?

    The sipmsg.log file is created on Acme Packet software when one of the following is enabled:

    1. Debug mode: notify sipd debug (disable with notify sipd nodebug)

    2. Advanced Logging (see the Oracle Communications SBC Maintenance and Troubleshooting Guide)

    3. Explicit SIP logging: notify sipd siplog (stop with notify sipd nosiplog)

    You can download it directly from the device or as part of a log bundle created with package-logfiles or package-crashfiles.

  3. What should I set for the timezone parameter? Use the tz database identifier that matches the SBC timezone configured via timezone-set. You can verify the current setting with show clock (note: it may not be an exact match). If omitted or incorrect, nothing bad will happen, but PCAP timestamps may be inaccurate.

Assumptions

  1. self-sufficient

    Aim to be as independent as possible and require only standard Python. While there are excellent libraries like scapy, this tool strives to work with pure Python.

  2. install or download

    Users can either install a release or download the single-file source and run it directly.

  3. wide support

    Support as many environments as practical, without targeting exotic or unsupported versions.

  4. simple

    Provide a command-line interface only. Implement only the essential protocol features needed for this conversion; do not attempt to implement a full protocol stack.

Metadata

Release files for acmepcap 0.4.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for acmepcap 0.4.0
File Interpreter ABI Platform Actions
acmepcap-0.4.0-py3-none-any.whl Python 3 none any Details for acmepcap-0.4.0-py3-none-any.whl

Release files / acmepcap-0.4.0-py3-none-any.whl

Download URL acmepcap-0.4.0-py3-none-any.whl
Size 13.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
427736af4e04a0ba0f297d2447d81ea1e5bc20ee274d48e183504419b741fe6f
BLAKE2b-256 checksum
How to use checksums
a41e88481b3b4cad7bbb253a217821b0ea087be6b895125e7dfa79a1860cf12a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.12.3

Security for acmepcap 0.4.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page