[asterisk-bugs] [Asterisk 0011536]: With "pedantic=yes" Asterisk shouldn't match To tag if the dialog is not established
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Aug 18 16:16:04 CDT 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=11536
======================================================================
Reported By: ibc
Assigned To: putnopvut
======================================================================
Project: Asterisk
Issue ID: 11536
Category: Channels/chan_sip/Interoperability
Reproducibility: always
Severity: minor
Priority: normal
Status: ready for testing
Asterisk Version: 1.4.15
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 2007-12-13 06:58 CST
Last Modified: 2008-08-18 16:16 CDT
======================================================================
Summary: With "pedantic=yes" Asterisk shouldn't match To tag
if the dialog is not established
Description:
Asterisk in SIP pedantic mode.
- Asterisk calls to an external SIP user in OpenSer proxy.
- After "Ringing" Asterisk sends CANCEL.
- OpenSer replies with "200 canceling" but Asterisk doesn't recognize it
so resends the CANCEL.
I've a theory of why it fails:
The "180 Ringing" contains a "To" tag:
To: <sip:ibc at aliax.net>;tag=veuje
When Asterisk sends CANCEL OpenSer replies with:
SIP/2.0 200 canceling
To: <sip:ibc at aliax.net>;tag=373b8885156114ecb2c4bd665f9faf0b-f9aa
So Asterisk asumes wrong To tag (because it's different as the received
one) and discards it.
Of course, OpenSer proxy behaviour is correct: there could be many "180
Ringing" each one with different To tag in case of forking scenario, so the
To tag in the "200 canceling" from OpenSer *shouldn't* match any previous
"To" tag received in any provisional response.
About it I opened a thread in Sip-implementators mailist in which this
issue is explained:
https://lists.cs.columbia.edu/pipermail/sip-implementors/2007-October/017668.html
IMHO the solution would be:
Asterisk shouldn't try to match a To tag if the dialog is not yet
established. And Asterisk should assume that it can receive multiples To
tag in provisional responses in case of forking scenarios (there are more
SIP in the world than just single phones registered in Asterisk XD).
======================================================================
----------------------------------------------------------------------
(0091524) putnopvut (administrator) - 2008-08-18 16:16
http://bugs.digium.com/view.php?id=11536#c91524
----------------------------------------------------------------------
It turns out that I misinterpreted section 15.1.1 of RFC 3261 with regards
to when a UAC should consider a dialog to be dissolved. The section states
that media sessions should be considered closed as soon as a UAC sends a
BYE request. I also took this to mean that the dialog between the two UAs
should also be closed. This, however, is incorrect, so I have modified the
patch to clear the flag as a UAC when a 200 OK is received in response to a
BYE. This patch has been uploaded as 11536v2.patch and is ready for
testing.
Issue History
Date Modified Username Field Change
======================================================================
2008-08-18 16:16 putnopvut Note Added: 0091524
======================================================================
More information about the asterisk-bugs
mailing list