The Adtran community holiday season is starting next week! The holiday period will span from December 21, 2024 to January 6, 2025. During this time, responses to feedback form submissions may be delayed. If you are encountering product issues, you can reach out to Adtran support at any time.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
ss_daveh
New Contributor III

Exporting SIP signalling to text

Jump to solution

I found this helpful post: https://supportforums.adtran.com/message/2248 and was able to set a packet dump in hex format and import to Wireshark PCAP. However, I am having difficulty getting SIP signalling to be exported in hex format and importing to a PCAP in a format that actually shows sip messaging. Does anybody have experience setting this up?

0 Kudos
1 Solution

Accepted Solutions
Anonymous
Not applicable

Re: Exporting SIP signalling to text

Jump to solution

Hi ss_daveh:

I like to create an ACL to define what I want to debug/dump in the console.  Example:

ip access-list extended sip-capture

  remark sip-capture

  permit udp any any eq 5060

Start logging to a text file in your terminal application, then use the following command at the enable prompt to begin the packet dump:

debug ip packet sip-capture dump

When finished:

undebug all (or just u a)

Stop your text logging and then follow the instructions in the post you mentioned to convert the text log to a PCAP file.

Sometimes it's important to collect data over a long period, but SSH/telnet sessions typically timeout after a few minutes.  I found this article helpful to setup persistent debugging over a longer period: 

Good luck,

Chris

View solution in original post

0 Kudos
2 Replies
Anonymous
Not applicable

Re: Exporting SIP signalling to text

Jump to solution

Hi ss_daveh:

I like to create an ACL to define what I want to debug/dump in the console.  Example:

ip access-list extended sip-capture

  remark sip-capture

  permit udp any any eq 5060

Start logging to a text file in your terminal application, then use the following command at the enable prompt to begin the packet dump:

debug ip packet sip-capture dump

When finished:

undebug all (or just u a)

Stop your text logging and then follow the instructions in the post you mentioned to convert the text log to a PCAP file.

Sometimes it's important to collect data over a long period, but SSH/telnet sessions typically timeout after a few minutes.  I found this article helpful to setup persistent debugging over a longer period: 

Good luck,

Chris

0 Kudos
ss_daveh
New Contributor III

Re: Exporting SIP signalling to text

Jump to solution

Thanks cj!

I had edited my access list to not capture the correct info. Thanks for the quick and helpful advice.