Guten Tag!

I need to use AM for SIP.
After your advice about your programs I added string and modified Phoner's file for SIP re-registration period.
But my SIP operator is non-stable so about every 3rd day it's answering error 503 Server Too Busy.
After that the Phoner doesn't retrying to register.
Now I don't know what time length that my operator can answering error 503.
I use and test your programs and my SIP operator not so long.
Now I am not sure that PhonerLite has not this bug because I didn't found string like Reg Retry Intvl for PhonerLite too.
Also I am not sure will your programs re-register after another 5xx server error?
Excuse me for these hypotheses.
Now I changed TCP to UDP and risked to change RegisterRequestRecipient to 0.
So I am testing again but I am not sure that this is the solution.
Excuse me for these hypotheses.
Please help, comment what to do for the solution?
Thanks!

I added string and set RegisterPeriod=60 as my SIP operator said.
Is it for reTry re-Registration too for any events?
But the Phoner program listen to my provider's server's answers about Expires: 60-180 range of changing.
So it's working several days for incoming (for out too) calls without problems.
But some programs and devices also have parameter like Reg Retry Intvl and some of them have also Reg Retry Long Intvl and also Reg Retry Random Delay, Reg Retry Long Random Delay, etc.
My 5060 and 5061 ports are busy by another device so here 5063 port is using for non-conflictness.
After the SIP operator answered 503 Server Too Busy there are no re-Reg for several hours.
Then I did manual restarts.
It was twice one after another with several days interval with SIP RTP over TCP and RegisterRequestRecipient=1 settings.
Final log with these settings: 

18:26:05,953: T: ProxyGateway:5060 (TCP)
REGISTER sip:Realm SIP/2.0
Via: SIP/2.0/TCP MyLocalIP:4717;branch=BRANCH1;rport
From: <sip:UserName@Realm>;tag=FromTAG
To: <sip:UserName@Realm>
Call-ID: CID@MyLocalIP
CSeq: 2334 REGISTER
Contact: <sip:UserName@MyIP:4717;transport=tcp>;+sip.instance="<urn:uuid:UrnUuid>"
Proxy-Authorization: Digest username="UserName", realm="BAND", nonce="NONCE", uri="sip:Realm", response="RESPONSE1", algorithm=md5, cnonce="Cnonse1", opaque="NONCE", qop=auth, nc=00000003
Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE, UPDATE
Max-Forwards: 70
User-Agent: SIPPER for phoner
Expires: 90
Content-Length: 0


-------------------------------------------
18:26:06,203: R: ProxyGateway:5060 (TCP)
SIP/2.0 200 OK
Via: SIP/2.0/TCP MyLocalIP:4717;received=MyIP;branch=BRANCH1;rport=4717
From: <sip:UserName@Realm>;tag=FromTAG
To: <sip:UserName@Realm>;tag=ToTAG1
Call-ID: CID@MyLocalIP
CSeq: 2334 REGISTER
Contact: <sip:UserName@MyIP:4717;transport=tcp>;expires=90;transport=udp
Allow: INVITE,OPTIONS,ACK,BYE,CANCEL,INFO,NOTIFY,MESSAGE,UPDATE
Supported: path
User-Agent: Realm
Expires: 90
Content-Length: 0
Service-Route: <sip:UserName@ProxyGateway:5060;transport=tcp;lr>


-------------------------------------------
18:27:17,953: T: ProxyGateway:5060 (TCP)
REGISTER sip:Realm SIP/2.0
Via: SIP/2.0/TCP MyLocalIP:4717;branch=BRANCH2;rport
From: <sip:UserName@Realm>;tag=FromTAG
To: <sip:UserName@Realm>
Call-ID: CID@MyLocalIP
CSeq: 2335 REGISTER
Contact: <sip:UserName@MyIP:4717;transport=tcp>;+sip.instance="<urn:uuid:UrnUuid>"
Proxy-Authorization: Digest username="UserName", realm="BAND", nonce="NONCE", uri="sip:Realm", response="RESPONSE2", algorithm=md5, cnonce="Cnonse2", opaque="NONCE", qop=auth, nc=00000004
Allow: INVITE, OPTIONS, ACK, BYE, CANCEL, INFO, NOTIFY, MESSAGE, UPDATE
Max-Forwards: 70
User-Agent: SIPPER for phoner
Expires: 90
Content-Length: 0


-------------------------------------------
18:27:18,296: R: ProxyGateway:5060 (TCP)
SIP/2.0 503 Server Too Busy
Via: SIP/2.0/TCP MyLocalIP:4717;received=MyIP;branch=BRANCH2;rport=4717
From: <sip:UserName@Realm>;tag=FromTAG
To: <sip:UserName@Realm>;tag=ToTAG2
Call-ID: CID@MyLocalIP
CSeq: 2335 REGISTER
Reason: Q.850;cause=47;text="Call Terminated"
Retry-After: 1
Content-Length: 0


-------------------------------------------
18:27:18,296: T: ProxyGateway:5060 (1276)
TCP connection closing to peer (Registration failed)
-------------------------------------------
18:27:18,296: T: ProxyGateway:5060 (640)
TCP connect to peer
-------------------------------------------
18:27:18,296: R: open TCP port (TCP connect): 4916

-------------------------------------------
18:27:18,562: R: close TCP port (TCP/TLS connection): 4717

-------------------------------------------
18:27:21,296: R: close TCP port (TCP/TLS connection): 4916

-------------------------------------------
18:27:21,296: R: close TCP port (TCP/TLS connection): 4717

I tried to imitate the registration failure by taking off the internet jack from my router.
After that when I returned the internet jack then the registration returned for all variants TCP or UDP or RegisterRequestRecipient=1 or 0.
Last days my SIP operator didn't answered error 503 Server Too Busy.
I don't have my own SIP server to imitate it.
When the bug will again Do You want txt report file or screenshot?
As You understand, It's not problem to make trust but fake results but I don't want to tangle You.
Please answer:
What does RegisterRequestRecipient mean in your programs?
What's better there are 1 or 0 and why?
Does RegisterRequestRecipient may impact for non-renewal of re-registration after the finishing of situation like error 503 Server Too Busy?

RegisterRequestRecipient in Phoner.ini file.
Also please answer the question like this topic http://www.forum.phoner.de/YaBB.pl?num=1384438875 but for Phoner.
I have DebugSIP.txt (without bug situation now) but the size of this file don't want to grow more than 100 kb and the file fix only last 2 hours.