[OpenSIPS-Users] Media-proxy dead air issue

[John Nash]

It seems like media proxy flag related issue to me. My guess is from first
gateway which fails you get session progress and then it rejects and you
get another session progress from second gateway. If you play around with
mediaproxy flags (at the time of session progress and 200 OK) it can be
solved.

On Wed, Jul 1, 2015 at 1:19 AM, <pwilliams at turnopen.com> wrote:

> I'm encountering a dead air issue with mediaproxy (version 2.5.2),
> specifically media-relay application.
> Seems similar to issue reported by Edwin
> http://lists.opensips.org/pipermail/users/2015-April/031498.html (no
> responses)
>
> My scenario is that an updated rtp port is sent by my clientSBC after
> failure of initial gateway, media-relay seems to get the new port via 183,
> but does not modify the stream correctly.
>
> I started media relay with no-fork option and received below.
>
> First rtp port negotiated.
> clientSBC:10568
>
> Updated rtp port requested
> clientSBC:10570
>
> Expecting this
> clientSBC:10570 (RTP: clientSBC:10570, RTCP: Unknown)
>
> Current Result (old port 10568, still remains)
> clientSBC:10570 (RTP: clientSBC:10568, RTCP: Unknown)
>
>
>
> debug: Received new SDP offer
> mediaproxy.mediacontrol.StreamListenerProtocol starting on 10000
> mediaproxy.mediacontrol.StreamListenerProtocol starting on 10001
> mediaproxy.mediacontrol.StreamListenerProtocol starting on 10002
> mediaproxy.mediacontrol.StreamListenerProtocol starting on 10003
> debug: Added new stream: (audio) internal-IVR:27980 (RTP: Unknown, RTCP:
> Unknown) <-> OpenSIPS:10000 <-> OpenSIPS:10002 <-> Unknown (RTP: Unknown,
> RTCP: Unknown)
> debug: created new session 7cf56d31-8aff-1233-8086-001a4a10fa59:
> 7185551212 at internal-IVR (F366pUF6HNHeg) --> 7325553535 at outsideProvider
> debug: Got traffic information for stream: (audio) internal-IVR:27980
> (RTP: Unknown, RTCP: Unknown) <-> OpenSIPS:10000 <-> OpenSIPS:10002 <->
> Unknown (RTP: clientSBC:10568, RTCP: Unknown)
> debug: updating existing session 7cf56d31-8aff-1233-8086-001a4a10fa59:
> 7185551212 at internal-IVR (F366pUF6HNHeg) --> 7325553535 at outsideProvider
> debug: Received updated SDP answer
> debug: Got initial answer from callee for stream: (audio)
> internal-IVR:27980 (RTP: Unknown, RTCP: Unknown) <-> OpenSIPS:10000 <->
> OpenSIPS:10002 <-> clientSBC:10570 (RTP: clientSBC:10568, RTCP: Unknown)
> debug: updating existing session 7cf56d31-8aff-1233-8086-001a4a10fa59:
> 7185551212 at internal-IVR (F366pUF6HNHeg) --> 7325553535 at outsideProvider
> debug: Received updated SDP answer
> debug: Unchanged stream: (audio) internal-IVR:27980 (RTP: Unknown, RTCP:
> Unknown) <-> OpenSIPS:10000 <-> OpenSIPS:10002 <-> clientSBC:10570 (RTP:
> clientSBC:10568, RTCP: Unknown)
> debug: updating existing session 7cf56d31-8aff-1233-8086-001a4a10fa59:
> 7185551212 at internal-IVR (F366pUF6HNHeg) --> 7325553535 at outsideProvider
> debug: Received new SDP offer
> debug: Found matching existing stream: (audio) internal-IVR:27980 (RTP:
> Unknown, RTCP: Unknown) <-> OpenSIPS:10000 <-> OpenSIPS:10002 <->
> clientSBC:10570 (RTP: clientSBC:10568, RTCP: Unknown)
> debug: updating existing session 7cf56d31-8aff-1233-8086-001a4a10fa59:
> 7185551212 at internal-IVR (F366pUF6HNHeg) --> 7325553535 at outsideProvider
> debug: Received updated SDP answer
> debug: Unchanged stream: (audio) internal-IVR:27980 (RTP: Unknown, RTCP:
> Unknown) <-> OpenSIPS:10000 <-> OpenSIPS:10002 <-> clientSBC:10570 (RTP:
> clientSBC:10568, RTCP: Unknown)
> debug: Got traffic information for stream: (audio) internal-IVR:27980
> (RTP: internal-IVR:27980, RTCP: Unknown) <-> OpenSIPS:10000 <->
> OpenSIPS:10002 <-> clientSBC:10570 (RTP: clientSBC:10568, RTCP: Unknown)
> debug: removing session 7cf56d31-8aff-1233-8086-001a4a10fa59:
> 7185551212 at internal-IVR (F366pUF6HNHeg) --> 7325553535 at outsideProvider
> (Port 10000 Closed)
> (Port 10001 Closed)
> (Port 10002 Closed)
> (Port 10003 Closed)
>
>
>
> Seems like a bug.
> Anyone experienced this before... is there a fix..
>
> If no fix, anyone familiar enough with the codebase to point out how to
> update the port object/attribute for the stream?
> I'm troubleshooting/modifying code on my own, but wanted to cover all
> bases.
>
>
> Thanks,
>
> Paul W.
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20150701/7b2c999a/attachment.htm>