<html><head>
<style>pre,code,address {
margin: 0px;
}
h1,h2,h3,h4,h5,h6 {
margin-top: 0.2em;
margin-bottom: 0.2em;
}
ol,ul {
margin-top: 0em;
margin-bottom: 0em;
}
blockquote {
margin-top: 0em;
margin-bottom: 0em;
}
</style></head>
<body><div>you call a reply route to handle the relpy. i.e. a positive outcome 200OK or a 183 etc. This reply should be relayed back to the originator and there should be no need to call another reply route. it won't expect a reply just an ack and that should be handled as an ACK and relayed or an error sent back. (see the default script)</div><div>if you want the reply route to do something else then add a route to do that or a branch route if needed. and call that from the reply route (not nested)</div><div><br></div><div>Richard<br><br></div><div><br></div><div>On Wed, 2026-04-08 at 15:38 +0200, spce@lard.at wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div> Hi,<br> <br> is it possible to use nested reply routes in opensips?<br> <br> I want to clean up my script and thinking of something like this:<br> </div><p><font size="2">> onreply_route[MAIN] {<br> > [...]<br> > is_from_gw(1) = t_on_reply("ADD_ISUP");> }<br> > [...] }<br> > onreply_route[ADD_ISUP] {<br> > add_isup_part() }</font></p><div> </div><p>The nested onreply route then should return to the parent onreply route. In my tests I specifically had issues with the rtpengine module: when using rtpengine_answer in the parent onreply route and then calling another onreply route from parent route, opensips wasn't able to see the SDP body in the reply and the rtpengine_answer thus failed.</p><div> </div><p><br> </p><div> -- <br> Liebe Grüße / Kind regards,<br> Malte<br> <br> </div><div>_______________________________________________<br></div><div>Users mailing list<br></div><div><a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br></div><div><a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br></div></blockquote><div><br></div><div><span></span></div></body></html>