Quote:
Originally Posted by v164
There isn't at the moment, unless you can find some SIP destination (perhaps among the SIP Broker peers) to which you could forward the call that would answer 486 BUSY to every call.
|
That's easy. Just send the call to an invalid (improperly formatted for the service) phone number, on any service reachable via SIP Broker, and the party will likely get a "busy". Yes, it's a royal kludge, but it does seem to work to "black list" some pattern...
Quote:
Originally Posted by v164
Actually, I've been thinking that a SIP server (VoXaLot or other) that just dishes out canned responses could be useful. For example, some dummy SIP URIs could be set up, such as:
reply486BUSY@voxalot.com (responds with 486 BUSY to every call).
reply380PSTN@voxalot.com (responds with 380 Alternative Service, PSTN) |
I like your thinking. If those URIs were around, than anyone trying to cause one of these behaviors should only need to redirect the call to the appropriate URI. Yes, that would still be a kludge, but a much less messy one than simply trying to get unexpected behaviors out of existing service providers.