[asterisk-dev] ContactStatus AMI Event on PJSIP Reregistration

Olivier oza.4h07 at gmail.com
Thu Aug 16 02:37:39 CDT 2018


2018-08-15 19:00 GMT+02:00 <asterisk-dev-request at lists.digium.com>:

>
> Message: 3
> Date: Wed, 15 Aug 2018 11:58:21 -0300
> From: Joshua Colp <jcolp at digium.com>
> To: asterisk-dev at lists.digium.com
> Subject: Re: [asterisk-dev] ContactStatus AMI Event on PJSIP
>         Reregistration
> Message-ID:
>         <1534345101.543194.1475072552.34B4051D at webmail.messagingengine.com
> >
> Content-Type: text/plain; charset="utf-8"
>
> On Wed, Aug 15, 2018, at 11:54 AM, Leandro Dardini wrote:
> > While you work on the AMI events for PJSIP endpoints, don't forget the
> > issue with no AMI events issued when a PJSIP endpoint loses completely
> the
> > connectivity. If it de-registers, an event is fired, if you just pull the
> > plug, no events are generated.
>
> If properly configured (qualify is enabled) then an event will be
> generated that it has become unreachable[1]. Without qualify there is no
> way for Asterisk to know this.
>
> [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+13+
> ManagerEvent_ContactStatus
>
> --
> Joshua Colp
> Digium, Inc. | Senior Software Developer
> 445 Jan Davis Drive NW - Huntsville, AL 35806 - US
> Check us out at: www.digium.com & www.asterisk.org
>


Hello Joshua,

I can think of a RegistrationExpiredWithoutRenewal event that is quite
independant of Qualify settings and still can be useful.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20180816/5b408d88/attachment.html>


More information about the asterisk-dev mailing list