search for: 190s

Hi all, I got a couple of Snom 190's through this week and after some initial foolishness I have them both setup no problems. But here comes the except. When there is voicemail waiting the softbutton appears but the phone always dials its own extension. No matter what I put into the "mailbox" parameter on the line settings. (Phone registers correctly with * and all standard

...1 c 2.812804e-03 1 <NA> 4 con 0.001 1 180s 0 s 3.791027e-01 1 <NA> 619 lim 0.003 2 160s 0 s 5.723237e-01 1 <NA> 620 lim 0.003 2 161t 1 t 1.096077e-02 1 <NA> 621 lim 0.003 2 161c 1 c 3.896926e-03 1 <NA> 630 lim 0.003 2 190s 0 s 1.340253e-02 1 <NA> 631 lim 0.003 2 190s 0 s 9.274320e-03 1 <NA> 632 lim 0.003 3 160s 0 s 6.527778e-01 1 <NA> 633 lim 0.003 3 180s 0 s 3.211201e-01 1 <NA> 634 lim 0.003 3 181c 1 c 2.610209e-02 1 <NA> 635 lim 0.003 4...

...;lim' and dia=2") > > ​ sol con dia NCar NIns isom area rep tipo > 1 lim 0.003 2 160s 0 s 0.572323700 1 <NA> > 2 lim 0.003 2 161t 1 t 0.010960770 1 <NA> > 3 lim 0.003 2 161c 1 c 0.003896926 1 <NA> > 4 lim 0.003 2 190s 0 s 0.013402530 1 <NA> > 5 lim 0.003 2 190s 0 s 0.009274320 1 <NA> > ​ > > ​Saludos.​ > > > -- > «But Gwindor answered: 'The doom lies in yourself, not in your name.'» > > JRR Tolkien > -- «But Gwindor answered: 'The doo...

...ones. A sample of the resulting output from the configuration script: =========== fkey0!: line fkey1!: line fkey2!: dest <sip:1000@asterisk-server;user=phone> fkey3!: dest <sip:1002@asterisk-server;user=phone> fkey4!: dest <sip:1011@asterisk-server;user=phone> =========== The 190s seem to ignore all fkey settings. The existing setting in the phone that I have from manually configuring the phone earlier remains and dosn't become overwritten. Also, how can I get hold of the Alpha/Beta firmware for the 190s? Cheers, -Shaun

...t * from graph where sol='lim' and dia=2") ​ sol con dia NCar NIns isom area rep tipo 1 lim 0.003 2 160s 0 s 0.572323700 1 <NA> 2 lim 0.003 2 161t 1 t 0.010960770 1 <NA> 3 lim 0.003 2 161c 1 c 0.003896926 1 <NA> 4 lim 0.003 2 190s 0 s 0.013402530 1 <NA> 5 lim 0.003 2 190s 0 s 0.009274320 1 <NA> ​ ​Saludos.​ -- «But Gwindor answered: 'The doom lies in yourself, not in your name.'» JRR Tolkien [[alternative HTML version deleted]]

...t; > > > sol con dia NCar NIns isom area rep tipo > > 1 lim 0.003 2 160s 0 s 0.572323700 1 <NA> > > 2 lim 0.003 2 161t 1 t 0.010960770 1 <NA> > > 3 lim 0.003 2 161c 1 c 0.003896926 1 <NA> > > 4 lim 0.003 2 190s 0 s 0.013402530 1 <NA> > > 5 lim 0.003 2 190s 0 s 0.009274320 1 <NA> > > > > > > Saludos. > > > > > > -- > > «But Gwindor answered: 'The doom lies in yourself, not in your name.'» > > > > JRR Tolkien...

...d changed disk param to- disk = [''access=w,vdev=xvda1,backend=storage,target=/root/domsi.img''] And I got this console log - [ 5.588091] XENBUS: Waiting for devices to initialise: 25s...20s...15s...10s...5s...0s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... [ 270.588319] XENBUS: Timeout connecting to device:...

...d changed disk param to- disk = [''access=w,vdev=xvda1,backend=storage,target=/root/domsi.img''] And I got this console log - [ 5.588091] XENBUS: Waiting for devices to initialise: 25s...20s...15s...10s...5s...0s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... [ 270.588319] XENBUS: Timeout connecting to device:...

...s: xen-vbd: registered block device major 202 xvda:<6>netfront: Initialising virtual ethernet driver. XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...<6>Uniform Multi-Platform E-IDE driver SCSI subsystem initialized st: Version 20080504, fixed bufsize 32768, s/g segs 256 BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information no...

Hi We are about to buy several Snom phones. Does anyone have warnings or advices against these phones ? Our finalists were Cisco, Polycom and Snom. We will be using only the SIP protocol. Thanks Patrick

...0.976647] NET: Registered protocol family 17 [ 0.976739] registered taskstats version 1 [ 6.077230] XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... [ 301.076163] XENBUS: Timeout connecting to device:...

...l Host Controller Interface driver v3.0 Loading jbd.ko module Loading ext3.ko module Loading xenblk.ko module XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s... XENBUS: Timeout connecting to device: device/vbd/517...

Hi, I am looking for hardware sip phone with very good sound quality. Can anyone recommend ? I use to have Grandstream Budge-Tone 100 but I feel that the sound is not very satisfactory and volume too soft Regards ASLAY

...get the intercom feature working on some snom 190 phones but having no luck... As you can see from the SIP trace below (from the called phone), intercom=true is being appended to the To: header as per requirements. I've email'd snom a few days ago but have yet to get a response. On my 190s, im running snom190-SIP 3.57v. I am pulling the config for the phone from a web page. Im setting: intercom_enabled&: on Looking in the settings.htm page on the phone verifies this, as does the listing in the advanced.htm page. Any one have any ideas why I'm having this problem? Cheers,...

Hello, I just bought a Snom-320 from ATAComm. I plugged it into my LAN, registered it with *, etc. All my other SIP gear is Sipura and works fine, both on the LAN and over the Internet. The new Snom seems like it can't process the audio from the handset mic. A steady tone is garbled, even on the LAN. I've contacted ATAComm, Snom and the company representing Snom in the US. So

I have a pair of snom 360s at a customer and they were giving me Low Memory errors. The distributor suggested updating the firmware. I did that, to the one just below 4.0 (which wasn't released yet). One of the phones is still giving the Low Memory error every 3-4 days. The other one had a broken display that was just RMA'd, so it' hasn't been up long enough to know if the

I want to configure my zfs like this : concatination_stripe_pool : concatination lun0_controller0 lun1_controller0 concatination lun2_controller1 lun3_controller1 1. There is any option to implement it in ZFS? 2. there is other why to get the same configuration? thanks This message posted from opensolaris.org

I am having major problems with the first run of Snom 360s that rolled out last month. I am working with the US vendor and they in turn are working with Snom but I wanted to see of anyone else was using these or having issues with them. Issues: Speakerphone/Hands Free volume spikes up and down during a call. You have to manually set the volume during every call. This makes it totally unusable.

...0.260070] sit: IPv6 over IPv4 tunneling driver [ 0.260194] NET: Registered protocol family 17 [ 0.260213] Bridge firewalling registered [ 5.360075] XENBUS: Waiting for devices to initialise: 25s...20s...15s...10s...5s...0s...235s...230s...225s...220s...215s...210s... 205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s... 150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s... 95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s... 35s...30s...25s...20s...15s...10s...5s...0s... [ 270.360180] XENBUS: Timeout connecting to devi...

This is a bit off topic, because I 'think' it isn't an Asterisk problem. However I'm not sure and anyhow I'm hoping someone may recognize the symptom. We moved offices a month ago. Our trusty SNOM190s (all between 3 and 5 years old) were packed up for the move, then unpacked a couple of weeks later. On unpacking them and connecting them to the new network, several of them didn't work well. The symptom is that outgoing RTP audio is garbled - like the packets are pulsed. Inbound is fine...