I have SIP (asterisk 11.23.0) running on port 5060 just fine. udp. I have another SIP trunk thats wants to run on port 5068 (long story). I have enabled tcpenable=yes in sip.conf and defined port=5068 in my trunk definition. It does not seem that anything is listening on 5068? How can I run SIP tcp on port 5068? telnet localhost 5068 Trying 127.0.0.1... telnet: connect to address 127.0.0.1: Connection refused telnet: Unable to connect to remote host: Connection refused My firewall is set to allow TCP port 5068. Thanks, Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20161015/a5b9daf8/attachment.html>
>Jerry has already clarified in a previous reply that he is running SIPover TCP, not UDP.>But he hasn't clarified on which machine he is applying the iptablesheader rewrite rules (10.201, or 1.3?).>Either way though, it seems like a kludgy work-around. IMO, it'd be betterto focus on creating the correct Asterisk peer configuration for the peer>that is operating on the non-standard separate port, and don't use anypacket-header mangling at all.>Jerry, can you post your configuration for the peer in Asterisk? (eg fromsip.conf)>PeteHi Pete, I am running iptables on the 10.201 machine. I have not control over the other machine. It is a microsoft lync product. my definition... [MyTrunk] type=friend dtmfmode=rfc2833 disallow=all allow=ulaw allow=alaw context=my-incoming host=192.168.1.3 ;port=5068 canreinvite=yes qualify=yes transport=tcp I have tried it with or without the port=5068. Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20161017/bc27f5c9/attachment.html>
> On 18/10/2016, at 12:30 am, Jerry Geis <geisj at pagestation.com> wrote: > > I am running iptables on the 10.201 machine. I have not control over the other machine. It is a microsoft lync product. > > my definition... > [MyTrunk] > type=friend > dtmfmode=rfc2833 > disallow=all > allow=ulaw > allow=alaw > context=my-incoming > host=192.168.1.3 > ;port=5068 > canreinvite=yes > qualify=yes > transport=tcp > > I have tried it with or without the port=5068.Heya Jerry With port=5068 and transport=tcp both defined, do calls outbound to the Lync device fail, or is it just registrations FROM it that are failing? I seem to recall you mentioning it's registrations that aren't working. However for those to work you would need your Asterisk on 10.201 to also be listening for registrations via TCP, and on port 5068. I'm thinking this would be a global configuration definition, not a peer-specific definition. Others may be able to chime in with the specific options required... Pete -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20161018/0b2dae5a/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3577 bytes Desc: not available URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20161018/0b2dae5a/attachment.bin>