[OpenSIPS-Users] mediaproxy 2.4.2

[Richard Revels]

This is interesting.  On one relay the ports are two apart from each other between the INVITE and 200 like I am used to seeing, but on the other relay the ports are all over the map.  However, I've done some test calls, and verified they used the second relay, and the audio set up fine on all of them.  I guess sometimes the media relay doesn't use consecutive ports.  Probably going to restart that one relay later anyway though.

Here is the tshark command I was using to look at this in my capture files.  Took me a while to get it right so it might save someone some time later.

tshark -T fields -e frame.time -e ip.src -e ip.dst -e sip.Method -e sip.Status-Code -e sip.Call-ID -e sdp.connection_info.address -e sdp.media.port -R "(sip.Method == INVITE or (sip.Status-Code == 200 and sip.CSeq.method == INVITE)) and sdp.connection_info.address == <MEDIA_RELAY_IP>" -r <CAPTUREFILENAME>

It will probably be tomorrow before I get that full trace to you.

Richard




On Dec 2, 2010, at 1:42 PM, Richard Revels wrote:

> Yeah, I used the function call on both the message and response.  This platform is production and does a lot of traffic each day.   I know this doesn't happen a lot or I would have gotten complaints by now.  I have no obvious error messages on either the dispatcher or relay so I don't have high hopes of troubleshooting this on this particular call.  I was really just wanting to verify that the media relay is expected to pick two ports that are one away from each other.
> 
> One other thing is that the same thing happened on a reinvite in this same call.  The ports were far from each other.
> 
> I do have a complete trace for the call.  Let me obfuscate all the IP addresses and I'll mail it.
> 
> Richard
> 
> On Dec 2, 2010, at 1:16 PM, Saúl Ibarra Corretgé wrote:
> 
>> Hi,
>> 
>> On 12/02/2010 07:04 PM, Richard Revels wrote:
>>> Here is the m line from an INVITE/200 after the messages were modified
>>> by use_media_proxy in each direction. The call happened to be mine and
>>> although it did not stay up long enough for me to be 100% sure, I think
>>> the person on the other end of the line was someone other than the
>>> person who called me. The call dropped due to my fumbling with buttons
>>> and hitting goodbye by mistake.
>>> 
>> 
>> I have never seen this so far. Can you confirm this somehow?
>> 
>>> I have only seen the port be offset by two when using the mediaproxy. Is
>>> that not the expected behavior always?
>>> 
>>> m=audio 52352 RTP/AVP 0 97 18 101.
>>> 
>>> m=audio 58676 RTP/AVP 0 101.
>>> 
>> 
>> Did you call use_media_proxy for *both* the caller and the callee? A SIP trace would help here.
>> 
>> 
>> Regards,
>> 
>> -- 
>> Saúl Ibarra Corretgé
>> AG Projects
>> 
>> _______________________________________________
>> 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/20101202/5c47a3cf/attachment.htm>