| Summary: | ASTERISK-01113: First call after MGCP endpoint restart fails | ||
| Reporter: | i3micro (i3micro) | Labels: | |
| Date Opened: | 2004-02-27 07:09:06.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: | ||
| Description: | After an endpoint has been restarted the first call often fails. The reason for this is that when you terminated a call the used connection is deleted BUT there is also a new connection created ???? If you in this state restart the endpoint (sending RSIP with restart) the previous created connection is not removed. So the first call made is trying to use this connection which the endpoint know nothing about now because it has restarted. The problem seems to be that this strange connection is created when you hangup the phone. What I can see this is because in the mgcpsock_read function a new connection is always created if you receive a response with an SDP in it and you don't have an rtp already up. During hangup a modify connection is first sent which produces a response with an SDP. So therefore a new connection is created causing problems at restarts. Shouldn't a restart from an endpoint clear all old data ?? You could get a restart in a middle of a call. | ||
| Comments: | By: serkan (serkan) 2004-02-27 14:27:25.000-0600 One of the issues fixed by patch in ticket ASTERISK-1108 is this one. FYI.. By: Mark Spencer (markster) 2004-04-15 10:28:40 Fixed in CVS | ||