Page 1 of 2 12 LastLast
Results 1 to 10 of 14

Thread: Unable to connect to remote asterisk

  1. #1

    Default Unable to connect to remote asterisk

    With two warp pika asterisk i have the same problem. With telnet command asterisk -rvvvvv i have the error message
    Unable to connect to remote asterisk ( does /var/run/asterisk/asterisk.ctl exist ?)

    But i can connect by http and i use the command cli by freepbx.

    Have you a solution ?

    Best Regards,
    Fabien

  2. #2

    Default

    Also I click on the button "Show Channels" of the menu "Warp System Administration" in FreePBX, i have the follow message :
    WARP Channel Status

    Unable to connect to remote asterisk (does /var/run/asterisk/asterisk.ctl exist?)

    Best Regards,
    Fabien

  3. #3
    Join Date
    Jul 2008
    Posts
    265

    Default

    Sounds like Asterisk is failing. Can you confirm Asterisk is started successfully?
    First I would suggest checking 'dmesg' to see if there are any errors. Also ensure you are starting asterisk/freepbx with the 'amportal start' command.

  4. #4

    Default

    Hi,

    Yes asterisk is running on the two pika warp .
    I included the dmesg in a file.

    Best Regards,
    Fabien
    Attached Files Attached Files

  5. #5

    Default

    How to resolve these problems, may be to reinstall the system but how, be careful with the problem attended transfer ?

    Best Regards,
    Fabien

  6. #6
    Join Date
    Jul 2008
    Posts
    265

    Default

    Perhaps the AMI interface is not working? Have you changed anything in manager.conf?
    Could you also include '/var/log/messages' from the unit?

  7. #7

    Default

    my /var/log/messages is

    Jan 4 08:15:53 warp syslog.info syslogd exiting
    Jan 1 00:01:20 warp user.info kernel: [ 121.588908] kjournald starting. Commit interval 5 seconds
    Jan 1 01:01:20 warp user.warn kernel: [ 121.608596] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
    Jan 1 01:01:20 warp user.info kernel: [ 121.621375] EXT3 FS on mmcblk0p1, internal journal
    Jan 1 01:01:20 warp user.info kernel: [ 121.626278] EXT3-fs: recovery complete.
    Jan 1 01:01:21 warp user.info kernel: [ 121.873795] EXT3-fs: mounted filesystem with writeback data mode.
    Jan 1 01:01:31 warp user.warn kernel: [ 132.038826] pikalcd: lcd_init_module
    Jan 4 09:18:22 warp user.warn kernel: [ 137.680279] pikahsp: module license 'PIKA Technologies Inc.' taints kernel.
    Jan 4 09:18:22 warp user.warn kernel: [ 137.687343] Disabling lock debugging due to kernel taint
    Jan 4 09:18:22 warp user.warn kernel: [ 137.714183] PIKA HSP Starting. HZ=1000.
    Jan 4 09:18:22 warp user.info kernel: [ 137.721219] pikacore: registered 253.0
    Jan 4 09:18:22 warp user.info kernel: [ 137.783085] taco: FPGA 00F13011
    Jan 4 09:18:22 warp user.info kernel: [ 137.786325] Modules A: FXO B: empty
    Jan 4 09:18:26 warp user.warn kernel: [ 138.299400] Performing Calibration. Please wait.
    Jan 4 09:18:26 warp user.warn kernel: [ 140.864808] Calibration Complete.
    Jan 4 09:18:26 warp user.info kernel: [ 141.015972] pikacore: registered 253.1
    Jan 4 09:18:26 warp user.info kernel: [ 141.140448] Zapata Telephony Interface Registered on major 196
    Jan 4 09:18:26 warp user.info kernel: [ 141.146344] Zaptel Version: 1.4.9.2
    Jan 4 09:18:26 warp user.warn kernel: [ 141.149866] Zaptel Echo Canceller: MG2
    Jan 4 09:18:26 warp user.warn kernel: [ 141.507874] pkdummy: init() finished
    Jan 1 00:01:00 warp user.info kernel: [ 101.162312] kjournald starting. Commit interval 5 seconds
    Jan 1 01:01:00 warp user.warn kernel: [ 101.177139] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
    Jan 1 01:01:00 warp user.info kernel: [ 101.189902] EXT3 FS on mmcblk0p1, internal journal
    Jan 1 01:01:00 warp user.info kernel: [ 101.194800] EXT3-fs: recovery complete.
    Jan 1 01:01:00 warp user.info kernel: [ 101.201857] EXT3-fs: mounted filesystem with writeback data mode.
    Jan 1 01:01:10 warp user.warn kernel: [ 111.602203] pikalcd: lcd_init_module
    Jan 4 10:14:07 warp user.warn kernel: [ 117.953307] pikahsp: module license 'PIKA Technologies Inc.' taints kernel.
    Jan 4 10:14:07 warp user.warn kernel: [ 117.960372] Disabling lock debugging due to kernel taint
    Jan 4 10:14:07 warp user.warn kernel: [ 117.987216] PIKA HSP Starting. HZ=1000.
    Jan 4 10:14:07 warp user.info kernel: [ 117.994434] pikacore: registered 253.0
    Jan 4 10:14:07 warp user.info kernel: [ 118.056266] taco: FPGA 00F13011
    Jan 4 10:14:07 warp user.info kernel: [ 118.059504] Modules A: FXO B: empty
    Jan 4 10:14:11 warp user.warn kernel: [ 118.585405] Performing Calibration. Please wait.
    Jan 4 10:14:11 warp user.warn kernel: [ 121.150849] Calibration Complete.
    Jan 4 10:14:11 warp user.info kernel: [ 121.295273] pikacore: registered 253.1
    Jan 4 10:14:11 warp user.info kernel: [ 121.422496] Zapata Telephony Interface Registered on major 196
    Jan 4 10:14:11 warp user.info kernel: [ 121.428404] Zaptel Version: 1.4.9.2
    Jan 4 10:14:11 warp user.warn kernel: [ 121.431919] Zaptel Echo Canceller: MG2
    Jan 4 10:14:11 warp user.warn kernel: [ 121.790051] pkdummy: init() finished

  8. #8

    Default

    Hi mrecoskie,


    The Asterisk server status is error in the FreePBX System Status. I shut down the pika warp without success.
    Therefore no alternative to it is no longer reachable by phone.
    I think the only solution is to upgrade to the last version with an usb key.
    How to make this please with the problem of the attended transfer ?

    Best Regards,
    Fabien SEUX

    PS: The telephony is a tool vital for this customer.

  9. #9
    Join Date
    Jul 2008
    Posts
    265

    Default

    If you are using 2.2.7 have you tried the following package?
    ftp://ftp.pikatech.com/outgoing/cust...erpatch227.tgz

  10. #10

    Default

    Hi mrecoskie,

    i don't know why that is the version 2.2.7.
    Is it possible an automatic upgrade by internet ?
    The only upgrade by an usb key it was the time so as to fix the problem with the attended transfer
    http://forum.pikatechnologies.com/sh...ended-transfer

    Best Regards,
    Fabien.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •