Can't register Trunk 408 Request Timeout/REGISTER from local

[andy-vdg]

Hi,

I've re-created our hosted instance and restored from a backup. Since then no registration attempts are making it to Peoplefone.
In the logs I get a new line every two minutes:

22/01/2024 12:03:49 - [CM504005]: Registration failed for: Lc:10000(@Peoplefone[<sip:[email protected]:0/UDP>]); Cause: Cause: 408 Request Timeout/REGISTER from local
22/01/2024 12:01:17 - [CM504005]: Registration failed for: Lc:10000(@Peoplefone[<sip:[email protected]:0/UDP>]); Cause: Cause: 408 Request Timeout/REGISTER from local
22/01/2024 11:58:45 - [CM504005]: Registration failed for: Lc:10000(@Peoplefone[<sip:[email protected]:0/UDP>]); Cause: Cause: 408 Request Timeout/REGISTER from local

Things I've already checked:

• I've got the Peoplefone IPs whitelisted
• the Trunk credentials work fine as I can use them without problems on another 3CX instance
• Checked with Peoplefone and they are getting no requests from the hosted instance at all
• Removed the trunk completely and re-set it up with the same result
• Ran wireshark but can't find much that is of help

Anything else I can check or is the connection possibly blocked by something on the hosting side?

Thanks in advance.

 

[Alejandro_3CX]

Hi @andy-vdg since you reinstalled the system please note that the public IP changed, could you please check in your provider account if by chance you are allowing the traffic from a specific IP, if so please modify it with the the new public IP.

The message shared in the log means that the system doesn't have any response back from the provider since the messages are being timed out.

 

[andy-vdg]

Hi @Alejandro_3CX
I did check with them and they said nothing is blocked from their end and they have not received any traffic from the new public IP in the last two weeks.

Andy

 

[Alejandro_3CX]

Hi Andy, you can start a packet capture in the pbx and open another window ---- go to sip trunk ---- click on refresh registration, wait around 2 minutes and stop the capture.

Then you can filter the capture by sip.CSeq.method==REGISTER and ip.addr == VOIP PROVIDER IP and check if the pbx gets any response from the voip provider.

 

[andy-vdg]

I already did a capture but did one again now. The result is the same.
Requests are going out - no answer. Just one way
source: my IP --> destination: VoiP provider IP.

The resulting traffic between the query sip.CSeq.method==REGISTER and ip.addr == VOIP PROVIDER IP is exactly the same.

Andy

 

[Alejandro_3CX]

I already did a capture but did one again now. The result is the same.
Requests are going out - no answer. Just one way
source: my IP --> destination: VoiP provider IP.

The resulting traffic between the query sip.CSeq.method==REGISTER and ip.addr == VOIP PROVIDER IP is exactly the same.

Andy

So the pbx is sending the register but does not have any reply, you may need to check this with your voip provider in order to know why they are not responding the registration request.

Note: check in the contact header that the correct pbx public IP is being sent.

 

[andy-vdg]

Yes - I've already checked with them as well. They are seeing 0 requests on their side. They have nothing blocked but no traffic coming from this systems IP address. They are saying it's a 3CX issue - 3CX is saying it's a provider issue... if I could just access the console of the instance it would be easy to troubleshoot.
When I connect from another instance it works fine - register goes through instantly.
So somewhere something is blocking this specific IP.
I'm thinking of just redeploying the instance completely - see if that makes a difference with obtaining a new IP.

Andy

 

[Alejandro_3CX]

Hi Andy, since this is a hosted by 3cx installation with a supported voip provider, please enter in contact with your 3cx partner, if you do not have one you can check this link, so they can open a support ticket with us and check the settings.

 

[andy-vdg]

Ok - re-set up the hosted server with a new IP address and it registered immediately.
So something was blocking it from getting through to the Peoplefone servers.