[OpenSIPS-Users] non-transactional 4XX messages

[Tyler Merritt]

I would do this by matching the method of the packet in the main routing
block, and then using textops to search for the 403 in a subsequent if () {}
block, and then just drop; or exit;

My methods are usually not the most elegant solution - I'll wait for Dave or
one of the Devs to chime in with a better method :)

On Tue, Feb 22, 2011 at 10:09 AM, Jason Yeh <jason at streamoso.com> wrote:

> Hello everyone,
>
> This certain SIP UAS keeps on sending "SIP/2.0 403" messages to my OpenSIPS
> machine out of blue, this failure/warning messages has nothing to do with
> this certain client on the call. I wanted to figure out how to drop ("not
> proxy") that annoying non-transactional 4XX SIP Messages being routed
> through this proxy server, however I couldn't figure out where to get this
> message landed to my routing script. Because the fact that this requests
> wasn't initially sent by proxy, it will not land to the "failure_route"
> routing block.
>
> In summary, how can I configure OpenSIPS routing logic to handle the
> non-transactional 4XX request sent by someone else out of blue?
>
> Thanks,
> Jason
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20110222/c5a2dc88/attachment.htm>