Patton SN4528 FXO can't dial out

Discussion in '3CX Phone System - General' started by natanel, Jul 26, 2015.

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

    Joined:
    Jun 24, 2015
    Messages:
    6
    Likes Received:
    0
    Hi guys,
    I switched to the PATTON SN4528 gateway, which has 4 FXO and 4 FXS.
    (I don't use the FXS as for now)
    I chose the SN4524 model (when I set it up in the 3cx), generated the file and uploaded it to the gateway.
    3cx shows the line with green color (Trunk status), but I can't dial out, only receive calls.

    Here is the log:
    26-Jul-2015 17:05:55.483 [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 198.50.247.220:3478 over Transport 10.0.0.11:5060
    26-Jul-2015 17:01:43.200 [CM503008]: Call(C:13): Call is terminated
    26-Jul-2015 17:01:43.199 Leg L:13.1[Extn] is terminated: Cause: CANCEL from 10.0.0.19:51931
    26-Jul-2015 17:01:39.624 Leg L:13.2[Line:10001>>0547341122] is terminated: Cause: 504 Server Time-out/INVITE from 10.0.0.4:5060
    26-Jul-2015 17:01:39.624 [CM503025]: Call(C:13): Calling T:Line:10001>>0547341122@[Dev:sip:10002@10.0.0.4:5061,Dev:sip:10003@10.0.0.4:5062,Dev:sip:10004@10.0.0.4:5063] for L:13.1[Extn]
    26-Jul-2015 17:01:39.621 Call to T:Line:10001>>0547341122@[Dev:sip:10001@10.0.0.4:5060,Dev:sip:10002@10.0.0.4:5061,Dev:sip:10003@10.0.0.4:5062,Dev:sip:10004@10.0.0.4:5063] from L:13.1[Extn] failed, cause: Cause: 504 Server Time-out/INVITE from 10.0.0.4:5060
    26-Jul-2015 17:01:39.621 [CM503003]: Call(C:13): Call to <sip:0547341122@10.0.0.4:5060> has failed; Cause: 504 Server Time-out/INVITE from 10.0.0.4:5060
    26-Jul-2015 17:01:28.643 [CM503025]: Call(C:13): Calling T:Line:10001>>0547341122@[Dev:sip:10001@10.0.0.4:5060,Dev:sip:10002@10.0.0.4:5061,Dev:sip:10003@10.0.0.4:5062,Dev:sip:10004@10.0.0.4:5063] for L:13.1[Extn]
    26-Jul-2015 17:01:28.595 [CM503027]: Call(C:13): From: Extn:10 ("Natanel " <sip:10@10.0.0.11:5060>) to T:Line:10001>>0547341122@[Dev:sip:10001@10.0.0.4:5060,Dev:sip:10002@10.0.0.4:5061,Dev:sip:10003@10.0.0.4:5062,Dev:sip:10004@10.0.0.4:5063]
    26-Jul-2015 17:01:28.595 [CM503004]: Call(C:13): Route 1: from L:13.1[Extn] to T:Line:10001>>0547341122@[Dev:sip:10001@10.0.0.4:5060,Dev:sip:10002@10.0.0.4:5061,Dev:sip:10003@10.0.0.4:5062,Dev:sip:10004@10.0.0.4:5063]
    26-Jul-2015 17:01:28.595 Line limit check: Current # of calls for line Lc:10004(@1[<sip:10004@10.0.0.4:5063>]) is 0; limit is 1
    26-Jul-2015 17:01:28.595 Line limit check: Current # of calls for line Lc:10003(@1[<sip:10003@10.0.0.4:5062>]) is 0; limit is 1
    26-Jul-2015 17:01:28.595 Line limit check: Current # of calls for line Lc:10002(@1[<sip:10002@10.0.0.4:5061>]) is 0; limit is 1
    26-Jul-2015 17:01:28.595 Line limit check: Current # of calls for line Lc:10001(@1[<sip:10001@10.0.0.4:5060>]) is 0; limit is 1
    26-Jul-2015 17:01:28.595 Call(C:13): Call from Extn:10 to 90547341122 matches outbound rule 'Rule for 1'
    26-Jul-2015 17:01:28.594 [CM503001]: Call(C:13): Incoming call from Extn:10 to <sip:90547341122@10.0.0.11:5060>


    Don't know what to do... please advise.

    Thanks!
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,355
    Likes Received:
    223
    I'm assuming the the IP of the gateway, is correct (10.0.0.4), and the the ports set-up in the gateway are 5060 to 5063.

    The failure is that there is no response when an Invite is sent. Cause: 504 Server Time-out/INVITE from 10.0.0.4:5060

    So... I have to think that 3CX thinks it is sending the Invite to the correct address, but it isn't, or there is another setting on the gateway that is not correct.

    That said, given that the gateway has both FXO and FXS services...more often that not, FXS services make use of port like 5060, 5061 etc. , and FXO ports are something like 5070, 5071, (a higher range) to avoid confusion (not a cast in stone rule, however). Be sure that the ports, data filled in 3CX, match the ports in the gateway. Unlike an ATA, registration does not tell 3CX what ports to use.
     
  3. natanel

    Joined:
    Jun 24, 2015
    Messages:
    6
    Likes Received:
    0
    I've checked the ports prior posting the problem here.
    All settings seems to be o.k, don't know what to do.
     
  4. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,355
    Likes Received:
    223
    Haven't used a Patton before, so someone else on the forum might be better able to answer. However, if the gateway has an internal log, syslog, or otherwise, then that may be able to help identify what is going on..

    I'm still suspicious that it may be a network setting.

    You did confirm that the phone lines are connected.
     
  5. natanel

    Joined:
    Jun 24, 2015
    Messages:
    6
    Likes Received:
    0
    I receive calls, so all lines are connected..
     
  6. armandoangeles

    Joined:
    Jul 28, 2015
    Messages:
    4
    Likes Received:
    1
    Hi natanel,

    I encounter same issue last month (I can receive a call but I can't make outbound call) the only difference is I used other model of Patton gateway (4524). The error logs you posted is same with my logs.


    What I did is coordinate it to Patton support group, they provide me new config file and upload to Patton gateway.
    Issue was resoled.
     
Thread Status:
Not open for further replies.