Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Patton 4114 Gateway not dialing out

Discussion in '3CX Phone System - General' started by apex7, Oct 17, 2013.

Thread Status:
Not open for further replies.
  1. apex7

    Joined:
    Jun 22, 2012
    Messages:
    5
    Likes Received:
    0
    Hi, I installed a Patton Gateway 4114 (4xFXO) onto the 3CX Version 12.

    I used the standard configuration as per the instructions in 3CX and uploaded the configuration file to the Patton gateway.
    I'm only using 2 of the 4 fxo ports.
    It was all working ok for a couple of weeks and then some of the handsets couldn't dial out over the Patton. I tried to reconfigure it, reset to factory settings etc, but now I cant get any phones to dial out via the Patton. I have 2 outgoing rules, dial 5 to route out via Patton, or 9 to dial out over the VoIP provider.

    Incoming calls on the Patton and VoIP are working correctly. Dialing out over the VoIP is working.
    It's only dialing OUT over Patton where there is an issue.

    Strange thing as well, even when it was working, if you dialed out via the Patton, it would use ports 10008 and 10009, even though those two FXO ports where not being used. I was only using FXO 0 and FXO 1 on the Patton, which in my mind should be port 10006 and 10007 in 3CX.
    So not sure how these things work together??

    Version of Firmware in Patton: R6.4 2013-09-05
    3CX - Version 12 with SP1

    Any help appreciated.
     

    Attached Files:

  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,105
    Likes Received:
    329
    The calls appear to be attempting to go out over trunks that are not connected to a phone line. You need to disable trunks 10008 and 10009 in 3CX.
     
  3. apex7

    Joined:
    Jun 22, 2012
    Messages:
    5
    Likes Received:
    0
    I tried that as well. It didnt work
     
Thread Status:
Not open for further replies.