James, Only SIP Requests are processed by the route function. That is why it makes sense for the INVITEs, REGISTERs, and OPTIONs, BYEs, ACKs, etc. The 486 is a reply and is handled by OpenSIPS according to normal SIP rules. It will not cause the script to run at all unless you are using the transaction module and have registered an onreply_route or failure_route with t_on_reply or t_on_failure. But you would not want to use loose_route there as that is meant only for request processing.
Ben Newlin From: James Thomas Reply-To: OpenSIPS users mailling list Date: Friday, May 22, 2015 at 12:56 PM To: "users@lists.opensips.org<mailto:users@lists.opensips.org>" Subject: [OpenSIPS-Users] Residential Script - noob question I've been stepping through the residential script and looking at rfc3665 in order to get an understanding of how things work. So far so good on simple INVITES, REGISTERS, etc. But I'm a little confused on case 3.9 Unsuccessful Busy. It might be my lack of complete understanding of loose_route.. When Bob's phone sends the 486 Busy and it comes into the proxy, the to-tag is set so that code block gets executed. Is loose_route true or not? I thought not since there aren't Route headers present. If it is true, why? If it's false what happens to the 486 at that point? Or does the proxy do work behind the scenes of the script by ACKing then creating its own 486 to send to proxy 1? Thanks for any insight.
_______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
