Call keeps going if application terminated about sipcmd HOT 4 OPEN

This is fairly standard for any SIP application. If the client does not
send CANCEL or BYE the server will often not disconnect the call in a
timely fashion

Ed

On 24 March 2014 15:34, AbdelRahman [email protected] wrote:

Due to segment fault, the application terminates, but the called number
still has the call in progress! This happens usually.

Reply to this email directly or view it on GitHubhttps://github.com//issues/24
.

from sipcmd.

Does it matter if it's UDP or TCP? Given the stateless nature of UDP?
On 24 Mar 2014 21:56, "Ed Holland" [email protected] wrote:

This is fairly standard for any SIP application. If the client does not
send CANCEL or BYE the server will often not disconnect the call in a
timely fashion

Ed

On 24 March 2014 15:34, AbdelRahman [email protected] wrote:

Due to segment fault, the application terminates, but the called number
still has the call in progress! This happens usually.

Reply to this email directly or view it on GitHub<
https://github.com/tmakkonen/sipcmd/issues/24>
.

Reply to this email directly or view it on GitHubhttps://github.com//issues/24#issuecomment-38492777
.

from sipcmd.

In other words, if connection was TCP will the SIP server terminates the
call if the tcp connection is closed as the process terminates?
On 24 Mar 2014 22:22, "Rahman" [email protected] wrote:

Does it matter if it's UDP or TCP? Given the stateless nature of UDP?
On 24 Mar 2014 21:56, "Ed Holland" [email protected] wrote:

This is fairly standard for any SIP application. If the client does not
send CANCEL or BYE the server will often not disconnect the call in a
timely fashion

Ed

On 24 March 2014 15:34, AbdelRahman [email protected] wrote:

Due to segment fault, the application terminates, but the called number
still has the call in progress! This happens usually.

Reply to this email directly or view it on GitHub<
https://github.com/tmakkonen/sipcmd/issues/24>
.

Reply to this email directly or view it on GitHubhttps://github.com//issues/24#issuecomment-38492777
.

from sipcmd.

Hi,

I've never worked directly with TCP based SIP. I would assume that it wont
terminate calls as SIP signalling is infrequent compared to the RTP audio
streams.

Ed

On 24 March 2014 20:29, AbdelRahman [email protected] wrote:

In other words, if connection was TCP will the SIP server terminates the
call if the tcp connection is closed as the process terminates?

On 24 Mar 2014 22:22, "Rahman" [email protected] wrote:

Does it matter if it's UDP or TCP? Given the stateless nature of UDP?
On 24 Mar 2014 21:56, "Ed Holland" [email protected] wrote:

This is fairly standard for any SIP application. If the client does not
send CANCEL or BYE the server will often not disconnect the call in a
timely fashion

Ed

On 24 March 2014 15:34, AbdelRahman [email protected] wrote:

Due to segment fault, the application terminates, but the called
number
still has the call in progress! This happens usually.

Reply to this email directly or view it on GitHub<
https://github.com/tmakkonen/sipcmd/issues/24>
.

Reply to this email directly or view it on GitHub<
https://github.com/tmakkonen/sipcmd/issues/24#issuecomment-38492777>

.

Reply to this email directly or view it on GitHubhttps://github.com//issues/24#issuecomment-38496494
.

from sipcmd.