Hi Jason,
What is interesting for you would be :
http://www.opensips.org/Resources/DocsCoreFcn16#toc38
As you say that 403 reply does not match any transaction on your
opensips, it will be considered stateless and dropped - for this you
have to be sure you are not using any stateless relay function like
"forward" for sending the requests.
Regards,
Bogdan
Jason Yeh 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
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
--
Bogdan-Andrei Iancu
OpenSIPS eBootcamp - 28th February 2011
OpenSIPS solutions and "know-how"
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
