Hi people, I just rolled out my first attempt with Asterisk to get a working PBX. I'm recieving my calls still through my ISDN connection. But I'm getting a lag of almost 1 second between the both sides of the conversation. What should be the first things to look at when trying to solve this lag? I'm using an Athlon 700MHz with Debian and the default Asterisk packages from Debian. The connection is made with a HPC-S PCI ISDN card, directly connected to the NT1 box. I'm using a Grandstream HandyTone 486 to connect my Philips DECT handset to the VoIP server. The HandyTone is connected through a 100Mbit switch with the server. Any advice is appreciated! -- Gegroet, Tim
I had the same problem with ISDN. I actually got the last second or so of the previous call "played back" at the beginning of each call. There is a patch for this problem. I wish I could remember the name of the person who sent it to me. Maybe she will contact you if she sees this post. I will also have a look in my old mail later today. Thor On 11/24/05, Tim Stoop <tim.stoop@gmail.com> wrote:> > Hi people, > > I just rolled out my first attempt with Asterisk to get a working PBX. > I'm recieving my calls still through my ISDN connection. But I'm > getting a lag of almost 1 second between the both sides of the > conversation. What should be the first things to look at when trying > to solve this lag? > > I'm using an Athlon 700MHz with Debian and the default Asterisk > packages from Debian. The connection is made with a HPC-S PCI ISDN > card, directly connected to the NT1 box. I'm using a Grandstream > HandyTone 486 to connect my Philips DECT handset to the VoIP server. > The HandyTone is connected through a 100Mbit switch with the server. > > Any advice is appreciated! > > -- > Gegroet, > Tim > _______________________________________________ > --Bandwidth and Colocation sponsored by Easynews.com<http://easynews.com/>-- > > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20051124/8977bc76/attachment.htm
I found the mail from Pauline Middelink! filename: hfc_pci.c.diff --- /root/hfc_pci.c Wed Aug 7 15:31:24 2002 +++ /usr/src/linux/drivers/isdn/hisax/hfc_pci.c Thu Oct 31 10:18:05 2002 @@ -270,8 +270,16 @@ if (fifo_state) cs->hw.hfcpci.fifo_en ^= fifo_state; Write_hfc(cs, HFCPCI_FIFO_EN, cs->hw.hfcpci.fifo_en); - bzt->za[MAX_B_FRAMES].z1 = B_FIFO_SIZE + B_SUB_VAL - 1; - bzt->za[MAX_B_FRAMES].z2 = bzt->za[MAX_B_FRAMES].z1; + /* Notice the z2 is readonly, and could be active when we enter this + * function. (I.e. changing.) When we now reset z1 to MAXSIZE, the + * FIFO thinks there is data and runs it when re-enabled... + * To prevent this from happening, we make z1 ONE higher than z2, so + * when the FIFO gets re-enabled, it thinks it only has to send a + * single byte, which hopefully nobody notices (1/8000 second?) + * (Pauline Middelink - 2002) */ + bzt->za[MAX_B_FRAMES].z1 = bzt->za[MAX_B_FRAMES].z2 + 1; + if (bzt->za[MAX_B_FRAMES].z1 >= B_FIFO_SIZE + B_SUB_VAL) + bzt->za[MAX_B_FRAMES].z1 -= B_FIFO_SIZE; bzt->f1 = MAX_B_FRAMES; bzt->f2 = bzt->f1; /* init F pointers to remain constant */ if (fifo_state)