Summary:	ASTERISK-00939: Q921 N(S) behaves weird causing resending on E100P
Reporter:	knut (knut)	Labels:
Date Opened:	2004-01-28 15:35:44.000-0600	Date Closed:	2004-09-25 02:51:27
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) resending.log
Description:	Messages from Q931 seems to get stuck (not sent), but causes N(S) to be increase anyway. Here is the sequence                            N(S)    N(R) > SETUP              3       5      (from asterisk to peer) < RR                         4 < CALL PROCEEDING    5       4 > STATUS             4       6                             Here SETUP is sent to libpri, but there is no trace of it in the libpri log.                                             < RR                         5 > DISCONNECT         6       6     Here N(S) is wrong < REJ                        5   > SETUP              5       6     Resending The strange thing is that there is no indication in the log (pri intense debug span 1) that SETUP is sent. So it is not lost on the line. There are lots of resending in the logs suggesting some software problems. ****** ADDITIONAL INFORMATION ****** CVS latest of libpri
Comments:	By: Mark Spencer (markster) 2004-02-16 02:26:43.000-0600 This is, i believe, the same as 944? By: knut (knut) 2004-02-19 17:34:17.000-0600 The log is the same, but it's a different problem I belive. That's why I wrote a second bug report. By: Mark Spencer (markster) 2004-04-08 00:56:35 Can you see if this has been fixed by my most recent changes? By: Mark Spencer (markster) 2004-04-15 01:05:21 Presumed fixed by earlier changes.