TCP connection termination not handled well

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



You make it sound like you want the client to hang up?! As you know, the
primary way a program finds out if a socket is closed is to try reading
or writing on it. In this case the server has closed its end of the
socket but the client probably doesn't know that (yet)--evidently
because it thought it would get the chance to REGISTER

On 5/6/13 5:15 PM, Khoa Pham wrote:
> Hi pjsip team,
>
> When I make REGISTER request to server, I often receive this
>
> 1. client: SYN
> 2. server: SYN, ACK
> 3. client: ACK
> 4. server: FIN, ACK
> 5. client: REGISTER
> 6. server: RST
>
> Why in step 5 does client not send FIN, ACK ??
>
> -- 
> Khoa Pham
> HCMC University of Science
> Faculty of Information Technology
>
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip at lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

-- 
Jens B. Jorgensen
jbj1 at ultraemail.net

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20130507/d87ba061/attachment-0001.html>


[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux