Search results

Hello, Unfortunately I can't pinpoint when exactly it started happening, but I think it was around 3-5 months ago. I keep a PuTTY window open that is SSH'd into the server, and I run: asterisk -rvvvvvvvv So that I can kind of keep an eye on the system. Anyway, around 3-5 months ago, I started...

Ooooohhhhh! Thank you sir!

Hello, I've got IncrediblePBX 13-13, with updates. I can't get into the web interface of 'Reminders'. I remember setting up the 'numerical password' for Reminders during the last part of setting up the system, and have that password recorded. However, I don't know what the username is when...

Well, it looks like this issue is fixed. After a couple more exchanged emails between me and VoIPSupply, they said the logs are showing that it looks like the Vega's are getting 'overloaded' (or something like that). Then in another email they asked me several questions: Then shortly after that...

I contacted tech support @ VoIPSupply.com. They got back to me pretty quickly actually, and their initial response was: Under the "FXO Hardware Profiles", ensure that "Full Scale" is disabled. This issue is occurring due to the impedance levels. I checked this and it was already disabled. I...

Oh man, I did not want to hear that. I'm going to contact VoIPSupply (where I got them from) to see what they say, but I'm hoping someone here can offer some additional insight.

I've got a strange problem happening on our phone system. Sometimes when we answer an incoming call, we hear a rapid succession of pulses (as in the old pulse dial pulses) for a second or two right after picking up the call. This is a new Incredible PBX 13-13.8 (Whole Enchilada) system that I...

Maybe this doesn't apply, but when you log into the console, it prompts you to do updates - did you try logging into the console and let it check for updates and install them? (At least this is how it works on the IncrediblePBX system I have. I didn't install on Ubuntu though - I installed the...

So I used the same phone for my next little test. I cleared the phone's log, then left myself a voicemail on the 1st line (the one that is connected to our older PBX-In-A-Flash system), and copied the phone's log: [5] 7/3/2019 15:52:12: rtp_port::set_port [6] 7/3/2019 15:52:12: Line-Seize...

Not sure if this helps at all, but I'm putting a piece of a log from one of the Snom phones below. I have the log level set to 7 currently. So I left a voicemail then immediately cleared the log. One thing to note is that this phone has 2 SIP extensions registered, both with the same extension...

Thanks for the suggestion. Followed the instructions to upgrade the modules, rebooted, but still no joy.

I just looked at my 'pbxstatus' and I have 13-13.8. So something seems to be wrong with my system in particular...any hints on the kind(s) of things I should look at to get it working?

Hello, I have a fairly fresh, and up-to-date Incredible PBX 13-13 system (on actual hardware - not a VM). I've got 3 phones (Snom 320s) connected to the system currently (more later) and I've noticed a problem with the voicemail notification light. When a voicemail is left for that extension...

Thank you @tbrummell ! That was it! For anyone else out there wanting to disable user logon and logoff (or change the feature code numbers for it), they do not seem to appear in Feature Codes by default. You have to go to: Settings → Advanced Settings → System Setup → Expose All Feature Codes –...

...continuation from 1st post ^ ... However, as I mentioned, when I try to leave a voicemail with say #112 or #115, I get a different message. Here is what I get when I dial *112: == Using SIP RTP TOS bits 184 == Using SIP RTP CoS mark 5 [2019-02-27 05:41:18] WARNING[2990][C-00000006]...

Hello, I have a fresh, and up-to-date Incredible PBX 13-13 system (on actual hardware - not a VM). I've got extension numbers #110 - #125 set up on the system. Not sure if it matters, but at the moment, I only have phones set up for extensions 112, 115, and 120 (though I'm guessing that that...

Glad I came across this thread. I was wondering why I'm getting a bunch of Fail2Ban emails every morning at 00:15. I feel better now knowing that this is intentional.

OK, I gave up. The DAHDi card beat me. I ordered another Sangoma Vega 60G Gateway this morning, so I'm ditching the card.

So as an update, I have good news and bad news. Good news: Not long after my last post, I got my one (newer) card working! Got green lights on the 4 ports, was able to make/receive calls successfully Bad news: I was not able to finish the system because I did not have the time to configure the...

Ooohhh. I see. Well that counts me out. We've got our server running on bare metal in-house. Thanks for the clarification Eliad!