Mar 10 13:51:35 sun-Alienware-X51-R2 turnserver: 672: session 128000000000000001: user <>: incoming packet BINDING processed, success
Mar 10 13:51:35 sun-Alienware-X51-R2 turnserver: 672: IPv4. tcp or tls connected to:
82.143.92.22:58024Mar 10 13:51:35 sun-Alienware-X51-R2 turnserver: 672: session 001000000000000001: user <>: incoming packet message processed, error 401
Mar 10 13:51:35 sun-Alienware-X51-R2 turnserver: 672: IPv4. Server relay addr:
82.143.92.18:80Mar 10 13:51:35 sun-Alienware-X51-R2 turnserver: 672: IPv4. Local relay addr:
82.143.92.18:62022Mar 10 13:51:35 sun-Alienware-X51-R2 turnserver: 672: session 001000000000000001: new, username=<root>, lifetime=600
Mar 10 13:51:35 sun-Alienware-X51-R2 turnserver: 672: session 001000000000000001: user <root>: incoming packet ALLOCATE processed, success
Mar 10 13:51:35 sun-Alienware-X51-R2 turnserver: 672: session 001000000000000001: user <root>: incoming packet CREATE_PERMISSION processed, success
Mar 10 13:51:45 sun-Alienware-X51-R2 turnserver: 682: session 128000000000000001: user <>: incoming packet BINDING processed, success
Mar 10 13:51:55 sun-Alienware-X51-R2 turnserver: 692: session 128000000000000001: user <>: incoming packet BINDING processed, success
Mar 10 13:52:05 sun-Alienware-X51-R2 turnserver: 702: session 128000000000000001: user <>: incoming packet BINDING processed, success
Mar 10 13:52:15 sun-Alienware-X51-R2 turnserver: 712: session 128000000000000001: user <>: incoming packet BINDING processed, success
Mar 10 13:52:25 sun-Alienware-X51-R2 turnserver: 722: session 128000000000000001: user <>: incoming packet BINDING processed, success
Mar 10 13:52:35 sun-Alienware-X51-R2 turnserver: 732: session 128000000000000001: closed (2nd stage), user <>, reason: allocation watchdog determined stale session state
Mar 10 13:52:35 sun-Alienware-X51-R2 turnserver: 732: session 128000000000000002: user <>: incoming packet BINDING processed, success
Mar 10 13:52:45 sun-Alienware-X51-R2 turnserver: 742: session 128000000000000002: user <>: incoming packet BINDING processed, success
Mar 10 13:52:55 sun-Alienware-X51-R2 turnserver: 752: session 128000000000000002: user <>: incoming packet BINDING processed, success
Mar 10 13:53:05 sun-Alienware-X51-R2 turnserver: 762: session 128000000000000002: user <>: incoming packet BINDING processed, success
Mar 10 13:53:15 sun-Alienware-X51-R2 turnserver: 772: session 128000000000000002: user <>: incoming packet BINDING processed, success
Mar 10 13:53:25 sun-Alienware-X51-R2 turnserver: 782: session 128000000000000002: user <>: incoming packet BINDING processed, success
Mar 10 13:53:35 sun-Alienware-X51-R2 turnserver: 792: session 128000000000000002: closed (2nd stage), user <>, reason: allocation watchdog determined stale session state
Mar 10 13:53:35 sun-Alienware-X51-R2 turnserver: 792: session 128000000000000003: user <>: incoming packet BINDING processed, success
Mar 10 13:53:45 sun-Alienware-X51-R2 turnserver: 802: session 128000000000000003: user <>: incoming packet BINDING processed, success
Mar 10 13:53:55 sun-Alienware-X51-R2 turnserver: 812: session 128000000000000003: user <>: incoming packet BINDING processed, success
Mar 10 13:54:05 sun-Alienware-X51-R2 turnserver: 822: session 128000000000000003: user <>: incoming packet BINDING processed, success
This is a Big problem cause this session is waiting for Peer 2 which is FreeSWITCH IVR to do the allocation, create channel and start relay