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

Lumps bug in latest 1.10 #79

Closed
nikbyte opened this issue Sep 20, 2013 · 1 comment
Closed

Lumps bug in latest 1.10 #79

nikbyte opened this issue Sep 20, 2013 · 1 comment
Assignees
Milestone

Comments

@nikbyte
Copy link
Member

nikbyte commented Sep 20, 2013

If I have something like

remove_hf("To");
append_hf("To: <$du>\r\n", "From");

in my script, packets after opensips looks like

OPTIONS sip:8.8.8.8:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 8.8.8.8:5060;branch=z9hG4bK42e3.ce41a6c7.0
From: sip:test@test.com;tag=0a8fdab7
Call-ID: 2045e661-8ac5e035-e71d2
CSeq: 1 OPTIONS
Max-Forwards: 69
Content-Length: 0

\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00[|sip]

(not only OPTIONS, every requests or replies).

If I change
remove_hf("To");
append_hf("To: <$du>\r\n", "From");
to
remove_hf("To");
append_hf("To: <$du>\r\n");

everything works as expected.

@ghost ghost assigned bogdan-iancu Sep 20, 2013
bogdan-iancu added a commit that referenced this issue Sep 20, 2013
…ial for deciding which lumps must be skipped (as overlapping with delete parts of the message)

  Credits go to Nick Altmann for reporting and helping with troubleshooting.
  Closes issue #79
bogdan-iancu added a commit that referenced this issue Sep 20, 2013
…ial for deciding which lumps must be skipped (as overlapping with delete parts of the message)

  Credits go to Nick Altmann for reporting and helping with troubleshooting.
  Closes issue #79
@bogdan-iancu
Copy link
Member

Nick, many thanks for reporting this and for the help in reproducing the problem. The fix is on GIT trunk and 1.10 .

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

2 participants