SOLVED SIP-T53 and SIP-T54W loosing registration and reconnecting

Status
Not open for further replies.
F

FunkStar

Member
Jun 16, 2017
33
1
8
Hi

I just installed 15 SIP-T53 and one SIP-T54W. The devices provisioned well and registered but after a few minutes they lost the registration. (Registration failed) after a while they are online again for a bit.
I also noticed double registrations sometimes. Its a complete new building and new devices (we were using a mix of T42G/S T46 before.)

Any idea what could be wrong? Only thing I noticed is that devices in the Registrations are showing as "Registered TCP expsecs XXX" while in other locations its showing as"Registered TCP-NAT expsecs XXX"
Firewall is an USG-Pro4 with SIP-ALG disabled (we have this setting in different locations).

firmware is:

96.84.188.7 (Yealink SIP-T54W)
95.84.188.7 (Yealink SIP-T53)

As you can see the transport is set to TCP and the server expire to 80.
Server Retry Counts are set to 3.

1625216152527.png

I also did an "Export All Diagnostic Files" first set some log lvl's to 6 but I can't seem to find the "register failed error" in te logs...

edit: It must be a device setting I think, I have 2 "commend SIP Series 4.3.1" intercoms connected for a few days without any trouble and using zoiper on this network also works.
 
Connected our reseller and asked for an more up 2 date .rom file. I received T54W(T57W,T53W,T53)-96.85.188.3 but sadly that didn't solve the problem. I also have a W60B and this is the only device that says connected... I tried comparing settings but I can't really find anything.

I'm trying to analyse the diagnostic file further but any help is welcome.
 
Couldn't find anything in the yealink files but sngrep does show this for all devices (T54W & T53 except the W60B)
1625403826703.png
 
Fixed: It seems the SIP ALG module was disabled but the provisioning didn't work. After a reboot, settings took effect and all devices got the "Registered TCP-NAT" status instead of "Registered TCP". No idea why the W60B and Commend devices did work and got the "Registered TCP-NAT" status right away...

1625426453945.png
 
Status
Not open for further replies.
Top Bottom