Installation on Fedora

Asterisk Asterisk Support
1

I’ve installed Asterisk 1.8.3 on Fedora 14, at the prompt I type asterisk -vvvvgc and asterisk starts. My SIP phones are not connecting. I get the following errors:

== Parsing ‘/etc/asterisk/cli.conf’: == Found
*CLI> [Mar 24 09:27:48] ERROR[2838]: netsock2.c:245 ast_sockaddr_resolve: getaddrinfo(“dynamic”, “(null)”, …): Name or service not known
[Mar 24 09:27:48] WARNING[2838]: acl.c:569 resolve_first: Unable to lookup 'dynamic’
Really destroying SIP dialog ‘0398ea372ea2879c7d03b36b1cadbccf@[::1]’ Method: REGISTER
[Mar 24 09:27:48] WARNING[2838]: chan_sip.c:12317 transmit_register: Probably a DNS error for registration to 7336@dynamic, trying REGISTER again (after 20 seconds)
[Mar 24 09:27:48] NOTICE[2838]: chan_sip.c:12155 sip_reregister: – Re-registration for 6336@dynamic
> doing dnsmgr_lookup for ‘dynamic’
[Mar 24 09:28:08] ERROR[2838]: netsock2.c:245 ast_sockaddr_resolve: getaddrinfo(“dynamic”, “(null)”, …): Name or service not known
[Mar 24 09:28:08] WARNING[2838]: acl.c:569 resolve_first: Unable to lookup 'dynamic’
Really destroying SIP dialog ‘4f60a32e7445697d121949001d0dfbf4@[::1]’ Method: REGISTER
[Mar 24 09:28:08] WARNING[2838]: chan_sip.c:12317 transmit_register: Probably a DNS error for registration to 6336@dynamic, trying REGISTER again (after 20 seconds)
Really destroying SIP dialog ‘489836159@10.1.4.21’ Method: REGISTER
> doing dnsmgr_lookup for ‘dynamic’
[Mar 24 09:28:28] ERROR[2838]: netsock2.c:245 ast_sockaddr_resolve: getaddrinfo(“dynamic”, “(null)”, …): Name or service not known
[Mar 24 09:28:28] WARNING[2838]: acl.c:569 resolve_first: Unable to lookup 'dynamic’
Really destroying SIP dialog ‘0398ea372ea2879c7d03b36b1cadbccf@[::1]’ Method: REGISTER
[Mar 24 09:28:28] WARNING[2838]: chan_sip.c:12317 transmit_register: Probably a DNS error for registration to 7336@dynamic, trying REGISTER again (after 20 seconds)
[Mar 24 09:28:28] NOTICE[2838]: chan_sip.c:12232 sip_reg_timeout: – Registration for ‘7336@dynamic’ timed out, trying again (Attempt #2)

<— SIP read from UDP:10.1.4.21:5060 —>
REGISTER sip:172.31.5.5 SIP/2.0
Via: SIP/2.0/UDP 10.1.4.21:5060;branch=z9hG4bK2361652467
From: 7336sip:7336@172.31.5.5;tag=2424547436
To: 7336sip:7336@172.31.5.5
Call-ID: 489836159@10.1.4.21
CSeq: 1156 REGISTER
Contact: sip:7336@10.1.4.21
Max-Forwards: 70
Expires: 3600
User-Agent: Clipcomm CP-100D v1.2.20 (051215)
Content-Length: 0
<------------->
— (11 headers 0 lines) —
Sending to 10.1.4.21:5060 (no NAT)
<— Transmitting (no NAT) to 10.1.4.21:5060 —>
SIP/2.0 404 Not found (unknown domain)
Via: SIP/2.0/UDP 10.1.4.21:5060;branch=z9hG4bK2361652467;received=10.1.4.21
From: 7336sip:7336@172.31.5.5;tag=2424547436
To: 7336sip:7336@172.31.5.5;tag=as2f2b1f4e
Call-ID: 489836159@10.1.4.21
CSeq: 1156 REGISTER
Server: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
Content-Length: 0
<------------>
[Mar 24 09:28:28] NOTICE[2838]: chan_sip.c:23511 handle_request_register: Registration from ‘7336sip:7336@172.31.5.5’ failed for ‘10.1.4.21:5060’ - Not a local domain
Scheduling destruction of SIP dialog ‘489836159@10.1.4.21’ in 32000 ms (Method: REGISTER)
> doing dnsmgr_lookup for ‘dynamic’

2

I’m running Fedora 14 with Asterisk 1.8.4 and have the exact same problem.

No @dynamic can register.

3

Howdy,

Does the same configuration work with a previous 1.8 release or a 1.6.2 release?

4

In my case is a fesh install so I cannot tell to be honest.

5

If an earlier version works, that’d let us know if there’s some problem that’s been introduced.

6

Hello,
I’m wondering little bit with the title, there’s no relation between this issue and Fedora itself as OS.

I had this issue in v. 1.8.4, but it despaired in v. 1.8.5 as it was reported as issue 18183 here: issues.asterisk.org/view.php?id=18183 even, no solution was given.

But now, we’re just making a new installation with 1.8.7, and the issue is there again.

I think it’s coming from the NULL behavior of the mysql which was treated with the new directives autoclear, and nullvalue in app_mysql.conf file implemented with the earlier versions.

The published documentation are “for me” unclear, and I may need heelp to understand what’s the correct configuration should be, considering that we have NULL entries in the DB… in app_mysql.conf file the explication is below:

Thanks for help and advice…

Regards,

7

Hello,
This error it’s coming from a2billing DB, in our specific case. We just solve it, we post the solution in a2billing forum, as it’s related to a2billing DB to get upgrade for asterisk 1.8. The post it’s here: forum.asterisk2billing.org/viewt … 521#p35521

In other cases, check the DB, in regard of our giving solution, it may be similar.

Regards,