Can dial only after 'SIP reload'

I faced strange problem. Using Asterisk 1.8, incoming calls from voip provider are possible only in few seconds after SIP reload. Outgoing calls are fine. After that period nothing gets to Asterisk, I don’t see even any SIP INVITE packets. I can see provider registered by sip show registry. I present some logs I can notice after not succesfull calls. Please help.

users.conf
[provider]
host=sip.provider.pl
port=5060
hostport=5060
username=61XXXXXXX
secret=*********
contact=61XXXXXXX
insecure=port,invite
trunkname=provider
context=from-internal
hasexten=no
hasiax=no
hassip=yes
registeriax=no
registersip=yes
trunkstyle=voip
outboundproxy=sip.provider.pl
fromdomain=sip.provider.pl
fromuser=61XXXXXXX
authuser=61XXXXXXX
disallow=all
allow=ulaw,alaw

asterisk*CLI> sip set debug on
SIP Debugging enabled
[Dec 10 13:15:34] NOTICE[17291]: chan_sip.c:12578 sip_reregister: – Re-registration for 61XXXXXXXXX@sip.provider.pl
> doing dnsmgr_lookup for 'provider.pl
REGISTER 11 headers, 0 lines
Reliably Transmitting (no NAT) to provider.IP:5060:
REGISTER sip:sip.provider.pl SIP/2.0
Via: SIP/2.0/UDP 192.168.7.100:5060;branch=z9hG4bK63024d76
Max-Forwards: 70
From: sip:61XXXXXXX@sip.provider.pl;tag=as649fd2f7
To: sip:61XXXXXXX@sip.provider.pl
Call-ID: 4cf6092116b9822e26fc24520d34af37@sip.provider.pl
CSeq: 107 REGISTER
User-Agent: Asterisk PBX 1.8.5.0
Authorization: Digest username=“61XXXXXXXX”, realm=“sip.provider.pl”, algorithm=MD5, uri=“sip:sip.provider.pl”, nonce=“50c5d28b66cfb9b5d8b684d0b2a765df74f7a280”, response="b01041f29684a4b90748bcea4c93e145"
Expires: 120
Contact: sip:61XXXXXX@192.168.my.local:5060
Content-Length: 0


<— SIP read from UDP:provider.IP:5060 —>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.my.local:5060;branch=z9hG4bK63024d76;received=46.238.XXX.XXX
From: sip:61XXXXXX@sip.provider.pl;tag=as649fd2f7
To: sip:616690236@sip.cdpnetia.pl
Call-ID: 4cf6092116b9822e26fc24520d34af37@sip.provider.pl
CSeq: 107 REGISTER
Content-Length: 0
Warning: 392 provider.IP:5060 “Noisy feedback tells: pid=17520 req_src_ip=46.238.XXX.XXX req_src_port=5060 in_uri=sip:sip.provider.pl out_uri=sip:sip.provider.pl via_cnt==1”

<------------->
— (8 headers 0 lines) —

<— SIP read from UDP:85.128.53.1:5060 —>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.my.local:5060;branch=z9hG4bK63024d76;rport=5060;received=46.238.XXX.XXX
From: sip:61XXXXXX@sip.provider.pl;tag=as649fd2f7
To: sip:61XXXXXX@sip.provider.pl;tag=2bec0592c7802f49af658696eaf61319.f79e
Call-ID: 4cf6092116b9822e26fc24520d34af37@sip.provider.pl
CSeq: 107 REGISTER
WWW-Authenticate: Digest realm=“sip.provider.pl”, nonce=“50c5d3ca3bcf05059d725d62707e5a8345d7dbfe”, stale=true
Content-Length: 0
Warning: 392 provider.IP:5060 “Noisy feedback tells: pid=17520 req_src_ip=46.238.XXX.XXX req_src_port=5060 in_uri=sip:sip.provider.pl out_uri=sip:sip.provider.pl via_cnt==1”

<------------->
— (9 headers 0 lines) —
Responding to challenge, registration to domain/host name sip.provider.pl
> doing dnsmgr_lookup for 'sip.provider.pl
REGISTER 11 headers, 0 lines
Reliably Transmitting (no NAT) to provider.IP:5060:
REGISTER sip:sip.provider.pl SIP/2.0
Via: SIP/2.0/UDP 192.168.my.local:5060;branch=z9hG4bK5c519348
Max-Forwards: 70
From: sip:61XXXXXX@sip.provider.pl;tag=as15eb438a
To: sip:61XXXXXX@sip.provider.pl
Call-ID: 4cf6092116b9822e26fc24520d34af37@sip.provider.pl
CSeq: 108 REGISTER
User-Agent: Asterisk PBX 1.8.5.0
Authorization: Digest username=“61XXXXXX”, realm=“sip.provider.pl”, algorithm=MD5, uri=“sip:sip.provider.pl”, nonce=“50c5d3ca3bcf05059d725d62707e5a8345d7dbfe”, response="63068043c0b6f54644ee2e3418148bbd"
Expires: 120
Contact: sip:61XXXXXX@192.168.my.local:5060
Content-Length: 0


<— SIP read from UDP:provider.IP.5060 —>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.my.local:5060;branch=z9hG4bK5c519348;received=46.238.XXX.XXX
From: sip:61XXXXXX@sip.provider.pl;tag=as15eb438a
To: sip:61XXXXXX@sip.provider.pl
Call-ID: 4cf6092116b9822e26fc24520d34af37@sip.provider.pl
CSeq: 108 REGISTER
Content-Length: 0
Warning: 392 provider.IP:5060 “Noisy feedback tells: pid=17518 req_src_ip=46.238.XXX.XXX
req_src_port=5060 in_uri=sip:sip.provider.pl out_uri=sip:sip.provider.pl via_cnt==1”

<------------->
— (8 headers 0 lines) —

<— SIP read from UDP:provider.IP:5060 —>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.my.local:5060;branch=z9hG4bK5c519348;rport=5060;received=46.238.XXX.XXX
From: sip:61XXXXXX@sip.provider.pl;tag=as15eb438a
To: sip:61XXXXXX@sip.provider.pl;tag=2bec0592c7802f49af658696eaf61319.45f5
Call-ID: 4cf6092116b9822e26fc24520d34af37@sip.provider.pl
CSeq: 108 REGISTER
Contact: sip:61XXXXXX@192.168.my.local:5060;expires=120;received="sip:46.238.XXX.XXX:5060"
Content-Length: 0
Warning: 392 provider.IP:5060 “Noisy feedback tells: pid=17518 req_src_ip=46.238.XXX.XXX req_src_port=5060 in_uri=sip:sip.provider.pl out_uri=sip:sip.provider.pl via_cnt==1”

<------------->
— (9 headers 0 lines) —
Scheduling destruction of SIP dialog '4cf6092116b9822e26fc24520d34af37@sip.provider.pl’ in 32000 ms (Method: REGISTER)
[Dec 10 13:15:34] NOTICE[17291]: chan_sip.c:20043 handle_response_register: Outbound Registration: Expiry for sip.provider.pl is 120 sec (Scheduling reregistration in 105 s)

<— SIP read from UDP:provider.IP:5060 —>

You are showing a successfull registration.

When incoming calls don’t work, what is the output of “sip show peers” command?

Did you check this issue with your VoIP provider?