Re: [asterisk-users] Asterisk 13.6.0/The simplest TCP configuration does not work

2016-02-18 Thread Joshua Colp 

Sonny Rajagopalan wrote:

George,

May I propose we improve the documentation on the Asterisk Wiki? I
thought I would have spent far less time here (though you folks have
been mightily helpful, and thanks again!) should the documentation for
the TCP transport be improved in both the Wiki and specifically, in
${ASTERISK_HOME}/configs/samples/, bundled as part of the code. I want
to see Asterisk as a product succeed (even more) and Asterisk in its new
version succeed wildly.

I don't know if you folks allow outside developers to pitch in, but
depending on a number of factors, I might contribute to
https://gerrit.asterisk.org/ if that is within Asterisk's policy. Again,
depending on a number of factors, including legal.


Anyone can contribute changes to Asterisk provided a contributor license 
agreement is signed. The process is on the wiki itself too[1].


[1] https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process

--
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

Re: [asterisk-users] Asterisk 13.6.0/The simplest TCP configuration does not work

2016-02-18 Thread Sonny Rajagopalan 
George,

May I propose we improve the documentation on the Asterisk Wiki? I thought
I would have spent far less time here (though you folks have been mightily
helpful, and thanks again!) should the documentation for the TCP transport
be improved in both the Wiki and specifically, in
${ASTERISK_HOME}/configs/samples/, bundled as part of the code. I want to
see Asterisk as a product succeed (even more) and Asterisk in its new
version succeed wildly.

I don't know if you folks allow outside developers to pitch in, but
depending on a number of factors, I might contribute to
https://gerrit.asterisk.org/ if that is within Asterisk's policy. Again,
depending on a number of factors, including legal.

Here, specifically, is the list of improvements I propose:

(a) One full example showing how a TCP based Asterisk platform should work
in the PJSIP world, including both SIP over TCP-compliant SIP trunk
configuration using pjsip_wizard.conf
(b) One complete example reflected in the distributed code samples within
Asterisk code, in ${ASTERISK_HOME}/configs/samples/.
(c) A full SIP trace for Asterisk, the working examples, for all manner of
transports (UDP, TCP, TLS), for REGISTER, INVITE etc.

Hope this helps.

Thanks again!

On Wed, Feb 17, 2016 at 3:48 PM, George Joseph 
wrote:

>
>
> On Wed, Feb 17, 2016 at 12:13 PM, Sonny Rajagopalan <
> sonny.rajagopa...@gmail.com> wrote:
>
>> Wow. Incredible. That worked. The backslash is important there; I kept
>> trying with no backslash and followed the instructions in
>> pjsip_wizard.conf.sample (in configs/samples) and it says we have to say
>>
>> transport=tcp ; the only example however talks about ipv4.
>>
>> Is this documented somewhere and I just missed it??
>>
>> So, let me sum the issues and their solutions:
>>
>> (a) Inside/from-internal calling. Only need transport=tcp in pjsip.conf.
>> No need to update every SIP (user) endpoint's transport, though that did
>> not disrupt anything.
>> (b) For pjsip_wizard configuration, add the transport into the
>> remote_hosts line like so noting that the backslash is important otherwise
>> the transport part of the line is a comment!
>>
>> remote_hosts = silly.pstn.twilio.com​\;transport=tcp
>>
>> Simple errors, but vexing, vexing, vexing issues.
>>
>
> One thing to be aware of...​
>
> There is currently a PJSIP bug when using TCP and TLS that shows up if you
> explicitly
> set transport= on an endpoint (or in the wizard).  It's best to leave
> transport unset and
> let PJSIP determine the transport from the ;transport= parameter of the
> URI.
>
> From a wizard perspective, if you have lots of TCP or TLS endpoints, use a
> template like so...
>
> [tcp-template](!)
> server_uri_pattern = sip:${REMOTE_HOST}\;transport=TCP
> client_uri_pattern = sip:${REMOTE_HOST}\;transport=TCP
> contact_pattern = sip:${REMOTE_HOST}\;transport=TCP
>
> [tls-template](!)
> server_uri_pattern = sips:${REMOTE_HOST}\;transport=TLS
> client_uri_pattern = sips:${REMOTE_HOST}\;transport=TLS
> contact_pattern = sips:${REMOTE_HOST}\;transport=TLS
>
> [tcp-provider](tcp-template]
> remote_hosts = my.provider.net
>
> Let me know if the wiki can use some clarification.  I haven't updated it
> in a while.
>
>
>>
>> Thanks, George, and thanks Joshua, for your time!
>>
>>
>
> --
> _
> -- 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
>
-- 
_
-- 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

Re: [asterisk-users] Asterisk 13.6.0/The simplest TCP configuration does not work

2016-02-17 Thread George Joseph 
On Wed, Feb 17, 2016 at 12:13 PM, Sonny Rajagopalan <
sonny.rajagopa...@gmail.com> wrote:

> Wow. Incredible. That worked. The backslash is important there; I kept
> trying with no backslash and followed the instructions in
> pjsip_wizard.conf.sample (in configs/samples) and it says we have to say
>
> transport=tcp ; the only example however talks about ipv4.
>
> Is this documented somewhere and I just missed it??
>
> So, let me sum the issues and their solutions:
>
> (a) Inside/from-internal calling. Only need transport=tcp in pjsip.conf.
> No need to update every SIP (user) endpoint's transport, though that did
> not disrupt anything.
> (b) For pjsip_wizard configuration, add the transport into the
> remote_hosts line like so noting that the backslash is important otherwise
> the transport part of the line is a comment!
>
> remote_hosts = silly.pstn.twilio.com​\;transport=tcp
>
> Simple errors, but vexing, vexing, vexing issues.
>

One thing to be aware of...​

There is currently a PJSIP bug when using TCP and TLS that shows up if you
explicitly
set transport= on an endpoint (or in the wizard).  It's best to leave
transport unset and
let PJSIP determine the transport from the ;transport= parameter of the URI.

>From a wizard perspective, if you have lots of TCP or TLS endpoints, use a
template like so...

[tcp-template](!)
server_uri_pattern = sip:${REMOTE_HOST}\;transport=TCP
client_uri_pattern = sip:${REMOTE_HOST}\;transport=TCP
contact_pattern = sip:${REMOTE_HOST}\;transport=TCP

[tls-template](!)
server_uri_pattern = sips:${REMOTE_HOST}\;transport=TLS
client_uri_pattern = sips:${REMOTE_HOST}\;transport=TLS
contact_pattern = sips:${REMOTE_HOST}\;transport=TLS

[tcp-provider](tcp-template]
remote_hosts = my.provider.net

Let me know if the wiki can use some clarification.  I haven't updated it
in a while.


>
> Thanks, George, and thanks Joshua, for your time!
>
>
-- 
_
-- 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

Re: [asterisk-users] Asterisk 13.6.0/The simplest TCP configuration does not work

2016-02-17 Thread Sonny Rajagopalan 
Wow. Incredible. That worked. The backslash is important there; I kept
trying with no backslash and followed the instructions in
pjsip_wizard.conf.sample (in configs/samples) and it says we have to say

transport=tcp ; the only example however talks about ipv4.

Is this documented somewhere and I just missed it??

So, let me sum the issues and their solutions:

(a) Inside/from-internal calling. Only need transport=tcp in pjsip.conf. No
need to update every SIP (user) endpoint's transport, though that did not
disrupt anything.
(b) For pjsip_wizard configuration, add the transport into the remote_hosts
line like so noting that the backslash is important otherwise the transport
part of the line is a comment!

remote_hosts = silly.pstn.twilio.com​\;transport=tcp

Simple errors, but vexing, vexing, vexing issues.

Thanks, George, and thanks Joshua, for your time!

On Wed, Feb 17, 2016 at 12:43 PM, George Joseph  wrote:

>
>
> On Wed, Feb 17, 2016 at 8:56 AM, Sonny Rajagopalan <
> sonny.rajagopa...@gmail.com> wrote:
>
>> I made some progress. The first thing I have realized is that it is my
>> Twilio configuration in pjsip_wizard.conf that was killing me. I have since
>> removed that entire file from /etc/asterisk and I am able to make
>> "from-internal" context calls (i.e., calls that do not leave the VoIP
>> island).
>>
>> Here's what I have right now in pjsip_wizard.conf (again, I have removed
>> it from /etc/asterisk/ because Asterisk won't even work for "from-internal"
>> calls with the conf in /etc/asterisk)
>>
>> [twilio-siptrunk]
>> type = wizard
>> sends_auth = yes
>> sends_registrations = no
>> remote_hosts = silly.pstn.twilio.com
>>
>
> remote_hosts = silly.pstn.twilio.com
> ​\;transport=TCP​
>
>
> outbound_auth/username = username
>> outbound_auth/password = sillypassword
>> endpoint/context = from-external ;;; change later
>> endpoint/disallow = all ;;; change later
>> endpoint/allow = ulaw ;;; change later
>> aor/qualify_frequency = 15
>>
>> What should I change/add/modify above to make Asterisk and Twilio work
>> with TCP? Note that I do not have to trigger a use of the twilio sip trunk
>> for my Asterisk daemon to not work for TCP. If I have the pjsip_wizard in
>> /etc/asterisk, it does not work for _any_ call, regardless of whether or
>> not the call should use the Twilio SIP trunk.
>>
>> (again, the same asterisk configuration on the same machine connected to
>> the same twilio SIP trunk worked for UDP)
>>
>> If anyone knows the trick to make pjsip_wizard.conf work with twilio, I
>> would very much appreciate any insight...
>>
>> Thanks,
>> Sonny.
>>
>> On Wed, Feb 17, 2016 at 8:38 AM, Sonny Rajagopalan <
>> sonny.rajagopa...@gmail.com> wrote:
>>
>>> Yes, it is enabled on port 5060. I do receive a TCP ACK back from the
>>> server, so I know the TCP segment is received at the server hosting the
>>> Asterisk build.
>>>
>>> On Wed, Feb 17, 2016 at 8:36 AM, A J Stiles <
>>> asterisk_l...@earthshod.co.uk> wrote:
>>>
 On Wednesday 17 Feb 2016, Sonny Rajagopalan wrote:
 > OK. Let me ask this. Is anything else necessary, except choosing TCP
 as the
 > preferred protocol on the client, to make TCP w Asterisk work? At the
 > moment, I have only changed one line in pjsip.conf from my working UDP
 > setup:
 >
 > [transport-tcp]
 > type=transport
 > protocol=tcp ; <--- only this line was changed.

 Presumably you have firewall rules in action. Did you enable TCP on
 port 5060?

 --
 AJS

 Note:  Originating address only accepts e-mail from list!  If replying
 off-
 list, change address to asterisk1list at earthshod dot co dot uk .

 --
 _
 -- 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

>>>
>>>
>>
>> --
>> _
>> -- 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
>>
>
>
> --
> _
> -- 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
>
--

Re: [asterisk-users] Asterisk 13.6.0/The simplest TCP configuration does not work

2016-02-17 Thread George Joseph 
On Wed, Feb 17, 2016 at 8:56 AM, Sonny Rajagopalan <
sonny.rajagopa...@gmail.com> wrote:

> I made some progress. The first thing I have realized is that it is my
> Twilio configuration in pjsip_wizard.conf that was killing me. I have since
> removed that entire file from /etc/asterisk and I am able to make
> "from-internal" context calls (i.e., calls that do not leave the VoIP
> island).
>
> Here's what I have right now in pjsip_wizard.conf (again, I have removed
> it from /etc/asterisk/ because Asterisk won't even work for "from-internal"
> calls with the conf in /etc/asterisk)
>
> [twilio-siptrunk]
> type = wizard
> sends_auth = yes
> sends_registrations = no
> remote_hosts = silly.pstn.twilio.com
>

remote_hosts = silly.pstn.twilio.com
​\;transport=TCP​


outbound_auth/username = username
> outbound_auth/password = sillypassword
> endpoint/context = from-external ;;; change later
> endpoint/disallow = all ;;; change later
> endpoint/allow = ulaw ;;; change later
> aor/qualify_frequency = 15
>
> What should I change/add/modify above to make Asterisk and Twilio work
> with TCP? Note that I do not have to trigger a use of the twilio sip trunk
> for my Asterisk daemon to not work for TCP. If I have the pjsip_wizard in
> /etc/asterisk, it does not work for _any_ call, regardless of whether or
> not the call should use the Twilio SIP trunk.
>
> (again, the same asterisk configuration on the same machine connected to
> the same twilio SIP trunk worked for UDP)
>
> If anyone knows the trick to make pjsip_wizard.conf work with twilio, I
> would very much appreciate any insight...
>
> Thanks,
> Sonny.
>
> On Wed, Feb 17, 2016 at 8:38 AM, Sonny Rajagopalan <
> sonny.rajagopa...@gmail.com> wrote:
>
>> Yes, it is enabled on port 5060. I do receive a TCP ACK back from the
>> server, so I know the TCP segment is received at the server hosting the
>> Asterisk build.
>>
>> On Wed, Feb 17, 2016 at 8:36 AM, A J Stiles <
>> asterisk_l...@earthshod.co.uk> wrote:
>>
>>> On Wednesday 17 Feb 2016, Sonny Rajagopalan wrote:
>>> > OK. Let me ask this. Is anything else necessary, except choosing TCP
>>> as the
>>> > preferred protocol on the client, to make TCP w Asterisk work? At the
>>> > moment, I have only changed one line in pjsip.conf from my working UDP
>>> > setup:
>>> >
>>> > [transport-tcp]
>>> > type=transport
>>> > protocol=tcp ; <--- only this line was changed.
>>>
>>> Presumably you have firewall rules in action. Did you enable TCP on port
>>> 5060?
>>>
>>> --
>>> AJS
>>>
>>> Note:  Originating address only accepts e-mail from list!  If replying
>>> off-
>>> list, change address to asterisk1list at earthshod dot co dot uk .
>>>
>>> --
>>> _
>>> -- 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
>>>
>>
>>
>
> --
> _
> -- 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
>
-- 
_
-- 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

Re: [asterisk-users] Asterisk 13.6.0/The simplest TCP configuration does not work

2016-02-17 Thread Sonny Rajagopalan 
I made some progress. The first thing I have realized is that it is my
Twilio configuration in pjsip_wizard.conf that was killing me. I have since
removed that entire file from /etc/asterisk and I am able to make
"from-internal" context calls (i.e., calls that do not leave the VoIP
island).

Here's what I have right now in pjsip_wizard.conf (again, I have removed it
from /etc/asterisk/ because Asterisk won't even work for "from-internal"
calls with the conf in /etc/asterisk)

[twilio-siptrunk]
type = wizard
sends_auth = yes
sends_registrations = no
remote_hosts = silly.pstn.twilio.com
outbound_auth/username = username
outbound_auth/password = sillypassword
endpoint/context = from-external ;;; change later
endpoint/disallow = all ;;; change later
endpoint/allow = ulaw ;;; change later
aor/qualify_frequency = 15

What should I change/add/modify above to make Asterisk and Twilio work with
TCP? Note that I do not have to trigger a use of the twilio sip trunk for
my Asterisk daemon to not work for TCP. If I have the pjsip_wizard in
/etc/asterisk, it does not work for _any_ call, regardless of whether or
not the call should use the Twilio SIP trunk.

(again, the same asterisk configuration on the same machine connected to
the same twilio SIP trunk worked for UDP)

If anyone knows the trick to make pjsip_wizard.conf work with twilio, I
would very much appreciate any insight...

Thanks,
Sonny.

On Wed, Feb 17, 2016 at 8:38 AM, Sonny Rajagopalan <
sonny.rajagopa...@gmail.com> wrote:

> Yes, it is enabled on port 5060. I do receive a TCP ACK back from the
> server, so I know the TCP segment is received at the server hosting the
> Asterisk build.
>
> On Wed, Feb 17, 2016 at 8:36 AM, A J Stiles  > wrote:
>
>> On Wednesday 17 Feb 2016, Sonny Rajagopalan wrote:
>> > OK. Let me ask this. Is anything else necessary, except choosing TCP as
>> the
>> > preferred protocol on the client, to make TCP w Asterisk work? At the
>> > moment, I have only changed one line in pjsip.conf from my working UDP
>> > setup:
>> >
>> > [transport-tcp]
>> > type=transport
>> > protocol=tcp ; <--- only this line was changed.
>>
>> Presumably you have firewall rules in action. Did you enable TCP on port
>> 5060?
>>
>> --
>> AJS
>>
>> Note:  Originating address only accepts e-mail from list!  If replying
>> off-
>> list, change address to asterisk1list at earthshod dot co dot uk .
>>
>> --
>> _
>> -- 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
>>
>
>
-- 
_
-- 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

Re: [asterisk-users] Asterisk 13.6.0/The simplest TCP configuration does not work

2016-02-17 Thread Sonny Rajagopalan 
Yes, it is enabled on port 5060. I do receive a TCP ACK back from the
server, so I know the TCP segment is received at the server hosting the
Asterisk build.

On Wed, Feb 17, 2016 at 8:36 AM, A J Stiles 
wrote:

> On Wednesday 17 Feb 2016, Sonny Rajagopalan wrote:
> > OK. Let me ask this. Is anything else necessary, except choosing TCP as
> the
> > preferred protocol on the client, to make TCP w Asterisk work? At the
> > moment, I have only changed one line in pjsip.conf from my working UDP
> > setup:
> >
> > [transport-tcp]
> > type=transport
> > protocol=tcp ; <--- only this line was changed.
>
> Presumably you have firewall rules in action. Did you enable TCP on port
> 5060?
>
> --
> AJS
>
> Note:  Originating address only accepts e-mail from list!  If replying off-
> list, change address to asterisk1list at earthshod dot co dot uk .
>
> --
> _
> -- 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
>
-- 
_
-- 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

Re: [asterisk-users] Asterisk 13.6.0/The simplest TCP configuration does not work

2016-02-17 Thread A J Stiles 
On Wednesday 17 Feb 2016, Sonny Rajagopalan wrote:
> OK. Let me ask this. Is anything else necessary, except choosing TCP as the
> preferred protocol on the client, to make TCP w Asterisk work? At the
> moment, I have only changed one line in pjsip.conf from my working UDP
> setup:
> 
> [transport-tcp]
> type=transport
> protocol=tcp ; <--- only this line was changed.

Presumably you have firewall rules in action. Did you enable TCP on port 5060?

-- 
AJS

Note:  Originating address only accepts e-mail from list!  If replying off-
list, change address to asterisk1list at earthshod dot co dot uk .

-- 
_
-- 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

Re: [asterisk-users] Asterisk 13.6.0/The simplest TCP configuration does not work

2016-02-17 Thread Joshua Colp 

Sonny Rajagopalan wrote:

OK. Let me ask this. Is anything else necessary, except choosing TCP as
the preferred protocol on the client, to make TCP w Asterisk work? At
the moment, I have only changed one line in pjsip.conf from my working
UDP setup:

[transport-tcp]
type=transport
protocol=tcp ; <--- only this line was changed.


No, nothing else is needed.

--
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

Re: [asterisk-users] Asterisk 13.6.0/The simplest TCP configuration does not work

2016-02-17 Thread Sonny Rajagopalan 
OK. Let me ask this. Is anything else necessary, except choosing TCP as the
preferred protocol on the client, to make TCP w Asterisk work? At the
moment, I have only changed one line in pjsip.conf from my working UDP
setup:

[transport-tcp]
type=transport
protocol=tcp ; <--- only this line was changed.

On Wed, Feb 17, 2016 at 8:28 AM, Sonny Rajagopalan <
sonny.rajagopa...@gmail.com> wrote:

> OK. I will report with my findings. It appears increasingly likely that I
> have done something very silly on my side. It is a little perplexing that
> the EXACT setup (on the same machine) worked for UDP ...
>
> On Wed, Feb 17, 2016 at 8:23 AM, Joshua Colp  wrote:
>
>> 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
>>
>>
>> --
>> _
>> -- 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
>>
>
>
-- 
_
-- 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

Re: [asterisk-users] Asterisk 13.6.0/The simplest TCP configuration does not work

2016-02-17 Thread Sonny Rajagopalan 
OK. I will report with my findings. It appears increasingly likely that I
have done something very silly on my side. It is a little perplexing that
the EXACT setup (on the same machine) worked for UDP ...

On Wed, Feb 17, 2016 at 8:23 AM, Joshua Colp  wrote:

> 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
>
>
> --
> _
> -- 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
>
-- 
_
-- 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

Re: [asterisk-users] Asterisk 13.6.0/The simplest TCP configuration does not work

2016-02-17 Thread Joshua Colp 

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


--
_
-- 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

Re: [asterisk-users] Asterisk 13.6.0/The simplest TCP configuration does not work

2016-02-17 Thread Sonny Rajagopalan 
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  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:
>>
>> tcp0  0 0.0.0.0:8088 
>>   0.0.0.0:*   LISTEN  10313/asterisk
>> tcp0  0 0.0.0.0:5060 
>>   0.0.0.0:*   LISTEN  10313/asterisk
>> tcp0  0 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
>
-- 
_
-- 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

Re: [asterisk-users] Asterisk 13.6.0/The simplest TCP configuration does not work

2016-02-17 Thread Joshua Colp 

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:

tcp0  0 0.0.0.0:8088 
  0.0.0.0:*   LISTEN  10313/asterisk
tcp0  0 0.0.0.0:5060 
  0.0.0.0:*   LISTEN  10313/asterisk
tcp0  0 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

Re: [asterisk-users] Asterisk 13.6.0/The simplest TCP configuration does not work

2016-02-17 Thread Sonny Rajagopalan 
Is there a specific place where I can set logger to log incoming TCP
segments from L4?

$ netstat -tulpn | grep asterisk | grep LISTEN:

tcp0  0 0.0.0.0:80880.0.0.0:*   LISTEN
 10313/asterisk
tcp0  0 0.0.0.0:50600.0.0.0:*   LISTEN
 10313/asterisk
tcp0  0 0.0.0.0:20000.0.0.0:*   LISTEN
 10313/asterisk

On Wed, Feb 17, 2016 at 7:57 AM, Joshua Colp  wrote:

> Sonny Rajagopalan wrote:
>
>> I receive a TCP ack back from that port (5060; owned by Asterisk)
>> --confirmed by wireshark on the Asterisk server.
>>
>
> That's from Wireshark, but what is Asterisk seeing? If Asterisk doesn't
> show the connection or the traffic then something else is up (firewall,
> etc). Try to isolate things further, start from Asterisk itself.
>
>
> --
> 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
>
-- 
_
-- 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

Re: [asterisk-users] Asterisk 13.6.0/The simplest TCP configuration does not work

2016-02-17 Thread Joshua Colp 

Sonny Rajagopalan wrote:

I receive a TCP ack back from that port (5060; owned by Asterisk)
--confirmed by wireshark on the Asterisk server.


That's from Wireshark, but what is Asterisk seeing? If Asterisk doesn't 
show the connection or the traffic then something else is up (firewall, 
etc). Try to isolate things further, start from Asterisk itself.


--
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

Re: [asterisk-users] Asterisk 13.6.0/The simplest TCP configuration does not work

2016-02-17 Thread Sonny Rajagopalan 
I receive a TCP ack back from that port (5060; owned by Asterisk)
--confirmed by wireshark on the Asterisk server.

What else should I be looking for? This is on a machine on AWS that was
running a UDP based Asterisk  fine (I did not make ANY other change other
than changing protocol=tcp). I also tried a fresh build with protocol=tcp.
Did not work.

On Wed, Feb 17, 2016 at 6:35 AM, Joshua Colp  wrote:

> Sonny Rajagopalan wrote:
>
>> I can confirm that the server is receiving the SIP request, but simply
>> doesn't do anything with it (log from the server below). Does this have
>> anything to do with how PJSIP was compiled or configured?:
>>
>
> TCP support is enabled in PJSIP by default. If you do "pjsip set logger
> on" does the message show up? What is the COMPLETE console output when a
> client connects? We have tests which cover TCP and they are working, so
> it's likely something environment specific.
>
>
> --
> 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
>
-- 
_
-- 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

Re: [asterisk-users] Asterisk 13.6.0/The simplest TCP configuration does not work

2016-02-17 Thread Joshua Colp 

Sonny Rajagopalan wrote:

I can confirm that the server is receiving the SIP request, but simply
doesn't do anything with it (log from the server below). Does this have
anything to do with how PJSIP was compiled or configured?:


TCP support is enabled in PJSIP by default. If you do "pjsip set logger 
on" does the message show up? What is the COMPLETE console output when a 
client connects? We have tests which cover TCP and they are working, so 
it's likely something environment specific.


--
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

Re: [asterisk-users] Asterisk 13.6.0/The simplest TCP configuration does not work

2016-02-16 Thread Sonny Rajagopalan 
I can confirm that the server is receiving the SIP request, but simply
doesn't do anything with it (log from the server below). Does this have
anything to do with how PJSIP was compiled or configured?:

Session Initiation Protocol (REGISTER)
Request-Line: REGISTER sip:11.12.13.14 SIP/2.0
Method: REGISTER
Request-URI: sip:11.12.13.14
Request-URI Host Part: 11.12.13.14
[Resent Packet: False]
Message Header
Via: SIP/2.0/TCP 192.168.1.16:54402
;rport;branch=z9hG4bKPjpaCDxnhZT22z-O183o5uZzMHNwTNrpkl;alias
Transport: TCP
Sent-by Address: 192.168.1.16
Sent-by port: 54402
RPort: rport
Branch: z9hG4bKPjpaCDxnhZT22z-O183o5uZzMHNwTNrpkl
alias
Route: 
Route URI: sip:11.12.13.14;transport=tcp;lr
Route Host Part: 11.12.13.14
Route URI parameter: transport=tcp
Route URI parameter: lr
Max-Forwards: 70
From: ;tag=Qb12fSdMpSBV4YJ2e4LGtM3biO.rPtcQ
SIP from address: sip:987654321@11.12.13.14
SIP from address User Part: 987654321
SIP from address Host Part: 11.12.13.14
SIP from tag: Qb12fSdMpSBV4YJ2e4LGtM3biO.rPtcQ
To: 
SIP to address: sip:987654321@11.12.13.14
SIP to address User Part: 987654321
SIP to address Host Part: 11.12.13.14
Call-ID: 8NDmEFaT2lmQRMUBf77UrRKRBIc3cT0h
CSeq: 29457 REGISTER
Sequence Number: 29457
Method: REGISTER
Supported: outbound, path
Contact: ;reg-id=1;+sip.instance=""
Contact URI: sip:987654321@192.168.1.16:54402;transport=TCP;ob
Contact URI User Part: 987654321
Contact URI Host Part: 192.168.1.16
Contact URI Host Port: 54402
Contact URI parameter: transport=TCP
Contact URI parameter: ob
Contact parameter: reg-id=1
Contact parameter:
+sip.instance=""\r\n
Expires: 900
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE,
NOTIFY, REFER, MESSAGE, OPTIONS
Content-Length:  0


On Mon, Feb 15, 2016 at 6:01 PM, Sonny Rajagopalan <
sonny.rajagopa...@gmail.com> wrote:

> Nope, there are no contacts to  show that pertain to these endpoints (only
> my SIP trunks show up).
>
> On Mon, Feb 15, 2016 at 5:31 PM, Joshua Colp  wrote:
>
>> Sonny Rajagopalan wrote:
>>
>>> Does this help:
>>>
>>
>> Yes, the transport parameter is in the Contact header so it's interesting
>> it didn't work. If you use pjsip show contacts what is the contact for the
>> AOR?
>>
>>
>> --
>> 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
>>
>
>
-- 
_
-- 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

Re: [asterisk-users] Asterisk 13.6.0/The simplest TCP configuration does not work

2016-02-15 Thread Sonny Rajagopalan 
Nope, there are no contacts to  show that pertain to these endpoints (only
my SIP trunks show up).

On Mon, Feb 15, 2016 at 5:31 PM, Joshua Colp  wrote:

> Sonny Rajagopalan wrote:
>
>> Does this help:
>>
>
> Yes, the transport parameter is in the Contact header so it's interesting
> it didn't work. If you use pjsip show contacts what is the contact for the
> AOR?
>
>
> --
> 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
>
-- 
_
-- 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

Re: [asterisk-users] Asterisk 13.6.0/The simplest TCP configuration does not work

2016-02-15 Thread Sonny Rajagopalan 
Does this help:

Session Initiation Protocol (REGISTER)
Request-Line: REGISTER sip:1.2.3.4;transport=TCP SIP/2.0
Method: REGISTER
Request-URI: sip:1.2.3.4;transport=TCP
Request-URI Host Part: 1.2.3.4
[Resent Packet: False]
Message Header
Via: SIP/2.0/TCP 192.168.1.15:47053
;branch=z9hG4bK-d8754z-5e3d9f441f1de1d3-1---d8754z-;rport;transport=TCP
Transport: TCP
Sent-by Address: 192.168.1.15
Sent-by port: 47053
Branch: z9hG4bK-d8754z-5e3d9f441f1de1d3-1---d8754z-
RPort: rport
transport=TCP
Max-Forwards: 70
Contact: 
Contact URI: sip:5678@192.168.1.15:47053
;rinstance=bea6f11f37c55605;transport=TCP
Contact URI User Part: 5678
Contact URI Host Part: 192.168.1.15
Contact URI Host Port: 47053
Contact URI parameter: rinstance=bea6f11f37c55605
Contact URI parameter: transport=TCP
To: 
SIP to address: sip:5678@1.2.3.4;transport=TCP
SIP to address User Part: 5678
SIP to address Host Part: 1.2.3.4
SIP To URI parameter: transport=TCP
From: ;tag=fc31c046
SIP from address: sip:5678@1.2.3.4;transport=TCP
SIP from address User Part: 5678
SIP from address Host Part: 1.2.3.4
SIP From URI parameter: transport=TCP
SIP from tag: fc31c046
Call-ID: ODRiMjBhNGY5MWJjMDFkNjk4MzRhYzg1ZTE3ZWM3Y2M.
CSeq: 1 REGISTER
Sequence Number: 1
Method: REGISTER
Expires: 70
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS,
INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, timer,
X-cisco-serviceuri
User-Agent: Z 3.3.25608 r25552
Allow-Events: presence, kpml
Content-Length: 0


On Mon, Feb 15, 2016 at 2:53 PM, Joshua Colp  wrote:

> Sonny Rajagopalan wrote:
>
>> Thanks for the mighty quick response, Joshua!
>>
>> I am using Zoiper on Linux softclient:
>> REGISTER sip:;transport=TCP SIP/2.0
>>
>
> That's the request URI, not the Contact header. The Contact contains the
> URI that the server should dial to reach the client. The full message would
> be useful.
>
> Cheers,
>
>
> --
> 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
>
-- 
_
-- 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

Re: [asterisk-users] Asterisk 13.6.0/The simplest TCP configuration does not work

2016-02-15 Thread Joshua Colp 

Sonny Rajagopalan wrote:

Does this help:


Yes, the transport parameter is in the Contact header so it's 
interesting it didn't work. If you use pjsip show contacts what is the 
contact for the AOR?


--
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

Re: [asterisk-users] Asterisk 13.6.0/The simplest TCP configuration does not work

2016-02-15 Thread Joshua Colp 

Sonny Rajagopalan wrote:

Thanks for the mighty quick response, Joshua!

I am using Zoiper on Linux softclient:
REGISTER sip:;transport=TCP SIP/2.0


That's the request URI, not the Contact header. The Contact contains the 
URI that the server should dial to reach the client. The full message 
would be useful.


Cheers,

--
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

Re: [asterisk-users] Asterisk 13.6.0/The simplest TCP configuration does not work

2016-02-15 Thread Sonny Rajagopalan 
Thanks for the mighty quick response, Joshua!

I am using Zoiper on Linux softclient:
REGISTER sip:;transport=TCP SIP/2.0

Changed the port back to 5060.


On Mon, Feb 15, 2016 at 1:40 PM, Joshua Colp  wrote:

> Sonny Rajagopalan wrote:
>
> 
>
>
> *CLI> pjsip set logger on
>> PJSIP Logging enabled
>> [Feb 15 18:28:12] WARNING[30075]: pjsip:0 : tsx0x7f14b0003 .Temporary
>> failure in sending Request msg OPTIONS/cseq=52002 (tdta0x7f14b0001470),
>> will try next server: Unsupported transport (PJSIP_EUNSUPTRANSPORT)
>> [Feb 15 18:28:12] WARNING[30075]: pjsip:0 : tsx0x7f14b0003 .Temporary
>> failure in sending Request msg OPTIONS/cseq=52002 (tdta0x7f14b0001470),
>> will try next server: Unsupported transport (PJSIP_EUNSUPTRANSPORT)
>> [Feb 15 18:28:12] WARNING[30075]: pjsip:0 : tsx0x7f14b0003 .Temporary
>> failure in sending Request msg OPTIONS/cseq=52002 (tdta0x7f14b0001470),
>> will try next server: Unsupported transport (PJSIP_EUNSUPTRANSPORT)
>> [Feb 15 18:28:12] WARNING[30075]: pjsip:0 : tsx0x7f14b0003 .Failed to
>> send Request msg OPTIONS/cseq=52002 (tdta0x7f14b0001470)! err=171060
>> (Unsupported transport (PJSIP_EUNSUPTRANSPORT))
>> *CLI> core set debug 99
>> Core debug was OFF and is now 99.
>> [Feb 15 18:28:27] WARNING[30133]: pjsip:0 : tsx0x7f14b4003 .Temporary
>> failure in sending Request msg OPTIONS/cseq=49786 (tdta0x7f14b40014f0),
>> will try next server: Unsupported transport (PJSIP_EUNSUPTRANSPORT)
>> [Feb 15 18:28:27] WARNING[30133]: pjsip:0 : tsx0x7f14b4003 .Temporary
>> failure in sending Request msg OPTIONS/cseq=49786 (tdta0x7f14b40014f0),
>> will try next server: Unsupported transport (PJSIP_EUNSUPTRANSPORT)
>> [Feb 15 18:28:27] WARNING[30133]: pjsip:0 : tsx0x7f14b4003 .Temporary
>> failure in sending Request msg OPTIONS/cseq=49786 (tdta0x7f14b40014f0),
>> will try next server: Unsupported transport (PJSIP_EUNSUPTRANSPORT)
>> [Feb 15 18:28:27] WARNING[30133]: pjsip:0 : tsx0x7f14b4003 .Failed to
>> send Request msg OPTIONS/cseq=49786 (tdta0x7f14b40014f0)! err=171060
>> (Unsupported transport (PJSIP_EUNSUPTRANSPORT))
>>
>
> This will happen if the URI added does not contain ;transport=tcp which
> informs things to use TCP. If the device registering doesn't do this then
> it will try to use a UDP transport instead, if not available then it will
> fail.
>
> What is the REGISTER from the device?
>
> --
> 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
>
-- 
_
-- 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

Re: [asterisk-users] Asterisk 13.6.0/The simplest TCP configuration does not work

2016-02-15 Thread Joshua Colp 

Sonny Rajagopalan wrote:




*CLI> pjsip set logger on
PJSIP Logging enabled
[Feb 15 18:28:12] WARNING[30075]: pjsip:0 : tsx0x7f14b0003 .Temporary
failure in sending Request msg OPTIONS/cseq=52002 (tdta0x7f14b0001470),
will try next server: Unsupported transport (PJSIP_EUNSUPTRANSPORT)
[Feb 15 18:28:12] WARNING[30075]: pjsip:0 : tsx0x7f14b0003 .Temporary
failure in sending Request msg OPTIONS/cseq=52002 (tdta0x7f14b0001470),
will try next server: Unsupported transport (PJSIP_EUNSUPTRANSPORT)
[Feb 15 18:28:12] WARNING[30075]: pjsip:0 : tsx0x7f14b0003 .Temporary
failure in sending Request msg OPTIONS/cseq=52002 (tdta0x7f14b0001470),
will try next server: Unsupported transport (PJSIP_EUNSUPTRANSPORT)
[Feb 15 18:28:12] WARNING[30075]: pjsip:0 : tsx0x7f14b0003 .Failed to
send Request msg OPTIONS/cseq=52002 (tdta0x7f14b0001470)! err=171060
(Unsupported transport (PJSIP_EUNSUPTRANSPORT))
*CLI> core set debug 99
Core debug was OFF and is now 99.
[Feb 15 18:28:27] WARNING[30133]: pjsip:0 : tsx0x7f14b4003 .Temporary
failure in sending Request msg OPTIONS/cseq=49786 (tdta0x7f14b40014f0),
will try next server: Unsupported transport (PJSIP_EUNSUPTRANSPORT)
[Feb 15 18:28:27] WARNING[30133]: pjsip:0 : tsx0x7f14b4003 .Temporary
failure in sending Request msg OPTIONS/cseq=49786 (tdta0x7f14b40014f0),
will try next server: Unsupported transport (PJSIP_EUNSUPTRANSPORT)
[Feb 15 18:28:27] WARNING[30133]: pjsip:0 : tsx0x7f14b4003 .Temporary
failure in sending Request msg OPTIONS/cseq=49786 (tdta0x7f14b40014f0),
will try next server: Unsupported transport (PJSIP_EUNSUPTRANSPORT)
[Feb 15 18:28:27] WARNING[30133]: pjsip:0 : tsx0x7f14b4003 .Failed to
send Request msg OPTIONS/cseq=49786 (tdta0x7f14b40014f0)! err=171060
(Unsupported transport (PJSIP_EUNSUPTRANSPORT))


This will happen if the URI added does not contain ;transport=tcp which 
informs things to use TCP. If the device registering doesn't do this 
then it will try to use a UDP transport instead, if not available then 
it will fail.


What is the REGISTER from the device?

--
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

[asterisk-users] Asterisk 13.6.0/The simplest TCP configuration does not work

2016-02-15 Thread Sonny Rajagopalan 
This question was asked by Chirag on March 4 2015 earlier, but I am
following exactly the same procedure here and I cannot even get my clients
to register on Asterisk.

Here's my PJSIP.conf:

[transport-tcp]
type=transport
protocol=tcp
bind=0.0.0.0:5061
...

[endpoint_internal](!)
type=endpoint
context=from-internal
disallow=all
allow=!all,ulaw
direct_media=no
rtp_symmetric=yes
message_context=text-context

[auth_userpass](!)
type=auth
auth_type=userpass

[aor_dynamic](!)
type=aor
max_contacts=1
remove_existing=yes

;;; Configuration for user 
...

I used basically exactly the same procedure for UDP based registration and
it works just fine.

Any help is appreciated. The specific error I see on the CLI is:

Connected to Asterisk 13.6.0 currently running on ... (pid = 30046)
*CLI> pjsip set logger on
PJSIP Logging enabled
[Feb 15 18:28:12] WARNING[30075]: pjsip:0 : tsx0x7f14b0003 .Temporary
failure in sending Request msg OPTIONS/cseq=52002 (tdta0x7f14b0001470),
will try next server: Unsupported transport (PJSIP_EUNSUPTRANSPORT)
[Feb 15 18:28:12] WARNING[30075]: pjsip:0 : tsx0x7f14b0003 .Temporary
failure in sending Request msg OPTIONS/cseq=52002 (tdta0x7f14b0001470),
will try next server: Unsupported transport (PJSIP_EUNSUPTRANSPORT)
[Feb 15 18:28:12] WARNING[30075]: pjsip:0 : tsx0x7f14b0003 .Temporary
failure in sending Request msg OPTIONS/cseq=52002 (tdta0x7f14b0001470),
will try next server: Unsupported transport (PJSIP_EUNSUPTRANSPORT)
[Feb 15 18:28:12] WARNING[30075]: pjsip:0 : tsx0x7f14b0003 .Failed to
send Request msg OPTIONS/cseq=52002 (tdta0x7f14b0001470)! err=171060
(Unsupported transport (PJSIP_EUNSUPTRANSPORT))
*CLI> core set debug 99
Core debug was OFF and is now 99.
[Feb 15 18:28:27] WARNING[30133]: pjsip:0 : tsx0x7f14b4003 .Temporary
failure in sending Request msg OPTIONS/cseq=49786 (tdta0x7f14b40014f0),
will try next server: Unsupported transport (PJSIP_EUNSUPTRANSPORT)
[Feb 15 18:28:27] WARNING[30133]: pjsip:0 : tsx0x7f14b4003 .Temporary
failure in sending Request msg OPTIONS/cseq=49786 (tdta0x7f14b40014f0),
will try next server: Unsupported transport (PJSIP_EUNSUPTRANSPORT)
[Feb 15 18:28:27] WARNING[30133]: pjsip:0 : tsx0x7f14b4003 .Temporary
failure in sending Request msg OPTIONS/cseq=49786 (tdta0x7f14b40014f0),
will try next server: Unsupported transport (PJSIP_EUNSUPTRANSPORT)
[Feb 15 18:28:27] WARNING[30133]: pjsip:0 : tsx0x7f14b4003 .Failed to
send Request msg OPTIONS/cseq=49786 (tdta0x7f14b40014f0)! err=171060
(Unsupported transport (PJSIP_EUNSUPTRANSPORT))
-- 
_
-- 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