Thanks Somesh,
 
I'm not too concerned anymore as I've found out that it has nothing to do with 
the problem I'm having but RFC 3261 also states:
 
   Additional "warn-code"s can be defined through IANA, as defined in
   Section 27.2.

Now the code that I'm receiving is clearly commonly used judging from a quick 
spell on google. The form of the warning text is always identical which leads 
me to think that it has been defined somewhere, I can't find where and it's not 
immediately obvious to me what the warning means. It looks like this (in a 200 
response to REGISTER):
 
Warning: 392 10.202.200.132:5061 "Noisy feedback tells:  pid=3439 
req_src_ip=10.202.200.143 req_src_port=1326 in_uri=sips:10.202.200.132:5061 
out_uri=sips:10.202.200.132:5061 via_cnt==1"
 
Basically what I was looking for is a list of all the warning codes that have 
been defined since 3261 but as I say, it is no longer of much importance to me 
as it has nothing to do with my problem so, unless anyone is aware of a such a 
list, I'll not take up any more of people's time.
 
Regards
 
Steve
 
 

-----Original Message-----
From: Somesh S Shanbhag [mailto:[EMAIL PROTECTED]
Sent: 21 July 2006 20:33
To: Stephen Paterson; SIP Implementors (E-mail)
Subject: Re: [Sip-implementors] Warning codes


Hi Stephen,

RFC 3261 27.2 clearly describes the following ...

"

Until a future specification
describes uses of warn-codes other than 3xx, only 3xx warn-codes may
be registered.

Warnings 300 through 329 are reserved for indicating problems with
keywords in the session description, 330 through 339 are warnings
related to basic network services requested in the session
description, 370 through 379 are warnings related to quantitative QoS
parameters requested in the session description, and 390 through 399
are miscellaneous warnings that do not fall into one of the above 
 categories.
"
Warning 392 is miscellaneous.

Section 20.43 of RFC 3261 has some descriptive list of 
warning codes which have been standardized.

Also, http://www.iana.org/assignments/sip-parameters summarises the codes.

Hope this helps,
Regards,
Somesh S. Shanbhag
  

Stephen Paterson <[EMAIL PROTECTED]> wrote: 

Hi all,

Is there an up to date list of codes for use in a Warning header anywhere? If 
so, please could someone send me a URL as I can't seem to find it. I am 
receiving such a header with a value of 392 from OpenSER when attempting to 
make a TLS call and do not fully understand it's meaning. It is not defined in 
3261.

Regards

Steve

Steve Paterson
Software Engineer
Aculab
Tel: +44 (0) 1908 273866
Fax: +44 (0) 1908 273801
Email: mailto:[EMAIL PROTECTED]
Website: http://www.aculab.com 

_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors





-----------------------------------------
SIMPLICITY IS THE BEAUTY.
BE NATURAL LIVE NATURAL.
-----------------------------------------
Somesh S. Shanbhag
Focus Area - VoIP Team (FA-VoIP)
Mascon Global Limited
#59/2, 100Ft Ring Road
Banashankari II stage
Bangalore-560070
Karnataka
INDIA
Website: http://www.mgl.com/
----------------------------------------- 



  _____  

Do you Yahoo!?
Everyone is raving about the all-new  
<http://us.rd.yahoo.com/evt=42297/*http://advision.webevents.yahoo.com/handraisers>
 Yahoo! Mail Beta.

_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to