[OpenSIPS-Users] Two OpenSIPS proxies issue

[duane.larson at gmail.com]

When comparing my sip trace to "  
http://www.tech-invite.com/Ti-sip-dialog.html#inv-ok " my 200OKs look  
right. They are being routed based on their VIA headers. The ACK messages  
don't look right when compared with the tech-invite website because the  
tech-invite websites ACK step doesn't have any Record-Route headers in  
them, only Route headers. My first ACK looks right with the ROUTE headers,  
but after that ACK is processed by my OpenSIPS/SBC the ACK message that is  
passed on to the OpenSIPS/Proxy has a ton of Record-Route headers and the  
RURI doesn't have the same uri as the first ACK. In my script I see that  
the ACK that comes from the caller is not being seen as a Loose Route so it  
is instead going to this part of my script

if ( is_method("ACK") ) {
if ( t_check_trans() ) {
# non loose-route, but stateful ACK; must be an ACK after
# a 487 or eg 404 from upstream server
force_send_socket(99.XX.XX.161:5060);
t_relay("udp:sip.XX.com:5060");
exit;


Perhaps this is the issue. Why would the ACK not show up as a loose route?  
This would explain why Record-Route headers are showing up in the ACK that  
is sent on to the OpenSIPS/Proxy.



On , duane.larson at gmail.com wrote:
> I did not find the problem. Yeah I've been looking at that exact link to  
> see what I am doing wrong. When I don't have the OpenSIPS/SBC device in  
> the equation, and a firewall that isn'ta pain, my logic on the  
> OpenSIPS/Proxy works without issue. I'll have to look harder at the ACK  
> and Route headers and see what is going wrong. If anyone spots the issue  
> let me know.



> On , Ali Pey alipey at gmail.com> wrote:
> > Does this mean that you found the problem?
> >
> > Basically you need to follow the Ack's request URI and Route headers to  
> see why it's being routed the way it is and then you'd know how to fix it.
> >
> >
> >
> > This is a good example similar to your scenario that you can use as a  
> reference: http://www.tech-invite.com/Ti-sip-dialog.html
> >
> >
> >
> > Regards,
> > Ali Pey
> >
> >
> > On Thu, Jul 5, 2012 at 10:18 PM, duane.larson at gmail.com> wrote:
> >
> > I see that the third 200 OK is edited by my OpenSIPS/Proxy server but  
> that is because in the location table in the "received" field I stored  
> the received Public IP address so that the replies are sent to the Public  
> IP address of the device instead of the private IP that was in the  
> original contact header.
> >
> >
> >
> >
> >
> >
> >
> > On , Ali Pey alipey at gmail.com> wrote:
> >
> > > Examine the Contact header of the 200 OK. That's where this usually  
> gets messed up.
> >
> > >
> >
> > > Regards,
> >
> > > Ali Pey
> >
> > >
> >
> > > On Wed, Jul 4, 2012 at 3:49 PM, Duane Larson duane.larson at gmail.com>  
> wrote:
> >
> > >
> >
> > >
> >
> > > I have the following scenario
> >
> > >
> >
> > >
> >
> >
> > > LAN OpenSIPS/SBC INTERNET OpenSIPS/Proxy
> >
> > >
> >
> > >
> >
> > >
> >
> > >
> >
> > > I have the OpenSIPS/SBC device because the firewall that is  
> protecting the LAN doesn't play well with SIP. It has the following IPs  
> (LAN = 192.168.88.1), WAN (99.xx.xx.161).
> >
> > >
> >
> > >
> >
> > >
> >
> > > The OpenSIPS/Proxy device sits on the internet and has the following  
> IP 50.xx.xx.156.
> >
> > >
> >
> > > All of the devices on the LAN point to the OpenSIPS/SBC as their  
> proxy and then the OpenSIPS/SBC relays all requests to the OpenSIPS/Proxy.
> >
> > >
> >
> > >
> >
> > >
> >
> > >
> >
> > >
> >
> > > The issue I am seeing is that when a call is set up after the Callee  
> sends the 200 OK the Caller sends the ACK but the ACK is never getting to  
> the Callee. So the Callee keeps sending 200 OKs and eventually when  
> someone hangs up the other person doesn't know.
> >
> > >
> >
> > >
> >
> > >
> >
> > >
> >
> > >
> >
> > > I see that when the Caller sends the ACK it is sent to the  
> OpenSIPS/SBC LAN address, then the OpenSIPS/SBC sends the ACK to the  
> OpenSIPS/Proxy, then the OpenSIPS/Proxy sends it back to the OpenSIPS/SBC  
> WAN address. All of that is good but the next thing that happens is that  
> the OpenSIPS/SBC sends the ACK not to the Callee but to its WAN  
> interface. I know this has something to do with my VIA headers but I am  
> not sure how my config is messed up.
> >
> > >
> >
> > >
> >
> > >
> >
> > >
> >
> > >
> >
> > >
> >
> > > Here is the siptrace of the call
> >
> > >
> >
> > > http://pastebin.com/wpbut5Nb
> >
> > >
> >
> > > Here is the current config on the OpenSIPS/SBC box
> >
> > >
> >
> > >
> >
> > >
> >
> > >
> >
> > >
> >
> > > http://pastebin.com/PsahZEX3
> >
> > >
> >
> > >
> >
> > > Any ideas where I've messed up?
> >
> > >
> >
> > >
> >
> > >
> >
> > > _______________________________________________
> >
> > >
> >
> > >
> >
> > > Users mailing list
> >
> > >
> >
> > >
> >
> > > Users at lists.opensips.org
> >
> > >
> >
> > >
> >
> > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
> > >
> >
> > >
> >
> > >
> >
> > >
> >
> > >
> >
> > >
> >
> > >
> >
> > >
> >
> > >
> >
> >
> > _______________________________________________
> >
> > Users mailing list
> >
> > Users at lists.opensips.org
> >
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
> >
> >
> >
> >
> >
> >
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20120707/c069f7f8/attachment-0001.htm>