[VoiceOps] SIP 404 Not Found vs 603 Decline
jared at compuwizz.net
Wed Jun 3 15:16:23 EDT 2015
I would play a 183 message saying "The subscriber you have dialed has
selective call reject enabled." Then send a 487 Request Terminated. That
way you don't have to answer the call and still get the message across.
I thought Verizon had a test case for this in interop.
I'm not sure if 487s get thrown back into the redial queue usually or if
most LCRs fail over on it. I would rather send a 603 or 604 back, but I
know LCRs typically route advance on 500 and 600 level responses.
On Wed, Jun 3, 2015 at 9:44 AM, Jay Hennigan <jay at west.net> wrote:
> On 6/2/15 1:58 PM, Peter Beckman wrote:
>> I offer a feature to our customers that allows them to configure their DID
>> to respond with "This number is disconnected" message for specific,
>> annoying callers, based on their CallerID.
>> Some customers send a Busy signal (486 BUSY) for these annoying callers.
>> seems that some Robocallers will retry numbers that ring busy repeatedly,
>> sometimes annoyingly aggressively.
>> I'm switching the default to declining the call, which brings me to which
>> SIP response is correct and/or ideal.
> 486 Busy has the advantage that it usually won't route-advance, ending the
> churn on the network for that call. Letting the abusers churn and waste
> their resources retrying forever may not be a bad thing.
> 200 OK followed by a "Go away" intercept recording would be another
> option. Let the call supervise and cost the abusers a fraction of a cent
> without bothering any humans on the receiving end.
> You don't want to do this if the endpoint is a tollfree number, obviously.
>  Asterisk's "Our phone system has been eaten by monkeys" might be a
> good choice.
> Jay Hennigan - CCIE #7880 - Network Engineering - jay at impulse.net
> Impulse Internet Service - http://www.impulse.net/
> Your local telephone and internet company - 805 884-6323 - WB6RDV
> VoiceOps mailing list
> VoiceOps at voiceops.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the VoiceOps