Please help,the asterisk crash

Discussion in 'General' started by kennethwu, Jul 10, 2009.

  1. kennethwu

    Joined:
    Jul 10, 2009
    Messages:
    15
    Likes Received:
    0
    After i have update the firmware from 1.3 to 1.5,my asterisk cannot run up,the error code is code1,do you know what it mean?
     
  2. Patrick_elx

    Joined:
    Dec 14, 2008
    Messages:
    1,120
    Likes Received:
    0
    could you please give us more info about the errors that you see.
    Go directly to your server to see all the messages.

    If you don't see anything try to reboot and look at the messages during the boot.
     
  3. kennethwu

    Joined:
    Jul 10, 2009
    Messages:
    15
    Likes Received:
    0
    I got a problem. My asterisk is configured,it can register softphones. When I trying to have a

    call,the call cannot translate the voice there but it can ring in and out,when i type core show

    translation,then it says :

    "unable to connect to remote asterisk (does /var/run/asterisk.ct1 exist?)"

    whats the problem and what do I need to do.
     
  4. gamba47

    Joined:
    May 28, 2009
    Messages:
    595
    Likes Received:
    0
    Please, por the result of :

    Console Mode:
    Code:
    tail -n 40 /var/log/asterisk/full
    try to start asterisk manually with :
    Code:
    /etc/init.d/asterisk restart
    Waiting for your comment

    gamba47
     
  5. kennethwu

    Joined:
    Jul 10, 2009
    Messages:
    15
    Likes Received:
    0
    [root@elastix ~]# tail -n 40 /var/log/asterisk/full
    [Jul 13 11:29:38] VERBOSE[3203] logger.c: Asterisk Event Logger Started /var/log/asterisk/event_log
    [Jul 13 11:29:38] ERROR[3203] asterisk.c: Asterisk has detected a problem with your Zaptel configuration and will shutdown for your protection. You have options:
    1. You only have to compile Zaptel support into Asterisk if you need it. One option is to recompile without Zaptel support.
    2. You only have to load Zaptel drivers if you want to take advantage of Zaptel services. One option is to unload zaptel modules if you don't need them.
    3. If you need Zaptel services, you must correctly configure Zaptel.
    [Jul 13 11:29:41] VERBOSE[3223] logger.c: Asterisk Event Logger Started /var/log/asterisk/event_log
    [Jul 13 11:29:41] ERROR[3223] asterisk.c: Asterisk has detected a problem with your Zaptel configuration and will shutdown for your protection. You have options:
    1. You only have to compile Zaptel support into Asterisk if you need it. One option is to recompile without Zaptel support.
    2. You only have to load Zaptel drivers if you want to take advantage of Zaptel services. One option is to unload zaptel modules if you don't need them.
    3. If you need Zaptel services, you must correctly configure Zaptel.
    [Jul 13 11:29:42] VERBOSE[3247] logger.c: Asterisk Event Logger Started /var/log/asterisk/event_log
    [Jul 13 11:29:42] ERROR[3247] asterisk.c: Asterisk has detected a problem with your Zaptel configuration and will shutdown for your protection. You have options:
    1. You only have to compile Zaptel support into Asterisk if you need it. One option is to recompile without Zaptel support.
    2. You only have to load Zaptel drivers if you want to take advantage of Zaptel services. One option is to unload zaptel modules if you don't need them.
    3. If you need Zaptel services, you must correctly configure Zaptel.
    [Jul 13 11:35:54] VERBOSE[3070] logger.c: Asterisk Event Logger Started /var/log/asterisk/event_log
    [Jul 13 11:35:55] ERROR[3070] asterisk.c: Asterisk has detected a problem with your Zaptel configuration and will shutdown for your protection. You have options:
    1. You only have to compile Zaptel support into Asterisk if you need it. One option is to recompile without Zaptel support.
    2. You only have to load Zaptel drivers if you want to take advantage of Zaptel services. One option is to unload zaptel modules if you don't need them.
    3. If you need Zaptel services, you must correctly configure Zaptel.
    [Jul 13 11:35:59] VERBOSE[3219] logger.c: Asterisk Event Logger Started /var/log/asterisk/event_log
    [Jul 13 11:35:59] ERROR[3219] asterisk.c: Asterisk has detected a problem with your Zaptel configuration and will shutdown for your protection. You have options:
    1. You only have to compile Zaptel support into Asterisk if you need it. One option is to recompile without Zaptel support.
    2. You only have to load Zaptel drivers if you want to take advantage of Zaptel services. One option is to unload zaptel modules if you don't need them.
    3. If you need Zaptel services, you must correctly configure Zaptel.
    [Jul 13 11:36:00] VERBOSE[3280] logger.c: Asterisk Event Logger Started /var/log/asterisk/event_log
    [Jul 13 11:36:00] ERROR[3280] asterisk.c: Asterisk has detected a problem with your Zaptel configuration and will shutdown for your protection. You have options:
    1. You only have to compile Zaptel support into Asterisk if you need it. One option is to recompile without Zaptel support.
    2. You only have to load Zaptel drivers if you want to take advantage of Zaptel services. One option is to unload zaptel modules if you don't need them.
    3. If you need Zaptel services, you must correctly configure Zaptel.
    [Jul 13 11:36:03] VERBOSE[3301] logger.c: Asterisk Event Logger Started /var/log/asterisk/event_log
    [Jul 13 11:36:03] ERROR[3301] asterisk.c: Asterisk has detected a problem with your Zaptel configuration and will shutdown for your protection. You have options:
    1. You only have to compile Zaptel support into Asterisk if you need it. One option is to recompile without Zaptel support.
    2. You only have to load Zaptel drivers if you want to take advantage of Zaptel services. One option is to unload zaptel modules if you don't need them.
    3. If you need Zaptel services, you must correctly configure Zaptel.
    [Jul 13 11:36:04] VERBOSE[3325] logger.c: Asterisk Event Logger Started /var/log/asterisk/event_log
    [Jul 13 11:36:04] ERROR[3325] asterisk.c: Asterisk has detected a problem with your Zaptel configuration and will shutdown for your protection. You have options:
    1. You only have to compile Zaptel support into Asterisk if you need it. One option is to recompile without Zaptel support.
    2. You only have to load Zaptel drivers if you want to take advantage of Zaptel services. One option is to unload zaptel modules if you don't need them.
    3. If you need Zaptel services, you must correctly configure Zaptel.


    Automatically restarting Asterisk.
    mpg123: no process killed
    Asterisk ended with exit status 1
    Asterisk died with code 1.
    Automatically restarting Asterisk.
    mpg123: no process killed
    Asterisk ended with exit status 1
    Asterisk died with code 1.
    Automatically restarting Asterisk.
    mpg123: no process killed
    Asterisk ended with exit status 1
    Asterisk died with code 1.
    Automatically restarting Asterisk.
    mpg123: no process killed
    Asterisk ended with exit status 1
    Asterisk died with code 1.
    Automatically restarting Asterisk.
    mpg123: no process killed
    Asterisk ended with exit status 1
    Asterisk died with code 1.
    Automatically restarting Asterisk.
    mpg123: no process killed
    Asterisk ended with exit status 1
    Asterisk died with code 1.
    Automatically restarting Asterisk.
    mpg123: no process killed
    Asterisk ended with exit status 1
    Asterisk died with code 1.
    Automatically restarting Asterisk.
    mpg123: no process killed
    Asterisk ended with exit status 1
    Asterisk died with code 1.
    Automatically restarting Asterisk.


    It seems not work,but i don't know why like this
     
  6. gamba47

    Joined:
    May 28, 2009
    Messages:
    595
    Likes Received:
    0
    Seems like zaptel is tryng to get work but he is unavailable on Elastix 1.5.2

    I don´t know how about solve it :S

    Patrick any idea ?

    gamba47
     
  7. Bob

    Bob

    Joined:
    Nov 4, 2007
    Messages:
    2,400
    Likes Received:
    1
    What Hardware interface card are you using??

    TDM400, TE122p, Sangoma, etc????

    What machine hardware are you using??

    Dell, HP, generic???

    It appears that it is not detecting your Zaptel hardware....

    Regards

    Bob
     

Share This Page