Calls take more that 30 secs to ring at destination

[Dominique_CH]

I have noticed a very strange behavior (using an unsupported SIP-provider, JustVoIP in my case):
- when a call is issued via this operator, the time to ring on the receiving end can take more than 30 secs
- the caller end (on 3CX) gets the ring control immediately.

As one can see from the attached log,
- a call is issued at 1:49.40 and immediately signalled as ringing (Alerting)
- However, at the other end the call rings only about 60s later (at this point the caller hangs-up = Cancel)

Has anybody noticed such similar effect and is there an explanation for it? As the same customer used another PBX with the same provider before and with no problem, I suspect the problem to be within the 3CX, however w/o any evidence.

 

[ChrisC_3CX]

Despite the fact that we cannot guarantee smooth operations due to not using a 3CX Supported Provider, what I recommend you do first, since you've already taken a look at the activity log, is enable Verbose Logging from within Dashboard >> Settings and then check the activity Log again.

The SIP Provider may very likely send a 180 Ringing SIP Message to denote that the call is ringing on the other end. You should then compare the time that message was received with the time the initial SIP INVITE was sent to the provider.

Do bear in mind that, whatever the case, if the SIP INVITE message is sent by 3CX on time, then it's pretty much out of 3CX's control from that point onwards as there is nothing else required by 3CX for the other end to start ringing (Provided of course that 3CX successfully also got authenticated by the SIP Provider). The above info though might give you a better idea on what is happening.