Summary:	ASTERISK-01281: [patch] transaction id made unsigned + delete stale connections
Reporter:	serkan (serkan)	Labels:
Date Opened:	2004-03-23 17:18:34.000-0600	Date Closed:	2004-09-25 02:53:45
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) chan_mgcp.c.diff
Description:	Attached patch attempts to resolve two issues raised by Sergi in bugid 1114 follow-up: 1) transaction id made unsigned 2) stale connections reported in AUEP response are deleted Please let me know if you encounter any issues with the patch... ****** ADDITIONAL INFORMATION ****** Quoting from bug 1114: " 1)(minor) As you know the mgcp request messages that asterisk sends to endpoints is sequenced and variable that is used for it is called oseq. There is no limit on increasing of them. In case of many endpoints it may cause overloading problem, because it has type static int it can get negative value and the endpoint will not work correctly. Also, I think there must be some kind of storage of oseq last value, because asterisk always starts with value of 0 and if in some case asterisk crashes after restarting it will send sequencies starting from 1 and if endpoint receives allready such sequense number (during variable period of time endpoints are ignoring messages with same sequence, this period is configurable on endpoints) will not response. I worked with other call manager(Clarent) and it works in mentioned way. 3) (major) As you know when there is established call between aterisk and endpoint there is ident assigned to each call on endpoint and asterisk. If in some case asterisk crashes or due to network condition endpoint do not receive dlcx request and it stays on ednpoint (it does in ASKEY).After that in case of new call new ident has been assigned and than endpoint do not work correctly. I think Asterisk must send DLCX request if it see in AUEP response that endpoint has ident and it is on hook. I dont know if these situation happens with other mgcp endpoints, but you can check it trying to kill asterisk(during conversation) and start it again and checking the AUEP response. "
Comments:	By: Brian West (bkw918) 2004-03-23 17:58:47.000-0600 YAY chan_mgcp luvins.... Have you sent in your disclaimer? Also is it possible to unload chan_mgcp.so without blowing up the box yet? By: Mark Spencer (markster) 2004-03-27 12:56:10.000-0600 Added to CVS.  Thanks!