Although, patlooptest ran clean. It's most likely either a)
misconfiguration between the card settings and the provider b)
cabling between the card and the smart jack or c) Just something bad
on the provider's end. The probability of it being system / hardware
related is low IMO.
I take it
On Tue, Jul 30, 2013 at 3:55 PM, Shaun Ruffell sruff...@digium.com wrote:
On Tue, Jul 30, 2013 at 11:46:04AM -0400, Andre Goree wrote:
Thanks I'll definitely be contacting Digium support shortly. For the
hell of it, here's my dmesg output -- I'm seemingly safe from an IRQ
issue, thankfully
On Fri, Aug 2, 2013 at 12:29 PM, Shaun Ruffell sruff...@digium.com wrote:
On Fri, Aug 02, 2013 at 10:12:54AM -0400, Andre Goree wrote:
Ran through a loopback test with Digium which seemingly proved that
there was no issue with their card. I've contacted my telco for
assistance but so far
Hello,
I seem to be having an issue with the configuration of my PRI on a new
asterisk server I've created to replace an old install that I have.
The card is Digium Wildcard TE133. I continually get messages like
Primary D-Channel on span 1 down, rather irregularly:
[2013-07-29 17:31:39]
On Tue, Jul 30, 2013 at 10:56 AM, Shaun Ruffell sruff...@digium.com wrote:
On Tue, Jul 30, 2013 at 10:36:58AM -0400, Andre Goree wrote:
I seem to be having an issue with the configuration of my PRI on a new
asterisk server I've created to replace an old install that I have.
The card is Digium
On Tue, Jul 30, 2013 at 11:40 AM, Shaun Ruffell sruff...@digium.com wrote:
On Tue, Jul 30, 2013 at 11:13:55AM -0400, Andre Goree wrote:
On Tue, Jul 30, 2013 at 10:56 AM, Shaun Ruffell sruff...@digium.com wrote:
On Tue, Jul 30, 2013 at 10:36:58AM -0400, Andre Goree wrote:
I've posted
Hello all.
I'm having trouble resolving an issue with our Asterisk system that
seems to have popped up recently (no one knows for sure when the issue
started). I'm still somewhat of a Asterisk newb and have been tasked
with administrating the system as the previous administrator has left
the
On Sat, Jun 15, 2013 at 2:18 PM, Daniel Tryba dan...@tryba.nl wrote:
Jun 15 13:06:05 VERBOSE[30232]: -- Executing Dial(Zap/1-1,
zap/g1/1XX|20|tT) in new stack
Jun 15 13:06:05 VERBOSE[30232]: -- Called g1/1XX
Jun 15 13:06:08 VERBOSE[30232]: -- Zap/2-1 answered Zap/1-1
Jun 15
They are either incompetant or lying to you. Call appears to succeed (it
is answered) and gets disconnected after 23s. You are not generating the
message, so the calls gets back to you telco.
Most likely someone is filtering on callerID (which is a good thing IMHO).
Set the callerid to one
On Sat, Jun 15, 2013 at 4:03 PM, Daniel Tryba dan...@tryba.nl wrote:
On Sat, Jun 15, 2013 at 03:02:41PM -0400, Andre Goree wrote:
Setting the CID did not work, unfortunately :(
[...]
I'm going to try another number that we have through them in hopes
that it'll complete and I'll let you know
Do a pri set debug (or whatever it is called in 1.4 (zap?)) Zap/Zap
bridging should work, it did on my PRIs and still does with DAHDI. Only
thing I can think of is the TON/NPI might be a problem (but doubt it
since SIP/Zap works).
Thanks so much for your suggestions.
I'm running 1.0.x
specific mobo (Supermicro X9SCA-F), but I'd like to not waste time by
ordering an incorrect adapter and figured it might be prudent to ask you
good folks :)
Thanks in advance for any guidance you can provide.
--
Andre Goree
Linux Systems Administrator, Atlantic.Net
Toll Free: 1.800.540.4686
on which one's people
are using with their cards, but I suppose and ol' pci-e - 32-bit PCI
should work in the case of the TE410P, lol.
--
Andre Goree
Linux Systems Administrator, Atlantic.Net
Toll Free: 1.800.540.4686
International: +1.321.206.3731
Mobile: 407.272.6886
:)
Thanks!
--
Andre Goree
-=-=-=-=-=-
Email - an...@drenet.net
Website - http://blog.drenet.net
PGP key - http://www.drenet.net/0x83ADAAAB.asc
-=-=-=-=-=-
--
_
-- Bandwidth and Colocation Provided by http://www.api
:/
Any insight on failover solutions?
On Mon, May 13, 2013 at 10:27 PM, Andre Goree an...@drenet.net wrote:
Hello all. I was hoping someone out there might have some advice or
suggestions regarding an upgrade from an archaic Asterisk version.
I've been given the daunting task of upgrading
, however those appear to
only work for hardware failures. I would need something that can
account for both hardware and software failures.
Thanks in advance for any advice that anyone can give on the subject.
Any suggestions, etc. would help immensely!
--
Andre Goree
-=-=-=-=-=-
Email
16 matches
Mail list logo
