SIP On Multiple Ports

Home » Asterisk Users » SIP On Multiple Ports
Asterisk Users 2 Comments

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

2 thoughts on - SIP On Multiple Ports

  • over TCP, not UDP. header rewrite rules (10.201, or 1.3?).

    to focus on creating the correct Asterisk peer configuration for the peer packet-header mangling at all.

    sip.conf)

    Hi 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 host2.168.1.3
    ;portP68
    canreinvite=yes qualify=yes transport=tcp

    I have tried it with or without the portP68.

    Jerry

  • –Apple-Mail=_27393A8E-F4D8-41E3-9096-142FEF041A41
    Content-Transfer-Encoding: quoted-printable Content-Type: text/plain;
    charset=us-ascii

    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
    –Apple-Mail=_27393A8E-F4D8-41E3-9096-142FEF041A41
    Content-Transfer-Encoding: quoted-printable Content-Type: text/html;
    charset=us-ascii

    On 18/10/2016, at 12:30 am, Jerry Geis <geisj@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


    –Apple-Mail=_27393A8E-F4D8-41E3-9096-142FEF041A41