I've been staring at nget output for a while now, comparing the working transaction (rewritehost at the top of route logic) against the rewrite after load_balance.
They look nearly identical, the change comes after the client (sipp) sends an ACK; In the working capture, sipp sends an ACK, and then opensips forwards the ACK to Asterisk, decrementing Max-Forwards to 69, call goes through, sipp says BYE and all is happy. In the failed example, opensips does not forward the ACK. Instead, Asterisk sends an OK response to opensips, and Max-Forwards remains at 70, and we're caught in a loop. _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
