Displaying 2 results from an estimated 2 matches for "6000ms".
Did you mean:
1000ms
2015 Apr 21
2
[BUG] imap-login segfault when running nmap -sV
....46.56.141:993 (IOD #1) EID 8
> NSOCK INFO [0.1550s] nsock_trace_handler_callback(): Callback: CONNECT SUCCESS for EID 8 [78.46.56.141:993]
> Service scan sending probe NULL to 78.46.56.141:993 (tcp)
> NSOCK INFO [0.1550s] nsock_read(): Read request from IOD #1 [78.46.56.141:993] (timeout: 6000ms) EID 18
> NSOCK INFO [6.1610s] nsock_trace_handler_callback(): Callback: READ TIMEOUT for EID 18 [78.46.56.141:993]
> Service scan sending probe GetRequest to 78.46.56.141:993 (tcp)
> NSOCK INFO [6.1610s] nsock_read(): Read request from IOD #1 [78.46.56.141:993] (timeout: 5000ms) EID 34
&g...
2013 Aug 21
1
IAX qualify timers
...w=ulaw
allow=ilbc
auth=md5
encryption=no
With this configuration, I expect that I can receive a response PONG
message from 172.16.6.45 up to 16 seconds after the POKE is sent out
before the peer is marked UNREACHABLE or LAGGED.
On the 172.16.6.45 machine I have configured an outgoing delay of
6000ms, effectively slowing down all outgoing traffic on the interface
by 6 seconds.
Here's what really happens:
- Asterisk is started
- outgoing POKE is sent
- even before the PONG is received (after about 3 seconds), the peer is
marked UNREACHABLE
- PONG message is received from 172.16.6.45 (6 se...