asterisk users - Feb 2016 - Asterisk 13.6.0/The simplest TCP configuration does not work

Sonny Rajagopalan wrote:
> Is there a specific place where I can set logger to log incoming TCP
> segments from L4?
>
> $ netstat -tulpn | grep asterisk | grep LISTEN:
>
> tcp        0      0 0.0.0.0:8088 <http://0.0.0.0:8088>
>   0.0.0.0:*               LISTEN      10313/asterisk
> tcp        0      0 0.0.0.0:5060 <http://0.0.0.0:5060>
>   0.0.0.0:*               LISTEN      10313/asterisk
> tcp        0      0 0.0.0.0:2000 <http://0.0.0.0:2000>
>   0.0.0.0:*               LISTEN      10313/asterisk
"pjsip set logger on" will output all incoming and outgoing SIP
traffic
for all transports in PJSIP, and when a connection is established it is 
logged to the console.

-- 
Joshua Colp
Digium, Inc. | Senior Software Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - US
Check us out at: www.digium.com & www.asterisk.org

Sorry, I was not being very clear, Joshua, and thanks for your patience
with this issue.

I had set pjsip set logger on and core set debug 99. See absolutely zilch
on asterisk CLI. Or in /var/log/asterisk/messages. If the messages are not
reaching Asterisk, what could be the issue? I am a little perplexed as to
why Asterisk wouldn't consume those TCP segments; the port is owned by
Asterisk.

On Wed, Feb 17, 2016 at 8:15 AM, Joshua Colp <jcolp at digium.com> wrote:
> Sonny Rajagopalan wrote:
>
>> Is there a specific place where I can set logger to log incoming TCP
>> segments from L4?
>>
>> $ netstat -tulpn | grep asterisk | grep LISTEN:
>>
>> tcp        0      0 0.0.0.0:8088 <http://0.0.0.0:8088>
>>   0.0.0.0:*               LISTEN      10313/asterisk
>> tcp        0      0 0.0.0.0:5060 <http://0.0.0.0:5060>
>>   0.0.0.0:*               LISTEN      10313/asterisk
>> tcp        0      0 0.0.0.0:2000 <http://0.0.0.0:2000>
>>   0.0.0.0:*               LISTEN      10313/asterisk
>>
>
> "pjsip set logger on" will output all incoming and outgoing SIP
traffic
> for all transports in PJSIP, and when a connection is established it is
> logged to the console.
>
>
> --
> Joshua Colp
> Digium, Inc. | Senior Software Developer
> 445 Jan Davis Drive NW - Huntsville, AL 35806 - US
> Check us out at: www.digium.com & www.asterisk.org
>
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
>               http://www.asterisk.org/hello
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20160217/fc808b6c/attachment.html>

Sonny Rajagopalan wrote:
> Sorry, I was not being very clear, Joshua, and thanks for your patience
> with this issue.
>
> I had set pjsip set logger on and core set debug 99. See absolutely
> zilch on asterisk CLI. Or in /var/log/asterisk/messages. If the messages
> are not reaching Asterisk, what could be the issue? I am a little
> perplexed as to why Asterisk wouldn't consume those TCP segments; the
> port is owned by Asterisk.
Then it's likely something outside the scope of Asterisk, if the 
connection (and messages) don't even seem to be reaching Asterisk at 
all. You could try to just telnet to it and see if you get a connection 
message on the Asterisk CLI. Do it from the machine itself and then 
outside. If it works from the machine itself but not outside, then 
you've narrowed it down more.

-- 
Joshua Colp
Digium, Inc. | Senior Software Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - US
Check us out at: www.digium.com & www.asterisk.org