Incoming Calls from Yeastar TG800 Routing to a Single Extension in 3CX

[Muhammed Shameem]

Hello Everyone,

We are facing a serious issue with our on-prem 3CX V20 setup and Yeastar TG800 GSM Gateway.

We've configured different VoIP trunks in both 3CX and the TG800 for different GSM ports, with the intention of forwarding calls to specific extensions in 3CX. However, all incoming calls from all GSM ports are being routed to a single extension in 3CX.

I’ve double-checked the configurations, but the problem persists.

Could anyone here help identify what might be causing this issue? Any insights or suggestions from the experts would be greatly appreciated!

 

[big3]

Hi dear this gateway not compatible with 3CX V20 , i face the same issue exactly

 

[N_G]

I think the best way to go about it is to make one SIP Gateway trunk with all ports bundled in one trunk. Then with the yeastar support ask them to identify how the calls from each part can be identified and then use that DID or field identifier to forward to different queues or extensions. Potentially might have to make an edit to the generic SIP trunk template so that the GSM number is used as a DID number or something like that. So the individual GSM number appears as DID to 3CX