[Bug 920020] Re: NOT FOUND answer on OPTIONS request

[Julian Taylor]

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.

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2011-4063

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2011-4598

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/920020

Title:
  NOT FOUND answer on OPTIONS request

Status in “asterisk” package in Ubuntu:
  Confirmed
Status in “asterisk” source package in Oneiric:
  Confirmed
Status in “asterisk” source package in Precise:
  Confirmed

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:pinger at sip.c5ng.b3g-telecom.com;tag=0
  To: sip:80.101.134.148:61304
  Call-ID: d34db33f-1325692477-3368860901 at 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:pinger at sip.c5ng.b3g-telecom.com;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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/920020/+subscriptions