[Home]

Summary:ASTERISK-20180: answer not found 404 to OPTIONS packet
Reporter:Alexey (ktoto)Labels:
Date Opened:2012-07-27 10:50:23Date Closed:2012-07-30 15:08:10
Priority:TrivialRegression?
Status:Closed/CompleteComponents:
Versions:10.6.1 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:look like issue described in ASTERISK-16997 (https://issues.asterisk.org/view.php?id=18348)
again affecting asterisk now version 10.6.x

<--- SIP read from TCP:1.1.1.1:50731 --->
OPTIONS sip:2.2.2.2 SIP/2.0
FROM: <sip:AV-LYNC01.AVDEV.local:5068;transport=Tcp;ms-opaque=36c4319c3ef90c0e>;epid=B1BEF88E13;tag=996ac7db2d
TO: <sip:2.2.2.2>
CSEQ: 109 OPTIONS
CALL-ID: 2e8d7e9baf814cdb8c78322ec5d21231
MAX-FORWARDS: 70
VIA: SIP/2.0/TCP 3.3.3.3:50731;branch=z9hG4bKd6a8de72
CONTACT: <sip:AV-LYNC01.AVDEV.local:5068;transport=Tcp;maddr=3.3.3.3>
CONTENT-LENGTH: 0
USER-AGENT: RTCC/4.0.0.0 MediationServer

<------------->
--- (10 headers 0 lines) ---
Looking for s in default (domain 2.2.2.2)

<--- Transmitting (NAT) to 1.1.1.1:50731 --->
SIP/2.0 404 Not Found
Via: SIP/2.0/TCP 3.3.3.3:50731;branch=z9hG4bKd6a8de72;received=1.1.1.1;rport=50731
From: <sip:AV-LYNC01.AVDEV.local:5068;transport=Tcp;ms-opaque=36c4319c3ef90c0e>;epid=B1BEF88E13;tag=996ac7db2d
To: <sip:2.2.2.2>;tag=as3615757e
Call-ID: 2e8d7e9baf814cdb8c78322ec5d21231
CSeq: 109 OPTIONS
Server: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Accept: application/sdp
Content-Length: 0
Comments:By: Rusty Newton (rnewton) 2012-07-27 13:25:26.473-0500

Alexy, it's looking for s in default, which should be correct.

What happens when you satisfy that with an s extension in default?
By: Alexey (ktoto) 2012-07-27 15:27:08.769-0500

Sorry. My fault.
I removed include => demo  from extensions.conf.
and not added anything.
After i added

[default]

exten => s,1,Hangup

All started to be ok.
Sorry for your time.

PS:
But i think it will be good to add to default extensions.conf special string for people who normally not use context default for calls but need to have handling of OPTIONS.
By: Rusty Newton (rnewton) 2012-07-30 15:08:01.755-0500

No worries!

At this time I'm not sure there is enough demand for that kind of option. As this scenario is fairly rare. We also don't want to add in too many tiny options and tweaks for every scenario under the sun.

The suggestion is noted, and always feel free to write a new feature and submit it, you never know.  Thanks.