Chan_sip.c: Purely numeric hostname (xxxx), and not a peer--rejecting!

General Help
1

Getting these errors constantly in the full logs… seems to only be with our Aastra phones. Thought I saw a line that I know was one of our Sangoma phones, but haven’t seen it again.

In searching I only see a few threads out there mentioning this but it’s always a chan_sip.c: create_addr and is followed by someone having a problem with the phone. I mean the log is bombarded with these entries, and we’re not using chan_sip at all. These are all totally working extensions and phones with no issues other than the garbage in the log file.

If these aren’t a problem, is there a way to silence these errors?

2018-02-26 13:37:43] WARNING[13238] chan_sip.c: Purely numeric hostname (2012), and not a peer–rejecting!
[2018-02-26 13:37:43] WARNING[13238] chan_sip.c: Purely numeric hostname (2005), and not a peer–rejecting!
[2018-02-26 13:37:43] WARNING[13238] chan_sip.c: Purely numeric hostname (2005), and not a peer–rejecting!
[2018-02-26 13:37:44] WARNING[13238] chan_sip.c: Purely numeric hostname (9010), and not a peer–rejecting!
[2018-02-26 13:37:44] WARNING[13238] chan_sip.c: Purely numeric hostname (9010), and not a peer–rejecting!
[2018-02-26 13:37:56] WARNING[13238] chan_sip.c: Purely numeric hostname (2008), and not a peer–rejecting!
[2018-02-26 13:37:56] WARNING[13238] chan_sip.c: Purely numeric hostname (2008), and not a peer–rejecting!
[2018-02-26 13:37:58] WARNING[13238] chan_sip.c: Purely numeric hostname (8012), and not a peer–rejecting!
[2018-02-26 13:37:58] WARNING[13238] chan_sip.c: Purely numeric hostname (8012), and not a peer–rejecting!
[2018-02-26 13:38:00] WARNING[13238] chan_sip.c: Purely numeric hostname (2003), and not a peer–rejecting!
[2018-02-26 13:38:00] WARNING[13238] chan_sip.c: Purely numeric hostname (2003), and not a peer–rejecting!
[2018-02-26 13:38:02] WARNING[13238] chan_sip.c: Purely numeric hostname (9009), and not a peer–rejecting!
[2018-02-26 13:38:02] WARNING[13238] chan_sip.c: Purely numeric hostname (9009), and not a peer–rejecting!
[2018-02-26 13:38:02] WARNING[13238] chan_sip.c: Purely numeric hostname (2021), and not a peer–rejecting!
[2018-02-26 13:38:02] WARNING[13238] chan_sip.c: Purely numeric hostname (2021), and not a peer–rejecting!
[2018-02-26 13:38:04] WARNING[13238] chan_sip.c: Purely numeric hostname (2013), and not a peer–rejecting!
[2018-02-26 13:38:04] WARNING[13238] chan_sip.c: Purely numeric hostname (2013), and not a peer–rejecting!

edit: Also, the hostnames are not purely numeric - they have the model number followed by the MAC addresses, so they always have 57ixxxxx 6739ixxxxx, etc in their hostnames.

2

I normally get that when I try to do a “sip notify reboot-yealink” and the extension doesn’t exist in extensions.

3

Don’t think that’s our case, all those extensions definitely exist, and this is just continuous on the log. It’s multiple extensions per second, nearly every second.

4

It’s from sip notify. It’s because it’s sending to both chansip and pjsip without looking up the technology first.

5

Ok, only thing I can find in Asterisk Settings is the notifcation and MWI settings under chan_sip for the polling frequency and the ringing/hold notify.

If I set the freq to 0 and turn off ringing and hold will that make any difference? sipstation uses chan_sip though doesn’t it, and will that cause problems with the trunks?

6

You’re looking in the wrong place. This is not a setting you can control or define. There’s a bug on it in the issue tracker.

1 Like
7

Posted there. Marked as closed. No link to other mentioned bug report.

https://issues.freepbx.org/browse/FREEPBX-16211

8

It’s closed as a duplicate of the linked issue. There is no fix.

9

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.