[Home]

Summary:ASTERISK-04859: app_meetme+chan_sip retries RTP packets indifinetly
Reporter:Juraj Bednar (juraj)Labels:
Date Opened:2005-08-19 03:40:50Date Closed:2011-06-07 14:10:45
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Applications/app_meetme
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Yesterday, I tried a conference call protected by IPSec protocol. Suddenly, both parties in meetme conference disconnected without hanging up the call. Then I got a full log of this (until morning):

Aug 18 21:57:11 NOTICE[2179] rtp.c: RTP Transmission error to 192.168.100.1:7208: Resource temporarily unavailable
Aug 18 21:57:11 NOTICE[2179] rtp.c: RTP Transmission error to 192.168.100.10:7586: Resource temporarily unavailable
Aug 18 21:57:11 NOTICE[2179] rtp.c: RTP Transmission error to 192.168.100.1:7208: Resource temporarily unavailable
Aug 18 21:57:11 NOTICE[2179] rtp.c: RTP Transmission error to 192.168.100.10:7586: Resource temporarily unavailable
Aug 18 21:57:11 NOTICE[2179] rtp.c: RTP Transmission error to 192.168.100.1:7208: Resource temporarily unavailable
Aug 18 21:57:11 NOTICE[2179] rtp.c: RTP Transmission error to 192.168.100.10:7586: Resource temporarily unavailable
Aug 18 21:57:11 NOTICE[2179] rtp.c: RTP Transmission error to 192.168.100.1:7208: Resource temporarily unavailable
Aug 18 21:57:11 NOTICE[2179] rtp.c: RTP Transmission error to 192.168.100.10:7586: Resource temporarily unavailable
Aug 18 21:57:11 NOTICE[2179] rtp.c: RTP Transmission error to 192.168.100.1:7208: Resource temporarily unavailable
Aug 18 21:57:11 NOTICE[2179] rtp.c: RTP Transmission error to 192.168.100.10:7586: Resource temporarily unavailable
Aug 18 21:57:11 NOTICE[2179] rtp.c: RTP Transmission error to 192.168.100.1:7208: Resource temporarily unavailable
Aug 18 21:57:11 NOTICE[2179] rtp.c: RTP Transmission error to 192.168.100.10:7586: Resource temporarily unavailable
Aug 18 21:57:11 NOTICE[2179] rtp.c: RTP Transmission error to 192.168.100.1:7208: Resource temporarily unavailable
Aug 18 21:57:11 NOTICE[2179] rtp.c: RTP Transmission error to 192.168.100.10:7586: Resource temporarily unavailable
Aug 18 21:57:11 NOTICE[2179] rtp.c: RTP Transmission error to 192.168.100.1:7208: Resource temporarily unavailable
Aug 18 21:57:11 NOTICE[2179] rtp.c: RTP Transmission error to 192.168.100.10:7586: Resource temporarily unavailable
Aug 18 21:57:11 NOTICE[2179] rtp.c: RTP Transmission error to 192.168.100.1:7208: Resource temporarily unavailable
Aug 18 21:57:11 NOTICE[2179] rtp.c: RTP Transmission error to 192.168.100.10:7586: Resource temporarily unavailable


 Resource temporarily unavailable is a common error in IPSec, when there's a security policy in
security policy database to communicate only with IPSec (using ESP), an operating system sends this
error to inform the application, that it tries to negotiate a security association using IKE. However,
this does not need to be temporary error, this could not finish.

 I suggest adding a sane timeout. If you can't temporarily send RTP data for say ten minutes, it's quite
probable it is a good idea to disconnect the client.

 Both clients were connected using SIP.

 BTW: Resource temporarily unavailable is not limited to ipsec, it can occur in other different cases on different systems, such as mac address of default gateway not known, ....
Comments:By: Michael Jerris (mikej) 2005-08-19 08:49:45

Is there an actual problem here, or do we need to just downgrade that message to debug?
By: Juraj Bednar (juraj) 2005-08-19 08:55:54

Of course there is a problem. There should be a timeout to disconnect the party, since there are failures to deliver rtp packets.

I don't care about the messages written to the logfile, I do care, that if all people in a conference loose their connection, there are still tries of sending RTP packets to them (while the system should notice, that there is indeed a long lasting problem -- if it's not possible to deliver RTP message even because of "temporary error" for 10 minutes, chance is that noone would be listening even if the temporary error would get solved -- the client would time out, so should we).

I suggest adding a timeout and disconnecting the user after that timeout, if there was no successful RTP delivery for some amount of time.
By: Michael Jerris (mikej) 2005-08-19 16:07:27

Ok, I understand the issue now.
By: Olle Johansson (oej) 2005-08-21 10:39:17

Check rtp timeouts in sip.conf.sample - they already exist.
By: Michael Jerris (mikej) 2005-08-23 14:02:52

rtp timeouts will fix this problem