Solved Old ProTalk SIP client

[ITatWork]

Hi all,

I am in the process of moving a client to 3CX as their old PBX died; got the ancient Snom 870's set up like a charm, but I cannot get the doorbell to register - wonder if anyone has any ideas as I think I've tried everything I can think of today.

3CX is on a VM, connected by a trunk-to-trunk VPN to the customer premesis, this is all working as clearly the phones are working etc.

Doorbell is a ProTalk system, they are now end of life, but this one was very carefully converted to match the exisiting brass faceplate of this particular property to meet herittage requirements, I can't even recall who or how I managed to get it done! I know that the distributor used to claim it was compatible with 3CX but obviously that was before 3CX had their strict list of supported phones.

The device has a registration log, it simply reports No Response ...

 

[Evolute IT]

Remove the proxy and leave the registrar, if it doesn't work, try the other way around.

 

[JohnS_3CX]

Are you seeing the registration attempts on the PBX?

Perhaps during your attempts to register it the IP of the doorbell became blacklisted, so check your management console and perhaps whitelist it for the duration of your tests.

 

[ITatWork]

Thank you all for your reply, JohnS was along the right lines, as we could see no traffic hitting the PBX (analysed the PCAP trace) from the doorbell. After much thought and the input of our distributor we decided it must be a network issue, and the solution oddly was to drop the static IP for a DHCP lease ... and lo and behold the damn thing registered!

Hopefully no one else is dealing with ancient hardware, but if you are, I hope this helps!

Edit to add ... it wasn't blacklisted, because we bound the MAC address to the IP it had already been on in our router tables.