HT801 running 1.0.49.2 Register Before DNSSRV Failover behavior


#1

Hello @grandstream,

I’m having an issue with the behavior of the Register Before DNSSRV Failover setting.

Thank the link limits for the Base64.

Scenario:

An HT801 with the below(relevant?) settings running firmware 1.0.49.2

RGV2aWNlLlNlcnZpY2VzLlZvaWNlU2VydmljZS4xLlZvaWNlUHJvZmlsZS4xLlhfR1JBTkRTVFJF
QU1fUmVnaXN0ZXJCZWZvcmVETlNTUlZGYWlsb3ZlciwgdmFsdWU6IHRydWUKRGV2aWNlLlNlcnZp
Y2VzLlZvaWNlU2VydmljZS4xLlZvaWNlUHJvZmlsZS4xLlhfR1JBTkRTVFJFQU1fRE5TU1JWVXNl
UmVnaXN0ZXJlZElQLCB2YWx1ZTogZmFsc2UKRGV2aWNlLlNlcnZpY2VzLlZvaWNlU2VydmljZS4x
LlZvaWNlUHJvZmlsZS4xLlhfR1JBTkRTVFJFQU1fRE5TU1JWRmFpbG92ZXJNb2RlLCB2YWx1ZTog
IkRlZmF1bHQiCkRldmljZS5TZXJ2aWNlcy5Wb2ljZVNlcnZpY2UuMS5Wb2ljZVByb2ZpbGUuMS5Y
X0dSQU5EU1RSRUFNX0ROU01vZGUsIHZhbHVlOiAiTkFQVFJfU1JWIgpEZXZpY2UuU2VydmljZXMu
Vm9pY2VTZXJ2aWNlLjEuVm9pY2VQcm9maWxlLjEuWF9HUkFORFNUUkVBTV9OQVRUcmF2ZXJzYWws
IHZhbHVlOiAiTm8iCkRldmljZS5TZXJ2aWNlcy5Wb2ljZVNlcnZpY2UuMS5Wb2ljZVByb2ZpbGUu
MS5YX0dSQU5EU1RSRUFNX0FsbG93T3V0Z29pbmdDYWxsV2l0aG91dFJlZ2lzdHJhdGlvbiwgdmFs
dWU6IHRydWUKRGV2aWNlLlNlcnZpY2VzLlZvaWNlU2VydmljZS4xLlZvaWNlUHJvZmlsZS4xLlhf
R1JBTkRTVFJFQU1fRW5hYmxlU0lQS2VlcEFsaXZlLCB2YWx1ZTogIk5PVElGWSIKRGV2aWNlLlNl
cnZpY2VzLlZvaWNlU2VydmljZS4xLlZvaWNlUHJvZmlsZS4xLlhfR1JBTkRTVFJFQU1fU0lQS2Vl
cEFsaXZlSW50ZXJ2YWwsIHZhbHVlOiAzMApEZXZpY2UuU2VydmljZXMuVm9pY2VTZXJ2aWNlLjEu
Vm9pY2VQcm9maWxlLjEuWF9HUkFORFNUUkVBTV9TSVBLZWVwQWxpdmVNYXhMb3N0LCB2YWx1ZTog
MwpEZXZpY2UuU2VydmljZXMuVm9pY2VTZXJ2aWNlLjEuVm9pY2VQcm9maWxlLjEuU0lQLlByb3h5
U2VydmVyLCB2YWx1ZTogImNsaS52b2lwLmV4YW1wbGUuY29tIgpEZXZpY2UuU2VydmljZXMuVm9p
Y2VTZXJ2aWNlLjEuVm9pY2VQcm9maWxlLjEuU0lQLlByb3h5U2VydmVyVHJhbnNwb3J0LCB2YWx1
ZTogIlRMUyIKRGV2aWNlLlNlcnZpY2VzLlZvaWNlU2VydmljZS4xLlZvaWNlUHJvZmlsZS4xLlNJ
UC5SZWdpc3RyYXJTZXJ2ZXIsIHZhbHVlOiAiY2xpLnZvaXAuZXhhbXBsZS5jb20iCkRldmljZS5T
ZXJ2aWNlcy5Wb2ljZVNlcnZpY2UuMS5Wb2ljZVByb2ZpbGUuMS5TSVAuUmVnaXN0cmFyU2VydmVy
VHJhbnNwb3J0LCB2YWx1ZTogIlRMUyIKRGV2aWNlLlNlcnZpY2VzLlZvaWNlU2VydmljZS4xLlZv
aWNlUHJvZmlsZS4xLlNJUC5PdXRib3VuZFByb3h5LCB2YWx1ZTogIiIKRGV2aWNlLlNlcnZpY2Vz
LlZvaWNlU2VydmljZS4xLlZvaWNlUHJvZmlsZS4xLlNJUC5Vc2VyQWdlbnRUcmFuc3BvcnQsIHZh
bHVlOiAiVExTIgpEZXZpY2UuU2VydmljZXMuVm9pY2VTZXJ2aWNlLjEuVm9pY2VQcm9maWxlLjEu
U0lQLlVzZXJBZ2VudERvbWFpbiwgdmFsdWU6ICJjbGkudm9pcC5leGFtcGxlLmNvbSIKRGV2aWNl
LlNlcnZpY2VzLlZvaWNlU2VydmljZS4xLlZvaWNlUHJvZmlsZS4xLlNJUC5YX0dSQU5EU1RSRUFN
X1ByZWZlclByaW1hcnlTSVBTZXJ2ZXIsIHZhbHVlOiB0cnVlCkRldmljZS5TZXJ2aWNlcy5Wb2lj
ZVNlcnZpY2UuMS5Wb2ljZVByb2ZpbGUuMS5TSVAuWF9HUkFORFNUUkVBTV9TaXBSZWdpc3RyYXRp
b24sIHZhbHVlOiB0cnVlCkRldmljZS5TZXJ2aWNlcy5Wb2ljZVNlcnZpY2UuMS5Wb2ljZVByb2Zp
bGUuMS5TSVAuWF9HUkFORFNUUkVBTV9BZGRBdXRoSGVhZGVyT25Jbml0aWFsUkVHSVNURVIsIHZh
bHVlOiBmYWxzZQpEZXZpY2UuU2VydmljZXMuVm9pY2VTZXJ2aWNlLjEuVm9pY2VQcm9maWxlLjEu
U0lQLlhfR1JBTkRTVFJFQU1fU3BlY2lhbEZlYXR1cmUsIHZhbHVlOiAiU3RhbmRhcmQiCg==

DNS Records:

Y2xpLnZvaXAuZXhhbXBsZS5jb20uIDg2NDAwIElOIE5BUFRSIDcgMTAwICJTIiAiU0lQUytEMlQi
ICIiIF9zaXBzLl90Y3AuY2xpLnZvaXAuZXhhbXBsZS5jb20uCgpfc2lwcy5fdGNwLmNsaS52b2lw
LmV4YW1wbGUuY29tLiAzNjAwIElOIFNSViAyMCA1MCA1MDYxIG4wMDAyLnZvaXAuZXhhbXBsZS5j
b20uCl9zaXBzLl90Y3AuY2xpLnZvaXAuZXhhbXBsZS5jb20uIDM2MDAgSU4gU1JWIDI1IDUwIDUw
NjEgbjAwMDEudm9pcC5leGFtcGxlLmNvbS4KCl9zaXAuX3RjcC5jbGkudm9pcC5leGFtcGxlLmNv
bS4gMzYwMCBJTiBTUlYgMTAgNTAgNTA2MCBuMDAwMS52b2lwLmV4YW1wbGUuY29tLgpfc2lwLl90
Y3AuY2xpLnZvaXAuZXhhbXBsZS5jb20uIDM2MDAgSU4gU1JWIDEwIDUwIDUwNjAgbjAwMDIudm9p
cC5leGFtcGxlLmNvbS4K

Odd/interesting:

A SIP NOTIFY message without an Event header?

Tk9USUZZIHNpcHM6Y2xpLnZvaXAuZXhhbXBsZS5jb206NTA2MSBTSVAvMi4wClZpYTogU0lQLzIu
MC9UTFMgMTkyLjE2OC4xLjU1OjU5MjQ2O2JyYW5jaD16OWhHNGJLMjAzNzczNjEzMTtycG9ydDth
bGlhcwpGcm9tOiA8c2lwczp1c2VyQGNsaS52b2lwLmV4YW1wbGUuY29tOjUwNjE+O3RhZz0yMDMx
MzAwOTUyClRvOiA8c2lwczpjbGkudm9pcC5leGFtcGxlLmNvbTo1MDYxPgpDYWxsLUlEOiAxOTcy
NTA0MTUxLTUwNjEtMjI3OEBCSkMuQkdJLkIuRkYKQ1NlcTogMjI3NTAgTk9USUZZCkNvbnRhY3Q6
IDxzaXBzOnVzZXJAMTkyLjE2OC4xLjU1OjU5MjQ2O3RyYW5zcG9ydD10bHM+Ck1heC1Gb3J3YXJk
czogNzAKVXNlci1BZ2VudDogR3JhbmRzdHJlYW0gSFQ4MDEgMS4wLjQ5LjIKU3VwcG9ydGVkOiBy
ZXBsYWNlcywgcGF0aCwgdGltZXIsIDEwMHJlbCwgb3V0Ym91bmQsIGdydXUsIGV2ZW50bGlzdApB
bGxvdzogSU5WSVRFLCBBQ0ssIE9QVElPTlMsIENBTkNFTCwgQllFLCBTVUJTQ1JJQkUsIE5PVElG
WSwgSU5GTywgUkVGRVIsIFVQREFURQpDb250ZW50LUxlbmd0aDogMAo=

Assuming that the authoritative indication of the server selected by the HT801 (ie. where it sends and expects to receive INVITES to/from) is the one where it sends keep alive messages to:

  1. Regardless of the “Register Before DNSSRV Failover” setting when the HT801 changes the server it sends keep alive messages to it does so without first registering to that server.
  2. When the status of the response to a keep-alive NOTIFY message is 403 or 401 (without an Authorization header) the HT801 doesn’t then register to that server. If responses to keep-alive messages are withheld due to being unregistered the HT801 switches back to the other server.

Assuming that the “Register Before DNSSRV Failover” is supposed to do as it suggests:
There are undocumented prerequisite settings for the code path that registers to a newly selected server before sending it keep-alive messages.


#2

What is the DNS failover mode?
Have you checked if the unit is shown as registered (status page)
Have u tried to reduce the register expiration?

Ps: the provided records are not r3l3v4n7