NOT FOUND answer on OPTIONS request

Bug #920020 reported by Marc Remijn
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
asterisk (Ubuntu)
Fix Released
Medium
Paul Belanger
Oneiric
Fix Released
Low
Paul Belanger
Precise
Fix Released
Medium
Paul Belanger

Bug Description

SIP OPTIONS req resulted in:

<--- SIP read from UDP:82.101.62.99:5060 --->
OPTIONS sip:80.101.134.148:61304 SIP/2.0
Via: SIP/2.0/UDP 82.101.63.5:5060;branch=0
From: sip:<email address hidden>;tag=0
To: sip:80.101.134.148:61304
Call-ID: d34db33f-1325692477-3368860901@folays
CSeq: 1 OPTIONS
Content-Length: 0

<------------->
--- (7 headers 0 lines) ---
Looking for in default (domain 80.101.134.148:61304)

<--- Transmitting (no NAT) to 82.101.62.99:5060 --->
SIP/2.0 404 NOT FOUND
Via: SIP/2.0/UDP 82.101.63.5:5060;branch=0;received=82.101.62.99
From: sip:<email address hidden>;tag=0

Can be fixed by applying issue18348_v1.8.patch.

https://issues.asterisk.org/jira/browse/18348

Can this be included in new version of ubuntu package

Update: Paul Belanger

[Impact]
Will fix SIP users that require OPTIONS messaged. Usually for NATs.

[Development Fix]
This bug was fixed in asterisk 1.8.5.0

[Stable Fix]
Already fixed upstream and backported.

[Test Case]
You will need to make sure you have an ITSP that uses SIP OPTIONS, usually to check it the connect is still alive. Once you have properly setup a SIP connect, for example you have create a sip peer called blah:

*CLi> sip set debug on peer blah

and confirm asterisk response with 200 OK to the OPTIONS message

[Regression Potential]
Minimal, a check of the asterisk issue tracker and code has not resulted in any know regressions.

Dave Walker (davewalker)
Changed in asterisk (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
tags: added: bitesize
description: updated
Revision history for this message
Paul Belanger (pabelanger) wrote :

Debdiff for preceise

Revision history for this message
Paul Belanger (pabelanger) wrote :

debdiff for oneiric-proposed

Changed in asterisk (Ubuntu Oneiric):
status: New → Confirmed
Changed in asterisk (Ubuntu Precise):
status: Triaged → Confirmed
Changed in asterisk (Ubuntu Oneiric):
assignee: nobody → Paul Belanger (pabelanger)
Changed in asterisk (Ubuntu Precise):
assignee: nobody → Paul Belanger (pabelanger)
Revision history for this message
Julian Taylor (jtaylor) wrote :

for precise it might be better to instead sync the version from debian which has the fix. It looks like its a bugfix only update so it could be synced without an exception.

for oneiric can the bug description please be updated for an SRU:
see https://wiki.ubuntu.com/StableReleaseUpdates

Revision history for this message
Paul Belanger (pabelanger) wrote :

No, I actually disagree with the debian sync of asterisk at this point of time. Between 1.8.4.4 and 1.8.9.0 / 1.8.10.0 there have been too many regressions. And this late in the game it would not want to go through the process of retesting asterisk to make sure we didn't break something new.

description: updated
Revision history for this message
Julian Taylor (jtaylor) wrote :

can you give some details on the regressions. Where they fixed in .10 or still open?
there have been several CVE's fixed in those versions which should then be backported.
e.g. CVE-2011-4598, CVE-2011-4063

also precise is supported 5 years, so getting a newer version will ease backporting future fixes.

Revision history for this message
Paul Belanger (pabelanger) wrote :

Right, they are still open. 1.8.4.4 is a nice release, it has it's issues however for each release moving forward something new / different breaks. Precise being a 5 year support is not much of an issue at this point, regardless of the regressions found we would need to backport them eventually.

Regarding the CVE's you have referenced, yes. They would need to be backported into other releases. I plan to open up a security issue for them shortly.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package asterisk - 1:1.8.4.4~dfsg-2ubuntu4

---------------
asterisk (1:1.8.4.4~dfsg-2ubuntu4) precise; urgency=low

  * debian/patches/backport-r312866.diff
  - Responding to OPTIONS packet with 404 because Asterisk not looking for
     "s" extension (LP: #920020)
 -- Paul Belanger <email address hidden> Sat, 10 Mar 2012 21:38:29 +0100

Changed in asterisk (Ubuntu Precise):
status: Confirmed → Fix Released
Revision history for this message
Julian Taylor (jtaylor) wrote :

I have also uploaded the fix to oneiric-proposed please test it when it has been accepted.

note that the version number for SRU in this case is ubuntu1.1
see https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging for general stable version number advice

thanks for the patches.

Changed in asterisk (Ubuntu Oneiric):
status: Confirmed → Fix Committed
importance: Undecided → Low
Revision history for this message
Jonathan Riddell (jr) wrote :

In oneiric-proposed, awaiting approval from ubuntu-sru

Revision history for this message
Martin Pitt (pitti) wrote : Please test proposed package

Hello Marc, or anyone else affected,

Accepted asterisk into oneiric-proposed. The package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

tags: added: verification-needed
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote : Verification still needed

The fix for the this bug has been awaiting testing feedback in the -proposed repository for oneiric for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now the package will be removed from the -proposed repository.

Revision history for this message
Paul Belanger (pabelanger) wrote :

I was able to confirm this fix a few weeks ago, however I never go around to updating the issue properly.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package asterisk - 1:1.8.4.4~dfsg-2ubuntu1.1

---------------
asterisk (1:1.8.4.4~dfsg-2ubuntu1.1) oneiric-proposed; urgency=low

  * debian/patches/backport-r312866.diff
  - Responding to OPTIONS packet with 404 because Asterisk not looking for
     "s" extension (LP: #920020)
 -- Paul Belanger <email address hidden> Sun, 11 Mar 2012 00:40:50 +0100

Changed in asterisk (Ubuntu Oneiric):
status: Fix Committed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Update Released

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.