[asterisk-bugs] [Asterisk 0010907]: "port" configuration parameter conflicts with runtime status

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10907 
====================================================================== 
Reported By:                dimas
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10907
Category:                   PBX/pbx_realtime
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.11  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             10-06-2007 14:53 CDT
Last Modified:              10-06-2007 16:58 CDT
====================================================================== 
Summary:                    "port" configuration parameter conflicts with
runtime status
Description: 
When IAX/SIP updates realtime database on peer registration etc, it updates
(among others) "ipaddr" and "host" columns. The problem is that "port" is 
also an input parameter for peer configuration.

Why this is a problem:

1. It is just not good that one of important peer configuration parameters
gets overwritten with runtime data. As I understand currently it is not a
problem but what if in the future, "input" port parameter will allow
specifying multiple ports or name instead of value for example? As soon as
channel driver registers the peer and updates realtime, original
configuration value is lost.

2. Realtime behaviour is just inconsistent with what you do with the text
file config. With text files, you can completely omit "port" parameter from
both [general] section and from specific peer sections. This will cause
default port to be used. With realtime, you HAVE TO specify port. Otherwise
default 0/NULL value will be used and nothing will work.

====================================================================== 

---------------------------------------------------------------------- 
 dimas - 10-06-07 16:58  
---------------------------------------------------------------------- 
Oops. Sorry, for lots of typos. Of course, realtime updates (among others)
"ipaddr" and "port" columns, not "ipaddr" and "host".

And small clarification - even if you are using default ports everywhere,
with reltime you have to have "port" column because it is the one that gets
updated.

Alternative solution of separating configuration port and runtime port
would be adding new "ipport" column to pair "ipaddr". Unfortunately this
approach breaks compatibility with already existing databases where putting
addr:port into already existing ipaddr column should not break much. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-06-07 16:58  dimas          Note Added: 0071588                          
======================================================================