Hi,
I have a Comtrend SIP UA here and it breaks when I have 'sip_warning=yes' in ser.cfg. It doesn't like the warning header to be too long. I couldn't find anywhere in the SIP RFC's whether there is a maximum length to this header. When I set sip_warning to no, the UA works fine, however I think I read somewhere once that this warning header is sometimes mandatory. Can someone confirm or deny that ?
Thanks,
Leon de Rooij leon@scarlet-internet.nl
On Oct 19, 2004 at 15:28, Leon de Rooij leon@scarlet-internet.nl wrote:
Hi,
I have a Comtrend SIP UA here and it breaks when I have 'sip_warning=yes' in ser.cfg. It doesn't like the warning header to be too long. I couldn't find anywhere in the SIP RFC's whether there is a maximum length to this header. When I set sip_warning to no, the UA works fine, however I think I read somewhere once that this warning header is sometimes mandatory. Can someone confirm or deny that ?
It's not mandatory, it's optional (rfc3261).
Andrei
Thanks !
Leon
On Tue, 2004-10-19 at 15:49 +0200, Andrei Pelinescu-Onciul wrote:
On Oct 19, 2004 at 15:28, Leon de Rooij leon@scarlet-internet.nl wrote:
Hi,
I have a Comtrend SIP UA here and it breaks when I have 'sip_warning=yes' in ser.cfg. It doesn't like the warning header to be too long. I couldn't find anywhere in the SIP RFC's whether there is a maximum length to this header. When I set sip_warning to no, the UA works fine, however I think I read somewhere once that this warning header is sometimes mandatory. Can someone confirm or deny that ?
It's not mandatory, it's optional (rfc3261).
Andrei
On Tuesday 19 October 2004 15:49, Andrei Pelinescu-Onciul wrote:
On Oct 19, 2004 at 15:28, Leon de Rooij leon@scarlet-internet.nl wrote:
Hi,
I have a Comtrend SIP UA here and it breaks when I have 'sip_warning=yes' in ser.cfg. It doesn't like the warning header to be too long. I couldn't find anywhere in the SIP RFC's whether there is a maximum length to this header. When I set sip_warning to no, the UA works fine, however I think I read somewhere once that this warning header is sometimes mandatory. Can someone confirm or deny that ?
It's not mandatory, it's optional (rfc3261).
It is only "mandatory" if you want to be able to make SIP traceroutes (e.g. with sipsak). Allthough for that feature it would only be necessary in responses on OPTIONS requests or generally in 483 responses :-)
Nils
-
Andrei Pelinescu-Onciul -
Leon de Rooij -
Nils Ohlmeier