[OpenSER-Users] [MediaProxy] If early media is longer than "idleTimeout" the RTP session is terminated

Iñaki Baz Castillo ibc at aliax.net
Fri Jul 25 17:13:19 CEST 2008


Hi, I use MediaProxy 1.9.1 with OpenSer.
idleTimeout=50 seconds

I've received an INVITE and a 183 with early media during 52 seconds and after 
that the 200 was received. But the RTP session in MediaProxy was terminated 
after 50 seconds (idleTimeout). Why?

Is a still no answered call considered "idle"?

This is the syslog:

-----------------------------------------------
# INVITE arrives:

Jul 25 15:21:17 server-sip proxydispatcher[21258]: request 
9b984e5890000e3e13c4aa99fd9a69852d69d32b2614fe1cc8-0228-6667 
77.14.6.152:57102:audio,77.14.6.152:41292:image 77.14.0.144 77.14.0.144 
remote 192.168.10.2 remote CS2000_NGSS/9.0 
info=from:882534800 at 77.14.0.144:5060,to:887332031 at 88.99.3.10:5060,fromtag:e3e-13c4-aa99fd-62c9f59e-aa99fd,totag:

Jul 25 15:21:17 server-sip mediaproxy[21253]: request 
9b984e5890000e3e13c4aa99fd9a69852d69d32b2614fe1cc8-0228-6667 
77.14.6.152:57102:audio,77.14.6.152:41292:image 77.14.0.144 77.14.0.144 
remote 192.168.10.2 remote CS2000_NGSS/9.0 
info=totag:,to:887332031 at 88.99.3.10:5060,from:882534800 at 77.14.0.144:5060,fromtag:e3e-13c4-aa99fd-62c9f59e-aa99fd

Jul 25 15:21:17 server-sip mediaproxy[21253]: session 
9b984e5890000e3e13c4aa99fd9a69852d69d32b2614fe1cc8-0228-6667: started. 
listening on 88.99.3.10:61820,61822

Jul 25 15:21:17 server-sip mediaproxy[21253]: execution time:  0.92 ms

Jul 25 15:21:17 server-sip proxydispatcher[21258]: forwarding to mediaproxy 
on /var/run/mediaproxy.sock: got: '88.99.3.10 61820 61822'


# After 50 seconds the session is ended by MediaProxy:

Jul 25 15:22:06 server-sip mediaproxy[21253]: session 
9b984e5890000e3e13c4aa99fd9a69852d69d32b2614fe1cc8-0228-6667: 0/0/0 packets, 
0/0/0 bytes (caller/called/relayed)
Jul 25 15:22:06 server-sip mediaproxy[21253]: session 
9b984e5890000e3e13c4aa99fd9a69852d69d32b2614fe1cc8-0228-6667: ended (did 
timeout).

# After 2 seconds the 200 OK arrives so media fails.

Jul 25 15:22:08 server-sip proxydispatcher[21258]: lookup 
9b984e5890000e3e13c4aa99fd9a69852d69d32b2614fe1cc8-0228-6667 
192.168.10.2:19084:audio 88.99.1.213 sip.domain.net local unknown unknown 
Asterisk=20testDesign 
info=from:882534800 at sip.domain.net,to:887332031 at 88.99.3.10:5060,fromtag:e3e-13c4-aa99fd-62c9f59e-aa99fd,totag:as6156af6c
Jul 25 15:22:08 server-sip mediaproxy[21253]: lookup 
9b984e5890000e3e13c4aa99fd9a69852d69d32b2614fe1cc8-0228-6667 
192.168.10.2:19084:audio 88.99.1.213 sip.domain.net local unknown unknown 
Asterisk=20testDesign 
info=totag:as6156af6c,to:887332031 at 88.99.3.10:5060,from:882534800 at sip.domain.net,fromtag:e3e-13c4-aa99fd-62c9f59e-aa99fd
Jul 25 15:22:08 server-sip mediaproxy[21253]: session 
9b984e5890000e3e13c4aa99fd9a69852d69d32b2614fe1cc8-0228-6667: started. 
listening on 88.99.3.10:61824
Jul 25 15:22:08 server-sip mediaproxy[21253]: execution time:  0.60 ms
Jul 25 15:22:08 server-sip proxydispatcher[21258]: forwarding to mediaproxy 
on /var/run/mediaproxy.sock: got: '88.99.3.10 61824'
Jul 25 15:22:08 server-sip proxydispatcher[21258]: execution time:  1.09 ms
-----------------------------------------------


-- 
Iñaki Baz Castillo




More information about the Users mailing list