I am reaching out regarding a perplexing issue we've encountered in our telephony infrastructure, specifically concerning the integration between our GoIP device and 3CX SIP Trunks.
Recently, we introduced a new SIM card into a fresh slot on the GoIP device, meticulously configuring the associated rules, SIP Trunks, and Call Queues. However, despite our careful setup, incoming calls seem to divert to an unintended SIP Trunk. Despite thorough troubleshooting, including rigorous examination of logs and real-time monitoring via iPhone, the call routing consistently deviates from the designated path.
Furthermore, I attempted to mitigate this issue by transferring an existing SIM card to the new SIP Trunk, yet encountered the same diversionary behavior.
At this juncture, our concern lies in pinpointing the root cause of this discrepancy. While we meticulously adhere to the established configurations, the system appears to deviate from its prescribed course of action, raising questions about potential underlying issues within either the GoIP or 3CX environments.
Your insights into this matter would be immensely valuable. Any guidance or suggestions you could offer to troubleshoot and resolve this anomaly would be greatly appreciated.
Recently, we introduced a new SIM card into a fresh slot on the GoIP device, meticulously configuring the associated rules, SIP Trunks, and Call Queues. However, despite our careful setup, incoming calls seem to divert to an unintended SIP Trunk. Despite thorough troubleshooting, including rigorous examination of logs and real-time monitoring via iPhone, the call routing consistently deviates from the designated path.
Furthermore, I attempted to mitigate this issue by transferring an existing SIM card to the new SIP Trunk, yet encountered the same diversionary behavior.
At this juncture, our concern lies in pinpointing the root cause of this discrepancy. While we meticulously adhere to the established configurations, the system appears to deviate from its prescribed course of action, raising questions about potential underlying issues within either the GoIP or 3CX environments.
Your insights into this matter would be immensely valuable. Any guidance or suggestions you could offer to troubleshoot and resolve this anomaly would be greatly appreciated.
