3CX and Yeastar TG100 GSM Gateway

Status
Not open for further replies.

willardc

Silver Partner
Advanced Certified
Joined
Jun 15, 2020
Messages
5
Reaction score
1
Hi everyone

I have a cloud 3CX in AWS.

I have an on prem GSM Gateway Yeastar TG100 with one SIM Slot

I have integrated the two using SIP trunks connections.

I have done some port forwarding on the firewall no traffic is being blocked on the Fortinet firewall side (INBOUND and OUTBOUND RULES.)

Incoming is working fine but outgoing it gives a false ring without ringing to the other end you just get the ringback as if the number is not being picked but nothing is being sent.

Below is what I am getting. Please help
  • Call or Registration to 0784977XXX@(Ln.10005@TG100_GW) has failed. 0.0.0.0 replied: 408 Request Timeout; internal
    SIP Server ID: 12294 09/05/2024 2:01:12 AM
  • Call or Registration to 0784977XXX@(Ln.10005@TG100_GW) has failed. 0.0.0.0 replied: 408 Request Timeout; internal
    SIP Server ID: 12294 09/05/2024 1:40:20 AM
  • Call or Registration to 0784977XXX@(Ln.10005@TG100_GW) has failed. 0.0.0.0 replied: 408 Request Timeout; internal
    SIP Server ID: 12294 09/05/2024 1:11:51 AM
 
Gateways should only be used with an on premises system, and not with a hosted or cloud system.

Only FXS gateways can be connected to 3CX via the SBC, Not FXO or GSM gateways.
 
Status
Not open for further replies.

Latest Posts

Members Online Now

Forum statistics

Threads
111,794
Messages
589,018
Members
164,590
Latest member
Infinitas