Oh, I see what you mean. I thought you meant initially not to put it in the main routing block. You are right, I have it in the route(1) block, and I should put it in the route_branch(1) block.<br><br>Thanks<br clear="all">
<br>-dg<br>
<br><br><div class="gmail_quote">On Thu, Aug 5, 2010 at 7:26 AM, Bogdan-Andrei Iancu <span dir="ltr"><<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi Daniel,<br>
<br>
by "I do the rtpproxy_offer in the first branch" do you mean you do the<br>
rtpproxy_offer() in a branch_route ?<br>
<div class="im"><br>
Regards,<br>
Bogdan<br>
<br>
Daniel Goepp wrote:<br>
</div><div class="im">> I'm not actually doing it globally, I do the rtpproxy_offer in the<br>
> first branch (since I need to for the first call), then when it fails,<br>
> it calls the second branch. I'm thinking the better way to handle<br>
> this I guess is to serialize the branches.<br>
><br>
> -dg<br>
><br>
><br>
> On Wed, Aug 4, 2010 at 2:51 PM, Bogdan-Andrei Iancu<br>
</div><div class="im">> <<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a> <mailto:<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a>>> wrote:<br>
><br>
> Hi Daniel,<br>
><br>
> not really....the bad idea was to to rtpproxy stuff in request route<br>
> (globally), considering that you want to do per-branch changes<br>
> :)....Again use only branch route to do the per-branch changes.<br>
><br>
> REgards,<br>
> Bogdan<br>
><br>
> Daniel Goepp wrote:<br>
> > Okay, I guess I will have to figure out a different way to handle<br>
> > this. Am I correct in assuming then the idea of putting a route(10)<br>
> > for example nested in the failure block of another route is a<br>
> bad idea?<br>
> ><br>
> > -dg<br>
> ><br>
> ><br>
> > On Wed, Aug 4, 2010 at 10:04 AM, Bogdan-Andrei Iancu<br>
> > <<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a> <mailto:<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a>><br>
</div>> <mailto:<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a> <mailto:<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a>>>><br>
<div><div></div><div class="h5">> wrote:<br>
> ><br>
> > Hi Daniel,<br>
> ><br>
> > it is not a bug - the idea is you must not call RTPproxy<br>
> function more<br>
> > than once per branch - and keep in mind that whatever<br>
> changes you<br>
> > do in<br>
> > request route do apply to all branches.....<br>
> ><br>
> > If you want to do per branch changed, use the branch route.<br>
> ><br>
> > Regards,<br>
> > Bogdan<br>
> ><br>
> > Daniel Goepp wrote:<br>
> > > I don't think I would call this a "bug" quite yet, but<br>
> figured it<br>
> > > might be worth bringing up. Here is the call scenario:<br>
> > ><br>
> > > User A calls User B, no answer, timer hit, forward call. The<br>
> > original<br>
> > > timeout was on route(1), and I just rewrite some info, and<br>
> execute<br>
> > > route(10) from the failure branch. This is probably bad<br>
> > practice, and<br>
> > > I would appreciate input on how this would be better<br>
> handled. But<br>
> > > that said, here is what I see. Since route(1) had already<br>
> done a<br>
> > > rtpproxy_offer, when I hit route (10), it does the same again,<br>
> > > resulting in a line in the SDP that looks like:<br>
> > ><br>
> > > m=audio 3061830618 RTP/AVP 99 100 101 9 11 0 102.<br>
> > ><br>
> > > See the problem? If I make a call that naturally would go to<br>
> > > route(10), that is not a problem, I see:<br>
> > ><br>
> > > m=audio 28568 RTP/AVP 99 100 101 9 11 0 102.<br>
> > ><br>
> > > It would appear that rtpproxy_offer is trying to append<br>
> the port<br>
> > > number to an already existing port number. Make sense?<br>
> > ><br>
> > > -dg<br>
> > ><br>
> ><br>
> ------------------------------------------------------------------------<br>
> > ><br>
> > > _______________________________________________<br>
> > > Users mailing list<br>
> > > <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a> <mailto:<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>><br>
</div></div>> <mailto:<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a> <mailto:<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>>><br>
<div class="im">> > > <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
> > ><br>
> ><br>
> ><br>
> > --<br>
> > Bogdan-Andrei Iancu<br>
> > OpenSIPS Bootcamp<br>
> > 20 - 24 September 2010, Frankfurt, Germany<br>
> > <a href="http://www.voice-system.ro" target="_blank">www.voice-system.ro</a> <<a href="http://www.voice-system.ro" target="_blank">http://www.voice-system.ro</a>><br>
> <<a href="http://www.voice-system.ro" target="_blank">http://www.voice-system.ro</a>><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > Users mailing list<br>
> > <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a> <mailto:<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>><br>
</div>> <mailto:<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a> <mailto:<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>>><br>
<div><div></div><div class="h5">> > <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
> ><br>
> ><br>
> ><br>
> ------------------------------------------------------------------------<br>
> ><br>
> > _______________________________________________<br>
> > Users mailing list<br>
> > <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a> <mailto:<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>><br>
> > <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
> ><br>
><br>
><br>
> --<br>
> Bogdan-Andrei Iancu<br>
> OpenSIPS Bootcamp<br>
> 20 - 24 September 2010, Frankfurt, Germany<br>
> <a href="http://www.voice-system.ro" target="_blank">www.voice-system.ro</a> <<a href="http://www.voice-system.ro" target="_blank">http://www.voice-system.ro</a>><br>
><br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a> <mailto:<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>><br>
> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
><br>
><br>
> ------------------------------------------------------------------------<br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
> <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
><br>
<br>
<br>
--<br>
Bogdan-Andrei Iancu<br>
OpenSIPS Bootcamp<br>
20 - 24 September 2010, Frankfurt, Germany<br>
<a href="http://www.voice-system.ro" target="_blank">www.voice-system.ro</a><br>
<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br>