On 02/09/2020 13:46, Pete Eisengrein wrote:
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...
Sounds like the timer for refreshing the
Thanks Carlos.
I did try searching the web, and thus the 3CX forums, before emailing the
group but came up blank.
We will move to unauthenticated, IP-based trust if necessary, but that's
usually a last resort. But I will ask about the low-level settings. Thanks
for the advice.
On Wed, Sep 2,
We host 3CX for our customers, in our own infrastructure, and manage it for
them. I have an advanced certification with them, but this sort of thing
was never covered in training, and I've never heard of it before. Our core
infrastructure is Asterisk (where all other servers register to). So
Back some time ago, we had a customer using 3CX to our Metaswitch… somewhat
similar issues.
Every time their 3CX had a hiccup, they too expected us to fix their issue… we
could prove via capture it wasn’t us. We tried everything we could come up
with… no luck. Finally suggested they engage
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
