similar to: OT: Aastra 390 - weird problem

Displaying 20 results from an estimated 6000 matches similar to: "OT: Aastra 390 - weird problem"

2005 Jan 04
6
Polycom Buddy Feature
Greetings, Recently there has been talk of the presence/buddy feature with asterisk and Polycom phones. I have it setup, and working as expected, however I can only get 7 buddies to appear on the screen at any given time. Has anyone gotten more than 7 buddies to appear? I'm just trying to find out if this is some polycom limitation, bug, or my error. Thanks, Matt -- Matt Gibson VOIP
2005 Jan 17
0
Multiple Line Caller Id With Polycom IP500
Greetings, I'm wondering if it's possible to display line breaks with caller ID display. I have the Polycom ip500 phone, and what I am trying to accomplish is instead of the phone saying 'Incoming call from: name/number' i want it to appear on the phone like this Incoming Call from: Menu Context last in Name Number I tried using \n and \\n between the variables (${VAR} \\n
2005 Jan 04
1
Re: Polycom Buddy Feature
I'm still trying to work this out. I've got this in my sip.conf [1003polycom] type=peer secret=abc123 host=dynamic defaultip=192.168.1.215 context=default mailbox=1003 subscribecontext=phonestatus [1004polycom] type=peer secret=abc123 host=dynamic defaultip=192.168.1.214 context=default mailbox=1004 subscribecontext=phonestatus And this in my extensions.conf [phonestatus] exten =>
2005 Jan 11
2
PA-168(S) - Netweb IPweb-301 Phone
Greetings, I just received some netweb-301 phones frm Seshu down in NJ. I cannot for the life of me get it to register with the asterisk server, nor upgrade the firmware to the latest (1.41) i'm still using 1.37. The packets are traversing the router, going into the other subnet, hitting the asterisk box, but not actually making it to asterisk. Nothing in the asterisk logs, but tcpdump
2004 Dec 03
4
Polycom 500, won't ring??
Hi, I have was testing some of the different ring types with my polycom 500, and the ALERT_INFO settings. Now when my phone receives a call it won't ring. All the other phones ring fine, and my phone wasn't the only one I rebooted with the changed sip.conf and impd.conf. I have reverted back to a standard sip.conf and impd.conf and I still can not get my phone to ring for any incoming
2008 Aug 15
1
Problem with Aastra 480ci and qualify=yes
Hi, We have a few Aastra 480ci phones and we've noticed that in order to get the phone to receive a call, qualify must be = no. Apparently the Aastras do not respond to the qualify message (or respond in a way Asterisk doesn't understand) and Asterisk thinks the phone is unreachable. However, this now prevents MWI from working properly on the phones. Does anyone know how to get MWI
2007 Mar 28
3
Multi-line phones - Asterisk uses wrong callerid
I have some phones (and an ATA) that are shared between two users who each have separate voicemail but they are not behaving as desired nor expected. Incoming calls show up on the correct lines. Calls originating from the device are seen, at the terminating device, as coming from the account listed last in sip.conf, regardless of the line selected. This creates three main issues I would like
2007 Jan 04
4
POE draw on Aastra 480i
Anyone know what the POE draw is for the Aastra 480i phones? We have switches that will do 15 watts on 12 ports but only do 7.7 watts on all 24 ports. A Cisco 3560 switch will do 15.6 watts on all 24 ports. Just trying to find out if we need that much power. Can't seem to find any info on the Aastra site. Comments?
2008 Jan 29
2
POE draw on Aastra 480i
> > Allen Casteran wrote: > > Anyone know what the POE draw is for the Aastra 480i phones? > > We have switches that will do 15 watts on 12 ports but only do 7.7 watts on all 24 ports. > > A Cisco 3560 switch will do 15.6 watts on all 24 ports. > > Just trying to find out if we need that much power. > Drew wrote: > According to Aastra tech support, 5 watts
2004 Dec 07
0
GrandStream BT VS. IP500 Latency
I just noticed something when I 'sip show peers' from the CLI, I get the following: 6113/6113 x.x.x.x D N 255.255.255.255 62927 OK (66 ms) 6112/6112 x.x.x.x D N 255.255.255.255 50079 OK (160 ms) 6111/6111 x.x.x.x D N 255.255.255.255 60810 OK (141 ms) 6109/6109 x.x.x.x D N 255.255.255.255 51331 OK (151 ms) All of those
2015 Jan 29
1
[Qemu-devel] [PATCH RFC v6 05/20] virtio: support more feature bits
On Thu, Jan 29, 2015 at 10:24:00AM +0100, Thomas Huth wrote: > > Hi, > > On Thu, 29 Jan 2015 11:11:32 +1100 > David Gibson <david at gibson.dropbear.id.au> wrote: > > > On Wed, Jan 28, 2015 at 04:59:45PM +0100, Cornelia Huck wrote: > > > On Thu, 22 Jan 2015 12:43:43 +1100 > > > David Gibson <david at gibson.dropbear.id.au> wrote: > >
2015 Jan 29
1
[Qemu-devel] [PATCH RFC v6 05/20] virtio: support more feature bits
On Thu, Jan 29, 2015 at 10:24:00AM +0100, Thomas Huth wrote: > > Hi, > > On Thu, 29 Jan 2015 11:11:32 +1100 > David Gibson <david at gibson.dropbear.id.au> wrote: > > > On Wed, Jan 28, 2015 at 04:59:45PM +0100, Cornelia Huck wrote: > > > On Thu, 22 Jan 2015 12:43:43 +1100 > > > David Gibson <david at gibson.dropbear.id.au> wrote: > >
2003 Feb 21
1
Fun new problem with Aastra 390 ADSI phones
Bill I have adtran750 with Vista/Aastra 350, 390, & 480's never seen that one tim -----Original Message----- From: asterisk at billheckel.com <asterisk at billheckel.com> To: asterisk-users at lists.digium.com <asterisk-users at lists.digium.com> Date: February 21, 2003 12:52 PM Subject: [Asterisk-Users] Fun new problem with Aastra 390 ADSI phones >I seem to have
2003 Sep 19
1
Aastra 390 w/ADSI - Doesn't automagically use "Asterisk PBX" script
I have an Aastra 390 ADSI phone. It's not locked. I can call ADSIProg without a problem and it programs my phone. Calling Voicemail2 also programs my phone. However, in order for the VMail option to appear on the screen I have to go into the Services menu, pick Asterisk PBX and pick Select. Then the VMail softbutton appears on the screen, but any time I make a call it goes back to the
2015 Jan 29
2
[Qemu-devel] [PATCH RFC v6 05/20] virtio: support more feature bits
On Wed, Jan 28, 2015 at 04:59:45PM +0100, Cornelia Huck wrote: > On Thu, 22 Jan 2015 12:43:43 +1100 > David Gibson <david at gibson.dropbear.id.au> wrote: > > > On Thu, Dec 11, 2014 at 02:25:07PM +0100, Cornelia Huck wrote: > > > With virtio-1, we support more than 32 feature bits. Let's extend both > > > host and guest features to 64, which should
2015 Jan 29
2
[Qemu-devel] [PATCH RFC v6 05/20] virtio: support more feature bits
On Wed, Jan 28, 2015 at 04:59:45PM +0100, Cornelia Huck wrote: > On Thu, 22 Jan 2015 12:43:43 +1100 > David Gibson <david at gibson.dropbear.id.au> wrote: > > > On Thu, Dec 11, 2014 at 02:25:07PM +0100, Cornelia Huck wrote: > > > With virtio-1, we support more than 32 feature bits. Let's extend both > > > host and guest features to 64, which should
2004 May 10
1
ztcfg and Aastra 390 phones
I am wandering if anyone can explain this unusual scenario. I am running Asterisk on Fedora. After the box boots, I run insmod wcfxs at a command line. The phones keep the red message light on and are in a state like they are not recognized yet. If I then run the command ztcfg, I don't get anything after the command, meaning that everything should be OK in zapata and zaptel confs and the
2019 Oct 14
3
[PATCH 1/2] dma-mapping: Add dma_addr_is_phys_addr()
On Fri, Oct 11, 2019 at 06:25:18PM -0700, Ram Pai wrote: > From: Thiago Jung Bauermann <bauerman at linux.ibm.com> > > In order to safely use the DMA API, virtio needs to know whether DMA > addresses are in fact physical addresses and for that purpose, > dma_addr_is_phys_addr() is introduced. > > cc: Benjamin Herrenschmidt <benh at kernel.crashing.org> > cc:
2019 Oct 14
3
[PATCH 1/2] dma-mapping: Add dma_addr_is_phys_addr()
On Fri, Oct 11, 2019 at 06:25:18PM -0700, Ram Pai wrote: > From: Thiago Jung Bauermann <bauerman at linux.ibm.com> > > In order to safely use the DMA API, virtio needs to know whether DMA > addresses are in fact physical addresses and for that purpose, > dma_addr_is_phys_addr() is introduced. > > cc: Benjamin Herrenschmidt <benh at kernel.crashing.org> > cc:
2015 Jan 22
2
[Qemu-devel] [PATCH RFC v6 05/20] virtio: support more feature bits
On Thu, Dec 11, 2014 at 02:25:07PM +0100, Cornelia Huck wrote: > With virtio-1, we support more than 32 feature bits. Let's extend both > host and guest features to 64, which should suffice for a while. > > vhost and migration have been ignored for now. [snip] > diff --git a/include/hw/virtio/virtio.h b/include/hw/virtio/virtio.h > index f6c0379..08141c7 100644 > ---