Displaying 3 results from an estimated 3 matches for "36ms".
Did you mean:
360s
2008 Oct 19
2
Latency woes, qos the fix?
...1038 OK (133 ms)
This seems pretty high when my ping time from a host on the same
network is ~30ms:
Pinging 209.251.157.93 with 32 bytes of data:
Reply from 209.251.157.93: bytes=32 time=30ms TTL=51
Reply from 209.251.157.93: bytes=32 time=27ms TTL=51
Reply from 209.251.157.93: bytes=32 time=36ms TTL=51
Reply from 209.251.157.93: bytes=32 time=28ms TTL=51
Any suggestions or is this normal?
Should I enable qos on my Cisco 3725 router and 2950 switch?
Would I also need to enable the following in the sip.conf
;tos_sip=cs3 ; Sets TOS for SIP packets.
;tos_audio=ef...
2013 Oct 01
1
Extensions fail to register themselves when all trunks are unreachable.
...al extension, and, obviously, I can't do
any internal call.
On the log I see only lines like:
[2013-09-30 01:35:04] NOTICE[1827] chan_sip.c: Peer 'xxx' is now
UNREACHABLE! Last qualify: 36
and then
[2013-09-30 01:35:07] NOTICE[1827] chan_sip.c: Peer 'yyy' is now
Reachable. (36ms / 2000ms)
How can I troubleshot this issue?
Thank you very much in advance.
Francesco Namuri
2016 Sep 16
3
Upgrade to 4.5 error (SLES 12 SP1)
Hi,
i upgrade to sles sp1 with sernet packages and get the following error after upgrade. Its looks like that port 135 will not reached.
Anyone who have an information about that or a solution?
Thanks
Sven
orion:~ # samba-tool drs showrepl
Failed to connect host 192.168.24.2 on port 135 - NT_STATUS_CONNECTION_REFUSED
Failed to connect host 192.168.24.2 (orion.domain.local) on port 135 -