No audio on production DID only - setup worked until today.

[lawit]

Problem: no audio on DID calls where setup worked until today.

Information:

• Trunk is registered (on my end and according to clearlyIP)
• DID calls show on Asterisk info and on Call Logs
• Outbound calls and calls between handsets behind NAT work.
• NAT / Router and port forwards are the same - no changes.
• DID route logs as working.
• Have gracefully restarted Asterisk; gracefully stopped asterisk and restarted hardware.
• IVR routed to exists and audio recordings play from FREEPBX webgui module.
  

Logs below [removed]. Any ideas on cause of problem? Thank you for your time and consideration.

 

[Eliad]

this is usually caused by your firewall. What firewall do you use?
For example Pfsense does this sometimes, you can fix this by resetting the firewall states. Rebooting the firewall does not work all the times.

 

[ostridge]

NAT / Router and port forwards are the same - no changes.

I do not have an answer as to why - so just scratching my head.
If I you are running incredible pbx 2020 on raspberry pi 4b w/ 4 gigs (as one of your posts)?

I notice you are using port forwards which usually are only needed if server is running 'public' or you need access for incoming mobiles or extensions from outside the NAT router.

Settings in 'Settings/SIP Settings/General SIP Settings/ RTP Port Ranges (default is 10000 to 20000 ) does your port forwards match your settings?

Is it happening on other extensions?

Regards

 

[lawit]

@Eliad and @ostridge thank you both for your consideration and replies. I believe the problem has been resolved. The ISP technician came out and observed that our router's electrical plug was very loosely touching the receptacle. He firmly plugged it back in. Since then the problem has been resolved. Interestingly, other than inbound calls the internet was working. After reviewing your comments and speaking with a FreePBX consultant I posit that the loose electrical connection cause the router to work in an undervoltage or varying voltage condition which caused the RTP stream to be either not routed or interrupted. On the one hand, its pitiful to have failed the most basic of IT diagnostics - "is it plugged in?" On the other hand, its great to have it working. Thank you both again!