25 Oct
2013
25 Oct
'13
5:18 p.m.
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
25 Oct
25 Oct
5:21 p.m.
Yup.
mediaproxy-ng is still a bit noisy :-)
Peter
On 25 October 2013 15:18, Juha Heinanen <jh(a)tutpro.com> 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
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
Peter Dunkley
Technical Director
Crocodile RCS Ltd
5:22 p.m.
i'm also seeing repeatedly kernelizing messages. why the streams are
continuously re-kernelized?
-- juha
Oct 25 17:18:49 rautu mediaproxy-ng[3966]: Successful STUN binding request on port 50038
from 87.95.166.173:59749
Oct 25 17:18:49 rautu mediaproxy-ng[3966]: Successful STUN binding request on port 50038
from 192.98.102.30:55958
Oct 25 17:18:50 rautu mediaproxy-ng[3966]: Successful STUN binding request on port 50038
from 87.95.166.173:59749
Oct 25 17:18:50 rautu mediaproxy-ng[3966]: Successful STUN binding request on port 50038
from 192.98.102.30:55958
Oct 25 17:18:51 rautu mediaproxy-ng[3966]: [g0fos3m93lvfdh4emltj] Confirmed peer
information for port 50036 - 192.98.102.30:10946
Oct 25 17:18:51 rautu mediaproxy-ng[3966]: Successful STUN binding request on port 50038
from 87.95.166.173:59749
Oct 25 17:18:51 rautu mediaproxy-ng[3966]: Successful STUN binding request on port 50038
from 192.98.102.30:55958
Oct 25 17:18:51 rautu mediaproxy-ng[3966]: [g0fos3m93lvfdh4emltj] Confirmed peer
information for port 50038 - 192.98.102.30:55958
Oct 25 17:18:51 rautu mediaproxy-ng[3966]: [g0fos3m93lvfdh4emltj] Kernelizing RTP streams
Oct 25 17:18:52 rautu mediaproxy-ng[3966]: [g0fos3m93lvfdh4emltj] Kernelizing RTP streams
Oct 25 17:18:52 rautu mediaproxy-ng[3966]: Successful STUN binding request on port 50038
from 87.95.166.173:59749
Oct 25 17:18:52 rautu mediaproxy-ng[3966]: Successful STUN binding request on port 50038
from 192.98.102.30:55958
Oct 25 17:18:52 rautu mediaproxy-ng[3966]: [g0fos3m93lvfdh4emltj] Kernelizing RTP streams
Oct 25 17:18:53 rautu mediaproxy-ng[3966]: Successful STUN binding request on port 50038
from 87.95.166.173:59749
Oct 25 17:18:53 rautu mediaproxy-ng[3966]: Successful STUN binding request on port 50038
from 192.98.102.30:55958
Oct 25 17:18:53 rautu mediaproxy-ng[3966]: [g0fos3m93lvfdh4emltj] Kernelizing RTP streams
...
4046
days inactive
4046
days old
2 comments
2 participants
participants (2)
-
Juha Heinanen -
Peter Dunkley