The key to GSM may be in how the data streams are reaching the phones. While you indicate 1-way audio, is this also true if the calls are directed to VM instead of the phone? Have you taken a data capture at the S PBX to see what the messaging looks like?
The other area of concern is that while you mention 1-way audio, you fail to mention which end of the conversation is the one that cannot hear and if there is any difference as to which end starts the call.
The reference to Linkus with 1-way audio and Linkus Client having robot voice needs some clarification. From the Yeastar website - "With Linkus Softphone App, all the features of a desk phone can be realized by your mobile device and desktop. Available using Microsoft Windows, macOS, iOS, and Android, Linkus makes real-time business communication easy across multiple devices."
As you can see, there are two flavors - a desktop client and then a mobile client and it is not clear as to which Linkus client is being used and where in your issue.
There will likely be many more questions as you have stated what may be a fairly complex problem, but without any real details. It is pretty much a high level explanation of what is happening, but no codecs, how the PBX network is set - switch, route, or dual, if there is more than just the GSM for telephony (seems somewhat strange to only have 4 call paths on a S300), etc. Is this a new install or an old and if old, was it all working at any point before?
Hi, thanks for the reply.
In my configuration I also have an E1 line.
The problem with GSM lines seems to have been solved. I think it would have been NAT.
My configuration has 3 internal vlans as in the image.
I created a default route for internet access via vlan 89. (works)
The Vlan (100) by default is only used to connect 200 phones (it works).
But, with the linkus desktop on a computer on vlan 89 I can't make myself heard calling any number that is on vlan 100. on linkus I use the ip on vlan 89 to connect.
am i doing wrong?
You have essentially repeated yourself, but added some details about how the S PBX is defined from a NAT perspective.
What is missing is where is the LINKUS client located? You indicated that you created VLAN 89 for internet access, and it is not clear how Linkus uses that. You stated on way audio, but failed to indicate which side could hear and which side could not and if there was any change depending on which side initiated the call. It would also possible help to know if Linkus can call and leave a VM on the system and then subsequently dial back in and see if they can hear the message they left.
You may need to check the PC as Linkus is apparently resident and it could be that the NIC interface of the PC is filtering. What VLAN is set in the PC NIC interface card? When using a common desk phone, the phone typically has a built in switch whereby on the input side you would pass 100 and on the PC side 89.
Microsoft Teams Integration
Hikvision Intercom Integration
ISDN Switch-off Migration
All materials to evaluate Yeastar as a PBX vendor on products, solutions, partner program, support, learning resources, etc.
