Hi Nitesh,
The reachable/unreachable determination is not connected to registration
expiry parameters in any way.
There is a qualify= parameter (that has a default value, and I think it
may be on by default) that is associated with all SIP peers. It is
basically a way to say that the SIP peer should be pinged periodically
(with a blank SIP OPTIONS message that returns some sort of response from
the other end) and that if the round-trip latency on that transaction
exceeds whatever number of milliseconds, the host should be deemed
'unreachable' until the next ping is attempted and the RTL moves back
into
qualified territory. This is the parameter to qualify, e.g. qualify=2000
means declare the host unreachable if its round-trip latency through SIP
ping exceeds 2000 ms.
I generally find the behaviour of this facility to be rather spurious
with end-user phones and prone to false alarms, for whatever reason.
So, I either give it a really high value, or say qualify=no.
Best of luck,
-- Alex
On Wed, 3 Oct 2007, Nitesh Divecha wrote:
> Hello All,
>
> For some odd reasons my Asterisk is keep on loosing registration of my
> SIP devices. On the SIP device it shows I am RESISTED but when I do
"sip
> show peers" it shows my sip endpoints are "UNREACHABLE". And
it keeps on
> flapping "Peer '9099993456' is now UNREACHABLE!" and
"Peer '9099993456'
> is now REACHABLE!"...
>
> I changed my maxexpiry and defaultexpiry to 3600 in sip.conf but still
> it didn't help.
>
> I am using Asterisk 1.2.18 with Real-Time config.
>
> Any help will be appreciated...
>
> Cheers,
> Nitesh
>
>
>
>
> _______________________________________________
> --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
>
--
Alex Balashov
Evariste Systems
Web : http://www.evaristesys.com/
Tel : +1-678-954-0670
Direct : +1-678-954-0671