[OpenSIPS-Users] media-relay error - operation not permitted

[Muhammad Shahzad]

you can add logging like this,

log.warn(">>>>> Got data from host %s:%d <<<<<<" % (host, port))

If you put this line in mediacontrol.py just above line 130 (where the
error is reported in syslog) and then restart the service then it will
print this warning for each call and give us some hint of the problem when
it happens.

Thank you.


On Fri, Feb 8, 2013 at 10:08 PM, Jeff Pyle <jpyle at fidelityvoice.com> wrote:

> Hi Muhammed,
>
>
> On Fri, Feb 8, 2013 at 3:19 PM, Muhammad Shahzad <shaheryarkh at gmail.com>wrote:
>
>> In my previous experience, i see this error due to one of following
>> reasons.
>>
>> 1. The media ports you have specified in media proxy configuration
>> overlaps some other service port range, e.g. in case you are running media
>> proxy and asterisk on same machine and RTP port range of asterisk overlaps
>> media proxy port range.
>>
>
> Asterisk is running on the same machine.
>
> /etc/asterisk/rtp.conf contains:
>   rtpstart=16384
>   rtpend=20480
>
>  /etc/mediaproxy/config.ini contains:
>   port_range = 20482:32768
>
> Having said that, one relay machine does see more Asterisk activity than
> the other.  Still it's activity is in the calls-per-minute range, not
> calls-per-second.
>
> 2. Check dmesg, do you see this message or any relevant message from
>> network stack or ethernet driver there?
>>
>
> No.  The last relevant line is:
>   [   44.905812] ctnetlink v0.93: registering with nfnetlink.
>
> Most "irrelevant" lines are promiscuous mode reports from my tshark
> testing.  Otherwise,
>   [40380457.905028] Machine check events logged
>
> The machine's uptime is just over 500 days.
>
>
>> 3. Check syslog and see if you get following message or something similar
>> from nf_conntrack.
>>
>> nf_conntrack: table full, dropping packet
>>
>
> Nothing of the sort.
>
> 4. Check ulimit and selinux, but seems from your previous posts on this
>> issue that they are fine.
>>
>
> ulimit is handled by the application itself I believe.  selinux has never
> been configured.
>
>
>> 5. Do you have any SNAT or Multicast related rule in iptables?
>>
>
> No.  There is no *nat table defined at all, only *mangle (to remark DSCP
> EF) and *filter (basic INPUT security).  No mention of multicast anywhere.
>  There is IPv6 but it's not used for this application.
>
>
> Saúl,
>
> I'd be happy to add a logging line, but I'm not familiar enough with
> Python to know what to add where.  Guidance is welcome!
>
>
>
> - Jeff
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>


-- 
Muhammad Shahzad
-----------------------------------
CISCO Rich Media Communication Specialist (CRMCS)
CISCO Certified Network Associate (CCNA)
Cell: +49 176 99 83 10 85
MSN: shari_786pk at hotmail.com
Email: shaheryarkh at googlemail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20130208/6133dea6/attachment.htm>