[asterisk-bugs] [Asterisk 0017347]: Astersik generates responses with missing Via headers
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon May 17 11:05:26 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17347
======================================================================
Reported By: klaus3000
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 17347
Category: Channels/chan_sip/Interoperability
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Asterisk Version: 1.6.2.7
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-05-17 08:07 CDT
Last Modified: 2010-05-17 11:05 CDT
======================================================================
Summary: Astersik generates responses with missing Via
headers
Description:
If Asterisk detects a spiraled SIP call (outgoing INVITE is coming in
again), it will handle the forwarding internally (Local/...) and cancels
the outgoing call. Therefore Asterisk will send a CANCEL and due to
spiraling it will also receive a CANCEL and will respond with 487 to the
incoming spiraled INVITE.
This 487 response generated by Asterisk is malformed, it misses the second
Via header (which is present in the incoming INVITE, and in the 100 Trying
sent by Asterisk immediately after receiving the spiraled INVITE).
Problem happens with both, pedantic=yes and =no.
I tried to capture the call with "call show history" but for some reasons,
this call is not present in the history.
======================================================================
----------------------------------------------------------------------
(0121989) pabelanger (manager) - 2010-05-17 11:05
https://issues.asterisk.org/view.php?id=17347#c121989
----------------------------------------------------------------------
If you could follow the document below and attach your debug log to the
issue. Posting it in the comments sections just clutters the issue.
---
We require a complete debug log to help triage the issue.
This document will provide instructions on how to collect debugging logs
from an Asterisk machine for the purpose of helping bug marshals
troubleshoot an issue:
http://svn.digium.com/svn/asterisk/trun/doc/HOWTO_collect_debug_information.txt
Issue History
Date Modified Username Field Change
======================================================================
2010-05-17 11:05 pabelanger Note Added: 0121989
======================================================================
More information about the asterisk-bugs
mailing list