Quantcast
Channel: Commercial Products and Partners - FreePBX Community Forums
Viewing all 928 articles
Browse latest View live

How to delete old backups via SSH commands

$
0
0

@skitterlad wrote:

I rebooted by pbxact and got this

[root@uc-8****** ~]# fwconsole ma listonline
No repos specified, using: [commercial,unsupported,standard,extended] from last GUI settings

In GPG.class.php line 397:

Unable to trust the FreePBX Key! – {“stdout”:"",“stderr”:“gpg: error writi
ng to \/home\/asterisk\/.gnupg\/.#lk0x1******.uc-84******.12377': No space left on device\ngpg: Fatal: can't create lock for/home/asterisk/.gnup
g/trustdb.gpg’\n”,“status”:[],“exitcode”:2}

moduleadmin [-f|–force] [-d|–debug] [–edge] [–ignorecache] [–stable] [–col or] [–skipchown] [-e|–autoenable] [–skipdisabled] [–snapshot SNAPSHOT] [–fo rmat FORMAT] [-R|–repo REPO] [-t|–tag TAG] [–skipbreakingcheck] [–sendemail] [–onlystdout] [–] []…
[root@uc-84****** ~]# moduleadmin -f|–force
-bash: --force: command not found
-bash: moduleadmin: command not found

~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/SangomaVG-root 108G 108G 20K 100% /
devtmpfs 1.8G 0 1.8G 0% /dev
tmpfs 1.8G 0 1.8G 0% /dev/shm
tmpfs 1.8G 8.7M 1.8G 1% /run
tmpfs 1.8G 0 1.8G 0% /sys/fs/cgroup
/dev/sda1 1.9G 106M 1.7G 6% /boot
tmpfs 369M 0 369M 0% /run/user/0

fdisk -l

Disk /dev/sda: 128.0 GB, 128035676160 bytes, 250069680 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x000e8eca

Device Boot Start End Blocks Id System
/dev/sda1 * 2048 4098047 2048000 83 Linux
/dev/sda2 4098048 250068991 122985472 8e Linux LVM

Disk /dev/mapper/SangomaVG-root: 115.7 GB, 115678904320 bytes, 225935360 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mapper/SangomaVG-swaplv1: 4160 MB, 4160749568 bytes, 8126464 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

The backups are hogging all the space, and i can not adjust the files via gui
I can navigate to
[root@uc-84544609 backup]# du -h | sort -h
3.9M ./Default_backup
7.0G ./Glendale
43G ./POMPs_Full_Backup
but to show the files and delete any old back ups is unknown to me.

what do i do, what commands to type. i can SSH into the device. thanks for any help you can give

Posts: 4

Participants: 2

Read full topic


FreePBX logo

PRI Question

PBXact 25 conference call muting

$
0
0

@gabosch wrote:

I have a customer who is using a PBXact 25 appliance. I’ve set them up with conference rooms and they sporadically report that when in conference calls, the parties are muted through no action of their own. They are using S505 phones, and the PBX has two NICs, one assigned with an external IP and the other with an internal IP that connects to their phone PoE switch. The PBXact is doing the DHCP. They say that after they reboot the phones, the muting issue goes away, but this has happened more than once in the last few weeks. Has anyone had an issue like this? I’m thinking it’s RTP related, but would like some advice on whether I’m wasting my time with that thinking. Thanks to anyone who responds.

Posts: 5

Participants: 3

Read full topic

HELP with PBXact

$
0
0

@bholler wrote:

This is my first deployment of freepbx/pbxact. It isnt as easy as digium switchvox I am used to. However, I see this as a learning curve.

I have 2 issues; Phonebook Directory and Permission to var/www/html

Phonebook Directory; I have read lots of articles and I realised there must be xml file for the IPPhones. I got some on this forum and I have tried to implement them. In doing that, I encountered the 2nd problem.

var/www/html permisssion; I uploaded the the php file for yealink and i could not execute the file. Also, I cannot view the dirctory on my browser - http://pbx-ipaddress/phonebook. I tried using the provisioning port http://pbx-ipaddress:84/phonebook. I always get error 404.

I need urgent help in resolving this. This project must be delivered on Monday 13th July 2020.

PLS HELP!!!

PS: I am using PBXact

Posts: 5

Participants: 3

Read full topic

Paid support

$
0
0

@joethegeek wrote:

Hi,

i am looking for occasional paid support / maintenance.
I know about Sangoma Support packages. Are there any other options?

Posts: 3

Participants: 3

Read full topic

Error de activación

$
0
0

@pepejjra wrote:

No puedo activar el equipo, estaba activado, el equipo es un freepbx 100
el único cambio que le hice fue habilitar otra interface y me desactivo el sistema

System Admin
System Activation
Your machine must be activated to install Commercial Modules. Note that some Free modules are classified as Commercial and require your machine to be activated.
This machine is not currently activated.
Would you like to activate this machine now? More information on Activation is available in the Wiki

por consola utilice:
fwconsole sysadmin activate deploymentid

obteniendo como resultado:
Attempting to activate against deployment ‘deploymentid’
Running /var/www/html/admin/modules/sysadmin/bin/activate_existing deploymentid
Asking for deployment deploymentid…Error!
Unable to track down your deployment

Posts: 2

Participants: 2

Read full topic

BLF Subscription for D-Series phones

$
0
0

@mdavenport wrote:

This thread appears because I received a direct message from @mcgrathr.

Unsolicited Direct Messages soliciting an answer to a question aren’t a good idea on a community forum, because, if you send such a thing, it means that you’re relying on one single person to see your question, and for that one single person to provide a response to that question. A community forum is most beneficial when questions are asked publicly, so that anyone can respond, and so that anyone else who stumbles on the same question in the future, can see those responses.

That said, the gist of the question, as I understand it, is, given that one is writing their own configuration files for a D-Series phone, and where they’d like to load some contacts onto the phone so that they show up in the Contacts app, and where they’d like one or more of those contacts to be mapped to BLF keys, and where, crucially, they’d like the LED indicators on the phone to do things depending on the device state of the mapped contact…

“how do I make that last bit happen?”

or so to speak.

Per:
https://wiki.asterisk.org/wiki/display/DIGIUM/Contacts
under the “Rapid Dial Keys” section, there’s a note that says:

Rapid Dial, or BLF, key subscriptions are set using the phone configuration parameter:

* blf_contact_group

This parameter, whether configured in res_digium_phone.conf for DPMA or in the blf_contact_group setting in XML,  **must**  be set to the group_name of the contacts group for which you wish subscriptions to be made.  Subscriptions  **cannot**  be made to more than one group_name.  Subscriptions  **will not be made**  if the blf_contact_group parameter is undefined. If you have skipped this step, you  **will not**  have blinking lights.  The use of Smart BLF capabilities is not independent of this setting; this setting  **must**  still be used for deployments using Smart BLF BLF Items lists.

So, make sure your blf_contact_group setting in the phone’s config matches the contacts group_name from your contacts file, for the items which you want SUBSCRIBEs to happen.

And, of course, you’ll need to actually set the subscribe_to setting within the contact itself, so that the phone knows where to subscribe.

Posts: 1

Participants: 1

Read full topic


Transfer Deployment ID

$
0
0

@thehammer86 wrote:

Hello,

I would like to get a fresh deployment of FreePBX up and running before I transfer over my licenses, users, endpoints, etc. I currently have no zend-resets remaining and understand I will have to go through support to have it reset again. The whole deployment ID and activation process is find of awkward.

Is it possible to switch the deployment ID of a particular FreePBX instance?

Posts: 4

Participants: 2

Read full topic

Sangoma support hours

$
0
0

@FreerPBXer wrote:

We ran into a show-stopper issue with a v13 to v15 upgrade yesterday at about 4:00 PM Pacific Time (GMT -7). I opened a level 3 severity ticket at that time.

I got an email at 4:19 AM and a phone call at 5:45 AM from the assigned support engineer in Argentina, GMT -3. He work 9-6, so goes off shift at 2:00 PM my time. The Sangoma support phone number goes dark at 3:00 PM our time, I think.

Is there any way, when creating a ticket, we can get it assigned to an engineer who is at least in the same time zone so there is better chance of working critical issues immediately, or at least a bigger overlap of working hours?

Posts: 2

Participants: 2

Read full topic

Digium/Sangoma D65, EPM, issues with echo, NTP, and "Dial Entry Timeout"

$
0
0

@jcbdmd wrote:

Total newb. Read some of the recommendtions on here about the digium/sangoma d65 and decided to try a few, and it feels much nicer to me all around than my sangoma s505 and certainly better than my AAastra phones.

However I am having some problems with NTP, their configs, EPM and also a possible codec/echo problem.

Does anyone have a cookbook of all the things to set this phone up with freepbx 15/Asterisk 16 using PJSIP?

Posts: 1

Participants: 1

Read full topic

Vega Gateway Manager - IP X.X.X.X is not a Vega Gateway error

$
0
0

@NDSiouxFan wrote:

I just installed a new install of FreePBX v15.0.16.72. Pulled an old Vega 60 off the shelf and did a factory reset and firmware update to VegaARM_R120S013. Go to Vega Gateway Manager and type in the IP address and Admin credentials and I get the error “IP= X.X.X.X is not a Vega Gateway. please recheck IP or network connectivity.” All my network settings are OK. I can get into the Vega Gateway via browser. Any ideas?

Posts: 3

Participants: 1

Read full topic

FreePBX 15 Unable to Activate

$
0
0

@Anointedone wrote:

HI,

I have just migrated my FreePBX 15 to AWS. However, upon cilcking “activate”, nothing happens. The page refreshes and remains as was.

Could you advise please.

Thank you!

Posts: 3

Participants: 2

Read full topic

Isymphony update broke desktop client

$
0
0

@joethegeek wrote:

Hope someone can help me out.

We run isymphony Desktop client.
after update to iSymphony v3.5.9.8 the Desktop client shows the dreaded big red banner at the top.

The documentation recommends CTRL+F5, but does not help, crtl-r does not either

uninstall and reinstall desktop client still red banner,

I logged a support ticket with getIsymphony,

maybe someone here has solved the problem, let me know.

Posts: 2

Participants: 2

Read full topic

Vega 60G FXO not sending DTMF tones to external IVR's after call is connected

$
0
0

@cray27249 wrote:

This is my first Vega Gateway that I have worked with. I have a Vega 60G 4 port FXO gateway. I can make and receive phone calls. However when I call an external IVR it will not pass any DTMF tones. DTMF tones can be received over gateway, just not sent. I used wireshark to confirm my freepbx was generating the tones. I can not find anything in the documentation about this. My apologies if this is not in the correct forum.

Vega 60Gv2
VEGAARMv2_R120S001.48

Posts: 2

Participants: 2

Read full topic


Incoming route to extension, not going to VM

$
0
0

@BradFacer wrote:

Sangoma PBXACT (14.0.3.26)
Few days ago customer says that incoming calls to a DID are ringing an extension as expected, but after NO ANSWER, the caller hears ‘please enter your area code and phone number’

I’ve checked the findme/followme settings and all looks correct. Setting the incoming route directly to their voicemail box does send it to the voicemail.
Internal calls act as normal- ring and if not answered they follow to the voicemail box

Any thoughts on what could have changed?
Thanks

Posts: 3

Participants: 3

Read full topic

PBXact 15 DAHDi missing from Asterisk Info report

$
0
0

@kgupta wrote:

Had to replace the drive in a PBXact 60 yesterday.
Loaded latest version of 15 (was previously on PBXact 13).
Everything appears to be working, but they use a PRI for their outside trunks and previously you could see the channels on the Asterisk Info page, but currently it isn’t there.

Calls seem to be working and DAHDi is running normally.
I can run ‘dahdi show channels’ from the Asterisk CLI page and see the channels, but it would be nice to see it in the Asterisk Info page still.

I tried uninstalling/re-installing the Asterisk Info module, but no change.
Has this been removed or is there something else going on here that can be fixed?

Posts: 4

Participants: 3

Read full topic

Assistance with Temporary Breaking BLF on Yealink Phone

$
0
0

@RTyrmida wrote:

Good Day,

I am having a BLF problem with a Yealink T48G handset.

Every 20 minutes, all the BLF lights disappear and come back a few seconds later.

In syslog on the Yealink unit I get an error saying:

Aug 14 11:29:33 192.168.2.36 [00:15:65:6f:1f:90] sua [1431]: SUB <4+warnin> [000] BLF Subscribe response is NULL

This repeats 5-6 times, and then the phone returns to normal.

The Yealink unit has firmware version: 35.83.0.50

I am using FreePBX 15.0.16.72 with commercial endpoint manager on Asterisk Asterisk 16.11.1

I would appreciate any assistance

I tried to post the asterisk logfile but the forum doesn’t allow me to post it because it detects links (not sure what part of it is a link).

Posts: 1

Participants: 1

Read full topic

FreePBX 15 Asterisk 16 Sangoma A104 SS7 Connection Problem

$
0
0

@pbyeoh wrote:

hi all,

i’ve been try to troubleshoot the problem with my freepbx 15 server (latest) in getting a solid link with ISUP via SS7.

Please could anyone give me pointers on how to resolve the issue i am facing? Thanks in advance.

Setup
HP ML380G5 Server
Sangoma A104 PRI E1 card
FreePBX 15
Asterisk 16
Dahdi (exist from distro)
Wanrouter (exist from distro)
LibSS7 (exist from distro)

system.conf
span=1,1,0,CCS,hdb3
span=2,2,0,CCS,hdb3
span=3,3,0,CCS,hdb3
span=4,4,0,CCS,hdb3
bchan=1-15,17-31,32-46,48-62,63-77,79-93,94-108,110-124
hardhdlc=16,47,78,109

chan-dahdi.conf
;autogenerated by /usr/sbin/wancfg_dahdi do not hand edit
;autogenrated on 2020-08-13
;Dahdi Channels Configurations
;For detailed Dahdi options, view /etc/asterisk/chan_dahdi.conf.bak

[trunkgroups]

[channels]
context=default
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
relaxdtmf=yes
rxgain=0.0
txgain=0.0
group=1
callgroup=1
pickupgroup=1
immediate=no

context=from-pstn
group=0
echocancel=no
;faxdetect=incoming

signaling=ss7 ;this is ss7 signaling
ss7type=itu ;using the ITU variant
defaultdpc=6000 ;the point code for the system that the CICs will be negotiated with…aka DPC
adjpointcode=6000 ;the point code for the system that we are signaling to… aka APC
pointcode=6021 ;the point code for this system…aka SPC
networkindicator=national ;NI value for MTP3
linkset=1 ;arbitrary name for this set of channels
ss7_called_nai=dynamic ;NAI for outgoing calls
ss7_calling_nai=dynamic ;NAI for incoming calls
ss7_internationalprefix=00 ;international prefix value for incoming calls
ss7_nationalprefix=33 ;national prefix value for incoming calls
ss7_subscriberprefix=3364 ;subscriber prefix value for incoming calls
ss7_unknownprefix= ;unknown prefix value for incoming calls
;ss7_explictacm=yes ;ACM is send as soon as call enters the dial plan…may not accepted yet though
ss7_autoacm=yes
;isup_timer.digittimeout=5000

sigchan=16
sigchan=47
sigchan=78
sigchan=109
cicbeginswith=1 ;the starting value of the CICs
channel=1-15 ;the channels that are CICs
cicbeginswith=17 ;the starting value of the CICs
channel=17-31 ;the channels that are CICs
;sigchan=16

cicbeginswith=32 ;the starting value of the CICs
channel=32-46 ;the channels that are CICs
cicbeginswith=48 ;the starting value of the CICs
channel=48-62 ;the channels that are CICs
;sigchan=47

cicbeginswith=63 ;the starting value of the CICs
channel=63-77 ;the channels that are CICs
cicbeginswith=79 ;the starting value of the CICs
channel=79-93 ;the channels that are CICs
;sigchan=78

cicbeginswith=94 ;the starting value of the CICs
channel=94-108 ;the channels that are CICs
cicbeginswith=110 ;the starting value of the CICs
channel=110-124 ;the channels that are CICs
;sigchan=109

wanpipe1.conf
[devices]
wanpipe1 = WAN_AFT_TE1, Comment

[interfaces]
w1g1 = wanpipe1, , TDM_VOICE, Comment

[wanpipe1]
CARD_TYPE = AFT
S514CPU = A
CommPort = PRI
AUTO_PCISLOT = NO
PCISLOT = 4
PCIBUS = 24
FE_MEDIA = E1
FE_LCODE = HDB3
FE_FRAME = CRC4
FE_LINE = 1
TE_CLOCK = NORMAL
TE_REF_CLOCK = 0
TE_HIGHIMPEDANCE = NO
TE_RX_SLEVEL = 430
LBO = 120OH
TE_SIG_MODE = CCS
FE_TXTRISTATE = NO
MTU = 1500
UDPPORT = 9000
TTL = 255
IGNORE_FRONT_END = NO
TDMV_SPAN = 1
TDMV_DCHAN = 0
TDMV_HW_DTMF = NO

[w1g1]
ACTIVE_CH = ALL
TDMV_ECHO_OFF = NO
TDMV_HWEC = NO

wanpipe2.conf
[devices]
wanpipe2 = WAN_AFT_TE1, Comment

[interfaces]
w2g1 = wanpipe2, , TDM_VOICE, Comment

[wanpipe2]
CARD_TYPE = AFT
S514CPU = A
CommPort = PRI
AUTO_PCISLOT = NO
PCISLOT = 4
PCIBUS = 24
FE_MEDIA = E1
FE_LCODE = HDB3
FE_FRAME = CRC4
FE_LINE = 2
TE_CLOCK = NORMAL
TE_REF_CLOCK = 0
TE_HIGHIMPEDANCE = NO
TE_RX_SLEVEL = 430
LBO = 120OH
TE_SIG_MODE = CCS
FE_TXTRISTATE = NO
MTU = 1500
UDPPORT = 9000
TTL = 255
IGNORE_FRONT_END = NO
TDMV_SPAN = 2
TDMV_DCHAN = 0
TDMV_HW_DTMF = NO

[w2g1]
ACTIVE_CH = ALL
TDMV_ECHO_OFF = NO
TDMV_HWEC = NO

wanpipe3.conf
[devices]
wanpipe3 = WAN_AFT_TE1, Comment

[interfaces]
w3g1 = wanpipe3, , TDM_VOICE, Comment

[wanpipe3]
CARD_TYPE = AFT
S514CPU = A
CommPort = PRI
AUTO_PCISLOT = NO
PCISLOT = 4
PCIBUS = 24
FE_MEDIA = E1
FE_LCODE = HDB3
FE_FRAME = CRC4
FE_LINE = 3
TE_CLOCK = NORMAL
TE_REF_CLOCK = 0
TE_HIGHIMPEDANCE = NO
TE_RX_SLEVEL = 300
LBO = 120OH
TE_SIG_MODE = CCS
FE_TXTRISTATE = NO
MTU = 1500
UDPPORT = 9000
TTL = 255
IGNORE_FRONT_END = NO
TDMV_SPAN = 3
TDMV_DCHAN = 0
TDMV_HW_DTMF = NO

[w3g1]
ACTIVE_CH = ALL
TDMV_ECHO_OFF = NO
TDMV_HWEC = NO

wanpipe4.conf
[devices]
wanpipe4 = WAN_AFT_TE1, Comment

[interfaces]
w4g1 = wanpipe4, , TDM_VOICE, Comment

[wanpipe4]
CARD_TYPE = AFT
S514CPU = A
CommPort = PRI
AUTO_PCISLOT = NO
PCISLOT = 4
PCIBUS = 24
FE_MEDIA = E1
FE_LCODE = HDB3
FE_FRAME = CRC4
FE_LINE = 4
TE_CLOCK = NORMAL
TE_REF_CLOCK = 0
TE_HIGHIMPEDANCE = NO
TE_RX_SLEVEL = 430
LBO = 120OH
TE_SIG_MODE = CCS
FE_TXTRISTATE = NO
MTU = 1500
UDPPORT = 9000
TTL = 255
IGNORE_FRONT_END = NO
TDMV_SPAN = 4
TDMV_DCHAN = 0
TDMV_HW_DTMF = NO

[w4g1]
ACTIVE_CH = ALL
TDMV_ECHO_OFF = NO
TDMV_HWEC = NO

wanrouter status
Devices currently active:
wanpipe1 wanpipe2 wanpipe3 wanpipe4

Wanpipe Config:

Device name | Protocol Map | Adapter | IRQ | Slot/IO | If’s | CLK | Baud rate |
wanpipe4 | N/A | A101/1D/2/2D/4/4D/8/8D/16/16D| 19 | 4 | 1 | N/A | 0 |
wanpipe3 | N/A | A101/1D/2/2D/4/4D/8/8D/16/16D| 19 | 4 | 1 | N/A | 0 |
wanpipe2 | N/A | A101/1D/2/2D/4/4D/8/8D/16/16D| 19 | 4 | 1 | N/A | 0 |
wanpipe1 | N/A | A101/1D/2/2D/4/4D/8/8D/16/16D| 19 | 4 | 1 | N/A | 0 |

Wanrouter Status:

Device name | Protocol | Station | Status |
wanpipe4 | AFT TE1 | N/A | Connected |
wanpipe3 | AFT TE1 | N/A | Connected |
wanpipe2 | AFT TE1 | N/A | Connected |
wanpipe1 | AFT TE1 | N/A | Connected |

service dahdi status

Span 1: WPE1/0 “wanpipe1 card 0” CCS/HDB3

1 PRI Clear
2 PRI Clear
3 PRI Clear
4 PRI Clear
5 PRI Clear
6 PRI Clear
7 PRI Clear
8 PRI Clear
9 PRI Clear
10 PRI Clear
11 PRI Clear
12 PRI Clear
13 PRI Clear
14 PRI Clear
15 PRI Clear
16 PRI Hardware-assisted HDLC
17 PRI Clear
18 PRI Clear
19 PRI Clear
20 PRI Clear
21 PRI Clear
22 PRI Clear
23 PRI Clear
24 PRI Clear
25 PRI Clear
26 PRI Clear
27 PRI Clear
28 PRI Clear
29 PRI Clear
30 PRI Clear
31 PRI Clear

Span 2: WPE1/1 “wanpipe2 card 1” (MASTER) CCS/HDB3

32 PRI Clear
33 PRI Clear
34 PRI Clear
35 PRI Clear
36 PRI Clear
37 PRI Clear
38 PRI Clear
39 PRI Clear
40 PRI Clear
41 PRI Clear
42 PRI Clear
43 PRI Clear
44 PRI Clear
45 PRI Clear
46 PRI Clear
47 PRI Hardware-assisted HDLC
48 PRI Clear
49 PRI Clear
50 PRI Clear
51 PRI Clear
52 PRI Clear
53 PRI Clear
54 PRI Clear
55 PRI Clear
56 PRI Clear
57 PRI Clear
58 PRI Clear
59 PRI Clear
60 PRI Clear
61 PRI Clear
62 PRI Clear

Span 3: WPE1/2 “wanpipe3 card 2” CCS/HDB3 RED

63 PRI Clear
64 PRI Clear
65 PRI Clear
66 PRI Clear
67 PRI Clear
68 PRI Clear
69 PRI Clear
70 PRI Clear
71 PRI Clear
72 PRI Clear
73 PRI Clear
74 PRI Clear
75 PRI Clear
76 PRI Clear
77 PRI Clear
78 PRI Hardware-assisted HDLC RED
79 PRI Clear
80 PRI Clear
81 PRI Clear
82 PRI Clear
83 PRI Clear
84 PRI Clear
85 PRI Clear
86 PRI Clear
87 PRI Clear
88 PRI Clear
89 PRI Clear
90 PRI Clear
91 PRI Clear
92 PRI Clear
93 PRI Clear

Span 4: WPE1/3 “wanpipe4 card 3” CCS/HDB3 RED

94 PRI Clear
95 PRI Clear
96 PRI Clear
97 PRI Clear
98 PRI Clear
99 PRI Clear
100 PRI Clear
101 PRI Clear
102 PRI Clear
103 PRI Clear
104 PRI Clear
105 PRI Clear
106 PRI Clear
107 PRI Clear
108 PRI Clear
109 PRI Hardware-assisted HDLC RED
110 PRI Clear
111 PRI Clear
112 PRI Clear
113 PRI Clear
114 PRI Clear
115 PRI Clear
116 PRI Clear
117 PRI Clear
118 PRI Clear
119 PRI Clear
120 PRI Clear
121 PRI Clear
122 PRI Clear
123 PRI Clear
124 PRI Clear

dahdi show status
Description Alarms IRQ bpviol CRC Fra Codi Options LBO
wanpipe1 card 0 OK 0 0 0 CCS HDB3 0 db (CSU)/0-133 feet (DSX-1)
wanpipe2 card 1 OK 0 0 0 CCS HDB3 0 db (CSU)/0-133 feet (DSX-1)
wanpipe3 card 2 OK 0 0 0 CCS HDB3 0 db (CSU)/0-133 feet (DSX-1)
wanpipe4 card 3 OK 0 0 0 CCS HDB3 0 db (CSU)/0-133 feet (DSX-1)

ss7 show linkset 1
SS7 flags: 0x10
SS7 linkset 1 status: Down
SS7 calling nai: -1
SS7 called nai: -1
SS7 nationalprefix: 33
SS7 internationalprefix: 00
SS7 unknownprefix:
SS7 networkroutedprefix:
SS7 subscriberprefix: 3364
Switch type: ITU
Our point code: 6021
SLS shift: 0
numlinks: 4
numsps: 1

Adjacent SP PC: 6000 STATE: DOWN
TRA: T19: not running T21: not running
Routes:
DPC State T6 T10
Link ADJ_PC:SLC: 6000:0 NetMngSLS: 0
State: NOTALIGNED, ALIGNING
STD Test: failed
Got, sent :
Inhibit:
Changeover: NO
Tx buffer: 0
Tx queue: 0
Retrans pos 0
CO buffer: 0
CB buffer: 0
Last FSN: 127
MTP3timers:
Link ADJ_PC:SLC: 6000:1 NetMngSLS: 1
State: NOTALIGNED, ALIGNING
STD Test: failed
Got, sent :
Inhibit:
Changeover: NO
Tx buffer: 0
Tx queue: 0
Retrans pos 0
CO buffer: 0
CB buffer: 0
Last FSN: 127
MTP3timers:
Link ADJ_PC:SLC: 6000:2 NetMngSLS: 2
State: ALARM, INALARM
STD Test: failed
Got, sent :
Inhibit:
Changeover: NO
Tx buffer: 0
Tx queue: 0
Retrans pos 0
CO buffer: 0
CB buffer: 0
Last FSN: 127
MTP3timers:
Link ADJ_PC:SLC: 6000:3 NetMngSLS: 3
State: ALARM, INALARM
STD Test: failed
Got, sent :
Inhibit:
Changeover: NO
Tx buffer: 0
Tx queue: 0
Retrans pos 0
CO buffer: 0
CB buffer: 0
Last FSN: 127
MTP3timers:

Posts: 1

Participants: 1

Read full topic

System Instability after PBXact 15 Upgrade

$
0
0

@bryanredeagle wrote:

So on Tue evening, I upgraded our PBX to version 15 and moved Asterisk from 13 to 16. I then moved the existing extensions from chan_sip to pjsip.

The upgrade went smoothly and the next day saw no problems. Yesterday however has been a nightmare.

It started with calling issues. One user reported (and I was able to recreate) an issue where Asterisk was not responding to SIP requests quickly. sngrep showed that a device would send an invite 5 or 6 times before Asterisk replied to it. For our carrier, that was enough to be considered unresponsive and treated it as a downed system.

We restarted Asterisk a couple times and even rebooted the whole system, but the issue would return in 5-10 minutes after start up.

I figured since Asterisk was being slow to respond (and everything else including system resources looked normal), that it was something in Asterisk 16 that I had misunderstood or missed. So I downgraded the system to Asterisk 13 and ran into more instability in the form of phones refusing to stay registered. Two D80s (used by the Owner and VP) refused to register all together.

I thought I had found the issue with Asterisk 16 using some forum posts that indicated that the version switch script could sometimes leave old modules in that caused Asterisk to flip out. So I followed those instructions to remove all old modules and then install Asterisk 16.

So far the extensions are staying registered, but the D80s are still not registered.

I have three questions for you fine folks:

Whats a good method to track down this slow response if it happens again?

Are there any known issues that require a setting adjustment to keep Asterisk 16 working?

Is there a way to troubleshoot why the D80s are not configuring? I see them trying to send MESSAGE packets with certs, but Asterisk logs make it look like that Asterisk has no idea what to do with them and doesn’t respond. I do have the DPMA configured and licensed.

Thanks!

Posts: 1

Participants: 1

Read full topic

Viewing all 928 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>