2009/2/17 Marc STORCK <msto...@voipgate.com> > Asterisk doesn't use PING to check the STATUS, it uses a SIP OPTION > message. >
Yes. I think that simply, in this case, the endpoint (SIP phone) is just broken : it wouldn't reply to anything ... I'm not 100% sure now, but wouldn't be surprised ... > > > Regards, > > > > Marc > > > > *From:* asterisk-users-boun...@lists.digium.com [mailto: > asterisk-users-boun...@lists.digium.com] *On Behalf Of *Olivier > *Sent:* mardi 17 février 2009 14:06 > *To:* Asterisk Users Mailing List - Non-Commercial Discussion > *Subject:* [asterisk-users] Pingable and Unreachable at the same time ! > > > > Hi, > > Has anyone met something like this ? > > dialor*CLI> sip show peers > Name/username Host Dyn Nat ACL Port Status > 7541/7541 (Unspecified) D 0 UNKNOWN > 7540/7540 (Unspecified) D 0 UNKNOWN > 7534/7534 (Unspecified) D 0 UNKNOWN > 7533/7533 (Unspecified) D 0 UNKNOWN > 7531/7531 192.168.100.199 D 5060 OK (10 ms) > 7530/7530 192.168.100.196 D 5060 UNREACHABLE > patton/patton 192.168.100.52 D 5060 OK (33 ms) > trunk/trunk4ipbx 192.168.64.2 5060 OK (1 ms) > 8 sip peers [Monitored: 3 online, 5 offline Unmonitored: 0 online, 0 > offline] > dialor*CLI> !ping 192.168.100.196 > PING 192.168.100.196 (192.168.100.196) 56(84) bytes of data. > 64 bytes from 192.168.100.196: icmp_seq=1 ttl=64 time=0.334 ms > 64 bytes from 192.168.100.196: icmp_seq=2 ttl=64 time=0.305 ms > 64 bytes from 192.168.100.196: icmp_seq=3 ttl=64 time=0.305 ms > > Any explaination ? > > Regards > > _______________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >
_______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users