Yup. mediaproxy-ng is still a bit noisy :-)
Peter On 25 October 2013 15:18, Juha Heinanen <[email protected]> wrote: > after call is established between jssip client and regular sip client > via mediaproxy-ng, it stats to continuously print to syslog these kind > of messages: > > Oct 25 17:14:22 rautu mediaproxy-ng[3966]: Successful STUN binding request > on port 50032 from 192.98.102.30:45284 > Oct 25 17:14:22 rautu mediaproxy-ng[3966]: Successful STUN binding request > on port 50033 from 192.98.102.30:40315 > Oct 25 17:14:23 rautu mediaproxy-ng[3966]: Successful STUN binding request > on port 50032 from 87.95.166.173:44738 > Oct 25 17:14:23 rautu mediaproxy-ng[3966]: Successful STUN binding request > on port 50033 from 87.95.166.173:43147 > Oct 25 17:14:23 rautu mediaproxy-ng[3966]: Successful STUN binding request > on port 50032 from 192.98.102.30:45284 > ... > > is that normal? > > -- juha > > _______________________________________________ > sr-dev mailing list > [email protected] > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev > -- Peter Dunkley Technical Director Crocodile RCS Ltd
_______________________________________________ sr-dev mailing list [email protected] http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
