Grandstream FXO must be rebooted every morning

[Zachary Peebels]

I'm pretty inexperienced with this stuff and have been searching for a fix for a very long time.
Calls will show on the activity log but do not ring through until I reboot the FXO.

07/20/2020 1:50:08 PM - [CM102001]: Authentication failed for AuthFail Recv Req INVITE from IPADDRESS tid=blahblah Call-ID=blahblah@yoyo: INVITE sip:000000@dingdong:5060 SIP/2.0 Via: SIP/2.0/UDP flipflop:5060;branch=chingaling Max-Forwards: 70 Contact: <sip:tingtang:5060> To: <sip:000000@bingbang:5060> From: "WIRELESS CALLER"<sip:dingdang@dong:5060>;tag=ting Call-ID:tang@tong CSeq: 11778 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE, PRACK Content-Type: application/sdp Proxy-Authorization: Digest username="something",realm="3CXPhoneSystem",algorithm=MD5,uri="sip:000000@tong:5060",nonce="chong",response="bong" Supported: replaces, timer, path User-Agent: Grandstream GXW4108 (HW 2.3, Ch:7) 1.4.1.5 Content-Length: 344 v=0 o=system 8007 8001 IN IP4 thong s=SIP Call c=IN IP4 kong t=0 0 m=audio 5032 RTP/AVP 0 8 18 4 2 103 101 a=sendrecv a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=rtpmap:4 G723/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:103 PCMU/8000 a=ptime:20 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-11 ; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings

I'm sure it's probably something ridiculously simple...
Any ideas?

 

[leejor]

And how is your network configured?

https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

 

[Zachary Peebels]

phones are Grandstream GXP2160s.
3cx on local server
GXP4108 FXO (aware it is unsupported but it works other than the required reboot)
firewall tests pass with flying colors.

 

[leejor]

The log seem to indicate an incoming call, which would mean that the gateway is sending the call to 3CX, or it would not appear in the log. Is it just incoming calls that fail, until a reboot, or outgoing as well? Does the gateway actually show as registered before the reboot?

Are you using local IP's , or FQDN. You have blanked out a lot of information, if those are local IPs, that can help in trouble shooting. Posting your public IP, or FQDN can be a security risk, not local IPs.

Credentials don't match, check that authorization-ID and password match the ones in extension settings

If this is the error you are seeing each time, before you re-boot, you may want to consider, re-setting and re-configuring the gateway.