Hi Mike I know exacty same situation about BT100 that sometimes lost any packets.
like a DoS attack for BT100? ;-( mack_jpn [EMAIL PROTECTED] asterisk]# ping 192.168.XX.XX PING 192.168.XX.XX (192.168.XX.XX) from 192.168.XX.X : 56(84) bytes of data. 64 bytes from 192.168.XX.XX: icmp_seq=0 ttl=250 time=2 usec Warning: time of day goes back, taking countermeasures. 64 bytes from 192.168.XX.XX: icmp_seq=1 ttl=250 time=969 usec 64 bytes from 192.168.XX.XX: icmp_seq=2 ttl=250 time=766 usec 64 bytes from 192.168.XX.XX: icmp_seq=3 ttl=250 time=746 usec 64 bytes from 192.168.XX.XX: icmp_seq=4 ttl=250 time=829 usec 64 bytes from 192.168.XX.XX: icmp_seq=5 ttl=250 time=725 usec 64 bytes from 192.168.XX.XX: icmp_seq=6 ttl=250 time=735 usec 64 bytes from 192.168.XX.XX: icmp_seq=7 ttl=250 time=703 usec 64 bytes from 192.168.XX.XX: icmp_seq=9 ttl=250 time=670 usec 64 bytes from 192.168.XX.XX: icmp_seq=10 ttl=250 time=728 usec 64 bytes from 192.168.XX.XX: icmp_seq=11 ttl=250 time=711 usec 64 bytes from 192.168.XX.XX: icmp_seq=12 ttl=250 time=701 usec 64 bytes from 192.168.XX.XX: icmp_seq=13 ttl=250 time=707 usec 64 bytes from 192.168.XX.XX: icmp_seq=14 ttl=250 time=693 usec 64 bytes from 192.168.XX.XX: icmp_seq=15 ttl=250 time=692 usec 64 bytes from 192.168.XX.XX: icmp_seq=16 ttl=250 time=678 usec 64 bytes from 192.168.XX.XX: icmp_seq=17 ttl=250 time=673 usec 64 bytes from 192.168.XX.XX: icmp_seq=18 ttl=250 time=699 usec 64 bytes from 192.168.XX.XX: icmp_seq=19 ttl=250 time=683 usec 64 bytes from 192.168.XX.XX: icmp_seq=20 ttl=250 time=696 usec 64 bytes from 192.168.XX.XX: icmp_seq=21 ttl=250 time=714 usec 64 bytes from 192.168.XX.XX: icmp_seq=22 ttl=250 time=704 usec 64 bytes from 192.168.XX.XX: icmp_seq=23 ttl=250 time=701 usec 64 bytes from 192.168.XX.XX: icmp_seq=24 ttl=250 time=691 usec 64 bytes from 192.168.XX.XX: icmp_seq=25 ttl=250 time=670 usec 64 bytes from 192.168.XX.XX: icmp_seq=26 ttl=250 time=690 usec 64 bytes from 192.168.XX.XX: icmp_seq=27 ttl=250 time=698 usec 64 bytes from 192.168.XX.XX: icmp_seq=28 ttl=250 time=713 usec 64 bytes from 192.168.XX.XX: icmp_seq=29 ttl=250 time=723 usec 64 bytes from 192.168.XX.XX: icmp_seq=30 ttl=250 time=703 usec 64 bytes from 192.168.XX.XX: icmp_seq=31 ttl=250 time=694 usec 64 bytes from 192.168.XX.XX: icmp_seq=32 ttl=250 time=685 usec 64 bytes from 192.168.XX.XX: icmp_seq=33 ttl=250 time=727 usec 64 bytes from 192.168.XX.XX: icmp_seq=34 ttl=250 time=720 usec 64 bytes from 192.168.XX.XX: icmp_seq=37 ttl=250 time=687 usec 64 bytes from 192.168.XX.XX: icmp_seq=38 ttl=250 time=704 usec 64 bytes from 192.168.XX.XX: icmp_seq=39 ttl=250 time=686 usec --- 192.168.XX.XX ping statistics --- 40 packets transmitted, 37 packets received, 7% packet loss round-trip min/avg/max/mdev = 0.002/0.695/0.969/0.126 ms On Sun, 04 Jan 2004 20:16:31 -0800 Mike Machado <[EMAIL PROTECTED]> wrote: > I am trying to get the handytone 286 to make a very simple call to * and > having problems. It registers with * just fine, but when I place a call > (to echo test, for example), the RTP stream seems to have problems > opening. Here is there error I get in *: snip _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users