> On April 23, 2014, 9:13 a.m., Mark Michelson wrote:
> > /trunk/channels/chan_sip.c, lines 30787-30791
> > <https://reviewboard.asterisk.org/r/3438/diff/1/?file=57236#file57236line30787>
> >
> > I'm a bit confused by this. If the configured timerc value is greater
> > than 100 seconds, then that is considered invalid and the default of 180
> > seconds is used instead.
> >
> > RFC 3261 Section 16.6, bullet point 11 states that timer C MUST be
> > larger than 3 minutes. I would expect, then, that if the configured value
> > were less than 180 seconds, that is when you would consider the
> > configuration to be invalid and go with the default value of 180 seconds.
Hey Olle - I took a look at RFC 3261 to see what Mark was alluding to here, and
I think he is right - the minimum shouldn't be less than 3 minutes:
{quote}
11. Set timer C
In order to handle the case where an INVITE request never
generates a final response, the TU uses a timer which is called
timer C. Timer C MUST be set for each client transaction when
an INVITE request is proxied. The timer MUST be larger than 3
minutes. Section 16.7 bullet 2 discusses how this timer is
updated with provisional responses, and Section 16.8 discusses
processing when it fires.
{quote}
Is there a reason why we wouldn't go with a default value of 180 seconds, per
the RFC?
- Matt
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/3438/#review11719
-----------------------------------------------------------
On May 16, 2014, 7:32 a.m., Olle E Johansson wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/3438/
> -----------------------------------------------------------
>
> (Updated May 16, 2014, 7:32 a.m.)
>
>
> Review request for Asterisk Developers.
>
>
> Repository: Asterisk
>
>
> Description
> -------
>
> SIP Timer C is defined for proxys that forward messages. In some ways, we
> forward calls. It is activated when we receive a 100 trying and wait for any
> other message. If that's not received, timer C triggers and cancels the call
> attempt.
>
> This is required in an interoperability test I'm working with.
>
> Red dots will be handled in the way they deserve.
>
>
> Diffs
> -----
>
> /trunk/configs/sip.conf.sample 414046
> /trunk/channels/sip/include/sip.h 414046
> /trunk/channels/chan_sip.c 414046
> /trunk/CHANGES 414046
>
> Diff: https://reviewboard.asterisk.org/r/3438/diff/
>
>
> Testing
> -------
>
> Passed interoperability testing with funky test tool.
>
>
> Thanks,
>
> Olle E Johansson
>
>
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
