Audio suddenly stopped working on AWS instance

[CBUTLER247]

I recently installed 16.0.1581 on an AWS T2.small instance last week and it has been working without any issues until today.

This morning (or sometime overnight) the PBX suddenly had no audio to/from the SIP Trunk (Fusion) it was connected to. I refreshed the registration and the issue persisted. Calls through a different SIP Trunk, internal calls, voicemail, system prompts continued to work. Calls were connecting, but just no audio both ways.

I did the firewall checker again and everything passed. Once the services restarted after the firewall checker the voice to/from the SIP trunk suddenly started to work.

Now I'd like to get to the bottom of the issue so it doesn't happen again, but once the services were restarted there are no logs from before the restart in the Activity Log.

Is there anything else that I can look into? Has anybody else run into this issue. This was installed on AWS via https://pbxexpress.3cx.com

Thanks!

 

[Evolute IT]

I recently installed 16.0.1581 on an AWS T2.small instance last week and it has been working without any issues until today.

This morning (or sometime overnight) the PBX suddenly had no audio to/from the SIP Trunk (Fusion) it was connected to. I refreshed the registration and the issue persisted. Calls through a different SIP Trunk, internal calls, voicemail, system prompts continued to work. Calls were connecting, but just no audio both ways.

I did the firewall checker again and everything passed. Once the services restarted after the firewall checker the voice to/from the SIP trunk suddenly started to work.

Now I'd like to get to the bottom of the issue so it doesn't happen again, but once the services were restarted there are no logs from before the restart in the Activity Log.

Is there anything else that I can look into? Has anybody else run into this issue. This was installed on AWS via https://pbxexpress.3cx.com

Thanks!

Have you checked if the SIP Provider IP's are not blacklisted? I had a similar issue recently and it was caused by a lot of simultaneous incoming calls. The PBX didn't like it and banned the IP of my provider, I had to unban it then whitelist it.

 

[CBUTLER247]

Have you checked if the SIP Provider IP's are not blacklisted? I had a similar issue recently and it was caused by a lot of simultaneous incoming calls. The PBX didn't like it and banned the IP of my provider, I had to unban it then whitelist it.

Hello, and thank you. Yes, I did check the IP blacklist and also cleared the few entries that were there just for safe measure and the issue continued.

Thanks!

 

[Evolute IT]

Hello, and thank you. Yes, I did check the IP blacklist and also cleared the few entries that were there just for safe measure and the issue continued.

Thanks!

Can you run a wireshark capture on the 3CX? Then make a test call, see where the audio stops. You should see the RTP route.

 

[CBUTLER247]

I'll have to do that once this issue occurs again. It is currently working after restarting the services.

I called my SIP Trunk provider and they didn't have much since they weren't media monitoring the calls, but they did say my localhost IP 127.0.0.1 was randomly showing up in the registration at times.

SIP Trunk was configured for account based registration and I checked the network settings and it is configured for Static Public IP with my correct public IP listed. I have just changed it to IP based registration so we will see if that fixes the issue with the localhost IP registration issue.

 

[Evolute IT]

I'll have to do that once this issue occurs again. It is currently working after restarting the services.

I called my SIP Trunk provider and they didn't have much since they weren't media monitoring the calls, but they did say my localhost IP 127.0.0.1 was randomly showing up in the registration at times.

SIP Trunk was configured for account based registration and I checked the network settings and it is configured for Static Public IP with my correct public IP listed. I have just changed it to IP based registration so we will see if that fixes the issue with the localhost IP registration issue.

The localhost IP is not supposed to be in the SDP so there was probably a network config issue.

However, Register or IP Based shouldn't change anything but we'll see.

 

[CBUTLER247]

I searched the parameters and the localhost IP is in the following:

IVRSIPINTERFACE
CM_API_INTERFACE
CM_API_IP
WEBRTC_SIP_BINDING_INTERFACE
TNL_CLIENT_SIPINTERFACE
CHR_LISTEN_IP
CHR_CONN_IP

Would any of those not be correct?

Thanks!

 

[Evolute IT]

I searched the parameters and the localhost IP is in the following:

IVRSIPINTERFACE
CM_API_INTERFACE
CM_API_IP
WEBRTC_SIP_BINDING_INTERFACE
TNL_CLIENT_SIPINTERFACE
CHR_LISTEN_IP
CHR_CONN_IP

Would any of those not be correct?

Thanks!

Those are normal. Please don't play with parameters unless explicitly told by 3CX to do so.