I could be missing something really obvious here so accept my apologies if I am but…
I’m trying to connect a brand new Snom D140 to a FreePBX 16.0.40.10 server. Went through the inital setup on device (language, admin username, admin password, timezone, etc) then logged on to the web interface to configure the extension / line.
On the identity 1 page I added Displaybame, Account (extension number), Password, Registrar (server fqdn) but it didn’t register.
Found a few things online suggesting Identity 1 > RTP > removing all codecs except pcmu, gsm and telephone-event and disabling RTP Encryption. Did that, saved, restarted, still not registering.
Going to status > system information gives me “[email protected]: Not Found”
settings > log gives me “SIP: Registrar [email protected] refused with code 404” but there is also a log entry before that to say “SIP: transport error 1000001: generating fake 404”
So that looks like maybe a network issue but a configured Yealink phone on the same cable/switch/internet is connecting to the server no problem.
I’m not familiar with Snom, but here are a few things to try:
I assume that the server is expecting UDP transport; if not, provide details. Is it listening on port 5060? If not, you need to configure the port number in Snom, e.g., for port 5678 you probably need to specify pbx.domain.co.uk:5678 or (if a separate field is provided for the port) putting 5678 in that field.
Possibly, a DNS issue; test by using the numeric IPv4 address instead of pbx.domain.co.uk.
Possibly, another network issue; does the phone show the correct date/time?
Though unlikely, there may be a malfunctioning SIP ALG in the path. Log into the local router and disable it if possible. Also, test by shutting down both Snom and Yealink, wait at least 10 minutes for any NAT associations to expire, then power on the Snom (leaving the Yealink off) and see whether it will register.
I have just had something along these lines. I had an extension previously set up with a static ip address (192.168.0.208 using its extension number-easy) disconnected from network for a day. (Its a Snom, but I don’t think that’s relevant-I swapped in a Yealink with same result). It would not re-register to the FreePBX set up. I deleted the extension from FreePBX, and re-added it. Changed the password. Did apply config each and every time. Factory reset the phone. on and on. The phone was pingable on the network, but would not register. I don’t think the PBX was even looking for it. The extension was listed in pjsip show endpoints, but unavailable.
Eventually I changed the ip address of the phone (left it as DHCP) and it registered like it always used to.
But… in the pjsip show endpoints now, it seems to show the wrong port: 44610 instead of 5060.
But the extension is working on early testing.
Endpoint: 208/208 Not in use 0 of inf
InAuth: 208-auth/208
Aor: 208 1
Contact: 208/sip:[email protected]:44610;line=dxby2f
So, problem solved, but what the?? Is it a FreePBX thing? And will I be able to change it back to its familiar static ip address so I’ll remember where it is next time this happens in 5 more years. And does that 44610 matter?
@petecat1 sounds firewall related. Is the pbx local? Something like this might help. Are you getting any packets in from the phone?
tcpdump -nn src 192.168.0.208
or check iptables (looking for a REJECT line)
iptables -L -n | grep 192.168.0.208
The port showing as something other than 5060 is normal. I’m sure someone will correct me ever so slightly here but 5060 is the “hey I’m a phone and I want to talk to you” port, the pbx responds with “cool, head over to port xxxx and we can chat there”.