onging issue with smartnode 4960

Discussion in '3CX Phone System - General' started by jeremyn, Jun 17, 2008.

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

    Joined:
    Mar 25, 2008
    Messages:
    42
    Likes Received:
    0
    hi all this is an issue we have had with version 5 and now alo with version 6
    attached is a backup of our config and also the generated patton file and also our log files
    any help would be appreciated as we are banging our head against a wall at the moment

    17:37:48.404 Call::Terminate [CM503008]: Call(5): Call is terminated
    17:37:48.388 Call::RouteFailed [CM503015]: Call(5): Attempt to reach [sip:98007777@192.168.4.200] failed. Reason: Not Found
    17:37:48.388 CallCtrl::eek:nSelectRouteReq [CM503014]: Call(5): No known route to target: [sip:98007777@192.168.4.200]
    17:37:48.373 CallCtrl::eek:nSelectRouteReq [CM503010]: Making route(s) to [sip:98007777@192.168.4.200]
    17:37:48.373 Extension::printEndpointInfo [CM505001]: Ext.112: Device info: Device Identified: [Man: Snom;Mod: 320;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [snom320/6.5.8] Transport: [sip:192.168.4.200:5060]
    17:37:48.341 CallCtrl::eek:nIncomingCall [CM503001]: Call(5): Incoming call from Ext.112 to [sip:98007777@192.168.4.200]



    the status shows the patton is registerd correctly
     
  2. 5qg4

    5qg4 Active Member

    Joined:
    Jan 31, 2007
    Messages:
    643
    Likes Received:
    0
    Please check your outbound rule. Referred to the log, it seems no outbound rule had been defined for 4960.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. jeremyn

    Joined:
    Mar 25, 2008
    Messages:
    42
    Likes Received:
    0
    am I missing somthing ? we have rules saying that all calls go to the smart node ? in the outbond ruls it says calls should go the the patton_sn
     
  4. 5qg4

    5qg4 Active Member

    Joined:
    Jan 31, 2007
    Messages:
    643
    Likes Received:
    0
    Just restored your backup file to see what's wrong.

    All issue should be from your outbound rules setting:
    - Rule name "all" just defined prefix. No calls route had been defined.
    - Rule name "Rule for patton_sn" just defined calls will route to "patton_sn". No prefix had been defined.

    That's why no SIP request send to smartnode.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. jeremyn

    Joined:
    Mar 25, 2008
    Messages:
    42
    Likes Received:
    0
    so following your advice I changed all to include all calls of 10 digets and no prefix then call and get :

    11:20:55.263 Call::Terminate [CM503008]: Call(1): Call is terminated
    11:20:55.216 Call::RouteFailed [CM503015]: Call(1): Attempt to reach [sip:0412537369@192.168.4.200] failed. Reason: No Answer
    11:20:55.216 CallLeg::eek:nFailure [CM503003]: Call(1): Call to sip:0412537369@192.168.4.201:5060 has failed; Cause: 408 Request Timeout; internal
    11:20:23.012 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(1): Calling: PSTNline:0412537369@(Ln.10000@patton_sn)@[Dev:sip:10000@192.168.4.201:5060]
    11:20:23.012 CallCtrl::eek:nSelectRouteReq [CM503010]: Making route(s) to [sip:0412537369@192.168.4.200]

    but the called phone (a mobile does not ring)
     
  6. 5qg4

    5qg4 Active Member

    Joined:
    Jan 31, 2007
    Messages:
    643
    Likes Received:
    0
    Please post your Patton gateway debug log here.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. jeremyn

    Joined:
    Mar 25, 2008
    Messages:
    42
    Likes Received:
    0
    thanks for your help log attached
     
  8. 5qg4

    5qg4 Active Member

    Joined:
    Jan 31, 2007
    Messages:
    643
    Likes Received:
    0
    Actually, the attached file not a Patton debug log. Before re-post the debug log again.
    Please let me know status of DN 10000 first. What color of its indicator(red or green)? And let me know can SN4960 respond the PING test by 3CX box.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. jeremyn

    Joined:
    Mar 25, 2008
    Messages:
    42
    Likes Received:
    0
    yes we have green light and can ping the smartnode
    we have 2 different ip ranges, 192.168.4.x and 192.168.3.x
    all phones are on the 192.168.3.x range
    pc's on te 192.168.4.x range
    the server is on both (2 nic's )
    and the smart node is also on both
    and 3cx an ping both intercaces on smartnode (192.168.3.201 and 192.168.4.201)
     
  10. jeremyn

    Joined:
    Mar 25, 2008
    Messages:
    42
    Likes Received:
    0
    also can u tell me where I would find the patton log you were refering to ?

    thanks
     
  11. jeremyn

    Joined:
    Mar 25, 2008
    Messages:
    42
    Likes Received:
    0
    this the debug log ?

    2008-06-17T07:17:36 : LOGINFO : Link up on interface ethernet 0 0 1
    2008-06-17T07:17:36 : LOGINFO : Link up on interface IF_IP_LAN
    2008-06-17T07:18:24 : LOGINFO : Link down on interface ethernet 0 0 1
    2008-06-17T07:18:24 : LOGINFO : Link down on interface IF_IP_LAN
    2008-06-17T07:18:26 : LOGINFO : Link up on interface ethernet 0 0 0
    2008-06-17T07:18:26 : LOGINFO : Link up on interface IF_IP_WAN
    2008-06-17T07:19:05 : LOGINFO : Link down on interface ethernet 0 0 0
    2008-06-17T07:19:05 : LOGINFO : Link down on interface IF_IP_WAN
    2008-06-17T07:19:07 : LOGINFO : Link up on interface ethernet 0 0 1
    2008-06-17T07:19:07 : LOGINFO : Link up on interface IF_IP_LAN
    2008-06-17T07:19:11 : LOGINFO : Link up on interface ethernet 0 0 0
    2008-06-17T07:19:11 : LOGINFO : Link up on interface IF_IP_WAN
    2008-06-17T07:19:39 : LOGINFO : Link down on interface ethernet 0 0 1
    2008-06-17T07:19:39 : LOGINFO : Link down on interface IF_IP_LAN
    2008-06-17T07:19:42 : LOGINFO : Link down on interface ethernet 0 0 0
    2008-06-17T07:19:42 : LOGINFO : Link down on interface IF_IP_WAN
    2008-06-17T07:19:46 : LOGINFO : Link up on interface ethernet 0 0 1
    2008-06-17T07:19:46 : LOGINFO : Link up on interface IF_IP_LAN
    2008-06-17T07:19:50 : LOGINFO : Link up on interface ethernet 0 0 0
    2008-06-17T07:19:50 : LOGINFO : Link up on interface IF_IP_WAN
    2008-06-17T07:20:00 : LOGINFO : Link down on interface ethernet 0 0 1
    2008-06-17T07:20:00 : LOGINFO : Link down on interface IF_IP_LAN
    2008-06-17T07:20:25 : LOGINFO : Auto Configuration (DHCP):
    IP Address of interface IF_IP_WAN set to 192.168.3.47
    Default gateway set to 192.168.3.1
    Added name server 192.168.3.1

    2008-06-18T04:13:21 : LOGINFO : Link down on interface ethernet 0 0 0
    2008-06-18T04:13:21 : LOGINFO : Link down on interface IF_IP_WAN
    2008-06-18T04:13:31 : LOGINFO : Link up on interface ethernet 0 0 0
    2008-06-18T04:13:31 : LOGINFO : Link up on interface IF_IP_WAN
    2008-06-18T04:14:23 : LOGINFO : Link up on interface ethernet 0 0 1
    2008-06-18T04:14:23 : LOGINFO : Link up on interface IF_IP_LAN
    2008-06-18T04:16:08 : LOGINFO : Link down on interface ethernet 0 0 1
    2008-06-18T04:16:08 : LOGINFO : Link down on interface IF_IP_LAN
    2008-06-18T04:16:37 : LOGINFO : Link down on interface ethernet 0 0 0
    2008-06-18T04:16:37 : LOGINFO : Link down on interface IF_IP_WAN
    2008-06-18T04:17:05 : LOGINFO : Link up on interface ethernet 0 0 0
    2008-06-18T04:17:05 : LOGINFO : Link up on interface IF_IP_WAN
    2008-06-18T04:17:51 : LOGINFO : Link down on interface ethernet 0 0 0
    2008-06-18T04:17:51 : LOGINFO : Link down on interface IF_IP_WAN
    2008-06-18T04:17:55 : LOGINFO : Link up on interface ethernet 0 0 1
    2008-06-18T04:17:55 : LOGINFO : Link up on interface IF_IP_LAN
    2008-06-18T04:18:52 : LOGINFO : Link up on interface ethernet 0 0 0
    2008-06-18T04:18:52 : LOGINFO : Link up on interface IF_IP_WAN
    2008-06-18T04:19:49 : LOGWARNING : router/IF_IP_WAN (Renw): T2 expired. Trying to rebind lease.
    2008-06-18T04:20:27 : LOGWARNING : router/IF_IP_WAN (Rbnd): Lease has expired
    2008-06-18T04:20:27 : LOGINFO : Auto Configuration (DHCP):
    Interface IF_IP_WAN shut down
    Removed default route
    Removed name servers

    2008-06-18T04:20:58 : LOGERROR : AutoConfig: Could not change IP interface settings
    2008-06-18T04:20:59 : LOGINFO : Link down on interface IF_IP_WAN
    2008-06-18T04:53:09 : LOGINFO : Link down on interface ethernet 0 0 0
    2008-06-18T04:53:40 : LOGINFO : Link up on interface ethernet 0 0 0
    2008-06-18T04:53:40 : LOGINFO : Link up on interface IF_IP_WAN
    2008-06-18T04:53:58 : LOGINFO : Auto Configuration (DHCP):
    Interface IF_IP_WAN shut down
    Removed default route
    Removed name servers
     
  12. jeremyn

    Joined:
    Mar 25, 2008
    Messages:
    42
    Likes Received:
    0
    digging around the smart node I found this which looks like ti comes from the 3cx generated config

    2008-06-18T06:01:40 : LOGWARNING : Config: Line 57: SN4960/1E15V(pf-sip)[default]#no autonomous-transitioning
    2008-06-18T06:01:40 : LOGWARNING : Config: % ^ Keyword mismatch
    2008-06-18T06:01:40 : LOGWARNING : Config: Line 87: SN4960/1E15V(if-sip)[IF_SIP_0]#bind gateway GW_SIP_0
    2008-06-18T06:01:40 : LOGWARNING : Config: % ^ Keyword mismatch
    2008-06-18T06:01:40 : LOGWARNING : Config: Line 90: SN4960/1E15V(if-sip)[IF_SIP_0]#service default
    2008-06-18T06:01:40 : LOGWARNING : Config: % ^ Keyword mismatch
    2008-06-18T06:01:40 : LOGWARNING : Config: Line 91: SN4960/1E15V(if-sip)[IF_SIP_0]#route default dest-interface IF_ISDN_0
    2008-06-18T06:01:40 : LOGWARNING : Config: % ^ Keyword mismatch
    2008-06-18T06:01:40 : LOGWARNING : Config: Line 92: SN4960/1E15V(if-sip)[IF_SIP_0]#remote-party-id called-party
    2008-06-18T06:01:40 : LOGWARNING : Config: % ^ Keyword mismatch
    2008-06-18T06:01:40 : LOGWARNING : Config: Line 99: SN4960/1E15V(ctx-cs)[switch]#gateway sip GW_SIP_0
    2008-06-18T06:01:40 : LOGWARNING : Config: % ^ Keyword mismatch
    2008-06-18T06:01:40 : LOGWARNING : Config: Line 100: SN4960/1E15V(ctx-cs)[switch]#call-signaling-port 5060
    2008-06-18T06:01:40 : LOGWARNING : Config: % ^ Keyword mismatch
    2008-06-18T06:01:40 : LOGWARNING : Config: Line 101: SN4960/1E15V(ctx-cs)[switch]#bind interface IF_IP_LAN router
    2008-06-18T06:01:40 : LOGWARNING : Config: % ^ Keyword mismatch
    2008-06-18T06:01:40 : LOGWARNING : Config: Line 103: SN4960/1E15V(ctx-cs)[switch]#service default
    2008-06-18T06:01:40 : LOGWARNING : Config: % ^ Keyword mismatch
    2008-06-18T06:01:40 : LOGWARNING : Config: Line 104: SN4960/1E15V(ctx-cs)[switch]#domain 192.168.4.200
    2008-06-18T06:01:40 : LOGWARNING : Config: % ^ Keyword mismatch
    2008-06-18T06:01:40 : LOGWARNING : Config: Line 105: SN4960/1E15V(ctx-cs)[switch]#defaultserver manual 192.168.4.200 loose-router
    2008-06-18T06:01:40 : LOGWARNING : Config: % ^ Keyword mismatch
    2008-06-18T06:01:40 : LOGWARNING : Config: Line 106: SN4960/1E15V(ctx-cs)[switch]#registration-lifetime 300
    2008-06-18T06:01:40 : LOGWARNING : Config: % ^ Keyword mismatch
    2008-06-18T06:01:40 : LOGWARNING : Config: Line 107: SN4960/1E15V(ctx-cs)[switch]#registration manual 192.168.4.200
    2008-06-18T06:01:40 : LOGWARNING : Config: % ^ Keyword mismatch
    2008-06-18T06:01:40 : LOGWARNING : Config: Line 108: SN4960/1E15V(ctx-cs)[switch]#user 10000 authenticate name 10000 password 10000 default register
    2008-06-18T06:01:40 : LOGWARNING : Config: % ^ Keyword mismatch
    2008-06-18T06:01:40 : LOGWARNING : Config: Line 110: SN4960/1E15V(ctx-cs)[switch]#gateway sip GW_SIP_0
    2008-06-18T06:01:40 : LOGWARNING : Config: % ^ Keyword mismatch
    2008-06-18T06:01:42 : LOGINFO : Link up on interface e1t1 0 0 0
    2008-06-18T06:01:42 : LOGINFO : Link up on interface ISDN 0 0
    2008-06-18T06:01:42 : LOGINFO : Link up on interface ethernet 0 0 1
    2008-06-18T06:01:42 : LOGINFO : Link up on interface IF_IP_LAN
    2008-06-18T06:01:42 : LOGINFO : Link up on interface ethernet 0 0 0
    2008-06-18T06:01:42 : LOGINFO : Link up on interface IF_IP_WAN
    2008-06-18T06:01:42 : LOGINFO : Warm start.
    2008-06-18T06:02:36 : LOGINFO : Auto Configuration (DHCP):
    IP Address of interface IF_IP_WAN set to 192.168.3.47
    Default gateway set to 192.168.3.1
    Added name server 192.168.3.1
     
  13. 5qg4

    5qg4 Active Member

    Joined:
    Jan 31, 2007
    Messages:
    643
    Likes Received:
    0
    3CX recommended setting should be connect the SN4960 to your network via it LAN port only. Please try to temporarily disconnected all NIC at 192.168.4.0 to see it works or not. Since all your phones are connected at subnet of 192.168.3.0
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. 5qg4

    5qg4 Active Member

    Joined:
    Jan 31, 2007
    Messages:
    643
    Likes Received:
    0
    Telnet to your SN4960 at command prompt type following command:
    enable
    debug gateway sip transport detail 5
    debug gateway sip error detail 5
    debug ccisdn error
    debug ccisdn signaling
    debug call-control detail 5
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. jeremyn

    Joined:
    Mar 25, 2008
    Messages:
    42
    Likes Received:
    0
    k changed 3cx to use the 192.168.3.x interface and got new message

    16:46:41.784 Call::Terminate [CM503008]: Call(1): Call is terminated
    16:46:41.769 Call::RouteFailed [CM503015]: Call(1): Attempt to reach [sip:0412537369@192.168.4.200] failed. Reason: Not Registered
    16:46:41.737 Call::RouteFailed [CM503015]: Call(1): Attempt to reach [sip:0412537369@192.168.4.200] failed. Reason: Not Registered
    16:46:41.737 CallCtrl::eek:nSelectRouteReq [CM503016]: Call(1): Target is not registered: PSTNline:0412537369 dialed on (AnyLine@patton_sn1)
    16:46:41.737 Line::Line [CM303003]: There are no available outbound lines on gateway patton_sn1 at this time.
    16:46:41.737 CallCtrl::eek:nSelectRouteReq [CM503010]: Making route(s) to [sip:0412537369@192.168.4.200]
    16:46:41.737 Extension::printEndpointInfo [CM505001]: Ext.112: Device info: Device Identified: [Man: Snom;Mod: 320;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [snom320/6.5.8] Transport: [sip:192.168.4.200:5060]


    about to post debug
     
  16. jeremyn

    Joined:
    Mar 25, 2008
    Messages:
    42
    Likes Received:
    0
    I get the following error
    192.168.4.201>enable
    192.168.4.201#debug gateway sip transport detail 5
    % ^ Keyword mismatch
     
  17. jeremyn

    Joined:
    Mar 25, 2008
    Messages:
    42
    Likes Received:
    0
    also tried it with caps on the G for Gateway
     
  18. 5qg4

    5qg4 Active Member

    Joined:
    Jan 31, 2007
    Messages:
    643
    Likes Received:
    0
    Please restart your 3CX box to make sure that it use the new setting. Referred to the log, you still use 192.168.4.0.
    Try to put your Phone system to 192.168.3.x. That's mean to form a simple network to make sure it works (3CX box, gateways and phones at 192.168.3.x).
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  19. jeremyn

    Joined:
    Mar 25, 2008
    Messages:
    42
    Likes Received:
    0
    restarted server now getting

    20:53:05.677 Call::Terminate [CM503008]: Call(4): Call is terminated
    20:53:05.615 Call::RouteFailed [CM503015]: Call(4): Attempt to reach [sip:0412537369@192.168.3.200] failed. Reason: Server Failure
    20:53:05.615 CallLeg::eek:nFailure [CM503003]: Call(4): Call to sip:0412537369@192.168.4.201:5060 has failed; Cause: 500 Internal Server Error; from IP:192.168.4.201:5060
    20:53:05.474 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(4): Calling: PSTNline:0412537369@(Ln.10000@patton_sn1)@[Dev:sip:10000@192.168.4.201:5060]
    20:53:05.474 CallCtrl::eek:nSelectRouteReq [CM503010]: Making route(s) to [sip:0412537369@192.168.3.200]
    :cry: :cry: :cry:
     
  20. 5qg4

    5qg4 Active Member

    Joined:
    Jan 31, 2007
    Messages:
    643
    Likes Received:
    0
    Still found your gateway at "192.168.4.201" highlight in red color.

    Update the IP for SN4960 at 3CX box from "192.168.4.201" to "192.168.3.201". Make sure that there is NO device at "192.168.4.0" is active to test!!!
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.