API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Dec 7th, 2023
51
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 37.16 KB | None | 0 0
raw download clone embed print report
  1. coturn | 33: (39): INFO: session 014000000000000001: realm <myserverdomain.org> user <>: incoming packet message processed, error 401: Unauthorized
  2. coturn | 33: (38): INFO: session 013000000000000001: realm <myserverdomain.org> user <>: incoming packet message processed, error 401: Unauthorized
  3. coturn | 33: (39): INFO: IPv4. Local relay addr: 192.168.172.102:57776
  4. coturn | 33: (39): INFO: session 014000000000000001: new, realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, lifetime=600
  5. coturn | 33: (39): INFO: session 014000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet ALLOCATE processed, success
  6. coturn | 33: (30): INFO: IPv4. tcp or tls connected to: xxx.xxx.xxx.xxx:11665
  7. coturn | 33: (30): INFO: session 005000000000000001: realm <myserverdomain.org> user <>: incoming packet message processed, error 401: Unauthorized
  8. coturn | 34: (35): INFO: IPv4. tcp or tls connected to: xxx.xxx.xxx.xxx:51853
  9. coturn | 34: (30): INFO: IPv4. Local relay addr: 192.168.172.102:63140
  10. coturn | 34: (30): INFO: session 005000000000000001: new, realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, lifetime=600
  11. coturn | 34: (30): INFO: session 005000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet ALLOCATE processed, success
  12. coturn | 34: (35): INFO: session 010000000000000001: realm <myserverdomain.org> user <>: incoming packet message processed, error 401: Unauthorized
  13. coturn | 34: (38): INFO: IPv4. Local relay addr: 192.168.172.102:63133
  14. coturn | 34: (38): INFO: session 013000000000000001: new, realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, lifetime=600
  15. coturn | 34: (38): INFO: session 013000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet ALLOCATE processed, success
  16. coturn | 34: (27): INFO: session 002000000000000001: realm <myserverdomain.org> user <>: incoming packet message processed, error 401: Unauthorized
  17. coturn | 34: (35): INFO: IPv4. Local relay addr: 192.168.172.102:59423
  18. coturn | 34: (35): INFO: session 010000000000000001: new, realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, lifetime=600
  19. coturn | 34: (35): INFO: session 010000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet ALLOCATE processed, success
  20. coturn | 34: (27): INFO: IPv4. Local relay addr: 192.168.172.102:65104
  21. coturn | 34: (27): INFO: session 002000000000000001: new, realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, lifetime=600
  22. coturn | 34: (27): INFO: session 002000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet ALLOCATE processed, success
  23. coturn | 34: (26): INFO: IPv4. tcp or tls connected to: xxx.xxx.xxx.xxx:18176
  24. coturn | 34: (26): INFO: session 001000000000000001: realm <myserverdomain.org> user <>: incoming packet message processed, error 401: Unauthorized
  25. coturn | 34: (33): INFO: session 008000000000000001: realm <myserverdomain.org> user <>: incoming packet message processed, error 401: Unauthorized
  26. coturn | 34: (27): INFO: IPv4. tcp or tls connected to: xxx.xxx.xxx.xxx:46581
  27. coturn | 34: (27): INFO: session 002000000000000002: realm <myserverdomain.org> user <>: incoming packet message processed, error 401: Unauthorized
  28. coturn | 34: (26): INFO: IPv4. Local relay addr: 192.168.172.102:54031
  29. coturn | 34: (26): INFO: session 001000000000000001: new, realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, lifetime=600
  30. coturn | 34: (26): INFO: session 001000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet ALLOCATE processed, success
  31. coturn | 34: (33): INFO: IPv4. Local relay addr: 192.168.172.102:50965
  32. coturn | 34: (33): INFO: session 008000000000000001: new, realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, lifetime=600
  33. coturn | 34: (33): INFO: session 008000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet ALLOCATE processed, success
  34. coturn | 34: (27): INFO: IPv4. Local relay addr: 192.168.172.102:60992
  35. coturn | 34: (27): INFO: session 002000000000000002: new, realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, lifetime=600
  36. coturn | 34: (27): INFO: session 002000000000000002: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet ALLOCATE processed, success
  37. coturn | 70: (32): INFO: IPv4. tcp or tls connected to: xxx.xxx.xxx.xxx:6631
  38. coturn | 70: (32): INFO: session 007000000000000001: realm <myserverdomain.org> user <>: incoming packet message processed, error 401: Unauthorized
  39. coturn | 70: (39): INFO: session 014000000000000002: realm <myserverdomain.org> user <>: incoming packet message processed, error 401: Unauthorized
  40. coturn | 70: (32): INFO: IPv4. Local relay addr: 192.168.172.102:65309
  41. coturn | 70: (32): INFO: session 007000000000000001: new, realm=<myserverdomain.org>, username=<1234567654:@otheruser:m.myserverdomain.org>, lifetime=600
  42. coturn | 70: (32): INFO: session 007000000000000001: realm <myserverdomain.org> user <1234567654:@otheruser:m.myserverdomain.org>: incoming packet ALLOCATE processed, success
  43. coturn | 70: (39): INFO: IPv4. Local relay addr: 192.168.172.102:51329
  44. coturn | 70: (39): INFO: session 014000000000000002: new, realm=<myserverdomain.org>, username=<1234567654:@otheruser:m.myserverdomain.org>, lifetime=600
  45. coturn | 70: (39): INFO: session 014000000000000002: realm <myserverdomain.org> user <1234567654:@otheruser:m.myserverdomain.org>: incoming packet ALLOCATE processed, success
  46. coturn | 70: (39): INFO: session 014000000000000002: peer 192.168.172.102 lifetime updated: 300
  47. coturn | 70: (39): INFO: session 014000000000000002: realm <myserverdomain.org> user <1234567654:@otheruser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  48. coturn | 70: (39): INFO: session 014000000000000002: peer 192.168.172.102 lifetime updated: 300
  49. coturn | 70: (39): INFO: session 014000000000000002: realm <myserverdomain.org> user <1234567654:@otheruser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  50. coturn | 70: (39): INFO: session 014000000000000002: peer 192.168.172.102 lifetime updated: 300
  51. coturn | 70: (39): INFO: session 014000000000000002: realm <myserverdomain.org> user <1234567654:@otheruser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  52. coturn | 70: (32): INFO: session 007000000000000001: peer 192.168.172.102 lifetime updated: 300
  53. coturn | 70: (39): INFO: session 014000000000000002: peer 192.168.172.102 lifetime updated: 300
  54. coturn | 70: (32): INFO: session 007000000000000001: realm <myserverdomain.org> user <1234567654:@otheruser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  55. coturn | 70: (39): INFO: session 014000000000000002: realm <myserverdomain.org> user <1234567654:@otheruser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  56. coturn | 70: (32): INFO: session 007000000000000001: peer 192.168.172.102 lifetime updated: 300
  57. coturn | 70: (32): INFO: session 007000000000000001: realm <myserverdomain.org> user <1234567654:@otheruser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  58. coturn | 70: (32): INFO: session 007000000000000001: peer 192.168.172.102 lifetime updated: 300
  59. coturn | 70: (32): INFO: session 007000000000000001: realm <myserverdomain.org> user <1234567654:@otheruser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  60. coturn | 70: (32): INFO: session 007000000000000001: peer 192.168.172.102 lifetime updated: 300
  61. coturn | 70: (32): INFO: session 007000000000000001: realm <myserverdomain.org> user <1234567654:@otheruser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  62. coturn | 71: (27): INFO: session 002000000000000001: refreshed, realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, lifetime=0
  63. coturn | 71: (27): INFO: session 002000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet REFRESH processed, success
  64. coturn | 71: (26): INFO: session 001000000000000001: refreshed, realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, lifetime=0
  65. coturn | 71: (26): INFO: session 001000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet REFRESH processed, success
  66. coturn | 71: (26): INFO: session 001000000000000001: TCP socket closed remotely xxx.xxx.xxx.xxx:18176
  67. coturn | 71: (26): INFO: session 001000000000000001: usage: realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, rp=3, rb=276, sp=3, sb=276
  68. coturn | 71: (26): INFO: session 001000000000000001: peer usage: realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, rp=0, rb=0, sp=0, sb=0
  69. coturn | 71: (26): INFO: session 001000000000000001: closed (2nd stage), user <1234567890:@myuser:m.myserverdomain.org> realm <myserverdomain.org> origin <>, local 192.168.172.102:3478, remote xxx.xxx.xxx.xxx:18176, reason: TCP connection closed by client (callback)
  70. coturn | 71: (26): INFO: session 001000000000000001: delete: realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>
  71. coturn | 71: (33): INFO: session 008000000000000001: refreshed, realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, lifetime=0
  72. coturn | 71: (33): INFO: session 008000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet REFRESH processed, success
  73. coturn | 71: (27): INFO: session 002000000000000002: refreshed, realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, lifetime=0
  74. coturn | 71: (27): INFO: session 002000000000000002: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet REFRESH processed, success
  75. coturn | 71: (27): INFO: session 002000000000000002: TCP socket closed remotely xxx.xxx.xxx.xxx:46581
  76. coturn | 71: (27): INFO: session 002000000000000002: usage: realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, rp=3, rb=276, sp=3, sb=276
  77. coturn | 71: (27): INFO: session 002000000000000002: peer usage: realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, rp=0, rb=0, sp=0, sb=0
  78. coturn | 71: (27): INFO: session 002000000000000002: closed (2nd stage), user <1234567890:@myuser:m.myserverdomain.org> realm <myserverdomain.org> origin <>, local 192.168.172.102:3478, remote xxx.xxx.xxx.xxx:46581, reason: TCP connection closed by client (callback)
  79. coturn | 71: (27): INFO: session 002000000000000002: delete: realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>
  80. coturn | 72: (27): INFO: session 002000000000000001: usage: realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, rp=7, rb=356, sp=7, sb=596
  81. coturn | 72: (27): INFO: session 002000000000000001: peer usage: realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, rp=0, rb=0, sp=0, sb=0
  82. coturn | 72: (27): INFO: session 002000000000000001: closed (2nd stage), user <1234567890:@myuser:m.myserverdomain.org> realm <myserverdomain.org> origin <>, local 192.168.172.102:3478, remote xxx.xxx.xxx.xxx:21385, reason: allocation timeout
  83. coturn | 72: (27): INFO: session 002000000000000001: delete: realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>
  84. coturn | 72: (33): INFO: session 008000000000000001: usage: realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, rp=7, rb=356, sp=7, sb=596
  85. coturn | 72: (33): INFO: session 008000000000000001: peer usage: realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, rp=0, rb=0, sp=0, sb=0
  86. coturn | 72: (33): INFO: session 008000000000000001: closed (2nd stage), user <1234567890:@myuser:m.myserverdomain.org> realm <myserverdomain.org> origin <>, local 192.168.172.102:3478, remote xxx.xxx.xxx.xxx:40101, reason: allocation timeout
  87. coturn | 72: (33): INFO: session 008000000000000001: delete: realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>
  88. coturn | 73: (30): INFO: session 005000000000000001: peer 192.168.0.166 lifetime updated: 300
  89. coturn | 73: (30): INFO: session 005000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  90. coturn | 73: (39): INFO: session 014000000000000001: peer 192.168.0.166 lifetime updated: 300
  91. coturn | 73: (39): INFO: session 014000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  92. coturn | 73: (38): INFO: session 013000000000000001: peer 192.168.0.166 lifetime updated: 300
  93. coturn | 73: (38): INFO: session 013000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  94. coturn | 73: (35): INFO: session 010000000000000001: peer 192.168.0.166 lifetime updated: 300
  95. coturn | 73: (35): INFO: session 010000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  96. coturn | 73: (30): INFO: session 005000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, error 403: Forbidden IP
  97. coturn | 73: (30): INFO: session 005000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet message processed, error 403: Forbidden IP
  98. coturn | 73: (39): INFO: session 014000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, error 403: Forbidden IP
  99. coturn | 73: (39): INFO: session 014000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet message processed, error 403: Forbidden IP
  100. coturn | 73: (35): INFO: session 010000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, error 403: Forbidden IP
  101. coturn | 73: (35): INFO: session 010000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet message processed, error 403: Forbidden IP
  102. coturn | 73: (38): INFO: session 013000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, error 403: Forbidden IP
  103. coturn | 73: (38): INFO: session 013000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet message processed, error 403: Forbidden IP
  104. coturn | 73: (30): INFO: session 005000000000000001: peer xxx.xxx.xxx.xxx lifetime updated: 300
  105. coturn | 73: (30): INFO: session 005000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  106. coturn | 73: (35): INFO: session 010000000000000001: peer xxx.xxx.xxx.xxx lifetime updated: 300
  107. coturn | 73: (35): INFO: session 010000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  108. coturn | 73: (39): INFO: session 014000000000000001: peer xxx.xxx.xxx.xxx lifetime updated: 300
  109. coturn | 73: (39): INFO: session 014000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  110. coturn | 73: (38): INFO: session 013000000000000001: peer xxx.xxx.xxx.xxx lifetime updated: 300
  111. coturn | 73: (38): INFO: session 013000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  112. coturn | 73: (35): INFO: session 010000000000000001: peer 192.168.172.102 lifetime updated: 300
  113. coturn | 73: (35): INFO: session 010000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  114. coturn | 73: (30): INFO: session 005000000000000001: peer 192.168.172.102 lifetime updated: 300
  115. coturn | 73: (30): INFO: session 005000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  116. coturn | 73: (39): INFO: session 014000000000000001: peer 192.168.172.102 lifetime updated: 300
  117. coturn | 73: (39): INFO: session 014000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  118. coturn | 73: (39): INFO: session 014000000000000001: peer 192.168.172.102 lifetime updated: 300
  119. coturn | 73: (39): INFO: session 014000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  120. coturn | 73: (38): INFO: session 013000000000000001: peer 192.168.172.102 lifetime updated: 300
  121. coturn | 73: (38): INFO: session 013000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  122. coturn | 73: (30): INFO: session 005000000000000001: peer 192.168.172.102 lifetime updated: 300
  123. coturn | 73: (30): INFO: session 005000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  124. coturn | 73: (35): INFO: session 010000000000000001: peer 192.168.172.102 lifetime updated: 300
  125. coturn | 73: (35): INFO: session 010000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  126. coturn | 73: (38): INFO: session 013000000000000001: peer 192.168.172.102 lifetime updated: 300
  127. coturn | 73: (38): INFO: session 013000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  128. coturn | 73: (39): INFO: session 014000000000000002: peer 192.168.172.102 lifetime updated: 600
  129. coturn | 73: (39): INFO: session 014000000000000002: realm <myserverdomain.org> user <1234567654:@otheruser:m.myserverdomain.org>: incoming packet CHANNEL_BIND processed, success
  130. coturn | 73: (39): INFO: session 014000000000000001: peer 192.168.172.102 lifetime updated: 600
  131. coturn | 73: (39): INFO: session 014000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CHANNEL_BIND processed, success
  132. coturn | 81: (30): INFO: session 005000000000000002: realm <myserverdomain.org> user <>: incoming packet message processed, error 401: Unauthorized
  133. coturn | 81: (38): INFO: IPv4. tcp or tls connected to: xxx.xxx.xxx.xxx:6593
  134. coturn | 81: (38): INFO: session 013000000000000002: realm <myserverdomain.org> user <>: incoming packet message processed, error 401: Unauthorized
  135. coturn | 81: (30): INFO: IPv4. Local relay addr: 192.168.172.102:57136
  136. coturn | 81: (30): INFO: session 005000000000000002: new, realm=<myserverdomain.org>, username=<1701941875:@otheruser:m.myserverdomain.org>, lifetime=600
  137. coturn | 81: (30): INFO: session 005000000000000002: realm <myserverdomain.org> user <1701941875:@otheruser:m.myserverdomain.org>: incoming packet ALLOCATE processed, success
  138. coturn | 81: (38): INFO: IPv4. Local relay addr: 192.168.172.102:53024
  139. coturn | 81: (38): INFO: session 013000000000000002: new, realm=<myserverdomain.org>, username=<1701941875:@otheruser:m.myserverdomain.org>, lifetime=600
  140. coturn | 81: (38): INFO: session 013000000000000002: realm <myserverdomain.org> user <1701941875:@otheruser:m.myserverdomain.org>: incoming packet ALLOCATE processed, success
  141. coturn | 81: (30): INFO: session 005000000000000002: peer 192.168.172.102 lifetime updated: 300
  142. coturn | 81: (30): INFO: session 005000000000000002: realm <myserverdomain.org> user <1701941875:@otheruser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  143. coturn | 81: (30): INFO: session 005000000000000002: peer 192.168.172.102 lifetime updated: 300
  144. coturn | 81: (30): INFO: session 005000000000000002: realm <myserverdomain.org> user <1701941875:@otheruser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  145. coturn | 81: (30): INFO: session 005000000000000002: peer 192.168.172.102 lifetime updated: 300
  146. coturn | 81: (30): INFO: session 005000000000000002: realm <myserverdomain.org> user <1701941875:@otheruser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  147. coturn | 81: (30): INFO: session 005000000000000002: peer 192.168.172.102 lifetime updated: 300
  148. coturn | 81: (30): INFO: session 005000000000000002: realm <myserverdomain.org> user <1701941875:@otheruser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  149. coturn | 81: (38): INFO: session 013000000000000002: peer 192.168.172.102 lifetime updated: 300
  150. coturn | 81: (38): INFO: session 013000000000000002: realm <myserverdomain.org> user <1701941875:@otheruser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  151. coturn | 81: (38): INFO: session 013000000000000002: peer 192.168.172.102 lifetime updated: 300
  152. coturn | 81: (38): INFO: session 013000000000000002: realm <myserverdomain.org> user <1701941875:@otheruser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  153. coturn | 81: (38): INFO: session 013000000000000002: peer 192.168.172.102 lifetime updated: 300
  154. coturn | 81: (38): INFO: session 013000000000000002: realm <myserverdomain.org> user <1701941875:@otheruser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  155. coturn | 81: (38): INFO: session 013000000000000002: peer 192.168.172.102 lifetime updated: 300
  156. coturn | 81: (38): INFO: session 013000000000000002: realm <myserverdomain.org> user <1701941875:@otheruser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  157. coturn | 81: (39): INFO: session 014000000000000001: peer 192.168.172.102 lifetime updated: 300
  158. coturn | 81: (39): INFO: session 014000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  159. coturn | 81: (30): INFO: session 005000000000000002: peer 192.168.172.102 lifetime updated: 600
  160. coturn | 81: (30): INFO: session 005000000000000002: realm <myserverdomain.org> user <1701941875:@otheruser:m.myserverdomain.org>: incoming packet CHANNEL_BIND processed, success
  161. coturn | 81: (38): INFO: session 013000000000000001: peer 192.168.172.102 lifetime updated: 300
  162. coturn | 81: (38): INFO: session 013000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  163. coturn | 81: (39): INFO: session 014000000000000001: peer 192.168.172.102 lifetime updated: 300
  164. coturn | 81: (39): INFO: session 014000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  165. coturn | 81: (30): INFO: session 005000000000000001: peer 192.168.172.102 lifetime updated: 300
  166. coturn | 81: (30): INFO: session 005000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  167. coturn | 81: (38): INFO: session 013000000000000001: peer 192.168.172.102 lifetime updated: 300
  168. coturn | 81: (38): INFO: session 013000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  169. coturn | 81: (30): INFO: session 005000000000000001: peer 192.168.172.102 lifetime updated: 300
  170. coturn | 81: (30): INFO: session 005000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  171. coturn | 81: (35): INFO: session 010000000000000001: peer 192.168.172.102 lifetime updated: 300
  172. coturn | 81: (35): INFO: session 010000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  173. coturn | 82: (35): INFO: session 010000000000000001: peer 192.168.172.102 lifetime updated: 300
  174. coturn | 82: (35): INFO: session 010000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  175. coturn | 82: (39): INFO: session 014000000000000001: peer 192.168.0.166 lifetime updated: 300
  176. coturn | 82: (39): INFO: session 014000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  177. coturn | 82: (30): INFO: session 005000000000000001: peer 192.168.0.166 lifetime updated: 300
  178. coturn | 82: (30): INFO: session 005000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  179. coturn | 82: (30): INFO: session 005000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, error 403: Forbidden IP
  180. coturn | 82: (30): INFO: session 005000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet message processed, error 403: Forbidden IP
  181. coturn | 82: (39): INFO: session 014000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, error 403: Forbidden IP
  182. coturn | 82: (39): INFO: session 014000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet message processed, error 403: Forbidden IP
  183. coturn | 82: (38): INFO: session 013000000000000001: peer 192.168.0.166 lifetime updated: 300
  184. coturn | 82: (38): INFO: session 013000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  185. coturn | 82: (35): INFO: session 010000000000000001: peer 192.168.0.166 lifetime updated: 300
  186. coturn | 82: (35): INFO: session 010000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  187. coturn | 82: (38): INFO: session 013000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, error 403: Forbidden IP
  188. coturn | 82: (38): INFO: session 013000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet message processed, error 403: Forbidden IP
  189. coturn | 82: (35): INFO: session 010000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, error 403: Forbidden IP
  190. coturn | 82: (35): INFO: session 010000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet message processed, error 403: Forbidden IP
  191. coturn | 83: (39): INFO: session 014000000000000001: peer xxx.xxx.xxx.xxx lifetime updated: 300
  192. coturn | 83: (30): INFO: session 005000000000000001: peer xxx.xxx.xxx.xxx lifetime updated: 300
  193. coturn | 83: (39): INFO: session 014000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  194. coturn | 83: (30): INFO: session 005000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  195. coturn | 83: (38): INFO: session 013000000000000001: peer xxx.xxx.xxx.xxx lifetime updated: 300
  196. coturn | 83: (38): INFO: session 013000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  197. coturn | 83: (35): INFO: session 010000000000000001: peer xxx.xxx.xxx.xxx lifetime updated: 300
  198. coturn | 83: (35): INFO: session 010000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet CREATE_PERMISSION processed, success
  199. coturn | 119: (30): INFO: session 005000000000000002: refreshed, realm=<myserverdomain.org>, username=<1701941875:@otheruser:m.myserverdomain.org>, lifetime=0
  200. coturn | 119: (30): INFO: session 005000000000000002: realm <myserverdomain.org> user <1701941875:@otheruser:m.myserverdomain.org>: incoming packet REFRESH processed, success
  201. coturn | 119: (38): INFO: session 013000000000000002: refreshed, realm=<myserverdomain.org>, username=<1701941875:@otheruser:m.myserverdomain.org>, lifetime=0
  202. coturn | 119: (38): INFO: session 013000000000000002: realm <myserverdomain.org> user <1701941875:@otheruser:m.myserverdomain.org>: incoming packet REFRESH processed, success
  203. coturn | 119: (38): INFO: session 013000000000000002: TCP socket closed remotely xxx.xxx.xxx.xxx:6593
  204. coturn | 119: (38): INFO: session 013000000000000002: usage: realm=<myserverdomain.org>, username=<1701941875:@otheruser:m.myserverdomain.org>, rp=49, rb=6332, sp=49, sb=5756
  205. coturn | 119: (38): INFO: session 013000000000000002: peer usage: realm=<myserverdomain.org>, username=<1701941875:@otheruser:m.myserverdomain.org>, rp=42, rb=2688, sp=42, sb=4032
  206. coturn | 119: (38): INFO: session 013000000000000002: closed (2nd stage), user <1701941875:@otheruser:m.myserverdomain.org> realm <myserverdomain.org> origin <>, local 192.168.172.102:3478, remote xxx.xxx.xxx.xxx:6593, reason: TCP connection closed by client (callback)
  207. coturn | 119: (38): INFO: session 013000000000000002: delete: realm=<myserverdomain.org>, username=<1701941875:@otheruser:m.myserverdomain.org>
  208. coturn | 119: (38): INFO: session 013000000000000002: peer 192.168.172.102 deleted
  209. coturn | 120: (30): INFO: session 005000000000000002: usage: realm=<myserverdomain.org>, username=<1701941875:@otheruser:m.myserverdomain.org>, rp=71, rb=8451, sp=63, sb=6252
  210. coturn | 120: (30): INFO: session 005000000000000002: peer usage: realm=<myserverdomain.org>, username=<1701941875:@otheruser:m.myserverdomain.org>, rp=51, rb=3264, sp=59, sb=6120
  211. coturn | 120: (30): INFO: session 005000000000000002: closed (2nd stage), user <1701941875:@otheruser:m.myserverdomain.org> realm <myserverdomain.org> origin <>, local 192.168.172.102:3478, remote xxx.xxx.xxx.xxx:6606, reason: allocation timeout
  212. coturn | 120: (30): INFO: session 005000000000000002: delete: realm=<myserverdomain.org>, username=<1701941875:@otheruser:m.myserverdomain.org>
  213. coturn | 120: (30): INFO: session 005000000000000002: peer 192.168.172.102 deleted
  214. coturn | 120: (32): INFO: session 007000000000000001: TCP socket closed remotely xxx.xxx.xxx.xxx:6631
  215. coturn | 120: (32): INFO: session 007000000000000001: usage: realm=<myserverdomain.org>, username=<1234567654:@otheruser:m.myserverdomain.org>, rp=22, rb=2776, sp=6, sb=472
  216. coturn | 120: (32): INFO: session 007000000000000001: peer usage: realm=<myserverdomain.org>, username=<1234567654:@otheruser:m.myserverdomain.org>, rp=0, rb=0, sp=16, sb=1536
  217. coturn | 120: (32): INFO: session 007000000000000001: closed (2nd stage), user <1234567654:@otheruser:m.myserverdomain.org> realm <myserverdomain.org> origin <>, local 192.168.172.102:3478, remote xxx.xxx.xxx.xxx:6631, reason: TCP connection closed by client (callback)
  218. coturn | 120: (32): INFO: session 007000000000000001: delete: realm=<myserverdomain.org>, username=<1234567654:@otheruser:m.myserverdomain.org>
  219. coturn | 120: (32): INFO: session 007000000000000001: peer 192.168.172.102 deleted
  220. coturn | 147: (39): INFO: session 014000000000000001: refreshed, realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, lifetime=0
  221. coturn | 147: (39): INFO: session 014000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet REFRESH processed, success
  222. coturn | 147: (30): INFO: session 005000000000000001: refreshed, realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, lifetime=0
  223. coturn | 147: (30): INFO: session 005000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet REFRESH processed, success
  224. coturn | 147: (30): INFO: session 005000000000000001: TCP socket closed remotely xxx.xxx.xxx.xxx:11665
  225. coturn | 147: (30): INFO: session 005000000000000001: usage: realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, rp=34, rb=3656, sp=34, sb=4272
  226. coturn | 147: (30): INFO: session 005000000000000001: peer usage: realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, rp=29, rb=2784, sp=21, sb=1344
  227. coturn | 147: (30): INFO: session 005000000000000001: closed (2nd stage), user <1234567890:@myuser:m.myserverdomain.org> realm <myserverdomain.org> origin <>, local 192.168.172.102:3478, remote xxx.xxx.xxx.xxx:11665, reason: TCP connection closed by client (callback)
  228. coturn | 147: (30): INFO: session 005000000000000001: delete: realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>
  229. coturn | 147: (30): INFO: session 005000000000000001: peer xxx.xxx.xxx.xxx deleted
  230. coturn | 147: (30): INFO: session 005000000000000001: peer 192.168.172.102 deleted
  231. coturn | 147: (30): INFO: session 005000000000000001: peer 192.168.0.166 deleted
  232. coturn | 147: (38): INFO: session 013000000000000001: refreshed, realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, lifetime=0
  233. coturn | 147: (35): INFO: session 010000000000000001: refreshed, realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, lifetime=0
  234. coturn | 147: (38): INFO: session 013000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet REFRESH processed, success
  235. coturn | 147: (35): INFO: session 010000000000000001: realm <myserverdomain.org> user <1234567890:@myuser:m.myserverdomain.org>: incoming packet REFRESH processed, success
  236. coturn | 147: (35): INFO: session 010000000000000001: TCP socket closed remotely xxx.xxx.xxx.xxx:51853
  237. coturn | 147: (35): INFO: session 010000000000000001: usage: realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, rp=33, rb=3556, sp=33, sb=4116
  238. coturn | 147: (35): INFO: session 010000000000000001: peer usage: realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, rp=28, rb=2688, sp=20, sb=1280
  239. coturn | 147: (35): INFO: session 010000000000000001: closed (2nd stage), user <1234567890:@myuser:m.myserverdomain.org> realm <myserverdomain.org> origin <>, local 192.168.172.102:3478, remote xxx.xxx.xxx.xxx:51853, reason: TCP connection closed by client (callback)
  240. coturn | 147: (35): INFO: session 010000000000000001: delete: realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>
  241. coturn | 147: (35): INFO: session 010000000000000001: peer xxx.xxx.xxx.xxx deleted
  242. coturn | 147: (35): INFO: session 010000000000000001: peer 192.168.172.102 deleted
  243. coturn | 147: (35): INFO: session 010000000000000001: peer 192.168.0.166 deleted
  244. coturn | 148: (39): INFO: session 014000000000000001: usage: realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, rp=140, rb=48494, sp=153, sb=37044
  245. coturn | 148: (39): INFO: session 014000000000000001: peer usage: realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, rp=132, rb=32729, sp=111, sb=44968
  246. coturn | 148: (39): INFO: session 014000000000000001: closed (2nd stage), user <1234567890:@myuser:m.myserverdomain.org> realm <myserverdomain.org> origin <>, local 192.168.172.102:3478, remote xxx.xxx.xxx.xxx:30229, reason: allocation timeout
  247. coturn | 148: (39): INFO: session 014000000000000001: delete: realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>
  248. coturn | 148: (39): INFO: session 014000000000000001: peer xxx.xxx.xxx.xxx deleted
  249. coturn | 148: (39): INFO: session 014000000000000001: peer 192.168.172.102 deleted
  250. coturn | 148: (39): INFO: session 014000000000000001: peer 192.168.0.166 deleted
  251. coturn | 148: (38): INFO: session 013000000000000001: usage: realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, rp=52, rb=4288, sp=52, sb=5908
  252. coturn | 148: (38): INFO: session 013000000000000001: peer usage: realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>, rp=32, rb=3040, sp=24, sb=1568
  253. coturn | 148: (38): INFO: session 013000000000000001: closed (2nd stage), user <1234567890:@myuser:m.myserverdomain.org> realm <myserverdomain.org> origin <>, local 192.168.172.102:3478, remote xxx.xxx.xxx.xxx:58514, reason: allocation timeout
  254. coturn | 148: (38): INFO: session 013000000000000001: delete: realm=<myserverdomain.org>, username=<1234567890:@myuser:m.myserverdomain.org>
  255. coturn | 148: (38): INFO: session 013000000000000001: peer xxx.xxx.xxx.xxx deleted
  256. coturn | 148: (38): INFO: session 013000000000000001: peer 192.168.172.102 deleted
  257. coturn | 148: (38): INFO: session 013000000000000001: peer 192.168.0.166 deleted
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!