Patton SN4120 / OXYGEN multigateway

[mikeB200]

Hello

recently we changed from copper NETMOD to fiber via providers own router OXYGEN multiGateway Model HDI34201.N3A2UV.
we have a PATTON SN4120 as a gateway for the ISDN line handling which was working without any issues so far.

The problem since our fiber integration is that either Patton or 3CX system does not see any incoming calls from time to time and we need to reboot the system which works for either a few minutes or a couple of days max. the outward calls seem to work via this trunk (PATTON) gateway ok.

all calls do show on OXYGEN status incoming / diagnostic page as "missed"

our system is installed on a standalone machine and we have install the DEBIAN v.18.0.237

we have also change in PATTON trunk configuration under options the BRI Q921 Protocol from point to multipoint.

any ideas?
thanks

 

[ChrisC_3CX]

The problem since our fiber integration is that either Patton or 3CX system does not see any incoming calls

First we'll need to determine if the calls are not reaching the Gateway or the PBX. How have you determined that they are not arriving, is it simply because you're not receiving an incoming call or did you perhaps actually perform a packet capture on the 3CX PBX interface? If it's just because no incoming calls are actually ringing, I'd highly recommend you perform a packet capture on the PBX to check if you see any SIP INVITE messages coming in from the gateway. You might want to consider checking out our training material on "Basic Troubleshooting" for more info on how to do this: https://www.3cx.com/3cxacademy/videos/advanced/basic-troubleshooting/

Also, what firmware version is the Patton gateway running?

 

[mikeB200]

hello

Patton details: SmartNode
Model SN4120/2BIS4V
Hardware Version 2.3
Software Version R6.11 2019-07-02 H323 SIP

i see no activity in 3cx event log when i face this situation.
the only thing that fixes it (at least that I am aware of) is a reboot in the server or probably a reboot in Patton..

i have not managed to capture another log so far.

 

[ChrisC_3CX]

i see no activity in 3cx event log when i face this situation.
the only thing that fixes it (at least that I am aware of) is a rebbot in server or probably a reboot in Patton.

It may be better that you run a packet capture to confirm this because, if you see nothing reaching the 3CX PBX, it may mean that you'll have to reach out to Patton to have them help you troubleshoot the gateway.

 

[mikeB200]

next time this reoccurs I will try to capture logs from 3cx. meanwhile, i will reach out to PATTON as well for their input.

thanks

 

[ChrisC_3CX]

You're very welcome! Let us know how it goes!