Make use of Wireshark, tcpdump or a similar tool to capture the traffic that SIPVicious PRO is producing so that we can reproduce the issue. Make use of a network capture filter such as
host example.org where
example.org is your target machine.
If using SIP over TLS, it is helpful to be able to decrypt the TLS traffic when sending packet capture files to us for analysis. Make use of the
tls-key-log and send us the output file together with your packet capture files.
The debug flag should be enabled to produce more detailed output. The following
.sipvicious.toml configuration (stored in the current working directory) would enable debug logs and TLS key logs and log the output to a file:
logfile = "sipvicious6.log" debug.logging = true sip.tls-key-log = "sipvicious-tls-key.log"
The same effect can be achieved by making use of the following flags:
--logfile sipvicious6.log --debug --tls-key-log sipvicious-tls-key.log.
If the issue is with a custom SIP template, please make use of the
sip utils template test tool for debugging purposes.
Please make use of our support form.