Hi, I'm suffering an important issue with MediaProxy in calls from/to my carrier softswitch. Sometimes it seems that MediaProxy assigns a media port during the INVITE but it closes it inmediatelly, so the following 183 forces the creation of a different media port and obviously the media dies. It works perfectly for long days but some days it has those problems. Please, could you people help me in investigating if a problem in my OpenSer/MediaProxy? I have a detailed real example. This is what happens: --------------------------------------------------------------------------- 09:28:46 - INVITE Client -> OpenSer (audio: 192.168.1.203:10370) 09:28:46 - INVITE OpenSer -> gateway (audio: 88.99.3.10:60696) <-- MediaProxy set 60696 port but inmediatelly ends the session. 09:28:48 - 183 Gateway -> OpenSer (audio: 66.11.6.142:45734) 09:28:48 - 183 OpenSer -> Client (audio: 88.99.3.10:60698) <-- Wrong port, MediaProxy set 60698 port !!! 09:28:49 - 200 Gateway -> OpenSer (audio: 66.11.6.142:45734) 09:28:49 - 200 OpenSer -> Client (audio: 88.99.3.10:60704) <-- Wrong port, MediaProxy set 60704 port !!! --------------------------------------------------------------------------- This is the mediaproxy/proxydispatcher log. As you can see media port open during INVITE is inmediatelly closed WHY?): --------------------------------------------------------------------------------------- ### 09:28:46 - 9:28:46 openser-host proxydispatcher[31874]: request 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net 192.168.1.203:10370:audio 88.99.1.192 sip.domain.net local 66.11.0.144 remote Domain=20-=20Asterisk=20PBX info=from:216@sip.domain.net,to:996511959@sip.domain.net,fromtag:as3c11216c,totag: - 09:28:46 openser-host mediaproxy[31869]: request 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net 192.168.1.203:10370:audio 88.99.1.192 sip.domain.net local 66.11.0.144 remote Domain=20-=20Asterisk=20PBX info=totag:,to:996511959@sip.domain.net,from:216@sip.domain.net,fromtag:as3c11216c - 09:28:46 openser-host mediaproxy[31869]: session 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net: started. listening on 88.99.3.10:60696 - 09:28:46 openser-host mediaproxy[31869]: execution time: 0.60 ms - 09:28:46 openser-host proxydispatcher[31874]: forwarding to mediaproxy on /var/run/mediaproxy.sock: got: '88.99.3.10 60696' - 09:28:46 openser-host proxydispatcher[31874]: execution time: 2.45 ms **************** ERROR: Why does it occur ??? *********************** - 09:28:46 openser-host mediaproxy[31869]: session 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net: 0/0/0 packets, 0/0/0 bytes (caller/called/relayed) - 09:28:46 openser-host mediaproxy[31869]: session 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net: ended (did timeout). ********************************************************************* ### 09:28:48 - 09:28:48 openser-host proxydispatcher[31874]: lookup 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net 66.11.6.142:45734:audio 66.11.0.144 sip.domain.net local unknown unknown CS2000_NGSS/9.0 info=from:216@sip.domain.net,to:996511959@sip.domain.net,fromtag:as3c11216c,totag:4d764120338220087992847 - 09:28:48 openser-host mediaproxy[31869]: lookup 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net 66.11.6.142:45734:audio 66.11.0.144 sip.domain.net local unknown unknown CS2000_NGSS/9.0 info=totag:4d764120338220087992847,to:996511959@sip.domain.net,from:216@sip.domain.net,fromtag:as3c11216c - 09:28:48 openser-host mediaproxy[31869]: session 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net: started. listening on 88.99.3.10:60698 - 09:28:48 openser-host mediaproxy[31869]: session 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net: ended (did timeout). ### 09:28:58 - 09:28:58 openser-host proxydispatcher[31874]: lookup 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net 66.11.6.142:45734:audio 66.11.0.144 sip.domain.net local unknown unknown CS2000_NGSS/9.0 info=from:216@sip.domain.net,to:996511959@sip.domain.net,fromtag:as3c11216c,totag:4d764120338220087992847 - 09:28:58 openser-host mediaproxy[31869]: lookup 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net 66.11.6.142:45734:audio 66.11.0.144 sip.domain.net local unknown unknown CS2000_NGSS/9.0 info=totag:4d764120338220087992847,to:996511959@sip.domain.net,from:216@sip.domain.net,fromtag:as3c11216c - 09:28:58 openser-host mediaproxy[31869]: session 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net: started. listening on 88.99.3.10:60704 - 09:28:58 openser-host mediaproxy[31869]: execution time: 0.62 ms - 09:28:58 openser-host proxydispatcher[31874]: forwarding to mediaproxy on /var/run/mediaproxy.sock: got: '88.99.3.10 60704' - 09:28:58 openser-host proxydispatcher[31874]: execution time: 1.15 ms **************** ERROR: Why does it occur ??? *********************** - 09:28:59 openser-host mediaproxy[31869]: session 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net: 0/0/0 packets, 0/0/0 bytes (caller/called/relayed) - 09:28:59 openser-host mediaproxy[31869]: session 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net: ended (did timeout). ********************************************************************* ### 09:29:05 - 09:29:05 openser-host proxydispatcher[31874]: delete 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net info= - 09:29:05 openser-host mediaproxy[31869]: delete 5be83da413f9dbd468a6d83818fb356d(a)sip.domain.net info= --------------------------------------------------------------------------------------- I also attach the complete SIP capture of this real example, but I see nothing wrong in it. The question is: Why MediaProxy ends the session during the INVITE? why does it close the port? Thanks a lot for any help. -- Iñaki Baz Castillo ibc(a)in.ilimit.es