Problems with patton 4552

Discussion in '3CX Phone System - General' started by drhans, Jun 18, 2010.

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

    Joined:
    Jun 18, 2010
    Messages:
    2
    Likes Received:
    0
    Hi,

    I'm justs trying out 3CX and it seems very nice, but I'm having problems with a Patton 4552 i just bought to try this setup out.

    I set up the Patton using the "add PSTN" guide and uploaded the cfg file to the Patton. I made a 0-prefix outbound rule to the Patton, but it seems like the Patton is not registered with 3CX (see log below). I disabled the firewall on the server (Win7) just to rule that out, but that changes nothing. I can't dial in thru the Patton either.. I can do internal calls just fine.

    The server and softphone is on ip 192.168.2.4 but the Patton is on 192.168.2.7, but there is no sign of 192.168.2.7 in the log for some reason.
    The Patton gateway is constantly listed as "status: Not Registered" in the Ports tab, but i don't know if that is proper behavior.


    Any help will be much appreciated..
    thanks in advance.

    ---------- LOG ----------
    23:45:13.644 [CM503020]: Normal call termination. Reason: Not available
    23:45:13.644 [CM503016]: Call(39): Attempt to reach <sip:028682626@192.168.2.4:5060> failed. Reason: Not Registered
    23:45:13.641 [CM503016]: Call(39): Attempt to reach <sip:028682626@192.168.2.4:5060> failed. Reason: Not Registered
    23:45:13.641 [CM503017]: Call(39): Target is not registered: Unknown:28682626 dialed on (AnyLine@ISDN gateway)
    23:45:13.641 [CM303003]: There are no available outbound lines on gateway ISDN gateway at this time.
    23:45:13.638 [CM503010]: Making route(s) to <sip:028682626@192.168.2.4:5060>
    23:45:13.637 [CM505001]: Ext.10: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone 4.0.12964.0] PBX contact: [sip:10@192.168.2.4:5060]
    23:45:13.631 [CM503001]: Call(39): Incoming call from Ext.10 to <sip:028682626@192.168.2.4:5060>
     
  2. carolinainnovative

    Joined:
    May 4, 2009
    Messages:
    369
    Likes Received:
    5
    Have you tried running wireshark on your machine to see if the patton is even attempting to connect? (if no - try that - see what it is doing)
     
  3. drhans

    Joined:
    Jun 18, 2010
    Messages:
    2
    Likes Received:
    0
    Yeah thanks. I will try that, but does it not look like the 3CX can't find the Patton from the log, and not the other way around?

    Should the status on the gateway be "Registered" all the time like the phones, or does it only register when a call is placed or received?

    Thanks.
     
  4. carolinainnovative

    Joined:
    May 4, 2009
    Messages:
    369
    Likes Received:
    5
    In general, the patton should show as registered... so when you wireshark it, make sure you tell 3cx to refresh the registration, then try a call. See what gets logged.
     
  5. earleyscripts

    Joined:
    Jun 11, 2010
    Messages:
    7
    Likes Received:
    0
    I need to know what versuion of Hardware the 4552 Unit is. Login in to the Unit with a Web browser and you should be able to see what version the Unit is. If it is less than Version 4.1 .....2.1 or 3.1 There is a fix for this and is requires a bit of work. The config file for the 4552 generated by the 3CX assuming you are on the latest version will not work. If you view this file in a Text editor is will state that the config file is only valid for Firmware versions 5.n ......
    Do not attempt to down load any versions of firmware if your hardware is less than 4.1 you might turn the Unit into a "brick".

    I can supply additional help but this is to long to do inside the Forum and not wishing to break any rules I need you to contact me directly.Never done this before so perhaps someone might guide me on the correct protocol to keep to the rules.

    In the mean time if you have any knowledge on getting 3CX to talk to Voxalot then you can help me.

    Regards..... Earleyscripts 20th at 07:58 Hrs BST :arrow:
     
Thread Status:
Not open for further replies.