[OT] SIP UDP fragmentation and SIP capture

Hello,

With Stir-Shaken for instance, SIP INVITE message size may exceed the limit that requires fragmentation.

While capturing SIP traffic with tshark or tcpdump, it seemed to me I couldn’t at the same time use BPF filter and capture full INVITE message including Stir-Shaken Date or Identity headers. I suspect it relates to SIP fragmentation.

My questions are:

  1. Where I can read about handling of SIP UDP fragmentation by Asterisk’s PJSIP channel ?
  2. Do you have any improvement suggestion over the following tshark command (meant to capture in the background, all SIP traffic but only SIP traffic (on a multi-homed using SIP on udp:0.0.0.0:5060) during 60 seconds.
tshark -i eth0 -f "udp port 5060" -w /tmp/foo.pcap -a duration:60 -Q &

Best regards

Asterisk doesn’t handle fragmentation. That is done by the operating system.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.