Calls not terminating properly?

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

 



Thanks,

Yes, indeed I'm not receiving the BYE request.switched the calls to pass
throught a proxy sip server first (voispeed), instead of calling it
directly, and this way I'm receiving the BYE command just after a RTCP
error. I suspect the proxy sip server is giving me the BYE cause the other
side closed unexpectedly. The cause is indeed on the other side not sending
the BYE (even if it says on logs that will send it) I'm investigating
further by contacting the 3rd party solution provider.

I have another question, regarding inv sessions. Can i use the same inv
session for multiple calls? Because i saw in your examples you have a call
data struct, and a inv session for each call data (when using pjsip), but im
using the pjsua-api, so don't know if this is ok.

Sorry for so many questions, but I've just landed on this project and some
code was already written, I'm debugging it =)

Best regards

---------- Forwarded message ----------
From: Benny Prijono <bennylp@xxxxxxxxx>
Date: Tue, Jun 3, 2008 at 3:17 PM
Subject: Re: Calls not terminating properly?
To: pjsip list <pjsip at lists.pjsip.org>


On Tue, Jun 3, 2008 at 12:10 PM, Jo?o C?sar <jpcesar at gmail.com> wrote:
>
> When running wireshark with filter udp.dstport = 5060 i dont see the BYE
> frame. I only see:
>
> source         dest            prot             info
> 10.0.1.19    10.0.1.30      SIP/SPD     Request: INVITE sip:3200 at 10.0.1.30<sip%3A3200 at 10.0.1.30>
,
> with session description
> 10.0.1.30    10.0.1.19      SIP             Status: 180 Ringing
> 10.0.1.30    10.0.1.19      SIP             Status: 200 OK, with session
> description
> 10.0.1.19    10.0.1.30      SIP             Request: ACK sip:
10.0.1.30:5060
>
> I dont see anymore frames regarding SIP session between those 2 hosts.
>
> However, checking the logs on the destination 3rd party product (10.0.1.30
)
>
> Received ACK
> Sent Command: BYE
> Received Message: STATUS
> Received STATUS msg after BYE(200)
> sendMessageToRtpProvider <CHANNEL_HANGUPPED_>
>
> After this happens on the destination endpoint, on pjsip i start to
receive
> spam of:
>
> RTP recv() error: Connection reset by peer (WSAECONNRESET)
>

It looks like pjsip doesn't receive the BYE request, for some reason,
hence it continues to send RTP, and since remote has closed the RTP
socket, we get ICMP error and this triggers WSAECONNRESET. So find out
why the BYE is not sent to pjsip and the problem should be fixed.

 -benny

_______________________________________________
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



-- 
Joao Cesar
msn: jpcesar at gmail.com
gtalk: jpcesar at gmail.com
icq: 13790802
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20080603/f14e990f/attachment.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