[Home]

Summary:ASTERISK-16850: sip_setoption: Unknown option: 9
Reporter:Chodorenko Michail (chodorenko)Labels:
Date Opened:2010-10-22 10:12:37Date Closed:2010-11-01 15:29:32
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Channels/chan_sip/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:  Set("SIP/test-00000002", "CHANNEL(secure_bridge_media)=0") in new stack
[Oct 22 17:40:21] NOTICE[9446]: chan_sip.c:4034 sip_setoption: Unknown option: 9


****** ADDITIONAL INFORMATION ******

 Set("SIP/test-00000002", "CHANNEL(secure_bridge_media)=0") in new stack
[Oct 22 17:40:21] NOTICE[9446]: chan_sip.c:4034 sip_setoption: Unknown option: 9

All SET operation give Unknown option: 9
Comments:By: David Woolley (davidw) 2010-10-22 11:48:54

What bug are you reporting?  Why is it major?

What did you expect to happen?  Why is what is actually happening causing a problem?

NOTICE messages don't indicate bugs; not even WARNING ones do; in fact NOTICE messages indicate normal operation.  Are you reporting that this message has been miscategorised?

By: Chodorenko Michail (chodorenko) 2010-10-22 12:36:14

1.What bug are you reporting?
"Unknown option: 9" is not normal answer
2.Why is it major?
1.8.0 it`s LTS release for production system, this error misleading users (real value is changed)
3.What did you expect to happen?
must check and repair function it is calling.

PS this line "Set(CHANNEL(secure_bridge_media)=0)" is example of doc/tex/secure-calls.tex . On example i no not retrieve errors

By: Leif Madsen (lmadsen) 2010-11-01 14:24:01

There is not enough information provided. Per all SIP issues please provide at least:

* Asterisk console trace showing the full call trace
* Asterisk SIP debug
* Asterisk SIP history (enabled via sip.conf)

You'll also need to provide the relative dialplan along with a description of the end-points you're using and their settings. Your goal is to provide enough information to allow a developer to reproduce the issue.

By: Paul Belanger (pabelanger) 2010-11-01 15:29:31

The warning was recently removed.

---
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. Thanks!