I tried passing the module parameters and setting it to hardhdlc but this is what I get when I start asterisk. The Bad FCS continues on for a while then the server crashes so bad that I can't even ping it anymore and I have to do a hard reset.
*CLI> [Oct 24 11:37:48] NOTICE[12038]: chan_zap.c:6940 handle_init_event: Alarm cleared on channel 2
[Oct 24 11:37:48] NOTICE[12038]: chan_zap.c:6940 handle_init_event: Alarm cleared on channel 3
[Oct 24 11:37:48] NOTICE[12038]: chan_zap.c:6940 handle_init_event: Alarm cleared on channel 4
[Oct 24 11:37:48] NOTICE[12038]: chan_zap.c:6940 handle_init_event: Alarm cleared on channel 5
[Oct 24 11:37:48] NOTICE[12038]: chan_zap.c:6940 handle_init_event: Alarm cleared on channel 6
[Oct 24 11:37:48] NOTICE[12038]: chan_zap.c:6940 handle_init_event: Alarm cleared on channel 7
[Oct 24 11:37:48] NOTICE[12038]: chan_zap.c:6940 handle_init_event: Alarm cleared on channel 8
[Oct 24 11:37:48] NOTICE[12038]: chan_zap.c:6940 handle_init_event: Alarm cleared on channel 9
[Oct 24 11:37:48] NOTICE[12038]: chan_zap.c:6940 handle_init_event: Alarm cleared on channel 10
[Oct 24 11:37:48] NOTICE[12038]: chan_zap.c:6940 handle_init_event: Alarm cleared on channel 11
[Oct 24 11:37:48] NOTICE[12038]: chan_zap.c:6940 handle_init_event: Alarm cleared on channel 12
[Oct 24 11:37:48] NOTICE[12038]: chan_zap.c:6940 handle_init_event: Alarm cleared on channel 13
[Oct 24 11:37:48] NOTICE[12038]: chan_zap.c:6940 handle_init_event: Alarm cleared on channel 14
[Oct 24 11:37:48] NOTICE[12038]: chan_zap.c:6940 handle_init_event: Alarm cleared on channel 15
[Oct 24 11:37:48] NOTICE[12038]: chan_zap.c:6940 handle_init_event: Alarm cleared on channel 16
[Oct 24 11:37:48] NOTICE[12038]: chan_zap.c:6940 handle_init_event: Alarm cleared on channel 17
[Oct 24 11:37:48] NOTICE[12038]: chan_zap.c:6940 handle_init_event: Alarm cleared on channel 18
[Oct 24 11:37:48] NOTICE[12038]: chan_zap.c:6940 handle_init_event: Alarm cleared on channel 19
[Oct 24 11:37:48] NOTICE[12038]: chan_zap.c:6940 handle_init_event: Alarm cleared on channel 20
[Oct 24 11:37:48] NOTICE[12038]: chan_zap.c:6940 handle_init_event: Alarm cleared on channel 21
[Oct 24 11:37:48] NOTICE[12038]: chan_zap.c:6940 handle_init_event: Alarm cleared on channel 22
[Oct 24 11:37:48] NOTICE[12038]: chan_zap.c:6940 handle_init_event: Alarm cleared on channel 23
[Oct 24 11:37:48] NOTICE[12038]: chan_zap.c:6940 handle_init_event: Alarm cleared on channel 24
[Oct 24 11:37:48] ERROR[12037]: chan_zap.c:8435 ss7_linkset: Alarm cleared on link
[Oct 24 11:37:48] ERROR[12037]: chan_zap.c:8451 ss7_linkset: Error in write Unknown error 500[Oct 24 11:37:48] ERROR[12037]: chan_zap.c:8423 ss7_linkset: Bad FCS!
[Oct 24 11:37:48] ERROR[12037]: chan_zap.c:8451 ss7_linkset: Error in write Unknown error 500[Oct 24 11:37:48] ERROR[12037]: chan_zap.c:8423 ss7_linkset: Bad FCS!
[Oct 24 11:37:48] ERROR[12037]: chan_zap.c:8451 ss7_linkset: Error in write Unknown error 500[Oct 24 11:37:48] ERROR[12037]: chan_zap.c:8423 ss7_linkset: Bad FCS!
[Oct 24 11:37:48] ERROR[12037]: chan_zap.c:8451 ss7_linkset: Error in write Unknown error 500[Oct 24 11:37:48] ERROR[12037]: chan_zap.c:8423 ss7_linkset: Bad FCS!
[Oct 24 11:37:48] ERROR[12037]: chan_zap.c:8451 ss7_linkset: Error in write Unknown error 500[Oct 24 11:37:48] ERROR[12037]: chan_zap.c:8423 ss7_linkset: Bad FCS!
[Oct 24 11:37:48] ERROR[12037]: chan_zap.c:8423 ss7_linkset: Bad FCS!
[Oct 24 11:37:48] ERROR[12037]: chan_zap.c:8423 ss7_linkset: Bad FCS!
[Oct 24 11:37:48] ERROR[12037]: chan_zap.c:8423 ss7_linkset: Bad FCS!
[Oct 24 11:37:48] ERROR[12037]: chan_zap.c:8423 ss7_linkset: Bad FCS!
[Oct 24 11:37:48] ERROR[12037]: chan_zap.c:8423 ss7_linkset: Bad FCS!
[Oct 24 11:37:48] ERROR[12037]: chan_zap.c:8423 ss7_linkset: Bad FCS!
[Oct 24 11:37:48] ERROR[12037]: chan_zap.c:8423 ss7_linkset: Bad FCS!
-----Original Message-----
From: asterisk-ss7-bounces@xxxxxxxxxxxxxxxx [mailto:asterisk-ss7-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Matt Fredrickson
Sent: Monday, October 23, 2006 4:56 PM
To: asterisk-ss7@xxxxxxxxxxxxxxxx
Subject: Re: ANSI SS7
Yes, but it only works with Digium TE2xxp and TE4xxp cards. When you load the wct4xxp.ko modules you need to pass the module parameter "hardhdlcmode=0x7f" and set your signalling channel in zaptel.conf as hardhdlc. That should put it into 56kbps link mode.
Matthew Fredrickson
----- Jason L. Nesheim <jason@xxxxxxxxxxx> wrote:
> It is a 56kbps F-link from my CopperCom. I can't use 64k links on
> that switch, is there a way to set up asterisk to use 56k?
>
> -----Original Message-----
> From: asterisk-ss7-bounces@xxxxxxxxxxxxxxxx
> [mailto:asterisk-ss7-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Matthew
> Fredrickson
> Sent: Thursday, October 19, 2006 10:39 AM
> To: asterisk-ss7@xxxxxxxxxxxxxxxx
> Subject: Re: [asterisk-ss7] ANSI SS7
>
> It looks like you have a very low level problem on that line. We are
>
> sending the other end SIO (To start the alignment, but the other end
> is
> not going through the alignment process. The only thing I can think
> of
> is that either:
>
> A) You don't have your signalling channel setup correctly. Are you
> using a sangoma card? I've seen weirdness like this with sangoma
> cards. The problem was a misconfiguration with the dchannel wanpipe
> setup. Another possibility is that maybe it's a 56kbps link and
> you're
> trying to use it in 64kbps mode.
>
> B) The line is not configured at the other end to begin alignment.
>
> I'm suspecting it is probably something along the lines of option A.
>
> Matthew Fredrickson
>
> On Oct 19, 2006, at 8:42 AM, Jason L. Nesheim wrote:
>
> > I changed this piece of code in ss7linktest.c before trying this:
> > if (!(ss7 = ss7_new(SS7_ANSI))) {
> > perror("ss7_new");
> > exit(1);
> > }
> >
> > Here is the output:
> >
> > [root@localhost libss7]# ./ss7linktest 1
> > Starting link 1
> > Link state change: IDLE -> NOTALIGNED
> > FSN: 127 FIB 1
> > BSN: 127 BIB 1
> >> LSSU SIO
> >
> > Link state change: NOTALIGNED -> IDLE
> > FSN: 127 FIB 1
> > BSN: 127 BIB 1
> >> LSSU SIOS
> >
> >
> > As far as ansi point codes go, what is the appropriate method for
> > converting the dotted format codes to a format usable by asterisk?
> >
> >
> > -----Original Message-----
> > From: asterisk-ss7-bounces@xxxxxxxxxxxxxxxx
> > [mailto:asterisk-ss7-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Matthew
>
> > Fredrickson
> > Sent: Wednesday, October 18, 2006 6:20 PM
> > To: asterisk-ss7@xxxxxxxxxxxxxxxx
> > Subject: Re: [asterisk-ss7] ANSI SS7
> >
> > Try using the ss7linktest program that is included with libss7.
> The
> > syntax is "ss7linktest x" where x is the zap channel that your
> > signalling is on. Paste the output of that to your next reply.
> >
> > Matthew Fredrickson
> >
> > On Oct 18, 2006, at 4:58 PM, Jason L. Nesheim wrote:
> >
> >> The link won't actually come up at all. This message scrolls
> through
> >> asterisk so fast that it's impossible to do anything in the CLI
> when I
> >> start it. The odd part is that now that I downloaded the latest
> 1.4
> >> beta 2 zaptel and installed that and rebooted the box it seems
> that
> >> the messages have stopped but now asterisk is doing nothing at all
> >> with the SS7. No messages appear in the logs relating to it and
> my
> >> CopperCom sits in an activating state on the f-link. The config
> is
> >> the same as before, any ideas?
> >>
> >> -----Original Message-----
> >> From: asterisk-ss7-bounces@xxxxxxxxxxxxxxxx
> >> [mailto:asterisk-ss7-bounces@xxxxxxxxxxxxxxxx] On Behalf Of
> Matthew
> >> Fredrickson
> >> Sent: Wednesday, October 18, 2006 2:15 PM
> >> To: asterisk-ss7@xxxxxxxxxxxxxxxx
> >> Subject: Re: [asterisk-ss7] ANSI SS7
> >>
> >> Unless you're seeing link related problems (link doesn't come up
> and
> >> those are scrolling continuously) you shouldn't worry about those
> >> messages. MTP2 is designed to work around link layer hickups such
> as
> >> this. You may see better performance though if you set your dchan
> to
> >> hardhdlc instead (though that only works on the TE4xxp and
> TE2xxp).
> >>
> >> Matthew Fredrickson
> >>
> >> On Oct 18, 2006, at 12:07 PM, Jason L. Nesheim wrote:
> >>
> >>> I'm getting a strange error when I start up asterisk and I can't
> tell
> >>> if it's a problem with the ss7 linkset or something hardware
> related.
> >>>
> >>> This is what asterisk outputs:
> >>> [Oct 18 12:02:16] ERROR[7160]: chan_zap.c:8273 ss7_linkset: HDLC
> >>> Abort!
> >>>
> >>> This is the SS7 part of my Zapata.conf:
> >>>
> >>> signalling = ss7
> >>>
> >>> ss7type = ansi
> >>>
> >>> linkset = 1
> >>>
> >>> pointcode = 351400
> >>>
> >>> adjpointcode = 351240
> >>>
> >>> defaultdpc = 351240
> >>>
> >>> networkindicator=national
> >>>
> >>> cicbeginswith = 1001
> >>> sigchan = 1
> >>> channel = 2-24
> >>>
> >>> This is from my zaptel.conf:
> >>>
> >>> span=1,1,0,esf,b8zs
> >>> bchan=2-24
> >>> dchan=1
> >>> defaultzone=us
> >> _______________________________________________
> >> --Bandwidth and Colocation provided by Easynews.com --
> >>
> >> asterisk-ss7 mailing list
> >> To UNSUBSCRIBE or update options visit:
> >> http://lists.digium.com/mailman/listinfo/asterisk-ss7
> >> _______________________________________________
> >> --Bandwidth and Colocation provided by Easynews.com --
> >>
> >> asterisk-ss7 mailing list
> >> To UNSUBSCRIBE or update options visit:
> >> http://lists.digium.com/mailman/listinfo/asterisk-ss7
> >
> > _______________________________________________
> > --Bandwidth and Colocation provided by Easynews.com --
> >
> > asterisk-ss7 mailing list
> > To UNSUBSCRIBE or update options visit:
> > http://lists.digium.com/mailman/listinfo/asterisk-ss7
> > _______________________________________________
> > --Bandwidth and Colocation provided by Easynews.com --
> >
> > asterisk-ss7 mailing list
> > To UNSUBSCRIBE or update options visit:
> > http://lists.digium.com/mailman/listinfo/asterisk-ss7
>
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> asterisk-ss7 mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-ss7
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> asterisk-ss7 mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-ss7
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-ss7 mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-ss7
|