Hi,
By the sip trace is very difficult to tell because the SIP messages are fine.
Try to enable all codec, and if possible copy and paste your asterisk sip
configuration for this peer.
Enviado do meu telefone Android usando o Symantec TouchDown (www.symantec.com)
-Original Message-
There's something weird at you linux system.
Your kernel sources are i686 sources, but the output of your ls shows you
are on a X86-64 system. (?)
lrwxrwxrwx 1 root root 54 Nov 6 23:31 build -
../../../usr/src/kernels/2.6.18-164.6.1.el5-xen-x86_64
Look here!
-bash-3.2# ls
Hi, it's not that simple.
It requires deep modification on asterisk and dahdi sources to work the way
you want.
Rafael Prado
-Original Message-
From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-
boun...@lists.digium.com] On Behalf Of Muro, Sam
Sent:
How many simultaneous channels?
Rafael Prado
-Original Message-
From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-
boun...@lists.digium.com] On Behalf Of Jim Dickenson
Sent: segunda-feira, 22 de março de 2010 2:33
To: Asterisk User MailList
Subject:
Or you can write your own application module.
Try looking at cdr_pgsql sources. ;)
Rafael Prado
+55 (11) 3323-1055
www.practis.com.br
PRACTIS - Comunicação Tecnologia
Av Aquidaban, 766 - Conj 51
CEP 13026-510, Campinas/SP - Brasil
-Original Message-
From:
Yes, it will catch congestion cases on the receiver side.
There's two ways to avoid it:
1) use ChanIsAvail on the dadhi channel. It works very well.
Or
2) Create a special signal for dahdi congestion (require modifying the
source and recompile) that differs from the congestion cause. Here we
