Bug 118742

Summary: configuration with 2 area codes ignored
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Per Jessen <per>
Component: ISDNAssignee: Karsten Keil <karsten.keil>
Status: RESOLVED WORKSFORME QA Contact: E-mail List <qa-bugs>
Severity: Enhancement    
Priority: P5 - None    
Version: RC 1   
Target Milestone: ---   
Hardware: i686   
OS: All   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Per Jessen 2005-09-25 18:18:14 UTC 
During installation I configured my two ISDN TAs with each their areacode - 43
and 44.  This was however ignored by th isdnlog configuration.  I reported this
problem to the isdn4linux project last year - December I think it was, and AFAIR
it was fixed in CVS then.
Comment 1 Per Jessen 2005-09-26 11:09:21 UTC 
It looks like the isdnlog version is actually happy with my manual
configuration, so it's just YaST that didn't do the configuration correct.
Comment 2 Karsten Keil 2005-09-26 13:43:38 UTC 
No yast fully support this, it writes the correct values in the config files, 
it only suggests the first entered value for every next configured controller 
and this value can be edited. 
files are /etc/sysconfig/isdn/cfg-contrX). 
The reason that this is still not working is, that we do not support multiple 
/etc/isdn/isdn.conf files for different isdnlog processes. so the areacode is 
still a global value for isdnlog. I'm not sure if we should change that, it's 
not very common you need different areacodes. 
 
I also do not remember how isdnlog will handle this, so please write a few 
words, what are your manual changes.
Comment 3 Per Jessen 2005-09-26 14:27:28 UTC 
I edited isdnlog.options.contrX to add lines containing:

[options]
AREACODE = xx 

I just added them at the top of file.
Comment 4 Karsten Keil 2007-02-22 18:18:08 UTC 
We do not support multiple areacodes with yast, but as you say, it's still possible to edit the config manually.