Call dropping with patton 4114

Discussion in '3CX Phone System - General' started by tsteffens, May 10, 2012.

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

    Joined:
    Jul 14, 2011
    Messages:
    85
    Likes Received:
    1
    We have a strange issue that has been going on for a while now. We have a single phone line coming into a patton 4114 device. Randomly a call will come in and provide caller id and ring twice, then the call will disconnect and 3 seconds later the call will come back as "anonymous" basically no caller id.

    I have spoke with a user on the other end of one of these calls and they tell me the phone rings the entire time.

    Below is a call that just happened via the server log.

    Code:
    16:06:46.537  [CM505001]: Ext.222: Device info: Device Identified: [Man: Yealink;Mod: T28;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Yealink SIP-T28P 2.61.0.70] PBX contact: [sip:222@192.168.254.69:5060]
    16:06:46.537  [CM503002]: Call(1631): Alerting sip:222@192.168.254.156:5062
    16:06:45.846  [CM503025]: Call(1631): Calling Ext:Ext.222@[Dev:sip:222@192.168.254.156:5062]
    16:06:45.770  [CM503004]: Call(1631): Route 1: Ext:Ext.222@[Dev:sip:222@192.168.254.156:5062]
    16:06:45.770  [CM503010]: Making route(s) to <sip:222@127.0.0.1:5060>
    16:06:19.449  [CM503003]: Call(1631): Call to sip:222@192.168.254.69 has failed; Cause: 487 Request Terminated; from IP:192.168.254.156:5062
    16:06:19.143  [CM503007]: Call(1631): Device joined: sip:800@127.0.0.1:40600;rinstance=228bdd5c8c8f9a6d
    16:06:19.141  [CM503007]: Call(1631): Device joined: sip:10004@192.168.254.70:5062
    16:06:19.126  [CM505001]: Ext.800: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX IVR;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX IVR] PBX contact: [sip:800@127.0.0.1:5060]
    16:06:19.126  [CM503002]: Call(1631): Alerting sip:800@127.0.0.1:40600;rinstance=228bdd5c8c8f9a6d
    16:06:19.080  [CM503003]: Call(1631): Call to sip:225@192.168.254.69 has failed; Cause: 487 Request Terminated; from IP:192.168.254.200:5060
    16:06:19.020  [CM503003]: Call(1631): Call to sip:224@192.168.254.69 has failed; Cause: 487 Request Terminated; from IP:192.168.254.198:5062
    16:06:18.993  [CM503003]: Call(1631): Call to sip:226@192.168.254.69 has failed; Cause: 487 Request Terminated; from IP:192.168.254.85:5060
    16:06:18.988  [CM503003]: Call(1631): Call to sip:100@192.168.254.69 has failed; Cause: 487 Request Terminated; from IP:192.168.254.180:5062
    16:06:18.987  [CM503025]: Call(1631): Calling Ext:Ext.800@[Dev:sip:800@127.0.0.1:40600;rinstance=228bdd5c8c8f9a6d]
    16:06:18.960  [CM503005]: Call(1631): Forwarding: Ext:Ext.800@[Dev:sip:800@127.0.0.1:40600;rinstance=228bdd5c8c8f9a6d]
    16:06:04.604  [CM505001]: Ext.224: Device info: Device Identified: [Man: Yealink;Mod: T28;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Yealink SIP-T28P 2.61.0.70] PBX contact: [sip:224@192.168.254.69:5060]
    16:06:04.604  [CM503002]: Call(1631): Alerting sip:224@192.168.254.198:5062
    16:06:04.549  [CM505001]: Ext.222: Device info: Device Identified: [Man: Yealink;Mod: T28;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Yealink SIP-T28P 2.61.0.70] PBX contact: [sip:222@192.168.254.69:5060]
    16:06:04.545  [CM503002]: Call(1631): Alerting sip:222@192.168.254.156:5062
    16:06:04.531  [CM505001]: Ext.100: Device info: Device Identified: [Man: Yealink;Mod: T28;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Yealink SIP-T28P 2.61.0.70] PBX contact: [sip:100@192.168.254.69:5060]
    16:06:04.531  [CM503002]: Call(1631): Alerting sip:100@192.168.254.180:5062
    16:06:04.062  [CM505001]: Ext.225: Device info: Device Identified: [Man: Grandstream;Mod: GXP Series;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream GXP2100 1.0.1.110] PBX contact: [sip:225@192.168.254.69:5060]
    16:06:04.061  [CM503002]: Call(1631): Alerting sip:225@192.168.254.200:5060;user=phone
    16:06:03.921  [CM503025]: Call(1631): Calling RingAll805[Ext.100,Ext.222,Ext.224,Ext.223,Ext.225,Ext.226]@[Dev:sip:226@192.168.254.85:5060]
    16:06:03.908  [CM503025]: Call(1631): Calling RingAll805[Ext.100,Ext.222,Ext.224,Ext.223,Ext.225,Ext.226]@[Dev:sip:225@192.168.254.200:5060;user=phone]
    16:06:03.895  [CM503025]: Call(1631): Calling RingAll805[Ext.100,Ext.222,Ext.224,Ext.223,Ext.225,Ext.226]@[Dev:sip:224@192.168.254.198:5062]
    16:06:03.882  [CM503025]: Call(1631): Calling RingAll805[Ext.100,Ext.222,Ext.224,Ext.223,Ext.225,Ext.226]@[Dev:sip:222@192.168.254.156:5062]
    16:06:03.868  [CM503025]: Call(1631): Calling RingAll805[Ext.100,Ext.222,Ext.224,Ext.223,Ext.225,Ext.226]@[Dev:sip:100@192.168.254.180:5062]
    16:06:03.832  [CM503004]: Call(1631): Route 1: RingAll805[Ext.100,Ext.222,Ext.224,Ext.223,Ext.225,Ext.226]@[Dev:sip:100@192.168.254.180:5062,Dev:sip:222@192.168.254.156:5062,Dev:sip:224@192.168.254.198:5062,Dev:sip:225@192.168.254.200:5060;user=phone,Dev:sip:226@192.168.254.85:5060]
    16:06:03.826  [CM503010]: Making route(s) to <sip:805@192.168.254.69:5060>
    16:06:03.823  [CM505002]: Gateway:[Patton Line 1] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Patton SN4114 JO EUI 00A0BA05A875 R5.7 2011-07-01 H323 SIP FXS FXO M5T SIP Stack/4.0.30.30] PBX contact: [sip:10004@192.168.254.69:5060]
    16:06:03.821  [CM503001]: Call(1631): Incoming call from anonymous@(Ln.10004@Patton Line 1) to <sip:805@192.168.254.69:5060>
    16:06:03.804  [CM503012]: Inbound office hours rule (unnamed) for 10004 forwards to DN:805
    16:05:51.186  [CM503003]: Call(1630): Call to sip:225@192.168.254.69 has failed; Cause: 487 Request Terminated; from IP:192.168.254.200:5060
    16:05:51.162  [CM503003]: Call(1630): Call to sip:224@192.168.254.69 has failed; Cause: 487 Request Terminated; from IP:192.168.254.198:5062
    16:05:51.121  [CM503003]: Call(1630): Call to sip:100@192.168.254.69 has failed; Cause: 487 Request Terminated; from IP:192.168.254.180:5062
    16:05:51.116  [CM503003]: Call(1630): Call to sip:222@192.168.254.69 has failed; Cause: 487 Request Terminated; from IP:192.168.254.156:5062
    16:05:51.087  [CM503003]: Call(1630): Call to sip:226@192.168.254.69 has failed; Cause: 487 Request Terminated; from IP:192.168.254.85:5060
    16:05:50.980  [CM503008]: Call(1630): Call is terminated
    16:05:41.676  [CM505001]: Ext.224: Device info: Device Identified: [Man: Yealink;Mod: T28;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Yealink SIP-T28P 2.61.0.70] PBX contact: [sip:224@192.168.254.69:5060]
    16:05:41.674  [CM503002]: Call(1630): Alerting sip:224@192.168.254.198:5062
    16:05:41.665  [CM505001]: Ext.222: Device info: Device Identified: [Man: Yealink;Mod: T28;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Yealink SIP-T28P 2.61.0.70] PBX contact: [sip:222@192.168.254.69:5060]
    16:05:41.664  [CM503002]: Call(1630): Alerting sip:222@192.168.254.156:5062
    16:05:41.659  [CM505001]: Ext.100: Device info: Device Identified: [Man: Yealink;Mod: T28;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Yealink SIP-T28P 2.61.0.70] PBX contact: [sip:100@192.168.254.69:5060]
    16:05:41.658  [CM503002]: Call(1630): Alerting sip:100@192.168.254.180:5062
    16:05:41.131  [CM505001]: Ext.225: Device info: Device Identified: [Man: Grandstream;Mod: GXP Series;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream GXP2100 1.0.1.110] PBX contact: [sip:225@192.168.254.69:5060]
    16:05:41.130  [CM503002]: Call(1630): Alerting sip:225@192.168.254.200:5060;user=phone
    16:05:40.972  [CM503025]: Call(1630): Calling RingAll805[Ext.100,Ext.222,Ext.224,Ext.223,Ext.225,Ext.226]@[Dev:sip:226@192.168.254.85:5060]
    16:05:40.959  [CM503025]: Call(1630): Calling RingAll805[Ext.100,Ext.222,Ext.224,Ext.223,Ext.225,Ext.226]@[Dev:sip:225@192.168.254.200:5060;user=phone]
    16:05:40.946  [CM503025]: Call(1630): Calling RingAll805[Ext.100,Ext.222,Ext.224,Ext.223,Ext.225,Ext.226]@[Dev:sip:224@192.168.254.198:5062]
    16:05:40.932  [CM503025]: Call(1630): Calling RingAll805[Ext.100,Ext.222,Ext.224,Ext.223,Ext.225,Ext.226]@[Dev:sip:222@192.168.254.156:5062]
    16:05:40.910  [CM503025]: Call(1630): Calling RingAll805[Ext.100,Ext.222,Ext.224,Ext.223,Ext.225,Ext.226]@[Dev:sip:100@192.168.254.180:5062]
    16:05:40.846  [CM503004]: Call(1630): Route 1: RingAll805[Ext.100,Ext.222,Ext.224,Ext.223,Ext.225,Ext.226]@[Dev:sip:100@192.168.254.180:5062,Dev:sip:222@192.168.254.156:5062,Dev:sip:224@192.168.254.198:5062,Dev:sip:225@192.168.254.200:5060;user=phone,Dev:sip:226@192.168.254.85:5060]
    16:05:40.841  [CM503010]: Making route(s) to <sip:805@192.168.254.69:5060>
    16:05:40.839  [CM505002]: Gateway:[Patton Line 1] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Patton SN4114 JO EUI 00A0BA05A875 R5.7 2011-07-01 H323 SIP FXS FXO M5T SIP Stack/4.0.30.30] PBX contact: [sip:10004@192.168.254.69:5060]
    16:05:40.837  [CM503001]: Call(1630): Incoming call from 6179485300@(Ln.10004@Patton Line 1) to <sip:805@192.168.254.69:5060>
    16:05:40.799  [CM503012]: Inbound office hours rule (unnamed) for 10004 forwards to DN:805
    
     
  2. RichardCrabb1

    RichardCrabb1 New Member

    Joined:
    Mar 7, 2009
    Messages:
    196
    Likes Received:
    0
    Perhaps the Patton is not set correctly for the ring cadence in your country? If this is the case then the timers for the inbound ringing may be slightly incorrect but close enough for it to work for most of the time.

    Is this something that you can look at?

    Kind regards
    Richard Crabb
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.