Service Unavailable when dialing out on FXO port

[Steve123]

I'm trying to get the FXO port on an Obi 212 working, using a single SP (sp2), by setting X_InboundCallRoute to: {>(<1:>xx.):SP1},{>(<65:>xx.):li}, as described on the Ohi website. The outbound rules prefix '1' for 10 digit numbers, and '65' for 8 digit numbers, and I can see that they get successfully prepended. Calls to GV work fine, but calls to 'li' never hit the Obi, so I'm guessing the problem is on the 3CX side. Here's the failure log:

12/02/2021 2:19:00 PM - Leg L:190.1[Extn:100] is terminated: Cause: BYE from PBX

12/02/2021 2:19:00 PM - [CM503020]: Call(C:190): Normal call termination. Call originator: Extn:100. Reason: Server Failure

12/02/2021 2:19:00 PM - L:190.1[Extn:100] failed to reach Line:10001>>6596235172, reason Server Failure

12/02/2021 2:19:00 PM - Leg L:190.2[Line:10001>>6596235172] is terminated: Cause: 503 Service Unavailable/INVITE from 10.65.0.204:5061

12/02/2021 2:19:00 PM - Call to T:Line:10001>>6596235172@[Dev:sip:[email protected]:5061] from L:190.1[Extn:100] failed, cause: Cause: 503 Service Unavailable/INVITE from 10.65.0.204:5061

12/02/2021 2:19:00 PM - [CM503003]: Call(C:190): Call to <sip:[email protected]:5061> has failed; Cause: 503 Service Unavailable/INVITE from 10.65.0.204:5061

12/02/2021 2:19:00 PM - [CM503025]: Call(C:190): Calling T:Line:10001>>6596235172@[Dev:sip:[email protected]:5061] for L:190.1[Extn:100]

12/02/2021 2:19:00 PM - [CM503027]: Call(C:190): From: Extn:100 ("100-09535382" <sip:[email protected]:0>) to T:Line:10001>>6596235172@[Dev:sip:[email protected]:5061]

12/02/2021 2:19:00 PM - [CM503004]: Call(C:190): Route 1: from L:190.1[Extn:100] to T:Line:10001>>6596235172@[Dev:sip:[email protected]:5061]

12/02/2021 2:19:00 PM - Line limit check: Current # of calls for line Lc:10001(@Obi212[<sip:[email protected]:5061/UDP>]) is 0; limit is 1

12/02/2021 2:19:00 PM - Call(C:190): Call from Extn:100 to 96235172 matches outbound rule 'Singapore Local'

12/02/2021 2:19:00 PM - [Flow] Call(C:190): has built target endpoint: Out#:>>Rule{Singapore Local}>>96235172 for call from L:190.1[Extn:100]

I'm not certain whether this is a problem on the Ohi side or 3CX. I don't see outbound calls hitting the Ohi, but neither do I see inbound calls doing so.

 

[Steve123]

I'm beginning to wonder if this isn't some kind of hardware fault with the Obi. If I change that rule to use 'ph', the phone rings. So it seems it might be the Ohi LI port. I'll pop over to the Ohi forum to see if anyone there can help. If anyone here has any suggestions, I'm listening.