Solved Hosted 3CX with DIDLogic

[Jessie.C]

Firewall check passed
DIDLogic showing as green in SIP trunks
Outbound rules set to use DIDLogic for default extension group
Can RECEIVE calls
Outbound calls fail from web client and iPhone app

Reviewed the logs and found a few errors or possible issues, but can't figure out how to resolve them.

06:18:54.173|| Info|MSEndPoint.cpp(3181): No EP found for 127.1.2.3:103 <- tunnel

And also

06:19:22.168||Error|TLSTransp.cpp(574): TLS connection read has returned socket error: 0


06:19:22.169||Error|ConnMgr.cpp(1341): TCPSocketProcessor: Connection 21<-::ffff:X.X.X.X:49498:28 read failure


06:19:22.169||Error|ConnMgr.cpp(1369): TCPSocketProcessor: Removed after error 21<-::ffff:X.X.X.X:49498:28


06:19:22.169|| Info|Tunnel.cpp(464): !! Tunnel 'ClientTunnel'(123456): terminating connection with ::ffff:X.X.X.X:49498


06:19:22.169|| Info|Tunnel.cpp(393): Forcing termination of JC-iPhone


06:19:22.169|| Info|Tunnel.cpp(464): !! Tunnel 'ClientTunnel'(123456): terminating connection with ::ffff:X.X.X.X:49498


06:19:22.169|| Warn|Bridge.cpp(464): Currently mapped connection with id=clnt.0-xtyqp7y4gu6c0ydfatjhaf1ume0gfnnb_30603664 doesn't match to one being removed, ignore removal


06:19:22.169|| Info|ConnMgr.cpp(1266): TCPSocketProcessor: Removed 21<-::ffff:.X.X.X.X:49498:28, total 0


06:19:22.169|| Info|ConnMgr.cpp(1266): TCPSocketProcessor: Removed 21<-::ffff:X.X.X.X:49498:28, total 0


06:19:22.169|| Info|ConnMgr.cpp(1705): TimerActions: Removed 21<-::ffff:X.X.X.X:49498:28


06:19:22.169|| Info|ConnMgr.cpp(1427): IncomingSlaveUDP: skip to DELETE connection 21<-::ffff:X.X.X.X:49498:28. It has no input channel for this handler.


06:19:22.169|| Info|ConnMgr.cpp(1427): IncomingSlaveUDP: skip to DELETE connection 21<-::ffff:X.X.X.X:49498:28. It has no input channel for this handler.


06:19:22.169|| Info|TCPSide.cpp(307): 21<-::ffff:X.X.X.X:49498:28: Destroyed; num.conn=0


06:19:22.169|| Info|TLSTransp.cpp(445): TLS broke


06:19:22.169|| Info|Tunnel.cpp(257): Destroying Tunnel 123456


06:19:22.169|| Info|Tunnel.cpp(393): Forcing termination of JC-iPhone


06:19:56.210|| Info|Stack.cpp(386): SIP Stats:


TU summary: 0 TRANSPORT 0 TRANSACTION 0 CLIENTTX 0 SERVERTX 0 TIMERS 1


Transaction summary: reqi 2 reqo 130 rspi 123 rspo 2


Details: INVi 1/S1/F0 INVo 52/S1/F51 ACKi 1 ACKo 52 BYEi 0/S0/F0 BYEo 1/S1/F0 CANi 0/S0/F0 CANo 23/S23/F0 MSGi 0/S0/F0 MSGo 0/S0/F0 OPTi 0/S0/F0 OPTo 0/S0/F0 REGi 0/S0/F0 REGo 0/S0/F0 PUBi 0/S0/F0 PUBo 0/S0/F0 SUBi 0/S0/F0 SUBo 0/S0/F0 NOTi 0/S0/F0 NOTo 2/S1/F1 REFi 0/S0/F0 REFo 0/S0/F0 INFi 0/S0/F0 INFo 0/S0/F0 PRAi 0/S0/F0 PRAo 0/S0/F0 SERi 0/S0/F0 SERo 0/S0/F0 UPDi 0/S0/F0 UPDo 0/S0/F0


Retransmissions: INVx 0 finx 0 nonx 0 BYEx 0 CANx 0 MSGx 0 OPTx 0 REGx 0 PUBx 0 SUBx 0 NOTx 0 REFx 0 INFx 0 PRAx 0 SERx 0 UPDx 0

 

[ChrisC_3CX]

I'm afraid the log provided is not enough to determine what's going on so we'll need a bit more information if we're to hopefully figure it out.

• What version of 3CX are you running? Check in "Dashboard >> Information >> License/Version".
• Where is the PBX hosted (on-prem, in cloud, etc) and what OS and Hypervisor is it running on?
• You mention webclient and iOS App specifically, is that to say that other clients or IP Phones work?
• I'd highly recommend you check the event log on the dashboard for an error upon an outbound call attempt.

 

[Jessie.C]

I'm afraid the log provided is not enough to determine what's going on so we'll need a bit more information if we're to hopefully figure it out.

• What version of 3CX are you running? Check in "Dashboard >> Information >> License/Version".
• Where is the PBX hosted (on-prem, in cloud, etc) and what OS and Hypervisor is it running on?
• You mention webclient and iOS App specifically, is that to say that other clients or IP Phones work?
• I'd highly recommend you check the event log on the dashboard for an error upon an outbound call attempt.

Thanks for the feedback!

I'm using a hosted by 3CX solution. So it's the latest version, running on Debian Linux. I haven't even tried IP phones yet.

The event log shows that the service is unavailable:
Call or Registration to 8*******@(Ln.10001@DID Logic) has failed. 206.191.159.247 replied: 503 Service unavailable; from IP:206.191.159.247:5060

It's showing the SIP Trunk as connected (Green Dot), but then shows Service Unavailable.

 

[ChrisC_3CX]

Based on the log it would seem that DIDLogic is replying with an error message. If IP 206.191.159.247 is them then that's definitely what's happening, in which case, you might actually need to reach out to them to find out exactly why they are replying with that message.

The message is not that specific so I'm afraid that I cannot be absolutely sure what the problem is, but if you want to try a few things before contacting them you could check things like making sure the number you're dialing is in a format the SIP Provider accepts (E164, etc), the Caller ID you are sending is allowed by the provider(check the extensions OutboundCallerID value), etc.

 

[Jessie.C]

I submitted a ticket to DIDLogic. They replied and let me know that it was as simple as placing a 1 in front of the number being dialed. That sure would have been a much better error response than "Service Unavailable", but at least the issue is solved! Thanks all!

 

[ChrisC_3CX]

Brilliant!

hey replied and let me know that it was as simple as placing a 1 in front of the number being dialed. That sure would have been a much better error response than "Service Unavailable"

At least you managed to get this sorted!

As such I'll be marking this thread as solved.