SIP Register failed

[ElementalWindX]

What could cause a phone to say SIP register failed, but all other phones are connecting just fine from the same office?

I'm sure a faulty cat5 cable can cause this but anything else?

 

[Evolute IT]

What could cause a phone to say SIP register failed, but all other phones are connecting just fine from the same office?

I'm sure a faulty cat5 cable can cause this but anything else?

Bad cable, blocked IP if LAN, wrong credentials, wrong server config... Many things can cause this.

 

[ElementalWindX]

I guess I should have clarified. What if it was working just fine prior to and the system is new? Only thing I can tell is bad cable.

 

[Evolute IT]

I guess I should have clarified. What if it was working just fine prior to and the system is new? Only thing I can tell is bad cable.

Then, it might be that. Could be the switch port. The cable in the wall. The phone itself could also have issues, have you tried a factory reset and reprovision?

 

[leejor]

Is this a local setup, STUN, SBC? If it is local, then the IP may be in the 3CX P Blacklist. Check the 3CX Activity Log to see if there is a log, of a registration attempt, for that set. Move the set only to a different location, as it could also be a bad port on a switch, bad set power supply (if used), or simply a bad/corrupted set.

 

[ElementalWindX]

Bringing this back up. It's still happening to this particular client. They are utilizing ATT DSL so I'm thinking it's just their internet connection somehow.

This PBX is hosted in our data center off site from this client. Over the past few days, phones have randomly shown "SIP Register Failed" and after several reboots, it'll work. There is no SBC involved.

Any idea how to troubleshoot or fix this issue? We are utilizing a Sophos XG firewall and Unifi switch. The same combo we use at every site that otherwise works fine.

 

[AWS2P]

Already got defective cable with just some inside wires cut and phone was with power but never get registred, a cable change fixed the problem.
another time it was final RJ45 not fully locked in phone side port, so sometimes it was working and a while after no more.

 

[ElementalWindX]

In this situation, it's been different phones each day. It's always just one phone that gives the error. There are a total of 6 physical phones on this site.

 

[AWS2P]

Are they POE ?

 

[ElementalWindX]

Yes. I've been power cycling the bad phone repetitively this morning just to see if it magically comes up. They're all the same model Fanvil x6u with the same firmware loaded too. v1.0.5

 

[ElementalWindX]

After 3 power cycles, the phone is up and working now -_- My moneys on it being ATT and their bs. We have a fiber provider installing fiber "soon" at this client.

 

[JohnS_3CX]

Hi @ElementalWindX

What phone provisioning method are you currently using?

 

[ElementalWindX]

Hi @ElementalWindX

What phone provisioning method are you currently using?

STUN

 

[JohnS_3CX]

It may be the provider, but you can try doing the following (if its just a few phones at the site) and this might help reduce the issues at that specific site.

For each phone extension, make sure the phone has a unique SIP port and unique RTP port range (non overlapping with the other phones)


In the firewall/modem at the site, you must also forward those ports externally (should not be a problem since they are unique). Be careful in case the router has SIP ALG / or SIP Helper as this should be disabled (it might mess with the SIP and NAT)

Since the ports will are now set statically, they should always stay alive and you should have the best possible chance to avoid losing SIP registration.

If there is no improvement, I can suggest further actions. Let us know how it goes!

 

[Alphabetic]

I had an issue with a Fanvil X5 doing this. Always the same phone. Think I changed the patch cable on the POE switch.

 

[AWS2P]

is your POE Budget enough comfortable to power all the phones and perhaps other POE devices connected on same switch?

 

[leejor]

Did you ever swap the phone with another location, to see if the problem moved with the set?