On Thu, Aug 16, 2018, at 4:37 AM, Olivier wrote:
> Hello Joshua,
>
> I can think of a RegistrationExpiredWithoutRenewal event that is quite
> independant of Qualify settings and still can be useful.
I believe this should already occur.
My original question wasn't about refining ContactStatus
2018-08-15 19:00 GMT+02:00 :
>
> Message: 3
> Date: Wed, 15 Aug 2018 11:58:21 -0300
> From: Joshua Colp
> To: asterisk-dev@lists.digium.com
> Subject: Re: [asterisk-dev] ContactStatus AMI Event on PJSIP
> Reregistration
> Message-ID:
> <1534
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
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.
Leandro
Il giorno mer 15 ago 2018 alle ore
Kia ora,
I currently have a code review up[1] which removes the ContactStatus AMI event
when a PJSIP endpoint re-registers. I removed it as I believed the
ContactStatus event was redundant (as the status has not changed from the last
event that would have been sent). Does anyone currently rely
