Changed dhcp server, 110 sangoma handsets no longer login?


(Jon Kelly) #1

Old dhcp server died, but we had config file, it was on a linux box, probably for 15 years, we had replacement configured and waiting to cut over. Handsets picking up ip’s, no problems.

Now all handsets fail to register with Freepbx 13.0.197.28 pbx, pbx distro 10.13.66-11, asterisk ver 13.7.1 also see a strange new error from our vega200a, which handles our trunks, digital to sip.

[2020-10-15 22:29:05] WARNING[20160] chan_sip.c: Autodestruct on dialog ‘2a21e81042c1b6f40be7d8b808ba58aa@192.168.212.230:5061’ with owner SIP/vega200a-out-000029a2 in place (Method: BYE). Rescheduling destruction for 10000 ms
[2020-10-15 22:29:06] WARNING[20160] chan_sip.c: Autodestruct on dialog ‘00F3-03AA-D5C755C7-00000063@5C1903681EC0533B8’ with owner SIP/vega200a-in-000029b1 in place (Method: BYE). Rescheduling destruction for 10000 ms
[2020-10-15 22:29:08] WARNING[20160] chan_sip.c: Autodestruct on dialog ‘00F1-138C-FADA1727-00000063@5C1903681EC0533B8’ with owner SIP/vega200a-in-000029ad in place (Method: BYE). Rescheduling destruction for 10000 ms
[2020-10-15 22:29:08] WARNING[20160] chan_sip.c: Autodestruct on dialog ‘00F0-209B-72F34E16-00000063@5C1903681EC0533B8’ with owner SIP/vega200a-in-000029ac in place (Method: BYE). Rescheduling destruction for 10000 ms
[2020-10-15 22:29:10] WARNING[20160] chan_sip.c: Autodestruct on dialog ‘00F0-2098-1157DC49-00000063@5C1903681EC0533B8’ with owner SIP/vega200a-in-000029a9 in place (Method: BYE). Rescheduling destruction for 10000 ms

We can call in, and hear the IVR menus. We can press selections, but you then get voicemail message user’s not available, since the hand sets are not registered.

Nothing changed, system has worked for 3 years, it resides on the vm, we changed our dhcp server, but still use same dhcp config, since we’re running same dhcp server software, again on linux box.

I understand, we could run dhcp on the Freepbx box, but we have 4 different segments, and currently the phones are getting their ip’s, and the error if “fail to register”.

Would appreciate a direction. And yes, I did attempt to setup a new phone, which is usually a fairly fast process, create user, create extension, select mac in endpoint manager, usually, on reboot, done. But the new handset does not login, just like the other 110 phones we have.

Thank you again,


(Jon Kelly) #2

I found this in the log, which I believe is directly related to my issues of end points, or handsets not registering.

[2020-10-16 07:37:07] WARNING[12037]: chan_sip.c:6064 create_addr: Purely numeric hostname (122), and not a peer–rejecting!

I turned off the firewall, it’s safe with this unit not directly connected to Internet, but still not able to register handsets.


#3

Is that one of the extensions using port 5061 for chan_sip rather than PJSIP?

May want to look at the sip debug, and look at what the telephone is doing also.

I got an S500 here, and notice it does not have a log,but I do see a pcap which you can export to look at what the telephone is doing.


#4

Is it possible the saved dhcp config was out of date and the dhcp options to specify the provisioning location are not current? That would explain why phones are getting IPs but not the provisioning.


(Dave Burgess) #5

Just throwing this out there, but it comes up on SCCP phones from time to time:

When you move the DHCP server from the phone server to another, external server, you may need to add the ‘next-server’ option to the DHCP stanza for your phones so that it knows where to connect to for it’s TFTP/Configuration settings.