similar to: Snom phones, blinking lights and call pickup

Hi! System: Debian/testing with selfcompiled kernel 3.5.5 (same error with 3.4 or 3.6) XEN: 4.1.3 After booting the Dom0 I notice the following errors: [ 2.939078] microcode: CPU0 sig=0x1067a, pf=0x1, revision=0xa07 [ 2.991998] microcode: CPU0 update to revision 0xa0b failed [ 2.992035] microcode: CPU1 sig=0x1067a, pf=0x1, revision=0xa07 [ 2.995882] microcode: CPU1 update to

Hi! Some persons are using a TAPI driver to connect via the manager interface to the asterisk (1.4). While I can give every user his own password, I didn?t find a way to restrict a user to a certain phone number, so that he can only dial with his number via the TAPI driver and can only answer calls for another number. Is the possible? If yes, how? Thanks for the answers. Shade and sweet

On Tue, 2015-05-19 at 13:31 +0200, Stephan Seitz wrote: > On Fri, May 15, 2015 at 08:26:42AM +0100, Ian Campbell wrote: > >Here's an idea. First extract the real initrd from the back half of the > >initrd: > > ijc at dagon:tmp$ cat /boot/initrd.img | ( cpio -t >&2 ; cat ) > initrd.real > > kernel > > kernel/x86 > >

Hello Everybody, I'm using the snom Phones together with Asterisk and I already able to see which Peer is used via "hint" priority. Then a LED on the snom phone is blinking. But I don't see who is calling the other phone. I know that the snom phones are already support this feature. But how I can enable this on Asterisk? Regards Bastian

AFAICT our current version does not correspond to any version in the Linux history. This commit resynchronised to the state in Linux commit 598bae70c2a8e35c8d39b610cca2b32afcf047af. Differences from upstream: find_cpio_data is __init, printk instead of pr_*. This appears to fix Debian bug #785187. "Appears" because my test box happens to be AMD and the issue is that the (valid) cpio

HelloI have the following system Asterisk 1.6.1dahdi 2.2.0.2 TE420P card Centos I have noticed that all the four lights are blinking(ie coming red and then off so on)... Previously I also noted that when dahdi drivers are not installed lights blink but one by one in sequence(like in marriage cermonies :P) and after dahdi installation lights get off ... but this time all at same time

> > according to the documentation the option ucode=scan should tell XEN to > > look for a microcode update in an uncompressed initrd. > > > > While I don?t use the Debian kernel the tools to generate the initrd are > > part of Debian. The command ?cpio -i < /boot/initrd.img-4.0.2-Dom0? > > creates the directory structure

hi listmembers, please test my new patch to chan_sip.c which is to make call pickup on the snom phones (and maybe other phones that support 'INVITE/Replaces') work and make comments in the bugtracker http://bugs.digium.com/view.php?id=3644 so it can make its way into the cvs. this patch sipsubscribe-20050715.rev779.txt enables: * monitoring of other lines (using the 'hint'

On Thu, 2015-05-14 at 22:45 +0200, Stephan Seitz wrote: > On Wed, May 13, 2015 at 11:57:55AM -0400, Konrad Rzeszutek Wilk wrote: > >> > according to the documentation the option ucode=scan should tell XEN to > >> > look for a microcode update in an uncompressed initrd. > >> > > >> > While I don?t use the Debian kernel the tools to generate the

Hi, I've used various patches with asterisk 1.4 to have support for call pickup and notification with good results. Now I'm trying vanilla 1.6.2 with its official support for "dialog-info +xml" notifications with no success. This is what i'm doing: - Phone A has a key configured as type "extension" pointing to Phone B. - In sip.conf I added

Hello, I am having some troubles with Snom phones and maybe someone can help me. Let me say this: BLF and pickup works great with Polycomes and Grandstream etc... So I think my problem might not be Asterisk related but I am not 100% sure. The snom phones subscribe to my extensions (hint priority) as expected. The light blinks (ringing) or is turned on (in the call) as expected. My problem is to

hi, i just ported the patch of David Hinkle http://www.mail-archive.com/asterisk-users@lists.digium.com/msg49781.html to the current cvs version of asterisk. the theory is that the leds of supervisioned extensions are blinking until a call is established whereafter the leds should be constantly lit. however it's not working. the asterisk server is sending the following xml notify to the

Hi! I would like to know the status of the frequency scaling in XEN. I found a web site saying that XEN doesn’t work with frequency scaling, at the other hand I found some fixes for powernow-k8 to get rid of some messages. I have an AMD64. powerno-k8 works find with non-XEN kernels, but with XEN-kernels I get the error: powernow-k8: Found 1 AMD Athlon(tm) 64 Processor 3400+ processors

Hi, I want to pick up a call with the snom's programmable buttons(snom190 -SIP 3.60x, snom360-SIP 4.1) with asterisk server (v 1.2.0), I tried with the option 'Destination' and when the incoming call arrive to another snom phone the button blinking. In this way I can only pick down it pressing the blinking button. The solution is call the *8 or parcking the call but my pbroblem

Hi, I'm banging my head over this. Usually, I'm using a SIP hardphone feature called "Call Pickup Starcode" to enhance BLF with Directed Call Pickup : basically, SIP hardphone (here a Thomson ST2030S) is configured to send an INVITE message whenever a BLF is pressed while blinking. The INVITE is build with the extension number (attached to the BLF that was blinking and pressed)

Package: xen-hypervisor-4.5-amd64 Version: 4.5.0-1 Severity: normal Dear Maintainer, according to the documentation the option ucode=scan should tell XEN to look for a microcode update in an uncompressed initrd. While I don?t use the Debian kernel the tools to generate the initrd are part of Debian. The command ?cpio -i < /boot/initrd.img-4.0.2-Dom0? creates the directory structure

On Wed, May 13, 2015 at 11:57:55AM -0400, Konrad Rzeszutek Wilk wrote: >> > according to the documentation the option ucode=scan should tell XEN to >> > look for a microcode update in an uncompressed initrd. >> > >> > While I don?t use the Debian kernel the tools to generate the initrd are >> > part of Debian. The command ?cpio -i <

On Fri, May 15, 2015 at 08:26:42AM +0100, Ian Campbell wrote: >Here's an idea. First extract the real initrd from the back half of the >initrd: > ijc at dagon:tmp$ cat /boot/initrd.img | ( cpio -t >&2 ; cat ) > initrd.real > kernel > kernel/x86 > kernel/x86/microcode > kernel/x86/microcode/GenuineIntel.bin > 16 blocks

On Tue, May 19, 2015 at 12:47:51PM +0100, Ian Campbell wrote: >The reconcatenate bit is easy, just: > $ cat initrd.ucode initrd.real > initrd.img >With initrd.real extracted above. > >initrd.ucode creation I'm a little unsure about but something like: > >$ mkdir initrd.ucode.tree >$ cd initrd.ucode.tree >$ cat /boot/initrd.img | cpio -id >$ find >.

Christian, Just a quick heads up warning that something seems to be amiss on the Snom 200 running v2.03h code. The Message Waiting Indicator is blinking (due to a voicemail left in Asterisk) as its suppose to. Some time later the LED stops blinking (as though no voicemail); then later it starts blinking again. I left a voicemail to x3008 (button 2) this morning at 8:48am, and purposefully have