[OpenSIPS-Users] Mediaproxy - timeout issue if ringing for more than 60 seconds

[Ruud Klaver]

Hi Thomas,

On 19 Jun 2009, at 15:03, Thomas Gelf wrote:

> # Update reaches the relay - but RTP information for the caller is  
> still
> # unknown (please note that SDP is fine, correctly parsed by QOS  
> modul,
> # available via MI - and also fine for Mediaproxy if timeout is  
> below 60
> # secs):
>
> 13:51:03 media-relay[690]: debug: updating existing session
> SOME-CALL-ID at 80.2.3.5: 0212345678 at 80.2.3.5 (69D9B578-1DC8) -->
> 0276543210 at outbound.tld
> 13:51:03 media-relay[690]: debug: Received updated SDP answer
> 13:51:03 media-relay[690]: debug: Unchanged stream: (audio)
> 100.3.4.5:60846 (RTP: Unknown, RTCP: Unknown) <-> 90.1.2.3:54436 <->
> 90.1.2.3:54438 <-> 90.1.2.1:10262 (RTP: 90.1.2.1:10262, RTCP:
> 90.1.2.1:10263)

Does the modified SDP reach your calling endpoint correctly? From this  
I see that it never even sent RTP to the relay. Did you say that, if  
you set the VM timeout to less than 60 seconds, the call works fine?  
Maybe it's a timeout in your calling endpoint then...

> # If I do not hang up and wait (hearing nothing) - after some seconds
> # the call has been teared down:
>
> 13:51:20 media-relay[690]: debug: expired session SOME-CALL-ID at 80.2.3.5 
> :
> 0212345678 at 80.2.3.5 (69D9B578-1DC8) --> 0276543210 at outbound.tld
> 13:51:20 media-relay[690]: (Port 54436 Closed)
> 13:51:20 media-relay[690]: (Port 54437 Closed)
> 13:51:20 media-relay[690]: (Port 54438 Closed)
> 13:51:20 media-relay[690]: (Port 54439 Closed)
>
> # Dispatcher receives the timeout and tells OpenSIPS to stop the call:
>
> 13:51:20 media-dispatcher[1697]: session with call_id
> SOME-CALL-ID at 80.2.3.5 from relay 90.1.2.3 did timeout
> 13:51:20 media-dispatcher[1697]: debug: Got statistics: {'from_tag':
> '69D9B578-1DC8', 'dialog_id': '2475:922919439', 'start_time':
> 1245412252.01, 'timed_out': True, 'call_id': 'SOME-CALL-ID at 80.2.3.5',
> 'to_tag': 'as4a00af3c', 'streams': [{'status': 'no-traffic timeout',
> 'caller_codec': 'Unknown', 'post_dial_delay': 61.350157022499999,
> 'callee_codec': 'G711a', 'start_time': 0, 'caller_bytes': 0,
> 'callee_bytes': 0, 'caller_packets': 0, 'end_time': 28,  
> 'callee_remote':
> '90.1.2.1:10262', 'caller_remote': 'Unknown', 'media_type': 'audio',
> 'callee_local': '90.1.2.3:54438', 'timeout_wait': 90, 'caller_local':
> '90.1.2.3:54436', 'callee_packets': 0}], 'duration': 28, 'to_uri':
> '0276543210 at outbound.tld', 'from_uri': '0212345678 at 80.2.3.5',
> 'callee_ua': 'ROL B2BUA', 'caller_ua': 'Cisco-SIPGateway/IOS-12.x'}
> 13:51:20 testproxy media-dispatcher[1697]:
> mediaproxy.interfaces.opensips.UNIXSocketProtocol starting on
> '/var/run/mediaproxy/opensips_01.sock'
>
> Any idea where to look for this timeout?
>
> Kind regards,
> Thomas Gelf

The timeout that does this, if that's what you are looking for, is  
configured in the MediaProxy relay section as stream_timeout and  
defaults to 90 seconds. It is triggered when, X seconds after seeing  
the first SDP, mediaproxy does not see RTP from both parties.

Ruud Klaver
AG Projects