Re: [OpenSIPS-Users] OpenSIPS debug logging SIP packets it deems non-local

2017-03-22 Thread Jock McKechnie
Thank you, Răzvan, I appreciate the confirmation of my suspicions.

The whole situation is very, VERY strange. I checked iptables (and
disabled) without a change, as well as ngrep - I have SIP traces
showing it attempting to talk to that OpenSIPS box by ngrepping _from_
the same OpenSIPS box. IP and port matches. I just cannot for the life
of me figure out why either the networking stack is not handing these
packets to OpenSIPS... or OpenSIPS is ignoring them to such a point it
isn't even logging them.

It's all very mysterious, and frankly, frustrating. I'm not entirely
sure what to try next.

I'm vaguely wondering if we have some really bizarre network assymetry
which is pushing the packets in via the wrong interface, but they have
totally different IPs (private vs public), so that doesn't even seem
possible, but I'm grasping at straws to explain what I'm seeing. I
need an exorcist!

 - Jock

On Mon, Mar 20, 2017 at 3:29 AM, Răzvan Crainea  wrote:
> Hi, Jock!
>
> If you are not seeing anything in the logs, it means that OpenSIPS doesn't
> even receive the message.
> I would first try to make a ngrep trace and see if the reply message gets on
> the machine. Next, I would double check the firewall rules of the machine,
> perhaps disabling the completely.
>
> Best regards,
>
> Răzvan Crainea
> OpenSIPS Solutions
> www.opensips-solutions.com
>
>
> On 03/15/2017 11:16 PM, Jock McKechnie wrote:
>>
>> We have an existing call flow layout that effectively runs:
>> "SBC" -> "OpenSIPS LB" -> "FreeSWITCH"
>>
>> and have recently added a middleman for completely abstract reasons so
>> it now goes:
>> "SBC" -> "OpenSIPS A" -> "OpenSIPS LB" -> "FreeSWITCH"
>>
>> And all of a sudden the LB OpenSIPS is unable to see replies from the
>> FreeSWITCH. My thinking at this time is that the LB has decided the
>> 200 OKs coming back from FreeSWITCH are not actually destined for it,
>> so it's ignoring them, as if were a stray packet on a different
>> dialogue that it's not able to understand mid-stream and dumps.
>>
>> The LB OpenSIPS is running a reasonably old version of OpenSIPS at
>> present, pending a mass corporate upgrade - 1.8.5.
>>
>> I have the 'debug' level set to '9' and I'm not seeing any hints that
>> OpenSIPS is seeing the discarded/ignored SIP packets in the log at
>> all. Is this action _not_ logged, or am I barking up the wrong tree
>> and OpenSIPS isn't even seeing this packet at all?
>>
>> Apologies for long-winded lead up to a simple question, but I wanted
>> to be thorough.
>>
>> As always, many thanks;
>>
>>   - Jock
>>
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] OpenSIPS debug logging SIP packets it deems non-local

2017-03-20 Thread Răzvan Crainea

Hi, Jock!

If you are not seeing anything in the logs, it means that OpenSIPS 
doesn't even receive the message.
I would first try to make a ngrep trace and see if the reply message 
gets on the machine. Next, I would double check the firewall rules of 
the machine, perhaps disabling the completely.


Best regards,

Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com

On 03/15/2017 11:16 PM, Jock McKechnie wrote:

We have an existing call flow layout that effectively runs:
"SBC" -> "OpenSIPS LB" -> "FreeSWITCH"

and have recently added a middleman for completely abstract reasons so
it now goes:
"SBC" -> "OpenSIPS A" -> "OpenSIPS LB" -> "FreeSWITCH"

And all of a sudden the LB OpenSIPS is unable to see replies from the
FreeSWITCH. My thinking at this time is that the LB has decided the
200 OKs coming back from FreeSWITCH are not actually destined for it,
so it's ignoring them, as if were a stray packet on a different
dialogue that it's not able to understand mid-stream and dumps.

The LB OpenSIPS is running a reasonably old version of OpenSIPS at
present, pending a mass corporate upgrade - 1.8.5.

I have the 'debug' level set to '9' and I'm not seeing any hints that
OpenSIPS is seeing the discarded/ignored SIP packets in the log at
all. Is this action _not_ logged, or am I barking up the wrong tree
and OpenSIPS isn't even seeing this packet at all?

Apologies for long-winded lead up to a simple question, but I wanted
to be thorough.

As always, many thanks;

  - Jock

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users