Please disregard.
I just found my problem. In my sip.conf, I had an include statement for another
file at the top. The included file also had a general section. Once I deleted
that general section and reloaded everything worked as expected, now using port
5061.
From: asterisk-users <asterisk-users-bounces at lists.digium.com> On
Behalf Of Dan Cropp
Sent: Friday, January 11, 2019 11:54 AM
To: asterisk-users at lists.digium.com
Subject: [asterisk-users] chan_sip bind port
Did something recently change for the chan_sip bindport setting?
I know I had this working with the previous version of asterisk. Can't
remember if it was an earlier 16.x version or 13.x
I was running chan_sip (binding to port 5061) and PJSIP using the default port
of 5060.
I recently upgraded to asterisk 16.1.1 and don't recall changing anything
specific for the sip.conf
My sip.conf ...
[general]
context = ABC
bindaddr = 0.0.0.0
bindport = 5061
websocket_enabled = false
srvlookup = no
sipdebug = yes
callcounter = yes
My pjsip.conf transports...
[transport1]
type = transport
bind = 0.0.0.0
protocol = udp
[transport2]
type = transport
bind = 0.0.0.0
protocol = wss
Every time I start up, asterisk logging is showing the following, as if it's
not reading in the bindport setting.
[01/11 09:43:51.059] WARNING[1658] chan_sip.c: Failed to bind to 0.0.0.0:5060:
Address already in use
Any thoughts?
Dan
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20190111/32092f22/attachment.html>