[VoiceOps] 3CX Trunk Unregistering

[Kent Adams]

Pete,

Does the same behavior happen regardless of how they are registered?
Specifically SRV, vs A record, vs IP registration? We have experienced some
peculiar behavior of this kind with customers and found that changing the
host resolution method to be an effective strategy for "fixing" such
problems.

Thanks,

Kent

On Wed, Sep 2, 2020 at 8:47 AM Pete Eisengrein <peeip989 at gmail.com> wrote:

> Hi all.
>
> I have a customer running 3CX who sometimes has calling problems because
> the trunk becomes unregistered from our Broadworks platform. When you look
> at the REGISTERs, there are a couple peculiarities:
>
>
>    1. 3CX sends an un-REGISTER (expires=0) right before it re-REGISTERs
>    rather than just re-registering the session
>    2. 3CX sometimes, but not always, starts a new session (new Call-ID)
>    for the "new" REGISTER rather than simply refreshing the existing session
>    3. Not a problem, but something I find odd and worth mentioning is
>    that it sends the User-Agent info when it un-registers but *not *when
>    it registers
>
>
> The problem comes in when we get the un-REGISTER but it is not followed by
> a new REGISTER and calls begin to fail. The customer is obviously
> frustrated and is expecting *me *to do something about it, but....
>
> Anyone familiar with 3CX and can give advice? Any idea why it behaves this
> way? They're running v16.0.5.619 (based on #3 above).
>
> Thanks in advance.
> -Pete
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20200902/7eb57a88/attachment.htm>