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 <[email protected]> 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, [email protected]> 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 [email protected]> 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 [email protected]>
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
>
>
> [email protected]
>
>
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
>
>
>
>
>
>
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
