similar to: SNOM 190 Configuration with Asterisk

Displaying 20 results from an estimated 100 matches similar to: "SNOM 190 Configuration with Asterisk"

2020 Nov 20
2
Desktop Over NFS Home Blocked By Firewalld
Hi, Just installed CentOS 7 that serves a home dir automounted over nfs. SELinux is disabled. If I go to the client (oldish version of Fedora) doing su - username works fine and the nfs export is mounted and I can see all files and everything seems well. But trying to actually login to the desktop from the client machine does not work. It starts to login but then just hangs with a black screen.
2005 Sep 30
2
OT: SIPSAK usage
I'm using sipsak to send messages to Snoms in my subnet. At work, works fine: sipsak -M -O desktop -B "foo" -s sip:1001@192.168.1.220 -H 192.168.1.46 displays "foo" on the Snom display On my home LAN (AAH 1.5, Snom 190 3.60s, switched 100, no VLAN, no routing) the same command (modified for my LAN) always yields: (type: 3, code: 3): from 192.168.171.8 at the console
2010 Nov 16
5
ssh prompting for password
hello list I have a network mounted home directory shared between all hosts on my network: [bluethundr at LCENT03:~]#df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/VolGroup00-LogVol00 140G 4.4G 128G 4% / /dev/sda1 99M 35M 60M 37% /boot tmpfs 1.6G 0 1.6G 0% /dev/shm nas.summitnjhome.com:/mnt/nas
2008 Apr 14
2
corrupt files... oplocks?
Suddenly in the past week we have been having users who share excel files via our Samba complain that the file has become corrupt, and also some database files (Orcad .tdb database files). Fortunately there has in each instance been a good copy in the .recycler... so far. I came across some docs and threads in the net about oplocks. I did find an error in the samba log: [2008/04/14 10:19:05,
2003 Sep 15
5
strange problem with: ed driver / 4.9-PRE
Hi, in the kernel I have these lines: [...] device miibus # MII bus support device rl device ed options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #enable logging to syslogd(8) options IPFIREWALL_VERBOSE_LIMIT=0 #limit verbosity options IPDIVERT #divert sockets options DUMMYNET
2013 Nov 10
1
Strange unexplainable CUPS problem after upgrade to 5.10
I manage a bunch of workstations at the Wendell Free Library. They are all diskless, boot via PXE and mount all of their file systems via NFS from a server. All of the machines are 32-bit and run CentOS (fully up-to-date running 5.10). There are two printers with queues managed on the server. The server 'shares' these printers on the local LAN (eg with all of the workstations).
2006 Mar 15
0
OT: Using Sipsak to reboot a Snom phone
I have a custom sip reboot message I am transmitting to a Snom 200 to reboot it. The Snom gets it, it says "200 OK" but it doesn't reboot. I have turned off the challenge-reboot option in the Snom. When I modify the "Event:" directive from "reboot" to "snom-reboot" the phone yields "Bad Event" and when it is just "reboot" the phone
2006 Mar 15
0
OT: Using Sipsak to reboot a Snom phone < -a nswered my own question
Forgot on the Snom 200 it won't reboot if under the Memory tab in the web interface, Connections > 0 then remote reboot is not possible. Manually cycling the power allows the phone to be rebooted by Sipsak remotely. HOWTO: Reboot a Snom with Sipsak Checklist: 1. Under Advanced in the web interface, is Network Identity set to 5060? 2. Under Advanced in the web interface, is Challenge for
2006 Feb 17
5
A unique 'click to call' project - Could use some advice
Hello List, I work for an IP communication provider in upstate NY as the engineer assisting our technical support team. We provide a number of different Telco systems to residential subscribers; and in an effort to more effectively trouble shoot termination problems I came up with the idea of creating a click to call system that will allow our agents to effortlessly place test calls. On a
2020 Nov 20
2
Desktop Over NFS Home Blocked By Firewalld
On Fri, Nov 20, 2020 at 11:19 AM Frank Cox <theatre at sasktel.net> wrote: > > So firewalld is blocking something that the Fedora desktop needs. What > > is it? What services do I need to add to firewalls? > > https://www.cyberciti.biz/faq/enable-firewalld-logging-for-denied-packets-on-linux/ Hi Frank, Thanks for that tip. Here's what I get: Nov 20 12:03:15 goose
2005 Sep 22
0
SNOM 190 '486/Busy here' after upgrade to firmware 3.60s
Looks like this phone has redirection or DND set. Anything on the display? If it still a mystery send us the settings of the phone, then it should become clear. BTW if you have a snom trouble ticket, you can also go to http://www.snom.com/onlinesupport.html (scroll down to set up an account). CS > -----Original Message----- > From: asterisk-users-bounces@lists.digium.com >
2013 Oct 08
1
nut-2.6.5:rhino.c:190: bad if test ?
Hello there, Offending source code is ????? if(? ( BattVoltage> 129 ) || ( BattVoltage < 144 ) ) Maybe swap || for && would be better. This problem I found by using cppcheck. It said [rhino.c:190]: (warning) Logical disjunction always evaluates to true: BattVoltage> 129 || BattVoltage < 144. Regards David Binderman
2002 Mar 27
0
[Bug 190] New: ssh locks while waiting for output of df
http://bugzilla.mindrot.org/show_bug.cgi?id=190 Summary: ssh locks while waiting for output of df Product: Portable OpenSSH Version: 2.9.9p2 Platform: PPC OS/Version: AIX Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: jesch
2002 Mar 30
1
[Bug 190] ssh locks while waiting for output of df
http://bugzilla.mindrot.org/show_bug.cgi?id=190 ------- Additional Comments From stevesk at pobox.com 2002-03-31 04:42 ------- what is the df bug that causes this? we should timeout for no output cases. can you also try 3.1p1? ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
2004 Oct 05
0
Paypal? Available in 44 of the world's approximately 190 countries
Hi, In the aftermath of trying to register for Astricon, I've been still trying to re-open my Paypal account. The credit card and bank account I used are UK-based. I live in South Africa at the moment. Paypal have now formally refused to open an account for me. Notwithstanding that I have successfully "verified" both my credit card and my current account following their
2004 Dec 17
1
Snom 190, led and shared lines with asterisk
Hi All, I am trying to setup my snom 190 so that the LED's light up when one of my shared lines are in use. e.g. Extension 2 should ring on the snom and the phone associated with extension 2 and I should be able to see if the phone associated with extension 2 is making a call on the Snom. I think this is achieved with hints but don't seem to be getting on very well with it, does
2005 Jan 20
1
SNOM 190 and dtmf
I have the dtmfmode in sip.conf set to use rfc 2833 however, when my users have to enter pin numbers to join let say someone's conference bridge the pin is received twice. Any ideas on how to solve this? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20050120/56ff46fa/attachment.htm
2005 Jul 12
0
Pushing new firmware to Snom 190 <--solved
Found out I was doing it right, but the outbound firewalls that the Snom's sits behind has a captive portal that intercepted the HTTP request. Adding the Snom's MAC address to the firewall's captive portal worked correctly. A shortcut for any future Snom users that want to update firmware remotely: 1. In the web portal, click Advanced 2. Scroll down until you get to "Update
2005 Sep 22
0
SNOM 190 '486/Busy here' after upgrade to firmwa re 3.60s
I have a Snom 190 that refuses to accept calls after upgrade to firmware 3.60s, latest. I get "SIP 486/Busy Here". No change in the dialplan, nor settings in the phone. Calls out fine. I did 30 other phones yesterday with 3.60s with no problem, this is the only one. In the phone's log I get: [5]22/9/2005 17:01:00: timeout::callback: Registering with timeout of 0 ms [5]22/9/2005
2005 Sep 23
0
RE: SNOM 190 '486/Busy here' after upgrade to re 3.60s
AHA! # 1 is the case! Seems the user was fooling around with the phone after the firmware upgrade. Shame that that setting couldn't be locked out. Thanks to Mr Tahir and Mr Stredicke for their spot on responses. -----Original Message----- From: Usman Tahir [mailto:Usman.Tahir@snom.de] Sent: Friday, September 23, 2005 12:34 AM To: ColinA@landmarkmasterbuilder.com Cc: