this post was submitted on 23 Oct 2023
2 points (100.0% liked)
VoIP
1 readers
1 users here now
Rules
-
Be civil. Disagreements of varying intensities will happen, but particularly vitriolic attacks will be pruned from the discussion.
-
Do not promote or advertise for any business, service or product unless responding to a specific request for recommendations. This includes recommending a user change providers when they have not indicated they are interested in doing so.
-
Do not send private messages to users, or invite users to send you a private message, for the purpose of promoting or advertising a business, service or product.
-
Do not invite, encourage, or seek help with engaging in unethical or fraudulent activity relating to VoIP, such as call spoofing, robocalling and autodialers, or fraudulent STIR/SHAKEN attestation.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This is a known issue. Google it to narrow down further but essentially there is a keepalive that should be sent at around 30 seconds (roughly, depends somewhat on where you start counting). Without this keepalive packet the call will drop as the carrier assumes you left.
It's been years since I hit this issue. Since you using a bad pbx system I won't help further than say most have already given you the likely solution but it's highly likely you need to consider ports, and said keepalive or ack in general.
Here's people fighting and resolving: https://stackoverflow.com/questions/27614532/sip-call-drop-after-30seconds