[asterisk-bugs] [Asterisk 0012504]: Changing port number on SIP trunk is not reflected in Asterisk

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12504 
====================================================================== 
Reported By:                voiptel
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12504
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.18 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             04-23-2008 09:42 CDT
Last Modified:              04-30-2008 12:04 CDT
====================================================================== 
Summary:                    Changing port number on SIP trunk is not reflected
in Asterisk
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.
====================================================================== 

---------------------------------------------------------------------- 
 voiptel - 04-30-08 12:04  
---------------------------------------------------------------------- 
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? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-30-08 12:04  voiptel        Note Added: 0086225                          
======================================================================