[OpenSIPS-Users] multiple use_media_proxy() calls

[Jeff Pyle]

Dan,

Brett and I communicated privately.  It turns out the majority of both our headaches with this issue is from the same, rather large carrier.  Does anything come to mind on how we might handle it?

I'd love an option I could include in engage_media_proxy to tell it to immediately set up the conntrack rules using the ports in the SDP rather than try to detect the ports on the fly.

Or, perhaps something already available in the code to force a reset of some sorts when the 18x w/ SDP message comes back?  By this point, the leaky media has stopped and the legit media is flowing.


- Jeff



From: Brett Nemeroff <brett at nemeroff.com<mailto:brett at nemeroff.com>>
Reply-To: OpenSIPS users mailling list <users at lists.opensips.org<mailto:users at lists.opensips.org>>
Date: Fri, 21 Jan 2011 10:37:15 -0500
To: OpenSIPS users mailling list <users at lists.opensips.org<mailto:users at lists.opensips.org>>
Subject: Re: [OpenSIPS-Users] multiple use_media_proxy() calls

On Fri, Jan 21, 2011 at 8:42 AM, Jeff Pyle chagrin I've seen a few more carriers exhibit this type of behavior.  One
way or another I think we're going to have to find a way to accommodate
it.


I'd just like to add my $0.02 here. I've had this exact same problem. It was a while ago, so I don't remember the details. But essentially the problem what that the media came from a different port than what was indicated in the SDP. The provider said that I should ignore the media and use the SDP and refused to work with me beyond that.

I'd bet that Jeff and I are having issues with the same carrier. And for what it's worth, it's a very big carrier.

-Brett


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20110121/753e5512/attachment.htm>