Re: Solved! Re: isdn4linux -> dialling uses (my) local area code
>>Are you sure your isdn.conf is read when using >>"isdnctrl dial ippp0"? >Positive. Remove whatever content you are assigning >to AREACODE (i.e. so that the isdn.conf line just reads >AREACODE= >and you should see an error message in the log >(proving that the file is being read - don't forget to >restart the machine, though maybe there is a way to >restart only the isdn subsystem). Ahh, wait, I don't >do a manual "isdnctrl dial ippp0", as I am using the >autodial feature. But still, I think isdn.conf is read >before that? Maybe Paul Slootman could comment. To only restart the isdn system you should look for: "/etc/init.d/isdnutils restart" isdn.conf is read by the isdnlog app which a helpful guy on the de.alt.comm.isdn4linux newsgroup told me. I didn't configure the isdnlog startup yet because I unfortunatly do not know how to, the isdnlog manual reports it should be launched shortly after hisax. In my case it does not. Isdnlog is a separate app which monitors the ISDN connection and seems to have some very helpful features. The program gains the information with the help of the D-channel and therefor needs isdn.conf for its own independant work. I didn't read any further in the manual yet, so I can't tell you more. >Do you see /anything/ in the log? I noticed that the file which my >isdn.conf specifies as the log is not the same as the entry in >isdnlog.isdnctrl0, which I consider odd but since it works as is I'm >not going to touch it. If you don't see anything in the log maybe you >are looking in the wrong place, or do not have isdnlog.isdnctrl0 >setup? This evening I will send the isdnlog setup I have, as I don't >have it to hand at present. I only retrieved the information out of /var/log/messages but I would recommend to read the isdnlog manual (locate isdnlog). If you do not happen to have this, I'll send the files. >>I'm quite sure that only device.ippp0 is read when using isdn4linux >>which comes with potato (I'm just placing a simular question on this >>list). >Which, oddly, I did not see. In fact I notice that I don't see quite >a few messages (I just see replies to them). Is it the list that's >fscked, or this email system? No wonder :-), I sent this inquiry to the mentioned NG instead because I have the impression Debian users are not that familiar with ISDN. Gary, are you using WINE on your system? I made a inquiry on this list refering to a path problem (Subject "path error using wine") but unfortunatly no one responded. Best Regards Robert
Solved! Re: isdn4linux -> dialling uses (my) local area code
At Tue, 12 Dec 2000 14:41:39 +0100 , [EMAIL PROTECTED] (robert_wilhelm_land) wrote: >Gary Jones wrote: > >>Here are the relevant parts of the config files: >>#isdn.conf >>[GLOBAL] >>COUNTRYPREFIX=+ >>AREAPREFIX=0 >>COUNTRYCODE=49 >>AREACODE=89 >> >>#device.ippp0 >>LOCALMSN=089*** >>REMOTEMSN=109000191799 >>LEADINGZERO='' >> >> So the problem is that my ISP, Dog bless them, have a different >> area code to me. There were a couple of problems with this, partly me being blind and stupid, and partly the fact that the ISP were seemingly MIA for at least some of the past few days, when I was trying to troubleshoot. Not very helpful but I switched to my setup to my alternate ISP and all now works :-) The correct setup is: LOCALMSN=*** # where *** is my local number without area code REMOTEMSN='***' # where *** is the ISPs number with area code. the ' # seem to be important, too LEADINGZERO=0 >> What happens is (from isdnlog):- >> Fri Dec 08 18:13:54 outgoing HDLC -> +49 89/109000191799, >> München Unallocated (unassigned) number (Public network serving local user) >> Fri Dec 08 18:13:54 outgoing HDLC -> +49 89/109000191799, >> München HANGUP Unallocated (unassigned) number (Public network serving >> local user) Actually what happens now is that I get a working connection :-) >Gary, how did you get the HDLC-output (by setting a higher debug or >isdnctrl verbose level)? > >Are you sure your isdn.conf is read when using "isdnctrl dial ippp0"? Positive. Remove whatever content you are assigning to AREACODE (i.e. so that the isdn.conf line just reads AREACODE= and you should see an error message in the log (proving that the file is being read - don't forget to restart the machine, though maybe there is a way to restart only the isdn subsystem). Ahh, wait, I don't do a manual "isdnctrl dial ippp0", as I am using the autodial feature. But still, I think isdn.conf is read before that? Maybe Paul Slootman could comment. Do you see /anything/ in the log? I noticed that the file which my isdn.conf specifies as the log is not the same as the entry in isdnlog.isdnctrl0, which I consider odd but since it works as is I'm not going to touch it. If you don't see anything in the log maybe you are looking in the wrong place, or do not have isdnlog.isdnctrl0 setup? This evening I will send the isdnlog setup I have, as I don't have it to hand at present. >I'm quite sure that only device.ippp0 is read when using isdn4linux >which comes with potato (I'm just placing a simular question on this >list). Which, oddly, I did not see. In fact I notice that I don't see quite a few messages (I just see replies to them). Is it the list that's fscked, or this email system? Get your own FREE E-mail address at http://www.linuxfreemail.com Linux FREE Mail is 100% FREE, 100% Linux, and 100% yours!
Re: isdn4linux -> dialling uses (my) local area code
Gary Jones wrote: >Here are the relevant parts of the config files: >#isdn.conf >[GLOBAL] >COUNTRYPREFIX=+ >AREAPREFIX=0 >COUNTRYCODE=49 >AREACODE=89 >#device.ippp0 >LOCALMSN=089***# my number >REMOTEMSN=109000191799 # Viag Interkom >LEADINGZERO='' # Have to use this here, otherwise the > # remotemsn becomes 0109... which is incorrect > > So the problem is that my ISP, Dog bless them, have a different > area code to me. This shouldn't be a problem, should it? I > don't believe that the folks who wrote isdn4linux didn't > consider the possibility (AFAIK this is normally the case > in the >UK, for example, where ISPs tend to be 0845-something). > This basically means I am either stupid, going blind, or both, > because I can't find anything in the FM. What happens is (from isdnlog):- > Fri Dec 08 18:13:54 outgoing * HDLC -> +49 89/109000191799, > München RING (Data) > Fri Dec 08 18:13:54 outgoing HDLC -> +49 89/109000191799, > München Unallocated (unassigned) number (Public network serving local user) > Fri Dec 08 18:13:54 outgoing HDLC -> +49 89/109000191799, > München HANGUP Unallocated (unassigned) number (Public network serving local > user) > i.e. isdn4linux puts the f*cking areacode on the outgoing number, > which might be perfectly correct in most cases but not in this one. > kjihj\cvkn klij\csdm Gary, how did you get the HDLC-output (by setting a higher debug or isdnctrl verbose level)? Are you sure your isdn.conf is read when using "isdnctrl dial ippp0"? I'm quite sure that only device.ippp0 is read when using isdn4linux which comes with potato (I'm just placing a simular question on this list). Robert
isdn4linux -> dialling uses (my) local area code
,bnj mkvfgsdzh jmklhzsdcfr I'm sorry, that was me beating my head against the keyboard in frustration. Here are the relevant parts of the config files: #isdn.conf [GLOBAL] COUNTRYPREFIX=+ AREAPREFIX=0 COUNTRYCODE=49 AREACODE=89 #device.ippp0 LOCALMSN=089***# my number REMOTEMSN=109000191799 # Viag Interkom LEADINGZERO='' # Have to use this here, otherwise the # remotemsn becomes 0109... which is incorrect So the problem is that my ISP, Dog bless them, have a different area code to me. This shouldn't be a problem, should it? I don't believe that the folks who wrote isdn4linux didn't consider the possibility (AFAIK this is normally the case in the UK, for example, where ISPs tend to be 0845-something). This basically means I am either stupid, going blind, or both, because I can't find anything in the FM. What happens is (from isdnlog):- Fri Dec 08 18:13:54 outgoing * HDLC -> +49 89/109000191799, München RING (Data) Fri Dec 08 18:13:54 outgoing HDLC -> +49 89/109000191799, München Unallocated (unassigned) number (Public network serving local user) Fri Dec 08 18:13:54 outgoing HDLC -> +49 89/109000191799, München HANGUP Unallocated (unassigned) number (Public network serving local user) i.e. isdn4linux puts the f*cking areacode on the outgoing number, which might be perfectly correct in most cases but not in this one. kjihj\cvkn klij\csdm Get your own FREE E-mail address at http://www.linuxfreemail.com Linux FREE Mail is 100% FREE, 100% Linux, and 100% yours!
