Moises Silva wrote:
my mistake.
the line in the unicall.conf should be something like
loglevel=4
Hi Moises,
I search for a error message and found this thread in the list:
http://lists.digium.com/pipermail/asterisk-users/2006-April/148978.html
I'm having the same error here.
Do you have a
my mistake.
the line in the unicall.conf should be something like
loglevel=4
On 5/26/06, Moises Silva <[EMAIL PROTECTED]> wrote:
you can specify the logging level in unicall.conf
logleve=0-255
select a value from 0 to 8. According to unicall.h the levels are:
enum
{
UC_LOG_ERROR
you can specify the logging level in unicall.conf
logleve=0-255
select a value from 0 to 8. According to unicall.h the levels are:
enum
{
UC_LOG_ERROR= 1,
UC_LOG_WARNING = 2,
UC_LOG_PROTOCOL_ERROR = 3,
UC_LOG_PROTOCOL_WARNING = 4
Fernando Lujan wrote:
Steve Underwood wrote:
The problem is almost solved. The card was configured as a T1 interface,
the selled came and jumped it.
Now I have the following problem. When I call from my legacy pbx, appear
a event:
*CLI> May 26 12:04:09 WARNING[5215]: chan_unicall.c:627
Steve Underwood wrote:
Hi Steve, nice to hear from you. I spoke with you in the irc some time ago.
I'm trying to configure a TE406P with MFC/R2.
here goes my zaptel.conf:
span=1,0,0,ccs,hdb3,crc4
cas=1-15:1101
dchan=16
cas=17-31:1101
span=2,0,0,ccs,hdb3,crc4
cas=32-46:1101
dchan=47
cas=48
Fernando Lujan wrote:
Guys,
I'm trying to configure a TE406P with MFC/R2.
here goes my zaptel.conf:
span=1,0,0,ccs,hdb3,crc4
cas=1-15:1101
dchan=16
cas=17-31:1101
span=2,0,0,ccs,hdb3,crc4
cas=32-46:1101
dchan=47
cas=48-62:1101
That config is completely wrong. Try following the config in th
I would recommend you to use the "testcall" application that comes
with Unicall distribution. This application will allow you to isolate
the problem. You can stop the asterisk service and use only testcall
application with proper debug format (read the source of testcall.c),
that will tell you wha
Guys,
I'm trying to configure a TE406P with MFC/R2.
here goes my zaptel.conf:
span=1,0,0,ccs,hdb3,crc4
cas=1-15:1101
dchan=16
cas=17-31:1101
span=2,0,0,ccs,hdb3,crc4
cas=32-46:1101
dchan=47
cas=48-62:1101
The first strange behavior is that the:
zap show status
shows this:
Description
