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

communick@netheads.online

Problem with freePBX & Yealink (alien.top)

submitted 11 months ago by linus0508@alien.top to c/voip@netheads.online

5 comments fedilink hide all child comments

So I have a bit of a difficult situation. I did a small install in an office with only one phone line at first. As a hardware phone we opted for a Yealink W60b Base with a W56H Handset. The setup is just working fine with no issues.

A couple months later the customer got a second line from the provider (German Telekom) which we setup in freePBX and got the customer a Yealink W52H as a mobile device. Strangely this phone is making and receiving calls just fine but if it gets called from outside the caller isn’t able to hear anything while the receiver is hearing anything normal. Also the call gets ended after around 30 seconds ago. I tried switching the lines around so the “old” line would lead to the new handset and vice versa and now the problem moved to the old line. So I thought it must be the handset. But both are configured the same (nearly defaults) and also the problem doesn’t exist internal calls.

Has anyone got an idea what the problem could be?

you are viewing a single comment's thread
view the rest of the comments

[–] linus0508@alien.top 1 points 11 months ago

By standard those are UDP. I tried swapping to TCP or TLS but always got the same result. Strangely setting one account in the Yealink Base to TCP and the other to UDP resolved the issue.