Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
1
Installation and Upgrades / LPD printer setup
« on: June 28, 2010, 09:51:00 am »
Hello,
I am afraid I do not see full LPD printer support in ver. 1.4.
I noticed significant progress comparing to v.1.2. In ver.1.4 its web-GUI allows selection of LPD printers, but then asks for two parameters:
1. server address (this is fine), and
2. IP - this one is odd and shall be perhaps replaced by queue name (see below).
According to RFC 1179, the port on which a line printer daemon listens is fixed and it is set to 515. There is no need to change it. So the IP parameter is surplus in web-GUI. However, LPD requires a name of queue to be set.
Quote from RFC 1179: The code is immediately followed by the ASCII name of the printer queue name on which the function is to be performed.
The eBox 1.4 web-GUI does not allow to enter queue name as requested for LPD printers. Does anyone plan to fix this in next release? Or should we (users) hack the code ourselves?
Regards,
-DarS
I am afraid I do not see full LPD printer support in ver. 1.4.
I noticed significant progress comparing to v.1.2. In ver.1.4 its web-GUI allows selection of LPD printers, but then asks for two parameters:
1. server address (this is fine), and
2. IP - this one is odd and shall be perhaps replaced by queue name (see below).
According to RFC 1179, the port on which a line printer daemon listens is fixed and it is set to 515. There is no need to change it. So the IP parameter is surplus in web-GUI. However, LPD requires a name of queue to be set.
Quote from RFC 1179: The code is immediately followed by the ASCII name of the printer queue name on which the function is to be performed.
The eBox 1.4 web-GUI does not allow to enter queue name as requested for LPD printers. Does anyone plan to fix this in next release? Or should we (users) hack the code ourselves?
Regards,
-DarS
2
Installation and Upgrades / Re: VoIP/Asterisk CRASHES the eBox
« on: February 20, 2010, 04:34:57 am »
Hi Jsalamero,
Any hope for updated 'asterisk' as promised? I am ready to test it ...
-DarS
Any hope for updated 'asterisk' as promised? I am ready to test it ...
-DarS
3
Installation and Upgrades / Re: VoIP/Asterisk CRASHES the eBox
« on: February 14, 2010, 07:06:18 am »
OK, I gathered some more details on Asterisk crashing the entire eBox server.
- the error is repeatable. It occurs at every VoIP call (I mean after finishing first VoIP call. 'First', because then the 'eBox' needs to be manually reset and rebooted)
- it is perhaps not hardware related. I observed identical behaviors on two configurations:
Compaq Evo D510
HP e-pc
Both are low-end desktop machines but with different hw specs (CPU, RAM, etc.) and architectures. In both cases the 'eBox` was installed as physical OS and not inside any virtual machine.
- apart from problems with Asterisk, the rest of 'eBox' runs fine on both machines. I guess PCs specs were not an issue for running Asterisk (CPU 1GHz+ in both cases, RAM 256M and 512M, HDD 160GB)
- it is not related to any VoIP equipment. I did not have any VoIP cards or alike. I used only softphones to test the Asterisk.
- typical methods of troubleshooting failed. I even tried to boot with
- it is perhaps related to kernel, as the entire system freezes completely. There is no access via web GUI and SSH. Even physical console (local keyboard and monitor) does not respond.
Regards,
DarS
- the error is repeatable. It occurs at every VoIP call (I mean after finishing first VoIP call. 'First', because then the 'eBox' needs to be manually reset and rebooted)
- it is perhaps not hardware related. I observed identical behaviors on two configurations:
Compaq Evo D510
HP e-pc
Both are low-end desktop machines but with different hw specs (CPU, RAM, etc.) and architectures. In both cases the 'eBox` was installed as physical OS and not inside any virtual machine.
- apart from problems with Asterisk, the rest of 'eBox' runs fine on both machines. I guess PCs specs were not an issue for running Asterisk (CPU 1GHz+ in both cases, RAM 256M and 512M, HDD 160GB)
- it is not related to any VoIP equipment. I did not have any VoIP cards or alike. I used only softphones to test the Asterisk.
- typical methods of troubleshooting failed. I even tried to boot with
Code: [Select]
acpi=off to ensure that the hw/interrupts were not causing this bug. Turning 'acpi=off' did not help! The 'acpi' was no longer listed in '/proc', but Asterisk (or rather the entire 'eBox') kept dying after first VoIP call.- it is perhaps related to kernel, as the entire system freezes completely. There is no access via web GUI and SSH. Even physical console (local keyboard and monitor) does not respond.
Regards,
DarS
4
Installation and Upgrades / VoIP/Asterisk CRASHES the eBox
« on: February 11, 2010, 06:04:43 am »
Hello,
I have fresh install of eBox 1.4 (some modules were upgraded yesterday to 1.4.1) with very unusual feature - the 'eBox' crashes completely after every VoIP call.
The VoIP user logs in to SIP 'eBox' without any problems, the user's status is displayed correctly. First VoIP connection is performed well - when I dialed test number 600, I could hear test announcement, stay on line and test voice feedback/echo, etc. However, when the call is being finished, the 'eBox' virtually freezes! There is no response from web console, SSH connection, ping, etc. The box needs to be manually rebooted. This happens every time I try to use VoIP.
Careful investigation after next reboot did not show anything unusual in 'eBox' logs. Nothing in 'messages' log nor in 'asterisk' one.
I am used to various flavors of Linux for several years, but I never seen Linux server 'so dead'
Question: has anyone else experienced such odd behavior?
If so, then I guess this is a bug somewhere in 'eBox' and/or 'Asterisk'.
If not, then I need to check more carefully the hardware (although my hw platform is a standard PC without any strange setup. I tested VoIP using softphones so I don't have any server hardware cards dedicated to Asterisk).
Regards,
-DarS
I have fresh install of eBox 1.4 (some modules were upgraded yesterday to 1.4.1) with very unusual feature - the 'eBox' crashes completely after every VoIP call.
The VoIP user logs in to SIP 'eBox' without any problems, the user's status is displayed correctly. First VoIP connection is performed well - when I dialed test number 600, I could hear test announcement, stay on line and test voice feedback/echo, etc. However, when the call is being finished, the 'eBox' virtually freezes! There is no response from web console, SSH connection, ping, etc. The box needs to be manually rebooted. This happens every time I try to use VoIP.
Careful investigation after next reboot did not show anything unusual in 'eBox' logs. Nothing in 'messages' log nor in 'asterisk' one.
I am used to various flavors of Linux for several years, but I never seen Linux server 'so dead'
Question: has anyone else experienced such odd behavior?
If so, then I guess this is a bug somewhere in 'eBox' and/or 'Asterisk'.
If not, then I need to check more carefully the hardware (although my hw platform is a standard PC without any strange setup. I tested VoIP using softphones so I don't have any server hardware cards dedicated to Asterisk).
Regards,
-DarS
5
Installation and Upgrades / Re: IMAP for external mail reader (Thunderbird) does not work
« on: July 05, 2009, 01:34:57 pm »
Unbelievably simple solution 
Yes, it did work - once I changed my mail reader settings from USER to USER@MAIL.DOMAIN, the IMAP access started to work flawlessly.
Thanks J.A. for your hint!
-DarS
Yes, it did work - once I changed my mail reader settings from USER to USER@MAIL.DOMAIN, the IMAP access started to work flawlessly.Thanks J.A. for your hint!
-DarS
6
Installation and Upgrades / IMAP for external mail reader (Thunderbird) does not work
« on: July 05, 2009, 07:43:00 am »
Hello,
Just a quick check whether anyone else experiences behavior similar to the one observed on my eBox (ver. 1.0 I believe - I installed it right from 'eBox' DVD in June this year). I've enabled 'mail' and 'eGroupware' and they work fine. I can access user mailboxes via eGroupware mail client (FelaMiMail). However, when I try to use external mail reader like Thunderbird, I got message 'login failed'.
I even did a quick check and tried to manually connect to IMAP service on eBox:
I am certain that the above USER and PASSWORD were correct, because they were identical to these used to log to 'eGroupware' account.
Are there any hints/tips required to configure IMAP mail access from external readers? I have all basic services ('network', 'mail', 'eGroupware', etc.) enabled and configured... Or I think so
Regards,
-DarS
Just a quick check whether anyone else experiences behavior similar to the one observed on my eBox (ver. 1.0 I believe - I installed it right from 'eBox' DVD in June this year). I've enabled 'mail' and 'eGroupware' and they work fine. I can access user mailboxes via eGroupware mail client (FelaMiMail). However, when I try to use external mail reader like Thunderbird, I got message 'login failed'.
I even did a quick check and tried to manually connect to IMAP service on eBox:
Code: [Select]
telnet localhost 143
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
* OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE STARTTLS]\
Courier-IMAP ready. Copyright 1998-2005 Double Precision, Inc. See COPYING for distribution information.
a login USER PASSWORD
a NO Login failed.
a logout
* BYE Courier-IMAP server shutting down
a OK LOGOUT completed
I am certain that the above USER and PASSWORD were correct, because they were identical to these used to log to 'eGroupware' account.
Are there any hints/tips required to configure IMAP mail access from external readers? I have all basic services ('network', 'mail', 'eGroupware', etc.) enabled and configured... Or I think so
Regards,
-DarS
7
Installation and Upgrades / LPD printers - how to setup?
« on: June 22, 2009, 05:53:00 am »
Hello,
I have a laser printer connected to a remote (LAN) print server. The latter is an old SMC Barricade (7004BR) router which has built-in LPD print server functionality. The print server queue is accessible via lpd://PRINT_SERVER_IP/lp. And this is the problem :-(
I cannot force eBox to setup properly the LPD printing. The eBox interface gives me several options for setup, but none actually allows to setup 'lpd' mode. The available options (modes) are:
- USB => for locally connected devices
- parallel => for locally connected devices
- Network printer
- Samba
I tried last both modes, but failed with the following results:
- Network printer => the eBox set up the following device: socket://PRINT_SERVER_IP:9100
- Samba => the eBox set up the following device: smb://lpd://PRINT_SERVER_IP/lp
So I am wondering what to do to achieve desired lpd://PRINT_SERVER_IP/lp. Note that LPD printing is fully supported by CUPS, so the issue is with eBox and not with CUPS.
I know Perl a bit so I am ready for more advanced troubleshooting and coding (if necessary). I guess all the changes which needs to be done are somewhere in printer schemas which define 'printer modes'. However, I could not find such schemas. Could anyone help me here?
Regards,
-Darek
I have a laser printer connected to a remote (LAN) print server. The latter is an old SMC Barricade (7004BR) router which has built-in LPD print server functionality. The print server queue is accessible via lpd://PRINT_SERVER_IP/lp. And this is the problem :-(
I cannot force eBox to setup properly the LPD printing. The eBox interface gives me several options for setup, but none actually allows to setup 'lpd' mode. The available options (modes) are:
- USB => for locally connected devices
- parallel => for locally connected devices
- Network printer
- Samba
I tried last both modes, but failed with the following results:
- Network printer => the eBox set up the following device: socket://PRINT_SERVER_IP:9100
- Samba => the eBox set up the following device: smb://lpd://PRINT_SERVER_IP/lp
So I am wondering what to do to achieve desired lpd://PRINT_SERVER_IP/lp. Note that LPD printing is fully supported by CUPS, so the issue is with eBox and not with CUPS.
I know Perl a bit so I am ready for more advanced troubleshooting and coding (if necessary). I guess all the changes which needs to be done are somewhere in printer schemas which define 'printer modes'. However, I could not find such schemas. Could anyone help me here?
Regards,
-Darek
Pages: [1]