Patton 4960 with 3cx v9

Discussion in '3CX Phone System - General' started by Coretech, Jan 25, 2011.

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

    Joined:
    Dec 30, 2010
    Messages:
    5
    Likes Received:
    0
    Hello,

    I am trying to get a Patton 4960 to work with the 3cx Version 9.15781 (January 2011). I have tried several different 4960 firmwares (including the recommended) with the same result. I generated a config file with the wizard and the Gateway is registered to the 3cx just fine and the T-1 is up and active. No matter what I do when I dial out I get a 404 Not Found error in the server log. I have the outbound rule set to dial out using the 4960 which is seen in the log. There is no message, just invalid number immediately.

    3cx Phone: 192.168.111.20
    Patton 4960: 192.168.111.21

    22:04:23.500 [CM503020]: Normal call termination. Reason: Not found
    22:04:23.500 [CM503016]: Call(39): Attempt to reach <sip:1234567@192.168.111.20> failed. Reason: Not Found
    22:04:23.500 [CM503003]: Call(39): Call to sip:1234567@192.168.111.21:5060 has failed; Cause: 404 Not Found; from IP:192.168.111.21:5060
    22:04:23.437 [CM503025]: Call(39): Calling Unknown:1234567@(Ln.10000@Patton 4960)@[Dev:sip:10000@192.168.111.21:5060]
    22:04:23.406 [CM503004]: Call(39): Route 1: Unknown:1234567@(Ln.10000@Patton 4960)@[Dev:sip:10000@192.168.111.21:5060]
    22:04:23.406 [CM503010]: Making route(s) to <sip:1234567@192.168.111.20>
    22:04:23.390 [CM505001]: Ext.350: Device info: Device Identified: [Man: Cisco;Mod: SPA Series;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco/SPA508G-7.4.3a] PBX contact: [sip:350@192.168.111.20:5060]
    22:04:23.390 [CM503001]: Call(39): Incoming call from Ext.350 to <sip:1234567@192.168.111.20>

    Below is verbose and using route 1 by dialing "9".

    22:43:25.437 [CM503020]: Normal call termination. Reason: Not found
    22:43:25.437 [CM503016]: Call(4): Attempt to reach <sip:91234567@192.168.111.20> failed. Reason: Not Found
    22:43:25.437 [CM503003]: Call(4): Call to sip:1234567@192.168.111.21:5060 has failed; Cause: 404 Not Found; from IP:192.168.111.21:5060
    22:43:25.375 [CM503025]: Call(4): Calling Unknown:1234567@(Ln.10000@Patton 4960)@[Dev:sip:10000@192.168.111.21:5060]
    22:43:25.375 [MS210006] C:4.2:Offer provided. Connection(by pass mode): 192.168.111.121:16532(16533)
    22:43:25.343 [CM503004]: Call(4): Route 1: Unknown:1234567@(Ln.10000@Patton 4960)@[Dev:sip:10000@192.168.111.21:5060]
    22:43:25.343 [CM503010]: Making route(s) to <sip:91234567@192.168.111.20>
    22:43:25.343 [MS210000] C:4.1:Offer received. RTP connection: 192.168.111.121:16532(16533)
    22:43:25.343 Remote SDP is set for legC:4.1
    22:43:25.343 [CM505001]: Ext.350: Device info: Device Identified: [Man: Cisco;Mod: SPA Series;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco/SPA508G-7.4.3a] PBX contact: [sip:350@192.168.111.20:5060]
    22:43:25.312 [CM503001]: Call(4): Incoming call from Ext.350 to <sip:91234567@192.168.111.20>
    22:43:25.312 [CM500002]: Info on incoming INVITE:
    INVITE sip:91234567@192.168.111.20:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.111.121:5060;branch=z9hG4bK-50725666
    Max-Forwards: 70
    Contact: "Driver1"<sip:350@192.168.111.121:5060>
    To: <sip:91234567@192.168.111.20>
    From: "Driver1"<sip:350@192.168.111.20>;tag=169cf76717f469feo0
    Call-ID: e07ede5b-19988f9a@192.168.111.121
    CSeq: 102 INVITE
    Expires: 240
    Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, UPDATE
    Proxy-Authorization: Digest username="350",realm="3CXPhoneSystem",nonce="414d535c034ed7dd29:3347a9c56923dc259d20f804e393ca35",uri="sip:91234567@192.168.111.20:5060",algorithm=MD5,response="44469633debbbec99427164233c15629"
    Supported: replaces
    User-Agent: Cisco/SPA508G-7.4.3a
    Content-Length: 0

    Thanks for any help!
     
  2. paul1

    Joined:
    Jan 14, 2010
    Messages:
    80
    Likes Received:
    0
    It looks to me like your outbound rules are working fine. (Maybe the "Dial 9" rule should drop the 9 before sending it to the 4960.) If you login to the Patton 4960 and turn on some debugging options you may get some good clues. This document describes the steps: http://www.3cx.com/blog/docs/patton-isdn-debugging/
     
Thread Status:
Not open for further replies.