Outbound error 408

[butzo]

I was getting outbound errors and switched from TCP to UDP, this seemed to solve my problem for a few days,
I also made sure my caller ID was in the outbound caller ID with +1XXXXXXXXXX
I get this error on any outbound call

Call or Registration to +1818XXXXXXX@(Ln.10000@Amazon Chime Voice Connector) has failed. 0.0.0.0 replied: 408 Request Timeout; internal
SIP Server ID: 12294 07/28/2021 12:05:42 AM

Please advise,

 

[Peter of a Telco]

Take a look at your REGISTRATION immediately before the INVITE and check that: (1) the INVITE is being sent to the same SBC Proxy Address as the REGISTRATION; (2) the INVITE is being sent to the same Destination Port (likely is of course) and the Source Port (trouble here I have seen) is the same as the REGISTRATION; (3) The transport being used (UDP/TCP) for the REGISTARTION and INVITE is the same. Also, take a look in Wireshark (etc) to see if it is a real Request Timeout (time elspase between INVITE and 408) as not all are, and that might give you a clue as well. On (2) above, no doubt your Source Port is 5060 but if you are using an Internet Gateway Modem/Firewall this is likely to be changed on the WAN side by its NAT function if you are using NAT which I suspect you are. Also, watch out for SIP ALG as that is a nasty manipulator that causes all manner of problems and not all Internet Gateway Modems that state it is turned Off in GUI actually turns it Off at all, or it is partically left On in function. The old TCP side-step (don't use UDP) might help there as SIP ALG loves to play with UDP. In NZ Destination Port 8333 was introduced as a means to get around it as well but that is for my SP as SIP-ALG has caused lots of trouble over here. Good luck.

 

[ChrisC_3CX]

Just want to clarify that 3CX supports Amazon Chime Voice Connector as an IP Based SIP Trunk so REGISTRATION should not occur.

When you switched to UDP did you also make the change on Amazon Chime's control panel to have incoming calls sent via UDP as well?

Please also provide more information regarding this 3CX Instance such as, where it's hosted, OS, version, etc.

 

[butzo]

I followed Network Chuck's YouTube video exactly, so I used AWS,
On Demand Linux t2.nano Instance, Debian, Linux/UNIX, amz-custom-us-east ohio
Chime settings:
calling plan is set to USA,
inbound rules 5060 UDP

I found this on my inbound rules:

Port range	Protocol	Source	Security groups
9000 - 10999	UDP	0.0.0.0/0	pbxexpress
9000 - 10999	UDP	::/0	pbxexpress
0	ICMP	0.0.0.0/0	pbxexpress
0	ICMP	::/0	pbxexpress
22	TCP	0.0.0.0/0	pbxexpress

Outbound rules

Port range	Protocol	Destination	Security groups
All	All	0.0.0.0/0	pbxexpress

 

[ChrisC_3CX]

To get a bit more info and help us better understand the situation:

• Does this 3CX Instance pass the firewall test when you run it under "Dashboard >> Firewall"?

• Do you remember approximately how long it worked after initial setup and approximately how long it worked after switching the transport protocol to UDP?

• Please run the following test and let me know what happens. Try placing at least 10 outbound calls and wait for every single call to time out and generate the "408 Request Timeout" message. Does this continue no matter how many calls you make?

 

[butzo]

Firewall everything looked ok and passed but I noticed--

• detecting SIP ALG... not detected

After I setup I made a few calls and it was fine, but I didnt make another call until about 7 days later, after I switched to UDP same I tested it and didnt notice until about 7 days later something was wrong.

I made 10 calls and all 10 calls WENT THROUGH FINE, I'm pleasantly confused