Configuring “packet-trace” SIP on the Acme Packet SBC19 Jun 2012 #acme packet #sbc #sip
packet-trace ACLI command allows the Acme Packet SBC (Session Director) to capture SIP signaling communication between two endpoints and send the capture to external server such as Wireshark.The SBC uses the network interfaces (ie. media interfaces) to send the capture.
The first step is to configure a capture receiver. This tells the SBC what interface is used for the mirrored packets and the target IP of the
Wireshark server. The network-interface is the SBC’s
capture-receiver state enabled ip-address 10.12.135.150 network-interface m00:0
The next step is to identify what
ports the SBC should listen to in order to send the packets to Wireshark. If no ports are identified then the SBC listens on all ports.
PHOEN?IX# packet-trace start Access:0 220.127.116.11 5060 5060 Trace start for 18.104.22.168
Even though it is not required to specify the local and remote TCP/UDP ports it’s always a good idea to be as specific as possible when defining captures so only the required data is captured. At this point any calls coming into the SBC that involve the
IP 22.214.171.124 on
5060 are going to trigger the capture and packets will be sent to Wireshark. Sixteen concurrent traces can be running at once.
One thing to note is the capture is sent to Wireshark using RFC 2003 (IP to IP encapsulation) as opposed to relaying SIP on port 5060. This means Wireshark needs to be configured to listen for RFC 2003 packets and then it will decode them. Use the ip.src filter to display only the encapsulated SIP packets