Quantcast
Channel: FreePBX Community Forums - Latest posts
Viewing all 226395 articles
Browse latest View live
↧

Upgrade to FreePBX 14 from 13 failing

August 15, 2017, 3:32 pm
$
0
0

The commands that the module runs are

/etc/init.d/dahdi stop
/etc/init.d/dahdi status
/etc/init.d/dahdi start

The output of status is an exit code retrieved from running echo $? after the command is executed.

When exit code is === 3 then start is run. if exit code is === 0 then dahdi is already running.

[root@freepbxdev1 zulu]# /etc/init.d/dahdi status
[root@freepbxdev1 zulu]# echo $?
0
[root@freepbxdev1 zulu]# /etc/init.d/dahdi stop
Unloading DAHDI hardware modules: done
[root@freepbxdev1 zulu]# /etc/init.d/dahdi status
[root@freepbxdev1 zulu]# echo $?
3
[root@freepbxdev1 zulu]# /etc/init.d/dahdi start
Loading DAHDI hardware modules:
  wct4xxp:                                                 [  OK  ]
  wcte43x:                                                 [  OK  ]
  wcte12xp:                                                [  OK  ]
  wcte13xp:                                                [  OK  ]
  wct1xxp:                                                 [  OK  ]
  wcte11xp:                                                [  OK  ]
  r1t1:                                                    [  OK  ]
  rxt1:                                                    [  OK  ]
  wctdm24xxp:                                              [  OK  ]
  wcaxx:                                                   [  OK  ]
  wcfxo:                                                   [  OK  ]
  wctdm:                                                   [  OK  ]
  rcbfx:                                                   [  OK  ]
  wcb4xxp:                                                 [  OK  ]
  wctc4xxp:                                                [  OK  ]
  xpp_usb:                                                 [  OK  ]

Running dahdi_cfg:                                         [  OK  ]
[root@freepbxdev1 zulu]# echo $?
0

Status codes of 0 or 3 are determined by the following code in /etc/init.d/dahdi

    if [ -d /proc/dahdi ]; then
            /usr/sbin/lsdahdi
            RETVAL=0
    else
            RETVAL=3
    fi

This part of the code checks if the folder /proc/dahdi exists. If it does then it executes /usr/sbin/lsdahdi

↧
Search

Upgrade to FreePBX 14 from 13 failing

August 15, 2017, 3:45 pm
$
0
0

Looks like dahdi stop isn't working correctly:

[root@freepbx ~]# /etc/init.d/dahdi status
### Span  1: WCTDM/4 "Wildcard TDM400P REV I Board 5" (MASTER)
  1 FXO        FXSKS       (In use) (EC: OSLEC - INACTIVE)
  2 FXS        FXOKS       (In use) (EC: OSLEC - INACTIVE)
  3 FXS        FXOKS       (In use) (EC: OSLEC - INACTIVE)
  4 FXO        FXSKS       (In use) (EC: OSLEC - INACTIVE)  RED
[root@freepbx ~]# echo $?
0
[root@freepbx ~]# /etc/init.d/dahdi stop
Stopping dahdi (via systemctl):                            [  OK  ]
[root@freepbx ~]# /etc/init.d/dahdi status
### Span  1: WCTDM/4 "Wildcard TDM400P REV I Board 5" (MASTER)
  1 FXO        FXSKS       (In use) (EC: OSLEC - INACTIVE)
  2 FXS        FXOKS       (In use) (EC: OSLEC - INACTIVE)
  3 FXS        FXOKS       (In use) (EC: OSLEC - INACTIVE)
  4 FXO        FXSKS       (In use) (EC: OSLEC - INACTIVE)  RED
[root@freepbx ~]# echo $?
0
[root@freepbx ~]# /etc/init.d/dahdi start
Starting dahdi (via systemctl):                            [  OK  ]
[root@freepbx ~]# echo $?
0
[root@freepbx ~]#

Why might that be? Could it be that I do have two instances of dahdi running, as @tonyclewis has suggested?

Also, when I'm stopping and starting dahdi, it's being done via systemctl on my system. This is different to what @tm1000 is reporting. Why would that be? I don't see the text 'Loading DAHDI hardware modules' when I start DAHDI, although I can see this text in the /etc/init.d/dahdi script file.

↧
↧

Is it possible to revert a specific pcode in base file in EPM?

August 15, 2017, 4:06 pm
$
0
0

hi, i modified a pcode in my base file, but now I want it set back to what it defaulted to, as i do not know what that is, is there a way to tell EPM to default just the one code (not the whole base file)?

thanks

↧

New FreePBX Build - No registrations?

August 15, 2017, 4:15 pm
$
0
0

Hi all, I'm building a new FreePBX using 14 and pjsip for the first time. I quickly/successfully registered 2 phones with zero problems and internal calling works perfectly. Just curious (not a big deal) but when I check Reports/pjsip info I see:

PJSip Registrations: 0
PJSip Endpoints:
Available: 2
Unavailable: 0
Unknown: 2

How should I interpret this? I suppose I do have 2 phones available but what is unknown? Shouldn't I have Registrations of 2 instead of 0?

Thanks!

↧

Upgrade to FreePBX 14 from 13 failing

August 15, 2017, 4:19 pm
$
0
0

Because I am showing how it works on CentOS 6.6 we are already discussing this. At this time it seems like a Digium issue with dahdi-tools in CentOS 7

↧
↧

Upgrade to FreePBX 14 from 13 failing

August 15, 2017, 4:22 pm
$
0
0

Ah. ok. I also made a further edit to my previous post, but your response probably answers that too. Really appreciate your support on this.

↧

Upgrade to FreePBX 14 from 13 failing

August 15, 2017, 4:28 pm
$
0
0

Unfortunately I can no longer replicate the issue on my Sangoma 7 distro.

/etc/init.d/dahdi redirects to systemd and that works 100% fine.

In fact both commands work fine now. It's not a digium issue it appears to be an issue with your unsupported card I think.

[root@freepbxdev4 ~]# /etc/init.d/dahdi start
Starting dahdi (via systemctl):                            [  OK  ]
[root@freepbxdev4 ~]# /etc/init.d/dahdi stop
Stopping dahdi (via systemctl):                            [  OK  ]
[root@freepbxdev4 ~]# /etc/init.d/dahdi status
[root@freepbxdev4 ~]# echo $?
3
[root@freepbxdev4 ~]# /etc/init.d/dahdi status
[root@freepbxdev4 ~]# echo $?
3
[root@freepbxdev4 ~]# systemctl stop dahdi
[root@freepbxdev4 ~]# systemctl status dahdi
● dahdi.service - LSB: DAHDI kernel modules
   Loaded: loaded (/etc/rc.d/init.d/dahdi; bad; vendor preset: disabled)
   Active: inactive (dead) since Tue 2017-08-15 16:27:09 PDT; 5s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 22523 ExecStop=/etc/rc.d/init.d/dahdi stop (code=exited, status=0/SUCCESS)
  Process: 22386 ExecStart=/etc/rc.d/init.d/dahdi start (code=exited, status=0/SUCCESS)

Aug 15 16:26:57 freepbxdevxxxxx.com dahdi[22386]: wctdm:  [  OK  ]
Aug 15 16:26:57 freepbxdevxxxxx.com dahdi[22386]: rcbfx:  [  OK  ]
Aug 15 16:26:57 freepbxdevxxxxx.com dahdi[22386]: wcb4xxp:  [  OK  ]
Aug 15 16:26:57 freepbxdevxxxxx.com dahdi[22386]: wctc4xxp:  [  OK  ]
Aug 15 16:26:57 freepbxdevxxxxx.com dahdi[22386]: xpp_usb:  [  OK  ]
Aug 15 16:26:57 freepbxdevxxxxx.com dahdi[22386]: Running dahdi_cfg:  [  OK  ]
Aug 15 16:26:57 freepbxdevxxxxx.com systemd[1]: Started LSB: DAHDI kernel modules.
Aug 15 16:27:07 freepbxdevxxxxx.com systemd[1]: Stopping LSB: DAHDI kernel modules...
Aug 15 16:27:09 freepbxdevxxxxx.com dahdi[22523]: Unloading DAHDI hardware modules: done
Aug 15 16:27:09 freepbxdevxxxxx.com systemd[1]: Stopped LSB: DAHDI kernel modules.
[root@freepbxdev4 ~]# systemctl start dahdi
[root@freepbxdev4 ~]# systemctl status dahdi
● dahdi.service - LSB: DAHDI kernel modules
   Loaded: loaded (/etc/rc.d/init.d/dahdi; bad; vendor preset: disabled)
   Active: active (exited) since Tue 2017-08-15 16:27:20 PDT; 1s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 22523 ExecStop=/etc/rc.d/init.d/dahdi stop (code=exited, status=0/SUCCESS)
  Process: 22729 ExecStart=/etc/rc.d/init.d/dahdi start (code=exited, status=0/SUCCESS)

Aug 15 16:27:19 freepbxdevxxxxx.com dahdi[22729]: wctdm24xxp:  [  OK  ]
Aug 15 16:27:19 freepbxdevxxxxx.com dahdi[22729]: wcaxx:  [  OK  ]
Aug 15 16:27:19 freepbxdevxxxxx.com dahdi[22729]: wcfxo:  [  OK  ]
Aug 15 16:27:19 freepbxdevxxxxx.com dahdi[22729]: wctdm:  [  OK  ]
Aug 15 16:27:19 freepbxdevxxxxx.com dahdi[22729]: rcbfx:  [  OK  ]
Aug 15 16:27:19 freepbxdevxxxxx.com dahdi[22729]: wcb4xxp:  [  OK  ]
Aug 15 16:27:19 freepbxdevxxxxx.com dahdi[22729]: wctc4xxp:  [  OK  ]
Aug 15 16:27:19 freepbxdevxxxxx.com dahdi[22729]: xpp_usb:  [  OK  ]
Aug 15 16:27:20 freepbxdevxxxxx.com dahdi[22729]: Running dahdi_cfg:  [  OK  ]
Aug 15 16:27:20 freepbxdevxxxxx.com systemd[1]: Started LSB: DAHDI kernel modules.
[root@freepbxdev4 ~]# echo $?
0
[root@freepbxdev4 ~]# /etc/init.d/dahdi status
[root@freepbxdev4 ~]# echo $?
0
↧

New FreePBX Build - No registrations?

August 15, 2017, 4:33 pm
$
0
0

That would be outbound registrations to a sip provider or pbx.

↧
Search

Is it possible to revert a specific pcode in base file in EPM?

August 15, 2017, 4:42 pm
$
0
0

Delete your modification and it will go back to default.

↧
↧

Upgrade to FreePBX 14 from 13 failing

August 15, 2017, 4:52 pm
$
0
0

I can get the same (or very similar) response on my system. However, DAHDI still isn't starting correctly on boot, and by doing a few things in a different sequence, I can get myself into a position where I can't stop DAHDI after having started it. Whilst it may be a compatibility issue with my card, all I can say is that it worked perfectly before I tried to upgrade.

[root@freepbx ~]# /etc/init.d/dahdi start
Starting dahdi (via systemctl):                            [  OK  ]
[root@freepbx ~]# /etc/init.d/dahdi stop
Stopping dahdi (via systemctl):                            [  OK  ]
[root@freepbx ~]# /etc/init.d/dahdi status
[root@freepbx ~]# echo $?
3
[root@freepbx ~]# /etc/init.d/dahdi status
[root@freepbx ~]# echo $?
3
[root@freepbx ~]# systemctl stop dahdi
[root@freepbx ~]# systemctl status dahdi
● dahdi.service - LSB: DAHDI kernel modules
   Loaded: loaded (/etc/rc.d/init.d/dahdi; bad; vendor preset: disabled)
   Active: inactive (dead)
     Docs: man:systemd-sysv-generator(8)

Aug 16 00:41:26 freepbx.xxx.co.uk dahdi[4237]: r1t1:  [  OK  ]
Aug 16 00:41:26 freepbx.xxx.co.uk dahdi[4237]: rxt1:  [  OK  ]
Aug 16 00:41:26 freepbx.xxx.co.uk dahdi[4237]: rcbfx:  [  OK  ]
Aug 16 00:41:26 freepbx.xxx.co.uk dahdi[4237]: D: auto '/sys/bus/dahdi_devices/devices/pci:0000:03:00.0'
Aug 16 00:41:26 freepbx.xxx.co.uk dahdi[4237]: auto-assign /sys/bus/dahdi_devices/devices/pci:0000:03:00.0
Aug 16 00:41:26 freepbx.xxx.co.uk dahdi[4237]: Running dahdi_cfg:  [  OK  ]
Aug 16 00:41:26 freepbx.xxx.co.uk systemd[1]: Started LSB: DAHDI kernel modules.
Aug 16 00:41:31 freepbx.xxx.co.uk systemd[1]: Stopping LSB: DAHDI kernel modules...
Aug 16 00:41:32 freepbx.xxx.co.uk dahdi[4354]: Unloading DAHDI hardware modules: done
Aug 16 00:41:32 freepbx.xxx.co.uk systemd[1]: Stopped LSB: DAHDI kernel modules.
[root@freepbx ~]# systemctl start dahdi
[root@freepbx ~]# systemctl status dahdi
● dahdi.service - LSB: DAHDI kernel modules
   Loaded: loaded (/etc/rc.d/init.d/dahdi; bad; vendor preset: disabled)
   Active: active (exited) since Wed 2017-08-16 00:45:24 BST; 5s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 4952 ExecStart=/etc/rc.d/init.d/dahdi start (code=exited, status=0/SUCCESS)

Aug 16 00:45:24 freepbx.xxx.co.uk dahdi[4952]: wcb4xxp:  [  OK  ]
Aug 16 00:45:24 freepbx.xxx.co.uk dahdi[4952]: wctc4xxp:  [  OK  ]
Aug 16 00:45:24 freepbx.xxx.co.uk dahdi[4952]: xpp_usb:  [  OK  ]
Aug 16 00:45:24 freepbx.xxx.co.uk dahdi[4952]: r1t1:  [  OK  ]
Aug 16 00:45:24 freepbx.xxx.co.uk dahdi[4952]: rxt1:  [  OK  ]
Aug 16 00:45:24 freepbx.xxx.co.uk dahdi[4952]: rcbfx:  [  OK  ]
Aug 16 00:45:24 freepbx.xxx.co.uk dahdi[4952]: D: auto '/sys/bus/dahdi_devices/devices/pci:0000:03:00.0'
Aug 16 00:45:24 freepbx.xxx.co.uk dahdi[4952]: auto-assign /sys/bus/dahdi_devices/devices/pci:0000:03:00.0
Aug 16 00:45:24 freepbx.xxx.co.uk dahdi[4952]: Running dahdi_cfg:  [  OK  ]
Aug 16 00:45:24 freepbx.xxx.co.uk systemd[1]: Started LSB: DAHDI kernel modules.
[root@freepbx ~]# echo $?
0
[root@freepbx ~]# /etc/init.d/dahdi status
### Span  1: WCTDM/4 "Wildcard TDM400P REV I Board 5" (MASTER)
  1 FXO        FXSKS       (EC: OSLEC - INACTIVE)
  2 FXS        FXOKS       (EC: OSLEC - INACTIVE)
  3 FXS        FXOKS       (EC: OSLEC - INACTIVE)
  4 FXO        FXSKS       (EC: OSLEC - INACTIVE)  RED
[root@freepbx ~]# echo $?
0
[root@freepbx ~]#
↧

Upgrade to FreePBX 14 from 13 failing

August 15, 2017, 5:06 pm
$
0
0

Interestingly, '/etc/init.d/dahdi status' and 'systemctl status dahdi' give different results on boot:

[root@freepbx ~]# /etc/init.d/dahdi status
[root@freepbx ~]# echo $?
0
[root@freepbx ~]# systemctl status dahdi
● dahdi.service - LSB: DAHDI kernel modules
   Loaded: loaded (/etc/rc.d/init.d/dahdi; bad; vendor preset: disabled)
   Active: inactive (dead)
     Docs: man:systemd-sysv-generator(8)
[root@freepbx ~]# echo $?
3
[root@freepbx ~]# /etc/init.d/dahdi status
[root@freepbx ~]# echo $?
0
[root@freepbx ~]# systemctl status dahdi
● dahdi.service - LSB: DAHDI kernel modules
   Loaded: loaded (/etc/rc.d/init.d/dahdi; bad; vendor preset: disabled)
   Active: inactive (dead)
     Docs: man:systemd-sysv-generator(8)
[root@freepbx ~]# echo $?
3
[root@freepbx ~]#
↧

Llamadas de salida se cortan a los 15 min

August 15, 2017, 5:36 pm
$
0
0

Esa es la causa por la cual se esta cortando la llamada. Mas de 30 segundos de inactividad RTP

↧

Failover Internet Programming

August 15, 2017, 6:39 pm
$
0
0

Hi there,
can you explain a bit more about what your trying to accomplish? I see the title of your post is "Failover Internet Programming", are you trying to use 2 wan connections for redundancy?

↧
↧

Call Center Stat tools

August 15, 2017, 6:42 pm
$
0
0

qxact is really nice, we use it pretty heavily. We did initially try asternic but it did not provide some of the functionality that qxact did.

↧

Can't run updates!

August 15, 2017, 6:57 pm
↧
Search

Latest update ruins XMPP

August 15, 2017, 7:03 pm
$
0
0

Odd. Active Directory is working fine for everything else (user / group creation and deletion, UCP authentication, etc.). Active Directory users don't get the XMPP icon in UCP; local users do (yes, the per-user XMPP settings were checked). I don't even know where to begin troubleshooting this issue... if it's too crazy to address in the forums, let me know and I'll buy some support time.

↧

Can't run updates!

August 15, 2017, 7:07 pm
$
0
0

Second problem I just noticed. After logging off (the console) I can't login again. I just get a blank cursor.

↧
↧

Update modules, HD full, system down. :(

August 15, 2017, 8:03 pm
$
0
0

Good evening, all (well, at least for some it might be)...

Ran an all module update this evening, and apparently in the middle of it, the HD became 100% full, causing the update to fail. Once I figured out what was causing it, I was able to remove the excess logs and clear space, but by then the update had already been stopped and the system is now essentially down.

Running the fwconsole command merely responds with:
SELECT value FROM admin WHERE variable = 'version'

SQLSTATE[HY000]: General error: 1017 Can't find file: 'admin' (errno: 2)::

My hope was to try installing all modules again (with a FORCE switch), but that's all contingent upon "fwconsole", which fails. I then thought, well maybe I can run the upgrade script, but that also failed because it essentially updates the modules via "fwconsole".

Does anyone have any thoughts on this one?

Thanks.

↧

Configuring a DTA 310/BVA8051 for Asterisk

August 15, 2017, 9:41 pm
$
0
0

You're welcome! I know how much time I spent researching and tinkering to make such a relatively simple thing work, and I just want to save other people the same grief I went through!

↧

My solution for implementing Flowroute SMS into Asterisk

August 15, 2017, 9:50 pm
$
0
0

The dialplan script I am using was actually written by Sanjay WS from code I found on this link, and then modified to split outgoing messages into extension-to-extension IMs and outgoing SMS messages. So by design it does just what you suggested; it allows incoming messages to be queued until the recipient's extension is available to receive the message.

↧
Viewing all 226395 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>