3CX on AWS EC2 V18 SIP Trunk not registering to provider

[actechsamoa]

New 3CX setup on AWS EC2 platform all works well. Firewall check all green, but SIP trunk not registering. Just need confirmaton that Provider needs to whitelist from their end.

This from Activity Log:
03/15/2024 3:02:29 AM - [CM504005]: Registration failed for: Lc:10000(@Breeze[<sip:[email protected]:0/UDP>]); Cause: Cause: 408 Request Timeout/REGISTER from local

This from Events Log:
Registration at xxxxx has failed. Destination (sip:202.151.30.147:5060;lr) is not reachable, DNS error resolving FQDN, or service is not available.

This is snippet from packet capture: appreciate any assistance.

 

[Alphabetic]

Are you sure the SIP server is correct? When I ping digicelvoice.com I get an error.

 

[actechsamoa]

Are you sure the SIP server is correct? When I ping digicelvoice.com I get an error.

Yes it's correct, they've disallowed ICMP.

 

[SteveITS]

If it failed ensure it isn't in the blacklist on your 3CX server. And/or add it as an Allow entry.

 

[actechsamoa]

Yeah there's nothing in the Blacklist.

 

[richiewhite]

Looks to me as though they haven't responded to your REGISTER, but the snippit doesn't give a lot to go on.

I generally go straight to Telephony > Sip Flows when I open Wireshark. You should be able to see the Register flow there, select it and click Flow Sequence to get a nice diagram. If you see REGISTER in one direction with nothing in the other direction, I'd be checking with the trunk provider to make sure they don't need to allow anything.

 

[OlegR_3CX]

@actechsamoa Indeed, as mentioned above there is only one registered message and no reply.
Reach your provider support and take it from there.