[asterisk-ss7] Re: chan_ss7 experience and question.

[Vernier Umali]

Relocating IRQ seems to work. IRQ misses are null now. Load for the
server isn't that much since we are still in testing.

The deal with the typ=CPR messages seems to be from another switch
which we are still investigating. Alcatel switch is passing the calls
to another switch. As for CRC and bitstreams errors, are those
critical? Seems like everything is ok for now. No drop calls and no
disconnection from switch. Signalling seems to be stable.

I was thinking of giving libss7 a try. Might be more stable with fewer errors.

On 12/20/06, Matthew Fredrickson <creslin at digium.com> wrote:
> In my testing of libss7 with chan_ss7, I found that chan_ss7 seemed to
> exhibit higher numbers of these type of errors when the system was
> under load.  It seemed like the thread servicing the zap channel wasn't
> able to keep up for whatever reason.
>
> Matthew Fredrickson
>
> On Dec 10, 2006, at 8:31 PM, Vernier Umali wrote:
>
> > I already set the digium card in its own IRQ. IRQ misses are now zero
> > after a few days. The errors below are still coming up in the logs.
> > Any ideas? BTW, the switch is an Alcatel. Thanks
> >
> > On 12/7/06, Vernier Umali <vernier at gmail.com> wrote:
> >> I have recently integrated with a switch using chan_ss7 0.90. Calls
> >> were passing thru from IAX to ss7 and voice quality is excellent. I
> >> haven't done calls from ss7 to IAX since they have to change something
> >> at the switch (routing). I have a few observations though.
> >>
> >> 1. When I use IAX to call ss7 and I send a busy tone from the mobile,
> >> the channel would still indicate initializing calls. But when I call
> >> the phone from IAX and pick up the fone then cancelled the call from
> >> the phone, everything turned out ok. I got these from the logs when I
> >> sent the busy tone.
> >>
> >> DEBUG[28643] l4isup.c: processing ISUP message, typ=CPR, CIC=24
> >> DEBUG[28643] l4isup.c: Process CPR, CIC=24 event=0x3, obci=0x1
> >>
> >> 2. I'm getting a few CRC and bitstream errors from the logs. I'm also
> >> getting a few IRQ misses. I think this is because of IRQ sharing. I
> >> intend to fix that next time and see what happens. But as I said,
> >> calls a coming through OK. Logs of the errors
> >>
> >> mtp.c: MTP2 bitstream frame format error, entering octet counting mode
> >> on link 'l1'.
> >> mtp.c: MTP2 CRC error (CRC=0x9496 != 0xf0b8) on link 'l1'.
> >>
> >> Besides the above, everything seems to be going ok. I haven't really
> >> tested it yet on long and many calls and I haven't done ss7 to ip
> >> calling yet. I'm also keen on ss7 to ss7 calls passing though
> >> asterisk.
> >>
> > _______________________________________________
> > --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
>