Inbound call problems

Discussion in '3CX Phone System - General' started by yaquaholic, Apr 18, 2013.

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

    Joined:
    Apr 17, 2013
    Messages:
    5
    Likes Received:
    0
    Hello fellow users,

    I recently started in a new position and one of my responsibilities is to look after the Grandstream VOIP/PSTN 3CX setup we have here. Anyway first day on the job and the phones system starts playing up, any caller dialing our PSTN line does not connect, but dialing the VOIP number does. On the GXW4104 we can see the line go "Line 1: busy Connected, idle" and we're hearing the ringtone as we dial in, but then the GXW4104 drops back to "Line 1: Connected, idle", but the ringtone keeps going on the phone we dial from.

    The chap who implemented the system left a nice PDF detailing the config of our GXW4104, that was working fine, until the day I arrived. Typically they would just restart the GXW4104 and all would be sorted, but not on this Monday morning.I have checked this against the device's config and all looks identical. We have tried getting 3CX Phone System to create the configuration, but no joy here.

    So could I ask some assistance from the forum group to possibly point a finger in the right direction to where I(we) are going wrong please? Below are screenshots from the various config pages that might help...










    Any ideas?

    Many thanks - yaquaholic
     

    Attached Files:

  2. yaquaholic

    Joined:
    Apr 17, 2013
    Messages:
    5
    Likes Received:
    0
    Re: Intermittent outward bound VOIP call problems

    Some more screen shots...




    Thanks.
     

    Attached Files:

  3. craigreilly

    craigreilly Well-Known Member

    Joined:
    Feb 1, 2012
    Messages:
    3,401
    Likes Received:
    273
    do the log files or system logs show anything of consequence?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. yaquaholic

    Joined:
    Apr 17, 2013
    Messages:
    5
    Likes Received:
    0
    The only thing that stands out is:
    Code:
    18-Apr-2013 18:19:20.615   [CM503003]: Call(C:197): Call to <sip:201@192.168.1.10:5060> has failed; Cause: 487 Request Terminated/INVITE from 192.168.1.23:5060
    18-Apr-2013 18:19:20.615   Session 145053 has failed in leg L:197.3[Extn] ; Cause: 487 Request Terminated/INVITE from 192.168.1.23:5060
    18-Apr-2013 18:19:20.595   L:197.5[Extn]: Terminating targets, reason: SIP ;cause=487 ;text="Request Terminated"
    18-Apr-2013 18:19:20.595   Leg L:197.5[Extn] is terminated: Cause: 487 Request Terminated/INVITE from 192.168.1.22:5060
    18-Apr-2013 18:19:20.595   L:197.5[Extn] got Terminated Recv 487/INVITE from 192.168.1.22:5060 tid=7f6962321e5db502 Call-ID=ZmUyNTk4NmEyYjVlYjdjMTU0NGY3YjM4YmNmODYyNjk.:
    SIP/2.0 487 Request Terminated
    Does anyone know what Cause 487 might mean?

    Thanks.
     
  5. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,848
    Likes Received:
    299
    487= Request Terminated ...Request has terminated by bye or cancel

    It doesn't tell you much, unfortunately.

    I'm not sure what this has to do with the gateway as it is a failed call between extensions.
     
Thread Status:
Not open for further replies.