Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trailing chars in SIP traffic on SLL in 1.47 #10

Open
jpr5 opened this issue Sep 11, 2017 · 0 comments
Open

Trailing chars in SIP traffic on SLL in 1.47 #10

jpr5 opened this issue Sep 11, 2017 · 0 comments
Assignees
Milestone

Comments

@jpr5
Copy link
Owner

jpr5 commented Sep 11, 2017

From dragonfly.net@gmail.com:

I test new version and now better filter packets, but trash in sip udp packets remained when -d any.
Example:
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 213.170.84.105:5060;branch=z9hG4bK6476719.
From: sip:ping@ringme.ru;tag=uloc-591da6eb-7745-005a02-3b80aa86-565d0154.
To: sip:0004*207@192.168.10.97:5060;transport=udp;user=phone;tag=2e4daf14d0b51a35.
Call-ID: 61b02552-5429af26-caac511@213.170.84.105.
CSeq: 1 OPTIONS.
User-Agent: Grandstream GXP1200 1.2.3.5.
Contact: sip:0004*207@192.168.10.97:5060;transport=udp;user=phone.
Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE.
Supported: replaces, timer.
Content-Length: 0.
.
B6.
Contact: <si

(look to end with B6 Contact ...) - may be any readable trash. If i set as -d eno1 - all packets are clean.

Run as: bin/ngrep -d any -q -W byline '0004*2' udp port 5080 or udp port 5060 or udp port 5068

I think, trouble in SLL, need some backport from tcpdump or option for ip sockets, when only ip can be catched but without SLL.

@jpr5 jpr5 self-assigned this Sep 11, 2017
@jpr5 jpr5 added this to the 1.47.1 milestone Sep 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant