Hello everyone,
I've had the time to examine some specific serial/parallel forking
scenarios with Asterisk lately. Looking at chan_sip it appears that
anytime Asterisk wants to tear down a call before it's brought up, it
sends a 603 Declined:
} else {/* Incoming
Kristian,
Unfortunately, 603 Declined is frequently misused this way by service
providers and SIP stacks. It seems to be a catch-all epithet for some
sort of miscellaneous call completion failure that cannot be categorised
any other way, much like 503 Service Unavailable.
I agree 100% with th
On Thu, Jan 28, 2010 at 4:23 PM, Alex Balashov
wrote:
>
> It's also problematic because a 3261-compliant SIP proxy or UAC is not
> going to attempt to reach the destination by alternate means (serial
> forking in the case of the proxy, or a new call leg in the case of the
> UA) because of this pre
On 01/28/2010 04:47 PM, Kristian Kielhofner wrote:
> On Thu, Jan 28, 2010 at 4:23 PM, Alex Balashov
> wrote:
>>
>> It's also problematic because a 3261-compliant SIP proxy or UAC is not
>> going to attempt to reach the destination by alternate means (serial
>> forking in the case of the proxy, o
On Thu, Jan 28, 2010 at 4:52 PM, Alex Balashov
wrote:
>
> I was just about to mention the disable_6xx_block parameter, but figured
> it would be too pedantic/off-topic for this thread.
I didn't. Google has a great memory and hopefully now when some
poor soul is researching this (Asterisk + Ope
Agree that the 603 is wrong. It hasn't caused me issues but I see where it
could. And it goes against what I have been teaching in my classes, which is
irritating ;-)
In Asterisk, it's only used when we have no other hangup cause - and is
propably an indication that there is a code path that do
I don't know about 4xx, but 503 would be more benign for general/
miscellaneous errors than 603.
--
Sent from mobile device
On Jan 29, 2010, at 3:54 AM, "Olle E. Johansson" wrote:
> Agree that the 603 is wrong. It hasn't caused me issues but I see
> where it could. And it goes against what
29 jan 2010 kl. 10.25 skrev Alex Balashov:
> I don't know about 4xx, but 503 would be more benign for general/
> miscellaneous errors than 603.
503 indicates that there's a problem with the server, so that's not a good
replacement.
We're sending this when there's a failed call, in most cases b
On Jan 29, 2010, at 5:59 AM, Olle E. Johansson wrote:
>
> 29 jan 2010 kl. 10.25 skrev Alex Balashov:
>
>> I don't know about 4xx, but 503 would be more benign for general/
>> miscellaneous errors than 603.
> 503 indicates that there's a problem with the server, so that's not a good
> replaceme
On Fri, Jan 29, 2010 at 5:59 AM, Olle E. Johansson wrote:
>
> 29 jan 2010 kl. 10.25 skrev Alex Balashov:
>
>> I don't know about 4xx, but 503 would be more benign for general/
>> miscellaneous errors than 603.
> 503 indicates that there's a problem with the server, so that's not a good
> replacem
Kristian Kielhofner wrote:
> I don't want to ruin your plans for tonight (RFC3261 is a lot of
> fun) but how about 403:
>
> 21.4.4 403 Forbidden
>
>The server understood the request, but is refusing to fulfill it.
>Authorization will not help, and the request SHOULD NOT be repeated.
W
On Fri, Jan 29, 2010 at 10:31 AM, Kevin P. Fleming wrote:
>
> Well, that's the problem, and it's the reason why 603 is so commonly
> used. This is a situation where the current request has failed, but
> there is no indication that repeating the request will also fail. 403
> means that the request
29 jan 2010 kl. 17.20 skrev Kristian Kielhofner:
> On Fri, Jan 29, 2010 at 10:31 AM, Kevin P. Fleming
> wrote:
>>
>> Well, that's the problem, and it's the reason why 603 is so commonly
>> used. This is a situation where the current request has failed, but
>> there is no indication that repeat
Olle E. Johansson wrote:
> Here's something interesting:
>
> 21.4.25 487 Request Terminated
> The request was terminated by a BYE or CANCEL request. This response is never
> returned for a CANCEL
> request itself.
>
> This is only used in combination with Cancel's, but in this case the call was
On Sat, Jan 30, 2010 at 9:03 AM, Kevin P. Fleming wrote:
> Olle E. Johansson wrote:
>
>> Here's something interesting:
>>
>> 21.4.25 487 Request Terminated
>> The request was terminated by a BYE or CANCEL request. This response is
>> never returned for a CANCEL
>> request itself.
>>
>> This is on
15 matches
Mail list logo