Summary:ASTERISK-11901: Changing port number on SIP trunk is not reflected in Asterisk
Reporter:voiptel (voiptel)Labels:
Date Opened:2008-04-23 09:42:22Date Closed:2011-06-07 14:02:50
Versions:Frequency of
Description:Changing the port number from 5060 to anything else (eg. 5061) and reloading Asterisk (in the Advanced settings of the SIP trunk in Service Providers) has no effect on the trunk in Asterisk, even after rebooting. Even manually adding the trunk to the users.conf file with a different port only results in it using port 5060 anyways (according to 'sip show registry').

To further eliminate any other possibilities, I've changed all references to port 5060 in all config files, including the bindport setting, but still it remains locked to 5060.

This bug first appeared in a custom project based on an older version of the Asterisk GUI, and was confirmed to exist in both version 0.9.6 and 1.0.2 of AsteriskNOW.
Comments:By: Brandon Kruse (bkruse) 2008-04-25 12:23:13

How is this a GUI issue?


By: voiptel (voiptel) 2008-04-25 17:07:28

If you feel that it fits better under some other category, please feel free to move it (if possible). However, are you perhaps saying that this is an Asterisk issue?

By: Brandon Kruse (bkruse) 2008-04-28 09:12:34

Moving to Asterisk -> Chan_Sip.

This does not seem like a GUI bug.

By: Olle Johansson (oej) 2008-04-30 10:31:18

If it's not a GUI bug, I need to see SIP conf and SIP debug of this.

By: Olle Johansson (oej) 2008-04-30 10:31:58

Oh, users.conf.
Well, that's an area that is broken...

By: voiptel (voiptel) 2008-04-30 11:00:13

I don't like the sound of that.. :P

Could you please elaborate?

By: Olle Johansson (oej) 2008-04-30 11:21:36

Well, that was my very personal opinion. In an open source project with multiple developers from multiple organizations involved, sometimes we have different opinions on a module, and that's fine. We can't have an agreement on everything in a complex toolkit like Asterisk.

My opinion is that users.conf is a broken concept that doesn't scale properly - there will have to be a lot of work to support all the features in sip.conf, so it's to me just for very basic settings and very basic configurations and something I don't want to spend my own time on. Sorry.

Other developers might just love it and want to fix everything :-)

By: Brandon Kruse (bkruse) 2008-04-30 11:39:32

Try just using sip.conf for the user entry. (The variables are very similar, check out the default config)


By: voiptel (voiptel) 2008-04-30 12:04:29

How about the bug itself, is it a known issue? Any (rough) estimate of when it might be fixed?

I will see what I can do to evade the bug in the meantime.

bkruse: So users.conf is optional in AsteriskNOW?

By: Tilghman Lesher (tilghman) 2008-06-03 17:21:57

voiptel: as oej requested, we need to see a sip debug to continue with this issue.

By: Tilghman Lesher (tilghman) 2008-06-16 11:05:12

Closed, due to failure of reporter to respond with needed information.