> 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 ta
On Fri, Aug 2, 2013 at 12:29 PM, Shaun Ruffell 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 have been unab
The last two companies I have worked for have both had this problem with
a BT ISDN30 line at some point. I also manage SS7 interconnects and its
not unusual for there to be issues with them either. So dont assume its
probably at your end :P
On 02/08/13 15:12, Andre Goree wrote:
I've contacted
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 have been unable to come up with
> anything...though there may be a timing
On Tue, Jul 30, 2013 at 3:55 PM, Shaun Ruffell 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, ha:
>>
>> [
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, ha:
>
> [root@asterisk-master dahdi]# dmesg | grep wcte13xp
> wcte13xp
On Tue, Jul 30, 2013 at 11:40 AM, Shaun Ruffell 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 wrote:
>> > On Tue, Jul 30, 2013 at 10:36:58AM -0400, Andre Goree wrote:
>> >
>> > > I've posted the configs and the output of a
On Tue, Jul 30, 2013 at 11:13:55AM -0400, Andre Goree wrote:
> On Tue, Jul 30, 2013 at 10:56 AM, Shaun Ruffell wrote:
> > On Tue, Jul 30, 2013 at 10:36:58AM -0400, Andre Goree wrote:
> >
> > > I've posted the configs and the output of a 'pri debug' below. Please
> > > let me know if I should incl
On Tue, Jul 30, 2013 at 10:56 AM, Shaun Ruffell 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 Wildcard T
On 30/07/13 15:36, Andre Goree wrote:
/etc/dahdi/system.conf:
span=1,0,0,ESF,B8ZS
bchan=1-23
dchan=24
loadzone=us
The first '0' in your span line above indicated that asterisk is
generating the timing source. Normally the network operator provides
timing so I would expect this to be a '1'. Thi
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 Wildcard TE133.
In case you haven't, you should feel free to contact D
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] VERBO
12 matches
Mail list logo
