Hello All the link http://www.sifira.com/chan-ss7/ cannot access. anybody can be send to me lasted chan_ss7. or mirror link to download. Thanks --- asterisk-ss7-request@xxxxxxxxxxxxxxxx wrote: > Send asterisk-ss7 mailing list submissions to > asterisk-ss7@xxxxxxxxxxxxxxxx > > To subscribe or unsubscribe via the World Wide Web, > visit > > http://lists.digium.com/mailman/listinfo/asterisk-ss7 > or, via email, send a message with subject or body > 'help' to > asterisk-ss7-request@xxxxxxxxxxxxxxxx > > You can reach the person managing the list at > asterisk-ss7-owner@xxxxxxxxxxxxxxxx > > When replying, please edit your Subject line so it > is more specific > than "Re: Contents of asterisk-ss7 digest..." > > > Today's Topics: > > 1. Re: Error in t1_timeout (arg=0x8180078) at > chan_ss7.c:765 > makes asterisk crash (Anders Baekgaard) > 2. Re: Error in t1_timeout (arg=0x8180078) at > chan_ss7.c:765 > makes asterisk crash (Kai Militzer) > 3. Re: Error in t1_timeout (arg=0x8180078) at > chan_ss7.c:765 > makes asterisk crash (Anton) > 4. Re: Error in t1_timeout (arg=0x8180078) at > chan_ss7.c:765 > makes asterisk crash (Anders Baekgaard) > 5. Where can i get source? (Vijaya Kumar) > 6. Re: Error in t1_timeout (arg=0x8180078) at > chan_ss7.c:765 > makes asterisk crash (Kristian Nielsen) > 7. Re: Where can i get source? (Jacob Tinning) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 21 Mar 2006 09:15:40 +0100 > From: Anders Baekgaard <ab@xxxxxxxxxx> > Subject: Re: [asterisk-ss7] Error in t1_timeout > (arg=0x8180078) at > chan_ss7.c:765 makes asterisk crash > To: Kristian Nielsen <kn@xxxxxxxxx> > Cc: asterisk-ss7@xxxxxxxxxxxxxxxx > Message-ID: <200603210915.40851.ab@xxxxxxxxxx> > Content-Type: text/plain; charset="iso-8859-1" > > This change was one of a number of changes to fix > propagation of hangup > causes. But this particular change is wrong. Will be > changed in next version. > > -Anderes > > On Monday 20 March 2006 21:36, you wrote: > > > I just made some load testing and came across a > problem. In some cases > > > with a high volume of calls ( > 40) all trying > to start a connection > > > asterisk sometimes crashed without any output. I > only got a coredump > > > when running it with asterisk -gvvvvvc (thanks > to the hint from RoyK in > > > IRC) but this shows, that the problem seems to > be found somewhere in > > > t1_timeout. This is what gdb says: > > > > > > (gdb) bt > > > #0 0x40861cf6 in t1_timeout (arg=0x8180078) at > chan_ss7.c:765 > > > #1 0x08056528 in ast_sched_runq (con=0x8148990) > at sched.c:373 > > > #2 0x40869643 in monitor_main (data=0x0) at > chan_ss7.c:3402 > > > #3 0x40027e51 in pthread_start_thread () from > /lib/libpthread.so.0 > > > #4 0x401ef92a in clone () from /lib/libc.so.6 > > > > The crash is in this line, which was changed in > version 0.8.3 of > > chan_ss7: > > > > @@ -737,7 +762,7 @@ > > struct ss7_chan *pvt = arg; > > > > ast_log(LOG_NOTICE, "T1 timeout (waiting for > RLC) CIC=%d.\n", pvt->cic); > > - isup_send_rel(pvt, pvt->hangupcause); > > + isup_send_rel(pvt, pvt->owner->hangupcause); > > return 1; /* Run us again > the next period */ > > } > > > > That change seems to me to be just plain wrong? > There is no guarantee > > that pvt->owner will be non-null (and I'll bet > that the crash is caused > > by it being NULL here). > > > > For example, if ss7_hangup() is called on an > active curcuit, it sets > > pvt->owner = NULL, then calls > initiate_release_circuit() which starts > > timer T1. If that timer triggers for some reason, > Asterisk will crash on > > a NULL pointer reference. > > > > I would try to revert that change and see if it > does not cure the > > crashes. Anders should be able to tell what the > purpose of the change > > was and if anything else is needed. > > > > The next question is why the timer T1 triggered > (this happens when the > > other end does not reply with "release confirmed" > in a timely > > manner). But to answer that more information is > needed, like a protocol > > dump (ss7 start dump ...). > > > > - Kristian. > > > ------------------------------ > > Message: 2 > Date: Tue, 21 Mar 2006 09:44:52 +0100 > From: Kai Militzer <km@xxxxxxxxxxx> > Subject: Re: [asterisk-ss7] Error in t1_timeout > (arg=0x8180078) at > chan_ss7.c:765 makes asterisk crash > To: asterisk-ss7@xxxxxxxxxxxxxxxx > Message-ID: <441FBD04.1090800@xxxxxxxxxxx> > Content-Type: text/plain; charset=ISO-8859-1; > format=flowed > > Hello Anders, > > Anders Baekgaard wrote: > > This change was one of a number of changes to fix > propagation of hangup > > causes. But this particular change is wrong. Will > be changed in next version. > > Kristian Nielsen wrote: > >>The next question is why the timer T1 triggered > (this happens when the > >>other end does not reply with "release confirmed" > in a timely > >>manner). But to answer that more information is > needed, like a protocol > >>dump (ss7 start dump ...). > > > So do you still need protocol dump of this? Please > tell me if I should > send you one. > > Regards, > Kai > > -- > Kai Militzer WESTEND GmbH | > Internet-Business-Provider > Technik CISCO Systems Partner - > Authorized Reseller > L?tticher Stra?e 10 > Tel 0241/701333-14 > km@xxxxxxxxxxx D-52064 Aachen > Fax 0241/911879 > > > > ------------------------------ > > Message: 3 > Date: Tue, 21 Mar 2006 13:55:22 +0500 > From: Anton <anton.vazir@xxxxxxxxx> > Subject: Re: [asterisk-ss7] Error in t1_timeout > (arg=0x8180078) at > chan_ss7.c:765 makes asterisk crash > To: asterisk-ss7@xxxxxxxxxxxxxxxx > Cc: Anders Baekgaard <ab@xxxxxxxxxx> > Message-ID: > <200603211355.22806.anton.vazir@xxxxxxxxx> > Content-Type: text/plain; charset="iso-8859-1" > > Dear Anders, > > Could you also give us any clue why AudioLost with > the > following error message happens > > Mar 20 15:48:39 NOTICE[22448]: chan_ss7.c:1880 > ss7_write: === message truncated === __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
|